@tmknight:
The problem is definitely that the built-in 'rtmpdump://' protocol isn't being selected by pmsencoder and it's defaulting to mencoder which has no idea what to do. add
- Code: Select all
rtmpdump.path = /usr/bin/rtmpdump
(or wherever) to your PMS.conf and restart. Your
pmsencoder.log should then report:
- Code: Select all
: setting global variable: RTMPDUMP = /usr/bin/rtmpdump
If that doesn't fix it then look further down to see if it says
- Code: Select all
: loading built-in script: scripts/rtmpdump.groovy
and that later on it isn't being overriden by a user script, e.g.
- Code: Select all
: loading user script: rtmpdump.groovy
You may need to look inside the user scripts in your pmsencoder script folder to make sure. Remove any script that mentions 'rtmpdump://'. I just played the same trailer no problem, and my pmsencoder.log shows:
- Code: Select all
: invoking matcher for: rtmpdump://rtmp2pms?-r=rtmpe%3A%2F%2Fcp39466.edgefcs.ne... etc
: 1 match ([rtmpdump://]) for: rtmpdump://rtmp2pms?-r=rtmpe%3A%2F%2Fcp39466.edge... etc
: downloader command: /usr/local/bin/rtmpdump -o /tmp/ps3med... etc
: transcoder command: ffmpeg -v 0 -y -threads 4 -i /tmp/ps3mediase... etc
Attach
pmsencoder.log if you have any questions.
@rocco24:
Does Jumpy reappear if you also exit and restart PMS when you restart the PS3?
I need to see
jumpy.log (and
pmsencoder.log) as well. The
debug.log shows you trying a bunch of megaupload links (which will fail unless you wait 60 seconds before clicking them), then some other links, but it's not clear at what point you turn off the PS3 and then turn it back on again. If you would do a short test where you start PMS, play one link, then restart the PS3 and attempt to browse again the scenario may be easier to follow inside the logs (zip your
PMS.conf,
debug.log,
jumpy.log and
pmsencoder.log together as one attachment). I'm pressed for time today but will have another go at attempting to recreate your problem tomorrow.