No MIDI Input

[Sweaty Ear]

Was trying to solve latency issues and installed ASIO4ALL. it worked for about 30min. Now there seems to be no midi data coming from the controller into the daw as no sound plays and the meters don't waver. I double-checked with a 2nd controller but still no input. Is there a setting somewhere that could cause this?

[Peter Widdicombe]

Did you bump the USB cable? Windows (Waveform?) is unforgiving when you lose the MIDI/USB connection momentarily. Sometimes you have to just save and restart waveform if that happens.

You could have also filtered out the MIDI channels on the MIDI device settings. If the MIDI channel your keyboard sends on is filtered, it will be "invisible". PS - this CAN be a good thing, if your keyboard has Pads as well, as you can have a virtual MIDI device on the same keyboard, where ie channel 1 is "keys" and channel 10 is PADS. Default "keyboard" you filter 10 out; and default "device-pads" filters out all BUT channel 10. Then you can play pads with one hand, and keys with the other; and not have pads playing your piano.

Maybe we need a FR: Re-init USB and discover newly connected MIDI (and audio) devices?

[Sweaty Ear]

How do you un/filter the midi channel? i've re-plugged the usb cable more than once. it was working but all of a sudden there was no sound. when the controller is plugged in you hear the Windows usb chime and it shows in the device manager. are there any other possible reasons why this could be happening?

[Watchful]

I suspect most issues like this are the result of the operating system. It's easy to hate on Microsoft Windows for this, because most of the time that's the culprit.

Peter's right about having to quit/restart Waveform. I often have to do that, but there are a couple of other things to try:

1. Go to the Settings tab, and find your ASIO4ALL driver. Switch to a different one... then switch back. That often nudges Windows to look in the right place.

2. Very seriously consider changing your USB cable with a different one. The less expensive or longer your USB cable is, the more error prone it will be. Sometimes it only takes a small system change--like adjusting latency or changing drivers--to make it fail. I can't count the number of nightmares that have been fixed with hardware and software just by testing a better USB cable.

3. If your hardware is plugged into a hub, and the hub connected to a computer, try powering off the hub and turning it back on before launching Waveform. Sometimes this resets a gummed-up buffer and lets you get back to work.

[Sweaty Ear]

saw the midi filter input setting. must've gotten switched off when changing drivers. that solved the issue. thanks. your expertise is appreciated.

[Watchful]

Wow, great call, Peter! Thanks for the update, Sweaty Ear.

[Tinkerer]

I use a Novation Launchkey 49 MK3 and whenever Waveform is unresponsive to controller inputs, I used to restart Waveform (and sometimes reboot the PC), but that can take too long when you're in the zone, so now I do 2 simple steps:
1. Check the USB cable to ensure it is securely seated
2. Go to the Waveform "Settings" page, and hit the "Refresh MIDI Device List" button
So far, this method has worked 100% of the time! (Oops, hope I didn't just jinx it)