Miniraze audio output device problem

Question

This is a question pertaining to the Standalone version of Miniraze running on Windows 10 Pro (22H2)

I have a Mackie ProFX10 USB mixer which has a dual USB stereo channel output capability.  Mackie has their own ASIO USB driver which I have successfully installed on Windows 10 Pro and which is detected by virtually ANY Windows audio processing and DAW software that I use as a choice within the Audio setup dialogs

One pair of USB outputs is named ProFX (1-2) and the other is named ProFX (3-4).  The ProFX (1-2) is my default because it feeds the Headphone and Control Room outputs and faders on the mixer.  The ProFX (3-4) output is primarily for sending the mix to the Main 1/4" and XLR out jacks but does NOT route to the Control Room or Headphone jacks so I don't use it.

In the Miniraze settings I try to choose ProFX (1-2) but when I do the Output field box remains empty, seemingly Miniraze does not recognize it.  I am able to choose the ProFX (3-4) and get Miniraze to recognize it but the synth will not produce any sound using this setting.

As I have never seen this lack of choice between these Mackie ASIO USB stereo output pairs on any other audio software I am stumped.

Any suggestions?

Answer 1

I'm getting the same issue using a Focusrite Scarlett Solo 4gen. Selecting my audio output from the dropdown does not change the value from "none." No other softsynth stand alones have this issue.

Answer 2

It's Feb 2025 now, still no answer other than another user reporting similar behavior.

Still looking for an answer to how MOK software coding (I'm guessing it at the coding level?) handles devices which have multiple ASIO outputs.  For devices which have more than one ASIO channel output, MOK is choosing one by default and the other is detected in the MOK Audio settings but when it is chosen the Audio slots becomes 'NONE' which effectively stops all audio.

Please MOK tech/designers confirm that this is either intended design or a bug.

-M

Answer 3

Currently, this is (unfortunately) the way we are using the Juce Audio I/O.   I have this on my list to look at for the next update, as all things JUCE and Audio are getting a major update...  if you would like to be on the Beta, email info@mok.com, and I can add you to the list.