anybody using Live with midi timecode succesfully?

[Rave]

8.1 is definitely the most bloated version, it doesn't crash but I can't run as many tracks as I used to be able to, nor can I use 192kHz as often as I used to.

I have downloaded 8.1 but not installed it. Sod that I am sticking with 8.09 for a while

[Tone Deft]

8.1 is definitely the most bloated version, it doesn't crash but I can't run as many tracks as I used to be able to, nor can I use 192kHz as often as I used to.

I have downloaded 8.1 but not installed it. Sod that I am sticking with 8.09 for a while

the only reason I went for 8.1 was for m4L support. I NEVER upgrade a working system and I kept all the working Live 7 versions until I found a Live 8 version. then I kept the latest Live 7 and started collecting Live 8 versions.

I went pale when I accidentally saved my huge set in 8.1 before backing it up as a 8.0 version. then I had that corrupt .als issue, that sucked but was resolved quickly. I've felt the pain but it wasn't for long.

I hope the 'quality bugfix' works out and I can get more life out of my aging laptop.

[senator adam]

It runs fine when I use a small set. However, my live setup has hundreds of clips and FX. When I sync my machinedrum and mpc to it, it is in sync for about 15-20 minutes, but then slowly drifts off into a trainwreck. I have to stop the set completely and then restart.

I tried rocking it like that for a while and it was fine (fade to grey and then stop, start back up and drift back in), but now I just record the machines as audio and edit them up for clips. It's more for me really than the setup: I feel less stressed about things getting sloppy this way so I perform better because I'm more confident.

I use a Dell Inspiron E1505 core 2 duo with a Motu Ultralite, if that matters.

[3phase]

3phase - do the other clock modes work for you?

again.. i am not talking about clockmodes.. i am talking about timecode.. thats 2 totally diferent concepts.. a timecode dont contains any tempo onformation.. it just gives a time..

you need that to sync to other daw´s ..in case you want to avoid sloppy sync...
or to video devices...

its not an unhandy feature to have especially in the actual situation wher you want to switch over to other daws but still want live to be running..
dj sync is the only solution... rewirde is crashing..timecode s not working..old libarys cant be accessed.. and probably even more fun stuff we dont know even yet because the whle mde of working is so slowed down that you rather spend the night before the tv soldering stuff than spendig more time in fruitless betatesting.. i never did so much betatesting for 129 euros.. i guess im down to 0,01 cent the hour by now... actually when the tendency holds on we cant tell it paid betatesting anymore

[Tone Deft]

in the midi preferences you can select several clock types, midi time code is just one of them. do you know the menu I'm talking about?

[3phase]

no.. i certainly dont know what you are talking about.

[3phase]

and uo again.. people from usa out of the coffins... what do you think? anybody on the other side of the sea that has succesfully worked with midi timecode and live?

[bigbadotis]

Tone Deft, if you have time (who does?) and are curious you can try this test.

1. Create an Ableton arrangement where the tempo is at 60 bpm for the first measure and 120 bpm every measure after
2. Set your MPC to be MIDI Timecode Master and Live to be a slave.
3. Tell your MPC to advance to 8 seconds.

At this point Live should be at the start of measure 4 (one measure at 60 and two at 120 bpm). If the bug I'm talking about is also on Windows Live will instead be at the start of measure 3, having effectively ignored the tempo change.

[3phase]

Tone Deft, if you have time (who does?) and are curious you can try this test.

1. Create an Ableton arrangement where the tempo is at 60 bpm for the first measure and 120 bpm every measure after
2. Set your MPC to be MIDI Timecode Master and Live to be a slave.
3. Tell your MPC to advance to 8 seconds.

At this point Live should be at the start of measure 4 (one measure at 60 and two at 120 bpm). If the bug I'm talking about is also on Windows Live will instead be at the start of measure 3, having effectively ignored the tempo change.

it seems that mr tonedeft dont knows what a timecode is and mixes it up with the midi clock...

Do i understand you wright that without the tempo change its working correctly and when you go for example to minute 1 on 120 bpm live will start properly at bar 31 ..in sync?

beside that i would think the behaviour you describe is correct or at least similar what can happen in other daw´s..because live as the timecode slave probably misses the event of the speed change at bar 2 and is still in 60 bpm..where bar 3 would be the correct result..

what happens when you stop and start again for example at bar 10 and start again..is it getting the new tempo and correct position than?

[bigbadotis]

You know, I just assumed that other DAWs handled tempo changes correctly; I've never tried it with other DAWs because they support video (as Live now does of course). Without tempo changes Live does start in sync.

Stopping and starting is fine, it's just jumps that move across tempo changes that screw Live up. But maybe this is a common (and accepted) problem in DAWs...

[3phase]

as a timecode slave the daw should or could be aware of what will happen because it can precalculate all the tempo changes for the entire song length.. But only if the developers see a reason to do so..

The good old atari program Notator form c-lab was allready able to do what you ask for.. but you had to render a sync refference with all the tempochanges first.. a modern DAW should be able to do this automatical in the background..
But as we all know..Ableton Live is "different"

With live such an algorythm probably wasnt applied... So you cant call it a bug..just some missing knowledge regarding timecode syncing.. MAybe just forgotten to develop for the case of tempochanges..

Was Live 1 able to do tempochanges? cant remember.. but i think tempochanges was a "new" feature at one point...
MAybe the missing feature is related to an initial one tempo concept?
I guess you should put in on the wishlist or claim this to be a conceptional bug and put it on the buglist..


However


On my machine timecode is not working at all.. and reffering to the bugforum Ableton dont considers this as a bug..
So good luck with your problem


MAy i ask on what system you are running? Mac/ Pc, which OS?

[HouseContainer]

So question... Is anybode working with ableton live as timecode slave succesfully? and on which platform are you working than?

Well I just blogged about my Perfect MIDI Sync with Ableton Live using MTC.

[3phase]

so you are on pc?

what do mean with that?
The result was a perfectly stable sync with noticeable packet drops from the wireless network. But the best is that after each packet drop, Ableton got perfectly back into sync.

perfect sync that jumps here and there???

[HouseContainer]

so you are on pc?

what do mean with that?
The result was a perfectly stable sync with noticeable packet drops from the wireless network. But the best is that after each packet drop, Ableton got perfectly back into sync.

perfect sync that jumps here and there???

The jump was caused by the Wireless Network. If I would use a wired connection the signal would be stable. But I wanted it to jump, to see if it would correct itself automatically and it did.

[3phase]

so midi timcode ist not working on mac than.. but its not seen as a bug :-/