I just bught a new DAC (Atoll HD-120) as an upgrade from a Maverick Tubemagic D1 Plus. Everything was fine with my D1 plugged in my Vero 4k+ via USB. The Atoll DAC is recognised by the Vero 4K+ and it is listed as “Atoll USB Audio 2.0, Analog” and “Atoll USB Audio 2.0, S/PDIF” but i only get distorted music out of the dac no matter what i try as output config.
I don’t know if it can help but the D1+ uses a Tenor 7022L interface which does’t require any driver to work, not even on windows. The Atoll uses an XMOS interface which doen’t require a driver on MacOs or linux but requires a driver on windows. (The Atoll works fine on my windows laptop with the driver installed).
This is puzzling. Your device seems to support USB Audio 2.0 which is a cross-platform standard so it’s not clear why a special driver is required for Windows. Usually, the Windows driver offers more than simple audio functionality (eg equaliser and other processing) but the device should work without those extras. Edit: I see the Windows driver is needed for asynchronous usage.
‘No driver needed for linux’ implies the interface is USB Audio 2.0 which we do support. When you say ‘distorted music’ what does it sound like? Can you also turn on debug logging and post logs again. Don’t turn on detailed logging for the audio component at this stage.
Something else to check is if you can play sounds without Kodi:
> osmc@osmc:~$ speaker-test -t wav -c2 -l2 -Dplughw:CARD=A20
> speaker-test 1.1.8
> Playback device is plughw:CARD=A20
> Stream parameters are 48000Hz, S16_LE, 2 channels
> WAV file(s)
> Rate set to 48000Hz (requested 48000Hz)
> Buffer size range from 16 to 131072
> Period size range from 8 to 65536
> Using max buffer size 131072
> Periods = 4
> was set period_size = 32768
> was set buffer_size = 131072
> 0 - Front Left
> 1 - Front Right
> Time per period = 0.713719
> 0 - Front Left
> 1 - Front Right
> Time per period = 2.732666
Same “robotic” and distorted voice.
I made me notice that i inverted left and right cables by the way… thanks for this too!
I will contact the manufacturer.
I also have an old Raspberry Pi 2 somewhere which i can use to test with a fresh osmc install, and maybe test with volumio too, but i won’t have enough time this week, maybe next week…
You were right about the windows driver, the DAC works fine without the driver, i think it just adds ASIO support.
From what i have read, the Tenor chip in the D1 plus isn’t asynchronious, it is “adaptative” (no idee what that meens…)
I’ll keep you in touch if i find anything relevant.
A friend of mine came to drink a beer and luckily he had a DragonFly Cobalt with him, which is an async dac too. I could test with it and it works perfectly (log file here). So i think the problem is definitely related to the HD120.
The only weird thing i see in the HD120 log file is that it seems listed as 32 Bits capable :
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_deviceName : @:CARD=A20,DEV=0
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_displayName : ATOLL USB Audio 2.0
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_displayNameExtra: Analog
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_deviceType : AE_DEVTYPE_PCM
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_channels : FL, FR
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_sampleRates : 48000
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_dataFormats : AE_FMT_S32NE
2022-05-22 20:35:56.315 T:2698 INFO <general>: m_streamTypes : No passthrough capabilities
and if i understand correctly, alsa sends a 32 bits format :
2022-05-22 20:36:16.525 T:2699 INFO <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2022-05-22 20:36:16.525 T:2699 INFO <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
but the manual says it is only 16 and 24 bits capable. Could this be the issue?
Just tried hooking up my Ayre QB-9 Dac, this one goes all the way up to 24/192 and is using an xmos chipset powered by usb (although the dac obviously from the size of it has it’s own psu for everything else)
Result: vero 4k+ running the latest update, Kodi 19.4. Usb dac works absolutely fine.
What else is connected to Vero 4k+: sd card, hdmi, usb remote receiver, stock psu.
It’s a long time since I dabbled into usb audio intricacies but I have a vague memory that xmos chipsets are using s32 format and that itself is no indication of anything particular.
osmc@osmc:~$ cat /proc/asound/card1/stream0
Ayre Acoustics Ayre USB Interface at usb-xhci-hcd.0.auto-1, high speed : USB Audio
I found the solution to my problem :
I added an Usb Hub with powered with an extarnal power supply and now everything works fine.
It looks like the power delivered by vero to its Usb ports is not enough for my Dac.
I tried with a Raspberry Pi 2 (both with osmc and volumio) and same problem with same solution.
Glad you fixed it. FWIW my CMedia-based USB DAC often trips out when connected to the front USB2 ports on my desktop PC so these things can be power-hungry.
I have found out why USB DACs often report only 48ks/s samplerate. It’s because the default device is a dmix which forces a 48ks/s rate. I’m working out the best way to fix that so that these DACs are switched to the source samplerate. I assume that’s what everyone would want. dmix has limited application in a mediacenter like OSMC. Multi-channel is unaffected. It’s only stereo that’s forced to 48k.