Topic: Setup JRiver Media Center 20 In Ubuntu/Linux Mint (Read 132836 times)

85Duppie · « **Reply #100 on:** March 04, 2015, 04:30:46 pm »

Quote from: bob on March 04, 2015, 01:23:34 pm

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?

bob · « **Reply #101 on:** March 04, 2015, 10:15:06 pm »

Quote from: 85Duppie on March 04, 2015, 04:30:46 pm

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.

85Duppie · « **Reply #102 on:** March 05, 2015, 10:36:26 pm »

Quote from: bob on March 04, 2015, 10:15:06 pm

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.

Awesome Donkey · « **Reply #103 on:** March 06, 2015, 05:49:50 pm »

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.

marzade · « **Reply #104 on:** March 10, 2015, 11:27:44 am »

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?

bob · « **Reply #105 on:** March 10, 2015, 11:45:55 am »

Quote from: marzade on March 10, 2015, 11:27:44 am

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

marzade · « **Reply #106 on:** March 10, 2015, 01:58:22 pm »

thanks, Bob!

- Perfect like always. That did it.

Awesome Donkey · « **Reply #107 on:** March 15, 2015, 07:10:07 pm »

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!

scas · « **Reply #108 on:** March 18, 2015, 10:03:05 am »

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"...

JimH · « **Reply #109 on:** March 18, 2015, 11:19:35 am »

The Master License won't work on older versions. Please try the latest from the top of this board.

scas · « **Reply #110 on:** March 18, 2015, 04:27:15 pm »

Quote from: JimH on March 18, 2015, 11:19:35 am

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

JimH · « **Reply #111 on:** March 18, 2015, 04:31:30 pm »

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.

scas · « **Reply #112 on:** March 18, 2015, 04:46:05 pm »

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?

JimH · « **Reply #113 on:** March 18, 2015, 04:50:39 pm »

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.

scas · « **Reply #114 on:** March 18, 2015, 05:01:39 pm »

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.

Awesome Donkey · « **Reply #115 on:** March 18, 2015, 05:24:59 pm »

Did something change in your hardware/network setup?

scas · « **Reply #116 on:** March 19, 2015, 05:08:39 am »

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

bob · « **Reply #117 on:** March 19, 2015, 10:07:29 am »

Quote from: scas on March 18, 2015, 04:46:05 pm

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

Weedos123 · « **Reply #118 on:** March 20, 2015, 05:28:54 am »

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.

Awesome Donkey · « **Reply #119 on:** April 16, 2015, 01:09:54 pm »

Tutorial updated to include support for Ubuntu 15.04. 15.04 lacks libgcrypt11 so I added a workaround to get it working.

outis · « **Reply #120 on:** April 18, 2015, 05:20:59 pm »

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

Awesome Donkey · « **Reply #121 on:** April 18, 2015, 06:18:04 pm »

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?).

JimH · « **Reply #122 on:** April 18, 2015, 06:35:18 pm »

The trial extension works from day 30 to day 45. Then it ceases to work. We could do a better job of communicating that.

bob · « **Reply #123 on:** April 19, 2015, 09:25:30 am »

Quote from: Awesome Donkey on April 18, 2015, 06:18:04 pm

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.

Awesome Donkey · « **Reply #124 on:** April 23, 2015, 04:03:13 pm »

Dropped Ubuntu 14.10 in favor of the newly released Ubuntu 15.04.

wormcycle · « **Reply #125 on:** April 26, 2015, 08:06:11 am »

I already own the Windows license, would like to convert one of my laptops to Linux. How I can upgrade to Master License?

JimH · « **Reply #126 on:** April 26, 2015, 09:01:23 am »

From the latest version of MC20, you can purchase a Master License for $24.98, if you have an MC20 license for Windows.

linuxdancer · « **Reply #127 on:** May 05, 2015, 08:38:50 am »

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.

Quote

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.

mwillems · « **Reply #128 on:** May 14, 2015, 07:28:11 am »

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:

Code: [Select]

mediacenter20 /RestoreFromFile "~/Downloads/Media Center20 Linux-YYYYYY.mjr"
But tilde expansion doesn't work when double quoted. It should probably be

Code: [Select]

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

bob · « **Reply #129 on:** May 14, 2015, 09:51:38 am »

Quote from: linuxdancer on May 05, 2015, 08:38:50 am

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.

JimH · « **Reply #130 on:** May 14, 2015, 10:26:41 am »

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.

pewe1263 · « **Reply #131 on:** May 14, 2015, 12:36:43 pm »

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 !

Awesome Donkey · « **Reply #132 on:** May 14, 2015, 01:17:40 pm »

Quote from: mwillems on May 14, 2015, 07:28:11 am

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!

Quote from: JimH on May 14, 2015, 10:26:41 am

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.

bob · « **Reply #133 on:** May 14, 2015, 01:55:15 pm »

Quote from: Awesome Donkey on May 14, 2015, 01:17:40 pm

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?

Awesome Donkey · « **Reply #134 on:** May 14, 2015, 02:39:22 pm »

Information on setting up a Launchpad PPA for Ubuntu.

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.

Awesome Donkey · « **Reply #135 on:** May 14, 2015, 09:49:29 pm »

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.

bob · « **Reply #136 on:** May 15, 2015, 10:47:29 am »

Quote from: Awesome Donkey on May 14, 2015, 09:49:29 pm

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.

linuxdancer · « **Reply #137 on:** May 19, 2015, 08:49:41 am »

Hi again

,

I respectfully disagree to your following reply.

Quote

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

Awesome Donkey · « **Reply #138 on:** May 19, 2015, 03:02:45 pm »

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 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.

Awesome Donkey · « **Reply #139 on:** May 19, 2015, 03:07:23 pm »

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.

linuxdancer · « **Reply #140 on:** May 21, 2015, 07:49:16 am »

Hi,

In response to:

Quote

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.

bob · « **Reply #141 on:** May 21, 2015, 03:10:58 pm »

Quote from: linuxdancer on May 21, 2015, 07:49:16 am

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.

Awesome Donkey · « **Reply #142 on:** June 01, 2015, 03:20:06 pm »

Updated the tutorial to reflect the new build method MC uses.

bob · « **Reply #143 on:** June 01, 2015, 03:52:14 pm »

Quote from: Awesome Donkey on June 01, 2015, 03:20:06 pm

Updated the tutorial to reflect the new build method MC uses.

Thanks!

juergen99 · « **Reply #144 on:** June 02, 2015, 01:06:15 pm »

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?

bob · « **Reply #145 on:** June 02, 2015, 01:17:47 pm »

Quote from: juergen99 on June 02, 2015, 01:06:15 pm

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).

Awesome Donkey · « **Reply #146 on:** June 02, 2015, 04:22:40 pm »

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.

juergen99 · « **Reply #147 on:** June 03, 2015, 10:35:25 pm »

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

Awesome Donkey · « **Reply #148 on:** June 04, 2015, 08:17:55 am »

Great! Glad to see it worked out for you!

Awesome Donkey · « **Reply #149 on:** July 02, 2015, 03:15:10 pm »

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.

INTERACT FORUM

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