More > JRiver Media Center 28 for Linux
Troubleshooting the Steinberg UR824 with JRiver on Linux
mwillems:
So this is a long shot, but I wanted to post here in case anyone might have any tips or insight on a technical issue I've been struggling with on and off for a few years. The Steinberg UR824 is an 8-channel DAC that I've been using successfully in windows with an ASIO driver.
However, the Steinberg also has a "class-compliant" mode that will let it function as a USB Audio Class 2 compliant device, which means it should work correctly with Linux. When I put the UR824 in class-compliant mode and connect it to a Linux PC, pulse audio "sees" the UR824 as an 8 channel device and normal Linux audio applications will play to it through pulse with no manual configuration of any kind. So far so good.
In JRiver, if the Steinberg is the default output, and I set the JRiver output device to "default" or to "pulse" everything works fine, I can play to all eight channels and things work perfectly. However, if I try to output in JRiver to any of the hardware direct modes (front:, hw:, surround71:, etc.). I get horrifying crunching distortion at maximum volume! Needless to say I've been reluctant to try too many things when the failure mode is 100dB crunching noise, but I did try each of the hardware outputs in JRiver and they all fail the same way. This problem has existed for a few years, and in every Linux distro I've tested. I would really prefer to be able to address the hardware directly in JRiver for a few different reasons (e.g. I need the system default sound output to go to a different device, but want JRiver to output to the Steinberg).
So I was wondering if anyone here encountered a similar issue either with this specific hardware or other hardware? Barring that, obviously pulseaudio is able to see and autoconfigure the device correctly, so it can work in the Linux environment; there's just some difference in the way JRiver is addressing the hardware I suspect that's causing this issue. I suspect there might be some ALSA configuration trick that might be able to smooth this out, but I just don't know enough about the way JRiver is addressing the device to know what might be the issue.
Bob, if you or anybody at JRiver have any thoughts, I can post logs, but I know this is a pretty niche issue so no worries if you guys have bigger fish to fry.
JimH:
No idea, but is a firmware update possible?
Does it work with another player?
mwillems:
--- Quote from: JimH on January 29, 2022, 05:40:18 pm ---No idea, but is a firmware update possible?
Does it work with another player?
--- End quote ---
I tried updating to the latest device firmware with no change, but that's a good idea.
It works with other players, but all the other players that I use go through the pulse mixer, and JRiver works fine too when pulse is in the middle. I don't have another player on hand that uses an ALSA direct type music connection like JRiver does. That's a good avenue for investigation though, I'll poke around and see if maybe I can find a Linux music player that will talk directly at the ALSA layer and see if it has the same issue.
JimH:
Can you ask Steinberg if they know of a player that works?
bob:
Try running /usr/lib/jriver/Media\ Center\ 28/alsacap and posting the results here.
Navigation
[0] Message Index
[#] Next page
Go to full version