Bloated resolution while using Preview in AutoGK

[unskinnyboy]

Hi neuron2...I am posting this here because this seems like a DGIndex issue. I was testing out my new PC. Made a clean install of AutoGK 2.09b and ran a preview of NTSC R1 of Short Circuit (http://www.amazon.com/exec/obidos/tg/detail/-/B0000UJDLM/qid=1117943585/sr=8-1/ref=pd_csp_1/103-5612846-0638262?v=glance&s=dvd&n=507846) with Fixed Width = 672. The resultant preview resolution was 672x8464 :confused:. Then I upgraded DGIndex from 1.3.0 to 1.3.1b9 and ran a preview again, this time the Media player itself didn't open for preview. Then I tried opening the *_preview.avs from the agk_tmp folder directly in VDM and Nandub, but they would just shut down. After a lot of attempts, one time it opened in Nandub and the resolution under File Information was shown as 672x12688 :confused:.

Totally confused, I cut a 15MB sample of the vob out and ran a 75% quality 1-pass in AutoGK and it worked.

What am I doing wrong here? Didn't know whether to post this in the AutoGK forum or DGIndex forum, please move the thread if you feel this is the wrong forum.

I have uploaded the d2v and avs into a folder and the test vob, AutoGK log, and avi into another folder, all under one master folder with the same name as my nick into your FTP. Please have a look. If you need any more info, samples etc, please ask.

TIA

[Guest]

I made a script with just the mpeg2source() call with your VOB and served it into VirtualDub. The size was as expected: 720x480. Thus, it appears DGMPGDec is doing its job.

Start adding your filters one-by-one until you identify the culprit.

I cannot perform this process for you because I do not have GK installed.

EDIT: I downloaded autocrop() and reproduced your problem. Standby...

[Guest]

The first frame of the VOB is very dark. In conjunction with the high threshold set for the first autocrop() call, this causes c_width and c_height to be an incorrect set. I got c_width=84 and c_height=221 with threshold 70. This gets magnified later in the script. If you reduce your thresholds to 20, things start to look reasonable.

I don't know who sets these thresholds and how they are determined, but it certainly looks like an area in need of attention.

This is how I display values of variables in a script:

subtitle(movie, String(c_width) + ", " + String(c_height))

[unskinnyboy]

You hit the nail on the head DG, Thank you. I had bumped the autocrop() threshold from the AutoGK default of 34 to 70, since a previous preview with 34 gave bad cropping. Now I reduced it to 34 and did another preview and this time it was fine.

I had set the number of frames to examine to 10 (samples=10). So unfortunately for me, looks like all the 10 frames were dark and autocrop() got thrown off by them.

But still who should be addressing this issue and how? Or is it that the resize algorithm can't be any more refined?

[len0x]

If you get bad values from autocrop, then nothing can be done afterwards. That is why you have control over threshold, number of frames and starting frame for autocrop filter in AutoGK.

[unskinnyboy]

OK, got it and thought as much. Thanks len0x and DG.