elupus Wrote:but why do you use them at all? are all your movies wrong aspect?
This topic prompts me to ask a question I've been wondering about...
elupus, I know that I can embed pixel aspect ratio information in an mpeg4 stream. If I do so, am I correct in assuming that it gets handled by mplayer during decoding - ie *IT* scales the image it generates in software as per the specified PAR?
Whereas if I don't embed the PAR, but rather use (for example) a 'stretch' mode to adjust the aspect ratio, that in this case the scaling is handled by the display hardware / gpu - ie less cpu impact?
I have been experimenting with anamorphic encodes of HD material, and would prefer hardware over software scaling for obvious reasons; ie software decodes the pixels, hardware scales it to the desired display aspect ratio (DAR) while scaling for video output?
For example, I've done some 960x720 encodes that say 'square pixel' for embedded PAR, that I then play back using 'stretch 16:9' to get to 1280x720, and I have not observed any cpu impact from this (but I've only done a few tests so far). I'm concerned that if I embed the 'actual' PAR that I will take a cpu hit... Will I?
If this is the case, is there any way to tell XBMC about the desired *DAR* for a movie other than manually tweaking the 'display mode' popup? Perhaps something in the header for the avi/mkv/... container (as opposed to embedded in the data stream)? Alternatively...
I'm aware that I can create a movie specific mplayer config file, but it isn't clear where the split between the mplayer code and the xbox/xbmc specific display driver code is (the mplayer docs don't mention an 'xbox display driver') or even if that config file is the correct place to twiddle such things...
Anyway, I'd appreciate clarification as to 'how things work'; it might provide both me and mataman with additional options for controlling playback scaling.
Thanks!