Bug fix update Live 7.0.12 is available!

[siddhu]

I've noted some really wild tempo fluctuations with Live in Slave mode with this release that did not happen in 7.010.

The slave computer was constantly jumping +/- about 2 BPM's when synching from a master.

Chain was Master > USB Midi Interface > Cable > USB Midi Interface > Slave

Both computers were running 7.012.

7.012 went absolutely crazy when midi synching over ethernet.

Tempos jumping to 800 BPM then dropping to 50. Basically it was as if it was generating/receiving totally random numbers for the BPM.

The transport controls displayed the same behavior.

Switching both machines back to 7.010 stabilised and solved the problems.

Normal USB midi chain works without any fluctuations, and the ethernet midi synch works.

[Crash]

I've noted some really wild tempo fluctuations with Live in Slave mode with this release that did not happen in 7.010.
...
Switching both machines back to 7.010 stabilised and solved the problems.

It may be hard to believe but that happens because .12 solved a bug with Live's Sync Slave behavior. Before .12 Live rounded incoming Sync Clock tempo roughly to full integer values and used that both for external plugins and it's own clip playback (at least with Warp enabled clips). It's good to have that bug removed, because it led to problems when the Master tempo shifted only slightly (ran at some non-integer tempo for a short time) and thus the Master and Slave could run out of Sync after some time.

The problem with .12 is that it's Sync Slave tempo calculation is so unbelieveably lousy that you can hardly use it anymore. Ableton knows about it and hopefully fixes it with the next update ASAP. Unfortunately they didn't care to publish that known flaw in their changelog or non-existant release notes. So you had to fall into that pit and climb out yourself only because there was no sign. Sorry.

The following screenshot demonstrates a comparison between Kore + Kontakt vs. Live + Kontakt running as Slaves from the very same Master Clock at supposely 333 bpm:

[didguitare]

Merci,du coup j'ai parlé de cette info ici :
http://abletonlive.xooit.com/t410-Mise- ... 7-0-10.htm

Amicalement,Didier.

[siddhu]

I've noted some really wild tempo fluctuations with Live in Slave mode with this release that did not happen in 7.010.
...
Switching both machines back to 7.010 stabilised and solved the problems.

It may be hard to believe but that happens because .12 solved a bug with Live's Sync Slave behavior. Before .12 Live rounded incoming Sync Clock tempo roughly to full integer values and used that both for external plugins and it's own clip playback (at least with Warp enabled clips). It's good to have that bug removed, because it led to problems when the Master tempo shifted only slightly (ran at some non-integer tempo for a short time) and thus the Master and Slave could run out of Sync after some time.

The problem with .12 is that it's Sync Slave tempo calculation is so unbelieveably lousy that you can hardly use it anymore. Ableton knows about it and hopefully fixes it with the next update ASAP. Unfortunately they didn't care to publish that known flaw in their changelog or non-existant release notes. So you had to fall into that pit and climb out yourself only because there was no sign. Sorry.

The following screenshot demonstrates a comparison between Kore + Kontakt vs. Live + Kontakt running as Slaves from the very same Master Clock at supposely 333 bpm:

Well this really needs to be sorted out because how can you play a gig as an "electronic band" using multiple computers if the tempo sync keeps fluctuating wildly!?

I mean Live is supposed to be a "live performance instrument" and should have industry leading tightness when it comes to sync.

[ddr400]

I've noted some really wild tempo fluctuations with Live in Slave mode with this release that did not happen in 7.010.

The slave computer was constantly jumping +/- about 2 BPM's when synching from a master.

Chain was Master > USB Midi Interface > Cable > USB Midi Interface > Slave

Both computers were running 7.012.

7.012 went absolutely crazy when midi synching over ethernet.

Tempos jumping to 800 BPM then dropping to 50. Basically it was as if it was generating/receiving totally random numbers for the BPM.

The transport controls displayed the same behavior.

Switching both machines back to 7.010 stabilised and solved the problems.

Normal USB midi chain works without any fluctuations, and the ethernet midi synch works.

yes.
i got total desync with my machinedrum. Live as master.
back to 7.0.10

[glockinpalm]

>>Under certain conditions an empty MIDI effect Rack could lead to audio drop-outs.

this sounds like it could be what was causing my proble i described here:

http://forum.ableton.com/viewtopic.php?t=102723

sweet...

[beatnick]

Bargh! The sync issue has totally rendered my live set unplayable!!!

I need to backtrack to 7.0.10 but ableton don't have previous version for download.

Any help???

Nick.

[IamInsane]

Bargh! The sync issue has totally rendered my live set unplayable!!!

I need to backtrack to 7.0.10 but ableton don't have previous version for download.

Any help???

Nick.

I'm not going to look it up myself right now, but getting older versions is pretty easy. Go to the URL for the new version, you'll see the version number embedded in the URL. Change the URL to the version you want. It's worked for me the few times I've needed it