[Video] Mencoder pipe error?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Choose Mencoder or tsMuxer as transcoder

What is the expected output? What do you see instead?
- Corrupted Data 
- Fetching Information on a movie displays the correct info (using FFmpeg 
to do that?):
   - Filesize always 94GB ?
   - Length and Dimensions are fine.

What version of the product are you using? On what operating system?
- PMS 1.02.1
- Windows XP Pro
- Java version 1.6.0_07

If you are transcoding a media file, which engine are you using (mencoder, 
avisynth/mencoder, tsmuxer?)
- Happens only with Mencoder / TsMuxer
- FFmpeg runs fine

According to the debug.log it looks like the mencoder is not able to read 
from the created pipe. I get the same error if i just try to start the 
mencoder with the same command in the commandline without any previous 
initialization.
I'm not sure if this issue is related to the PMS or it has something to do 
with named pipes in windows. Can it be that a specific WinXP setting is 
prohibiting creating pipes? 

Original issue reported on code.google.com by mfrey0@gmail.com on 11 Jan 2009 at 11:00

Attachments:

• PMS_MEncoder_PipeError.log

[GoogleCodeExporter]

Did a little digging online, maybe it has something to do with a 
firewall/antivirus, 
any blocking software... (It seems you can block them with a simple registry 
setting) 
I cannot think of something else who could break that mechanism

Original comment by ps3mediaserver@gmail.com on 16 Jan 2009 at 9:19

[GoogleCodeExporter]

seems that sunbelt firewall is the culprit

http://ps3mediaserver.org/forum/viewtopic.php?f=6&t=218

waiting for your confirmation

I will maybe later detecting this software and display a warning if installed

Original comment by ps3mediaserver@gmail.com on 30 Jan 2009 at 11:25

• Changed title: [Video] Mencoder pipe error?
• Changed state: Accepted

[GoogleCodeExporter]

Thought about that. I also use the Sunbelt Firewall and i tried every switch i 
found 
in the preferences. Even disabling it didnt help like written in the forum...

I'm not at home at the moment, but it seems the Registry Fix works. I'll test 
that 
one once i'm home.

Nice hint. Thanks alot!

Original comment by mfrey0@gmail.com on 30 Jan 2009 at 12:35

[GoogleCodeExporter]

Original comment by robinmul...@gmail.com on 20 Jul 2009 at 8:12

• Changed state: Invalid