Print

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

[budge]

Hi All,

I managed to install jriver but am getting "no devices found" upon start up. I can play audio via the DAC using vlc, amarok, clementine etc.

Works fine in Windows (Dual boot)

JRiver does not appear in pavucontrol.

I'm at a loss. I'm not a Linux newbie, but I don't compile my own kernel either...

Would like to get this working.

Thanks,
Budge.
(Don't think I've ever posted for help in a forum, please be gentle :-) )

[Awesome Donkey]

Is the DAC even plugged in? If I had to guess, I'd say in all likelihood the issue is in the USB cable used.

[mwillems]

Hi All,

I managed to install jriver but am getting "no devices found" upon start up. I can play audio via the DAC using vlc, amarok, clementine etc.

Is the "no devices found" message you're referring to in the terminal?  If so that's not referring to audio devices.  If you go to tools-->options-->Audio-->devices what do you see?  You should see a big bunch of alsa devices and a pulseaudio device.  Try the pulse device just to confirm its working.  The device you actually want to use is one of the one's labelled "front:" as those are hardware direct devices.  If you see no devices there something else is wrong, probably a permissions problem.

You won't see JRiver in pavucontrol as I don't think JRiver registers with the sound server, which has pluses and minuses

[budge]

Thanks for the replies.

The DAC is plugged in. That is how I listen to vlc, amarok, clementine etc and I installed jriver in Windows to check and the same configuration works fine.

Are you saying that the USB cable might not work with jriver when it works in those other cases? I wouldn't have thought that would be the case.

It is the "Found 0 devices" message in the terminal. I thought I would start it from the terminal to see any messages. And I think I saw something about that not being related, so thanks for confirming that.

So when I try and play something, a dialog pops up saying Something went wrong with playback. Details: Playback could not be started on the output 'ALSA' using the format '44.1 kHz 2ch' and mentions using DSP studio.

I have tried different selections from the drop down list in Tools -> Options -> Audio Device. Tried deafult[ALSA] pulse[ALSA] front:card=DAC,DEV=0 [ALSA] and sysdefault:CARD=DAC [ALSA] and all give the same result.

Thanks.

[mwillems]

Thanks for the replies.

The DAC is plugged in. That is how I listen to vlc, amarok, clementine etc and I installed jriver in Windows to check and the same configuration works fine.

Are you saying that the USB cable might not work with jriver when it works in those other cases? I wouldn't have thought that would be the case.

It is the "Found 0 devices" message in the terminal. I thought I would start it from the terminal to see any messages. And I think I saw something about that not being related, so thanks for confirming that.

So when I try and play something, a dialog pops up saying Something went wrong with playback. Details: Playback could not be started on the output 'ALSA' using the format '44.1 kHz 2ch' and mentions using DSP studio.

I have tried different selections from the drop down list in Tools -> Options -> Audio Device. Tried deafult[ALSA] pulse[ALSA] front:card=DAC,DEV=0 [ALSA] and sysdefault:CARD=DAC [ALSA] and all give the same result.

Thanks.

So I've got an idea of what's happening. Pulse audio locks the sample rate of any device it's using to 48KHz by default.   However, 99% of recorded digital music is 44Khz.

So JRiver is trying and failing to playback 44KHz music on a device locked to 48KHz.   Most players don't try to faithfully preserve the sample rate, they just hand it off Pulse and hope for the best.  So you have two options: either set JRiver's DSP studio to resample everything to 48KHz (which is what pulse is doing for other players anyway), or set pulse to a different device than your DAC (i.e. the internal soundcard) so that JRiver can have unfettered control of the hardware.  In that case the front device should be the correct one.

I went through this myself: on most of my systems setting the output to the "pulse" output works normally without further fiddling, but on one of my systems I had your issue and I had to set up resampling (or move pulse off of the device).

[budge]

I upgraded to version 22 (was 20 before) and can get audio from the built in ports on the PC but not via the DAC.

or set pulse to a different device than your DAC (i.e. the internal soundcard) so that JRiver can have unfettered control of the hardware.  In that case the front device should be the correct one.

Sorry but I don't know how to set pulse to a different device other than the DAC.

Hmmm, I'm kind of not sure if I should worry about this when I have been fine with open source stuff. A colleague said he used it so I thought I would check it out, but not sure if it's worth the effort let alone the cost of the license. I will try for a bit longer...

[mwillems]

I upgraded to version 22 (was 20 before) and can get audio from the built in ports on the PC but not via the DAC.

Sorry but I don't know how to set pulse to a different device other than the DAC.

Hmmm, I'm kind of not sure if I should worry about this when I have been fine with open source stuff. A colleague said he used it so I thought I would check it out, but not sure if it's worth the effort let alone the cost of the license. I will try for a bit longer...

MC has a lot of features not available in open source alternatives.  Not just a couple either.  But I know what you mean it's a bit of a learning curve at the start, and MC for linux isn't quite as polished as the windows version yet.  MC20 was the first really usable Linux version (they offered a beta in 19), but lacked a lot of features; if you started there I'm not surprised you had trouble (that was more than two years of development ago); MC 22 is a much better experience.  To be clear, I'm not a dev, I'm just a user like you.

If you open up pavucontrol (or the gnome audio menu), pulse outputs to a specific device by default (like the device your browser sound plays out of).  That's the device Pulse is holding onto; you can set pulse to default to a different device.  Or you can just set MC to resample everything (which is what's happening behind the scenes with the other players anyway). 

Now that you've moved up to MC22, you should try the front: outputs again too, that may just work.

Hope this helps.

[budge]

OK so I finally got it working, thanks for your support mwillems!!

Here is how I got it work in the end if anyone else has this problem - well this is what did it for me anyway...

Statrted playing a song in jriver just set to default ALSA so the internal audio was being used.

Opened up Volume Control (pavucontrol) and when a song was playing on Clementine, selected the output to be Built in Stereo from the drop down list. When I did this an "ALSA plug-in [mediacenter22]: ALSA Playback on: (drop down box)" appeared. I selected FiiO USB Audio DAC from the list and boom!! We have sound playing from jriver through the DAC. Woohoo!!

Now to start using it in anger and also seeing how it goes on a Raspberry Pi.

Cheers!