You’ll really need to ask Vitus. If it came with Windows drivers and they don’t explicitly state it works with Linux, it’s possible the ALSA protocol doesn’t support it.
Roonserver works with ALSA in Linux. But you need to know if Vitus works with ALSA.
As Scott says, you need to ask Vitus. I notice that there’s no mention of the RD-100 working with Linux-based systems (which is what your QNAP is) in the manual:
Thanks gents, appreciate the input! - pun intended
Vitus do indeed say the USB interface, an M2Tech module; M2TOEM-01-USB-to-I2S requires windows and Mac drivers.
Later Vitus updated the module to M2Techs; M2TOEM-04-USB-to-I2S which M2Tech say has native support for W10, Mac OS and Linux.
So it maybe that my unit doesn’t have the updated module. I’ll have to check this with Vitus i suppose!
My question would then be does roon support the M2Tech module; M2TOEM-01-USB-to-I2S natively?
The good news is the module is a plug in board and easily updated. According to M2Techs website its only about ÂŁ50-100 and the M2TOEM-04-USB-to-I2S module is a direct replacement.
Thanks Simon, I’m a Linux Luddite so haven’t really a clue what to do with that. Can you educate me a little; how would i apply this code/driver if at all possible?
I’ll very probably do both. The new board is a no brainer and it’ll also do 2x DSD natively too.
The idea of a another device between the NAS and the DAC is the update I’ve been putting off for some time. Was looking at the way Antipodes CX/EX servers work and they effectively split the brains from the brawn in a similar way.
It’s also the way RoonLabs suggests that you do things, so maybe there’s something to it .
In the meantime, if you have time to burn and your QNAP can do that, maybe you can try to set a very minimal Windows virtual machine up on it, with just the DAC drivers and Roon.
In any case, as others have told you, until you swap the board out, unless you use a Windows box as an endpoint, which’d be, well, less efficient, you won’t fix your Linux driver problem.
It’s not a case of Roon supporting any particular device. ROCK uses ALSA through the USB port to communicate with a DAC. The DAC will either work with ALSA, or it won’t.
Vitus will know this. If you are lucky you may find another Vitus user in the Forum, but you’ll need to get lucky on that.
DESCRIPTION
M2TOEM-01 is a high performance USB-to I2S converter which allows for asynchronous audio transfer from a computer provided with an USB 2.0 port to a digital audio device or equipment provided with I2S interface. Thanks to proprietary drivers (included in the package), M2TOEM-01 overcomes all the problems and limitations of various off-the- shelf IC’s which operation is generally limited to direct sound 48kHz, 16 bits or, using ASIO or WASAPI drivers, to 96kHz, 24 bits. M2TOEM-01 operates up to 192kHz, 24 bits in kernel streaming mode.
Reason for the question is I have a NUCi7 G10 coming tomorrow with W10 preinstalled.
Was toying with the idea of changing the OS to ROCK, but if the support doesn’t exist in ROCK then W10 will remain till I get the new USB module fitted, then I’ll do the OS thang.
Just tried it with a Mac/Sierra, it didn’t find the RD-100 natively.
I installed the W7 driver on my W10 laptop prior to the RD-100 landing at my door, it was instantly found… I think you may have a point with retaining W10 as the OS.
Please note that a driver is required for Linux also. The driver is already included in the kernel mainline of most distributions, therefore your Linux computer most probably already has it. In this case, your computer will automatically detect and use your old M2Tech product.
Yep, sometimes it just isn’t easy.
ROCK is certainly a custom distribution and you can’t add a driver. So you are at a disadvantage there.
It wouldn’t hurt to shoot them an email. Roon/ROCK is probably mainstream enough that they’ve run across this.
I have ROCK. But I gotta say I never had any problems with Windows and Roon when I used them. And if @rugby prefers, it there are sound reasons behind it.