Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[zenpmd]

Is this something which could be compiled? Would be really useful!

[JimH]

What are you asking for?  Most USB DAC's work.  

Do you mean a sticky thread?  

[zenpmd]

I have found neither the Benchmark HGC2 works, nor the McIntosh D100.

And yes, sorry a Sticky!

[Arindelle]

I have found neither the Benchmark HGC2 works, nor the McIntosh D100.

they should work  ?

[zenpmd]

Yeah I agree, but it seems that some dacs just dont play well with Linux.

The Benchmark is quite buggy even when used with windows.

[Awesome Donkey]

Schiit DACs work fine on Linux.

In fact, most DACs should work fine out-of-the-box.

[mwillems]

All USB Audio class 1 and 2 compliant devices "should" work out of the box with Linux. The "should" is in quotes because some devices claim UAC2 compliance when they are not actually remotely compliant. Note that UAC1 and UAC2 are not the same as USB1 or USB2 compliance.  The USB Audio Class is a distinct standard from the main USB data transfer standard.

The authoritative source for Linux audio device support for non-UAC1 and UAC2 compliant devices is the ALSA matrix:

http://www.alsa-project.org/main/index.php/Matrix:Main

So when I buy DACs for Linux, I follow the following three steps:

1) Scour online reviews (Amazon, et al.) for mentions of people actually trying the device with Linux (this is by far the most reliable source of information).
2) If no help at 1), check and see if the device claims UAC1 or UAC2 compliance, and, if not
3) Check the ALSA matrix.

Both the DACs you mention advertise UAC2 compliance, and both the McIntosh is reported (in professional reviews) as working with Linux.  If they're not working you may want to make sure you don't have a configuration issue.

[zenpmd]

All USB Audio class 1 and 2 compliant devices "should" work out of the box with Linux. The "should" is in quotes because some devices claim UAC2 compliance when they are not actually remotely compliant. Note that UAC1 and UAC2 are not the same as USB1 or USB2 compliance.  The USB Audio Class is a distinct standard from the main USB data transfer standard.

The authoritative source for Linux audio device support for non-UAC1 and UAC2 compliant devices is the ALSA matrix:

http://www.alsa-project.org/main/index.php/Matrix:Main

So when I buy DACs for Linux, I follow the following three steps:

1) Scour online reviews (Amazon, et al.) for mentions of people actually trying the device with Linux (this is by far the most reliable source of information).
2) If no help at 1), check and see if the device claims UAC1 or UAC2 compliance, and, if not
3) Check the ALSA matrix.

Both the DACs you mention advertise UAC2 compliance, and both the McIntosh is reported (in professional reviews) as working with Linux.  If they're not working you may want to make sure you don't have a configuration issue.

Thanks so much. Thats very helpful. Slightly different question, why dos windows require manufacturer specific drivers in order to play 192? (At least in the case of the Benchmark)

Thanks

[mwillems]

Thanks so much. Thats very helpful. Slightly different question, why dos windows require manufacturer specific drivers in order to play 192? (At least in the case of the Benchmark)

Thanks

The short answer is that 192 requires UAC2 support (UAC1 doesn't support 192), and Windows doesn't support the UAC2 protocol out of the box, it only supports UAC1 devices.  In that respect, both OSX and Linux are "more compatible" than windows.  Windows (for the moment) still has a dominant enough market position that they can effectively say to vendors "write a driver or risk incompatibility." 

It's frustrating as that attitude has slowed UAC2 adoption among vendors as they know they have to write a driver for windows anyway, and that's most of their market share, so why bother with UAC2 at all?  Which means that Linux and OSX get left in the cold sometimes despite "doing the right thing" with respect to standards compliance.  That's changing (slowly), but mostly at the high end of the market.  Budget and mid-range DACs are often entirely incompatible with Linux or only work with reduced UAC1 functionality. 

[zenpmd]

The short answer is that 192 requires UAC2 support (UAC1 doesn't support 192), and Windows doesn't support the UAC2 protocol out of the box, it only supports UAC1 devices.  In that respect, both OSX and Linux are "more compatible" than windows.  Windows (for the moment) still has a dominant enough market position that they can effectively say to vendors "write a driver or risk incompatibility." 

It's frustrating as that attitude has slowed UAC2 adoption among vendors as they know they have to write a driver for windows anyway, and that's most of their market share, so why bother with UAC2 at all?  Which means that Linux and OSX get left in the cold sometimes despite "doing the right thing" with respect to standards compliance.  That's changing (slowly), but mostly at the high end of the market.  Budget and mid-range DACs are often entirely incompatible with Linux or only work with reduced UAC1 functionality. 

Thanks so much for educating me. This is wonderful. A total idiot as PS Audio asked the "software guy" within his own organisation who couldnt say whether the Sprout has UAC2. HOW CAN THEY NOT KNOW THIS!?!

[Awesome Donkey]

I really, really hope they add UAC2 support to the next Windows 10 update.

Seriously, Windows is more-or-less the last holdout OS without UAC2 support - even Android has UAC2 support! There's an open discussion/request for UAC2 support here: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/windows-support-for-usb-audio-20/0d633b9f-3193-4c63-8654-fb10b3614a04

[mwillems]

Thanks so much for educating me. This is wonderful. A total idiot as PS Audio asked the "software guy" within his own organisation who couldnt say whether the Sprout has UAC2. HOW CAN THEY NOT KNOW THIS!?!

If you didn't spell it out in your inquiry (USB audio class 2) they might have been been confused by the UAC2 acronym (some industry folks just call it "USB 2" which immediately leads to confusion between the audio and data standards).  If you spelled it out and they still don't know, I'm not sure I'd want to buy a DAC from them.

According to their forums/ad literature, it's plug and play on Mac which suggests UAC2 support.  So if I were forced to take a bet, I would probably bet on some kind of UAC2 compliance, but I certainly wouldn't bet $500 on it  

[zenpmd]

Thanks so much mcwillems, you're the best. This is all so helpful.

By the way, I am new to Linux, and want to learn it properly - I know Arch is suprisingly good for this. Is there any particular way of going about it? I know the arch forums are not designed for noobs hence that verification check which a noob cannot answer, but is there any good guides other than their wiki to get up and running?

[mwillems]

Thanks so much mcwillems, you're the best. This is all so helpful.

By the way, I am new to Linux, and want to learn it properly - I know Arch is suprisingly good for this. Is there any particular way of going about it? I know the arch forums are not designed for noobs hence that verification check which a noob cannot answer, but is there any good guides other than their wiki to get up and running?

I would advise using the beginner's guide on the Arch wiki; it's really very step by step (but read it all first). That way you can get support on the Arch forums later (they don't support third party install guides).  If you have trouble with the Arch wiki, keep trying and reading more until you sort it out.  Take your time.  The Arch forums can be quite helpful provided you specify your issue carefully and lay out all the steps you've taken.  Arch requires a certain amount of maintenance and care to "do right," and it's better to work through it yourself.  Many of the "easy arch installers" mangle things or don't call your attention to the fact that they're doing or not doing certain things at all.  

Doing it using the Arch wiki method (especially the first time) is an important part of the learning experience.  Arch can be tough for new users, but you'll learn a lot trying  

[Awesome Donkey]

Arch is definitely a leap into the rabbit hole compared to other 'easier' distros like Debian and Ubuntu.

Many of the "easy arch installers" mangle things or don't call your attention to the fact that they're doing or not doing certain things at all.

Ugh, yeah, can't stress this one enough. I've read stories about Antergos, Evolution Linux and Architect Linux. Oh man, there was a lots of drama over the last two weeks with Architect all because of somebody making a bug report and the developer being very rude about it. The *only* Arch installer I've heard good things about is Arch-Anywhere, which I might have to download at some point and try it in a VM.

Doing it using the wiki method (especially the first time) is an important part of the learning experience.  Arch can be tough for new users, but you'll learn a lot trying  

Couldn't agree with this more. The Arch way is the way to go with the first install.

However, I will say that MC works perfectly on Arch and looks perfectly with my custom Arc Theme skin I made for it. Arch + Gnome + Dash to Dock + Arc Theme + MC = eye candy.

[mwillems]

However, I will say that MC works perfectly on Arch and looks perfectly with my custom Arc Theme skin I made for it. Arch + Gnome + Dash to Dock + Arc Theme + MC = eye candy.

It does work nicely, and a reskinned Gnome with the right extensions is a beauty to behold (I like the numix dark themes personally, which Modern cards fits in with moderately well).  I'm pretty much a permanent Gnome convert at this point.  I only keep windows around on workstations for AAA games and Theater View in JRiver; everything else I use runs on Linux or in Wine.  Now we just have to convince Bob to build in MPRIS/dbus hooks so the new Gnome 3.20 media controls will work with MC  

I'd be interested to see your Arc theme if you're interested in sharing  

[Awesome Donkey]

I assume you're running the Arch testing repo? I'm still using the stable repo, but I'm itching to get GNOME 3.20.

Here's a screenshot of my desktop - I still go for the Unity-esk type of thing with the dock, though this is much better (and Arc Theme enhanced!): http://i.imgur.com/dj7QMGY.jpg

Here's a screenshot of my file manager using Arc Theme. I'm using Nemo since I can't stand what they did to Nautilus/Files and the horrible icons: http://i.imgur.com/aUApDM1.png

Here's MC itself using the system fonts and the Arc Theme modified ModernCards skin (which I do plan on changing the buttons/menus colors): http://i.imgur.com/FKuVII5.png

Mmmm, very nice setup if I say so myself.

zenpmd, if you want to try Arch, I highly suggest you try it in a virtual machine first.

[st1]

Mutec mc-1.2  usb  bidirectional signal converter interface works with 15.10 ubuntu even though not officially supported by mutec.  I use it as aes ebu converter for active  signal manipulation devices.  Also good for a connection to Genelec DSP speakers that have dac inside and aes ebu digital input.  the 3+ version is then even way better than the 1.2 but far more expensive. 
info:    http://www.mutec-net.com/product_mc-12.php

[wellywu]

The Oppo Digital HA-1 and Chord Mojo work with GNU/Linux and Apple Macintosh OS X "El Capitan." The HA-1 has been utterly reliable and hassle free with GNU/Linux.

[skidmata]

FYI  Oppo ha-2 works perfectly.

[VR6]

I have an Ayon Audio S-5 streamer and I am running the Linux version of MC through a QNAP TS-251+. The input on the Ayon is by Ethernet cable. There must be compatibility issues because I have songs that i can play through other software packages that give me file format errors on the Ayon.
Under the devices on the MC I have it set to the default ALSA but I am reading here that that is for USB. Maybe that is my issue.

If I am running my music through my LAN and to my Ayon by Ethernet which of the devices do I use? The items on the list are unknown to me and have names I am unfamiliar with.

My unit does not have standard USB inputs.

Jerry

[bob]

I have an Ayon Audio S-5 streamer and I am running the Linux version of MC through a QNAP TS-251+. The input on the Ayon is by Ethernet cable. There must be compatibility issues because I have songs that i can play through other software packages that give me file format errors on the Ayon.
Under the devices on the MC I have it set to the default ALSA but I am reading here that that is for USB. Maybe that is my issue.

If I am running my music through my LAN and to my Ayon by Ethernet which of the devices do I use? The items on the list are unknown to me and have names I am unfamiliar with.

My unit does not have standard USB inputs.

Jerry

The Audio output (ALSA) selections only apply to devices connected physically to the linux box (QNAP in your case).
Network devices use DLNA and therefore use the settings in MC's DLNA server configuration.
When you click on the zone for your Ayon in the tree that becomes the default playback device and the files that you play are transferred via DLNA protocol over the network to your renderer.
DLNA devices are not uniform, they have different configurations depending on their capabilities. The settings in MC's DLNA server configuration are how you match the capabilities of your device with what's being sent to it.

[VR6]

Thank you Bob. That answers my question. I still cannot get it to work. My settings for the DNLA are on the Generic DNLA and for original format, no conversion. I can play a few albums but most I get a message on my streamer that says 'file format error' and then the whole program locks up and it takes a while to get it to respond again. I have tried the other setting of 24 bit DAC and legacy UPnP and the same thing happens.

Is it possible that my Ayon does not work with the Linux version of MC? It does work with the Mac version played through a Mac Mini.

Jerry

[bob]

Thank you Bob. That answers my question. I still cannot get it to work. My settings for the DNLA are on the Generic DNLA and for original format, no conversion. I can play a few albums but most I get a message on my streamer that says 'file format error' and then the whole program locks up and it takes a while to get it to respond again. I have tried the other setting of 24 bit DAC and legacy UPnP and the same thing happens.

Is it possible that my Ayon does not work with the Linux version of MC? It does work with the Mac version played through a Mac Mini.

Jerry

I'm guessing your Mac is probably using the generic DLNA setting as well.
The generic setting doesn't get the information about what the playback device supports from the device itself because a lot of devices provide unreliable information about what they support.
Because of the the generic DLNA profile converts everything that isn't in 16 bit wave format or mp3 to mp3. Every device out there should play those two formats.
Because you are using "original format" on the QNAP, there must be files in your library that your Ayon can't play natively.
To get the most out of your Ayon you will need to know just exactly what formats it supports.
The 24 bit audiophile DAC format is designed to do this for most devices.
You could try that to start and check the "stereo downmix" option under the advanced audio settings for MC's DLNA server configuration.
To handle sample rate issues if they exist, in that same advanced area you could change the "same as source" setting to a fixed rate, say 96k if you AYON supports that.

[VR6]

Bob,

My Ayon supports 192/24 no problem. I will try the 24 bit DAC setting again I guess.

[VR6]

I tried the 24 bit DAC setting. Also a no go. 

[kstuart]

Schiit says on their Bifrost FAQ page:

Q: How about your USB with Linux ?
A: Most Linux distros that support USB Audio Class 2 will work without drivers. Please note that we are not able to provide troubleshooting or support of Linux issues.