All Live/Vista performance problems identified!
Posted: Sat Jun 14, 2008 6:22 pm
Hey folks!
I thought that I should let you know that after two more days of diving into my Vista/Live/RME related problems I am now able to identify and reproduce about all of them.
Additionally I think to have found the source/reason for the bad performance of RME Fireface drivers on Vista and I am able to reproduce their performance hit in Reaper now. So this is not a sole problem of Live, but it's alot worse in Live than in Reaper.
(Furthermore I found some very interesting performance problems with Live 6/7's multiprocessing methods on both Vista and XP that should be discussed in detail. Likely this ain't no Live specific problem though, but a problem of multiprocessing overhead in general.)
And No, turning off multiprocessing does not solve any of these issues, it just alleviates the symptoms.
Some of these were reported as early as January by me (AERO anyone?) and Ableton was not able to solve or even successfuly reproducing them.
Meanwhile I have been told not to spend time on analysing things on my own, not to write thorough reports to support "No 300+ words mail!") and not to draw my own conclusions. But in the end I prefer drawing my own limited and amateurish conclusions to getting no conclusions at all.
If you are only interested in the solutions then skip the entire "Analysis" and "Proof" sections!
I thought that I should let you know that after two more days of diving into my Vista/Live/RME related problems I am now able to identify and reproduce about all of them.
Additionally I think to have found the source/reason for the bad performance of RME Fireface drivers on Vista and I am able to reproduce their performance hit in Reaper now. So this is not a sole problem of Live, but it's alot worse in Live than in Reaper.
(Furthermore I found some very interesting performance problems with Live 6/7's multiprocessing methods on both Vista and XP that should be discussed in detail. Likely this ain't no Live specific problem though, but a problem of multiprocessing overhead in general.)
And No, turning off multiprocessing does not solve any of these issues, it just alleviates the symptoms.
Some of these were reported as early as January by me (AERO anyone?) and Ableton was not able to solve or even successfuly reproducing them.
Meanwhile I have been told not to spend time on analysing things on my own, not to write thorough reports to support "No 300+ words mail!") and not to draw my own conclusions. But in the end I prefer drawing my own limited and amateurish conclusions to getting no conclusions at all.
If you are only interested in the solutions then skip the entire "Analysis" and "Proof" sections!