I have a installed Roon 1.3 (using Chris Reike excellent installer v2017-02-02) on my QNAP TS-459 Pro II (running QTS 4.2.5 - can’t be upgraded to 4.3.x) and connected an AUDIOLAB M-DAC+ to it using an USB cable.
When I try to render the sound on the DAC (by selecting the Audio tab of Roon preferences) the Audiolab device is not listed as ‘Connected to Core’. Any idea why?
I noticed the following messages in dmesg / console when plugging the Audiolab device:
[15289.569038] usb 2-4: new high-speed USB device number 15 using ehci_hcd
[15289.773857] cannot get ctl value: req = 0x83, wValue = 0x201, wIndex = 0xa00, type = 4
[15289.774327] cannot get ctl value: req = 0x83, wValue = 0x200, wIndex = 0xa00, type = 4
[15289.803241] input: AUDIOLAB AUDIOLAB USB Audio 2.0 as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.3/input/input12
[15289.804714] generic-usb 0003:2622:0041.000B: input: USB HID v1.10 Device [AUDIOLAB AUDIOLAB USB Audio 2.0] on usb-0000:00:1d.7-4/input3
Here’s the /proc/asound/cards content:
1 [A20 ]: USB-Audio - AUDIOLAB USB Audio 2.0
AUDIOLAB AUDIOLAB USB Audio 2.0 at usb-0000:00:1d.7-3, high speed
When aplay can see the device, Roon will also. I think we’ve just proven that this problem is lower-level than Roon.
The fact that it’s in procfs is a good sign that the kernel can initialize the device at some level.
To check if the device is being used, you could run speaker-test -D hw:1,0 -c 2 -r 44100 -F S32_LE and see if you can make sound come out of it.
If it works, that tells us one thing. If not, then it should print an error that either indicates the device is in use, or maybe tells us something else.
Just like with aplay, if speaker-test can’t be made to work, Roon won’t work either.
Ideally, you would be running all of these commands with the same account/permissions as Roon’s environment on the NAS.
Playback device is hw:1,0
Stream parameters are 44100Hz, S32_LE, 2 channels
Using 16 octaves of pink noise
ALSA lib pcm_hw.c:1713:(_snd_pcm_hw_open) Invalid value for card
Playback open error: -2,No such file or directory
Chris,
No soundcore.ko file under /sys/module… But on yours neither, apparently so this might not be the problem. What does lsmod | grep snd tell on your system ?
@Christian_Chateauvie, why did you delete your comment saying MusicStation is working–is it not actually working? (Just making sure we’re thinking about this clearly).
Also, on the off-chance that you can do this test–do you have another Linux machine that you could plug the DAC into and see if it works with Roon Bridge?
Especially if MusicStation is not working, this could be an issue between the DAC + Linux instead of the DAC + QNAP. Just helps isolate the problem further.
MusicStation is working - but I suspect it is using OSS and not Alsa. This is why I’ve deleted my post.
I’ve connected the DAC to another Linux box and it is probably recognized by ALSA (aplay -l lists the device).
Unfortunately this other linux box is not supported by Roon (it is a 32-bit kernel)
So this must be something about the QNAP kernel or something. I haven’t tried connecting another USB device to it because I don’t have any right now - but will test further
Frankly I am a bit desperate now. Not certain if I should sell my QNAP for another model (do you know if things might get better on a TS-469L, which supports QTS 4.3.3) or if I should better switch to Synology - your advice would be welcome.
PS I tried to downgrade the firmware to 4.2.0, to no avail.
I don’t see this app being available in my QNAP app center.
But anyways.
Things work on your QNAP in spite of alsa -l not working
so where do you think the problem can be ? Brian seemed to indicate that Roon wouldn’t detect if aplay doesn’t …
Not on mine at least. But this is not a prereq for Roon, right ?
So could the problem be coming from Roon and not from my NAS ? I suppose Roon detects your devices even whe you don’t have HybridDesk and the alsa command does not work ?..
