"Clip-launch-other-clip" lag issue (Internal routing prob)
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
"Clip-launch-other-clip" lag issue (Internal routing prob)
Ok, I've been looking online for a while but can't find a good answer to my question. My idea is to use a dummy MIDI or Audio clip to control another MIDI or Audio clip on another channel. With control I mean launch and stop the clip. So for instance, I would have 2 channels, with an audio clip on channel one, and a MIDI clip on channel two. Then when I launch the MIDI clip, I would like for the audio clip to automatically start.
To do this, I enabled the IAC driver (I'm on Snow Leopard and have Live 7.0.18), and made a MIDI clip playing note G8. Then in the I/O, I send the MIDI to the IAC driver. I have this all set up so it will sync, and control. Then with the MIDI map, I set the audio clip to start for note G8.
So far so good. Now when I launch the MIDI clip, the audio clip also launches, but there is a significant lag (silence of 5s) before the audio clip starts, which makes it unuseable.
Now for my question. Is there something I can do to reduce the lag? Or is there an easier way of achieving my goal without the IAC driver for instance?
Thanks for all the help!!!!!
To do this, I enabled the IAC driver (I'm on Snow Leopard and have Live 7.0.18), and made a MIDI clip playing note G8. Then in the I/O, I send the MIDI to the IAC driver. I have this all set up so it will sync, and control. Then with the MIDI map, I set the audio clip to start for note G8.
So far so good. Now when I launch the MIDI clip, the audio clip also launches, but there is a significant lag (silence of 5s) before the audio clip starts, which makes it unuseable.
Now for my question. Is there something I can do to reduce the lag? Or is there an easier way of achieving my goal without the IAC driver for instance?
Thanks for all the help!!!!!
-
chapelier fou
- Posts: 6355
- Joined: Mon May 15, 2006 12:15 pm
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
i think it's just because of the global quantization. Put your triggering note at the end of the clip.
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Thanks for the tip. However, I already thought of this, so it is not the problem.chapelier fou wrote:i think it's just because of the global quantization. Put your triggering note at the end of the clip.
-
chapelier fou
- Posts: 6355
- Joined: Mon May 15, 2006 12:15 pm
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Tried with quantize to "none", just for testing ?
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Just checked it, but it still lags.
I also reduced the latency from 512 to 64, and the lag reduces, but it's still to much. I also want to run this alongside Traktor, so I don't want to set the latency too low. I only have 2 Gb of RAM.
I also reduced the latency from 512 to 64, and the lag reduces, but it's still to much. I also want to run this alongside Traktor, so I don't want to set the latency too low. I only have 2 Gb of RAM.
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
What your asking is generally impossible without latency, how does ableton know to launch the next track before your clip has played?
I dont know what to really suggest, could you not midi map the play buttons of both clips?
Cheers
D
I dont know what to really suggest, could you not midi map the play buttons of both clips?
Cheers
D
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
I understand the latency part, and that it's impossible to get rid of. However, the lag I'm talking about is accompanied by a total screen freeze and a pause in the sound (if other clips are also playing). So this isn't a latency issue I'm taking about.S4racen wrote:What your asking is generally impossible without latency, how does ableton know to launch the next track before your clip has played?
I dont know what to really suggest, could you not midi map the play buttons of both clips?
Cheers
D
This brings me to the second part of the question: Is there another way to achieve this?
When launching a clip with quantisation set to 1 bar, it will wait for the first beat of the new bar. In this time, it should be possible for the clip to send some kind of signal to another clip, making it possible for both clips to start simultaneously. Any ideas on how to achieve this?
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Yeah with max4live, using midi just aint gonna cut it as the clip itself would have to be playing to send the note....
M4L can read that a clip is triggered ready to play and can perform an action based on it...
What controller are you using that you can't hit two buttons at the same time??
Cheers
D
M4L can read that a clip is triggered ready to play and can perform an action based on it...
What controller are you using that you can't hit two buttons at the same time??
Cheers
D
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
I don't want to link two clips to a controller button. I want to have 1 channel with launch clips. These launch clips should trigger clips on other channels, be it an Impulse controlled by MIDI, a VST synth or an audio clip or whatever. But the main adea is to have 1 channel with all the launch clips that I can scroll through with an endless rotary, and to launch the highlighted launch clip by a push of the rotary, meaning no horizontal scrolling through individual channels is needed, only vertical scrolling through the clips.S4racen wrote:Yeah with max4live, using midi just aint gonna cut it as the clip itself would have to be playing to send the note....
M4L can read that a clip is triggered ready to play and can perform an action based on it...
What controller are you using that you can't hit two buttons at the same time??
Cheers
D
Did I explain it good enough?
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Then it sounds like you want to group your tracks??
Cheers
D
Cheers
D
-
pepezabala
- Posts: 3503
- Joined: Mon Jun 07, 2004 4:29 pm
- Location: In Berlin, finally
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Billdesman wrote:I don't want to link two clips to a controller button. I want to have 1 channel with launch clips. These launch clips should trigger clips on other channels, be it an Impulse controlled by MIDI, a VST synth or an audio clip or whatever. But the main adea is to have 1 channel with all the launch clips that I can scroll through with an endless rotary, and to launch the highlighted launch clip by a push of the rotary, meaning no horizontal scrolling through individual channels is needed, only vertical scrolling through the clips.S4racen wrote:Yeah with max4live, using midi just aint gonna cut it as the clip itself would have to be playing to send the note....
M4L can read that a clip is triggered ready to play and can perform an action based on it...
What controller are you using that you can't hit two buttons at the same time??
Cheers
D
Did I explain it good enough?
and what prevents you from triggering scenes? Scenes are just like that, "launch buttons" stacked vertically.
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
I am running Live 7, which don't have group tracks. But, is it possible to group MIDI and audio tracks together? If so, I might just have to upgrade to 8.S4racen wrote:Then it sounds like you want to group your tracks??
Cheers
D
As stated above, I'm running Live 7. I would like to color code everything, which is not possible in 7. This is why I want to use clips instead. But, this might just be the easiest alternative. I'm going to try this out.pepezabala wrote:Billdesman wrote:I don't want to link two clips to a controller button. I want to have 1 channel with launch clips. These launch clips should trigger clips on other channels, be it an Impulse controlled by MIDI, a VST synth or an audio clip or whatever. But the main adea is to have 1 channel with all the launch clips that I can scroll through with an endless rotary, and to launch the highlighted launch clip by a push of the rotary, meaning no horizontal scrolling through individual channels is needed, only vertical scrolling through the clips.S4racen wrote:Yeah with max4live, using midi just aint gonna cut it as the clip itself would have to be playing to send the note....
M4L can read that a clip is triggered ready to play and can perform an action based on it...
What controller are you using that you can't hit two buttons at the same time??
Cheers
D
Did I explain it good enough?
and what prevents you from triggering scenes? Scenes are just like that, "launch buttons" stacked vertically.
Thanks!
PS. I might be nagging, but I really wat to get everything exactly as I want it, without compromising if possible. So my search isn't over yet!
-
chapelier fou
- Posts: 6355
- Joined: Mon May 15, 2006 12:15 pm
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
was about to say about grouping tracks.
Or if you trigger the clips via midi, you do know that you can map several clips to the same button ?
Or if you trigger the clips via midi, you do know that you can map several clips to the same button ?
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
-
chapelier fou
- Posts: 6355
- Joined: Mon May 15, 2006 12:15 pm
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
sorry, it's been covered above.
MacBook Pro 13" Retina i7 2.8 GHz OS 10.13, L10.0.1, M4L.
MacStudio M1Max 32Go OS 12.3.1
MacStudio M1Max 32Go OS 12.3.1
-
Billdesman
- Posts: 34
- Joined: Wed Jul 19, 2006 4:32 pm
- Location: The Netherlands
- Contact:
Re: "Clip-launch-other-clip" lag issue (Internal routing prob)
Any other ideas?