MOTUnation.com

David Polich wrote:James, I keep forgetting you have the same Mac as I do. I haven't gone to Leopard because I honestly don't
think it's worth it for PPC machines. On my G4 Powerbook Leopard makes everything slower.

Might indeed be worth a shot to go back to Tiger - myself I've decided not to go to Leopard until I get
a new Mac (maybe next summer).

FWIW I know a mastering engineer who has Sonic Solutions running on OS9/G4 and has no intention
of updating ever. Her logic - "I don't have another 60 grand to spend on going to something else".

Yeah... may be the way to go. I wonder how involved it is to downgrade stuff?

James, without going back through the whole thread to see if someone has mentioned this, I'm posting the relevant part of the "Get Info" window in the Finder for Kontakt Player 2. See if you are using the same version: 2.2.4.

/Library/Audio/Plug-Ins/Components/KontaktPlayer2.component


If you are using Leopard but not this version, then that would most likely be the problem. I'm trying to remember the sequence of events last December, but they are hazy in memory. I'm thinking it was only the Intel/Leopard users who had to upgrade in January. G5 users may have been able to continue using the previous version with Leopard at that time. I just don't remember. I remember being one of a small group who were disenfranchised by Leopard when it came to Native Instrument plugins, so I'm thinking G5 users may have been unaffected. In any case, my memory doesn't matter. If your version number isn't at least as high as this one, then that might be the problem. Otherwise... well, what can I say? That sucks! Get on the phone and call Native Instruments and tell them the problem. I guarantee the US rep doesn't know about it until you call him.

Shooshie

Hi Shooshie. No, I definitely AM using 2.2.4 of Kontakt Player. As I said... I highly suspect this is a combination PPC + Leopard issue.

groove wrote:The same here. I went back to DP 6.0 and the workaround of using "MAS AudioUnit Support.bundle" version 1.6.1 of DP 5.13.
I've tried DP 6.01 with the two bundles - ie "MAS AudioUnit Support.bundle" version 1.7.0 from DP 6 and 1.6.1 from DP 5.13 but got all crashes and graphical problems with NI stuff as well as Stylus RMX.
UAD 5.0 and the latest Vienna worked well with "MAS AudioUnit Support.bundle" version 1.7.0 wich is a good start.

Hope the next fix - maybe DP 6.02 - will do the trick.

i fix the graphical problems take out MOTU SUPPORT BUNDLE 1.6.1 and 1.7.0
and install 1.5 alpha5 instead.

David Polich wrote:Well all of this news is just sad. Seems like we have trouble on three fronts - with third-party developers who haven't tested their plugs with DP6,
to specific computer/OS combinations (PPC and Leopard, PPC and Tiger, Intel and Leopard), and MOTU themselves, although I really think
they're trying their best to address the myriad concerns.

The plug-ins issues dwarf any other issues at this point, I think. I couldn't care less about the GUI issues. It's the plug-in and VI's situation which is the biggest problem right now.

Totally agree. The incompatibility is bad and dwarfs anything else.

I am also sure that it must be MOTU’s fault. These plug-ins work ok with other DAWS – they work ok with DP 5.13? It seems again like an example of a rushed product. We know MOTU had time problems with version 6 because of the delays.

I also know that there are different platforms / processors to test, but there aren’t that many permutations, just 4 – PPC/Leopard, PPC/Tiger, Intel/Leopard and Intel /Tiger.

I have Komplete 5 and have just tested all on DP6.01 (I am Intel/Leopard) and all is working fine; same as Shooshie.

James Steele wrote:Looks even more like a PPC + Leopard issue. I'm seriously thinking of downgrading to Tiger then... I can't use VI ONE with Kontakt Player2 as a plug right now.

That really is a bummer James. Except I think it’s a PPC+Leopard AND DP6 problem.

Anyone that’s on PPC+Leopard could perhaps try their NI plugs in Garageband? If they work, won’t that seriously point the finger at DP6 with PPC+Leopard?

I also use Live 6 and the NI plugs work fine on both my PPC machine and my Intel MacBook Pro.

JMSchur wrote:I also use Live 6 and the NI plugs work fine on both my PPC machine and my Intel MacBook Pro.

hmmm, well I guess that just about sums it up. Pity the guys on PPC/Leopard, because I imagine downgrading to Tiger would be a lot of work.

tyronehowe wrote:

JMSchur wrote:I also use Live 6 and the NI plugs work fine on both my PPC machine and my Intel MacBook Pro.

hmmm, well I guess that just about sums it up. Pity the guys on PPC/Leopard, because I imagine downgrading to Tiger would be a lot of work.

I'm not about to spend the time to downgrade. I guess I'll just avoid the NI stuff until [if ever] MOTU gets their problems worked out. I took a step in that direction yesterday by taking advantage of the MOTUNATION discount on TruePianos. It's an apt replacement for Akoustic Piano.

James Steele wrote:

Shooshie wrote:I have Akoustik Piano and Kontakt2 Player. Within Kontakt2 Player I have several libraries of Garritan instruments. They all work fine. Akoustik Piano is working fine. I just tested it. I use deep features in Kontakt2 Player, and everything is working. No problems. Zero.

Looks even more like a PPC + Leopard issue. I'm seriously thinking of downgrading to Tiger then... I can't use VI ONE with Kontakt Player2 as a plug right now.

James, I did not go through the rest of this thread yet, but I just saw on NI's site some download about VI one (regarding leopard) I think, check it out. (might be an old one)

For me (look in sig) K2 player and K2 don't work either, but K3 works. That's all I have from NI.

But even with K3, I'm having problems loading Scarbee's Black Bass. (which was created in K2) It crashes DP. In DP 6.0.0 it never went trough, but yesterday it worked in DP6.0.1 but now it's not working again.

JMSchur wrote:I'm not about to spend the time to downgrade. I guess I'll just avoid the NI stuff until [if ever] MOTU gets their problems worked out.

Don’t blame you – that is just how I would feel. It seems ridiculous to have to downgrade the operating system just to allow the latest software to work. Especially since the NI Plugs seem to work in other DAWs on the same system.

This plug-in problem with DP6 is really beginning to worry me. On anther thread I performed a test and found that my Melodyne plug doesn’t work in 6 or 6.01 but works perfectly in 5.13! In fact, to say it doesn’t work in 6 or 6.01 is an understatement, it actually crashes DP.

Sheesh. This is getting beyond a joke. Surely making the Plugs work correctly must be top priority – or do most other people just use DP for audio? I somehow doubt that.

chaim wrote:For me (look in sig) K2 player and K2 don't work either, but K3 works. That's all I have from NI.

But even with K3, I'm having problems loading Scarbee's Black Bass. (which was created in K2) It crashes DP. In DP 6.0.0 it never went trough, but yesterday it worked in DP6.0.1 but now it's not working again.

OK Scarbee Black Bass does not load in K3 stand alone either, so this has nothing to do with DP, but I still wonder why it does not work? All K2 patches should really work in K3, no?

tyronehowe wrote:

JMSchur wrote:I'm not about to spend the time to downgrade. I guess I'll just avoid the NI stuff until [if ever] MOTU gets their problems worked out.

Don’t blame you – that is just how I would feel. It seems ridiculous to have to downgrade the operating system just to allow the latest software to work. Especially since the NI Plugs seem to work in other DAWs on the same system.

This plug-in problem with DP6 is really beginning to worry me. On anther thread I performed a test and found that my Melodyne plug doesn’t work in 6 or 6.01 but works perfectly in 5.13! In fact, to say it doesn’t work in 6 or 6.01 is an understatement, it actually crashes DP.

Sheesh. This is getting beyond a joke. Surely making the Plugs work correctly must be top priority – or do most other people just use DP for audio? I somehow doubt that.

To add to the anguish, I posted a Tech Link on the MOTU support site on July 14, right after I installed DP6 and discovered the problem. I got no response until August 28... and then it was an inane question that could have been answered by reading the original Tech Link.

JMSchur wrote:To add to the anguish, I posted a Tech Link on the MOTU support site on July 14, right after I installed DP6 and discovered the problem. I got no response until August 28... and then it was an inane question that could have been answered by reading the original Tech Link.

Again, that’s really not a good sign. I have just posted a Tech Link myself (about 10 minute ago) regarding the Melodyne problem. I’m hoping that some kind of answer will be with me this week…

tyronehowe wrote:

James Steele wrote:Looks even more like a PPC + Leopard issue. I'm seriously thinking of downgrading to Tiger then... I can't use VI ONE with Kontakt Player2 as a plug right now.

That really is a bummer James. Except I think it’s a PPC+Leopard AND DP6 problem.

Might very well be, but doesn't really matter to me as I want to use DP 6.01, not another DAW.