Streaming issues with latest PS3 firmware update ?

[sanjeev]

Since I have updated to the latest PS3 firmware update, video has been choppy & grainy. While I am not sure if it is UMS or PS3, that is the only thing that has changed.

Anyone seen similar issues ?

[smirk]

That's odd, I haven't noticed that. I stream from UMS to PS3 and it looks clear and sharp.

[SubJunk]

Yeah I'm using the latest and it looks fine to me too

[sanjeev]

Part of the problem solved - bad HDMI cable

But the choppy video still happens - once every 20 mins. The new HDMI cable works fine for BlueRay on PS3, so the cable is fine.

I am streaming 720p & 1080p both via UMS to PS3. I have a gigabit wireless N router & a mac with 4 GB ram + 4 core, should not be a problem there. Will test with some older versions of UMS and update again.

Another issue I have seen with 2.6.0 with ffmpeg is subtitles do not get updated when we forward the movie . Subtitles are fine when starting from beginning. If we skip say 10 mins, the subititles still are 10 mins old.

[SubJunk]

Another issue I have seen with 2.6.0 with ffmpeg is subtitles do not get updated when we forward the movie . Subtitles are fine when starting from beginning. If we skip say 10 mins, the subititles still are 10 mins old.

Yeah that's a bug in FFmpeg itself, it's a big reason why MEncoder is still the default engine

[sanjeev]

Thanks for the quick reply.

The reason I am on ffmpeg is mencoder keeps giving me "content cannot be played (800288E1)" on my PS3 for many video, while ffmpeg works just fine. If you have any thoughts on that - it will be very useful.

Also any ideas on the choppy video ?

I checked with a very old UMS 1.6 and I do not see any of the above errors

Sanjeev

[Optimus_prime]

sanjeev, post us a debug log with the problem and without it, as it may shed some light on the problem

[sanjeev]

Files attached. I could see that in case of error the input stream from tsmuxer could not be read (that is just my guess).

Thanks for the help

[sanjeev]

Any news on this ?

[SubJunk]

You can try replacing mencoder.exe in 2.6.0 with the one from 1.6.0 to see if it's a MEncoder issue