Member Login Submit News :: FAQ :: Advanced Search :: Reviews :: Polls
Main Menu
· Home

Modules
· Downloads
· FAQ
· Members List
· News
· Forums
· Reviews
· Search
· Sections
· Stats
· Topics
· Top List
· Web Links

Search Box


Who's Online
We have 5 guests and 0 members online

You are an anonymous user. You can register for free by clicking here



Preview Release of the PRISMIQ MediaServer for Linux! (Version 4101)

(1770 total words in this text)
(4130 Reads)   Printer friendly page

Readme for The PRISMIQ MediaServer Linux Preview Release, June, 2004

Due to the desire in the PRISMIQ User Community, as well as within PRISMIQ,
we have decided to release a "Preview" release of MediaServer for Linux and 
Mac OS X. This release is not a final "product", and does not include a user 
interface for managing your MediaPlayer data, but allows you to serve your 
media contents on a machine running Linux or Mac OS X, as opposed to requiring
a Windows computer.

THE INFORMATION PROVIDED HERE IS FOR YOUR OWN USE, AND COMES WITH NO WARRANTY
OR SUPPORT. PLEASE DO NOT CONTACT TECHNICAL SUPPORT FOR HELP, INSTEAD PLEASE
USE THE PRISMIQ.ORG COMMUNITY FORUMS.

THE CODE PROVIDED HERE IS COPYRIGHT 2003, 2004 PRISMIQ INC, AND LICENSED UNDER EITHER
THE GNU GENERAL PUBLIC LICENSE, THE BSD LICENSE, OR A PROPRIETARY PRISMIQ 
LICENSE. CONSULT THE LICENSE FILE FOR MORE INFORMATION.

We hope that the PRISMIQ MediaPlayer users will try out this release, and
let us know what they think. We welcome your comments, feedback, ideas, and
suggestions. Please send them to us via linux-preview@PRISMIQ.com (please
use "linux-preview" for both linux and Mac OS X). Due to the volume of email,
we may not be able to reply to every email personally, but we do read every 
email and consider community feedback to be a key part of development.

The Linux version of the PRISMIQ MediaServer has been tested on Redhat 7.3
(glibc 2.2.5), Redhat 9.0 (glibc 2.3.2), and SuSE 8.0 (glibc 2.2.5). It
should function on any other similar or compatible Linux distributions.
You will need at least 128 MB of RAM (preferably 256), and at least 30
megabytes of hard drive space, not including your Media files. You will also
need the Java Development Kit, Standard Edition (J2SE) version 1.4.1 or
greater, although we have not tested the betas of version 1.5 that are
available at the time of this writing (12/2003). You can obtain the J2SE from
Sun Microsystem's Website at http://java.sun.com/j2se/downloads.html.
You will also need X11 installed on your computer. X11 need not be running, 
but the Java 2 SDK requires certain X libraries to run. For more information, see 
<a 

href="http://prismiq.org/modules.php?op=modload&name=phpBB2&file=viewtopic&t=920&start=0&postdays=0

&postorder=asc&highlight=&sid=cf6159f094907228c4c252a07bf0853b">this thread on the PRISMIQ 

Forums.

The package is available here

 (20 MB).

The package that this README accompanies contains the MediaServer components
of the PRISMIQ MediaPlayer (http://www.prismiq.com/products) software suite.
At this time, there is no tool available on Linux to create the datafiles
needed for the MediaServer, however we have included a tool to convert files
created on the Windows version of the software. Instructions are below for
using these tools. Also included in the "gather" directory is a script written by Rob
Flickenger that will find media and create the data files needed. For more
information, see the READMEs in the "gather" directory, as well as Rob's web
site at http://nocat.net/~rob/prismiq/.

Also included is a document describing technical aspects of the MediaServer
for Linux or Mac OS X. This HTML document is located in the "docs" directory,
named "PRISMIQ MediaServer Tech Info.html".

Before the MediaServer will function properly, you will need to create four
files that are not included in the installer. These files describe your media
data, as well as your user preferences. We have also included a "samples"
directory showing a basic set of files. The files have inline XML comments
describing them that should illustrate how to create files that fully take
advantage of the MediaPlayer's functionality. There are also instructions
below that will help you to use Samba to create the files on a Windows
computer and copy them over. You can use any means to copy them, Samba, ftp,
etc, or use the "gather" script as mentioned above.

----------------------------------------------------------------------------

Release History:
4101: This release coincides with the release of version 4.1.0.1 for windows.

4002: This release coincides with the release of version 4.0.0.2 for windows.

3202: This release coincides with the release of version 3.2.0.2 for 
windows. Not publicly released.

311b: This release includes the correct license file. An incorrect one
was distributed with version 311 and 311a.

311a: This release corrects a file ownership setting. If you have
installed version 311, you can simply do the following:

    su -
    chown root mserver_311/bin/mmserv

311: Initial Release

----------------------------------------------------------------------------

To install the MediaServer on Linux:
1) As root, run the MediaServer for Linux installer, and accept the license.
   (You must install as root, as one component of the MediaServer needs to
   be setuid to bind to port 554, the RSTP port). Note: use the "su" command,
   not "su -", or, use the "sudo" command.
    
   Linux:
   su
   chmod +x mserver_install_4002.sh
   ./mserver_install_4002.sh
   
   Mac OS X:
   chmod +x mserver_install_4002.sh
   sudo ./mserver_install_4002.sh

To Upgrade from a previous version:
   
   After unpacking the MediaServer:
   cd mserver_4002
   ./upgrade.sh [-v] /path/to/old/mserver_version    

   The upgrade script will stop any running versions of the MediaServer, 
   and copy over your data files to the new MediaServer location.

To start the MediaServer:

    cd mserver_4002
    If you copied over window files (see below), do this next:
    ./start.sh -c

    If you created your own data files, do this:
    ./start.sh
    
    The MediaServer components will start up in the background. To see
    the startup progress, run "start.sh" with the "-v" command line argument.

To Stop the MediaServer:

    cd mserver_4002
    If you copied over window files (see below), do this next:
    ./stop.sh

    Again, the "-v" command line flag will show the progress of the stopping.

----------------------------------------------------------------------------

Some notes:

- bin/mmserv must be owned by root, and setuid. This is because mmserv needs
to bind to the IANA assigned RSTP port, 554. 

- The PRISMIQ Transcoder, bin/prismiq_xcode, will sometimes stop operating.
Symptoms of this include the message "movie.avi: not found" on the MediaPlayer
when playing any transcoded media types (such as DivX/MPEG4/WAV, etc).
Pressing the "stop" key on the MediaPlayer, and then selecting the media item
again will usually restart playback, however we have seen some instances where
the plugin will drop core and need to be restarted. This can be some simply by
executing "bin/prismiq_xcode &", or running "start.sh", which will only restart
the any processes that need starting.

We realize that a User Interface for playlist and media management is needed on
Linux, and plan to address that in the future. At the current time, however,
there should be enough information in the "start.sh" and "bin/convert.pl"
scripts, as well as the XML files stored in "bin/gui" themselves to allow some
customization for our Linux users. The XML files of interest are the following:

- userprefs.xml - Contains Stock ticker symbols, as well as Weather location
  info
- media.xml - needs to be paired with a matching media.map, contains all of
  the media data.

- playlist.xml - contains a mapping of Media ID's from media.xml/media.map to
  playlist name/type/contents.

- radio.xml - contains the list of Internet Radio stations

- bookmarks.xml - contains the list of bookmarks shown in the Web Browser.

All other xml files will be created on the fly by the Tomcat server, and will
be overwritten on a regular basis.

The key files for playing audio and video, as well as viewing images are
media.map and media.xml. The screen generator uses media.xml to create the
lists of tracks or images that appear on the MediaPlayer. To select an
individual track, the MediaPlayer will request a track by ID from the
MediaServer, which will consult media.map for the filename as well as tag file.

----------------------------------------------------------------------------

Below is a set of steps to copy over the correct files via Samba. Again, you
can you whatever method you'd like to transfer the files once they are created.
If you are creating your own data files, skip to step number 13.

1) Use samba to make your Media Files available for Windows, as well as your
   MediaServer directory.

   For instance, if all of your media is stored in /home/media, then add an
   entry to smb.conf something along the lines of:

[media]
  comment = Linux Media Directory
  path = /home/media
  public = yes
  writable = yes
[mediaserver]
  comment = Linux MediaServer Directory
  path = /home/user/mserver/
  public = yes
  writable = yes

2) On the Windows machine, map these new share to a drive, say "Z:" for the
   "media" share, and "Y:" for the mediaserver share.

3) Install MediaManager 3.1.1 (from http://update.PRISMIQ.com/pmm_3.1.1-r0.exe)

4) When scanning for files, only scan the "Z:" drive into MediaManager.

5) Exit MediaManager by right clicking in the system tray area on the
   MediaManager icon and selecting "Exit".

6) Remove the Auto-start entry on the PC by deleting the "PRISMIQ
   MediaManager Launcher" item in the Startup Items folder in the Start Menu.

7) Use Windows Explorer to navigate to 
   C:\Program Files\PRISMIQ\MediaManager\gui

8) Select all of the ".xml" files in this directory, as well as the media.map
   file.

9) Copy these files to the Linux MediaServer "gui" directory, for instance
"y:\bin\gui" (you will overwrite the "skeleton" files that are in this 
directory now).

10) Unmap the Z: and Y: share on Windows (optional).

11) Edit .mserverrc and insert the proper paths for the Windows root, Linux
    root, and tag file root. These paths are used in converting media.xml
    and media.map's paths to the Linux file system. There are 3 required
    values, and one optional one.

   WINDOWS_MEDIA_MAP_ROOT - set this to the "root path" on Windows from when
   you scanned in the media. In this example, that is "Z:\\". Note the need for
   double slashes on the Windows path separators.

   LINUX_MEDIA_MAP_ROOT - set this to the "root path" of the media in linux.
   In this example, this is /home/media.

   LINUX_TAG_PATH - this is where the MediaServer will store it's "tag" files,
   which are information about each Media File used for playback. In this
   example, there is no required place that it has to be, so a suggestion is
   /home/media/.tags

   You can also set JAVA_HOME here to point to the root directory of the Java
   Development Kit, version 1.4. If it is unset here, it will be picked up
   from the environment variables, if set. It must be set somewhere before
   starting the MediaServer.

   See the comments in the provided .mserverrc for more information. 

   The next step is to start the MediaServer, as described above.

------------------------------------------------------------------------------

PRISMIQ and the PRISMIQ logo are trademarks of PRISMIQ, Inc. in the United
States of America. Other company or product names mentioned herein may be
trademarks of their respective owners.

Copyright 2003, 2004 PRISMIQ, Inc. All rights reserved.
  

[ Back to MediaPlayer | Sections index ]

www.PRISMIQ.com / PRISMIQ Product FAQ
The opinions expressed on this community site are not neccessarily those of PRISMIQ, Inc.