View Full Version : AutoGK Deinterlacer Magic, please explain
Hobojobo
30th April 2004, 00:34
@lenox or @anybody who can help
I love AutoGK. It is perfect for me.
I have already spent so much time on deinterlacing with mixed success.
Even episodes of the same season can be different.
I have started DVB recording recently and I am transcoding some episodes to DivX to save some space.
The Deinterlacer of AutoGK is great.
But I would like to crop/resize my episodes to 4:3 ratio.
Now I often end up with 640:496, 640:464 and so on.
I would rather crop the episodes a bit more and loose some pixel on the borders to get a 4:3 ratio.
I assume, there will never be manual crop/resize option in AutoGK. Correct me, if I am wrong.
So I have to use GK. That is o.k for me.
Could you explain the De-Interlacing Magic of AutoGK, so I can do the steps in GK manually ?
Thank you.
len0x
30th April 2004, 16:06
actually, I wanted to have a look at this 4:3 problem (of course if you referring to 4:3 sources) myself. So probably I will soon.
Regarding deinterlacer magic - not sure what you mean. Analysis step cannot be reproduced manually - that's why its automatic...
Angelus
30th April 2004, 19:01
If you want to you can use decomb to de-interlace your material. Decomb 5.1.1 was released by neuron2 about a month ago:
http://forum.doom9.org/showthread.php?s=&threadid=73812&highlight=decomb
Then you could fool around with something like this for an avisynth script to import into GK:
AviSource("c:\myvideo.avi")
LoadPlugin("C:\DVD Backup Programs\DoItFast4U\new.avs\decomb.dll")
FieldDeinterlace()
Use that if your input video is pure video. If it is "hybrid" video, try a combo like this:
AviSource("c:\myvideo.avi")
LoadPlugin("C:\DVD Backup Programs\DoItFast4U\new.avs\decomb.dll")
Telecide(guide=1)
Decimate(mode=3,threshold=3)
You'll have to fool around with the settings and read the readme included with the Decomb filter to figure out what settings best apply your video.
therealjoeblow
30th April 2004, 22:56
Originally posted by len0x
actually, I wanted to have a look at this 4:3 problem (of course if you referring to 4:3 sources) myself. So probably I will soon.
Regarding deinterlacer magic - not sure what you mean. Analysis step cannot be reproduced manually - that's why its automatic...
@len0x - I did "The Maltese Falcon" a few weeks ago, at 640 wide it auto crops to 480 high, perfect 4x3 (1.33:1); but at 608, it crops to 392 (IIRC), which is 1.55:1.
608x448 would be closer to 1.33:1, and still a multiple of 32, don't know why it doesn't choose that resolution (but as you know, I'm no expert in these things).
Well, I played around with my avs script and got 4:3 ratio to work properly. The problem now resides in crop procedure. Right now AutoGK tries to keep AR which it got after initial cropping. Very rarely you have actually proper 4:3 picture - you still get 4:3 more often in the end though, coz of mod32/16 restrictions. But lots of sources (like Friends or oldies) have small black bars on left and right which significally change input AR. But if ppl happy to enforce 4:3 output on upto 1.4 (1.45) actual AR with more stuff cropped that needed - I can do that.
Hobojobo
1st May 2004, 12:11
I would love to have a enforced 4:3 crop/resize-feature to ensure a proper 4:3 output.
Loosing some bits on the border would be ok, even necessary to avoid a ratio error.
I vote for it !!!! :)
henryho_hk
15th May 2004, 02:51
Some cropping must be done before resize in order to
obtain the _right_ AR. This is by the nature of these
analog output resolutions.
The point is... once you have your required picture,
do you want the black bars to be removed?
AutoGK should stick to one-resize only so as to avoid
quality loss. However, I think that those mod-4 and
mod-16 limitations had caused len0x many headache pills
already.
len0x
15th May 2004, 12:10
I hope everybody following this thread knows that 4:3 is now always enforced for 4:3 sources.
Hobojobo
15th May 2004, 12:45
Yep.
And I am really grateful for the 4:3 output.:D
For me AutoGK is sort of perfect.
A direct mpg2-input feature would complete "my" AutoGK, but that's kind of solved.
Thank you for the nice/useful piece of software.
:thanks:
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.