INTERACT FORUM
More => Old Versions => JRiver Media Center 20 for Linux => Topic started by: Awesome Donkey on January 27, 2014, 01:26:58 pm
-
This tutorial aims to aid users into setting up JRiver Media Center 20 onto computers running the following Linux operating systems;
Ubuntu 15.04 Vivid Vervet
Ubuntu 14.04.2 LTS Trusty Tahr
Linux Mint 17.2 Rafaela
Linux Mint Debian Edition 2 Betsy
NOTE: This tutorial does borrow ideas and parts done by InflatableMouse and his excellent Debian Wheezy tutorial found here (http://yabb.jriver.com/interact/index.php?topic=85957.0), so please thank him.
Before we continue, please note the following;
- Media Center 20 for Linux is developed on Debian Wheezy 32-bit and Debian Jessie 64-bit - support for distros other than Wheezy 32-bit and Jessie 64-bit, like Ubuntu and Mint is considered experimental and not officially supported!
- This tutorial will focus on the operating systems above, any others you're on your own with.
- This *should* also apply to Ubuntu/Mint derivatives like Xubuntu, Kubuntu, Lubuntu, Ubuntu GNOME, Linux Mint (MATE), Linux Mint (Xfce), etc. However, extra steps may be required!
- Before installing, please read the outstanding issues topic (http://yabb.JRiver.com/interact/index.php?topic=85770.0)! Many of the issues noted for Debian also apply to Ubuntu/Mint!
Step 1 - Add the JRiver APT Repository:
The APT repository is required to install Media Center 20 and keep Media Center 20 updated with every new release.
First, open a Terminal (by either pressing CTRL+ALT+T or by searching for the terminal in your desktop environment) and either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add -
Next, with the Terminal still open, we need to download and add the correct mediacenter.list file to /etc/apt/sources.list.d/ depending if you're using 32-bit or 64-bit so either type one the following commands or copy and paste the command in and press Enter;
If you're using 64-bit Ubuntu/Linux Mint:
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter20jessie.list -O /etc/apt/sources.list.d/mediacenter20.list
Or...
If you're using 32-bit Ubuntu/Linux Mint:
sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter20.list -O /etc/apt/sources.list.d/mediacenter20.list
Finally, we need to reload the packages list, so with the Terminal still open either type the following command or copy and paste the command in and press Enter;
sudo apt-get update
That's it! Proceed to step 2!
Step 2 - Installing Media Center 20:
It's finally time to install Media Center 20! First, open a Terminal (by either pressing CTRL+ALT+T or by searching for the Terminal in your desktop environment) or re-use the Terminal from the previous step. Next either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
sudo apt-get install mediacenter20
During this process it should say something along the following;
The following extra packages will be installed:
lame libao-common libao4 libcue1 libreplaygain1 musepack-tools vorbis-tools
xfonts-100dpi xfonts-75dpi xfonts-unifont
Suggested packages:
libesd0 libesd-alsa0 ttf-unifont
The following NEW packages will be installed:
lame libao-common libao4 libcue1 libreplaygain1 mediacenter20 musepack-tools
vorbis-tools xfonts-100dpi xfonts-75dpi xfonts-unifont
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 39.9 MB of archives.
After this operation, 146 MB of additional disk space will be used.
Do you want to continue? [Y/n]
However, if you receive an error like;
dependency problems prevent configuration of mediacenter20:
mediacenter20 depends on ....
This means all dependencies have not been met. Don't fret, this can usually be taken care of by using the following command in the Terminal by either typing the following command or copying and pasting the command in and press Enter;
sudo apt-get install -f
It'll show you the missing dependencies, after looking them over just press enter to install them.
Now, if you're using a GNOME-based desktop environment (GNOME, Cinnamon, MATE, Unity, etc.) you should either type the following command or copy and paste the command in into the Terminal and press Enter to install these additional dependencies, otherwise skip this step if it's already installed!
sudo apt-get install libp11-kit-gnome-keyring p11-kit-modules
Now assuming all dependencies are met, you've been successful at installing Media Center 20 in Ubuntu/Mint! However, I recommend rebooting since this will allow MC to load up fonts correctly - otherwise if you run MC without rebooting first, fonts may look pretty horrendous!
Now, after rebooting you can start Media Center either go into the Unity dash, Mint menu, etc. and search for Media Center 20 or you can run it from the Terminal by either typing the following command or copying and pasting the command in and press Enter;
mediacenter20
Now, we're going to cover installing the license for those who have purchased in step 3!
-
Step 3 - Installing A Media Center 20 Linux License Or Master License:
This portion of the tutorial will explain how to manually install your purchased license (either Linux licence or Master licence) in Media Center 20. Thanks for purchasing a license and supporting the development!
First, make sure MC20 is closed and either download the .mjr by either restoring the license here (https://rover.jriver.com/cgi-bin/restore.cgi) or if you just purchased a Media Center 20 Linux or Master license, then use the .mjr file downloaded with your purchase. After downloading your license file, open a Terminal and either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
If you're using a Linux license:
mediacenter20 /RestoreFromFile "Media Center20 Linux-YYYYYY.mjr"
NOTE: Replace the X's and Y's with the correct numbers from your specific .mjr file AND adjust the path to your file.
If you're using a Master license:
mediacenter20 /RestoreFromFile "Media Center20 Master-YYYYYY.mjr"
NOTE: Replace the X's and Y's with the correct numbers from your specific .mjr file AND adjust the path to your file.
If your code is located in the default downloads directory, the following command should work (remember to replace the X's and Y's with the correct numbers and change Linux to Master if you're using a Master license!);
mediacenter20 /RestoreFromFile ~/Downloads/"Media Center20 Linux-YYYYYY.mjr"
If you do not encounter an error while restoring your license from the file, open Media Center 20 up then go to the Help menu > Registration Info... - if it's registered, congratulations, your MC20 for Linux is now registered!
Additional information and discussion regarding licenses can be found in this topic (http://yabb.jriver.com/interact/index.php?topic=95014.0).
Once you're done, you should be ready to go! Congratulations, you've successfully installed Media Center 20 on your Ubuntu/Linux Mint machine! The next step will aid you in keeping Media Center 21 up-to-date.
Step 4 - Updating Media Center 20:
Okay, so you've got Media Center 20 installed and you might be wondering "how do I keep MC 20 up-to-date?". Well, there's several different ways available to accomplish this.
The easiest method to check for updates and update Media Center 20 if an update is available? Simple! Just open a Terminal and either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
sudo apt-get update && sudo apt-get dist-upgrade
Let the command run and it should prompt you with a list of updates for your Linux distribution of choice. Just type Y (or yes) and the system should be updated. It's HIGHLY recommended to run this command once a week - not just for MC 20 updates but for keeping up with the latest patches for vulnerabilities and various other potential security concerns.
The other ways to update Media Center 20? Well, if you Have Synaptic Package Manager installed you can update your system from there as well. Or you can just use the built-in update manager, if one is available for your Linux distro of choice! :)
Okay, what's next? The next post contains various information and tips you may find handy. Enjoy!
-
Get Pulseaudio Output Working:
If desired, you can also output using Pulseaudio - keep in mind though that ALSA is bit-perfect. I'd highly recommend sticking with ALSA instead of Pulseaudio since Pulseaudio requires resampling to one sample rate, but if you wish to use Pulseaudio for whatever reason you'll need to set it up...
Pulseaudio *should* work out-of-the-box on Ubuntu 14.04+/Linux Mint 17+ 64-bit however if you want to cover all your bases on getting Pulseaudio working try the following commands in a Terminal by either typing the following command or copying and pasting the command in and press Enter (you *may* be prompted for your password);
sudo apt-get install libasound2-plugins
NOTE: You don't need to use this command in Ubuntu 15.04 Vivid Vervet 64-bit.
Just open Media Center up, go to Tools > Options > Audio > click the Device settings... button and select pulse as the output device but keep in mind you may need to specify the default output device Pulseaudio uses via the pavucontrol utility.
Setting Default Pulseaudio Device Via PulseAudio Volume Control (pavucontrol):
When trying to use the Pulseaudio output in Media Center, you might find yourself with this type of error when trying to play music...
(http://i.imgur.com/IOvowyP.png)
This means the correct output device for Pulseaudio isn't being used, thus why this error is encountered. Fortunately, there's a way to fix this. Open up a Terminal window and either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
sudo apt-get install pavucontrol
After installing, either start PulseAudio Volume Control by typing pavucontrol into the Terminal or by typing in Pulseaudio into the Unity dash until you see PulseAudio Volume Control. Once open, you'll want to go to the Configuration tab like seen here;
(http://i.imgur.com/Co2KCVo.png)
Notice how there's multiple output devices listed here? I used my old AMD machine just for this example and left onboard audio enabled for this example. As seen above, what I want to use as the default is my old Xonar STX card aka Virtuoso 100. In this example, to set this card up I setup the Configuration tab to the following...
(http://i.imgur.com/d4npreQ.png)
And take a look at the Output Devices tab now. See how it's using the Virtuoso 100 as the default device?
(http://i.imgur.com/HaWNa97.png)
Remember, this is an example with my old Xonar STX sound card. Please setup your device(s) accordingly for your own needs! And if desired setup your input devices via the Input Devices tab! If everything looks good, try playing music through pulse again in Media Center. If sound works, congrats, you have working sound via pulse!
How To Remove Media Center 19 and Media Center 20
If you've updated from Media Center 19 to Media Center 20, you might find yourself with two versions of Media Center installed. Since Media Center 20 is a free upgrade from Media Center 19, it's recommended you backup your settings in Media Center 19 (to somewhere you can find it, e.g. Desktop) and remove Media Center 19.
Step 1: Backup your library and settings. Read the wiki article on how to backup your library and settings (http://wiki.jriver.com/index.php/Library_Backup).
Step 2: Open a Terminal and input the following (you *may* be prompted for your password - answer yes when it prompts!);
sudo apt-get remove mediacenter19
Now, if you want to remove Media Center 20, just repeat step 1 and use this command instead;
sudo apt-get remove mediacenter20
If all goes well, your Media Center 19/20 installation(s) should be removed.
Enabling Copy And Paste Buffers
Currently Media Center 20 for Linux supports one copy and paste buffer system (cut buffers) and it can be challenging to use. For further information please read Bob's topic about this here (http://yabb.jriver.com/interact/index.php?topic=90381.0) (I HIGHLY suggest you do!). The current downside is I've not found a working way to add these copy and paste commands to the X startup scripts for Ubuntu/Mint. I'll continue looking into this but for those who want copy and paste working only while Media Center 20 is open, this is the best way to do it.
Step 1: Close MC20 if its open and open a Terminal window and input the following (you *may* be prompted for your password);
sudo apt-get install autocutsel
Step 2: Once this is installed, leave the Terminal open and input the following;
autocutsel -fork &
Again, make sure to leave the Terminal open and input the following;
autocutsel -selection PRIMARY -fork &
Remember to leave the Terminal with the commands running open for as long as you need copy and paste functionality. If you close the Terminal you'll lose the ability to copy and paste!
Step 3: Open MC20 and you should be able to successfully copy and paste.
Once you're done with copy and paste, close the Terminal window. To re-enable copy and paste, just follow step 2 again.
Tutorial changelog:
3.2 (06-01-2015): Updated for the new build method MC uses - install process is now simplified!
3.1 (05-18-2015): Changed the wording and updated the tutorial.
3.0 (05-14-2015): Heavily updated all the tutorials - I also removed all the dependencies as they'll be installed alongside mediacenter20. 32-bit may be supported, but needs testing!
2.2 (04-23-2015): Dropped Ubuntu 14.10 in favor of Ubuntu 15.04.
2.1 (04-16-2015): Added Ubuntu 15.04 support with a workaround to install the required libgcrypt11.
2.0 (03-15-2015): Tutorial has been rewritten and simplified. Lots of various changes!
1.8 (03-03-2015): Updated the tutorial specifying libgl1-mesa-glx:i386 and libgl1-mesa-glx as dependencies for Ubuntu 14.10 64-bit/32-bit. Also specified libgl1-mesa-glx-lts-utopic:i386 and libgl1-mesa-glx-lts-utopic as dependencies for Ubuntu 14.04.2 LTS 64-bit/32-bit (as they're apparently needed to avoid broken packages in Ubuntu 14.04.2).
1.7 (02-24-2015): Added APT repository tutorial and updated Media Center 20 links to the latest.
1.6 (02-24-2015): Added tutorial for removing Media Center 19 and Media Center 20.
1.5 (02-01-2015): Added tutorial for restoring a license, using copy and paste and updated the links
1.4 (11-10-2014): Added Linux Mint, updated links to the latest MC20 build and added a quick tutorial on updating Media Center 20 builds via the terminal
1.3 (10-23-2014): Updated for Ubuntu 14.10 and updated links
1.2 (08-12-2014): Updated for Media Center 20 + new requirements
1.1 (04-22-2014): Pulseaudio + pavucontrol information and screenshots added
1.0 (04-22-2014): Updated to reflect and require Ubuntu 14.04 LTS, updated dependencies and various fixes/changes
0.7 (03-15-2014): Updated stuff!
0.6 (02-04-2014): Updated Ubuntu 32-bit tutorial
0.5 (01-29-2014): Updated the kernel links to 3.13.1
0.4 (01-28-2014): Modified and cleaned up the formatting
0.3 (01-28-2014): Added AMD HDMI audio tutorial
0.2 (01-28-2014): Added Ubuntu 32-bit tutorial (still experimental, will need to check a couple more times)
0.1 (01-27-2014): Initial tutorial for Ubuntu 64-bit
-
Thank you!
-
No problem. I'll be editing it more as the day passes. Hopefully I can get the Pulseaudio tutorial up by the end of today or tomorrow as I'll need to do some testing there (e.g seeing if .asoundrc is required or not for Pulse output, if adding yourself to the audio group is required and seeing if adding pulseaudio --start to startup is required). If I can't get it done by today instead I'll work on the tutorial of updating the kernel to get AMD HDMI audio working.
I also want to cover the ALSA device settings in MC and alsacap usage. :)
EDIT: Got side tracked by something, will resume testing and work on the tutorial tomorrow!
-
- Media Center 19 on Linux is a 32-bit binary, but seeing how Ubuntu 13.04+ supports multiarch this isn't and shouldn't be an issue!
See, here I am trying to install it on Ubuntu 12.10LTS and wondering why it's spitting errors at me, and you've just answered it.
Thanks! Will wait until 14.04 to update the server and install this to serve music.
-
Here's an article (https://help.ubuntu.com/community/MultiArch) about MultiArch in Ubuntu - it *might* help you.
-
Okay, got some stuff added like 32-bit Ubuntu (experimental, will need to double verify in another virtual machine install, time permitting), AMD HDMI Audio and modified the wording. Still working on a few other things, hopefully I get enough time to finish it and get it posted.
Feedback welcome! :)
-
I can't verify it but it looks good 8).
Thanks for the effort!
-
For ubuntu 32 bit 13.10 fresh install, the following worked for me:
sudo apt-get install libssh2-1 <- missing dependency identified with first install attempt
sudo dpkg --install ~/Downloads/MediaCenter-19.0.108.deb <- already downloaded from this website
-
I fixed the tutorial above to reflect that dependency - my apologies for the late reply. I've been absolutely swamped as of late and sadly I just haven't had the time to focus more on the advanced parts of this tutorial but *hopefully* soon within the next few weeks my workload will significantly decrease and I'll have more time dedicated to updating and improving this tutorial!
P.S. Can this topic be stick'd? Thanks! :)
EDIT 03/03/2014: Still experiencing issues with time, part of the reason having to do with this long horrible Winter, but hopefully my workload decreases soon as Spring comes!
-
I am attempting to set up Ubuntu 13.10 64 bit so I can install Mediacenter 19. I copied the setup code and got the following response when I entered it.
mark@AsusZ87:~$ sudo apt-get install libcurl3:i386 libx11-6:i386 lib32stdc++6 libmpcdec6:i386 libc6:i386 libstdc++6:i386 libx11-6:i386 xfonts-75dpi xfonts-100dpi libcrypto++9:i386 libasound2:i386 libuuid1:i386 libboost-regex1.49.0:i386 libicu48:i386 lame musepack-tools vorbis-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
musepack-tools : Depends: libmpcdec6 (>= 1:0.1~r435) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
I am new to Linux and would appreciate any help.
-
Have you tried running sudo apt-get install -f from the terminal? Or try sudo apt-get install libmpcdec6 and see what happens. If those fail you can try running sudo apt-get remove musepack-tools but keep in mind you'll lose Musepack support.
-
Thanks for your response. Following are the results of the commands you suggested:
mark@AsusZ87:~$ sudo apt-get install -f
[sudo] password for mark:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
mark@AsusZ87:~$ sudo apt-get install libmpcdec6
Reading package lists... Done
Building dependency tree
Reading state information... Done
libmpcdec6 is already the newest version.
libmpcdec6 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
mark@AsusZ87:~$
Am I correct in concluding that libmpcdec6 is already installed? If so, should that be deleted from the code you initially posted to prepare Ubuntu for installing Media Center 19? I am new to Linux, so I do not fully understand the results of the commands I entered.
-
> Am I correct in concluding that libmpcdec6 is already installed?
Yep, looks like you've got it already and you should be good to go. Does MC start?
> If so, should that be deleted from the code you initially posted to prepare Ubuntu for installing Media Center 19?
Well, it should automatically satisfy all dependencies, unless those have changed in the last few builds. When I get a new Ubuntu install up and going, I'll be testing exactly this (I'm trying to wait until Ubuntu 14.04 LTS is released).
> I am new to Linux, so I do not fully understand the results of the commands I entered.
sudo (https://wiki.debian.org/sudo)
apt-get (https://wiki.debian.org/apt-get)
Basically what you did was install the required packages (binaries) from the terminal so the software (MC) can function correctly. libmpcdec6 was the specific package which originally gave out a broken package error (due to it not being installed/requirement satisfied), but it seems to have resolved itself, assuming you can now run MC without issue.
-
I did the install and got dependency problems. I then ran the sudo apt-get install -f command and the system corrected dependencies and downloaded and installed archived information. When I launch Media Center in terminal it runs with the following errors in the terminal window.
mark@AsusZ87:~$ mediacenter19
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 3 request code 3
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 15
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 3
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 15
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 3
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 15
Details: BadWindow (invalid Window parameter)
I can't find an icon in the Dashboard to launch from. My files are stored on a NAS drive that I need to figure out how to mount so I can try to play some files.
Do the errors mean something is wrong with the install? I installed the latest version (121) just released today.
-
I did the install and got dependency problems. I then ran the sudo apt-get install -f command and the system corrected dependencies and downloaded and installed archived information. When I launch Media Center in terminal it runs with the following errors in the terminal window.
mark@AsusZ87:~$ mediacenter19
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 8 request code 42
Details: BadMatch (invalid parameter attributes)
Ignoring Xlib error: error code 3 request code 3
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 15
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 3
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 15
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 3
Details: BadWindow (invalid Window parameter)
Ignoring Xlib error: error code 3 request code 15
Details: BadWindow (invalid Window parameter)
I can't find an icon in the Dashboard to launch from. My files are stored on a NAS drive that I need to figure out how to mount so I can try to play some files.
Do the errors mean something is wrong with the install? I installed the latest version (121) just released today.
Those are non-fatal xlib errors which are normal (for now).
Look under applications and you'll find the MC icon then you can drag it to the dashboard IIRC.
Perhaps someone else has more info on the NAS, it seems mounting these is pretty distro/desktop dependent.
-
Thank your for your response.
When I look at applications, I cannot find the icon for Media Center. It does show up on my left icon bar when I launch the application from terminal.
My other problem is I can't find Media Center when I access my network with my Google Nexus 7. It did pick it up when I tested the Windows version.
-
I just found the icon under an expanded menu and now have it on my main icon bar.
-
Thank your for your response.
When I look at applications, I cannot find the icon for Media Center. It does show up on my left icon bar when I launch the application from terminal.
My other problem is I can't find Media Center when I access my network with my Google Nexus 7. It did pick it up when I tested the Windows version.
Turn on media network under options.
-
Thank you.
I did figure out how to use the media network and it recognized my DAC. I can find it and control it with the Nexus 7 tablet.
-
I updated the tutorial some yesterday after doing a clean Ubuntu install.
-
An update for this topic. I'm going to wait until Ubuntu 14.04 LTS' release before making major updates to this tutorial. Why? Because by default Ubuntu 14.04 will address certain issues users may have, especially getting HDMI audio working out of the box. That way I can have basically a clean state to restructure this tutorial and simplify it. My main goal once Ubuntu 14.04's released? Getting the Pulseaudio tutorial up since to me that's very important.
In the meantime, I've made small updates to the requirements and updated MC mentions to the latest build.
-
The updates you described in your March 16 posting worked great. I did an install on my laptop and everything ran like clock work without any errors.
Thank you very much for your contribution.
-
I think it's time for an update. I've done a clean install of the Ubuntu 14.04 LTS Final Beta and checked MC. Some requirements don't seem to be needed anymore (libboost-regex1.49.0:i386 and libicu48:i386) but there's one brand new requirement (libtasn1-3:i386). So, because of that the current list of dependencies to get MC running on x64 Ubuntu 14.04 is...
libtasn1-3:i386 libcurl3:i386 libx11-6:i386 libmpcdec6:i386 libc6:i386 libstdc++6:i386 libx11-6:i386 libcrypto++9:i386 libasound2:i386 libuuid1:i386 libssh2-1:i386 lib32stdc++6 xfonts-75dpi xfonts-100dpi lame
Also, Pulseaudio is easy as pie to get working! Only requires two steps (installing two dependencies; libasound2-plugins:i386 and installing pavucontrol to setup Pulseaudio) and using pavucontrol to setup your output correctly. :) Because of that, when 14.04 LTS final is released, it'll be the minimum version supported by this tutorial and I'll get to remove the HDMI stuff as it *should* include kernel 3.14. :)
-
Hi, I tried installing on Ubuntu 14.04 by downloading and installing via the terminal, got dependency errors, ran the sudo apt-get install -f command and installed whatever it prompted me to install and I'm still getting errors when trying to install both the latest version of MediaCenter 19 as well as the version 19.0.122 (which I tried after trying to install 19.0.128). Here's the error message I'm getting:
2014-04-16 21:20:42 (1.61 MB/s) - ‘MediaCenter-19.0.122.deb’ saved [38883752/38883752]
electric@electric-System-Product-Name:~/Downloads$ sudo dpkg -i MediaCenter-19.0.122.deb
dpkg: warning: downgrading mediacenter19 from 19.0.128 to 19.0.122
(Reading database ... 176223 files and directories currently installed.)
Preparing to unpack MediaCenter-19.0.122.deb ...
Unpacking mediacenter19 (19.0.122) over (19.0.128) ...
dpkg: dependency problems prevent configuration of mediacenter19:
mediacenter19 depends on libtasn1-3 (>= 2.13).
dpkg: error processing package mediacenter19 (--install):
dependency problems - leaving unconfigured
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Errors were encountered while processing:
mediacenter19
I also went to the following link and tried installing but I'm still getting the same error when installing MC: http://packages.ubuntu.com/trusty/amd64/libtasn1-6-dev/download
I'm new to Linux so I'm sure I'm doing something wrong. If anyone has a chance to give me a hand I'd be very appreciative!
-
Yes, I found that out myself. As of right now, MC can't officially be installed on Ubuntu 14.04 LTS due to Ubuntu depreciating libtasn1-3 in favor of libtasn1-6. Since Debian Wheezy, the main Linux distro MC is developed on, still supports and requires libtasn1-3 MC won't officially work. So, there's four choices here...
1) Move to Debian Wheezy or Jessie to officially install MC.
2) Wait and see if there's anything Bob can do. The worst case scenario here, besides non-support of Ubuntu, is the need of a secondary .deb file for Ubuntu/libtasn1-6.
3) Stay on an older build of Ubuntu (not really recommended).
4) Take matters into your own hands by unpacking the .deb file, editing the control file changing the libtasn1-3 dependency to libtasn1-6 then rebuilding it. This could potentially be frowned upon here so I won't discuss how to do this, unless administration tells me otherwise. Personally, I already worked around this issue and MC is working fine for me.
So as of right now, UBUNTU ISN'T SUPPORTED FOR MC... officially!
-
Just an FYI
I had MC 19.0.128 running on Ubuntu 13.10. I upgraded to to Ubuntu 14.04 using the software updater and instructions on the Ubuntu website (not a clean install). I did not reinstall MC and it is still working perfectly. I am a Linux noob but based on what I have been reading here it appears that the upgrade did not remove the MC dependency files (libtasn1-3) that were already installed.
P.S. the upgrade went smoothly except for one issue. I tried to get it to leave my Grub2 file alone but it ended up messing it up and I had to repair it before I could reboot.
-
Tutorial updates are inbound! :D
EDIT: Got Pulseaudio + pavucontrol stuff added.
EDIT 2: Hopefully the list of dependences is correct, didn't get to test this yet on a clean install - would be great if somebody could verify this on 64-bit and 32-bit Ubuntu 14.04!
EDIT 3: I'll hold off on adding alsacap stuff until if/when it may be added within MC.
-
i have 13.10 upgraded tp 14.04 lts
v121 was already installed
upgrade to 129-3 worked perfectly.
robert@robert-nas:~$ cd ~/Downloads
robert@robert-nas:~/Downloads$ sudo dpkg -i MediaCenter-19.0.129-3.deb
[sudo] password for robert:
(Reading database ... 173787 files and directories currently installed.)
Preparing to unpack MediaCenter-19.0.129-3.deb ...
Unpacking mediacenter19 (19.0.129-3) over (19.0.121) ...
Setting up mediacenter19 (19.0.129-3) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for mime-support (3.54ubuntu1) ...
robert@robert-nas:~/Downloads$
-
MC works well on my Ubuntu 14.04LTS box. But in order to pass a 192k file to my DAC, I have to set the alternate sample rate parameter in pulse/daemon.conf to 192000. Then to play a 96k file, I have to go in and change the alt sample rate to 96000. I'd like to use Pulse, but having to reset the rate album by album is a real pain. Is there a way to set MC for Linux up to detect and configure file by file (or, better yet, to pass files in their native formats without resampling)?
-
EDIT 2: Hopefully the list of dependences is correct, didn't get to test this yet on a clean install - would be great if somebody could verify this on 64-bit and 32-bit Ubuntu 14.04!
I just installed MC on a fresh install of 14.04, and I noticed there is a typo in the dependencies for 64-bit Ubuntu: libidn11:1386 should be libidn11:i386. I also had to install libstdc++6:i386 and its dependencies as well.
-
Corrected, thanks!
-
Updated for MC20 and its new requirements!
-
Successfully installed MediaCenter20.0.6 on Ubuntu 14.04 64-bit, and this has fixed the problem with sound card settings. Now listening to Brahms in glorious sound once again, without needing a complicated 2-PC Linux file-server/Win7 player setup on my desk. Good work, fast solution to an annoying bug. I also recently bought a Flirc USB dongle - allows me to use an existing remote to control MediaCenter -is this of interest to the user community?
-
Successfully installed MediaCenter20.0.6 on Ubuntu 14.04 64-bit, and this has fixed the problem with sound card settings. Now listening to Brahms in glorious sound once again, without needing a complicated 2-PC Linux file-server/Win7 player setup on my desk. Good work, fast solution to an annoying bug. I also recently bought a Flirc USB dongle - allows me to use an existing remote to control MediaCenter -is this of interest to the user community?
Yes. Please start a thread with details. Thank you.
-
ubuntu 14.04 lts 32 bit - installed fine but without lib32stdc++6. i ran the below command, then dropped lib32stdc++6, followed by sudo apt-get autoremove to tidy up. finally downloaded mc20 v6 and installed. no settings were retained from v19, it's currently rebuilding the library.
regards, Robert
robert@robert-nas:~$ sudo apt-get install libx11-6 libc6 libasound2 libuuid1 libssl1.0.0 libidn11 libstdc++6 libxcb1 libxau6 libxdmcp6 zlib1g libxext6 libgtk2.0-0 lib32stdc++6 xfonts-75dpi xfonts-100dpi lame
[sudo] password for robert:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package lib32stdc++6
E: Couldn't find any package by regex 'lib32stdc++6'
-
Interesting, I'll remove that from the 32-bit tutorial.
-
Oh Donkey of awesomely awesome awesomeness, I've got an edit job for you
This tutorial aims to aid users into setting up JRiver Media Center 20 onto Ubuntu 14.04 LTS systems. This tutorial does borrow ideas and parts done by InflatableMouse and his excellent Debian tutorial, so please thank him.
...
Next we need to download and install the latest Media Center build via the terminal. Copy and paste each line into the terminal (pressing enter after each line so it downloads);
cd ~/Downloads
wget http://files.JRiver.com/mediacenter/channels/[b][color=red]v19[/color][/b]/latest/MediaCenter-20.0.6.deb
sudo dpkg -i MediaCenter-20.0.6.deb
...
In the code above, v19 should read v20.
While you're in the neighbourhood, you could change the detail to refer to build 7.
Cheers and thanks for the guide - worked a treat.
;)
-
Fixed! :)
-
Updates inbound! Added Linux Mint 17 to the tutorial, updated the build links and added a tutorial on how to update Media Center 20 via the terminal.
Also Bob, looking at the dependencies, am I missing any from the list?
-
Updates inbound! Added Linux Mint 17 to the tutorial, updated the build links and added a tutorial on how to update Media Center 20 via the terminal.
Also Bob, looking at the dependencies, am I missing any from the list?
libp11-kit0
which seems to want plugins on 64 bit ubuntu anyway
p11-kit-modules
and for gnome
libp11-kit-gnome-keyring
libgl1-mesa-glx | libgl1
optional vorbis-tools and musepack-tools (for encoding those formats). Lame is also optional for the same reason.
xdg-utils (for opening a browser, etc).
-
I'm assuming for libp11-kit0, p11-kit-modules, libp11-kit-gnome-keyring and libgl1-mesa-glx the i386 packages on 64-bit is required.
-
This is my lazy auto upgrade - I have this set up as a cron job that runs every morning (UK time) at 3 am.
I have a file called "mc20v" that contains this:
v=31That file gets read in using "source" command, so the script has a starting point. It basically then loops through the next 10 versions (so 32,33,34,35,36 etc) using "wget" with --spider option to see if the file exists on the jriver server. If one is found, that number is written out to a temp file. When the loop has finished, then the temp file is checked against the number we started with. Then if a new version number has been found, that number is passed through to a 2nd script.
#!/bin/bash
me=`basename $0`
cd /home/robert/scripts
source mc20v
savedv=$v
echo "existing is v" $savedv
echo "v=$v" > mc20vtemp
for i in 1 2 3 4 5 6 7 8 9 10
do
d=`expr $v + $i`
fname="MediaCenter-20.0.$d.deb"
download="http://files.jriver.com/mediacenter/channels/v20/latest/$fname"
if [[ `wget --spider -U Mozilla/5.0 $download 2>&1 | grep '200 OK'` ]]
then
echo "$d exists"
echo "v=$d" > mc20vtemp
else
echo "$d not found"
fi
done
##read in from temp file to see if new version had been found
source mc20vtemp ## loads variable $savedv
if [ $v == $savedv ]
then
echo "stopping, no new version found"
echo "$(date) $me no new version keeping $savedv" >> mc20.log
else
echo "downloading newer version $v"
echo "$(date) $me upgrading mc20 to v$v" >> mc20.log
/bin/bash /home/robert/scripts/getmc20 "$v"
fi
"getmc20" is this: it does a recheck on the file as this was my original script for downloading a new version, after I checked the forum to see if a new version had been published. Just belt and braces in case I mistyped the number, as I would execute it by running "./getmc20 31" or whatever new version number was available.
#!/bin/bash
##init variables
me=`basename $0`
log="/home/robert/scripts/mc20.log"
mc20v="/home/robert/scripts/mc20v"
mc20email="/home/robert/scripts/mc20.email"
wgetlog="/home/robert/Downloads/wget.log"
fname="MediaCenter-20.0.$1.deb"
download="http://files.jriver.com/mediacenter/channels/v20/latest/$fname"
##
echo "getting $download"
##check if file is available remotely, if yes then proceed with download
if [[ `wget --spider -U Mozilla/5.0 $download 2>&1 | grep '200 OK'` ]]
then
echo "$1 exists, proceed with download"
##check if file already exists locally, if so then delete
if [ -f $fname ]
then
rm -rv $fname
fi
##now download new version
cd ~/Downloads
wget -U Mozilla/5.0 $download 2>$wgetlog
##check if wget was successful
if grep --quiet saved $wgetlog
then
##kill running version, install new, restart application
pkill mediacenter
##wait until it's dead before proceeding
var=0
checkmc=1
while [ $checkmc -gt 0 ]
do
checkmc=`ps -aux | grep -v grep | grep mediacenter | wc -l`
var=$((var+1))
if [ $var -gt 30 ]
then
break
fi
sleep 1
done
checkmc=`ps -aux | grep -v grep | grep mediacenter | wc -l`
if [ $checkmc -gt 0 ]
then
echo "To: xxxxxxxxxxxx@gmail.com" > $mc20email
echo "From: xxxxxxxxxxx@gmail.com" >> $mc20email
echo "Subject: mc20 upgrade to v$1 failed" >> $mc20email
echo "" >> $mc20email
echo "$(date) $me failed to pkill running mc20" >> $mc20email
ps -aux | grep -v grep | grep mediacenter >> $mc20email
ssmtp xxxxxxxxxxxx@gmail.com < $mc20email
exit 0
fi
##if we get to here then running mc20 has been killed
##install latest version
sudo dpkg -i $fname
echo "$(date) $me installed v$1" >> $log
echo "v=$1" > $mc20v
##get version info from jriver yabb forum
wget --quiet http://yabb.jriver.com/interact/index.php?board=35.0 -O yabb1.txt ## this is the main linux forum page
## drop references to other builds
sed -i '/ARM/d' yabb1.txt
sed -i '/AMD64/d' yabb1.txt
## explanation of the next line: $nextpage will be the url for the thread post. grep the title using version number (in $1) and then using " as delimiter for awk, take the 4th substring.
nextpage=`grep "JRiver Media Center 20.0.$1 for Debian" yabb1.txt | head -1 | awk 'BEGIN { FS = "\"" } ; { print $4 }'`
wget --quiet $nextpage -O yabb2.txt ## this is the post announcing a new version is available
## explanation of the next line: find the first line containing "div class = post", replace the new line / new line / 20 with |20 (20 = current version number). awk that with pipe delimiter.
## finally replace html codes for new line and ' and space and " with the real thing
grep '<div class="post">' yabb2.txt | head -1 | sed 's_<br /><br />20_|20_g' | awk 'BEGIN { FS = "|" } ; { print $2 }' | sed 's_<br />_\n_g' | sed "s_'_'_g" | sed "s_ _ _g" | sed 's_"_"_g' > yabb3.txt
##now send via email
echo "To: xxxxxxxxxxxx@gmail.com" > $mc20email
echo "From: xxxxxxxxxxxxxxx@gmail.com" >> $mc20email
echo "Subject: mc20 upgraded to v$1" >> $mc20email
echo "" >> $mc20email
echo "$(date) $me Successfully installed mc20 v$1" >> $mc20email
cat yabb3.txt >> $mc20email
ssmtp xxxxxxxxxxxxxxx@gmail.com < $mc20email
rm yabb*.txt
##launching mc20 has to be the last action
/usr/bin/mediacenter20
else
##file not found locally, abort
echo "download of" $fname "failed"
echo "$(date) $me download of $fname failed" >> $log
cat $wgetlog >> $log
fi
else
##file not available remotely, abort
echo "$1 not found remotely, aborting"
fi
The script also send me emails using ssmtp so I know if a new version has been installed overnight.
I hope someone benefits from this; I had some fun writing and improving it, and getting it to run automatically with cron, and the ssmtp was the last bit I cracked.
regards, Robert
[updated 25th Feb 2015]
script has been tweaked since the first publication here.
added the ssmtp email generation - real email addresses masked. http://www.howtogeek.com/51819/how-to-setup-email-alerts-on-linux-using-gmail/
added checking that the pkill has been successful before proceeding with the install.
added getting the version update history from the yabb forum to be included in the final email.
-
Nice. Thanks for sharing.
-
I'm assuming for libp11-kit0, p11-kit-modules, libp11-kit-gnome-keyring and libgl1-mesa-glx the i386 packages on 64-bit is required.
Yes. And it's libgl1 OR libgl1-mesa-glx
Also, I just added xdg-utils to the recommended (it allows the internet browser to be pulled up, it should be the native architecture I believe).
-
Excellent, should be up-to-date now with the dependencies. :D
-
Okay, I've updated the post with a couple things.
1) Updated the links to the current build.
2) Added a small tutorial on how to register MC20 from a license file.
3) Using copy and paste.
Enjoy!
-
THANX!
Works great with the little bother Lubuntu.
-
I have been running MC 19 in Ubuntu. I followed the instructions in this post for MC 20. It looks like it downloaded and installed, but I can still only launch MC 19 from that installation. Where do I look to find MC 20 and get an icon for it on my launch bar?
-
I have been running MC 19 in Ubuntu. I followed the instructions in this post for MC 20. It looks like it downloaded and installed, but I can still only launch MC 19 from that installation. Where do I look to find MC 20 and get an icon for it on my launch bar?
If you have both installed, then this will prove it:
robert@robert-nas:~/scripts$ ls -l /usr/bin | grep mediacenter
-rwxr-xr-x 1 root root 20987764 Aug 6 2014 mediacenter19
-rwxr-xr-x 1 root root 20089684 Feb 20 21:56 mediacenter20
And if you want to run version 20, then this will do it:
/usr/bin/mediacenter20
also see the very first post:
Now assuming all dependencies are met, you've been successful at installing Media Center 20 in Ubuntu! To start Media Center either go into the Unity dash and search for Media Center 20 or you can run it from the terminal via this command...
mediacenter20
-
Thank you for your suggestions. That brought up Media Center 20. I was looking for the icon in the applications section and could not find it. Would it show up if I deleted Media Center 19?
-
In this case, I'd recommend making a backup of your MC19 settings somewhere you can find them (like the desktop), then completely remove Media Center 19 via the Terminal. For good measure, it'd probably be a good idea to reinstall MC20 then.
-
Thank you for your suggestions.
I did get MC 20 to run from a command, but it locks up shortly afterwards.
What are the commands to use to uninstall software? I think I should remove both versions and then do a clean install of MC 20.
What is Synaptic?
-
Okay, let's make it as simple as possible for you. Just put the following into the Terminal;
sudo apt-get remove mediacenter19
That should remove Media Center 19. Remember to backup your library + settings first!
EDIT: Added tutorial for removing Media Center 19 and Media Center 20 to the first page.
-
I found Synaptic and it looks fairly straight forward.
How does one back up settings?
I need to go to a meeting for a few hours, then I'll resume with MC.
-
Thanks for your help. That should make things easy for me.
-
Yes, hope it works out for you (it should). :)
Also, I've added the APT repository tutorial for those who want to add it.
-
I was able to uninstall MC 19 and MC 20. I then used your commands to download the latest version and the install went like clockwork. I saw the icon in the applications section and the MC 20 will launch.
The only command that did not work was the one to install the license key. I did receive the .mjr file, but the system tells me it could not restore the license from that file. I checked the file and made sure I entered it correctly but no success.
Thank you for your support. You have been very helpful.
-
I just tried the code I have for registration on the Help Menu in MC, and I received a registration completed message. I checked the registration information and it shows a registered product, not a 30 day expiration. It did not show it registered to my name. I guess it won't expire. I'm ready to test drive it and see how it works.
-
I have installed and tried both MC 20.0.70 and MC 20.0.74. Both versions will not run much more that 15 to 20 minutes without crashing, frequently it will crash even sooner. Either version plays really great when it works, but with the continuous crashing, it's not usable.
Isn't there a way to capture a log from MC that could be sent in to help resolve the problem?
-
I have installed and tried both MC 20.0.70 and MC 20.0.74. Both versions will not run much more that 15 to 20 minutes without crashing, frequently it will crash even sooner. Either version plays really great when it works, but with the continuous crashing, it's not usable.
Isn't there a way to capture a log from MC that could be sent in to help resolve the problem?
Turn on logging under help. The log is in the users home directory under
.jriver/Media Center 20/Log.txt
On my system it never crashes so I suspect you have an issue with the distro and architecture you are using or perhaps a hardware issue.
The distro supported by JRiver is Debian Wheezy i386.
-
Turn on logging under help. The log is in the users home directory under
.jriver/Media Center 20/Log.txt
On my system it never crashes so I suspect you have an issue with the distro and architecture you are using or perhaps a hardware issue.
The distro supported by JRiver is Debian Wheezy i386.
Thank you for your help. Can I attach a log in a forum message? I have been running MC 19 for over months with Ubuntu 14.04 LTS and it only recently was giving me trouble over about the last month or so.
-
Turn on logging under help. The log is in the users home directory under
.jriver/Media Center 20/Log.txt
On my system it never crashes so I suspect you have an issue with the distro and architecture you are using or perhaps a hardware issue.
The distro supported by JRiver is Debian Wheezy i386.
Thank you for your help. Can I attach a log in a forum message? I have been running MC 19 for over months with Ubuntu 14.04 LTS and it only recently was giving me trouble over about the last month or so.
If you zip the file you should be able to attach the log.
I'm suspicious about your description of the problem. It sounds like a hardware error to me. I'd start with a memory test.
-
If you zip the file you should be able to attach the log.
I'm suspicious about your description of the problem. It sounds like a hardware error to me. I'd start with a memory test.
I have been thinking the old computer may be giving up. It is 9 1/2 years old and I did replace a power supply along the way. Is there a memory test function in Ubuntu?
My next thought is to try it on another computer.
-
I'd recommend grabbing the MemTest86 ISO, burning it to a CD then booting from the CD to use MemTest86.
-
I have been thinking the old computer may be giving up. It is 9 1/2 years old and I did replace a power supply along the way. Is there a memory test function in Ubuntu?
My next thought is to try it on another computer.
cat /proc/cpuinfo from a terminal.
It better support at least sse2
-
cat /proc/cpuinfo from a terminal.
It better support at least sse2
I tried to load MC 20 on my laptop (also running Ubuntu 14.04) and it will not properly load. The icon does not appear in my applications section, so I launch it with the mediacenter20 command in Terminal. The following comes up in the Terminal screen:
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Found 0 devices (devices will be listed below)
Total time: 8 ms
Result: 0
Does this mean MC 20 is incompatible with Ubuntu? When MC 20 did come up, Clicking on buttons and objects did not work properly. You had to point above the object you wanted to click on.
About a year ago, I had MC 19 running on this same laptop. I believe that was Ubuntu 13.
-
I tried to load MC 20 on my laptop (also running Ubuntu 14.04) and it will not properly load. The icon does not appear in my applications section, so I launch it with the mediacenter20 command in Terminal. The following comes up in the Terminal screen:
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(mediacenter20:6710): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Found 0 devices (devices will be listed below)
Total time: 8 ms
Result: 0
Does this mean MC 20 is incompatible with Ubuntu? When MC 20 did come up, Clicking on buttons and objects did not work properly. You had to point above the object you wanted to click on.
About a year ago, I had MC 19 running on this same laptop. I believe that was Ubuntu 13.
MC is compiled only on debian wheezy i386. Ubuntu is based on debian but is not exactly the same. I've seen that behavior on one ubuntu system, once you move the window it's fine. Don't know what the deal is. Try moving it with alt-left click and everything should sort itself out.
-
I've not seen that behaviour on my systems. Do you have all dependencies satisfied? According to the Google search I did, you can try these in a Terminal;
sudo apt-get install gtk2-engines:i386
sudo apt-get install gtk2-engines-*:i386
sudo apt-get install libgtkmm-2.4-1c2:i386
sudo apt-get install libcanberra-gtk-module:i386
That error is from missing the gtk2-engines-murrine and/or gtk2-engines-murrine:i386 package.
I think I'll add getting custom skins working on Ubuntu to the tutorial next.
-
I've not seen that behaviour on my systems. Do you have all dependencies satisfied? According to the Google search I did, you can try these in a Terminal;
sudo apt-get install gtk2-engines:i386
sudo apt-get install gtk2-engines-*:i386
sudo apt-get install libgtkmm-2.4-1c2:i386
sudo apt-get install libcanberra-gtk-module:i386
That error is from missing the gtk2-engines-murrine and/or gtk2-engines-murrine:i386 package.
I think I'll add getting custom skins working on Ubuntu to the tutorial next.
Thank you for your input. I'll give that a try.
-
I did a clean installation of Ubuntu 14.04.2 64 bit LTS GNU/Linux on my Lenovo IdeaPad Y510P notebook PC and this is what I get:
wellywu@IdeaPadY510P:~$ sudo apt-get install libx11-6:i386 libc6:i386 libasound2:i386 libuuid1:i386 libssl1.0.0:i386 libidn11:i386 libstdc++6:i386 libxcb1:i386 libxau6:i386 libxdmcp6:i386 zlib1g:i386 libxext6:i386 libgtk2.0-0:i386 libp11-kit0:i386 p11-kit-modules:i386 libgl1-mesa-glx:i386 libcanberra-gtk-module:i386 xdg-utils lib32stdc++6 xfonts-75dpi xfonts-100dpi lame vorbis-tools musepack-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
xfonts-100dpi is already the newest version.
xfonts-100dpi set to manually installed.
xfonts-75dpi is already the newest version.
xfonts-75dpi set to manually installed.
libasound2:i386 is already the newest version.
libasound2:i386 set to manually installed.
libp11-kit0:i386 is already the newest version.
libp11-kit0:i386 set to manually installed.
libstdc++6:i386 is already the newest version.
libstdc++6:i386 set to manually installed.
libx11-6:i386 is already the newest version.
libx11-6:i386 set to manually installed.
libxau6:i386 is already the newest version.
libxau6:i386 set to manually installed.
libxcb1:i386 is already the newest version.
libxdmcp6:i386 is already the newest version.
libxdmcp6:i386 set to manually installed.
libxext6:i386 is already the newest version.
libxext6:i386 set to manually installed.
zlib1g:i386 is already the newest version.
xdg-utils is already the newest version.
xdg-utils set to manually installed.
libc6:i386 is already the newest version.
libssl1.0.0:i386 is already the newest version.
libssl1.0.0:i386 set to manually installed.
libuuid1:i386 is already the newest version.
libuuid1:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
Depends: gstreamer1.0-clutter but it is not going to be installed
libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.1.3-0ubuntu0.3)
Recommends: libgl1-mesa-dri:i386 (>= 7.2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
wellywu@IdeaPadY510P:~$
-
how to fix broken packages http://askubuntu.com/questions/118749/package-system-is-broken-how-to-fix-it
You probably just need this
sudo apt-get install -f
-
Canonical upgraded the X.Org display server and client to Utopic Unicorn with Ubuntu 14.04.2 64 bit LTS GNU/Linux. Sudo apt-get -f install does not fix these broken packages because I've already tried it. I also tried Synaptic's fix broken packages and it does not fix the problem. I think that J River has to test this on a QA platform and fix their installation instructions so Media Center will completely install and work properly. Please look into this issue for me. Thank you.
-
wellywu@IdeaPadY510P:~$ sudo apt-get install libx11-6:i386 libc6:i386 libasound2:i386 libuuid1:i386 libssl1.0.0:i386 libidn11:i386 libstdc++6:i386 libxcb1:i386 libxau6:i386 libxdmcp6:i386 zlib1g:i386 libxext6:i386 libgtk2.0-0:i386 libp11-kit0:i386 p11-kit-modules:i386 libgl1-mesa-glx:i386 libcanberra-gtk-module:i386 xdg-utils lib32stdc++6 xfonts-75dpi xfonts-100dpi lame vorbis-tools musepack-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
xfonts-100dpi is already the newest version.
xfonts-100dpi set to manually installed.
xfonts-75dpi is already the newest version.
xfonts-75dpi set to manually installed.
libasound2:i386 is already the newest version.
libasound2:i386 set to manually installed.
libp11-kit0:i386 is already the newest version.
libp11-kit0:i386 set to manually installed.
libstdc++6:i386 is already the newest version.
libstdc++6:i386 set to manually installed.
libx11-6:i386 is already the newest version.
libx11-6:i386 set to manually installed.
libxau6:i386 is already the newest version.
libxau6:i386 set to manually installed.
libxcb1:i386 is already the newest version.
libxdmcp6:i386 is already the newest version.
libxdmcp6:i386 set to manually installed.
libxext6:i386 is already the newest version.
libxext6:i386 set to manually installed.
zlib1g:i386 is already the newest version.
xdg-utils is already the newest version.
xdg-utils set to manually installed.
libc6:i386 is already the newest version.
libssl1.0.0:i386 is already the newest version.
libssl1.0.0:i386 set to manually installed.
libuuid1:i386 is already the newest version.
libuuid1:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
Depends: gstreamer1.0-clutter but it is not going to be installed
libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.1.3-0ubuntu0.3)
Recommends: libgl1-mesa-dri:i386 (>= 7.2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
wellywu@IdeaPadY510P:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
wellywu@IdeaPadY510P:~$
-
wellywu@IdeaPadY510P:~$ sudo apt-get install libx11-6:i386 libc6:i386 libasound2:i386 libuuid1:i386 libssl1.0.0:i386 libidn11:i386 libstdc++6:i386 libxcb1:i386 libxau6:i386 libxdmcp6:i386 zlib1g:i386 libxext6:i386 libgtk2.0-0:i386 libp11-kit0:i386 p11-kit-modules:i386 libgl1-mesa-glx:i386 libcanberra-gtk-module:i386 xdg-utils lib32stdc++6 xfonts-75dpi xfonts-100dpi lame vorbis-tools musepack-tools
[sudo] password for wellywu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
xfonts-100dpi is already the newest version.
xfonts-100dpi set to manually installed.
xfonts-75dpi is already the newest version.
xfonts-75dpi set to manually installed.
libasound2:i386 is already the newest version.
libasound2:i386 set to manually installed.
libp11-kit0:i386 is already the newest version.
libp11-kit0:i386 set to manually installed.
libstdc++6:i386 is already the newest version.
libstdc++6:i386 set to manually installed.
libx11-6:i386 is already the newest version.
libx11-6:i386 set to manually installed.
libxau6:i386 is already the newest version.
libxau6:i386 set to manually installed.
libxcb1:i386 is already the newest version.
libxdmcp6:i386 is already the newest version.
libxdmcp6:i386 set to manually installed.
libxext6:i386 is already the newest version.
libxext6:i386 set to manually installed.
zlib1g:i386 is already the newest version.
xdg-utils is already the newest version.
xdg-utils set to manually installed.
libc6:i386 is already the newest version.
libssl1.0.0:i386 is already the newest version.
libssl1.0.0:i386 set to manually installed.
libuuid1:i386 is already the newest version.
libuuid1:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
Depends: gstreamer1.0-clutter but it is not going to be installed
libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.1.3-0ubuntu0.3)
Recommends: libgl1-mesa-dri:i386 (>= 7.2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
wellywu@IdeaPadY510P:~$ sudo apt-get install libgl1-mesa-dri:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not going to be installed
Depends: libcheese7 (>= 3.0.1) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
wellywu@IdeaPadY510P:~$ sudo apt-get install libcheese-gtk23 libcheese7
Reading package lists... Done
Building dependency tree
Reading state information... Done
libcheese-gtk23 is already the newest version.
libcheese-gtk23 set to manually installed.
libcheese7 is already the newest version.
libcheese7 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
wellywu@IdeaPadY510P:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
wellywu@IdeaPadY510P:~$
-
Ubuntu technically isn't supported by JRiver, the supported distro = Debian wheezy i386. These instructions are written by forum members not by JRiver.
What happens if you try to install mediacenter by itself, have you tried this via the apt repository?
-
I added the GnuPG signing key for JRiver and I successfully installed Media Center 20, but it doesn't work. When I try to select my Oppo Digital HA-1, it isn't listed. I have not tested to see if it will play audio or music yet. Give me a few more hours to figure this out from this point and I'll update this thread.
-
Canonical upgraded the X.Org display server and client to Utopic Unicorn with Ubuntu 14.04.2 64 bit LTS GNU/Linux. Sudo apt-get -f install does not fix these broken packages because I've already tried it. I also tried Synaptic's fix broken packages and it does not fix the problem. I think that J River has to test this on a QA platform and fix their installation instructions so Media Center will completely install and work properly. Please look into this issue for me. Thank you.
I'll try to get a VM of 14.04.2 running in the next few days to test this out. I can tell you however that it works just fine in a fresh 14.10 installation.
-
I added the GnuPG signing key for JRiver and I successfully installed Media Center 20, but it doesn't work. When I try to select my Oppo Digital HA-1, it isn't listed. I have not tested to see if it will play audio or music yet. Give me a few more hours to figure this out from this point and I'll update this thread.
Assuming your Oppo device is a DAC, if the hardware devices aren't listed your user usually isn't in the audio group.
-
Turn on logging under help. The log is in the users home directory under
.jriver/Media Center 20/Log.txt
On my system it never crashes so I suspect you have an issue with the distro and architecture you are using or perhaps a hardware issue.
The distro supported by JRiver is Debian Wheezy i386.
I did get MC 20 installed on my laptop as a check against my old tower that kept crashing. I still have the crash problem with the laptop. I did capture a log from the last crash that I attached to this post. I am running Ubuntu 14.04 and I loaded the gtk files suggested by Awesome Donkey on a post done yesterday.
Please let me know if it sheds any light on why MC crashes.
-
When I run MC 20 GNU/Linux, it freezes and I have to quit the program. I'll look into this issue more closely in the next few days to see what's going on in detail. I'll learn how to turn on logs and upload them, but what do I need to know to do this?
-
When I run MC 20 GNU/Linux, it freezes and I have to quit the program. I'll look into this issue more closely in the next few days to see what's going on in detail. I'll learn how to turn on logs and upload them, but what do I need to know to do this?
Open the Help menu. There is an option for logging. Click that and then click on the option to turn on logging. Run the program until the problem happens again, then reopen it, Click on logging from the Help menu, then on the box to Report Problem. That should put a log file on your desktop that you can attach to a post for review.
-
I can confirm the package breakage on 14.04.2 LTS. Looking into a solution now.
EDIT: The breakage occurs because of the libgl1-mesa-glx:i386 package. I'm going to remove it for the time being from the list, as MC20 seems to install and function completely fine without it (no errors or warnings).
-
That's the same exact package that broke my Codeweavers' CrossOver for Ubuntu 64 bit GNU/Linux software application.
http://www.codeweavers.com
After I performed a clean installation of Ubuntu 14.04.2 64 bit LTS GNU/Linux, CrossOver and Media Center refused to install completely. I created a support ticket with Codweavers and they're investigating this specific software package and its missing dependencies on their QA test system. They'll get back to me when they know more information.
Now, I'm running into the same missing software dependencies with Media Center 20.
There's a couple of Launchpad bug reports about this specific software package and its missing dependencies, but I have to Google it to get more specific information for you and Codeweavers.
Unfortunately, I've been permanently banned at Ubuntu Forums, but I did request to have my account re-enabled. I have to wait for Elfy the administrator at Ubuntu Forums to decide to let me back into the community or not.
-
An update, you should be able to install libgl1-mesa-glx-lts-utopic:i386 and it *should* work. This breakage is also affecting Steam it seems. I added a note for this on the first page.
-
If you zip the file you should be able to attach the log.
I'm suspicious about your description of the problem. It sounds like a hardware error to me. I'd start with a memory test.
I just got a second log from my old tower computer that was about 825 KB, too big to send. Is there an alternate way to send, or should I attempt to re create the problem with a smaller file? I ran for a couple of hours playing FLAC (all my files are FLAC) at 44/16. When I went to 192/24, it crashed as soon as I attempted to change tracks.
-
wellywu@IdeaPadY510P:~$ libgl1-mesa-glx-lts-utopic:i386
libgl1-mesa-glx-lts-utopic:i386: command not found
wellywu@IdeaPadY510P:~$ sudo apt-get install libgl1-mesa-glx-lts-utopic:i386
[sudo] password for wellywu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libgl1-mesa-glx-lts-utopic:i386 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
wellywu@IdeaPadY510P:~$ sudo apt-get install libx11-6:i386 libc6:i386 libasound2:i386 libuuid1:i386 libssl1.0.0:i386 libidn11:i386 libstdc++6:i386 libxcb1:i386 libxau6:i386 libxdmcp6:i386 zlib1g:i386 libxext6:i386 libgtk2.0-0:i386 libp11-kit0:i386 p11-kit-modules:i386 libgl1-mesa-glx:i386 libcanberra-gtk-module:i386 xdg-utils lib32stdc++6 xfonts-75dpi xfonts-100dpi lame vorbis-tools musepack-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
xfonts-100dpi is already the newest version.
xfonts-100dpi set to manually installed.
xfonts-75dpi is already the newest version.
xfonts-75dpi set to manually installed.
libasound2:i386 is already the newest version.
libasound2:i386 set to manually installed.
libidn11:i386 is already the newest version.
libidn11:i386 set to manually installed.
libp11-kit0:i386 is already the newest version.
libp11-kit0:i386 set to manually installed.
libstdc++6:i386 is already the newest version.
libstdc++6:i386 set to manually installed.
libx11-6:i386 is already the newest version.
libx11-6:i386 set to manually installed.
libxau6:i386 is already the newest version.
libxau6:i386 set to manually installed.
libxcb1:i386 is already the newest version.
libxdmcp6:i386 is already the newest version.
libxdmcp6:i386 set to manually installed.
libxext6:i386 is already the newest version.
libxext6:i386 set to manually installed.
zlib1g:i386 is already the newest version.
xdg-utils is already the newest version.
xdg-utils set to manually installed.
libc6:i386 is already the newest version.
libgtk2.0-0:i386 is already the newest version.
libgtk2.0-0:i386 set to manually installed.
libssl1.0.0:i386 is already the newest version.
libssl1.0.0:i386 set to manually installed.
libuuid1:i386 is already the newest version.
libuuid1:i386 set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
Depends: gstreamer1.0-clutter but it is not going to be installed
libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed
Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.1.3-0ubuntu0.3)
Recommends: libgl1-mesa-dri:i386 (>= 7.2)
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
wellywu@IdeaPadY510P:~$
-
Remove libgl1-mesa-glx:i386 from your list. It should work fine then. The first page has an updated Terminal command without libgl1-mesa-glx:i386 included by default.
-
It worked!
wellywu@IdeaPadY510P:~$ sudo apt-get install libx11-6:i386 libc6:i386 libasound2:i386 libuuid1:i386 libssl1.0.0:i386 libidn11:i386 libstdc++6:i386 libxcb1:i386 libxau6:i386 libxdmcp6:i386 zlib1g:i386 libxext6:i386 libgtk2.0-0:i386 libp11-kit0:i386 p11-kit-modules:i386 libcanberra-gtk-module:i386 xdg-utils lib32stdc++6 xfonts-75dpi xfonts-100dpi lame vorbis-tools musepack-tools[sudo] password for wellywu:
Sorry, try again.
[sudo] password for wellywu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
xfonts-100dpi is already the newest version.
xfonts-100dpi set to manually installed.
xfonts-75dpi is already the newest version.
xfonts-75dpi set to manually installed.
libasound2:i386 is already the newest version.
libasound2:i386 set to manually installed.
libidn11:i386 is already the newest version.
libidn11:i386 set to manually installed.
libp11-kit0:i386 is already the newest version.
libp11-kit0:i386 set to manually installed.
libstdc++6:i386 is already the newest version.
libstdc++6:i386 set to manually installed.
libx11-6:i386 is already the newest version.
libx11-6:i386 set to manually installed.
libxau6:i386 is already the newest version.
libxau6:i386 set to manually installed.
libxcb1:i386 is already the newest version.
libxdmcp6:i386 is already the newest version.
libxdmcp6:i386 set to manually installed.
libxext6:i386 is already the newest version.
libxext6:i386 set to manually installed.
zlib1g:i386 is already the newest version.
xdg-utils is already the newest version.
xdg-utils set to manually installed.
libc6:i386 is already the newest version.
libgtk2.0-0:i386 is already the newest version.
libgtk2.0-0:i386 set to manually installed.
libssl1.0.0:i386 is already the newest version.
libssl1.0.0:i386 set to manually installed.
libuuid1:i386 is already the newest version.
libuuid1:i386 set to manually installed.
The following extra packages will be installed:
libao4 libcanberra-gtk0:i386 libcanberra0:i386 libcue1 libreplaygain1
libtdb1:i386
Suggested packages:
libesd0 libesd-alsa0 libcanberra-pulse:i386
The following packages will be REMOVED:
lame:i386 vorbis-tools:i386
The following NEW packages will be installed:
lame lib32stdc++6 libao4 libcanberra-gtk-module:i386 libcanberra-gtk0:i386
libcanberra0:i386 libcue1 libreplaygain1 libtdb1:i386 musepack-tools
p11-kit-modules:i386 vorbis-tools
0 upgraded, 12 newly installed, 2 to remove and 0 not upgraded.
Need to get 743 kB of archives.
After this operation, 2,471 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ubuntu.mirror.constant.com/ trusty/main libao4 amd64 1.1.0-2ubuntu2 [31.5 kB]
Get:2 http://ubuntu.mirror.constant.com/ trusty/main libtdb1 i386 1.2.12-1 [38.6 kB]
Get:3 http://ubuntu.mirror.constant.com/ trusty/main libcanberra0 i386 0.30-0ubuntu3 [35.0 kB]
Get:4 http://ubuntu.mirror.constant.com/ trusty/main libcanberra-gtk0 i386 0.30-0ubuntu3 [7,584 B]
Get:5 http://ubuntu.mirror.constant.com/ trusty/universe libreplaygain1 amd64 1.0~r475-1 [9,510 B]
Get:6 http://ubuntu.mirror.constant.com/ trusty/universe lame amd64 3.99.5+repack1-3ubuntu1 [48.5 kB]
Get:7 http://ubuntu.mirror.constant.com/ trusty/main libcanberra-gtk-module i386 0.30-0ubuntu3 [8,868 B]
Get:8 http://ubuntu.mirror.constant.com/ trusty/universe libcue1 amd64 1.4.0-1 [25.2 kB]
Get:9 http://ubuntu.mirror.constant.com/ trusty/universe musepack-tools amd64 2:0.1~r459-1ubuntu3 [82.8 kB]
Get:10 http://ubuntu.mirror.constant.com/ trusty/main vorbis-tools amd64 1.4.0-1ubuntu3 [129 kB]
Get:11 http://ubuntu.mirror.constant.com/ trusty/main lib32stdc++6 amd64 4.8.2-19ubuntu1 [261 kB]
Get:12 http://ubuntu.mirror.constant.com/ trusty/main p11-kit-modules i386 0.20.2-2ubuntu2 [66.1 kB]
Fetched 743 kB in 0s (950 kB/s)
(Reading database ... 219136 files and directories currently installed.)
Removing lame (3.99.5+repack1-3ubuntu1) ...
Removing vorbis-tools (1.4.0-1ubuntu3) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Selecting previously unselected package libao4:amd64.
(Reading database ... 219112 files and directories currently installed.)
Preparing to unpack .../libao4_1.1.0-2ubuntu2_amd64.deb ...
Unpacking libao4:amd64 (1.1.0-2ubuntu2) ...
Selecting previously unselected package libtdb1:i386.
Preparing to unpack .../libtdb1_1.2.12-1_i386.deb ...
Unpacking libtdb1:i386 (1.2.12-1) ...
Selecting previously unselected package libcanberra0:i386.
Preparing to unpack .../libcanberra0_0.30-0ubuntu3_i386.deb ...
Unpacking libcanberra0:i386 (0.30-0ubuntu3) ...
Selecting previously unselected package libcanberra-gtk0:i386.
Preparing to unpack .../libcanberra-gtk0_0.30-0ubuntu3_i386.deb ...
Unpacking libcanberra-gtk0:i386 (0.30-0ubuntu3) ...
Selecting previously unselected package libreplaygain1:amd64.
Preparing to unpack .../libreplaygain1_1.0~r475-1_amd64.deb ...
Unpacking libreplaygain1:amd64 (1.0~r475-1) ...
Selecting previously unselected package lame.
Preparing to unpack .../lame_3.99.5+repack1-3ubuntu1_amd64.deb ...
Unpacking lame (3.99.5+repack1-3ubuntu1) ...
Selecting previously unselected package libcanberra-gtk-module:i386.
Preparing to unpack .../libcanberra-gtk-module_0.30-0ubuntu3_i386.deb ...
Unpacking libcanberra-gtk-module:i386 (0.30-0ubuntu3) ...
Selecting previously unselected package libcue1.
Preparing to unpack .../libcue1_1.4.0-1_amd64.deb ...
Unpacking libcue1 (1.4.0-1) ...
Selecting previously unselected package musepack-tools.
Preparing to unpack .../musepack-tools_2%3a0.1~r459-1ubuntu3_amd64.deb ...
Unpacking musepack-tools (2:0.1~r459-1ubuntu3) ...
Selecting previously unselected package vorbis-tools.
Preparing to unpack .../vorbis-tools_1.4.0-1ubuntu3_amd64.deb ...
Unpacking vorbis-tools (1.4.0-1ubuntu3) ...
Selecting previously unselected package lib32stdc++6.
Preparing to unpack .../lib32stdc++6_4.8.2-19ubuntu1_amd64.deb ...
Unpacking lib32stdc++6 (4.8.2-19ubuntu1) ...
Selecting previously unselected package p11-kit-modules:i386.
Preparing to unpack .../p11-kit-modules_0.20.2-2ubuntu2_i386.deb ...
Unpacking p11-kit-modules:i386 (0.20.2-2ubuntu2) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Setting up libao4:amd64 (1.1.0-2ubuntu2) ...
Setting up libtdb1:i386 (1.2.12-1) ...
Setting up libcanberra0:i386 (0.30-0ubuntu3) ...
Setting up libcanberra-gtk0:i386 (0.30-0ubuntu3) ...
Setting up libreplaygain1:amd64 (1.0~r475-1) ...
Setting up lame (3.99.5+repack1-3ubuntu1) ...
Setting up libcanberra-gtk-module:i386 (0.30-0ubuntu3) ...
Setting up libcue1 (1.4.0-1) ...
Setting up musepack-tools (2:0.1~r459-1ubuntu3) ...
Setting up vorbis-tools (1.4.0-1ubuntu3) ...
Setting up lib32stdc++6 (4.8.2-19ubuntu1) ...
Setting up p11-kit-modules:i386 (0.20.2-2ubuntu2) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
wellywu@IdeaPadY510P:~$ sudo ubuntu-tweak
compizconfig - Info: Backend : ini
compizconfig - Info: Integration : true
compizconfig - Info: Profile : default
TypeError: can't convert return value to desired type
/usr/bin/ubuntu-tweak:123: Warning: g_value_copy: assertion 'G_IS_VALUE (src_value)' failed
app.run(sys.argv)
/usr/bin/ubuntu-tweak:123: Warning: g_value_reset: assertion 'G_IS_VALUE (value)' failed
app.run(sys.argv)
/usr/bin/ubuntu-tweak:123: Warning: g_value_unset: assertion 'G_IS_VALUE (value)' failed
app.run(sys.argv)
wellywu@IdeaPadY510P:~$
Now, I have to test J River Media Center 20 64 bit. I'll do this later tonight or tomorrow. I didn't get any sleep last night because I was busy.
-
There ya go, enjoy! :) You should try running mediacenter20 from the Terminal first to see if you get any errors there. If there's no errors, run it normally.
-
JRiver Media Center 20 64 bit GNU/Linux seems to be working right now. I'm playing Diana Krall's Quiet Nights FLAC music album at 16 bits 44.1 kHz. It has not crashed yet. However, I still can not select my Oppo Digital HA-1 DAC and headphone amplifier in the Tools -> Options -> Audio Device. I have to use the sound icon in Ubuntu Unity to select my Oppo Digital HA-1 in order to route music playback through JRiver Media Center 20 64 bit GNU/Linux. How do I fix this?
Here's my audiophile headphone system:
Oppo Digital HA-1 DAC & headphone amplifier
CEntrance HiFi-M8 LX XL4 portable DAC & headphone amplifier
Sennheiser HD-800
Shure SE-846 CL quad driver earphones
$4,400.00 USD
The sound quality sounds no different from DeadBeef, Clementine, etc. Right now, JRiver Media Center 20 64 bit GNU/Linux seems to be a bit buggy. It's nowhere near the Microsoft Windows 8.1 build. I understand that video and picture playback are not currently supported in the early GNU/Linux build, correct? What else do I need to know?
I may purchase this software product for my birthday next month. It seems to be a good investment and I strongly prefer JRiver Media Center for its advanced unique features and capabilities. The price is affordable.
-
Okay...
However, I still can not select my Oppo Digital HA-1 DAC and headphone amplifier in the Tools -> Options -> Audio Device. I have to use the sound icon in Ubuntu Unity to select my Oppo Digital HA-1 in order to route music playback through JRiver Media Center 20 64 bit GNU/Linux. How do I fix this?
There's several things you can try here. First, open a Terminal and input the following for alsacap then post the results here;
/usr/lib/jriver/Media\ Center\ 20/alsacap
Second, you can try going through every device listed under Tools -> Options -> Audio Device until you find the correct one for your Oppo.
The sound quality sounds no different from DeadBeef, Clementine, etc.
And that's a bad thing? :P Sound in MC is of the highest quality available in Linux (ALSA/PulseAudio).
Right now, JRiver Media Center 20 64 bit GNU/Linux seems to be a bit buggy.
It can be at times, but as anything it's a work-in-progress. I find it's pretty stable for me, but then again I use it as audio only (for now).
It's nowhere near the Microsoft Windows 8.1 build.
Nope, Linux is a completely different beast compared to Windows (or Mac) which required a lot of work porting from Windows to Linux and Mac.
I understand that video and picture playback are not currently supported in the early GNU/Linux build, correct?
Video support has been added, but keep in mind it doesn't work the same as the Windows version so there may be functionality missing (e.g. theater view). Again, another work-in-progress. I believe they're working on image support, not sure though. I also think they're working on theater view for Linux and Mac.
What else do I need to know?
Best advice is to keep track of the changelogs for new builds as they come. They add new features at random.
-
Turn on logging under help. The log is in the users home directory under
.jriver/Media Center 20/Log.txt
On my system it never crashes so I suspect you have an issue with the distro and architecture you are using or perhaps a hardware issue.
The distro supported by JRiver is Debian Wheezy i386.
I sent you a log from my laptop earlier today.
I was able to get 2 logs off my old tower computer. My experience today was that it could play for a couple of hours running some FLAC files at 44/16. When I loaded a 192/24 file, it started to play, then crashed when I attempted to switch tracks. The second time I attempted to reload the 192/24 file, it crashed again. It's now running a 44/16 file and running fine.
Please let me know anything you can gain from these logs.
-
I sent you a log from my laptop earlier today.
I was able to get 2 logs off my old tower computer. My experience today was that it could play for a couple of hours running some FLAC files at 44/16. When I loaded a 192/24 file, it started to play, then crashed when I attempted to switch tracks. The second time I attempted to reload the 192/24 file, it crashed again. It's now running a 44/16 file and running fine.
Please let me know anything you can gain from these logs.
Your output device in the MC audio configuration is???
-
I wanted to install a multi room audio system and wanted to give JRiver a try.
I have succeeded to install JRiver 20.0.74 on an old PC (Q6600 / 4G Ram 128 GB SSD) with two sound cards (one Intel HDA and one Xonar ST/H6 ) on Ubuntu 14.04.2 LTS 64-bit without to much problems
I created a permanent mounted network connections to my music servers (one Ubuntu 14.04 and one Windows 7) and created three libraries (one on the local disk and the others on the mounted network drives (which actually shouldn't make any difference) and al that went fine too.
Was able to create 10 zones (3 stereo + 2 mono zones on Xonar + 3 stereo + 2 mono zones on the Intel)
Everything seems to work as expected I can link zones within and across the two sound cards and all that seems to work as well.
Even streaming to my PS-Audio DirectStream DAC seems to work (With the exception of the DSD format I still have to look into that), and even the rubbish Onkyo TX-NR717 (they all seem somehow to die just after the warranty expires) it seem to work flawlessly.
For the time being there are I seem sometimes to lose the playlists I created with my internet radio URL's (By the way you cannot copy/paste into the "File/Open URL/Open Streaming File" Drop down field which is very unfortunate. Luckily it keeps the old entries in the drop down list).
And there are the random crashes of MC20. It sometimes just disappears. By the way it would be nice, to be able to have the (huge) log files on a configurable path (as my SSD is only 128GB) so that I can write it on the HDD (on which he local music files are stored too)
I do not know if enabling the log file would be helpful I will give it a try.
Taking into account that this is an under development system its fairly stable I must say (I have seen much worse in my 35 Years as system software developer.
And also, I know, it should be on a Debian Wheezy 32-bit distro and not on a Ubuntu 64 bit, but the Ubuntu is the most widely use distro by far so for commercial reasons (as this is a paid for package) it would preferable if it would also be fully supported on Ubuntu.
-
Your output device in the MC audio configuration is???
If I understand your question, MC configuration was set using the toolbar as follows: Tools>Options>Media Network>Add or configure DLNA Servers. The settings on that screen are:
Audiophile 24-bit DAC
Mode: Specified output format
Format: PCM 24 Bit
Under Advanced, Stereo downmix is checked.
Sample Rate: Same as Source
The window from DSP studio has no output encoding and Channels shows Source number of channels.
The output is going over my network to a JRiver id. On the id, the only change was to set the output to USB. It has a power supply, Cat 6 network cable, and a USB that connects to a PS Audio DirectStream DAC.
I just received the id on Feb 20. Is the software on it registered before shipping, or do I need to do that? I did not receive a code, so I assumed it was registered.
-
Your output device in the MC audio configuration is???
I neglected to mention on my last post that I am running MC 20.0.70. As I am posting, I have a 96/24 FLAC file running and it plays fine, just as well as a 44/16.
-
I wanted to install a multi room audio system and wanted to give JRiver a try.
I have succeeded to install JRiver 20.0.74 on an old PC (Q6600 / 4G Ram 128 GB SSD) with two sound cards (one Intel HDA and one Xonar ST/H6 ) on Ubuntu 14.04.2 LTS 64-bit without to much problems
I created a permanent mounted network connections to my music servers (one Ubuntu 14.04 and one Windows 7) and created three libraries (one on the local disk and the others on the mounted network drives (which actually shouldn't make any difference) and al that went fine too.
Was able to create 10 zones (3 stereo + 2 mono zones on Xonar + 3 stereo + 2 mono zones on the Intel)
Everything seems to work as expected I can link zones within and across the two sound cards and all that seems to work as well.
Even streaming to my PS-Audio DirectStream DAC seems to work (With the exception of the DSD format I still have to look into that), and even the rubbish Onkyo TX-NR717 (they all seem somehow to die just after the warranty expires) it seem to work flawlessly.
For the time being there are I seem sometimes to lose the playlists I created with my internet radio URL's (By the way you cannot copy/paste into the "File/Open URL/Open Streaming File" Drop down field which is very unfortunate. Luckily it keeps the old entries in the drop down list).
And there are the random crashes of MC20. It sometimes just disappears. By the way it would be nice, to be able to have the (huge) log files on a configurable path (as my SSD is only 128GB) so that I can write it on the HDD (on which he local music files are stored too)
I do not know if enabling the log file would be helpful I will give it a try.
Taking into account that this is an under development system its fairly stable I must say (I have seen much worse in my 35 Years as system software developer.
And also, I know, it should be on a Debian Wheezy 32-bit distro and not on a Ubuntu 64 bit, but the Ubuntu is the most widely use distro by far so for commercial reasons (as this is a paid for package) it would preferable if it would also be fully supported on Ubuntu.
Greetings Percy.
I also have a PS Audio DirectStream DAC. It's a really great DAC, and will be even better when they perfect the Bridge. I've been waiting for 4 1/2 years.
I am also experiencing MC 20 crashes, and have sent some logs. I would encourage you to also send logs as it could help them make improvements.
Mine runs with Ubuntu 14.04 LTS.
-
If I understand your question, MC configuration was set using the toolbar as follows: Tools>Options>Media Network>Add or configure DLNA Servers. The settings on that screen are:
Audiophile 24-bit DAC
Mode: Specified output format
Format: PCM 24 Bit
Under Advanced, Stereo downmix is checked.
Sample Rate: Same as Source
The window from DSP studio has no output encoding and Channels shows Source number of channels.
The output is going over my network to a JRiver id. On the id, the only change was to set the output to USB. It has a power supply, Cat 6 network cable, and a USB that connects to a PS Audio DirectStream DAC.
I just received the id on Feb 20. Is the software on it registered before shipping, or do I need to do that? I did not receive a code, so I assumed it was registered.
Actually I was asking about the settings in MC where the audio output device is connected, in this case, the Id.
If the Id is your only or primary output device I would change the DLNA server settings to use original format. With very few exceptions, the Id can play anything that the MC server PC can play. The output format settings are designed to deal with the usual DLNA devices that play a small fraction of the formats supported by the Id.
If there are limitations with the output device on the Id as far as sample rates and number of channels are concerned you should use the DSP settings on the Id to handle that.
-
Actually I was asking about the settings in MC where the audio output device is connected, in this case, the Id.
If the Id is your only or primary output device I would change the DLNA server settings to use original format. With very few exceptions, the Id can play anything that the MC server PC can play. The output format settings are designed to deal with the usual DLNA devices that play a small fraction of the formats supported by the Id.
If there are limitations with the output device on the Id as far as sample rates and number of channels are concerned you should use the DSP settings on the Id to handle that.
What are the default DLNA server settings on the id? Are there differences in MC as it's loaded on the id vs. downloading to a computer? The reason it puzzles me is if I switch from MC on the old tower computer to the integrated Twonky on my NAS drive, all files sent to the id will play. If I look on my MC server, under the DSP settings, the table shows frequencies all the way up to 384K with output the same as input.
Have you had a chance to look at the log files I sent to see what they reveal? Does the id ship with the loaded software registered?
-
What are the default DLNA server settings on the id? Are there differences in MC as it's loaded on the id vs. downloading to a computer? The reason it puzzles me is if I switch from MC on the old tower computer to the integrated Twonky on my NAS drive, all files sent to the id will play. If I look on my MC server, under the DSP settings, the table shows frequencies all the way up to 384K with output the same as input.
Have you had a chance to look at the log files I sent to see what they reveal? Does the id ship with the loaded software registered?
We are still talking basics here. No need to look at the log files yet.
Did you configure the MediaCenter that provides the files to the Id to play as I suggested?
Unless you are using the Id as a DLNA server which it doesn't sound like you are, there is no need to check the DLNA server settings on the Id.
I was referring to the audio settings on the Id which it seems you answered, your DSP studio isn't changing anything.
You should check the actual capabilities of your USB device and match the DSP studio settings on the Id to it. The Id's DSP default settings are for the on board audio hardware.
-
We are still talking basics here. No need to look at the log files yet.
Did you configure the MediaCenter that provides the files to the Id to play as I suggested?
Unless you are using the Id as a DLNA server which it doesn't sound like you are, there is no need to check the DLNA server settings on the Id.
I was referring to the audio settings on the Id which it seems you answered, your DSP studio isn't changing anything.
You should check the actual capabilities of your USB device and match the DSP studio settings on the Id to it. The Id's DSP default settings are for the on board audio hardware.
I was confused from you last response thinking you were telling me to change settings on my id. I did change the Media Center running on my old tower as you suggested, and it now works as it should. That is my server computer. The id is the renderer out in my rec room with the audio gear.
Some months in the future, I plan to change the role of the id to being a server. It depends on when PS Audio releases the Bridge 2 that they are now beta testing. The Bridge 1 cannot play gapless, or 192/24 files smoothly. The id does both very well. I would have to put it down as one of the best audio bargains I bought.
-
This weekend I'm going to start redoing parts of the tutorial to reflect the easier installation procedure via the APT repositories and the addition of the 64-bit (test) builds. I also plan on adding a quick tutorial on how to add skins to the Linux version of MC.
-
My Problem: Installation works on 14.04 from terminal like described (the 4 commands with all the sudos...), but starting then with only "mediacenter20" (without "sudo") gives a "Database Read-Only" box and also a long list of errors in the terminal concerning missing files etc. The same happenes, when I open the program from the icon. Database is empty and there are no songs etc.
When I start the program in a terminal with "sudo..." everything seems to be O. K., resp. I can use my music, send it to a UPnP client etc. The program continues as a primary task and writes also permanently comments in the terminal window, which I can't close during that time. When I put an "&" at the end of the starting command, to set the task to background, the program stoppes directly.
The Problem seems to be that the installation uses the root home directory (/root/.jriver/...) while the program would use my personal home. There are hidden subdirectories under my home directory (/home/user/.jriver/...), but the owner is root also, so that there is no possibility for the program to write to these directories.
I would like to use the program just with the icon. I tried different times to remove and install again, but found no way to solve this. Any idea?
-
My Problem: Installation works on 14.04 from terminal like described (the 4 commands with all the sudos...), but starting then with only "mediacenter20" (without "sudo") gives a "Database Read-Only" box and also a long list of errors in the terminal concerning missing files etc. The same happenes, when I open the program from the icon. Database is empty and there are no songs etc.
When I start the program in a terminal with "sudo..." everything seems to be O. K., resp. I can use my music, send it to a UPnP client etc. The program continues as a primary task and writes also permanently comments in the terminal window, which I can't close during that time. When I put an "&" at the end of the starting command, to set the task to background, the program stoppes directly.
The Problem seems to be that the installation uses the root home directory (/root/.jriver/...) while the program would use my personal home. There are hidden subdirectories under my home directory (/home/user/.jriver/...), but the owner is root also, so that there is no possibility for the program to write to these directories.
I would like to use the program just with the icon. I tried different times to remove and install again, but found no way to solve this. Any idea?
You shouldn't run as root.
Run as the normal user and fix your ownership/permissions issues.
The .jriver directory is where the settings are. This is normal unix convention.
The reason you are getting a read-only error is because of the ownership/permissions.
Assuming your user really is named "user" you should be able to do a terminal window as that user and fix the permissions thusly:
cd ~user
sudo chown -R user:user .jriver
-
thanks, Bob! ;D - Perfect like always. That did it. ;D
-
I'm a week late, but I finally had the time to rewrite the tutorial - there's now one tutorial for both 64-bit and 32-bit (using the 64-bit test builds as default for 64-bit). It's been simplified and for now it'll only focus on the latest builds but I do plan on adding stable builds to the tutorial at some point. Enjoy!
-
Hi,
I am using Master License on 2 PCs with dual boot Windows 7 64bit and Linux (Mint 17 Cinnamon on one, Xubuntu 14 on the other, both 64-bit).
Currently, Linux is secondary OS but I tend to use it more and more, hence the purchase of the Master License.
MC20 was licensed on both OSes.
The problem: suddenly, today, when I tried to start MC20 (under Mint 17), it told me that "The trial period has expired"!!!
I went and restored the license by manually inputting the Registration Code. It accepted it but, when I run the MC20 again, it says the same. And I got the message that my remaining count of restore is 16, (-1 from before).
So, I tried to use the .mjr file, as per your instructions and it says:"Could not restore license from file /home/scas/Downloads/Media Center20 Master-285036.mjr" which is the same message as if you give it the wrong file name or location.
I even tried to open the .mjr file from the folder with "Open with" typing mediacenter20 /RestoreFromFile: it did not complain, but the MC20 still says "The trial period has expired"...
-
The Master License won't work on older versions. Please try the latest from the top of this board.
-
The Master License won't work on older versions. Please try the latest from the top of this board.
OK, but it doesn't add-up (at least in my mind):
1. the Master License seemed to work when I installed it.
2. Even today, when I typed the Registration key, it said it was successful...
3. After that, earlier today, I re-installed using the Software Manager (without removing the previous version, if that is necessary). Installation worked without any complaint and the details of the current installed version says 20.0.84.
I am at lost here...
Anyways, should I try to re-enter the key by hand once more? (I am just worried that I am spending counts I might need later in the year).
Please advise on
-
That version will work with the Master License.
Try entering it again. Don't worry about restores. We can reset them if you run out.
-
I am sorry to report that I tried it once more and got the same result
I received an email that says
...
You have recently restored a licence for Media Center 20 Master. There are 20 restores available in each 12 month period. There are 14 restores remaining at this time.
The restore activates Media Center and installs the license automatically.
...
But when I start the app, it gives me the cold shoulder again: "The trial period has expired"...
Please help.
PS: Also, is there any cure for the ugly fonts and looks of the GUI in Linux?
-
You may be able to select the font under Options for Tree and View. I'm not sure.
Bob may be able to help with the license issue tomorrow.
-
Looking forward to finding a solution. Thank you for trying to help me.
I will have a look at the Xubuntu installation to see what is happening there.
-
Did something change in your hardware/network setup?
-
No. No changes.
On the same machine, the Windows (7) installation does not present any problems (yet?). Actually, I am posting this from within the mc20.
A bit of background:
This is a laptop and for the time being, I am using the MediaCenter standalone, mobile where I go, trying to learn it and see how I can better use my music collection. I have copied a small subset of my library on a mobile HDD to move it around with me and see how it goes. Because I want to migrate most of my activity on Linux, I have a multi boot installation.
I did not have the time to check what happened with the other Linux install I have.
I will update
-
I am sorry to report that I tried it once more and got the same result
I received an email that says
...
You have recently restored a licence for Media Center 20 Master. There are 20 restores available in each 12 month period. There are 14 restores remaining at this time.
The restore activates Media Center and installs the license automatically.
...
But when I start the app, it gives me the cold shoulder again: "The trial period has expired"...
Please help.
PS: Also, is there any cure for the ugly fonts and looks of the GUI in Linux?
Sounds to me like you have a permissions issue.
You didn't run as root at some point did you?
Check the permissions and owner of the .jriver folder (and the folders/files underneath it) in the users home directory.
As for fonts, pcf fonts are the only supported type at this time.
Since you aren't running on the supported linux distro it's up to you to make sure the correct fonts are installed.
In debian this is xfonts-75dpi
To check, from a terminal window do:
xlsfonts | grep -- "-b&h-lucida-medium-r-normal-sans-12-120-75-75-p-71-iso10646-1"
You should see at least one line that matches -b&h-lucida-medium-r-normal-sans-12-120-75-75-p-71-iso10646-1
-
I too have the same or similar problem as scas. Fresh install of mint 17.1 on pc. Followed the instructions in the first post to the letter and all worked as expected. Came to install my master licence, by putting my code in the registration window, which was accepted, but MC still said not registered. Received a mjr file by email, copied it to the mint machine, ran the command to register it and got the same could not use file message.
MC still says not registered. V20.0.84 on mint 17.1
The whole mc install was done as user admin, an administrator, the only user on the machine apart from root.
Complete Linux first timer here. I found a ./JRiver directory under home/admin, it and all the sub folders have appear to have the correct permissions as admin admin appears in a list of all the files and folders. The mjr file is also owned by admin.
-
Tutorial updated to include support for Ubuntu 15.04. 15.04 lacks libgcrypt11 so I added a workaround to get it working.
-
Hello,
I'm a little bit stupid... ;)
A few hours ago I've installed Mediacenter20 and played a little bit around with it. Because I couldn't change the very small fonts I removed .jriver-directory - and the trouble began. Trial period has expired - ok, I ordered an extended trial. The key was accepted in the dialog, but when I start MC again, every time I got the same hint: Trial ... expired.
What's going wrong?
Please excuse my poor english...
TIA
-
Sadly, this seems to be an issue on Linux and Mac - once the trial expires (regardless if time's up or if the install was tampered with) it's expired with no way to get another trial (outside of reformatting and reinstalling Linux) even if you attempt the extended trial (due to some bug, perhaps?).
-
The trial extension works from day 30 to day 45. Then it ceases to work. We could do a better job of communicating that.
-
Sadly, this seems to be an issue on Linux and Mac - once the trial expires (regardless if time's up or if the install was tampered with) it's expired with no way to get another trial (outside of reformatting and reinstalling Linux) even if you attempt the extended trial (due to some bug, perhaps?).
I think there is an issue with the extension on linux and Mac.
-
Dropped Ubuntu 14.10 in favor of the newly released Ubuntu 15.04.
-
I already own the Windows license, would like to convert one of my laptops to Linux. How I can upgrade to Master License?
-
From the latest version of MC20, you can purchase a Master License for $24.98, if you have an MC20 license for Windows.
-
I see by the caption at the top of the page that Mint and Ubuntu is not officially supported. I understand this has been this way for a while, but find this somewhat disconcerting.
Media Center 20 for Linux is developed on Debian Wheezy 32-bit - support for distros other than Wheezy 32-bit, like Ubuntu/Mint is considered experimental and not officially supported!
Ubuntu and Mint are the two most popular distro's . Yet I did notice that Debian was in 3rd place according to DistroWatch web site. Even with Debian also being a popular distro, I still believe that Mint and Ubuntu are in more use by your "average Joe" user. I like the fact that it comes with all the codec's and video drivers I already need.
It just seems to make more sense to me that you should be directly supporting the most popular distros without having to apply a bunch of patches ( which I already did ). To get the software to behave properly.
Anyway my 2 cents, if I have repeated any previous discussions on this I apologize. Thanks for reading.
-
I think there's a small error in the guide above (in the license installation section). You advise using the following command if the .mjr file is in the Downloads directory:
mediacenter20 /RestoreFromFile "~/Downloads/Media Center20 Linux-YYYYYY.mjr"
But tilde expansion doesn't work when double quoted. It should probably be
mediacenter20 /RestoreFromFile ~/Downloads/"Media Center20 Linux-YYYYYY.mjr"
I just spotted it while helping someone with a license install over here: http://yabb.jriver.com/interact/index.php?topic=97433
-
I see by the caption at the top of the page that Mint and Ubuntu is not officially supported. I understand this has been this way for a while, but find this somewhat disconcerting.
Ubuntu and Mint are the two most popular distro's . Yet I did notice that Debian was in 3rd place according to DistroWatch web site. Even with Debian also being a popular distro, I still believe that Mint and Ubuntu are in more use by your "average Joe" user. I like the fact that it comes with all the codec's and video drivers I already need.
It just seems to make more sense to me that you should be directly supporting the most popular distros without having to apply a bunch of patches ( which I already did ). To get the software to behave properly.
Anyway my 2 cents, if I have repeated any previous discussions on this I apologize. Thanks for reading.
I'll just reiterate the logic on this.
Ubuntu and Mint are supersets of Debian.
Building on those platforms specifically will not create a build that can be run on Debian.
It also would make it much more difficult to run on non-Debian based builds (ie OpenSuse, Fedora, etc).
We need to minimize the number of different linux builds that we have to maintain. In my opinion there are already too many.
-
Bob and I talked about this again this morning, and I agree with his thinking. Maybe some day we will do builds for more distros, but it won't be any time soon.
-
Hi All,
I'm running Ubuntu 14.04.2 and performed all the steps as mentioned on the first page until getting mc20. When I try to do step "sudo apt-get install mediacenter20" I get a nice message saying "Unable to locate package mediacenter20"
Since I'm not a linux expert I'm at a stand still here, your help is very welcome !
-
I think there's a small error in the guide above (in the license installation section). You advise using the following command if the .mjr file is in the Downloads directory:
Yes, you're right. Corrected, thanks! :)
Bob and I talked about this again this morning, and I agree with his thinking. Maybe some day we will do builds for more distros, but it won't be any time soon.
Honestly, I'd say the current Debian build is already enough for Ubuntu and Mint as well. Besides using different window managers (Unity, Cinnamon, MATE, Xfce, GNOME, etc.), they're really not too different. There is a couple potential sticks in the mud in the future, Mir and Wayland replacing X. I'm not sure if XMir and XWayland is enough to get MC running on Mir or Wayland or not, it's something that may need tested. But other than the various window managers and X replacements, yeah, I think the Debian build is enough for Ubuntu and Mint.
The other issue is the potential difference in required dependencies. Setting up a Launchpad PPA to easily handle this would be the ideal solution here. But that adds another level of needing to maintain. I thought about trying to set one up myself (assuming its okay with you guys) and maintaining it by myself or with others as a team if anyone's willing. I've never setup a PPA before, but I'd be willing to try and test out the various Ubuntu and Mint configurations in virtual machines. Or if you guys want to setup the PPA to start out and I'd be willing to update it for new builds for you guys, I could do that too. :)
-
Yes, you're right. Corrected, thanks! :)
Honestly, I'd say the current Debian build is already enough for Ubuntu and Mint as well. Besides using different window managers (Unity, Cinnamon, MATE, Xfce, GNOME, etc.), they're really not too different. There is a couple potential sticks in the mud in the future, Mir and Wayland replacing X. I'm not sure if XMir and XWayland is enough to get MC running on Mir or Wayland or not, it's something that may need tested. But other than the various window managers and X replacements, yeah, I think the Debian build is enough for Ubuntu and Mint.
The other issue is the potential difference in required dependencies. Setting up a Launchpad PPA to easily handle this would be the ideal solution here. But that adds another level of needing to maintain. I thought about trying to set one up myself (assuming its okay with you guys) and maintaining it by myself or with others as a team if anyone's willing. I've never setup a PPA before, but I'd be willing to try and test out the various Ubuntu and Mint configurations in virtual machines. Or if you guys want to setup the PPA to start out and I'd be willing to update it for new builds for you guys, I could do that too. :)
Could you explain how the launchpad ppa works and how it's different than an apt repository?
-
Information on setting up a Launchpad PPA for Ubuntu (https://help.launchpad.net/Packaging/PPA).
More-or-less a PPA repository is the same as an apt repository except for some differences. The main benefits to a PPA are having missing dependencies automatically installed regardless of arch used, specifying specific dependencies for certain Ubuntu releases (e.g. Trusty has an extra dependency whereas Vivid doesn't). Might be able to get ARM builds this way too. But ultimately it probably doesn't really matter, just need to account for the LTS and latest Ubuntu releases.
Actually, I've been thinking about splitting this tutorial off into three separate forum topics (instead of having one topic); one tutorial topic for Ubuntu LTS, one for the latest Ubuntu release and one more for Linux Mint. I think I need to do this finally - this topic will become the Ubuntu latest topic. Scratch that, I deleted the split off tutorials and was able to merge them all back into one for the time being. Was also able to remove the list of dependencies as it seems they'll be installed alongside mediacenter20! Also 32-bit builds *may* work now, but it needs major testing!
I need to redo my two Ubuntu test VMs again to test the Jessie builds in 14.04.2 and 15.04 cleanly - I'd also take the opportunity to test more of the window manager things noted here. Done this, tested clean installs of MC and made note of a couple things in the AMD64 topic.
-
I tested Linux Mint Debian Edition 2 with the Wheezy repository (Jessie won't work there), it works fine there now so I added it to the tutorial.
-
I tested Linux Mint Debian Edition 2 with the Wheezy repository (Jessie won't work there), it works fine there now so I added it to the tutorial.
Cool, thanks.
-
Hi again :),
I respectfully disagree to your following reply.
Honestly, I'd say the current Debian build is already enough for Ubuntu and Mint as well.
When I look at most of the "pay for" linux programs I have bought they usually come in three flavors, 1. deb files for debian, ubuntu and mint etc, 2. rpm files for fedora, red hat and centos etc and 3. a tar file used to compile from source for other distro's.
Examples of this would be "Softmaker Office, Notecase Pro and Code Weavers: Crossover Program. These are pretty complex programs and they seem to all run very well. You go to the site download and install using your software manager or for the lesser used distro's from source. This is how it should be. Your method is the kind of thing that detours from regular customers wanting to use your program. I'd be willing to bet if it was changed to the examples I have mentioned you would notice an increase in your sales. You could just post the 3 download links at your software home page.
Thanks
-
In this case, the dev team develops Media Center on Debian, so it makes sense to only support Debian (and unofficially support Debian-based distros like Ubuntu and Linux Mint). That said, you can get Media Center working on Fedora if you follow the guide in this forum section. Also you can use Alien (http://joeyh.name/code/alien/) to convert the .deb to a .rpm and it might work, not sure. As for a .tar release, this won't happen as Media Center isn't open source.
-
I re-installed Linux Mint Debian Edition 2 64-bit in a VM, and re-tested the AMD64 build... it works now but make sure you update LMDE 2 before installing MC, so I've edited the tutorial. :D
-
Hi,
In response to:
In this case, the dev team develops Media Center on Debian, so it makes sense to only support Debian (and unofficially support Debian-based distros like Ubuntu and Linux Mint).
I understand that, but don't you think maybe it should be the other way around? Look at the number of hits this thread has! More than any other other thread by quite a margin. Make's you wonder I would think. Anyway I've expressed my concern and won't bring up the subject any more. Thanks for listening.
-
Hi,
In response to:
I understand that, but don't you think maybe it should be the other way around? Look at the number of hits this thread has! More than any other other thread by quite a margin. Make's you wonder I would think. Anyway I've expressed my concern and won't bring up the subject any more. Thanks for listening.
I hear you but it can't be the other way around because they are supersets of debian and the resulting package won't go backwards. We make the build as generic as possible and we simply can't afford to support a bunch of distro packages.
-
Updated the tutorial to reflect the new build method MC uses. :)
-
Updated the tutorial to reflect the new build method MC uses. :)
Thanks!
-
I recently installed Ubuntu 14.04 on an old laptop following the instructions at the beginning of this thread with no errors. Unfortunately I am unable to get MC to recognize my Bifrost DAC. However, I am able to play music through the DAC using another media player (can't remember the name) so I know the DAC is recognized by Ubuntu and functions. In MC I get the "Something went wrong with playback..." error. I installed and ran pavucontrol. It sees the Bifrost and the onboard sound card is off. In the sound tab in MC under Audio Device there are numerous choices (default:CARD+Intel [ALSA], dmix:CARD=S2, etc.). I chose "pulse [ALSA]". Still not working. Since I was able to listen to music through the laptop/Bifrost the issue seems to be MC. Any ideas?
-
I recently installed Ubuntu 14.04 on an old laptop following the instructions at the beginning of this thread with no errors. Unfortunately I am unable to get MC to recognize my Bifrost DAC. However, I am able to play music through the DAC using another media player (can't remember the name) so I know the DAC is recognized by Ubuntu and functions. In MC I get the "Something went wrong with playback..." error. I installed and ran pavucontrol. It sees the Bifrost and the onboard sound card is off. In the sound tab in MC under Audio Device there are numerous choices (default:CARD+Intel [ALSA], dmix:CARD=S2, etc.). I chose "pulse [ALSA]". Still not working. Since I was able to listen to music through the laptop/Bifrost the issue seems to be MC. Any ideas?
Either follow the instructions in the tutorial to get pulse working
or
use the hardware device for your DAC (front: something) and setup DSP studio to handle the sample rates your DAC cannot do.
(from a terminal window run /usr/lib/jriver/Media\ Center\ 20/alsacap to see the sample rates your device actually supports).
-
If all else fails, you can try going through every output listed in MC's Audio Device list one-by-one (test by trying to play a file) until you find one that works.
-
bob, Awesome Donkey,
I ran the alsacap command and it listed the sample rates as suggested. More importantly it listed the device name of my DAC. It was listed as "S2". It then hit me. S2 stands for Schiit USB version 2. I then went through the device list (with about 24 entries) and chose the one that had both S2 and front. It works!! Thanks ;D
-
Great! Glad to see it worked out for you! :)
-
Due to lightning striking last night and taking out and frying my PC and all its components, network components and my storage array that housed my 73,000+ FLAC music library - most I can't replace anymore (sadly my expensive surge protectors failed), I'm pretty much out of commission for the time being - which might be indefinitely, not sure yet what to do. Fortunately my Android phone still works so I can reply with it. However somebody else might need to take over these tutorials.
-
Due to lightning striking last night and taking out and frying my PC and all its components, network components and my storage array that housed my 73,000+ FLAC music library - most I can't replace anymore (sadly my expensive surge protectors failed), I'm pretty much out of commission for the time being - which might be indefinitely, not sure yet what to do. Fortunately my Android phone still works so I can reply with it. However somebody else might need to take over these tutorials.
I am very sorry to read about this?
George
-
Bad luck. Sorry to hear about it.
-
Due to lightning striking last night and taking out and frying my PC and all its components, network components and my storage array that housed my 73,000+ FLAC music library - most I can't replace anymore (sadly my expensive surge protectors failed), I'm pretty much out of commission for the time being - which might be indefinitely, not sure yet what to do. Fortunately my Android phone still works so I can reply with it. However somebody else might need to take over these tutorials.
That's terrible :-[ Hopefully some of the data is recoverable.
-
An update:
Hopefully some of the data is recoverable.
By some miracle it looks like one of the NAS hard drives for the music library survived with all data intact. The only problem is, the partition was accidently deleted but not reformatted over. So right now I'm running scans of the drive and it looks like all the files are intact and can be recovered. I'll know for sure by tomorrow morning after the scan finishes. If it's verified everything's there, I'm going shopping for 4TB hard drives and I'll use one to recover the data and the others as offline backups. Other than that, the lightning strike fried the motherboard* and my graphics card* and my NAS and its hard drives... except the one. I believe the CPU, RAM, SSDs and power supply are alright so I rebuild a temp PC using them and an old but semi-broken motherboard that still works to use as I work on replacing everything. If the data is recovered and I'm back in business, one of the first things I'll do is stop using wired ethernet for the NAS and computer.
As long as I can recover the music library, I don't really care for the other stuff - they can easily be replaced. Hopefully the bullet there has been dodged.
* Both are ASUS and my God ASUS has one of the worst RMA procedures there is, UGH. I'll just buy new ones.
-
Good news. Do you accept Paypal Donations? I'm serious. We need to get you back up and running.
-
My pride aside, I might have to. Honestly, I may have no choice but to accept them since otherwise it'd take me at least 3 months to replace everything.
-
My pride aside, I might have to. Honestly, I may have no choice but to accept them since otherwise it'd take me at least 3 months to replace everything.
Are you in the U.S?
I will donate via Paypal, if that is ok with you?
I do appreciate your contribution on the MC Linux forum, though I am not on Linux yet, with MC 21, I hope to get on board soon.
send me a PM with info.
George Omoregie.
-
If you'd like to help out, please read here (http://yabb.jriver.com/interact/index.php?topic=98567.0).
-
(sadly my expensive surge protectors failed)
Most expensive surge protectors have some kind of equipment guarantee where they'll pay you (often up to $10k) if they do fail and your stuff gets fried.
Look it up now!
-
Most expensive surge protectors have some kind of equipment guarantee where they'll pay you (often up to $10k) if they do fail and your stuff gets fried.
Look it up now!
Huh, I didn't even think of that! But won't they take issue that the lightning hit through the phone line and that the phone line wasn't connected to the surge protector in the first place? Nonetheless, good idea, I'm going to hunt down its box and read its information right now. :D
Another small update, scan of the remaining hard drive is completed - there is some missing data, but a large majority is intact. Well, that's better than no data at all.
-
Probably, if you tell them that. But what they don't know won't hurt you. ;)
I believe they typically inspect the surge protector itself, if there is a claim, but I don't know how rigorous it is. Worth looking into, unless you're absolutely sure the surge protectors were untouched entirely in the incident (they still work fine, etc), and weren't at all at fault.
-
Worth looking into, unless you're absolutely sure the surge protectors were untouched entirely in the incident (they still work fine, etc), and weren't at all at fault.
Yeah, that's the problem, they were completely untouched. Other components plugged into the protectors came out completely unharmed, like my speakers. Still, I'll be looking into this.
-
Due to lightning striking last night and taking out and frying my PC and all its components, network components and my storage array that housed my 73,000+ FLAC music library - most I can't replace anymore (sadly my expensive surge protectors failed), I'm pretty much out of commission for the time being - which might be indefinitely, not sure yet what to do. Fortunately my Android phone still works so I can reply with it. However somebody else might need to take over these tutorials.
Wow, that's a drag, sorry...
-
The recently released Linux Mint 17.2 Rafaela *should* work fine with this tutorial, however I can't currently test this. I don't see any reason why it shouldn't work, so please let me know if the tutorial works for you when using Linux Mint 17.2 Rafaela. I should be able to finally test it within a month or so.
-
I own both a Lenovo IdeaPad Y510P and ZaReason Zeto notebook and desktop PC respectively running Ubuntu 14.04.2 64 bit LTS GNU/Linux. I purchased J River Media Center 21 master license and I successfully install Media Center 20 64 bit and put in my master license on both PCs. Now, I have an Oppo Digital HA-1 and Sennheiser HD-800 along with a CEntrance HiFi-M8 LX XL4 and Shure SE-846 CL on the desktop and notebook PCs respectively. When I select Tools -> Options -> Audio -> Audio Device -> I get a bunch of stuff that does not reflect my current audio devices' names. It's hard to sort out. I also can't get beyond 32 bit 44.1 kHz playback. How do I fix this? Also, J River Media Center 20 64 bit keeps crashing randomly. How do I fix this issue?
I keep getting this error:
wellywu@ZaReasonZeto:~$ mediacenter20
Found 0 devices (devices will be listed below)
Total time: 2 ms
Result: 0
mediacenter20: symbol lookup error: /usr/lib/jriver/Media Center 20/libhogweed.so.2: undefined symbol: __gmpz_limbs_read
wellywu@ZaReasonZeto:~$
I set Ubuntu's Nautilus file manager to show hidden files and I deleted my /home/wellywu/.jriver hidden folder and I restored my master license. Now, it sort of works, but it keeps crashing in the middle of a song during playback. It also is limited to 32 bit 44.1 kHz playback. How do I fix this or should I wait for an update or upgrade to J River Media Center 21?
-
I own both a Lenovo IdeaPad Y510P and ZaReason Zeto notebook and desktop PC respectively running Ubuntu 14.04.2 64 bit LTS GNU/Linux. I purchased J River Media Center 21 master license and I successfully install Media Center 20 64 bit and put in my master license on both PCs. Now, I have an Oppo Digital HA-1 and Sennheiser HD-800 along with a CEntrance HiFi-M8 LX XL4 and Shure SE-846 CL on the desktop and notebook PCs respectively. When I select Tools -> Options -> Audio -> Audio Device -> I get a bunch of stuff that does not reflect my current audio devices' names. It's hard to sort out. I also can't get beyond 32 bit 44.1 kHz playback. How do I fix this? Also, J River Media Center 20 64 bit keeps crashing randomly. How do I fix this issue?
I keep getting this error:
wellywu@ZaReasonZeto:~$ mediacenter20
Found 0 devices (devices will be listed below)
Total time: 2 ms
Result: 0
mediacenter20: symbol lookup error: /usr/lib/jriver/Media Center 20/libhogweed.so.2: undefined symbol: __gmpz_limbs_read
wellywu@ZaReasonZeto:~$
I set Ubuntu's Nautilus file manager to show hidden files and I deleted my /home/wellywu/.jriver hidden folder and I restored my master license. Now, it sort of works, but it keeps crashing in the middle of a song during playback. It also is limited to 32 bit 44.1 kHz playback. How do I fix this or should I wait for an update or upgrade to J River Media Center 21?
The "found 0 devices" refers to handheld (not directly supported yet) NOT audio devices.
Try this test build:
http://files.jriver.com/mediacenter/channels/v20/latest/MediaCenter-20.0.132-amd64.deb
and report back.
It eliminates the need for an external libgmp.
-
That solved it for now. It's working now. Thanks for your help so far. If I run into another problem or I have another question, then I'll follow up here.
-
PS: Also, is there any cure for the ugly fonts and looks of the GUI in Linux?
Has anyone figured out how to solve the "Ugly" font issue? I looked under the font option in MC and I am only give three font and they are all "ugly". It causing buttons not to render correctly as well. I have the problem on both Ubuntu 14.04.2 and Xubuntu 14.04.2.
-
I had a similar issue after a clean Ubuntu 15.04 install, does it look like this?
(http://i.imgur.com/u9gF9gO.png)
-
If yours looks like the above, you might want to try completely removing mediacenter20, xfont-100dpi and xfont-75dpi and then reboot and then reinstall them. Try these in a Terminal;
sudo apt-get remove mediacenter20 xfont-100dpi xfont-75dpi
Then after rebooting try these in a Terminal;
sudo apt-get install mediacenter20 xfont-100dpi xfont-75dpi unifont
Then reboot again. After rebooting try MC20 and see if it appears correctly. Otherwise try using xlsfonts in a Terminal and posting the output here.
-
Attached is what I was seeing. MC20 was using a serif font instead of the sans-serif font. And there was white space after every row of text. Interestingly, I just let an automatic OS update happen and it rebooted, and automagically, all is fine.
-
Attached is what I was seeing. MC20 was using a serif font instead of the sans-serif font. And there was white space after every row of text. Interestingly, I just let an automatic OS update happen and it rebooted, and automagically, all is fine.
MC will fallback to
mutt-clearlyu as a last resort if it can't find the lucida font. This explains what you were seeing.
-
I discovered that JRiver MediaCenter appears to install it's own fonts when you install it in Linux, however when you first open it the font will look terrible because the new fonts haven't been loaded in to the xserver yet. After installing JRiver on Linux make sure you reboot after to restart the xserver and pull in the new fonts, then the font will look proper like in the following screenshot.
(http://dmon.org/graphics/screens/jriver_artwiz.png)
-
I store all of my music and MC library on a NAS. From windows, the path starts with \\NAS01\andy. From Linux, it is /mnt/nas01/andy.
When I go into "Rename, Move, & Copy Files" to update the database to point to the new location and do a "Find & Replace", I am seeing MC20 add an extra "/" between the path and the file name.
In other words, the final result is "/mnt/name/andy/<rest of path>//<filename of song>"
The attached screenshot shows the issue. Interestingly, the song still plays, but it causes havoc when I make future changes.
Is this a bug, or am I doing something wrong.
Second question, are people successfully sharing the same library between different operating systems? (Not using the library server, but actually opening the same library across different OS.)
-
Second question, are people successfully sharing the same library between different operating systems? (Not using the library server, but actually opening the same library across different OS.)
there's an existing feature request that would enable that to work -> http://yabb.jriver.com/interact/index.php?topic=98915.0
I previously raised a thread about that here -> http://yabb.jriver.com/interact/index.php?topic=94080.0
I suspect those two threads give all the info on that point
-
I discovered that JRiver MediaCenter appears to install it's own fonts when you install it in Linux, however when you first open it the font will look terrible because the new fonts haven't been loaded in to the xserver yet. After installing JRiver on Linux make sure you reboot after to restart the xserver and pull in the new fonts, then the font will look proper like in the following screenshot.
Yeah, I've known about this for awhile now, I've updated the tutorial with the recommendation to reboot after installing Media Center 20.
I'll be posting new Media Center 21 tutorials for Ubuntu/Linux Mint and Debian Jessie later today! :)