Bug fix update Live 7.0.12 is available!
-
- Posts: 308
- Joined: Tue Feb 12, 2008 1:13 am
- Location: Brooklyn
bugs in 0.12
you copy a section, if you do certain actions before pasting, like pressing stop to go back to zero , or click on a marker to go at a specific position, there's no pasting, it's gone from the RAM.
and the ever popular Midi Overdub doesn't work
you copy a section, if you do certain actions before pasting, like pressing stop to go back to zero , or click on a marker to go at a specific position, there's no pasting, it's gone from the RAM.
and the ever popular Midi Overdub doesn't work
Quad 6600 Intel, AsusP5Q, 2Gb ram, XP sp3, Evolution MK361c & UC33e, Line6 UX8
Anyone else getting these issues?Chris J wrote:bugs in 0.12
you copy a section, if you do certain actions before pasting, like pressing stop to go back to zero , or click on a marker to go at a specific position, there's no pasting, it's gone from the RAM.
and the ever popular Midi Overdub doesn't work
MBP 2.4GHz, 4Gb RAM, OSX 10.5.5, Live7Suite, Motu Ultralite Mk3, ADAM p11A
Hi Misteron and Siddhu
We had this issue in the Bugs & Problems forum too. This is what my colleague Jörg said:
best,
dfi
We had this issue in the Bugs & Problems forum too. This is what my colleague Jörg said:
If that is not what you experience, please let me know!there´s nothing wrong with with Copy&Paste, it just functions as specified:
Before your can paste anything, the insert mark needs to be in focus.
If you click the Global Stop Button, the focus is on the transport, you can´t paste anything to the transport.
If you click a marker, you can see that the focus is not on the track anymore but on the marker.
Simply click into track display to place the insert mark, you´ll be able to paste anywhere. Nothing is lost in the RAM.
Best regards,
Jörg
best,
dfi
That is not what I experience.[dfi] wrote:If that is not what you experience, please let me know!
While Live is busy with Copy or Paste operation of memory intensive tracks the keyboard controls don't work anymore until some time after the operation is completed. That means you cannot use cursor-keys, del, space and neither ctrl-v (Paste on Windows).
The mouse on the other hand is still perfectly useable, including chosing Paste operations while the keys are still disabled (that is why I wrote "some time after").
I reported problems with that as early as last January but obviously no one at Ableton took a closer look at it since then.
HAL: I know I've made some very poor decisions recently, but I can give you my complete assurance that my work will be back to normal. I've still got the greatest enthusiasm and confidence in the mission. And I want to help you.
Major Sync Problems in 7.012
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.
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.
Re: Major Sync Problems in 7.012
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.siddhu wrote: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.
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:
HAL: I know I've made some very poor decisions recently, but I can give you my complete assurance that my work will be back to normal. I've still got the greatest enthusiasm and confidence in the mission. And I want to help you.
-
- Posts: 71
- Joined: Sun Jun 08, 2008 1:57 pm
- Location: france
- Contact:
Merci,du coup j'ai parlé de cette info ici :
http://abletonlive.xooit.com/t410-Mise- ... 7-0-10.htm
Amicalement,Didier.
http://abletonlive.xooit.com/t410-Mise- ... 7-0-10.htm
Amicalement,Didier.
Re: Major Sync Problems in 7.012
Crash wrote: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.siddhu wrote: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.
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.
Re: Major Sync Problems in 7.012
yes.siddhu wrote: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.
i got total desync with my machinedrum. Live as master.
back to 7.0.10
-
- Posts: 6
- Joined: Thu Jan 04, 2007 3:12 pm
>>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...
this sounds like it could be what was causing my proble i described here:
http://forum.ableton.com/viewtopic.php?t=102723
sweet...