INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Linux => Topic started by: bob on May 15, 2015, 04:32:37 pm
-
https://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.129-armhf.deb (also in the latest MC apt repository)
This build requires a linux or master license.
It does not have a permanent timeout.
See the announcement for the generic i386 build for non-arm specific changes.
Only arm specific issues should be posted in this thread.
20.0.129 (7/16/2015)
1. Fixed: The focus fix from 20.0.123 was incomplete and was preventing the DSP studio (amongst others) from showing properly on hover.
2. Changed: All MC windows are class hinted properly now.
20.0.123 (6/25/2015)
1. Changed: Updates from the main branch.
-
Updated :)
Did it all via ssh on the iPhone. Nice and simple with the new APT repository!
Used VNC on the iPhone to login and check and all looks great. Thanks guys another new milestone for JRiver. :)
And did the command line registration too. Nice.
-
Updated :)
Did it all via ssh on the iPhone. Nice and simple with the new APT repository!
Used VNC on the iPhone to login and check and all looks great. Thanks guys another new milestone for JRiver. :)
And did the command line registration too. Nice.
Thanks for the feedback!
-
Yep, all went great here too. Everything's up and running all licenses happily installed on Raspbian, Raspbian Jessie, and Arch.
BTW, is xfonts-unifonts a hard requirement for the ARM build now too? I saw it was for the AMD build, but I want to make sure my RPi tutorial is still accurate.
-
BTW, is xfonts-unifonts a hard requirement for the ARM build now too? I saw it was for the AMD build, but I want to make sure my RPi tutorial is still accurate.
Yes it is.
The only reason it's not in the generic i386 build is that the depends: for fonts doesn't work properly on multiarch machines.
-
Yes it is.
The only reason it's not in the generic i386 build is that the depends: for fonts doesn't work properly on multiarch machines.
Thanks for confirmation, I added it to the dep list.
-
Like many posting on various forums, I've never been able to get the HDMI to work on my BeagleBone Black. So I've been running MPD headlessly and controlling it with MPoD. I want to put MC on my 'bone, but I need a way to set it up and control it from my iPhone &/or Androids since I have no video output. Will JRemote work with an ARM instance of MC?
-
Like many posting on various forums, I've never been able to get the HDMI to work on my BeagleBone Black. So I've been running MPD headlessly and controlling it with MPoD. I want to put MC on my 'bone, but I need a way to set it up and control it from my iPhone &/or Androids since I have no video output. Will JRemote work with an ARM instance of MC?
I can't comment on a Beagle Bone, but I'm controlling a Raspberry Pi 2 running JRiver with JRemote as we speak. Works a treat.
-
I can't comment on a Beagle Bone, but I'm controlling a Raspberry Pi 2 running JRiver with JRemote as we speak. Works a treat.
Good enough for me! I'll invest $10 to find out and report back. Keep your wires crossed.......(http://www.en.kolobok.us/smiles/artists/mother_goose/MG_64.gif)
-
Good enough for me! I'll invest $10 to find out and report back. Keep your wires crossed.......(http://www.en.kolobok.us/smiles/artists/mother_goose/MG_64.gif)
Try it with Gizmo first for free. If Gizmo works, there's a 99% chance JRemote will.
-
Gents,
I have issue with my registration, MC keeps pops up window said "The trail period has expired".
I did both restore methods via same window by entering the serial number and also via terminal "MediaCenter20 /RestoreFromFile "MediaCenter20_Linux-xxxxxx.mjr". By window it was ok but whenever I restart mc or reboot, the same trail expired window pops up again. The way it goes, I soon will run out my restoration allowance. :(
Can any one of you please help?
Chanh
-
Gents,
I have issue with my registration, MC keeps pops up window said "The trail period has expired".
I did both restore methods via same window by entering the serial number and also via terminal "MediaCenter20 /RestoreFromFile "MediaCenter20_Linux-xxxxxx.mjr". By window it was ok but whenever I restart mc or reboot, the same trail expired window pops up again. The way it goes, I soon will run out my restoration allowance. :(
Can any one of you please help?
Chanh
Sound like a permissions or ownership issue for the Settings files.
Check ~/.jriver/Media\ Center\ 20/Settings
-
Bob - can you pls elaborate further? Do I do this via terminal or GUI? If via Terminal, I need a clearer folder path or instructions on how to get there, please!
Many thanks
-
Sound like a permissions or ownership issue for the Settings files.
Check ~/.jriver/Media Center 20/Settings
I got into the folder and see two files.
Machine Settings.ini
User Settings.ini
Nano into each file but have no idea what must be amended.
-
Try it with Gizmo first for free. If Gizmo works, there's a 99% chance JRemote will.
First, I have to get it running. I was able to install MC on my 'bone after only two tries - I had some dependency problems that were corrected with sudo apt-get install -f. But my master license file doesn't seem to be in the right place because I can't get it recognized from the command line using mediacenter20 /RestoreFromFile ~/Downloads/"Media Center20 Linux-YYYYYY.mjr" . I'll go back in tonight and make sure the mjr file is in the right folder, then try again. Assuming it works, I'll drop the ip address into Gizmo and give it a go. Thanks!
-
Hello,
I've been using JRiver on windows for a while now but just got it running on the RPi - simply amazing.
I have a couple of small bugs, I think:
1. JRemote seems unable to restart or shutdown the RPi - if that would work it'll make it much more convenient as I'm sure most people are running headless.
2. I get occasional 'hick-ups' where the music would cut out for a second or so - this corresponds to a spike on the CPU performance meter... I couldn't find a specific situation where this is happening but seems more often with Hi-rez music. My RPI is connected with Ethernet to the music server and I never had network issues running the windows machine in exactly the same network setup.
Lastly,
Is JRiver 20 on RPi exactly like the windows version in terms of DSP and digital volume etc?
Thanks, keep up the great work!
-
I have issue with my registration, MC keeps pops up window said "The trail period has expired".
Did fresh install to my Banana Pro, reinstalled Bananian and JRiver from scratch has solved the issue. Working great now!
-
Hello,
I've been using JRiver on windows for a while now but just got it running on the RPi - simply amazing.
I have a couple of small bugs, I think:
1. JRemote seems unable to restart or shutdown the RPi - if that would work it'll make it much more convenient as I'm sure most people are running headless.
I don't speak for JRiver (I'm just a user), and bob can weigh in on this, but my guess would be that that's unlikely to happen in the short term because a shutdown or reboot in linux typically requires elevated privileges (i.e. sudo), which requires authentication. The various desktop environments all have a shutdown button that does not require authentication, but they do that using dark magic involving consolekit or logind/polkit. And each desktop environment handles that magic a little differently, and consolekit vs. logind/polkit work differently, etc.
So I would expect, based on my admittedly limited knowledge, that writing a shutdown script that didn't require elevated privileges would require writing at least two, or three, or four different approaches and trying to detect on the fly which of them would work on a given user's system, and it would, inevitably, not work on some systems.
2. I get occasional 'hick-ups' where the music would cut out for a second or so - this corresponds to a spike on the CPU performance meter... I couldn't find a specific situation where this is happening but seems more often with Hi-rez music. My RPI is connected with Ethernet to the music server and I never had network issues running the windows machine in exactly the same network setup.
If you're seeing a CPU spike and it only happens with hi rez material, it's not likely a network issue, more likely that you're testing the limits of your RPi. Are you using a Pi1 or a Pi2? If you're using a Pi 1 that's to be expected, it will play normal res material fine, but will likely struggle a bit with higer res. If you're using the Pi 2, you shouldn't have issues with native playback of hi res material. Check out this post for some CPU usage comparison graphs: http://yabb.jriver.com/interact/index.php?topic=97100.0
But even the Pi 2 has limits (the cpu is more powerful than a Pi 1, but still a ways behind a regular computer), so if you're trying to upsample on the fly, that might not work. Have you tried overclocking the Pi to see if the issue goes away (obviously only try it if you're comfortable with it, and I wouldn't recommend exceeding the "recommended" overclock settings)?
Lastly,
Is JRiver 20 on RPi exactly like the windows version in terms of DSP and digital volume etc?
Thanks, keep up the great work!
Not sure about this one; I haven't identified any differences yet, but there may be some. I'll let Bob weigh in.
-
Thanks for the feedback mate!
I'm using the RPi2b and during normal playback CPU usage is around 25%.
I'd like to clarify that I'm having these occasional pauses with Redbook material too, often after I'd start a new song or skip to the next (via JRemote on iPhone 6) it would start playing a few seconds than a pause...
-
Good enough for me! I'll invest $10 to find out and report back. Keep your wires crossed.......(http://www.en.kolobok.us/smiles/artists/mother_goose/MG_64.gif)
MC's making good music on the Beaglebone - I finally resorted to TightVNC, and it was a breeze once I had a GUI. So I dropped the big dime and bought JRemote - it's very nice and easy to use, although it doesn't blow the Gizmos away. I don't see an option to stream to my iPhone, though. And when I try to play a track on my phone using WebGizmo, I get a message that the file can't be found, even though it opens and plays fine through the USB out of the BBB. Does the ARM MC stream to a remote device through JRemote like the other platforms do?
-
ARM should work the same way that other Linux distro's do.
-
ARM should work the same way that other Linux distro's do.
It does - I just found the zone settings when sliding the "now playing" line at the bottom of the JRemote screen to the right. Yes, it was an accident. But all is right with the world.
-
I'd like to clarify that I'm having these occasional pauses with Redbook material too, often after I'd start a new song or skip to the next (via JRemote on iPhone 6) it would start playing a few seconds than a pause...
What playback device do you use?
I've similar behavior, got redbook material working OK now by setting the CPU scaling Governor off.
Simplest way to do this is adding force_turbo=1 to your /boot/config.txt
Be aware the PI is running on the max frequency settings all time;
others have to jump in for more elegant solutions
-
Bob is out of the office until tomorrow.
There are other threads about licensing on this board. You can enter it from the command line if necessary.
-
What playback device do you use?
I've similar behavior, got redbook material working OK now by setting the CPU scaling Governor off.
Simplest way to do this is adding force_turbo=1 to your /boot/config.txt
Be aware the PI is running on the max frequency settings all time;
others have to jump in for more elegant solutions
Thanks Mate,
I'm using a Chord Hugo - so I assume the problem isn't there. I'll try your idea - thanks Mate!
-
What playback device do you use?
I've similar behavior, got redbook material working OK now by setting the CPU scaling Governor off.
Simplest way to do this is adding force_turbo=1 to your /boot/config.txt
Be aware the PI is running on the max frequency settings all time;
others have to jump in for more elegant solutions
FYI, using the force_turbo flag is not a great idea, especially if you're overclocking. My understanding is that it not only disables CPU scaling, but also voltage/thermal throttling, and will void your warranty if used in combination with overclocking because it gives the pi no way to get rid of excess heat.
If your issue is the performance lag from the default "ondemand" governor, the safe way to handle that with or without overclocking is to set the CPU governor to "performance" which will set the frequency to maximum, but does not disable thermal throttling. I'm not in front of a pi so I can't post the exact command, but you should be able to do it with the cpufreq-set command. You'll probably need to install cpufrequtils first.
I haven't personally had dropouts with the standard governor on my Pi 2's, but I could see how that might be an issue with latency-sensitive equipment.
See here (both article and comments) for more info about the warranty issue: https://www.raspberrypi.org/introducing-turbo-mode-up-to-50-more-performance-for-free/
-
FYI, using the force_turbo flag is not a great idea, especially if you're overclocking. My understanding is that it not only disables CPU scaling, but also voltage/thermal throttling, and will void your warranty if used in combination with overclocking because it gives the pi no way to get rid of excess heat.
If your issue is the performance lag from the default "ondemand" governor, the safe way to handle that with or without overclocking is to set the CPU governor to "performance" which will set the frequency to maximum, but does not disable thermal throttling. I'm not in front of a pi so I can't post the exact command, but you should be able to do it with the cpufreq-set command.
I haven't personally had dropouts with the standard governor on my Pi 2's, but I could see how that might be an issue with latency-sensitive equipment.
See here (both article and comments) for more info: https://www.raspberrypi.org/introducing-turbo-mode-up-to-50-more-performance-for-free/
Thanks, I'll try it too - I'm not overlocking at the moment.
-
FYI, using the force_turbo flag is not a great idea, especially if you're overclocking. My understanding is that it not only disables CPU scaling, but also voltage/thermal throttling, and will void your warranty if used in combination with overclocking because it gives the pi no way to get rid of excess heat.
thanx, never understood why it is a bad idea
If your issue is the performance lag from the default "ondemand" governor, the safe way to handle that with or without overclocking is to set the CPU governor to "performance" which will set the frequency to maximum, but does not disable thermal throttling. I'm not in front of a pi so I can't post the exact command, but you should be able to do it with the cpufreq-set command. You'll probably need to install cpufrequtils first.
for each core (cpu0, cpu1, cpu2, cpu3)
echo -n performance | tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
got this form: http://wiki.linuxaudio.org/wiki/raspberrypi
See reply below
I haven't personally had dropouts with the standard governor on my Pi 2's, but I could see how that might be an issue with latency-sensitive equipment.
Still looking for a success story with an (USB) UAC2 device, RPI/MC/UAC2 doesn't seem to be a good marriage.
I'll guess it is quite latency-sensitive because its running or standstill.
-
I would recommend against making any kernel setting changes that you don't understand, and setting swappiness to 0 is potentially a bad idea depending on how you use memory. A lot of the advice on that page will lead to instability or poor results.
The cpu frequency command offered there is correct as far as it goes, but will not survive a reboot and isn't particularly elegant.
The way I would suggest instead is to use cpufrequtils (which is how you do it in normal linux). First install cpufrequtils
sudo apt-get install cpufrequtils
Then try entering
for n in {0..3}; do sudo cpufreq-set -c $n -g performance; done
If you want to confirm whether the command succeeded enter the "cpufreq-info" command.
If you want to have the governor settings survive reboots, add the "for..." line to your rc.local (removing the sudo), or you can run it as a script (also removing the sudo) on reboot using cron (in root's crontab). I'm going to add some info on this to my quick start guide at some point.
-
Thanks Mate,
I'm using a Chord Hugo - so I assume the problem isn't there. I'll try your idea - thanks Mate!
Unfortunately manufacturers are not very clear of which Usb Audio Class their device is, probably because Windows lacks native support of UAC2. The Cord Hugo isn’t an exception, the specs say HD-USB audio. As it is capable of 32 bit audio and need a windows driver chances are big it is an UAC2 device.
JRiver confirmed they haven’t got a UAC2 device that works with the PI:
http://yabb.jriver.com/interact/index.php?topic=96616.0
For all readers: Sorry to be persistent on this subject, I'm just an enthusiastic MC user trying to get his setup working.
Although hesitating to bring half-baked info, reads on the subject:
http://www.thewelltemperedcomputer.com/KB/USB.html
and (JUST FOR READING , never use a script/command if you don’t know what your doing)
http://lacocina.nl/
-
Unfortunately manufactures are not very clear of witch Usb Audio Class they’re device is, probably because Windows lacks native support of UAC2. The Cord Hugo isn’t an expectation, the specs say HD-USB audio. As it is capable of 32 bit audio and need a windows driver chances are big it is an UAC2 device.
JRiver confirmed they haven’t got a UAC2 device that works:
http://yabb.jriver.com/interact/index.php?topic=96616.0
For all readers: Sorry to be persistent on this subject, I'm just an enthusiastic MC user trying to get his setup working.
Although hesitating to bring half-backed info, reads on the subject:
http://www.thewelltemperedcomputer.com/KB/USB.html
and (JUST FOR READING , never use a script/command if you don’t know what your doing)
http://lacocina.nl/
Thanks Mate,
This is why I'm using Optical toslink to connect the Pi and DAC...
-
I don't work at JRiver, but needing a windows driver isn't a good proxy for UAC2 compliance. I've had no problems with four or five different USB DACs with the Pi using a variety of sample rates, including some that needed windows drivers.
You don't necessarily need UAC2 to get high sample rate output with the Pi, so I'm not sure what the advantage is? An Asus U7 allows high sample-rate playback, and requires a bit of fiddling, but (eventually) works with the Pi. The U7 requires a driver in windows, but isn't (to my knowledge) UAC2 compliant. The fiio e17 or ODAC don't need windows drivers (so are probably UAC1 compliant), but both work without dropouts at 96KHz with the Pi.
Mark_NL, does your DAC work correctly with a normal linux install on an x86 computer? You've mentioned before that it's in the newer ALSA builds, but have you tested your specific DAC (the one you're holding in your hands) to make sure the USB interface works with a normal linux computer? If you haven't investigated those avenues you may be barking up the wrong tree.
-
I don't work at JRiver, but needing a windows driver isn't a good proxy for UAC2 compliance. I've had no problems with four or five different USB DACs with the Pi using a variety of sample rates, including some that needed windows drivers.
You don't necessarily need UAC2 to get high sample rate output with the Pi, so I'm not sure what the advantage is? A fiio e17 or ODAC, for example, work at 96KHz with the Pi, they just don't happen to be UAC2 compliant DACs. An Asus U7 requires a bit of fiddling, but also works with the Pi but that card requires a driver in windows, and isn't (to my knowledge) UAC2 compliant.
Yes you are right and I know, therefor big chance. It's darn hard to determine the exact nature of a USB audio divice. I've looked at the specs of all the DAC's reported to work (including yours, wasn't sure about the e17...) none was without any doubt UAC2. There is a DD_DAC reported working: There are two type's the NOS 1794 often comes with a UAC2 to i2s interface but again not always. Can't find the post but he used an Banana PI, which (as far my knowledge goes) it has a more mature USB implementation.
Mark_NL, does your DAC work with a normal linux install on an x86 computer? You've mentioned before that it's in the newer ALSA builds, but have you tested your specific DAC with a normal linux computer? If you haven't investigated those avenues you may be barking up the wrong tree.
Yes, specially made a laptop dual boot MS Windows/Debian. Dac works like a charm!
Furthermore in one Raspbian setup (SD card) installed VLC beside MC - VLC using the same alsa settings playing without a glitch.
Till now i don't know if it is barking on the right tree: is it specific for this USB implementation+PI2+MC? Or is MC + UAC2 just to much for the lovely PI2?
So let's keep it in the middle, it hasn't been proven PRI+UAC2+MC works.
OT - really appreciate your informative posts
-
First, I have to get it running. I was able to install MC on my 'bone after only two tries - I had some dependency problems that were corrected with sudo apt-get install -f. But my master license file doesn't seem to be in the right place because I can't get it recognized from the command line using mediacenter20 /RestoreFromFile ~/Downloads/"Media Center20 Linux-YYYYYY.mjr" . I'll go back in tonight and make sure the mjr file is in the right folder, then try again. Assuming it works, I'll drop the ip address into Gizmo and give it a go. Thanks!
Use the full path to the license file, don't use a tilde.
-
Yes, specially made a laptop dual boot MS Windows/Debian. Dac works like a charm!
Furthermore in one Raspbian setup (SD card) installed VLC beside MC - VLC using the same alsa settings playing without a glitch.
Till now i don't know if it is barking on the right tree: is it specific for this USB implementation+PI2+MC? Or is MC + UAC2 just to much for the lovely PI2?
Are you seeing issues with Redbook files? If so, then VLC is a good point of comparison. For high res, however VLC generally just outputs to the system default output (usually pulse) which resamples everything to the system sample rate (typically 48KHz), so it's not really a good point of comparison for hi res files. You may be playing a 192KHz file, but with VLC the system is quietly downsampling it to 48K before it ever hits the USB bus.
Let's get back to basics, have you tried choosing different ALSA outputs for your DAC in JRiver? Specifically have you tried the hardware outputs (the ones with names starting with "front:")?
Just for testing, have you tried using the system default in JRiver? Does that work the same as VLC, or does that not work either? That's not a desirable long-term solution, but will tell us something if it works.
Do you have other USB peripherals plugged in? Have you tried moving all peripherals to a powered USB hub?
So let's keep it in the middle, it hasn't been proven PRI+UAC2+MC works.
I certainly haven't been able to confirm or disconfirm, but that's more due to the scarcity of UAC2 DACs than anything. I would be very surprised if UAC2 DACs as a group did not work with MC and the Pi.
OT - really appreciate your informative posts
My pleasure, I hope we get you sorted ;D
-
Are you seeing issues with Redbook files? If so, then VLC is a good point of comparison. For high res, however VLC generally just outputs to the system default output (usually pulse) which resamples everything to the system sample rate (typically 48KHz), so it's not really a good point of comparison for hi res files. You may be playing a 192KHz file, but with VLC the system is quietly downsampling it to 48K before it ever hits the USB bus.
Minnor issues with redbook but not flawless. Just payed 24/96 with VLC:
DIYINHK DIYINHK USB Audio 2.0 at usb-bcm2708_usb-1.4, high speed : USB Audio
Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 127
Momentary freq = 96013 Hz (0xc.0068)
Feedback Format = 16.16
Interface 1
Altset 1
Format: S32_LE
Channels: 2
Endpoint: 1 OUT (ASYNC)
Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000
Data packet interval: 125 us
BTW: I think "Feedback Format = 16.16" and "Data packet interval: 125 us" are indicators for dealing with a UAC 2 device, can you confirm??
Let's get back to basics, have you tried choosing different ALSA outputs for your DAC in JRiver? Specifically have you tried the hardware outputs (the ones with names starting with "front:")?
The hardware output "Front:CARD=D20 DEV=0 [ALSA]" works best thus this is the one i use.
Just for testing, have you tried using the system default in JRiver? Does that work the same as VLC, or does that not work either? That's not a desirable long-term solution, but will tell us something if it works.
In JRiver Sysdefault:CARD=D20 only plays material in the 48 kHz family Correction does not play 44,1 kHz and above 48 play's downsampled to 48 kHz. DSP seems to set this on the fly.
VLC samples verything to 48 kHz playing to ....USB.. DEFAULT AUDIO", playing 44.1 kHz:
pi@raspberrypi ~ $ cat /proc/asound/card0/stream0
DIYINHK DIYINHK USB Audio 2.0 at usb-bcm2708_usb-1.4, high speed : USB Audio
Playback:
Status: Running
Interface = 1
Altset = 1
Packet Size = 67
Momentary freq = 48007 Hz (0x6.0038)
Feedback Format = 16.16
Do you have other USB peripherals plugged in? Have you tried moving all peripherals to a powered USB hub?
Only the dac is plugged in. The USB receiver is partly powered by USB, the DAC it self (and some parts of the USB receiver) has separate power supplies.
-
Bob,
I have repeated issue with "trail period expired" windows pops up, again. This had happened before and after many unsuccessfully restore, I made fresh installation. It was working for few days, now the same registration issue appears. I only have three more restore left...!
How can I rectify this?
Many thanks.
-
Bob has been on vacation. He's returning tomorrow your time. l've cleared your restores, so don't worry about using them.
-
Bob has been on vacation. He's returning tomorrow your time. l've cleared your restores, so don't worry about using them.
Many thanks Jim. Really appreciate your supports! I wonder if I was single out from this weird "trail period expired" or there is a bug within 110-build? I upgraded from 20.0.91 to 20.0.110.
Btw, I use Banana Pro as all in one server with Built-in wifi as AP. JRiver is playing to my BeagleBone Black under UPnP protocol for I2S direct to my DAC via Miero Botic driver.
(http://images.tapatalk-cdn.com/15/05/28/774fa67b1f97b96d7394ea0836e314db.jpg)
(http://images.tapatalk-cdn.com/15/05/19/90243bf867398f042edc12b833ac2d09.jpg)
-
Many thanks Jim. Really appreciate your supports! I wonder if I was single out from this weird "trail period expired" or there is a bug within 110-build? I upgraded from 20.0.91 to 20.0.110.
I have several Pi's running 20.0.110 with no license issues, and so do several other folks, so it's not a general issue.
Given that your license seems to "take" but is then "forgotten" it sounds a lot like a filesystem permissions issue. If you need to restore the license whenever you reboot, it's definitely a permissions issue.
-
I have several Pi's running 20.0.110 with no license issues, and so do several other folks, so it's not a general issue.
Given that your license seems to "take" but is then "forgotten" it sounds a lot like a filesystem permissions issue. If you need to restore the license whenever you reboot, it's definitely a permissions issue.
so how to address this, do you know?
-
so how to address this, do you know?
Post the output of the following terminal commands:
ls -la ~/.jriver/Media\ Center\ 20
ls -la ~/.jriver/Media\ Center\ 20/Settings
-
Btw, I use Banana Pro as all in one server with Built-in wifi as AP. JRiver is playing to my BeagleBone Black under UPnP protocol for I2S direct to my DAC via Miero Botic driver.
Ahh, Found the DD-DAC!
Chanh have you ever tried to drive your dac with an USB to i2c converter using MC20-arm?
If so, was it a USB Audio Class 2 device?
-
Post the output of the following terminal commands:
ls -la ~/.jriver/Media\ Center\ 20
ls -la ~/.jriver/Media\ Center\ 20/Settings
Many thanks for this! Did the fresh installation again with JRiver 20.0.91, seems trouble free. Will do the upgrade tonight to 110 and if I face the same issue again, these command lines are coming in handy. Will report back soon.
Ahh, Found the DD-DAC!
Chanh have you ever tried to drive your dac with an USB to i2c converter using MC20-arm?
If so, was it a USB Audio Class 2 device?
Yes, I have been using JRiver-Arm from early day 20.0.66. Working flawlessly with USB DAC. I used it for Accuphase DC-37, driver pick up as ei9560 under audio option. As for DDDAC, I use WaveIO. Driver pickup as Luckit. No issue with USB driver to DAC. Only issue up and until 110 is the JRemote does not automatically sync/showing actual playing screen whenever new album or track is selected. Have to get out, press next or close JRemote altogether and reopen for the actual showing. This doesn't bother me as JRiver interface with JRemote are awesome! :)
-
I would recommend against making any kernel setting changes that you don't understand, and setting swappiness to 0 is potentially a bad idea depending on how you use memory. A lot of the advice on that page will lead to instability or poor results.
The cpu frequency command offered there is correct as far as it goes, but will not survive a reboot and isn't particularly elegant.
The way I would suggest instead is to use cpufrequtils (which is how you do it in normal linux). First install cpufrequtils
sudo apt-get install cpufrequtils
Then try entering
for n in {0..3}; do sudo cpufreq-set -c $n -g performance; done
If you want to confirm whether the command succeeded enter the "cpufreq-info" command.
If you want to have the governor settings survive reboots, add the "for..." line to your rc.local (removing the sudo), or you can run it as a script (also removing the sudo) on reboot using cron (in root's crontab). I'm going to add some info on this to my quick start guide at some point.
Hello again,
I tried these commands and they work (CPUFreq) but I can't get it to boot with those settings...
I created an rc.local file in my /home/pi directory but my pi doesn't play along... am I missing something?
Thanks!
-
Hello again,
I tried these commands and they work (CPUFreq) but I can't get it to boot with those settings...
I created an rc.local file in my /home/pi directory but my pi doesn't play along... am I missing something?
Thanks!
That won't work. Try this:
type touch /home/pi/governor.sh
chmod 755 /home/pi/governor.sh
nano /home/pi/governor.sh Then enter the following text in the file:#!/bin/bash
for n in {0..3}; do cpufreq-set -c $n -g performance; done
Save by pressing CTRL-X, y, and then enter twice.
Now type sudo nano /etc/rc.local
And add the following above the line that reads "exit 0" /home/pi/governor.shSave by pressing CTRL-X, y, and then enter twice.
Now it should survive reboots.
-
Sorry,
I'm a complete Noob,
When I follow your instructions and save the governor.sh file I get an error message (in Nano) saying 'Error writing home/pi/governor.sh: no such file or directory'...?
Thank you,
-
Sorry there's a typo in my instructions. There should be a slash "/" before home in the third line. I just fixed it.
-
Sorry there's a typo in my instructions. There should be a slash "/" before home in the third line. I just fixed it.
Perfect!
Works now - thanks so much!
Let's hope this solves the annoying pops in the sound...
-
Hello,
I've changed the CPU governor to performance and now it's running at 900Mhz constantly.
I'm Using an RPI 2 + HifiBerry digi+
Sadly it didn't stop the occasional (very annoying) audio cut-outs.
I've taken a few screenshots and you can see that for some reason MC spikes in CPU usage - this is when it happens. I always take these screen shots a few seconds in delay (while I log into the VNC app, etc) but take my word for it - MC spikes.
I also noticed what looks like a memory leak when I boot up fresh MC (and VNC the only other thing running on the RPi) takes about 250mb of memory but after a while it keeps growing and after two days without a reboot it get's to 600mb memory in use...
I'm not sure if it's connected but I'm worried that if I used room correction (once I get there) I'll run out of memory.
(http://i60.tinypic.com/2eal954.png)
(http://i57.tinypic.com/255584m.png)
I hope it helps,
Please share your thoughts,
Thank you
-
A few thoughts:
1) You're not trying to use playback from memory are you? If so, turn it off, it's not a good idea on the Pi
2) I notice that your Pi's toolbar has several hardware monitoring widgets not enabled on a default NOOBS install. I mention them because another user (with a regular computer, not a pi) recently had intermittent dropouts that were actually caused by system monitoring graph software: http://yabb.jriver.com/interact/index.php?topic=97571.msg676633#msg676633. Generally speaking, when troubleshooting it's a good idea to disable anything extraneous that you can.
3) Have you tried playing with the buffering settings in options-->audio?
On the memory issue I haven't been able to get MC to eat up more than about 350 MB of RAM. Any particular steps you have to take to make that happen? I have a few pis running 24/7 and have seen no such memory increases. If you can reproduce the 600MB usage, could you post the output of the command "free -h" in a terminal?
In the meanwhile you could just setup a cronjob to restart JRiver every night, but that's suboptimal.
-
Hello Again,
I still have this problem - occasional pauses in playback, I've now realized there are also occasional 'pops' - which are disturbing because I'm going direct to power-amp - using JRiver to substantially attenuate the volume but a full volume 'pop' can probably ruin my speakers...
I set the CPU governor to performance mode and closed every other utility or program running on my pi... I also tried playing with the pre-buffering settings in JRiver - but 'no cigar'.
Any ideas are welcome,
Thank you
-
Any ideas are welcome,
Thank you
Some other thought's:
Set the output format (just above the Buffer time setting) to 24 bit, the digi + isn't capable of more anyway. (The linux guy’s say more is better and adding zero’s don’t matter, I disagree)
If you use vnc connection a lot you could try it without the spectrum analyzer to keep network traffic down (left click on it) not sure of this has a big impact.
(btw tested the digi+ with the initial release of MC a had no problems at all. Hooked it up to a naim naid of a friend , if there where click's we should have heard them)
-
Thanks Guys,
I've tried everything and I still have these pauses and clicks... I think I'm really risking my speakers.
Not sure what to do other than reinstall everything from scratch?
Your ideas are welcome - thanks!
BTW
After about 14 hours of playing non stop, my JRiver is now using 453Mb of memory,
Here is the 'free -h' output bellow:
pi@raspberrypi ~ $ free -h
total used free shared buffers cached
Mem: 927M 792M 134M 0B 57M 216M
-/+ buffers/cache: 518M 408M
-
Do the clicks or pauses occur during song playback or between songs? If between songs, do they happen only or more often when changing sample rate (i.e. switching from a redbook track to a 24/96 track)?
Are you streaming the files over a network or playing from an external harddrive? IF so, just to test, try putting a file or two on the sd card and see if you get the same problems.
-
Do the clicks or pauses occur during song playback or between songs? If between songs, do they happen only or more often when changing sample rate (i.e. switching from a redbook track to a 24/96 track)?
Are you streaming the files over a network or playing from an external harddrive? IF so, just to test, try putting a file or two on the sd card and see if you get the same problems.
Thanks McWilliams -
The pauses happen during playback, sometime when switching songs (as well as changing sample rates) but often while playback is playing and with no provocation on my part...
I am streaming but I'll try to see if local playback has the same issue.
thank you
-
Thanks McWilliams -
The pauses happen during playback, sometime when switching songs (as well as changing sample rates) but often while playback is playing and with no provocation on my part...
You mention pauses, but what about the pops/clicks? The reason I ask is that some DACs give out a loud "pop" or click when changing sample rates. If you're getting the pops in the middle of songs, that rules out that issue, but if you only get them between tracks or when changing sample rates, it may be a "feature" of your DAC.
-
You mention pauses, but what about the pops/clicks? The reason I ask is that some DACs give out a loud "pop" or click when changing sample rates. If you're getting the pops in the middle of songs, that rules out that issue, but if you only get them between tracks or when changing sample rates, it may be a "feature" of your DAC.
it does both (occasionally) so sometimes art the start of songs (with changing sampling rate) and sometime in the middle of playback, often the click comes at the end of a tiny 'pause'.
I use the 'play silence at start up for hardware sync' - set at 2 seconds - but I still get the clicks/pauses - occasionally.
-
I read somewhere that the original audio circuit of the RPI can sometime engage and shutdown and it results in an audible pop sound.
Is there a way for me to shut it down or disable it (as I'm using the optical out of the Digi+?
I'm trying to find solution...
-
Hello,
I think I made some progress, I noticed that most of the pauses/clicks/pops happen immediately after I do something via JRemote on my iPhone 6 - things like spiking a song, or adjusted the volume.
Does this help? Can this have something to do with the way JRemote is implemented in the RPI version? or something with the network?
Any ideas are welcome, the pauses are annoying but the pops are really loud and I'm concerned can damage my speakers...
Thanks!
-
Is there a way for me to shut it down or disable it (as I'm using the optical out of the Digi+?
I'm trying to find solution...
This is worth a try;
before you do this you have to remove the volume control item form the task bar:
VNC into the PI and right click on the taskbar > add/remove panel items and remove volume control (alsa).
After removing the on board sound there is (in your configuration) no alsa mixer (volume control) available and i’ve experienced weird behavior in the past.
then in a terminal:
sudo nano /etc/modules
mark-out the onboard sounddriver so it looks like this:
#snd-bcm2835
(ctrl x, y, enter)
reboot your pi, and test
-
This is worth a try;
before you do this you have to remove the volume control item form the task bar:
VNC into the PI and right click on the taskbar > add/remove panel items and remove volume control (alsa).
After removing the on board sound there is (in your configuration) no alsa mixer (volume control) available and i’ve experienced weird behavior in the past.
then in a terminal:
sudo nano /etc/modules
mark-out the onboard sounddriver so it looks like this:
#snd-bcm2835
(ctrl x, y, enter)
reboot your pi, and test
Thanks Mate,
Much appreciated!
I did it, let's see how it works.
Thank you again
-
Hello,
I think I made some progress, I noticed that most of the pauses/clicks/pops happen immediately after I do something via JRemote on my iPhone 6 - things like spiking a song, or adjusted the volume.
Does this help? Can this have something to do with the way JRemote is implemented in the RPI version? or something with the network?
Any ideas are welcome, the pauses are annoying but the pops are really loud and I'm concerned can damage my speakers...
Thanks!
Another thing you could try.
From a terminal window as a user that can access the audio device (or root) run
/usr/lib/jriver/Media\ Center\ 20/alsacap
and see what sample formats your device supports. (i.e. S16_LE, S32_LE, etc).
In Mediacenter's audio options look at the Device Settings and change the output format from Auto to one of the fixed formats.
-
Another thing you could try.
From a terminal window as a user that can access the audio device (or root) run
/usr/lib/jriver/Media\ Center\ 20/alsacap
and see what sample formats your device supports. (i.e. S16_LE, S32_LE, etc).
In Mediacenter's audio options look at the Device Settings and change the output format from Auto to one of the fixed formats.
Thanks Bob,
Can I ask you to write the exact command? I'm quite a Noob, when trying to execute this I get no where...
Thank you!
-
Thanks Bob,
Can I ask you to write the exact command? I'm quite a Noob, when trying to execute this I get no where...
Thank you!
Hi, that is the exact command.
If you copy and paste it into a terminal window you should get a response.
-
:-[ Thanks mate,
now it works
I got this:
S16_LE, S32_LE
So which setting should I use in JRiver?
Thanks for the help,
-
Either should work.
-
Either should work.
Thanks mate, where exactly should I set them in JRiver? Also what does LE means?
-
In the Audio settings.
-
Thanks Jim.
I may have isolated the bloody pops/clicks - it was the wifi dongle - I removed it and got back to good old Ethernet cable and no pops - still a few pauses but very rarely...
To who, it may be useful...
-
Thanks Jim.
I may have isolated the bloody pops/clicks - it was the wifi dongle - I removed it and got back to good old Ethernet cable and no pops - still a few pauses but very rarely...
To who, it may be useful...
Wifi requires more processing power (the encryption is done in software).
That combined with the issue someone brought up earlier that all of the interrupts on the pi2 go through the first core probably explains your results.
-
Guys,
I'm sorry to report that I still get these bloody Pops/clicks...
They are very loud and I'm worried for my speaker thought they seem to survive so far.
Switching to wired Ethernet from Wifi helped reduce them a lot but I'm still getting them... I'm running out of ideas...
-
Try another sound device as a test.
-
Try another sound device as a test.
Thank you,
You mean a different DAC?
I also notice often these pops would happen when the player changes to a new song with a different sample rate. I have the option of playing silence when switching formats in JRiver on but it doesn't help the pops. I would hear a pop and then the 'silence' bit.
Not sure if that's a clue or not...?
-
If you're hearing the pops when the sample rate changes it is probably a problem with your DAC. Some DACs always make pops when changing sample rates, if that's when you hear them it's a hardware issue that JRiver cannot fix (it's a relay switching).
-
Although I don't run Linux, I found that using "Gapped Fade" under Audio Options/Track Change reduces pops with my USB DACs, not sure if that option is in the Linux version of MC, worth a try.
-
If you're hearing the pops when the sample rate changes it is probably a problem with your DAC. Some DACs always make pops when changing sample rates, if that's when you hear them it's a hardware issue that JRiver cannot fix (it's a relay switching).
Thanks Mate,
I know how relay switching sounds (like a physical click inside the DAC) - what I'm talking about is a loud pop sounds form the speakers at full volume...
I'll keep trying to isolate it...
-
Thanks Mate,
I know how relay switching sounds (like a physical click inside the DAC) - what I'm talking about is a loud pop sounds form the speakers at full volume...
I'll keep trying to isolate it...
That's what I'm talking about. The relay switch in many DACs causes a loud pop to come out of the speakers when sample rates switch.
-
That's what I'm talking about. The relay switch in many DACs causes a loud pop to come out of the speakers when sample rates switch.
However in 99 percent of the cases when I'm playing music that changes sample rates it doesn't do a loud pop... And to complicate it further it sometime pops while playing a song so it's not a sample rate change... ;-(
-
However in 99 percent of the cases when I'm playing music that changes sample rates it doesn't do a loud pop... And to complicate it further it sometime pops while playing a song so it's not a sample rate change... ;-(
You didn't say if you tried the fixed format output instead of Auto.
The other difference between MC and other programs is that it doesn't use the linux resampler. You could set DSP studio to resample everything to a specific rate to see if that changes anything.
Also, set the track transition to gapless and turn off the eliminate silence switch.
Other that that, I'm not sure where else we can go with this. MC uses a very simple interface to the sound device so it's not likely that changes in MC will affect this, especially since it doesn't seem to be present in other devices.
-
You didn't say if you tried the fixed format output instead of Auto.
The other difference between MC and other programs is that it doesn't use the linux resampler. You could set DSP studio to resample everything to a specific rate to see if that changes anything.
Also, set the track transition to gapless and turn off the eliminate silence switch.
Other that that, I'm not sure where else we can go with this. MC uses a very simple interface to the sound device so it's not likely that changes in MC will affect this, especially since it doesn't seem to be present in other devices.
Thanks Mate,
I'll try these suggestions.
To be honest I suspect this is more of a Raspberry Pi issue rather than MC - you've all been very helpful and kind - thank you!
-
I've upgraded the Pi to the new branch Linux raspberrypi 4.0.5-v7+ #797.
All working great.
-
I've upgraded the Pi to the new branch Linux raspberrypi 4.0.5-v7+ #797.
All working great.
Thanks mate,
Sounds promising.
Can I ask you for the command(s) to use?
-
There's a lot of new drivers and some drivers haven't been brought across yet that were in the old branch on version 3 kernel.
Unless you know what you're doing, experiencing problems or are prepared to rebuild from scratch I'd stay on that current 3 branch for now. It should be fine but its still very new and there maybe undetected regressions(problems).
To upgrade to the latest stable use sudo apt-get update and then sudo apt-get upgrade
This will upgrade all installed software to the latest stable release and is less likely to have problems than changing to the latest branch.
If you really want to temp fate you can run sudo apt-get update and then sudo apt-get install rpi-update
This will install a firmware/kernel update tool which can be used to get onto the latest branch. It can break things, so do so in the full knowledge you may have to rebuild your Pi from scratch.
Finally... if your really really sure.. the command to upgrade to the latest branch is sudo rpi-update
You have been warned! :)
-
When successful you should get this output.
pi@raspberrypi ~ $ sudo rpi-update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 10185 100 10185 0 0 29302 0 --:--:-- --:--:-- --:--:-- 32333
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
#############################################################
WARNING: This update bumps to rpi-4.0.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=113753
##############################################################
Would you like to proceed? (y/N)
*** Downloading specific firmware revision (this will take a few minutes)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 168 0 168 0 0 111 0 --:--:-- 0:00:01 --:--:-- 139
100 46.7M 100 46.7M 0 0 37123 0 0:22:00 0:22:00 --:--:-- 203k
*** Updating firmware
*** Updating kernel modules
*** depmod 4.0.6+
*** depmod 4.0.6-v7+
*** Updating VideoCore libraries
*** Using HardFP libraries
*** Updating SDK
*** Running ldconfig
*** Storing current firmware revision
*** Deleting downloaded files
*** Syncing changes to disk
*** If no errors appeared, your firmware was successfully updated to a51e2e072f2c349b40887dbdb8029f9a78c01987
*** A reboot is needed to activate the new firmware
-
Thanks mate,
It all worked out well ;-)
-
20.0.123 released and in apt repo.
See the top message of this topic.
-
This build requires a linux or master license.
It does not have a permanent timeout.
(I apologize in advance for this noob question:)
Does you mean that there's no 30-day trial on the ARM version?
I'd like to try this software out on the Beaglebone Black, and it would be good to know whether I'd be wasting my time if I haven't yet purchased a license.
-
There is a 30 day trial for the ARM version.
-
20.0.123 released and in apt repo.
See the top message of this topic.
All good here on Linux raspberrypi 4.0.6-v7+
:)
-
Hello,
There seems to be a small bug in the latest version:
Do you know the button on the right of 'repeat' and random' that if clicked shows the audio path? That no longer works in the latest version - it worked fine before.
This is annoying as I'm using the RPI as renderer via DLNA and can't confirm it doesn't change the volume or anything like that without this audio path view...
Thank you
-
I have added a HDMI touchscreen to my Raspberry Pi 2. It can only use a display setting of 800 x 600. I can't seem to reset the JRiver display to a usable size. It goes off screen and has a tendency to slide upward with parts of the display off screen.
Is there a setting or a text file I can edit to reset the size or otherwise make it re size for the 800 x 600 desktop to be usable?
-
I have added a HDMI touchscreen to my Raspberry Pi 2. It can only use a display setting of 800 x 600. I can't seem to reset the JRiver display to a usable size. It goes off screen and has a tendency to slide upward with parts of the display off screen.
Is there a setting or a text file I can edit to reset the size or otherwise make it re size for the 800 x 600 desktop to be usable?
I don't know of a convenient text configuration file you could edit, but if you hold down -alt- while attempting to move or resize the window using a mouse it will behave better (you'll need to hook up a keyboard and mouse, obviously).
If that doesn't work, JRiver also remembers what size it was last time it opened, so you could temporarily connect to a regular monitor, change the size down, then switch back to the touchscreen.
Honestly, if I were you, I would strongly consider using webgizmo in a lightweight browser for touchscreen control rather than the normal UI: http://wiki.jriver.com/index.php/WebGizmo
-
Hello,
There seems to be a small bug in the latest version:
Do you know the button on the right of 'repeat' and random' that if clicked shows the audio path? That no longer works in the latest version - it worked fine before.
This is annoying as I'm using the RPI as renderer via DLNA and can't confirm it doesn't change the volume or anything like that without this audio path view...
Thank you
Did anyone see this bug? The current build doesn't show the audio path... Please fix this?
-
It's already fixed in the main build: https://yabb.jriver.com/interact/index.php?topic=98698.0
ARM builds just lag a little bit.
-
It's already fixed in the main build: https://yabb.jriver.com/interact/index.php?topic=98698.0
ARM builds just lag a little bit.
Great,
Thanks!
-
The DSP studio hover issue is fixed in this latest build.