InflatableMouse-temp: Difference between revisions

From wiki.jriver.com
Jump to navigation Jump to search
No edit summary
No edit summary
 
(82 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This document will guide you through the process of installing and configuring MediaCenter for Linux. You are advised to read through the document before installing MediaCenter. It assumes some basic knowledge of Linux in general and familiarity working from a terminal. It also assumes an installation on 64-bit distribution as that will most likely be the target system. Installation on a 32-bit system will be very similar and, where applicable, notes will clarify the differences.
This is InflatableMouse' scratch page.
----
[[Category:Frequently Asked Questions]]
We take crashes and other stability problems very seriously. We want to know as much as possible about the cause.


Throughout this document you are required to run certain commands in a terminal, sometimes with root permissions. Whether you do that as root itself or using temporarily elevated permissions through sudo is up to you. This document will precede each command with a # or $ sign, signifying whether the command needs to run as root (#) or as a regular user ($). Unless you changed your terminal prompt, it will show this same symbol for root (#) or user ($) on its prompt. You should not include this symbol in your command, it only signifies how the command should be run.
This article describes the basic steps you would typically take when facing stability issues. A more detailed forum thread on Interact about troubleshooting stability issues can be found here: [http://yabb.jriver.com/interact/index.php?topic=86699.0 '''How To: Fix MC If It Is Misbehaving (Hanging Regularly or Crashing)'''].


{{Related articles start}}
You can help determine why a problem occurred. In this order, try these:
{{Related|Installation & Removal}}
{{Related|Getting Started}}
{{Related|Trial Information}}
{{Related|http://www.jriver.com/purchase.html Purchase and License Information}}
{{Related articles end}}


== Before you begin ==
1. Please '''use the download link above to update your player'''. If a newer version has been released, please try it. For example, if you're using MC14, but MC15 has been released, please try it. The latest known stable build is always on the [http://www.jriver.com/download.html download page], but a newer version may be found at the top of each board on the [http://yabb.jriver.com/interact/ forum].
MediaCenter is in beta and is under heavy development. As such, it may not work as expected. Although it is considered to be stable enough for regular use it may still show unexpected behavior such as crashes or random refusals to play a track. Please make sure you read through the list of [http://yabb.jriver.com/interact/index.php?topic=85770.0 Outstanding issues].


It is strongly advised to make regular backups of your media. There have been no reports of MediaCenter for Linux messing up tags or otherwise corrupting files, but it is still in beta - consider yourself warned. You can configure MediaCenter to not update tags at all, it will only read from your files but that does not negate the fact that you should always have backups.
2. '''Disable plug-ins''' and other third party software that you use with MC. We have had some problems with bugs in plug-ins causing problems in the past. The Audioscrobbler plug-in, for example, would crash MC if you weren't logged into last.fm.


It is also a good idea to read through the [http://yabb.jriver.com/interact/index.php?board=35.0 sticky threads on the forums], too.
3. Problems with '''Virus Checkers''', Pop-up Blockers, and SPAM programs are not uncommon. Please disable these to test.


=== System requirements ===
4. '''Reboot, reinstall''', [http://www.jriver.com/purchase.html reinstall your license].
MediaCenter is being developed on Debian Wheezy 32-bit, x86 architecture. It will run on multiarch distributions (64-bit with 32-bit libraries) once the proper 32-bit dependencies are satisfied. See DEPENDENCIES for more information.


MediaCenter requires a CPU that supports SSE2. This means the CPU needs to be from around 2002 or later.
5. Check the [http://yabb.jriver.com/interact/index.php?topic=24031.0 '''Weird Problems'''] thread for similar problems. This thread lists a number of problems caused by other software or hardware.


==== Hardware Requirements (Minimum) ====
6. Turn off auto-import. It's under tools/options/libraries.
* Intel or AMD x86 Compatible CPU with SSE2
* 2GB RAM
* 300MB free hard drive space for installation (excluding space for digital media)
* Sound device supported by ALSA
* Internet connection (recommended)


==== Software Requirements ====
7. Think about any changes you've made to your system; both hardware and software. Crashes can be caused by a bad CPU, bad memory, bad drivers, etc. A "blue screen", for example, is a hardware or driver issue. Some machines may not be stable under heavy use. The fact that other software works may mean that the software doesn't use the machine in the same way. If you have more than one stick of RAM, consider using just one at a time in order to test.
Official Support:
* Debian Wheezy or a similar distribution based on Debian
* Working Xorg - see [[#Headless|Running MC Headless]] for a minimal installation. GUIfied - MediaCenter should work on any desktop. Its confirmed to work on XFCE, Unity, KDE, Gnome and Cinnamon. MATE and others are untested (try searching [http://yabb.jriver.com/interact/index.php?board=35.0 Interact]). If you know one that works or how to get it working, you are invited to share this on [http://yabb.jriver.com/interact/index.php?board=35.0 Interact].
* Working ALSA sound stack


MediaCenter requires:
8. Start a thread on [http://yabb.jriver.com/interact/ Interact] with details about what version you're using, and the events that lead up to the crash.
* X86 (32-bit)
* SSE2
* libc6 >= 2.13
* libX11-6 >= 2.1.5
* libcurl3 >= 7.26
* lame >= 3.99
* xfonts-75dpi
* xfonts-100dpi
* An ALSA device that supports S32_LE
* On multiarch/multilib systems, all libraries MediaCenter depend on need to be 32-bit.


MediaCenter is known to work on recent versions of Mint, Ubuntu, OpenSuse, Fedora and Arch Linux. However, this is considered experimental and is not guaranteed to work. If you intent to run MediaCenter on such a distribution, you are strongly encouraged to share your experience on [http://yabb.jriver.com/interact/index.php?board=35.0 Interact].
9. Enable logging in MC and send us a log (to logs at jriver) with a link to your thread. Logging is under MC's Help menu, and there you can also e-mail the logs. There is more information about logging in the 'Logging' section below.


=== Limitations ===
10. Examine the logs and search for the word "crash".
* Although Linux can run on architectures other than x86 (like ARM or PowerPC for instance), MediaCenter does not run on architectures other than i386 or x86_64.
* OSS and Pulse are currently not supported by MediaCenter. It may work with Pulse, but it is currently unsupported.
* MediaCenter can run in server mode on a headless server, but it requires an Xserver running. See [[#Headless|Running MC Headless]] for more information.
* MediaCenter can run on bleeding edge distributions like Arch Linux. However it is built on Debian Wheezy, so some of the libraries it depends on are older versions not included or compatible with the versions used on bleeding edge distributions. The [[#Troubleshooting|Troubleshooting]] section may contain some tips to get it working.


== Logging ==
=== Dependencies ===
To successfully install MediaCenter, you need to make sure that the following depencies are installed. Installation on a 64-bit system requires multiarch to be enabled for 32-bit compatibility.


To enable multiarch on a 64-bit system, type the following in a terminal:
Media Center can create a log file of what it is doing as it runs. Logging can be enabled under MC's Help menu, and there you can also e-mail logs.


<pre>
When a crash is recorded, the word "crash" will normally be written to the log.
# dpkg --add-architecture i386
</pre>


This command require you update. Type:
Each run, a "Log.txt" file is created. The log from the previous run will be renamed "Previous Log.txt". When restarting after a crash, "Previous Log.txt" will contain the crash.


<pre>
It is recommended that you use the logging dialog to email logs, and it will include both logs in the email.
# apt-get update && apt-get upgrade
</pre>


If you had not updated in a while, you may get a lot of new packages. Read the output carefully. If it says certain packages are held-back, cancel using CTRL-C and issue the following command instead:
Logs are stored here:


<pre>
Windows Vista: C:\Users\[User Name]\AppData\Roaming\J River\Media Center 15
# apt-get update && apt-get dist-upgrade
</pre>


You should reboot your system when it is done, unless it didn't update anything of course.
Windows XP: C:\Documents & Settings\[User Name]\Application Data\J River\Media Center 15


Next we are going to install the following packages and libraries:
== Enabling logging when the program won't run ==


In some cases, a problem may prevent the program from running. In this case, logging must be manually enabled by using the Registry Editor.


* lame
1. From the start menu, select Run and type regedit
* musepack-tools
* xfonts-75dpi
* xfonts-100dpi
* vorbis-tools


* libcurl3:i386
2. Locate this key (create it if necessary):
* libx11-6:i386
HKEY_CURRENT_USER\Software\J. River\Media Center 15\Debug
* lib32stdc++6
* libmpcdec6:i386
* libc6:i386
* libstdc++6:i386
* libcrypto++9:i386
* libasound2:i386
* libuuid1:i386
* libboost-regex1.49.0:i386
* libicu48:i386


Note: On a 32-bit system, you can install the same libraries by removing ':i386' part.
3. Add (or modify if it exists) a DWORD named "File" and set it to 1


Unless you're installing on a fresh system you probably have some of these installed already. This doesn't matter as Aptitude will simply skip packages that are already installed. You can install all of them at once by issuing the following command with root privileges from a terminal:
[[Category: Frequently Asked Questions]]


<pre>
== Other Tests ==
# apt-get install lame musepack-tools xfonts-75dpi xfonts-100dpi vorbis-tools libcurl3:i386 libx11-6:i386 lib32stdc++6 libmpcdec6:i386 \
Thanks to glynor for this:
bc6:i386 libstdc++6:i386 libx11-6:i386 libcrypto++9:i386 libasound2:i386 libuuid1:i386 libboost-regex1.49.0:i386 libicu48:i386
</pre>


Or, on a 32-bit system (REQUIRES CONFIRMATION):
A good, simple first test is Memtest86+. Grab it, burn it, boot to it, and make sure the system can run one full pass on the memory with no errors. Then, boot to windows... I'd get Prime95 to start. It should absolutely be able to run the torture test on "blend" for at least 24 hours with no crashes, warnings, or errors.


<pre>
Assuming you pass those two basic tests, I'd test the GPU. There are some special-purpose GPU testers out there, but I'm not really a big fan. Many of them seemed designed to crash the system, even if you'd otherwise never see any real problems. If you don't have any newer high-end games to test with, I'd try running a few passes of FutureMark's 3DMark. That should push the GPU pretty hard, but in a realistic manner. Make sure you download and install the LATEST drivers for your graphics card before starting, even if 3DMark warns that they aren't "certified" (you don't care about publishing your score and showing off, just testing).
# apt-get install lame musepack-tools xfonts-75dpi xfonts-100dpi vorbis-tools libcurl3 libx11-6 libstdc++6 libmpcdec6 bc6 libstdc++6 \
libx11-6 libcrypto++9 libasound2 libuuid1 libboost-regex1.49.0 libicu48
</pre>


Carefully read the output and make sure no packages are being removed.
Memtest86+: http://www.memtest.org/


Installing these packages and libraries do not require a reboot. Other packages these might pull in may require a reboot so to be sure, reboot your system afterwards.
Prime95: http://www.mersenne.org/freesoft/


On a fresh install the CD or DVD from which the system was installed might have been added to the sources.list as an available source for packages. It is advised you remove this and use online repositories instead. To do this, edit /etc/apt/sources.list and remove any lines starting with "deb cdrom:". First, make a backup of the current file:
3DMark Vantage: http://www.futuremark.com/benchmarks/3dmarkvantage/download/


<pre>
And a great post on Stress Testing by InflatableMouse:
# cp /etc/apt/sources.list{,.bak}
</pre>


Open the file in nano:
http://yabb.jriver.com/interact/index.php?topic=72050.msg487385#msg487385

<pre>
# nano /etc/apt/sources.list
</pre>

Remove the lines, or comment them out, for example:

<pre>
# deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot i386 LIVE/INSTALL Binary 20131014-03:33]/ wheezy main

deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot i386 LIVE/INSTALL Binary 20131014-03:33]/ wheezy main
</pre>

=== Downloading MediaCenter ===

The latest version of MediaCenter for Linux should be downloaded, this version can be found in one of the stickies on [http://yabb.jriver.com/interact/index.php?board=35.0 Interact]. You can download it from your browser to ~/Downloads, or use the terminal issuing the following command (replace the version/build number with the latest found on the Linux board above):

<pre>
$ cd ~/Downloads && wget http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter-19.0.103.deb
</pre>

Obviously, the directory Downloads should exist under your home directory ;).

== Installing MediaCenter ==

After having satisfied all MediaCenter's dependencies and having downloaded the package to your PC, you can continue with the installation. Change to the directory to which you downloaded, or add the full path on the commandline. Again, change the version/build number for the version you downloaded. Issue the following command from a terminal:

<pre>
# dpkg -i /location/of/MediaCenter-19.0.103.deb
</pre>

If the output says it is missing dependencies, leaving unconfigured, you should take note of the packages mentioned. You can try to install them manually, or you can try issuing the following command:

<pre>
# apt-get install -f
</pre>

Examine the output carefully, as it may remove packages to satisfy dependencies. This may not always lead to a happy ending - so be careful.

If you run into unresolvable dependencies, have a look at the troubleshooting section, or post your problems on [http://yabb.jriver.com/interact/index.php?board=35.0 Interact] where someone will try to help you resolve the issue.

=== First Run ===
When MediaCenter is first run, it will popup a Notification that it will timeout at a certain date. If it pops up a notification that it is has timed out already, you may have installed an older version. Visit [http://yabb.jriver.com/interact/index.php?board=35.0 Interact] and find the latest version in one of the sticky threads from the top of the board. You can simpy install it over the older version, see Upgrading.

=== Auto Import ===
MediaCenter will automatically start an Import shortly after startup to scan your home directory for media files. This is fine if your media is located there and you can let it run. If your media is somewhere else, you can cancel this in the lower left hand corner, where there will be a countdown from 45 seconds. Click the X to close the Action Window and not import anything, or click the link to configure Media Import. This automatic import will keep coming back until there is something in its library. There is no way to turn off this behavior.

Note that the option called "Auto-Import" is called "Configure Auto-Import" on Windows. This option allows you to configure how Auto-Import should run.

At the time of writing the browse button does not work, you need to type in the path to the location of the media files you wish to import.

=== Upgrading from an older version ===
Download the latest version from [http://yabb.jriver.com/interact/index.php?board=35.0 Interact] and install it, for example:

<pre>
$ sudo dpkg -i MediaCenter-19.0.xxx.deb
</pre>

Replace xxx with the build number from the file you downloaded. There are currently no complications or different dependencies. All versions should be able to install the same way.

=== Library Server Compatibility ===
MediaCenter for Linux can connect to a MediaCenter Library server running on Windows, Mac OS X or Linux. It will only play Audio however, even if the server is serving video as well. The Linux version currently supports only audio playback.

== Configuring MediaCenter ==
Config Intro.

=== Sound ===
ALSA info.

=== Output Mode ===
Configuring Resampling with MC.

== Headless Configuration ==

=== MC GUI via SSH ===

== Troubleshooting ==

Latest revision as of 01:53, 11 February 2018

This document will guide you through the process of installing and configuring MediaCenter for Linux. You are advised to read through the document before installing MediaCenter. It assumes some basic knowledge of Linux in general and familiarity working from a terminal. It also assumes an installation on 64-bit distribution as that will most likely be the target system. Installation on a 32-bit system will be very similar and, where applicable, notes will clarify the differences.

Throughout this document you are required to run certain commands in a terminal, sometimes with root permissions. Whether you do that as root itself or using temporarily elevated permissions through sudo is up to you. This document will precede each command with a # or $ sign, signifying whether the command needs to run as root (#) or as a regular user ($). Unless you changed your terminal prompt, it will show this same symbol for root (#) or user ($) on its prompt. You should not include this symbol in your command, it only signifies how the command should be run.

Related articles

Before you begin

MediaCenter is in beta and is under heavy development. As such, it may not work as expected. Although it is considered to be stable enough for regular use it may still show unexpected behavior such as crashes or random refusals to play a track. Please make sure you read through the list of Outstanding issues.

It is strongly advised to make regular backups of your media. There have been no reports of MediaCenter for Linux messing up tags or otherwise corrupting files, but it is still in beta - consider yourself warned. You can configure MediaCenter to not update tags at all, it will only read from your files but that does not negate the fact that you should always have backups.

It is also a good idea to read through the sticky threads on the forums, too.

System requirements

MediaCenter is being developed on Debian Wheezy 32-bit, x86 architecture. It will run on multiarch distributions (64-bit with 32-bit libraries) once the proper 32-bit dependencies are satisfied. See DEPENDENCIES for more information.

MediaCenter requires a CPU that supports SSE2. This means the CPU needs to be from around 2002 or later.

Hardware Requirements (Minimum)

  • Intel or AMD x86 Compatible CPU with SSE2
  • 2GB RAM
  • 300MB free hard drive space for installation (excluding space for digital media)
  • Sound device supported by ALSA
  • Internet connection (recommended)

Software Requirements

Official Support:

  • Debian Wheezy or a similar distribution based on Debian
  • Working Xorg - see Running MC Headless for a minimal installation. GUIfied - MediaCenter should work on any desktop. Its confirmed to work on XFCE, Unity, KDE, Gnome and Cinnamon. MATE and others are untested (try searching Interact). If you know one that works or how to get it working, you are invited to share this on Interact.
  • Working ALSA sound stack

MediaCenter requires:

  • X86 (32-bit)
  • SSE2
  • libc6 >= 2.13
  • libX11-6 >= 2.1.5
  • libcurl3 >= 7.26
  • lame >= 3.99
  • xfonts-75dpi
  • xfonts-100dpi
  • An ALSA device that supports S32_LE
  • On multiarch/multilib systems, all libraries MediaCenter depend on need to be 32-bit.

MediaCenter is known to work on recent versions of Mint, Ubuntu, OpenSuse, Fedora and Arch Linux. However, this is considered experimental and is not guaranteed to work. If you intent to run MediaCenter on such a distribution, you are strongly encouraged to share your experience on Interact.

Limitations

  • Although Linux can run on architectures other than x86 (like ARM or PowerPC for instance), MediaCenter does not run on architectures other than i386 or x86_64.
  • OSS and Pulse are currently not supported by MediaCenter. It may work with Pulse, but it is currently unsupported.
  • MediaCenter can run in server mode on a headless server, but it requires an Xserver running. See Running MC Headless for more information.
  • MediaCenter can run on bleeding edge distributions like Arch Linux. However it is built on Debian Wheezy, so some of the libraries it depends on are older versions not included or compatible with the versions used on bleeding edge distributions. The Troubleshooting section may contain some tips to get it working.

Dependencies

To successfully install MediaCenter, you need to make sure that the following depencies are installed. Installation on a 64-bit system requires multiarch to be enabled for 32-bit compatibility.

To enable multiarch on a 64-bit system, type the following in a terminal: 

# dpkg --add-architecture i386

This command require you update. Type: 

# apt-get update && apt-get upgrade

If you had not updated in a while, you may get a lot of new packages. Read the output carefully. If it says certain packages are held-back, cancel using CTRL-C and issue the following command instead: 

# apt-get update && apt-get dist-upgrade

You should reboot your system when it is done, unless it didn't update anything of course.

Next we are going to install the following packages and libraries:


  • lame
  • musepack-tools
  • xfonts-75dpi
  • xfonts-100dpi
  • vorbis-tools
  • libcurl3:i386
  • libx11-6:i386
  • lib32stdc++6
  • libmpcdec6:i386
  • libc6:i386
  • libstdc++6:i386
  • libcrypto++9:i386
  • libasound2:i386
  • libuuid1:i386
  • libboost-regex1.49.0:i386
  • libicu48:i386

Note: On a 32-bit system, you can install the same libraries by removing ':i386' part.

Unless you're installing on a fresh system you probably have some of these installed already. This doesn't matter as Aptitude will simply skip packages that are already installed. You can install all of them at once by issuing the following command with root privileges from a terminal: 

# apt-get install lame musepack-tools xfonts-75dpi xfonts-100dpi vorbis-tools libcurl3:i386 libx11-6:i386 lib32stdc++6 libmpcdec6:i386 \
bc6:i386 libstdc++6:i386 libx11-6:i386 libcrypto++9:i386 libasound2:i386 libuuid1:i386 libboost-regex1.49.0:i386 libicu48:i386

Or, on a 32-bit system (REQUIRES CONFIRMATION): 

# apt-get install lame musepack-tools xfonts-75dpi xfonts-100dpi vorbis-tools libcurl3 libx11-6 libstdc++6 libmpcdec6 bc6 libstdc++6 \
libx11-6 libcrypto++9 libasound2 libuuid1 libboost-regex1.49.0 libicu48

Carefully read the output and make sure no packages are being removed.

Installing these packages and libraries do not require a reboot. Other packages these might pull in may require a reboot so to be sure, reboot your system afterwards.

On a fresh install the CD or DVD from which the system was installed might have been added to the sources.list as an available source for packages. It is advised you remove this and use online repositories instead. To do this, edit /etc/apt/sources.list and remove any lines starting with "deb cdrom:". First, make a backup of the current file: 

# cp /etc/apt/sources.list{,.bak}

Open the file in nano: 

# nano /etc/apt/sources.list

Remove the lines, or comment them out, for example: 

# deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot i386 LIVE/INSTALL Binary 20131014-03:33]/ wheezy main

deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot i386 LIVE/INSTALL Binary 20131014-03:33]/ wheezy main

Downloading MediaCenter

The latest version of MediaCenter for Linux should be downloaded, this version can be found in one of the stickies on Interact. You can download it from your browser to ~/Downloads, or use the terminal issuing the following command (replace the version/build number with the latest found on the Linux board above): 

$ cd ~/Downloads && wget http://files.jriver.com/mediacenter/channels/v19/latest/MediaCenter-19.0.103.deb

Obviously, the directory Downloads should exist under your home directory ;).

Installing MediaCenter

After having satisfied all MediaCenter's dependencies and having downloaded the package to your PC, you can continue with the installation. Change to the directory to which you downloaded, or add the full path on the commandline. Again, change the version/build number for the version you downloaded. Issue the following command from a terminal: 

# dpkg -i /location/of/MediaCenter-19.0.103.deb

If the output says it is missing dependencies, leaving unconfigured, you should take note of the packages mentioned. You can try to install them manually, or you can try issuing the following command: 

# apt-get install -f

Examine the output carefully, as it may remove packages to satisfy dependencies. This may not always lead to a happy ending - so be careful.

If you run into unresolvable dependencies, have a look at the troubleshooting section, or post your problems on Interact where someone will try to help you resolve the issue.

First Run

When MediaCenter is first run, it will popup a Notification that it will timeout at a certain date. If it pops up a notification that it is has timed out already, you may have installed an older version. Visit Interact and find the latest version in one of the sticky threads from the top of the board. You can simpy install it over the older version, see Upgrading.

Auto Import

MediaCenter will automatically start an Import shortly after startup to scan your home directory for media files. This is fine if your media is located there and you can let it run. If your media is somewhere else, you can cancel this in the lower left hand corner, where there will be a countdown from 45 seconds. Click the X to close the Action Window and not import anything, or click the link to configure Media Import. This automatic import will keep coming back until there is something in its library. There is no way to turn off this behavior.

Note that the option called "Auto-Import" is called "Configure Auto-Import" on Windows. This option allows you to configure how Auto-Import should run.

At the time of writing the browse button does not work, you need to type in the path to the location of the media files you wish to import.

Upgrading from an older version

Download the latest version from Interact and install it, for example: 

$ sudo dpkg -i MediaCenter-19.0.xxx.deb

Replace xxx with the build number from the file you downloaded. There are currently no complications or different dependencies. All versions should be able to install the same way.

Library Server Compatibility

MediaCenter for Linux can connect to a MediaCenter Library server running on Windows, Mac OS X or Linux. It will only play Audio however, even if the server is serving video as well. The Linux version currently supports only audio playback.

Configuring MediaCenter

Config Intro.

Sound

ALSA info.

Output Mode

Configuring Resampling with MC.

Headless Configuration

MC GUI via SSH

Troubleshooting

Retrieved from "https://wiki.jriver.com/index.php?title=InflatableMouse-temp&oldid=15243"