How to launch a more natural clip in session view?

[davesmiths]

Hi

Is it possible to launch a more natural clip in session view?

For example, when someone intends to start singing on the first beat of a bar, they produce sound just before the beat and when on the beat the sound peaks. Using the clips in session view, is it possible to set-up a clip so that this is possible?

I hope I've made sense there, it's easier in my head than I'm describing

all the best
Dave

[oddstep]

Like an eigth note lead in? Make the loop start point later than the clip launch point. Make the clip longer than the loop.

[davesmiths]

Thanks oddstep, yeah like an eighth note lead in. I tried the technique given but might have been doing something wrong as it wasn't working quite the way I wanted. The loop would end up out of sync by the eighth.

While messing about I found track delay, which in combination with the technique produced the desired output. It's limited to milliseconds or frames though so is probably easily broken.

all the best
Dave

[Angstrom]

if you still want to launch the clip with bar quantisation then move the start marker of the clip to a bar before the actual bar start , note I said the bar start not the note start. Then : launch the clip a bar earlier than you think you should - voila an eighth note lead-in then the actual bar.

the clip start marker readout should say something like -1.0.1
from memory

[chapelier fou]

this is the thing that disturbed me the most when i started using live.
it would be amazing to have an option to play the end of the clip when you launch it, despite global quantization. like a "ghost legato mode".

[chapelier fou]

on stage, when possible, i mute the track, launch the clip, and unmute before the end of the bar.

[Angstrom]

why not just use an unlinked volume envelope then?
achieves the same thing without the manual effort,
In the unlinked clip volume env, set the vol env to -inf then allow it up to 0db at your start point, then have it enter a loop state where it remains at 0db

I've used that technique before, and it works fine.

[chapelier fou]

why not just use an unlinked volume envelope then?
achieves the same thing without the manual effort,
In the unlinked clip volume env, set the vol env to -inf then allow it up to 0db at your start point, then have it enter a loop state where it remains at 0db

I've used that technique before, and it works fine.

I mean, using envelopes are not so "live". It's premade things. This is particularly relevant for instance for drums. When you want the snare hit on beat 4 instead on attacking on the first kick (to make it simple).
And i launch and stop the same clip several times in a song, by hand.

Thinking of it just had a idea : link the clip to 2 dry/wet unquantized dummy clips mapped to the same midi control as launch and stop....god i got to try this !

[ze2be]

Thinking of it just had a idea : link the clip to 2 dry/wet unquantized dummy clips mapped to the same midi control as launch and stop....god i got to try this !

I was thinking the same as Angstrom, but can you explaine this a bit better?

[chapelier fou]

Thinking of it just had a idea : link the clip to 2 dry/wet unquantized dummy clips mapped to the same midi control as launch and stop....god i got to try this !

I was thinking the same as Angstrom, but can you explaine this a bit better?

let's imagine, like 4 different rhythm clips in the same track. For my performance, i'd have normally 4 pads to launch them, and the bottom pad to stop. The idea is to have them playing all the time, but instead of launching them or stopping them, route them to an input track with dummy clips in it without quantization. One dummy clip would fake the stop button, by just cutting the sound. The others would just let the sound pass through and would be assigned to the same pad. this way it would open the audio gate before the clips are launched, letting the former's clip's sound pass through.

[chapelier fou]

Yeah and by "dry/wet dummy clips", i meant "mute/unmute".

[Angstrom]

I know what you mean about "live-ness" when you are manually playing around with a clip, but my suggestion is more for a case where your hands are busy elsewhere - eg playing bass. Then you need to hit go, and be sure that the whole thing will just come in on time when you need it to.

[chapelier fou]

No prob i got it. It's just that your suggestion has the effect that the clip will be every time played the same way.
I don't if i was clear about my explanation. Anyway, i'd never thought of that without this topic. So, thank you everyone !

[ze2be]

For a while now, ive been using the method of adding say two bars in the clips before the loop, playing them from there. The scene has to be triggered then exactly 2 bars prior, and it is sometimes a hazzle when occupied with a lead instrument. But one problem is that I also get the notes from the next scene, 2 bars before it should start. Its ok if I follow the scenes down numerically. Because I can just copy the notes from the previous clip to the beginning of the next, prior to the loop. But changing the scenes play order would fuck things up in this setup, because you might not want the melody from a scene to start playing 2 bars before another. Even if there was some cross fade transition, the previous clip will just be cut by the next clip in the same track. Some tracks you might want to start 2 bars prior, while some maybe only a couple of beats. I dont really see how to avoid all the previous clips to be cut at two bars prior. Im trying now instead a project where the scenes trigger a swell/buildup that lasts 16bars, but only audiable the last 4 or 8. This makes it easier to do other stuf at the same time, but it also forces the performance into a certain grid. And there will not be any intro roll for the rest of the clips.

When a new track is triggered by a new scene, id like to have it start with a short roll before the first beat. Its dificult to hit the scene right, so I set global quantize to 1 bar. But this forces all the clips to cut one bar prior.
While other sounds like drones need a few bars.

Optionally there could be some sort of ghost clip that sends midi to the tracks when triggered, adding some sort of roll effect. If so, it should be a clip trigger, because as a scene trigger it would occupy to much space, imo. Start it when its time for a build up, and when its done, hit the next scene. Hm.. chapelier fou: If you are going to cross fade between two clips from the same track, say the main bass, they have to be on different tracks, no?


("and I still havent found what im looking for")