KVCD: Interlaced or not?
Hi,
I've captured a movie via tv-capture card at 480x576 to an avi file. If I open the avi file as source in tmpg the source video type is set to interlaced. Because of the resolution both fields are captured and so interlaced is correct. If I wrap the avi file into an avs script containing a call to FieldDeinterlace right after the AVISource line, the output of the avs should be an deinterlaced movie, right? But why is the source video type set to interlaced after loading the avs into tmpg? Holger |
I'm not sure TMPGENC can detect automatically what is interlaced and what is not.
|
Re: interlaced or not
Quote:
Quote:
-kwag |
Re: interlaced or not
Quote:
Well on the one hand you can deinterlace if your Tv-source is good, like Tv-Commercials etc. But if you capture a blockbuster like from PRO7 (german tvStation) you often receive more grainy and unsharper captures. Compare, you will see! ;-) And than you can make this: In the deinterlacing process you will obtain quality loss, even by using a adaptive deinterlacer. Try to encode your Video using mpg2+interlaced @ 480x576 with no deinterlacing in the AVS Script and do your prediction. BUT caution if you determine your video size using Moviestacker! If you choose overscanning than at least use overlap-overscanning! By using resize-overscanning the orig interlaced Fieldorder will be destroyed cause of also vertical resizing afterwards and everything was for nothing ;-) |
Re: interlaced or not
Quote:
Can you verify this :?: Because to my understanding, the image will always be resized on the TV, to do the overscan blocks. So the image is always streched both horizontally and vertically. So if we encode with "Resize" or "Overlap", the final image is still going to be stretched horizontally AND vertically on the TV, no matter what, because it's an internal TV function. :?: :? -kwag |
Re: interlaced or not
Quote:
The basic (for example PAL) interlacing is build on 50 Lines at 50Hz which give you 25 FPS (pictures) PAL for example @ 704x576 and thats the point. In (full PAL) digitally captured pictures you got an interlaced image at 576 high if you scale down (not cropping) the size for the amount of 50 Lines proportionally to the space is trashed. (Its like dots per inch in Photoshop, .. I only use this comparison to explain ;-)) You can let out every 2nd line to obtain 288 px but also then its not interlaced anymore but also correct handled cause you did not "resize" to 288 but you let out every 2nd line and thats for example they way a direct capture at 352x288 works (PAL). If you capture at 768x576 and want to scale to for example 640x480 you HAVE to deinterlace before. What we want to receive is that the architecture of the 50 Lines at 576px of picture high will be untouched and we can if we only resize the widh to 480 .. so we get a Picture at 480x576 which is still interlaced and in this untouched state it appears more sharpen than an interlaced one. Ok by watching it on a PC you can see the comb effekt, but who cares, cause our intention is to make CDs watchable with a DVD Player ... and not CD with Dvix which will only be seen on a PC Screen. But you have to use for example asharp with caution! Cause asharp sharpens horizontally and vertically... and if you sharp an interlaced picture at is vertcal to much .. you can see flickering when watching on Tv! So it would be better to make a combination of asharp() and unfilter(only horizontally) .. this will give good results. The picture then will not be scaled in the DVD Player internal as we "digitally" think, no ... it will be converted using the d/a converters to give an analog signal to the Tv and the Tv scales the "analog" picture as a whole and thats the difference. So every Tv scales the picture more or less and thats why they use the "cache" which normaly takes about 10% at the borders of the screen .. calles overscanning ;-) So we put on the untouched (at the high *576*) stream a black layer at the borders .. and this we call overlapping. So with all this we get a correct interlaced 3/4 PAL 480x576 interlaced picture including correct set overscanning borders, ready to convert to mpeg2 which can handle interlaced frame architecture. Maybe someone sees now a misunderstanding, but I tried to explain this complex materie in my best english words ;-) |
Re: interlaced or not
Quote:
The reason why I deinterlace is, that I want to encode to mpeg-1. Read more then once that mpeg-1 is better on low bitrates which I must to use to fit 90-120 minutes to once 80min cdr. Holger |
Re: interlaced or not
Quote:
The CQ you reach is not only based upon the mpeg encoding method you choose. Also it depends upon the "real" movie information within the whole picture (fullscreen, widescreen, cinemascope) the more borders you have, .. the more you will receive a higher CQ. And ... it depends also upon what "happens" during the movie. Example: Matrix= ca. 120min / much dark scenes/ 80min-CDR used = ca. CQ 62 Message in a Bottle: = ca. 115 min / very much changes in light and dark = ca. CQ 46!! Both predictions came with the same MA Script used! Same conditions same mpeg etc ... |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.