The deinterlacing thing

[majinsnake]

Okay, i did read some past threads on Interlacing/Deinterlacing. If i have to go by what was said to "Starfish" and his futurama stuff to use avisynth, that's fine. This is a ntsc dvd.
I am using AutoGK 1.96, stable version. I have tried the option "Force deinterlacing when souce is detected as a hybrid" and "Tune kernelDeInt filter threshold (1-255)". The little blurryness/blurryness of the pixels still happens. The KernelDeInt Filter i have used the default which is 10 and move it to 12 for to try it out. I use Xvid, since divx takes long to encode and Ac3 for audio. I mostly use custom size for how much the video is encoded. The quality i prefer ranges from 50 to 70%. As long as it is viewable and i can tell what is going on, im happy.

Thankyou, Bradley

[unskinnyboy]

So what exactly is your issue? blurriness? Please provide unprocessed VOB sample and processed avi sample which shows this "blurriness".

[majinsnake]

That's not really helpful with a limit of 2 mb to upload. Ok it won't even except it, says file limit is too large for 300k/b for that filetype which is a zip. I will have to do a screenshot of the unprocessed vob and processed vob.

[majinsnake]

http://www.geocities.com/majin_snake/unprocessed.zip

www.geocities.com/majin_snake/processed.zip

I figured i just do the samples and upload them to my page where i don't have to worry about that problem above. The vob and avi last about 2 1/2 seconds. Assuming that is enough for a sample.

Some reason now when i use autogk, i get this message while processing the vob. I never got this message last week and my settings have only been on KernelDeInt and Force Deinterlacing when detected as a hybrid. I tried uinstalling, rebooting and reinstalling.

[7/31/2005 3:53:59 PM] Duration was: 5 seconds
[7/31/2005 3:53:59 PM] Speed was: 12.66 fps.
[7/31/2005 3:53:59 PM] Expected quality of first pass size: 305.38
[7/31/2005 3:53:59 PM] Trying to adjust settings.
[7/31/2005 3:53:59 PM] No adjustment is possible
[7/31/2005 3:53:59 PM] Setting min quantizer to 1 to prevent undersize.
[7/31/2005 3:53:59 PM] It is recommended to use smaller size or larger resolution!
[7/31/2005 3:53:59 PM] Running second pass.
[7/31/2005 3:54:06 PM] Duration was: 6 seconds
[7/31/2005 3:54:06 PM] Speed was: 10.64 fps.
[7/31/2005 3:54:06 PM] Job finished. Total time: 21 seconds

[manono]

Hi-

I couldn't access the first one as it says, "The web site you are trying to access has exceeded its allocated data transfer." The second one looks like it was deinterlaced properly, and that IVTC couldn't be applied. Deinterlaced AVIs won't ever look all that good. Maybe it's just a low budget movie (or TV show) shot on video. If you're wondering why it's blurry, you have no further to look than the 288x224 resolution.

[majinsnake]

that's strange, i have no problem doing it. Maybe it was by the hour.
I thought a source could only be IVTC or interlaced and what not. As in 1 thing per source, depending on ntsc/pal. If it was interlaced, just De-interlace it, and you are fine.
I use chopperxp to split or cut out a part of the vob, and then encode that. Easy interface. You said "If you're wondering why it's blurry, you have no further to look than the 288x224 resolution.".

Do you mean my resolution has to be lower then that of 288 or no more then 288? That's really odd, because when i started using AutoGK, i at first used whatever resolution was the default. The view of the video was too small in windows media, so i raised it up from other video's i have to get an idea for resolution. It's odd that i am now getting this. This was actually from a dvd, not a movie. Wrestling clip.

[jggimi]

Well, I couldn't access the second file ("processed") for the same reason -- transfer limits exceeded -- but I could grab the 2mb VOB, and I took a look at it.

The source is 100% interlaced, but Top Field First, not Bottom Field First.

When I ran it through AviSynth with SeparateFields(), I saw the usual "frame shuffle" behavior, which straightened out when I used AssumeTFF() before separating fields.

[jggimi]

I went back and was able to obtain the "processed" avi. Manono's right, 224 is an odd height to choose -- at 240 or below (1/2 the 480), you don't need to use a deinterlacer at all, since all artifacts will be eliminated by resizing.

[majinsnake]

i thought 288 is the height, and 224 is the width. If you prefer a better resolution, not something too small. I guess i should ignore that AutoGK detects it as interlaced and encode it plain. Be good to go.

[manono]

at 240 or below (1/2 the 480), you don't need to use a deinterlacer at all, since all artifacts will be eliminated by resizing.

I actually had that written down, and then deleted it. Figured I didn't need to confuse things further. Plus, I don't know if len0x can drop the deinterlacer when the AVI height is half or less than the source height. That low of a resolution isn't used all that often around here. We pride ourselves on making quality backups. :)

288 is the Width, and 224 is the Height. I was saying that the reason it looks blurry is that the resolution is low. A higher resolution and file size should give you better results.

And if it's from a wrestling DVD, then it's shot on video (30fps interlaced) and probably hard as hell to compress.

[majinsnake]

oh ok i see your point. I didn't know that was actually considered low, like extremely low. Speaking of higher resolution, i did that 1 time, but the size of the video was a 100 mb for a minute length playback. =)

Bradley.

[jggimi]

..And if it's from a wrestling DVD, then it's shot on video (30fps interlaced) and probably hard as hell to compress.As I mentioned, the sample was 100% interlaced TFF.

One thing to mention -- Interlaced NTSC content such as this should never be Inverse Telecined (IVTCed). That process is used only for content that had been originally transfered to NTSC video from film (16mm or 35mm) rather than shot with a video camera. That film transfer to NTSC process is called Telecining.