Kontakt Standalone and Oxygen 8 problem

Hello all,

I have the latest Kontakt running under OS X 10.4.5 and have an Oxygen 8 keyboard. I am going to the computer with both the midi out via a M-Audio FW410 and the USB port out. Both midi forms work fine with other apps and i have no problem controlling Kontakt from within Cubase. But in the standalone I can't get the keyboard to work. Anyone know what's wrong?

In audio/midi setup I have both ins and outs turned on (they default to off) but no go. I am not seeing that it's getting any midi signal. Other than that, the app works fine. Thanks!

 

Same thing here misterpatrick.

I started a thread here: http://www.nativeinstruments.de/forum_us/showthread.php?t=33979

Perhaps this is a 10.4.5 thing?

 

So I guess we're the only ones with this issue?

 

Hmmmmm. There's only two possibilities here.

One is that it might be a channelization issue. Maybe the Oxygen8 is transmitting MIDI on a specific channel, and the Kontakt instrument you're trying to play is only receiving on another specific channel. To check this, change the Kontakt instrument to OMNI. That'll tell us right away whether MIDI is being received at all by Kontakt.

The second possibility is that there really is an incompatibility between the Oxygen8 and Kontakt. I would recommend calling tech support for both companies. The problem could lie on either end.

You can try rolling back to earlier versions of the drivers but there's no guarantee that'll help. I really doubt it's 10.4.5 causing it.

 

I am on a PC and in standalone mode, K2 sometimes depending on apparently its mood see my Korg T2 at all times, but the Emu Xboard 49 some of the times....
fortunately I dont' really use standalone mode......but I have never been able to figure it out.

Neither Reason 3, Nuendo 3.2 or any of my other standalone synths, has this problem.
thanks.
rsp

 

Zvenx, more details? Your Korg T2 is certainly connected to the computer via a traditional MIDI interface (USB?) but is the Emu Xboard 49 a direct USB connection or going through the same interface or what?

The Audio/MIDI setup dialog box is common to all NI applications. I've noticed that the MIDI side of it usually works absolutely perfectly with regular USB MIDI interfaces (I use MOTU stuff, for example), but the dialog box has hit-and-miss results with direct USB devices. In the past, I've worked with both Edirol and M-Audio USB keyboards. After installing the Edirol/M-Audio drivers and restarting the computer, I have to power up the USB keyboard before I launch K2. When I go into the Audio/MIDI setup, I usually see the USB keyboard but sometimes its name is totally messed up. But usually after quitting and relaunching or futzing with it a little, I can get it to work. I've never had a situation in which it refused to work. But if the Emu unit you're talking about is in this category, maybe it's subject to the same flakiness as I've seen with Edirol/M-Audio...?

Try reinstalling the Emu drivers, rebooting the computer, power-cycling the Emu, THEN launching K2, and see if that works.

If not, call NI tech support.

 

Greetings,

K2 consistently refuses to work with my O8 until I do this:

Start up K2, set the midi inputs to ON (of course with O8 on and connected, so you see it in the list), get out of the Settings window. Then restart K2 (quit and launch it again). Play away - always works.

Not sure if anyone's thrown this log on the bug list fire. I haven't because I'd rather see the occasional CPU meltdowns fixed, I can live with this one. Hope it works for you.

Cheers.

 

Ouzo, yeah, I've had to do weird tweaks like that when working with USB keyboards. Glad you've got a recipe for a workaround -- I'll submit this to the devs, although my hunch it's an NI-wide thing, not just Kontakt (since they share their Audio/MIDI Setup code).

Start a new thread with your "occasional CPU meltdown" issue and I'll try and help. I'm not familiar with what you're talking about.

 

sorry ddas, yes you are correct re: connections.
T2 connected via a midisport 4x4 and emu connected via usb directly.

problem is:
Nuendo 3.2, Reason 3.04, Korg Legacy Collection Digital Edition, are all on the same computer, and the ONLY ONE that has this problem is Big suprise K2.......

if they all had similar problems I could safely blame emu and driver installation.... however since it is K2 only, sorry, K2 gets full responsibility.
rsp

 

ddas,
Thanks for the quick response!

I've got to say that this O8 recognition issue has only happened to me with K2. Absynth, Reaktor, and FM7 have always responded for me to any midi setting changes on the fly (without needing to restart those).

Sorry for throwing out the word 'meltdown' without further detail. I am referring to the "CPU spike" discussions in other threads. I believe I am experiencing the same thing (unfortunately) and am eagerly awaiting any update in this area . . .

(I forgot to mention I am on the latest OS X . . . . since the orignal poster had the same config)

Cheers.

 

I kind of lost track of this thread.
But to reply to your suggestions ddas, setting MIDI to "Omni" is the first thing I do in K2.

I've also tried turning off all the MIDI connections in K@. Closing K2. Then launching k2 again, then enabling all the MIDI connections. In other words rewriting the prefs. The issue persists.

I do not believe rolling back the drivers is a reasonable solution. As I believe the last update from M-Audio was 11/05.

I am hesitant to reinstall K@, but will if I need to. I do enjoy using it in standalone mode. As stated in my other thread, my BCR2000 is doing the same thing. Other apps are not having this issue. I still come back to this potentially being a 10.4.5 + K2 issue.

Yeah, emailing tech support will be my last resort. But I've been going back and forth with NI on a GR 2 issue for months.

I'd prefer to sort it out here.

 

At this point, I'd much recommend CALLING tech support rather than e-mailing. I don't know how long it takes to get a response to an e-mailed question, but the 2-3 times I've called NI tech support (in the U.S.) in the past few months, I've gotten hold of someone almost immediately and they've been able to help me through my immediate issue.

 

Thanks for the suggestions David.

I'll try to make time to call NI. I've sent them an email in the meantime.
Support hours are of course my work hours. Which complicates things.

I just noticed that that the MIDI prefs see the BCR 2000 as a BCF 2000, and when selecting the MIDI device and channel, it sees 2 BCF 200's instead of the BCR and the BCF, and does not see the Oxygen 8 at all.

What fun!!

At least it works in Live. (Don't mean to sound cynical. I still like the app. This is just an irritating glitch.)

 

Spoke with NI support yesterday, who were nice enough, but had not heard of my specific issue. Considering that I am probably not the only person using Behringer controllers, an Oxygen 8, OS 10.4.5 and the latest version of Kontakt 2, I must assume that this is a User-specific issue.

NI's recommendations were to uninstall the M-Audio drivers and K2, then reinstall everything.

Fair enough. Both we were both perplexed as to why my M-Audio 2x2 interface is working fine, but not the Oxygen 8.

As stated above, the Oxygen 8 and the BCR are functioning normally in other apps and when K2 is used within host software.

 

I did for the most part what NI support suggested (reinstalled new M-Audio drivers, trashed all the K2 elements and reinstalled).

No change.

By chance tonight I had both Behringer controllers turned off when I launched K2. The Oxygen 8 worked fine.

I quit K2, turned on the Behringers, and relaunched K2, Oxygen 8 did not work. I did this several times, no change.

I have a few USB hubs in the chain that I need to remove for testing. But I'm almost convinced this is a 10.4.5-K2 issue, as no other apps have these issues.

 

I normally hook my oxygen 8 to my laptop using a USB hub. I know that’s probably the worst thing to do but… I’m out of ports and I also leave my Ilok plugged while I play. Here’s where it gets kind of tricky, (stand alone) when I use the Hub with my controller after a little while of play K2 give a very faint clip sound and forgets that the controllers hooked to it, so I have to go to the setup section in K2, disable the controller hit o.k. then go back and enable it, that works for a while but eventually I have to do it again. When I plug the controller directly into my laptop I get horrible ticks and crackles, how is this related?

Laptop:
Toshiba
3.2 p4
1g ram
7200 rpm external hard drive
PT LE7
Oxygen 8 midi controller
Windows XP