The post isn't lost and I haven't forgotten it's there. Just have to find time to look at it and work out exactly what's going on with your captures as no one else has ever said anything about problems with aspect ratio detection.
Cheers,
Arkay.
Copied here so it doesn't get lost...
Quote:
|
Originally Posted by arkay
Yep, just changing those values is all that is required to adapt to the source res. Although, in technical terms you also need to know the exact source res after the crop is performed. You can find this out. If you run Crunchie from the command line like this:
crunchie.exe -d
If will spew out debugging information (to the log and screen), including the crop detection. You should see a line in the output something along the lines of:
"Final crop string is xx:yy:xx:yy"
Those values will tell you what your image was really cropped too. Using values for Ar16:9/AR4:3 any larger or smaller than the values returned will result in scaling of the image.
The ratio is quite simple determined by the size of the crop area. If x > than 640 it assumes 16:9, else 4:3. At some point I need to make this more accurate as it propably won't work for HD files etc.
|
Hi,
Maybe you can point out a rule from the "genre tag" in the dvr-ms files. For instance a profile for films in 16:9 and a 4:3 for old series ?
Here is my results on the first 7'28'' of Alien movie (the original dvr-ms file is 267 463 723 bytes for a resolution of 720x576 with upper and lower black bars and bitrate at 159622kbps) :
Here is a cap at 0:05:30:
the caps is 704x576 (whereas dvr-ms info in Media player says 720... dvr is a tricky guy...)
Default format, double pass, double deinterlace, bitrate 1000, auto-crop with default AR169
=> 640x368, 16:9, 63 611 434 bytes
Default format, double pass, double deinterlace, bitrate 1000, target resolution higher AR169
= > 704x368, 16:9, 63 606 238 bytes... nearly the same size. Rescaling means harder compression ? Seems OK when playing in WMplayer but the caps from Cyberlink PowerDVD shows something else (seems that pixels are not "square"). In Cyberlink I use for the aspect ratio "original video source size". So it seems that WMplayer does a correction when playing the files...
Force 4.3, double pass, double deint, bitrate 1000, auto-crop
no comment.
> What should I do ? Keep the original AR43 and AR169 ini definitions ?
WMPlayer seems to do the apropriate ratio correction when playing, but how to be sure that the file is universal and play well with other environments (MCE, Cyberlink Player, Kiss DP500 player...).
I have another sample. Here is a caps from a MPEG2 file (one extracted from Terratec application) and the original stream appears like that (it is 544x576)...
For this kind of stream, how cruncher will react ? Do I have to force the 4:3 ratio to extend the picture (even if it is cropped afterwards) ? Should you stick to original AR ini settings ?
I found a neat editor for dvr-ms (dcut) but not for plain vanilla Mpeg2. So, if I test crunchie on one of my mpeg2 movie, I have to do it on the whole movie and it takes hours so I prefer to ask you before
Do you have a web reference that treats that mad ratio stuff ?
Cheers.
