Trouble with Placeshifter video playback on linux

[g-man]

Placeshifter works without a problem on XP and my MVP, but I can't seem to get video playback on my Ubuntu 6.10 box.

Does anyone have any ideas on where I should start looking. The menu comes up fine, just no video playback. I see that there is a command line error, but don't know where or what to change it to. I have attached the errors.

Thu 2/22 12:29:47.390 MPlayer was launched successfully
Thu 2/22 12:29:47.394 Waiting for MPlayer to finish loading
Thu 2/22 12:29:48.420 stdout:MPlayer 2:0.99+1.0pre8-0ubuntu8 (C) 2000-2006 MPlayer Team
Thu 2/22 12:29:48.422 stdout:CPU: AMD Athlon(tm) processor (Family: 6, Model: 4, Stepping: 2)
Thu 2/22 12:29:48.422 stdout:CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
Thu 2/22 12:29:48.422 stdout:Compiled with runtime CPU detection.
Thu 2/22 12:29:48.533 stdout:
Thu 2/22 12:29:48.552 stdout:
Thu 2/22 12:29:48.634 stderr:Unknown option on the command line: -stream-buffer-size
Thu 2/22 12:29:48.635 stderr:Error parsing option on the command line: -stream-buffer-size
Thu 2/22 12:29:48.645 stdout consumer has closed
Thu 2/22 12:29:48.655 stderr consumer has closed
Thu 2/22 12:29:57.407 Done waiting for MPlayer to finish loading
Thu 2/22 12:29:57.408 Waiting for MPlayer to pass time:0
Thu 2/22 12:30:07.415 Done waiting for MPlayer to pass time:0
Thu 2/22 12:30:07.416 Execute media command 1
Thu 2/22 12:30:07.417 Closing down mplayer
Thu 2/22 12:30:07.417 Sending mplayer command:inactive_file
Thu 2/22 12:30:07.418 Sending mplayer command:quit
Thu 2/22 12:30:07.422 MPlayer process exit code:1
Thu 2/22 12:30:07.498 Error w/ Media Thread: java.net.SocketException: Broken pipe
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at sage.miniclient.MiniClientConnection.MediaThread(MiniClientConnection.java:1360)
at sage.miniclient.MiniClientConnection.access$000(MiniClientConnection.java:6)
at sage.miniclient.MiniClientConnection$3.run(MiniClientConnection.java:264)
Thu 2/22 12:30:07.570 Connection accepted by server

[brewston]

I've got it working on Ubuntu 6pointsomething. I would check that its picking up the mplayer binary that came with placeshifter and not another one you have installled. I do this by temporarily renaming the non-sage one


Tim

[g-man]

I originally had the mplayer that came with the client, but received the attached error. I created a symlink to my mplayer and that gave me the previous error.

Thu 2/22 12:42:39.710 stderr:MPlayer interrupted by signal 4 in module: init_audio_codec
Thu 2/22 12:42:39.710 stderr:- MPlayer crashed by an 'Illegal Instruction'.
Thu 2/22 12:42:39.710 stderr: It usually happens when you run it on a CPU different than the one it was
Thu 2/22 12:42:39.710 stderr: compiled/optimized for.
Thu 2/22 12:42:39.711 stderr: Verify this!
Thu 2/22 12:42:39.711 stderr:- MPlayer crashed by bad usage of CPU/FPU/RAM.
Thu 2/22 12:42:39.711 stderr: Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
Thu 2/22 12:42:39.711 stderr: disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
Thu 2/22 12:42:39.712 stderr:- MPlayer crashed. This shouldn't happen.
Thu 2/22 12:42:39.712 stderr: It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
Thu 2/22 12:42:39.712 stderr: gcc version. If you think it's MPlayer's fault, please read
Thu 2/22 12:42:39.712 stderr: DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
Thu 2/22 12:42:39.712 stderr: won't help unless you provide this information when reporting a possible bug.
Thu 2/22 12:42:39.786 stderr:CACHE THREAD ENDING
Thu 2/22 12:42:39.786 stderr consumer has closed
Thu 2/22 12:42:39.787 stdout consumer has closed
Thu 2/22 12:42:49.243 Done waiting for MPlayer to finish loading
Thu 2/22 12:42:49.244 Waiting for MPlayer to pass time:0
Thu 2/22 12:42:59.253 Done waiting for MPlayer to pass time:0
Thu 2/22 12:42:59.256 Execute media command 1
Thu 2/22 12:42:59.257 Closing down mplayer
Thu 2/22 12:42:59.257 Sending mplayer command:inactive_file
Thu 2/22 12:42:59.258 Sending mplayer command:quit
Thu 2/22 12:42:59.259 MPlayer process exit code:1
Thu 2/22 12:42:59.261 Error w/ Media Thread: java.net.SocketException: Broken pipe
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at sage.miniclient.MiniClientConnection.MediaThread(MiniClientConnection.java:1360)
at sage.miniclient.MiniClientConnection.access$000(MiniClientConnection.java:6)
at sage.miniclient.MiniClientConnection$3.run(MiniClientConnection.java:264)
Thu 2/22 12:42:59.350 Connection accepted by server

[brewston]

Right, the first error makes sense as it appears that miniclient.jar is calling the native mplayer with -stream-buffer-size argument which the native version doesn't recognise

The second error looks like sage's mplayer doesn't like your CPU :-) what CPU is it ? Some kind of AMD ? I can check whats my my Ubuntu box tomorrow (its AMD of some kind)

Tim

[brewston]

Here we go :

http://www.mplayerhq.hu/DOCS/HTML/en/faq.html#id2539879

I would contact support and see what they say.

I've google'd stream-buffer-size and mplayer and I suspect its something special that Sage have coded into their version of mplayer

Tim

[g-man]

Thanks Brewston,

It's just a standard AMD Athlon 1.2. I'll contact support and see what they say.

[brewston]

Here's cpuinfo on my box :

cat cpuinfo

processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(tm) XP 1500+
stepping : 2
cpu MHz : 1300.315
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnowbogomips : 2603.26