PS3mediaserver

[leez0rs]

Hi

I'm a little worried about read/write activity to my flash drive. I found out that the PS3 mediaserver writes a log to the flashdrive...

Should I be worried?

 

/Lappen

Yes, after 100,000 or so writes, the flash drive might wear out.  Reading is not an issue, writes are limited.

 

Configure the PS3 Media server drive to "write" elsewhere... one of your data disks perhaps.

 

How would one do this?  I haven't seen any examples anywhere and I don't think the conf file is documented, but I may be wrong.

[vwalien]

Hi

I'm a little worried about read/write activity to my flash drive. I found out that the PS3 mediaserver writes a log to the flashdrive...

Should I be worried?

 

/Lappen

Yes, after 100,000 or so writes, the flash drive might wear out.  Reading is not an issue, writes are limited.

 

Configure the PS3 Media server drive to "write" elsewhere... one of your data disks perhaps.

 

How would one do this?  I haven't seen any examples anywhere and I don't think the conf file is documented, but I may be wrong.

 

I tried to figure this out back in August, unfortunately it was not possible to change the log directory, PS3Media server would only output to the directory the process was launched from....

 

[edit]: It wasn't possible to disable the logging either, some users were able to make a sym link for the debug.log to /dev/null, but you can't create sym links on the flash drive. So that was another idea that fell through.

 

Maybe it's possible to move the whole PMS install folder to a data disk and run it from there as well?

[vindes]

I tried the other version of ffpeg--get a different error then:

Package ffmpeg-0.5-i486-1alien.tgz installed.                                            id:/bo
root@Unraid:/boot/custom/ps3mediaserver/mencoder# ffmpeg
ffmpeg: relocation error: /usr/lib/libavdevice.so.52: symbol snd_pcm_htimestamp, version ALSA_0.9 not defined in file libasound.so.2 with link time reference

 

I had that problem as well.  Needed to update to the latest ALSA libraries.

 

cd /boot/custom/ps3ms/mencoder
wget http://slackware.osuosl.org/slackware-current/slackware/l/alsa-lib-1.0.23-i486-1.txz
installpkg alsa-lib-1.0.23-i486-1.txz

 

You'll also want to remove the old alsa-lib-1.0.15-i486-1.tgz from that directory and edit your /boot/config/go script to installpkg *.tgz *.txz

 

Not sure there's any reason the Mencoder libraries linked on the wiki page should include the 0.15 version instead of the 0.23 version.  But the alternate ffmpeg (i486 version) definitely chokes on the older alsa libraries.

 

[mkny13]

Thanks for the reply!  I was beginning to fear that my post was getting buried.

 

Your tip seems to have gotten me one step closer, but still not solved.  After downloading and installing that package, ffmpeg works better.  I removed the other alsa libs, edited my go file, and rebooted.  Sadly, I get the same bad behavior when I browse to a VIDEO_TS folder on the Ps3 (no file found).  So I logged into my unraid box and discovered something weird:

 

 

root@Unraid:/boot/custom/ps3mediaserver/mencoder# ffmpeg
FFmpeg version 0.5, Copyright (c) 2000-2009 Fabrice Bellard, et al.
  configuration: --prefix=/usr --mandir=/usr/man --enable-gpl --enable-postproc --enable-avfilter --enable-swscale --enable-libdc1394 --enable-libgsm --enable-libfaad --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libx264 --enable-memalign-hack --enable-pthreads --enable-x11grab --enable-bzlib --enable-zlib --enable-shared --enable-static --disable-debug --logfile=/tmp/ffmpeg_conf.log --extra-cflags=-I/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/include -DRUNTIME_CPUDETECT --extra-ldflags=-L/tmp/build/tmp-ffmpeg/ffmpegdeps/usr/lib
  libavutil     49.15. 0 / 49.15. 0
  libavcodec    52.20. 0 / 52.20. 0
  libavformat   52.31. 0 / 52.31. 0
  libavdevice   52. 1. 0 / 52. 1. 0
  libavfilter    0. 4. 0 /  0. 4. 0
  libswscale     0. 7. 1 /  0. 7. 1
  libpostproc   51. 2. 0 / 51. 2. 0
  built on Mar 20 2009 11:04:02, gcc: 4.2.4
At least one output file must be specified
root@Unraid:/boot/custom/ps3mediaserver/mencoder# cd /boot
root@Unraid:/boot# cd ..
root@Unraid:/# mplayer
mplayer: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory
root@Unraid:/#

 

So ffmpeg works (or seems to) in the mencoder folder.  But when it's called from another folder, I get the same old error.  Could it be that ps3ms is calling it and getting the second (bad) result?  How would I fix that?  Just move the ffmpeg file?  Is there a linux equivalent to the windows PATH that I should edit?  More help needed!  Thanks

[vindes]

So ffmpeg works (or seems to) in the mencoder folder.  But when it's called from another folder, I get the same old error.  Could it be that ps3ms is calling it and getting the second (bad) result?  How would I fix that?  Just move the ffmpeg file?  Is there a linux equivalent to the windows PATH that I should edit?  More help needed!  Thanks

 

I think that mplayer error you're getting is it trying to open a window to display but you don't have X set up (as most of us don't on an unraid box).  At least I think that's what it is.  I get that same error as well if I just type "mplayer".  Try just "ffmpeg" from other directories and you should be ok.

 

i haven't tried playing anything from a VIDEO_TS folder.  I'll try it out in the next few days and see.

[mkny13]

Duh--brain fart on my part.  My head thought ffmpg both times, but my fingers typed mplayer the 2nd time.  Just tried running ffmpeg from root directory, it looks ok.  Still doesn't solve my VIDEO_TS issue though.  Thanks for replying.  Looking forward to how your VIDEO_TS tests go.

 

This weekend, I'm going to clear my debug.log, try browsing a VIDEO_TS, and post the results here and at the ps3ms forum (though I didn't get much of a response there last time).  Since it seems like I have the dependencies all straightened out, maybe we'll now be able to pin down the problem.

[molesza]

I've managed to install ps3mediaserver on my unraid server. Thanks to everyone who contributed to making this a reality.

 

If I select an avi video it works just fine but MKV files the video plays slower than the audio so sync is way out very quickly. I am choosing the video file directly and not going to transcode. The reason for this is it wont start playing the video under transcode for whatever reason. It must be transcoding when i select the file though because the ps3 doesnt natively support MKV does it?

 

My Unraid box is running a Q6600 cpu with 4gig of ram. It worked fine when the box was running windows.

 

Does anyone have any suggestions for sorting out the sync issue?

[MarkV]

Are there test files one could recommend for the PS3 to show performance with streaming, with encoding at different resolutions?  I'm trying to stream a 1080p mp4 that is supposedly in the right format (DVDfab'd for PS3 with AC3 audio).  It's a stop and go fest (can't really call it judder).  

Audio works when the video actually plays.

Checking the unRAID server shows almost no load on a quad core 2.8GHz box.

PS3 shows network speed around 10-15 Mbps when video is actually playing.

Gige connection and PS3 is using a wired connection.

 

I get 40+MB/second reads from the server to a windows box.

[mkny13]

This weekend, I'm going to clear my debug.log, try browsing a VIDEO_TS, and post the results here and at the ps3ms forum (though I didn't get much of a response there last time).  Since it seems like I have the dependencies all straightened out, maybe we'll now be able to pin down the problem.

 

Here's the latest log  As always, I'd appreciate any advice anyone has to offer.  Strwaming an mp4/m4v works beautifully, it just chokes on VIDEO_TS.  I really don't want to have to maintain two formats.

[Kryspy]

Here's my pms.conf file.

 

 

thumbnails = true

mencoder_ass = true

embed_dts_in_pcm = false

mencoder_disablesubs = true

mencoder_nooutofsync = false

folders = /mnt/user/Videos,/mnt/user/Music,/mnt/user/Pictures

minimized = true

network_interface = eth0

hostname = 192.168.1.1XX

mencoder_usepcm = false

mencoder_remux_mpeg2 = true

mencoder_mux_compatible = false

dvd_isos_thumbnails = true

use_mplayer_for_video_thumbs = true

usecache = false

hide_media_library_folder = true

hide_extensions = true

mencoder_yadif = false

mencoder_forcefps = false

fix_25fps_av_mismatch = false

tsmuxer_forcefps = false

 

 

I am streaming gigabit wired to my PS3.  Server is a AMD Athlon II 235 with 2 GB of RAM.  Everything I stream is clean and judder free.  This includes Video_TS files which I just rip to a single VOB file with DVD Shrink.

 

Kryspy

 

Kryspy

[mkny13]

Which version of ps3ms are you running?

[mkny13]

I'm going to try out your conf, edited only to match my folder names.  Anyone know the quickest way to restart PMS via the shell?  Just killall java, then run PMS.sh again?

[MarkV]

I'm going to try out your conf, edited only to match my folder names.  Anyone know the quickest way to restart PMS via the shell?  Just killall java, then run PMS.sh again?

I'm hardly a pro (more of a neophyte to ps3mediaserver), but this seems to work for me.

[mkny13]

@Kryspy tried it out, same error as before.

[Kryspy]

I'm using the latest beta files.

 

Kryspy

[mkny13]

I've tried 1.10 and the betas, but now I'll double check with the beta and your conf.

[mkny13]

With 1.20.412, I can see the following errors/warnings as soon as I run PMS.sh:

 Error in MediaInfo Library loading: Unable to load library 'mediainfo': libmediainfo.so: cannot open shared object file: No such file or directory
[main] TRACE 15:45:36.264 Make sure you have libmediainfo and libzen installed
[main] TRACE 15:45:36.267 The server will now use the less accurate ffmpeg parsing method

 

and

 

[main] TRACE 15:45:36.400 Checking font cache... launching simple instance of MPlayer... You may have to wait 60 seconds !
[main] TRACE 15:45:36.407 [127] Cannot launch MPlayer / Check the presence of /boot/custom/pms-linux-1.20.412/mplayer ...
[main] TRACE 15:45:36.457 [127] Cannot launch MPlayer / Check the presence of /boot/custom/pms-linux-1.20.412/mplayer ...
[main] TRACE 15:45:36.458 Done!
[main] TRACE 15:45:36.486 Registering transcoding engine FFmpeg Audio
[main] TRACE 15:45:36.518 Registering transcoding engine MEncoder
[main] TRACE 15:45:36.519 Registering transcoding engine MPlayer Audio
[main] TRACE 15:45:36.519 Registering transcoding engine MEncoder Web
[main] TRACE 15:45:36.519 Registering transcoding engine MPlayer Video Dump
[main] TRACE 15:45:36.520 Registering transcoding engine MPlayer Web

 

I don't have a mplayer folder in the pms folder.  Per the directions on the wiki and elsewhere (unless I missed something), in the mencoder folder I have MPlayer-r29301-i486-1alien.tgz, which is loaded with all the other packages.  I don't see this error with v1.10.

[Kryspy]

mkny13,

 

I would delete installation and start over.  I used the instructions found at http://bloggyvonbloggerstein.blogspot.com/2010/03/ps3mediaserver-on-unraid.html

 

There is obviously something not right about your install.

 

Kryspy

 

[hoeg]

Just got a PS3 and trying to install this.  I am stuck at testing java, mencoder, and ffmpeg.  When I telnet and type java it gives a long list of switches and stuff.  Then I type mencoder and I get -bash: mencoder: command not found.  ffmpeg also get command not found.  Can anyone point me in the direction to fix this?  Thanks.

 

Edit:  I changed the file extension of the mplayer file and the ffmpeg file from .gz to .tgz.  Now I can play xvid files and mkv files.  But .mp4 files and .m4v files say "data is corrupted" - any ideas?  Did I mess something up by changing the file extensions?  On the downloads the link says .tgz, but they download with .gz.

 

Here is what I get when I run the mencoder and ffmpeg files:

root@Media:~# mencoder
MEncoder r29301-4.2.4 (C) 2000-2009 MPlayer Team
No file given

Exiting... (error parsing command line)
root@Media:~# ffmpeg
-bash: /usr/bin/ffmpeg: cannot execute binary file
root@Media:~#

[hoeg]

Ok, I guess I have it working now.  Had to use the ffmpeg that vwalien used:

3) type "ffmpeg"

it should show some kind of message like "ffmpeg version 0.5 copyright" etc...

I had to use ffmpeg-0.5-i486-1alien.tgz to get it to run on mine. I have a p4 3.2gig x86 system, and the other library ffmpeg-0.5-x86_64-2alien.tgz would actually install, but when I type "ffmpeg" at command line it would say "cannot execute binary file". switching versions fixed that.

 

Now on the mp4 and m4v I can choose the transcode option and they will play, but shouldn't they play without transcoding?  Still get the "file is corrupt" error without going to the transcode way.  Also, when playing an m4v with the transcode option, the sound seems to be cutting out on low volume parts of movies.  Guessing there must be an option for the config file I can change to fix it?

[monza]

Hi

I'm a little worried about read/write activity to my flash drive. I found out that the PS3 mediaserver writes a log to the flashdrive...

Should I be worried?

 

/Lappen

Yes, after 100,000 or so writes, the flash drive might wear out.  Reading is not an issue, writes are limited.

 

Configure the PS3 Media server drive to "write" elsewhere... one of your data disks perhaps.

 

How would one do this?  I haven't seen any examples anywhere and I don't think the conf file is documented, but I may be wrong.

 

I tried to figure this out back in August, unfortunately it was not possible to change the log directory, PS3Media server would only output to the directory the process was launched from....

 

[edit]: It wasn't possible to disable the logging either, some users were able to make a sym link for the debug.log to /dev/null, but you can't create sym links on the flash drive. So that was another idea that fell through.

 

Maybe it's possible to move the whole PMS install folder to a data disk and run it from there as well?

 

 

i just setup PS3MS on my unRAID yesterday, thanks to all the people who have written guides and tips. Most things seem to work, i just need to tweak some settings.

 

Today i had a look at the debug.log and found that it logs every few minutes and the file already has over 28000 lines! Here is a snipet from the last few minutes... Can someone please tell me the best way to stop this? I am worried about all those writes to my poor flash drive.

 

[Thread-6] DEBUG 12:36:53.418 Multicast socket is on interface: /192.168.0.5
[Thread-6] DEBUG 12:36:53.418 Socket Timeout: 0
[Thread-6] DEBUG 12:36:53.418 Socket TTL: 32
[Thread-7] DEBUG 12:36:53.418 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:54.207 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:54.358 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:54.887 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:55.308 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:55.778 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:56.357 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:56.427 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:56.728 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:36:57.488 Receiving a NOTIFY from [192.168.0.5:34164]
[Thread-7] DEBUG 12:38:39.388 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:39.390 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:39.400 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:39.410 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:39.420 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:39.443 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:42.390 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:42.400 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:42.401 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:42.414 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:42.428 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:42.439 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:45.391 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:45.392 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:45.393 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:45.413 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:45.414 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:38:45.445 Receiving a NOTIFY from [192.168.0.3:1900]
[Thread-7] DEBUG 12:39:01.758 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-7] DEBUG 12:39:01.872 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-7] DEBUG 12:39:01.982 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-7] DEBUG 12:39:02.092 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-6] TRACE 12:39:57.695 Sending ALIVE...
[Thread-6] DEBUG 12:39:57.695 Setting multicast network interface: name:eth0 (eth0) index: 2 addresses:
/192.168.0.5;

[Thread-6] DEBUG 12:39:57.695 Sending message from multicast socket on network interface: name:eth0 (eth0) index: 2 addresses:
/192.168.0.5;

[Thread-6] DEBUG 12:39:57.695 Multicast socket is on interface: /192.168.0.5
[Thread-6] DEBUG 12:39:57.695 Socket Timeout: 0
[Thread-6] DEBUG 12:39:57.695 Socket TTL: 32
[Thread-7] DEBUG 12:39:57.695 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:39:57.975 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:39:58.285 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:39:59.145 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:39:59.465 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:40:00.125 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:40:00.655 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:40:01.415 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:40:01.715 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-7] DEBUG 12:40:02.055 Receiving a NOTIFY from [192.168.0.5:41733]
[Thread-6] TRACE 12:43:02.282 Sending ALIVE...
[Thread-6] DEBUG 12:43:02.282 Setting multicast network interface: name:eth0 (eth0) index: 2 addresses:
/192.168.0.5;

[Thread-6] DEBUG 12:43:02.283 Sending message from multicast socket on network interface: name:eth0 (eth0) index: 2 addresses:
/192.168.0.5;

[Thread-6] DEBUG 12:43:02.283 Multicast socket is on interface: /192.168.0.5
[Thread-6] DEBUG 12:43:02.283 Socket Timeout: 0
[Thread-6] DEBUG 12:43:02.283 Socket TTL: 32
[Thread-7] DEBUG 12:43:02.283 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:02.592 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:03.242 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:03.692 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:04.132 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:04.702 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:05.212 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:06.032 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:06.762 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:07.042 Receiving a NOTIFY from [192.168.0.5:48350]
[Thread-7] DEBUG 12:43:31.759 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-7] DEBUG 12:43:31.867 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-7] DEBUG 12:43:31.977 Receiving a NOTIFY from [192.168.0.18:32797]
[Thread-7] DEBUG 12:43:32.085 Receiving a NOTIFY from [192.168.0.18:32797]

[mkny13]

I believe there should be a setting to turn the log frequency down from full debug mode to something that would write less frequently...let me know if you find it

 

I'm coming close to the conclusion that ps3ms just isn't ready for primetime on unraid.  Lots of squeezing a square peg into a round hole is required.

[monza]

I believe there should be a setting to turn the log frequency down from full debug mode to something that would write less frequently...let me know if you find it

 

I'm coming close to the conclusion that ps3ms just isn't ready for primetime on unraid.  Lots of squeezing a square peg into a round hole is required.

 

ok, ill have a browse of the ps3ms forums and let you know if i find anything. Install for me was fairly straightforward thanks to the guide from warrior (thanks!). I did notice that when trying to test ffmpeg i got:

 

root@Tower:/mnt/disk4/torrents/tdownload# ffmpeg -version

-bash: /usr/bin/ffmpeg: cannot execute binary file

 

But i tried about ten different movies in different containers and i mananged to get audio and video on all of them...so i was a bit confused that the error was appearing but i could still see/hear everything. 

 

 

In the short term, does anyone have a quick way of stopping/starting PS3MS? If not, i am tempted to just comment out the relevant lines in my go script to diable ps3ms, then reboot the server (all so ps3ms doesnt keep writing ridiculous amounts of info into that debug file!)

 

cheers

 

 

[prostuff1]

I'm coming close to the conclusion that ps3ms just isn't ready for primetime on unraid.  Lots of squeezing a square peg into a round hole is required.

 

unRAID was never really designed to be used like we are trying to use it.  unRAID is first and foremost a media storage device.

 

We are trying to get it to do many more and different things than it was designed to do.

[prostuff1]

In the short term, does anyone have a quick way of stopping/starting PS3MS? If not, i am tempted to just comment out the relevant lines in my go script to diable ps3ms, then reboot the server (all so ps3ms doesnt keep writing ridiculous amounts of info into that debug file!)

 

If you have unMenu installed You can probably create some Start and Stop buttons for use on the user scripts page.  That is exactly what I did for the Crashplan service that is installed on my server.