Posted: Sat Feb 02, 2008 11:09 am
MacBook Pro 2.16Ghz, 2Gb ram, OS 10.4.11, Live 7
Just upgraded to Live 7 hoping to leave the "dragging cpu" problem behind (as well as the bug with tracks that use the EQ Three suddenly breaking into level meter-buried/amplifier overloading/sound technician cursing noise).
Alas, the "dragging CPU" is still happening, and it started up with the first (although granted, big) project I loaded into Live 7. This project, although buggy from the EQ Three problem, has been performance tested in Live 6, and I thought the problem was under control. Guess not.
Re: Ableton's response:
I am reporting the problem now, but it takes valuable time to send reports/logs. It is not the user's responsibility to keep Ableton up to date on the status of a major, long-term problem like this. Not that I don't wish for the best relationship possible between producer/consumer, but Ableton Live is not cheap. Ableton should consider the time of their users as valuable as theirs. Otherwise, Ableton will lose customers.
Just upgraded to Live 7 hoping to leave the "dragging cpu" problem behind (as well as the bug with tracks that use the EQ Three suddenly breaking into level meter-buried/amplifier overloading/sound technician cursing noise).
Alas, the "dragging CPU" is still happening, and it started up with the first (although granted, big) project I loaded into Live 7. This project, although buggy from the EQ Three problem, has been performance tested in Live 6, and I thought the problem was under control. Guess not.
Re: Ableton's response:
I am reporting the problem now, but it takes valuable time to send reports/logs. It is not the user's responsibility to keep Ableton up to date on the status of a major, long-term problem like this. Not that I don't wish for the best relationship possible between producer/consumer, but Ableton Live is not cheap. Ableton should consider the time of their users as valuable as theirs. Otherwise, Ableton will lose customers.