First of all, vital stats
Toshiba laptop, running Windows 7 64bit, Intel Core i3 Inside processor. 4.00GB of RAM.
Cubase AI5, latest version. Had it bundled with a Yamaha Audiogram 3 USB soundcard.
MIDI device is a Yamaha YPT200 keyboard with a USB-MIDI interface, first of all a cheap cable from Amazon, now a Yamaha UX16
Right, so a month or so ago, Cubase would BSOD whilst recording MIDI. I could record hours of audio if I wanted to, but it would crash within five minutes of recording midi input. The crash report blamed a driver belonging to another program, NCH Soundtap. After uninstalling the program, the driver still caused problems, and after some stressful attempts to delete that, finally got rid of it (not deleting anything else, I know futzing about with the registry is dangerousā¦). And nowā¦ no MIDI input. The transport bar shows no signal. Everything in Cubase seems to be in working order, ports are visible, right ones selected, cables plugged in rightā¦ nothing.
Have tried reinstalling the generic Windows MIDI driver, that didnāt change anything. Cubase support couldnāt help because I got it bundled with a Yamaha product. Yamaha support thought it was a driver issue, and suggested I buy the aforementioned Yamaha UX16. Having got this, Cubase sees it ok, the Yamaha driver is installed, and everything is in the right placeā¦ except I still have no MIDI input. Iām stumped!
Still nothingā¦ Everything is as it should be in Cubase. It just seems like nothing is coming in. The transport just registers no incoming MIDI signalā¦
Try the free MIDIOX (google it). It is a Windows application that allows you to see if the MIDI is making into Windows. It might help determine where the MIDI is getting cut off.
HTH
J.L.
Well now that says my Yamaha UX16 is suffering an āunspecified external errorā. And yeah, no signal is coming in at all there. The cable is brand new, so it could be the keyboard? Sheeshā¦ In the morning. Thanks for the help!
Ok, so with both cables the same error message comes up. So all signs point to the keyboardā¦? Except I canāt figure out how it would have deteriorated soā¦
Got my hands on a Korg Nanokey that again, used to work but I havenāt used it with the computer for about 6 months. Same issuesā¦ So if no keyboards work, if no special midi drivers work, if reinstalling cubase doesnāt workā¦ What the hell do i do? This is getting rather urgent.
If I follow you correctly, you have now had problems with two different keyboards and testing them both with MIDIOX taking Cubase out of the equation. If I am correct, it seems like it has to beā¦
Something Windows related to that registry change. Windows restore/repair/re-install may be needed.
USB port problems. Try different USB ports and double check the correct/latest drivers. I am a little unclear as to your interfacing. Are you are using the Audiogram AND a MIDI interface or when you say the āYamaha keyboard with a USB interfaceā do you just mean it is a USB plug to software interface? (i.e. NOT a physical MIDI interface). How is the Nanokey connected?
J.L.
Thanks for the prompt replies - another thing to add confusion is that I just installed, for lack of any other solution, a trial of another DAW (Cockos Reaper) and the Midi Input works! It is still unresponsive in Cubase, though, and MIDI-OX claims an āunspecified external errorā still with the nanokey.
Jaslan, to clarify: With my Yamaha keyboard, the one in the first post, it is a USB to MIDI cable - it does not connect to the Audiogram, rather one end in the computers USB port and the other which connects to the back of the keyboard with MIDI in/outs. The Nanokey connects with a USB cable, no traditional MIDI in/outs on it. Iāve checked all the drivers, and theyāre ok.
This is very similar to what has happened to my PC. Also Windows 7 64-bit. I have a Kontakt Audio 6 USB audio/MIDI interface and a Yamaha S70 XS keyboard connected via USB MIDI. The Kontakt came with Cubase LE 4 and the S70 XS came with Cubase AI 4. I installed LE first and then uninstalled in favor of AI. For both, MIDI worked initially, that is, the devices could be seen and MIDI data flowed. However I was getting random BSOD with anything where I used MIDI, especially when I exited an application.
As atomiklust reported, I also had NCH SoundTap applications and the BSOD was referring to the stdriver64.sys driver from those applications. SO I uninstalled all of them (via Control Panel). Now I have no MIDI response whatsoever. Nothing is recognized. The devices all show in Device Manager, Control Panel, etc, but the applications donāt actually seem to pass any MIDI information at all. Very strange.
Have referred it to Yamaha also, but so far they are stumped. Iām going to see if I can run this by the folks at NCH since it was their driver uninstall routine that seems to have caused the problem.
i also seem to have the same problem with this as i installed sound trap then got BSOD after a days use, sorted the problem now my midi is not working within cubase nor protools. but yet it works with my VST standalone plugins???
very strange indeed.
Similar problem here. āAll midi inputsā (both USB and virtual keyboards) had always worked up until 5/11/2012. Also have the same issue where All midi inputs work fine in a standalone vst. Found some great sounds, but now i canāt record them. There were some Windows 7 automatic updates around that time, I donāt know if that is a factor.
