Asio connection after boot failing [Resolved]

Support
1

After I (re)boot my NUC the connection with the asio driver of my singxer su-1 seems to be failing.
I can remote into the box, simply stop de roon bridge service and restart it, after which it works fine.

Prior to the 1.3 release I had no issues. Will see if I inadvertently mucked something else up, but nothing obvious (i.e. don;t have jriver or other application that could access the device running at or post boot)

Intel NUC core i5, 16 Gb
windows 10
roon bridge
USB device: singxer SU-1

In the logs the key difference is:

02/24 21:53:18 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [output/asio] [XMOS USB Audio 2.0 ST 3086] calling start()
02/24 21:53:18 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [output/asio] [XMOS USB Audio 2.0 ST 3086] asioMessage 3 0
02/24 21:53:18 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [output/asio] driver reset

versus

02/24 21:59:33 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [output/asio] [XMOS USB Audio 2.0 ST 3086] calling start()
02/24 21:59:33 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [output/asio] [XMOS USB Audio 2.0 ST 3086] asio output started
02/24 21:59:33 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [lua@000000000388FD38] [192.168.1.181:58767]  got output message {"signal_path": [{"type": "output", "quality": "lossless", "method": "asio"}]}
02/24 21:59:33 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [lua@000000000388FD38] [192.168.1.181:58767]  SENT [6] {"message":{"signal_path":[{"type":"output","quality":"lossless","method":"asio"}]},"status":"OutputMessage"}
02/24 21:59:34 Trace: [RAAT::XMOS USB Audio 2.0 ST 3086] [lua@000000000388FD38] [192.168.1.181:58767]  SENT [6] {"status":"Success","audio_port":60053,"clock_port":60052}

Any suggestions? Remoting into the box after a (re)start is not very convenient…

2

Hi @rovinggecko ----- Thank you for the report and my apologies for the troubles here. I would like to grab a copy of your Core + RAATServer logs and will be contacting you momentarily via PM with upload instructions. Thanks!

-Eric

3

Case closed. :slight_smile:

My AcourateConvolver Asio driver is a virtual driver that adds convolving functionality to the end asio driver (for example my singxer su-1 dac asio driver).
You can only use that su-1 driver once…

At start, Roon polls all asio drivers (looking for their capabilities).
The acourateconvolver driver triggers the su-1 driver, but… Roon tries to lock that su-1 asio driver at the same time, as I have set this as my driver for Roon.
Result: 50% no joy.
Simply setting a different end driver for acourateconvolver works around this issue.

2 Likes