garyb wrote:yes, the logic 5.0 pc thing. exaclty the same when apple took over emagic, but worse.
Which was worse?

"Hey upgrade to our newest version if u want those fixes we promised for your current version" or "Hey upgrade your entire machine & software library if you want future updates!"
Both are pathetic eh?
Steinberg lost me during Nuendo 1.x. Nuendo was NOT intially a steinberg product, and I was 'moved' over to Steinberg when they lapped up the codebase. Things were fine up through 1.4 although there were no virtual instruments. The company that had produced the original codebase had incredibly optimized multithreading (I could get 120-150% out of my dual xeons). By 1.5 Steinberg owned the codebase and attempted to integrate the VSTi spec, and system stability went out the window. After extensive testing on the older Cubase & Nuendo forums (much of which was deleted for v2 launch) it was obvious that instead of integrating VSTi processing into the current codebase it was just added on as a separate thread, which meant that when SMP (dual cpu) mode was enabled VSTi's would load down only one of the two cpu's and inevitably cause instability when workloads became high (when nearing the end of a track etc). The promised over & over to 'fix' this, and instead focused on porting a few additional MIDI functions over from Cubase VST and released Cubase SX. Further investigation on the forums revealed that Cubase SX also the same stability issues.
Mind you I was running the 'recommended' RME + Dual Xeon system that the pre-steinberg company had optimized the code extensively for. In the RME MUltiface was later even sold directly by STeinberg as the 'Nuendo' audio interface, and the steinberg website listed the top recommended PC specs as being a dual xeon with an RME multiface, exactly my machine. And yet to work reliably with Virtual Instruments (VSTi) I had to disable SMP support and run. with essentially only 1 cpu. Steinberg's response was that 'SMP Mode' was only for use during 'advanced tracking and mixdown' and stopped claiming a fix was forthcoming.
It's my understanding that in the v3 codebase 'improvements were made' by allowing VSTi's to still run in a separate thread but that thread now load balances, and finally in version 4 of 'coobase' they've done the audio engine rewrite which was promised to Nuendo 1.5x users back in 2000. Needless to say while I still own Nuendo 1.6 (current version for 1.x) I am not really feeling the loss of all the upgrades I never did to get what was promised to me years ago.
And then back to my reason for replying to GaryB. The reason I never upgraded to v2 (which wouldn't have fixed my issues with SMP mode in Nuendo anyway) is because I started using Logic 4.8 and then 5.x on PC, since win2k/Xp support was coming along so well. Even more interesting was that (given teh SMP issues under cubase) the differences between Logic's 'only when needed' and Nuendo (Cubase)'s "all the time" processing meant that I could achieve much higher plugin counts in Logic (which only used 1 cpu on PC under normal conditions). The ultimate Irony was that I moved from Nuendo to Logic due to Steinberg's crappy treatment of existing Nuendo customers, only to have Emagic sell to Apple.
At least Emagic was kind enough to give us a maintenance release (5.51) before moving on.
Most of the progress I've had over the last few years, rather than being my main DAW, have been in integrating Scope and interesting tools like Bidule & Usine into my studio workflow. And to be quite honest, since I don't have to resort to virtual audio cables and/or rewire to record virtual instruments I'm quite happy to run Logic for at least the next year or two.