This worked fine in Tiger. I've been ping-ponged back and forth between Apple saying it's a DigiDesign issue, and DigiDesign saying it's an Apple issue..... I don't ****ing care who's issue it is, both of them are supposed to be working together to resolve such things!
Yeah it's pathetic. I've been working with audio on the Windows platform since 1992 and I've lost count of the people who have insisted over the years that Mac is the *only* choice for audio and music production, and I'm crazy for using that creepy other platform that's only for spreadsheets.
Well, admittedly Windows was a crap platform for audio up until Win2K, but starting with 2K and all the way through XP and Vista it's been a solid DAW platform and the only downtime I've experienced waiting for OS-related issues to be resolved was during the XP->Vista transition when things got a little dodgy, but after a couple of months it was workable again and I've been using Vista since.
Meanwhile, during that same time (year 2000 to present day) the Mac audio ppl have had a lot of problems. First there was the transition from OS9 to OS X, Cheetah and Puma were jokes and it wasn't until Jaguar in 2002 that stuff like Cubase, Reason etc would run properly on OS X... and just when things were starting to settle, Apple went ahead and introduced Audio Units, causing even more delays. Subsequently it seems there's always something that breaks with every update. If it's not your MIDI controller driver it's your audio device driver, or your DAW software, or its third party plugins...
When I got a Mac a while ago I borrowed Logic 8 from work to check it out. Installed it and loaded up some included demo songs to get a feel for it (hadn't tried Logic since the days it was an Emagic product). After 4 crashes in less than 15 minutes I just shrugged and uninstalled it, hoping Cubase would fare better. Yeah, it kinda did, so the next step was to install drivers for my Yamaha 01X firewire device. Uh... not, because there were no working Tiger drivers yet (this was in the fall of 2007!). Gave up on that too. Then Leopard came along in October and I installed it (breaking Cubase of course, had to wait till Feb 2008 for a Leopard-compatible update). Meanwhile I tried to get Yamaha drivers again. Yep, now there were Tiger drivers were finally available... but incompatible with Leopard. Next update scheduled for Jan 2008. When I finally had everything (Mac running Leopard, Leopard-compatible Cubase, Leopard compatible 01X drivers) after 6 months of waiting, I sat down with baited breath and installed everything, rebooted and.... hmm, is the screen supposed to be blue for that long? Waited 1 minute... 2 minutes... 5 minutes... 10 minutes... still a blank blue screen on startup. Really loving this "one and only platform for audio".
Went back to Windows and business as usual. I use the Mac for graphics only now.
I agree with you that getting ProTools to work properly is a joint responsibility for Apple and Digi. And they should solve it
before OS updates, not let the update break stuff first in order to assess the scope of the damage because by the time Digi has a fix ready, Apple has already released the new 10 point blah point bleh which breaks other stuff.
What?!?!?
I thought I hit the band wagon late with 10.2
I wouldn't call it junk, I know it's an opinion and all but that is just a gross over statement.
10.0 was little more than a public beta. 10.1 was better but there was still so much 3rd party software yet to be ported to X, it was a mere curiosity. By 10.2 both the OS and the software was in good shape. IMO, 10.2 is where it stopped being junk, though some might argue it happened with 10.3. But to call everything prior to 10.4 junk is a bit harsh, yes.
