I\'ve been reading the threads concerning the problems with OSX, and it seems to me the vast majority of us are having problems using GPO with Digidesign hardware... or is it the Digidesign software?
Can\'t tell yet.
Logic users, except for one notable exception, seem to be doing fine. Same with Digital Performer users (except for one guy). Same with Cubase users.
Wonder what hardware the Logic and Cubase guys are using?
Like Ed, who posted in another thread, I can only get four sounds into GPO tops. But unlike Ed, I don\'t care. All I asked from GPO when I bought it was one track of sound expanded into 32-bit samples. I\'m an audio guy, so once I get that one track of midi, I bounce it to an audio track. If I need more, I just call up another midi track, get what I want, and bounce it to audio again.
I\'m a satisfied customer.
That said, someone in another thread wrote, \"So are the Mac guys beta testers?\" Ahhhhh... yeah, kind of. Frankly, that\'s one of the fun things about being a Mac user. You\'ve got to pretty much be a computer geek to survive. So yeah, at this point I\'m an unofficial beta tester.
For example: GPO Studio simply does not work on my machine using Digi hardware. It does work using the built-in hardware, but that means it\'s coming out of the little speakers on my G4, since all my audio is routed through my Digidesign hardware. Not good. Although GPO Studio recognizes my Digidesign driver, as soon as I switch to it GPO Studio crashes.
But... when I run the standalone Kontact Player, it recognizes the driver and doesn\'t crash when I switch to it.
I have to conclude the problem is with the Plogue software. Plogue, a Canadian company (don\'t get me started about Canadians) hasn\'t made anything but betas so far. How the hell did they get into the game? I\'m all for giving the kids a chance, but not in the championships. Was Plogue subcontracted by NI?
Can\'t tell yet.
In fairness, I don\'t hear anything about GPO Studio crashing with OSX people who use non-Digidesign hardware, so it might just be a conflict between Plogue and Digidesign, which means the companies are mutually culpable.
Let\'s review. Native Instruments might be responsible for the poor performance of Kontact in Pro Tools (and it\'s a given if you use Pro Tools, you\'re using Digidesign hardware, so that means it\'s impossible to tell whether it\'s the hardware or the software in conflict with Kontact). But isn\'t Plogue responsible for my GPO Studio crashes?
This I can tell for sure. It\'s a Plogue problem.
I also agree with whoever said that Apple is part of the problem -- they need to rally Apple developers to get their code-crunching acts together. If Logic users are having problems with anything whatsoever, that\'s clearly an Apple problem. By default.
It seems Mac users have a harder go with GPO than PC users, and Digidesign users have the most problems overall. At least, based on what I\'ve read at this forum.
So why did I mention Unity by Bitheadz? Because Unity could have been the Gigasampler of the Mac world, but they dropped the ball. IT\'S ALL THEIR FAULT, DAMMIT! (Just kidding. Well, just kidding about the yelling anyway.) Bitheadz could have made Gary\'s life easier, but despite having a great Mac-oriented sampler, they just didn\'t jump on the translation bandwagon the way Native Instruments did. You\'ve got to give credit to NI for its vision.
So what can we do, Mac OSX users? First, we can be beta testers, and find every little glitch on every individual platform, so we know what we\'re up against. Second, we can be activists and write to these software developers directly.
I plan on writing Digidesign and Native Instuments. I definitely want to let Digidesign know that GPO works on all the other platforms much better than Digidesign\'s. And Native Instruments offesr a link to its Forums on Kontact Player standalone, but as of this writing there is no Kontact Player/Garritan Forum. No, instead Gary gets the flak. NI needs to face the music, as it were.
As to Plogue, I already wrote to them regarding my GPO Stuido crash when switching to the Digidesign audio driver. Here\'s the definitely-not-out-of-context reply I got from one of their employees:
\"We have made some changes to our CoreAudio code in the yet unreleased GPO Studio update, but we can\'t make any warranties that this will fix the problem.\"
Could this mean my GPO Studio problems are solved?
Can\'t tell yet.