Log in

View Full Version : Trying To Diagnose Why PS3 Wont Play Some MPEG4-ASP Files


Bathrone
24th March 2009, 09:17
I have a maddening problem where my PS3 wont playback some MPEG4-ASP files. It seems to be independent of streaming or USB playback and I suspect its got something to do with encoding options or some sort of header details.

Ive googled around on this problem but no answer seems to have been found. Both of these files play fine on other devices.

Ive compared two xvid files, where one plays and the other does not below:

//
// This file plays
//
CompleteName : zzz.avi
Format_Settings_Matrix/String : Default (H.263)
MuxingMode : Packed bitstream
Width/String : 640 pixels
Height/String : 352 pixels
Alignment/String : Aligned on interleaves
Encoded_Library_Settings : VBR (mtrh)

//
// This file does not play
//

CompleteName : xyz.avi
Format_Settings_Matrix/String : Custom
Width/String : 560 pixels
Height/String : 320 pixels
Alignment/String : Split accross interleaves
Encoded_Library_Settings : ABR

Both files dont use qpel or gmc. I decided to try to rebuild the index using mencoder like so:

mencoder -idx xyz.avi -ovc copy -oac copy -o newindex.avi

But this resulted in the same failure to playback. I dont know the format settings matrix string is. I know many other VBR encoded audio files play fine so thats not it.

kypec
24th March 2009, 10:43
Well, I do not own PS3 nor have any experience with it but WHY are you using different settings for your encodes?
I mean, once you have the xvid encoder settings proven to produce playable AVI files then there is only one way to determine
which parameters affect the compatibility with PS3 -> try to change only one parameter at a time and test the file.
I suspect custom quantization matrix be the biggest issue here, then probably interleaving of audio and video streams inside AVI container.

Bathrone
24th March 2009, 12:52
They arent my encodes. As I said in my original post Im trying to diagnose what the incompatible setting is.

Guest
24th March 2009, 13:17
They're not your encodes and you are using obscurantist filenames. That's a recipe for thread closure. You may explain in PM if you think the thread should be reopened.