Ableton Forum

No worries, glad I could help.

The quantization settings can be a powerful ally once they are understood.

Usually you want to set thet Master Quantizaton Menu to 1/4 or Bar, and then mess with some of your loops individual quantization settings to make Live feel a little more organic. . .

for instance you might have a guitar or sound effect clip (that is not looped) set at "none" so that it sounds like they are coming in a little ahead of the beat, anticipating the next section etc . .


by the way, don't think I didn't learn this the hard way.

be well,
gb

Hmm. I seem to be having some problems with clips in 2.02 also.

Here's the behavior:

1.5.2: Drag a 170bpm clip to a cell, start, it correctly comes up as a 170.03BPM clip, loops and plays flawlessly @ 165BPM. it's a 1 bar clip.

2.0.1 Drag a 170BPM clip to a cell, clip comes up as a -1BPM clip (the same clip as before). Loops on it's own time.

2.0.2. Drag a 170BPM clip to a cell, and the original BPM is figured at 165 BPM (The project tempo). Now, either one or two things happen:

1. The clip plays for a bar, then fuzz is played for a bar. This happens when the clip is correctly marked as a 1 bar clip, but the tempo is wrong.

or

2. It plays on it's own time, not with the project tempo. This happens when the tempo is wrong and the bar length is wrong.

geargasm wrote: Drag a 170BPM clip to a cell, and the original BPM is figured at 165 BPM (The project tempo). Now, either one or two things happen:

1. The clip plays for a bar, then fuzz is played for a bar. This happens when the clip is correctly marked as a 1 bar clip, but the tempo is wrong.

or

2. It plays on it's own time, not with the project tempo. This happens when the tempo is wrong and the bar length is wrong.

I cannot seem to reproduce this. I drag a sample containing a one bar loop at 170 BPM into a Live Set at 160 BPM and everything works as expected. Please make sure you have set Preferences/Misc/Clip/Loop/Warp to "Auto". If the problem persists, please write down step by step what you are doing to get the error. We will work it from there.

Gerhard / ableton

Try This:

Trigger a scene and simply let it play. Dont do anything and eventually clips start to lose sync.

Is this not a bug??

Not a huge problem really, but it does hapen in both my machines everytime.

PS
You have to give it a good few minutes before it loses sync.

Thanks guvnorbeats.
I had the same problem... couldnt figure it out.
and yep it was that one of my samples didnt have its quantization turned on.

beautiful, glad I could help.

I have worked extensively with Live and cannot get loops to go out of synch in any way. (unless it is my own mistake). Not saying it is impossible, but I have never seen it, uh I mean heard it.

One other possible solution the Guest above's problem . . .
Occasionally, Live's loop region will shift (this is a known bug, though it is minor), when slecting warp makers, and create a loop that is less than even (for example 3.3.3 beats long as opposed to 4 beats)

i have this scene launch problem also-- but mine is for real as far as i can tell.

i've checked and re-checked the clip quan vs. global quan (glad that's solved everybody elses' probs ), but when i click a scene launch button a few clips per scene will launch a bar after the others have started. this happens without fail when launching from the 1.1.1 arrangement position and intermittently once it's running. and, as far as i can tell, it's the same clips every time that fail to launch.

i've checked the transient settings as suggested earlier but can't find a pattern there.

the only correlation i can draw from the clips that launch late is that they all have some degree of warping. while unwarped loops seem to consistently launch on time. is that what causes the delay? is there some type of 'load-up' for warped clips in live 2?

i'm certain i didn't have this problem with live 1.x, anyone else?

here's my set up if it helps:
g4 733 tower
os x 10.2
live 2.02

thanks for any insight,
brian

I have a silly question, is your master loop setting on?

On the transport bar at the top . . . is the PROJECT / SONG loop set to a shorter length than the clips that are falling out of sync?

for instance, if you have the loop set to 4 bars, and you are launching two 8 measure loop, with several warp markers, Live may be reseting the loops in a funny place.

Otherwise, I'm baffled.

what are the lengths of each of the loops you are trying to sync?
and when you say you've checked the quantization, is each and every loop set to global? and your global is set to bar?
just making sure

upon further investigation of my own problem

in addition to warped clips, it seems that clips that have their region set to some place other than the very beginning of the clip are the ones launching late.
also, the clip in the farthest left track (even if it's not track 1) will always launch on time-- even if it shares the characteristics of 'late launchers' (as i'm know calling them )

strange, Are you sure your loop "offset" is set to the place you want it?

loop offset is the little triangle just beneath the loop region. (sure you know this, but trying to alleviate confusion).

Try setting the loop offset on a normal beat like 1.1 or 1.2 . . .

is the loop off all of the time? or does it gradually get worse?

Gerhard wrote:Gentlemen,


There is another issue which I guess is what you are talking about. This is about clips that have odd loop lengths, like 7.3.3 plus something instead of 8.0.0. When such a clip is running in the Session View, the Track Status Field will show a '7+' loop length next to the pie chart.

It is easy to create such clips. When a clip is set to play unwarped, you can adjust the clip region (aka loop) in milliseconds rather than sixteenth notes; when warping is re-activated, the region / loop length is likely not be a "round" musical loop. We have also seen clips with an *almost* round loop in Live Sets that were created with an old Live version.

Anyhow, in case of a such a clip with an unround loop, the fix is easy: dragging the loop start and end marker makes them snap to sixteenth notes.

I would like to know from you: can you confirm that your drifting clips have an unround loop length? After dragging the loop markers to snap them to sixteenths, is the problem fixed?

Thank you

Gerhard / ableton

i think i'm having this problem with certain oneshots but I can't drag the loop markers to 8 because no such part of the file exists. in 1.5 it would not do this.

hey guvnor, yeah man, the offsets are all in 'normal' places-- all on a beat, nothing too kooky. there's no 'drift' of any sort. these problem clips just do not trigger with the others when you launch a scene.

i've been taking a hard look at one set that has this problem and trying to recreate it in a new one. i might have something figured out. if someone else could give this a shot that would be awesome.

> place three clips in three tracks.
> take the clip in track 2 and pull the warp / beat marker "1" right until negative beat markers appear at the left (why you would need to do this in real life who knows, but i think this is what i had) but leave the start of the loop on marker "1"
> take clip 3 and place the loop region somewhere in the middle of the clip.
> now launch the scene from a dead stop (1.1.1), clip 1, the untouched clip, should start fine but do clips 2 and 3 flash then launch a bar later?

even if you pull back the warp marker on clip 2 to get rid of the negative beat markers the late launch 'problem' persists. i think this is what may have got me on these sets... for some nutty reason i had some clips with negatives and they, in turn, threw off the offset clips.

hit be back if you've got time to waste on this experiment.

you are absolutely right.
this is a bug.

you should report it.

It only happens from a dead stop, but it definitely occurs.

good job! Ableton will fix it if you send it in to [email protected]

The Ableton's do not have email. All the emails that are sent to [email protected] are sucked into a black hole and piped to /dev/null.

well, got the same live 2.02 behaviour here, on mac 10.2.4 tiBook 867mhz and desktop 400mhz. (i mean clips not starting simultaneously; difficulties in communication with ableton I only had on my tiBook, but I still like them if they at leats are working on the problems, if not answering about it. )
on comparing this bug on my tiBook and my old G4 i discovered that the delay with wich the late sample is playing (which i discovered a long time ago, unfortunately) is exactly the global quantisation-
so if that is BAR, the clip will start a bar too late; if it's NONE, it'll be in time (but that's not exactly how i want it to work..).

the way i worked around this until now is to (as said before) put all samples into global quant (1/4), and before triggering any sample, press space (or start "sequencing" in another way. by the way, I just discovered another oddity, although not bad: for the "stop clips" button, i chose the key "q" in keymapping. when i press q now, all playing clips are stopped, as desired. if at that moment sequencing is on / live plays / whatever, it will continue to do so. if it wasn't, it will START!! - that's strange (in my perception), as just pressing the "stop all clips" button won't do this... but that's a bit misplaced here, sorry..).
nevermind, this way the clips won't wait for the next global quantisation picking them up, which could help until (hopefully) 2.0.3 will fix this; preferably yesterday (without wanting to rush)


greetings,

jan[/b]