cannot connect with Yamaha MG-XU usb mixers on Windows

[iamthechrisb]

great project! Been testing with a few people and have not been able to get anyone on that has one of the Yamaha MG-XU usb mixers -- eg the MG10XU and 16. This happened with both the Yamaha/Steinberg Driiver and Asio4all. The device would show as unsupported at times. These messages were seen in the log:
22:29:24: Accessing audio device Yamaha Steinberg USB ASIO
22:29:28: Setup>Inputs>Device updated: Yamaha Steinberg USB ASIO
22:29:31: Device reports no buffer sizes are available!

Any Ideas?

Thank You!

[christofmuc]

Hm, the log file should list the sample rates and buffer sizes reported to be available by the interface. Also, some drivers on Windows do not allow the software to configure the audio device, but only the driver's control panel. So the sample rate needs to be set to 48000 and the buffer size to 128 manually before launching the software.

But first check the output to see which values are reported.

Worst case would be to recompile once you found out which samplerate/buffer size is supprted by the audio interface - try to adjust the buffer and sample rate settings in the BuffersConfig.h - https://github.com/christofmuc/JammerNetz/blob/master/common/BuffersConfig.h.

I have not managed to get a good experience with Asio4all, I would strongly recommend the native driver if one is available.

[christofmuc]

No buffer sizes could actually point to a wrong sample rate. The software is compiled for 48000, and needs to be recompiled for different sample rates.

[iamthechrisb]

No buffer sizes could actually point to a wrong sample rate. The software is compiled for 48000, and needs to be recompiled for different sample rates.
Thanks for the reply
was compiled with defaults. we want to run at 48, the device supports this and runs fine with Jamulus and Sonobus. If the device is set to 44.1 when not used by say Jamulus, then Jamulus can open it and use it. Is Jamulus telling it to use 48? Feels like something is missing when Jammernetz goes to open the device.

[christofmuc]

Hm, the code is pretty straightforward and in line with the ASIO functions. The problem might lie within the JUCE library used by Jammernetz, there is an additional define possible to turn on ASIO detailed logging.

What library is used by Jamulus and Sonobus? I know JUCE is no longer that well maintained by now.

[iamthechrisb]

Sonobus is Juice as far as I know. Jamulus uses the ASIO SDK? I thought JUICE was pretty active. Is there something that needs updated perhaps? I recall some time ago there were issues with JUICE and yamaha.

[christofmuc]

You might be referring to https://forum.juce.com/t/yamaha-steinberg-usb-asio-problems-since-july-commit/36685/30

What we need to find out is if Jammernetz makes anything funny - I don't think so, but we can investigate when compiling with -DJUCE_ASIO_DEBUGGING=1, e.g. by adding

		JUCE_ASIO_DEBUGGING=1

to line 160 in the CMakeLists.txt file. We should see the full communication and ASIO calls.

[iamthechrisb]

You might be referring to https://forum.juce.com/t/yamaha-steinberg-usb-asio-problems-since-july-commit/36685/30

What we need to find out is if Jammernetz makes anything funny - I don't think so, but we can investigate when compiling with -DJUCE_ASIO_DEBUGGING=1, e.g. by adding

		JUCE_ASIO_DEBUGGING=1

to line 160 in the CMakeLists.txt file. We should see the full communication and ASIO calls.

clarification - would this be for the client build or server?

[christofmuc]

The client. The server contains no ASIO code as it does not need to work with audio devices directly.

[iamthechrisb]

The client. The server contains no ASIO code as it does not need to work with audio devices directly.

makes sense -- just did not want to build the client and wanted to make sure

[iamthechrisb]

The client. The server contains no ASIO code as it does not need to work with audio devices directly.

It could take me a while to get this built. Would you be willing to build a client with this option? it could be a handy command line switch to help troubleshoot other potential ASIO issues.