Arturia Forums
Controllers => MicroLab => MicroLab - Technical Issues => Topic started by: creativeforge on January 29, 2021, 07:29:49 pm
-
I'm on Windows 7 64 bit. I just bought a MicroLab. I'm facing an issue that I never faced before. I have been emailing Arturia tech support back and forth since yesterday. And the agent is completely not understanding my issue. Before I return this unit to the store, I thought I'd ask on the forum, maybe someone went through this and found a solution.
MICROLAB DOES NOT generate AUDIO OUTPUT in OMNISPHERE (standalone, NOT going through a DAW).
MICROLAB DOES NOT generate AUDIO OUTPUT in KONTAKT (standalone, NOT going through a DAW).
I'm on Windows 7 64 bit machine, with 24 GB RAM and Intel Core i7 920 @ 2.67GHz.
I did modify all the settings I could find but nothing changed. I searched online too.
With Arturia MicroLab, ALL my virtual synths respond with audio output, but NOT Kontakt. And NOT Omnisphere. I can see the MIDI lights flashing (so it works) but no audio comes out of my DAW. I can record and I see the MIDI data, but there is no audio out.
With a different MIDI controller M-Audio Oxygen 49) everything works perfectly, plug and play.
Kontakt does not output audio with Arturia MicroLab.
Anything I should know about Kontakt with Arturia products? Anyone has encountered this issue and fixed it easily? (I'm on Win7, but Win10 also has the same issue).
Thank you for any help,
Andre
-
Sorry for asking such a complicated question that had everyone reading it completely stomped. ;)
In case someone else faces this issue as a NEW OWNER of a MicroLab keyboard, and unfamiliar with Arturia's settings, I will now share the solution to my dilemma.
MANUAL - PAGE 10:
2.1.3.1. Selecting the Keyboard MIDI Channel:
Hold Shift and press a key on the keyboard to select the output MIDI Channel for the MicroLab keyboard. The channel number (1-16) is labeled directly above the first 16 keys of the keyboard.
Took me 3 days to find this simple answer. I hope to help someone to avoid the same fate.
Regards,
Andre
-
Welcome.
Glad you got it sorted.
The vital bit of information you initially forgot to share was that you'd obviously already changed the default midi channel from 1 to something else, probably why nobody thought of suggesting you check the midi channel is still set to 1.
But you got there in the end, which is good.
-
If I changed the channel, it was unwittingly. Just glad I found a solution! :)
BUT I LOATHE THE MORONIC THREE-STEPS VALIDATION TO POST A SIMPLE QUESTION ON THIS FORUM!!! OMG! ARE YOU KIDDING ME?!