Topic: Setup JRiver Media Center 21 In Ubuntu/Linux Mint (Read 104765 times)

percy · « **Reply #100 on:** June 03, 2016, 03:47:45 am »

Thanks seems to work like a charm with "MediaCenter-21.0.83-amd64.deb".
This of course means that I cannot upgrade any longer until the JRiver fixes it.
I took a log from the MC21 85 version where launching an internet radio URL which could not be opened (although the same URL in a windows music player worked perfectly at the same time). Maybe the people from JRiver could have look at it. I shortened the log file to make it a bit smaller (< 700K)
I try to find out what went wrong by looking in that log file but didn’t understand what was going on.
Thanks a lot already

bob · « **Reply #101 on:** June 03, 2016, 11:30:00 am »

Quote from: percy on June 03, 2016, 03:47:45 am

Thanks seems to work like a charm with "MediaCenter-21.0.83-amd64.deb".
This of course means that I cannot upgrade any longer until the JRiver fixes it.
I took a log from the MC21 85 version where launching an internet radio URL which could not be opened (although the same URL in a windows music player worked perfectly at the same time). Maybe the people from JRiver could have look at it. I shortened the log file to make it a bit smaller (< 700K)
I try to find out what went wrong by looking in that log file but didn’t understand what was going on.
Thanks a lot already

Made a bit of a change, can you test this one?
http://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-21.0.87-amd64.deb

bob · « **Reply #102 on:** June 03, 2016, 05:32:48 pm »

Quote from: bob on June 03, 2016, 11:30:00 am

Made a bit of a change, can you test this one?
http://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-21.0.87-amd64.deb

One more change, can you try this one?
The debugging message has changed a bit too. You will see empty reads, if they return non-zero bytes requested I'd like to know.

http://files.jriver.com/mediacenter/channels/v21/latest/MediaCenter-21.0.87-2-amd64.deb

percy · « **Reply #103 on:** June 04, 2016, 01:26:50 am »

I have installed the “MediaCenter-21.0.87-2-amd64.deb” version and it seems to behave normally when playing internet radio.
Would you like me to perform certain tests or provide log files from specific test use cases?
Already a big thanks for your extremely fast response.

bob · « **Reply #104 on:** June 06, 2016, 10:41:36 am »

Quote from: percy on June 04, 2016, 01:26:50 am

I have installed the “MediaCenter-21.0.87-2-amd64.deb” version and it seems to behave normally when playing internet radio.
Would you like me to perform certain tests or provide log files from specific test use cases?
Already a big thanks for your extremely fast response.

Thanks for reporting back. Nothing more is needed for now but if you notice that a subsequent build has the same issue would you please report it in this thread?

percy · « **Reply #105 on:** June 06, 2016, 11:38:24 am »

Sure thanks

kstuart · « **Reply #106 on:** June 06, 2016, 10:49:55 pm »

What are all the dozens and dozens of "devices" in MC21 Linux under "Audio Devices" (which usually just has a handful like "Realtek HDMI" or "Cmedia ASIO" ?

mwillems · « **Reply #107 on:** June 06, 2016, 11:19:17 pm »

Quote from: kstuart on June 06, 2016, 10:49:55 pm

What are all the dozens and dozens of "devices" in MC21 Linux under "Audio Devices" (which usually just has a handful like "Realtek HDMI" or "Cmedia ASIO" ?

The devices with names that start with "front:" or "surround:" are hardware devices that use the ALSA protocol to talk directly to the hardware without resampling. They're analogous to (but not exactly the same as) WASAPI exclusive in windows in that they take exclusive control of the hardware and prevent resampling. The same device may be enumerated multiple times because Linux treats different output channel counts on the same device as separate devices (also called sinks). So for a six channel dac, you might see a "front" device, a "surround2.1" device, a "surround5.1" device, etc. For stereo playback, the appropriate hardware sink is the "front:" entry that corresponds to the audio device you want to play to.

There will be some others as well; the main other "notable" one to look for is the "Pulse" output. Pulse is the current system mixer software bundled with most linux distributions. It's analogous to direct sound output on windows: all programs can output at the same time, but all audio must be resampled to a single rate (48k by default). Depending on how your distro configured the audio stack the ALSA[default] and ALSA[dmix] outputs may work the similarly to the pulse output, or differently, or not work at all.

Generally, I'd recommend choosing the hardware output that corresponds to the number of channels you want for the physical device you want. So "[ALSA] front: cmedia," for stereo output on a cmedia device, etc.

Pierre67 · « **Reply #108 on:** June 07, 2016, 04:13:05 pm »

HI

I got Trusty Tahr, and the Purchase/Restore/Extend always show up when I click media center regardless of restoring my Master key. It s a real PITA.

I tried a re-install in vain.

Help...

Thanks,

Pierre

Awesome Donkey · « **Reply #109 on:** June 07, 2016, 04:25:34 pm »

Which version of MC are you using (go to the Help > About window)?

Pierre67 · « **Reply #110 on:** June 07, 2016, 04:38:58 pm »

85..Master Licence

Pierre67 · « **Reply #111 on:** June 08, 2016, 10:34:45 am »

I am using MC 21.0.85 for Ubuntu. The program is installed, upgraded and updated. I install the key no problems MC 21 comes up. When I exit the program and later return in it, it tells me that the trial period is over and gives me the options to purchase etc. I tried bringing up the program via terminal, but it tells me it is not there. This program used to run great up until yesterday ?

Any ideas?

bob · « **Reply #112 on:** June 10, 2016, 10:55:28 am »

Quote from: Pierre67 on June 08, 2016, 10:34:45 am

I am using MC 21.0.85 for Ubuntu. The program is installed, upgraded and updated. I install the key no problems MC 21 comes up. When I exit the program and later return in it, it tells me that the trial period is over and gives me the options to purchase etc. I tried bringing up the program via terminal, but it tells me it is not there. This program used to run great up until yesterday ?

Any ideas?

Likely a configuration permissions/ownership issue or a corrupted Settings file.
You aren't using sudo or something to run MC, right?

You can correct ownership issues by doing this from a terminal prompt (as your user, not root):
cd ; touch ugidfile ; sudo chown -R --reference=ugidfile .jriver

Then reenter the license key.

If that still doesn't work, move the Machine Settings file out of the way and rerun MC and reenter the key. From a terminal prompt as your user, not root and with MC NOT running:

cd ; mv .jriver/Media\ Center\ 21/Settings/Machine\ Settings.ini .jriver/Media\ Center\ 21/Settings/Machine\ Settings.sav
then rerun MC which will create a new Machine Settings file. Enter your key and see if it sticks.

Pierre67 · « **Reply #113 on:** June 13, 2016, 06:38:36 pm »

Last option worked out well.

Thank you.

Pierre

more10 · « **Reply #114 on:** July 16, 2016, 03:39:43 pm »

Crashes on newly installed Ubuntu Studio 16.04 x64. I was importing my library at the same time as playing a record. I checked "send error report". Is that enough or should I post stack trace etc here?

Awesome Donkey · « **Reply #115 on:** July 16, 2016, 04:20:16 pm »

You can try running mediacenter21 in a Terminal and post the output here when it crashes. Ubuntu Studio is an untested configuration, so it may or may not work.

audiotone · « **Reply #116 on:** July 16, 2016, 06:43:23 pm »

Mc 20 works fine in ubuntu studio...mc 21 still does not...
I already payed for mc 22...hope that one will work...

gm.cnc · « **Reply #117 on:** July 24, 2016, 04:06:49 pm »

Hi,

I am a long time user of Media Center on Windows. I am now investigating its usage on Mint.

Is there a device/setting that guarantees that the source information (FLAC) is not modified by the audio stack? For instance, unlike for Windows, it's always possible to adjust the sound level. I have an IEC958 interface + DAC.

Thanks in advance,

Gilles

Quote from: mwillems on June 06, 2016, 11:19:17 pm

The devices with names that start with "front:" or "surround:" are hardware devices that use the ALSA protocol to talk directly to the hardware without resampling. They're analogous to (but not exactly the same as) WASAPI exclusive in windows in that they take exclusive control of the hardware and prevent resampling. The same device may be enumerated multiple times because Linux treats different output channel counts on the same device as separate devices (also called sinks). So for a six channel dac, you might see a "front" device, a "surround2.1" device, a "surround5.1" device, etc. For stereo playback, the appropriate hardware sink is the "front:" entry that corresponds to the audio device you want to play to.

There will be some others as well; the main other "notable" one to look for is the "Pulse" output. Pulse is the current system mixer software bundled with most linux distributions. It's analogous to direct sound output on windows: all programs can output at the same time, but all audio must be resampled to a single rate (48k by default). Depending on how your distro configured the audio stack the ALSA[default] and ALSA[dmix] outputs may work the similarly to the pulse output, or differently, or not work at all.

Generally, I'd recommend choosing the hardware output that corresponds to the number of channels you want for the physical device you want. So "[ALSA] front: cmedia," for stereo output on a cmedia device, etc.

bob · « **Reply #118 on:** July 25, 2016, 10:40:51 am »

Quote from: gm.cnc on July 24, 2016, 04:06:49 pm

Hi,

I am a long time user of Media Center on Windows. I am now investigating its usage on Mint.

Is there a device/setting that guarantees that the source information (FLAC) is not modified by the audio stack? For instance, unlike for Windows, it's always possible to adjust the sound level. I have an IEC958 interface + DAC.

Thanks in advance,

Gilles

When the hardware device is selected (ie IEC958) and the system volume control you won't be able to control the volume since the source will be sent to the device driver as is.
I assume that is also the case when the volume control is set to internal and the volume is at 100% and you aren't using any DSP functions.

gm.cnc · « **Reply #119 on:** July 25, 2016, 02:52:48 pm »

I can always control the volume, even IEC958 interface is selected. What do you mean by "volume control is set to internal" ?

Thanks

bob · « **Reply #120 on:** July 25, 2016, 03:22:45 pm »

Quote from: gm.cnc on July 25, 2016, 02:52:48 pm

I can always control the volume, even IEC958 interface is selected. What do you mean by "volume control is set to internal" ?

Thanks

When you click on the volume control you can select the type of volume control that is used (system, internal or disabled).

sekrit · « **Reply #121 on:** August 30, 2016, 12:01:04 pm »

Quote from: Awesome Donkey on September 30, 2015, 05:36:33 pm

Just tested MC21 in the final beta of Ubuntu 15.10 Wily Werewolf and it functions fine as expected.

That said there's one bit of news to pass along, I've decided to stop using Ubuntu and Linux in general outside of a virtual machine due to a nasty bug in the Linux kernel's USB driver since 3.18.0 where when XHCI will give off device descriptor errors and cause USB devices to malfunction during the boot and after rebooting back into Windows and Mac - even after disabling XHCI and XHCI hand-off! The issue was supposed to be fixed in 4.0 kernel but it still persists in 4.1, 4.2 and 4.3 (it got really bad in 4.3-rc3 for some reason). So yeah, I'll be retiring Ubuntu off the main machine for now and just use Ubuntu virtual machines to test. I've been reporting this issue for nearly 8 months now, but not much has been done about it. I've tried different hardware (keyboard, mouse, USB DAC, motherboard, GPU, RAM, etc.) and it doesn't make a difference. It also happens in a VM too, but it doesn't mess with other OSes so it's pretty straightforward to correct.

Also going to retire the Mac portion off the main machine too and just use Windows for the foreseeable future due to multiple annoying issues trying to get the AMD graphics card to function correctly. I'll probably reinstate the Mac once I can save up and get a Nvidia card. I'll likely reinstate Ubuntu if/when they manage to fix that annoying USB issue.

EDIT: Decided to redo the Mac and Ubuntu installs and keep reporting the Linux XHCI issue.

Appreciate your help for setting up. Ubuntu 16.04 both i386 and amd64 installed without any errors.

Interesting to read that you are turning away from Ubuntu. I have been using Windows 10x64 bit for some time and got tired of it. Lately, it was causing me relentless music skipping issue and high latencies (despite latest Xeon CPU and server motherboard).

So, I pulled an ancient CPU and motherboard from basement. I installed Debian 8.5 Jessie first. I had that USB audio going silent problem every time. It played only a few hours and then USB sound was dead.

I am using Ubuntu 16.04 x64 now and so far no USB audio issue. Maybe Ubuntu engineers fixed that issue, but not the Debian?

sekrit · « **Reply #122 on:** September 02, 2016, 01:57:02 pm »

Ubuntu 16.04.1 installed and updated. It is hard to say "stable" version of JRiver is 21.0.90. I cannot keep it running longer than a couple of hours. It keeps crashing.

I tried it on Debian 8.5 first. JRiver doesn't crash on Debian but I lose audio to the external USB DAC due to USB audio driver bug.

Anybody has a "stable" running JRiver on Ubuntu? Please advice...

sekrit · « **Reply #123 on:** September 07, 2016, 12:55:01 pm »

Quote from: sekrit on September 02, 2016, 01:57:02 pm

Ubuntu 16.04.1 installed and updated. It is hard to say "stable" version of JRiver is 21.0.90. I cannot keep it running longer than a couple of hours. It keeps crashing.

I tried it on Debian 8.5 first. JRiver doesn't crash on Debian but I lose audio to the external USB DAC due to USB audio driver bug.

Anybody has a "stable" running JRiver on Ubuntu? Please advice...

Guys, how can I find out what is crashing JRiver on Ubuntu?

JimH · « **Reply #124 on:** September 07, 2016, 12:59:06 pm »

You could try playing to a different output to see if the problem is related to USB or not.

Awesome Donkey · « **Reply #125 on:** September 07, 2016, 02:20:33 pm »

You could try enable logging and post the logs here after a crash. Hard to say what could be causing it though. Auto-Import enabled? You could also try running mediacenter21 in a Terminal and using it until it crashes to see if it leaves behind a clue as to why it's crashing in the Terminal.

sekrit · « **Reply #126 on:** September 08, 2016, 01:37:41 pm »

Quote from: JimH on September 07, 2016, 12:59:06 pm

You could try playing to a different output to see if the problem is related to USB or not.

This happens when using JRemote more often than JRiver on office Mac. So, I don't think is the USB bridge, yet.. Motherboard sound chip is disabled.

sekrit · « **Reply #127 on:** September 08, 2016, 01:51:40 pm »

Quote from: Awesome Donkey on September 07, 2016, 02:20:33 pm

You could try enable logging and post the logs here after a crash. Hard to say what could be causing it though. Auto-Import enabled? You could also try running mediacenter21 in a Terminal and using it until it crashes to see if it leaves behind a clue as to why it's crashing in the Terminal.

Ok, enabled logging. Btw, installed all the updates to Ubuntu and JRiver. No other app installed or running.

Yes, auto-import is enabled. I have 126,000+ files. I don't have any m4p (DRM) files. 8 of them are SACD ISO. The rest are variety of lossless formats FLAC, DSD, DSF, etc. Could this be the problem?

How do I run JRiver in a terminal?

Awesome Donkey · « **Reply #128 on:** September 08, 2016, 02:14:22 pm »

Quote from: sekrit on September 08, 2016, 01:51:40 pm

How do I run JRiver in a terminal?

Make sure MC is already closed, open the Terminal app then type in mediacenter21 and press Enter. That's all.

sekrit · « **Reply #129 on:** September 08, 2016, 02:29:00 pm »

Quote from: Awesome Donkey on September 08, 2016, 02:14:22 pm

Make sure MC is already closed, open the Terminal app then type in mediacenter21 and press Enter. That's all.

Done.

I was starting it from "startup applications" at boot time. For some reason, startup option in JRiver does not work in Ubuntu.

sekrit · « **Reply #130 on:** September 10, 2016, 06:23:07 am »

Quote from: sekrit on September 08, 2016, 01:37:41 pm

This happens when using JRemote more often than JRiver on office Mac. So, I don't think is the USB bridge, yet.. Motherboard sound chip is disabled.

Attached is my log file. It crashes last night when it was inactive, making me think a background process crashed it. What caused it?

Previous log file is too large 1.5 MB. But I found many errors like this:

0186515: 2684352256: General: RunProgram: Start
0186515: 2684352256: General: RunProgram: Running blocking command via popen: stat -fc %T '/media/username/w10share/Hi-Fi/16BIT_MUSIC/Berliner Philharmoniker/'
0186524: 2684352256: General: RunProgram: Finish (9 ms)
0186524: 2684352256: Import: CWatchFoldersThread::Thread: Failed to watch folder '/media/username/w10share/Hi-Fi/16BIT_MUSIC/Berliner Philharmoniker/', via inotify. Will scan every 120 minutes (error: 0)

sekrit · « **Reply #131 on:** September 10, 2016, 09:23:01 am »

Another crash.This time it was streaming to JRemote. Terminal reported "segmentation fault"

sekrit · « **Reply #132 on:** September 13, 2016, 10:34:56 am »

Quote from: JimH on September 07, 2016, 12:59:06 pm

You could try playing to a different output to see if the problem is related to USB or not.

This is the latest crash report. It is hard to decode these messages to solve the problem.

Terminal said "segmentation error" again. What does this segmentation error mean?

Awesome Donkey · « **Reply #133 on:** September 13, 2016, 02:57:36 pm »

Looks like the semi-known JRTools segfault issue that's happened to people in the past. I'm not sure if it's been fixed in MC22 yet or not (as it's probably too late for MC21).

Try disabling auto-import and try running it then and see if it still crashes.

sekrit · « **Reply #134 on:** September 13, 2016, 03:11:34 pm »

Quote from: Awesome Donkey on September 13, 2016, 02:57:36 pm

Looks like the semi-known JRTools segfault issue that's happened to people in the past. I'm not sure if it's been fixed in MC22 yet or not (as it's probably too late for MC21).

Try disabling auto-import and try running it then and see if it still crashes.

Thanks AD. I turned off the auto-import and crossed fingers. I read about this segmentation fault which seems to be a nasty bug.

sekrit · « **Reply #135 on:** September 24, 2016, 02:17:40 pm »

It did not crash with auto-import for 1 week. I turned on the auto-import and crashed again.

Here is the log file.

bob · « **Reply #136 on:** September 26, 2016, 10:52:10 am »

Quote from: sekrit on September 24, 2016, 02:17:40 pm

It did not crash with auto-import for 1 week. I turned on the auto-import and crashed again.

Here is the log file.

The last thing in that log file was the viewing of the log file!
I assume that means you restarted MC and viewed the log but in that case it's the Previous Log.txt that we want to look at.
So, can you do it again and send both logs?

Since you are crashing in import it's almost certain that there is a damaged media file amongst your files.

MrKleanWitHare · « **Reply #137 on:** November 25, 2016, 12:56:56 pm »

Hello,

I've been having some trouble running JRiver 21 lately. The program will not boot. When trying to start from terminal I get "Segmentation fault."

Any ideas? I'm running Mint (Rosa).

Thanks!

bob · « **Reply #138 on:** November 26, 2016, 11:43:07 am »

Quote from: MrKleanWitHare on November 25, 2016, 12:56:56 pm

Hello,

I've been having some trouble running JRiver 21 lately. The program will not boot. When trying to start from terminal I get "Segmentation fault."

Any ideas? I'm running Mint (Rosa).

Thanks!

Probably missing a library or bad settings files.

in terminal:

Code: [Select]

ldd -d /usr/lib/jriver/Media\ Center\ 21/*.so* | less
ldd -d /usr/lib/jriver/Media\ Center\ 21/Plugins/*.so* | less
ldd -d /usr/bin/mediacenter21

Look for "Not Found"

If everything is ok, move the settings dir and try again.

Code: [Select]

mv ~/.jriver/Media\ Center\ 21/Settings ~/.jriver/Media\ Center\ 21/Settings.savand re-run mediacenter21

MrKleanWitHare · « **Reply #139 on:** December 02, 2016, 06:41:36 pm »

Quote from: bob on November 26, 2016, 11:43:07 am

Probably missing a library or bad settings files.

in terminal:
Code: [Select]
ldd -d /usr/lib/jriver/Media\ Center\ 21/*.so* | less ldd -d /usr/lib/jriver/Media\ Center\ 21/Plugins/*.so* | less ldd -d /usr/bin/mediacenter21
Look for "Not Found"

If everything is ok, move the settings dir and try again.
Code: [Select]
mv ~/.jriver/Media\ Center\ 21/Settings ~/.jriver/Media\ Center\ 21/Settings.savand re-run mediacenter21

Thanks for your help. That did work temporarily, until MC would not play a single file.

Turns out it was just a bad memory stick. Stick replaced. OS updated to Sarah. MC is working just fine now.

Thanks!

INTERACT FORUM

Author Topic: Setup JRiver Media Center 21 In Ubuntu/Linux Mint (Read 104765 times)