IVTC questions
-
- Joined: Mon Aug 05, 2002 2:07 pm
- Location: MA
- Contact:
IVTC questions
I've read Ermac's guide quite a few times, but there is one point that he doesn't seem to make clear that I'm having a logic block (like a....brain freeze) with in my head.
It's obvious that inverse telecining when exporting is a big deal in terms of saving space or what not, but Ermac points out that it's easier to edit in the format as well, probably as you don't have to deal with the extra fields. However...
How does one do that when going through AVISynth?
I'm not a huge programmer that has delved into the innards of the thing, but my understanding of it, and from what I've seen, it seems to be similar to VFAPI in that it's a frameserver, tell it what frame you want, and it'll dredge it up for you, although it's a bit more efficient and troublefree than VFAPI itself.
From the other posts I've seen on the forum about IVTC-ing, it seems that everyone has their own video source, but if all I've got is VOBs, and just want to run it through AVISynth without actually hard-encoding it, how would I go about that, or at least to the point where Premiere stops displaying those overlaid fields?
It's obvious that inverse telecining when exporting is a big deal in terms of saving space or what not, but Ermac points out that it's easier to edit in the format as well, probably as you don't have to deal with the extra fields. However...
How does one do that when going through AVISynth?
I'm not a huge programmer that has delved into the innards of the thing, but my understanding of it, and from what I've seen, it seems to be similar to VFAPI in that it's a frameserver, tell it what frame you want, and it'll dredge it up for you, although it's a bit more efficient and troublefree than VFAPI itself.
From the other posts I've seen on the forum about IVTC-ing, it seems that everyone has their own video source, but if all I've got is VOBs, and just want to run it through AVISynth without actually hard-encoding it, how would I go about that, or at least to the point where Premiere stops displaying those overlaid fields?
- jbone
- Joined: Sat Jan 12, 2002 4:45 am
- Status: Single. (Lllladies.)
- Location: DC, USA
- Contact:
Inverse Telecining is the process of restoring progressive 23.976fps source from interlaced 29.97fps source.
When you make your D2V project files, set DVD2AVI to "Force FILM" so that your source will be 23.976fps. This way, you can edit it at 23.976fps, and you can also create an end-product which is 23.976fps. Thus, you won't need to worry about inverse telecining, since your source will already be at FILM's framerate - most animation is produced at 23.976fps, so you won't have to worry about losing anything.
If you're using 23.976fps source footage and it's coming through with interlacing, then there source itself is interlaced and you'll have to either use an AVISynth plugin to remove the interlacing, or just deal with the interlacing through the editing stage and reduce it in post-processing with a similar plugin for VirtualDub.
When you make your D2V project files, set DVD2AVI to "Force FILM" so that your source will be 23.976fps. This way, you can edit it at 23.976fps, and you can also create an end-product which is 23.976fps. Thus, you won't need to worry about inverse telecining, since your source will already be at FILM's framerate - most animation is produced at 23.976fps, so you won't have to worry about losing anything.
If you're using 23.976fps source footage and it's coming through with interlacing, then there source itself is interlaced and you'll have to either use an AVISynth plugin to remove the interlacing, or just deal with the interlacing through the editing stage and reduce it in post-processing with a similar plugin for VirtualDub.
"If someone feels the need to 'express' himself or herself with a huge graphical 'singature' that has nothing to do with anything, that person should reevaluate his or her reasons for needing said form of expression, possibly with the help of a licensed mental health practitioner."
-
- Joined: Mon Aug 05, 2002 2:07 pm
- Location: MA
- Contact:
Well...
Well, that worked out well, but a sorta-related followup question about Premiere:
Now that the it's coming off the avs as 24 frames, I've realized that the DV editing that Premiere uses on default (well, it's the highlighted project format) doesn't support the 24fps (as Ermac pointed out). The preloaded project options in Premiere offer DV, Video for Windows and Quicktime as options.
The question is, is there any difference while in editing if I choose Video for Windows or Quicktime (unlikely) instead of DV? And will either of those support the 24fps of film?
Now that the it's coming off the avs as 24 frames, I've realized that the DV editing that Premiere uses on default (well, it's the highlighted project format) doesn't support the 24fps (as Ermac pointed out). The preloaded project options in Premiere offer DV, Video for Windows and Quicktime as options.
The question is, is there any difference while in editing if I choose Video for Windows or Quicktime (unlikely) instead of DV? And will either of those support the 24fps of film?
- klinky
- Joined: Mon Jul 23, 2001 12:23 am
- Location: Cookie College...
- Contact:
- jbone
- Joined: Sat Jan 12, 2002 4:45 am
- Status: Single. (Lllladies.)
- Location: DC, USA
- Contact:
I always use Video for Windows, and I often edit with a 24fps timefase.
I haven't played with DV, so I can't really talk about the pros and cons of using it (aside from the fact that it's not lossless, which is a con).
For exporting a master post-editing, you'd probably want to use Huffyuv over DV, anyway, unless you have hardware that does DV in realtime. Huffyuv is lossless, but DV is lossy (meaning you'll lose some visual data). DV isn't <I>nearly</I> as lossy as, say, MJPEG or MPEG, but if you re-encode DV enough times you will most definitely see degradation.
I haven't played with DV, so I can't really talk about the pros and cons of using it (aside from the fact that it's not lossless, which is a con).
For exporting a master post-editing, you'd probably want to use Huffyuv over DV, anyway, unless you have hardware that does DV in realtime. Huffyuv is lossless, but DV is lossy (meaning you'll lose some visual data). DV isn't <I>nearly</I> as lossy as, say, MJPEG or MPEG, but if you re-encode DV enough times you will most definitely see degradation.
"If someone feels the need to 'express' himself or herself with a huge graphical 'singature' that has nothing to do with anything, that person should reevaluate his or her reasons for needing said form of expression, possibly with the help of a licensed mental health practitioner."
-
- Joined: Mon Aug 05, 2002 2:07 pm
- Location: MA
- Contact:
Yet another...
I'm getting interlacing in Premiere, and it very well could be because of the original video source, but I just had to check everything out/make sure/bother you all again.
My d2v is Forced Film, and in most cases there isn't any interlacing, but I'll get back to that. Premiere still shows telecining, although DVD2AVI doesn't, when I do it frame by frame. What DVD2AVI DOES do is that there are some parts that are interlaced, or appear to be, yet, it's only for certain parts: i.e. If Ed were talking, his mouth would be interlaced, yet none of his body would. This might be correct for how interlacing works, and I'm not aware of it, but what's curious (and this might be where my knowledge is sorely lacking) is that in certain frames of movement, interlacing is visible (again, in parts), yet they aren't the 'intermediate' frames of telecining. By 'intermediate' I mean the frames, telecined, where the overlap occurs between frame one and frame two.
Does this mean that the source itself is interlaced?
My d2v is Forced Film, and in most cases there isn't any interlacing, but I'll get back to that. Premiere still shows telecining, although DVD2AVI doesn't, when I do it frame by frame. What DVD2AVI DOES do is that there are some parts that are interlaced, or appear to be, yet, it's only for certain parts: i.e. If Ed were talking, his mouth would be interlaced, yet none of his body would. This might be correct for how interlacing works, and I'm not aware of it, but what's curious (and this might be where my knowledge is sorely lacking) is that in certain frames of movement, interlacing is visible (again, in parts), yet they aren't the 'intermediate' frames of telecining. By 'intermediate' I mean the frames, telecined, where the overlap occurs between frame one and frame two.
Does this mean that the source itself is interlaced?
- klinky
- Joined: Mon Jul 23, 2001 12:23 am
- Location: Cookie College...
- Contact:
Well it's fairly confusing but...
Pretend TVs display 60 fields a second..
and you have 30frames per second video.
a field is half a frame, either the even or odd lines of the video.
so on a computer since it is progressive and CAN display 30fps, you can see the whole frame. But on a TV you would view it fields at a time.
okay well that's sorta confusing..
What telecining does is mesh, two frames together to make a whole new frame.
So take the even lines from frame A and take the odd lines from Frame B and put then together. If you view this on a computer, then it looks horrid, since you have two frames mangled together, on the TV however you don't notice it because it only displays the even lines.... then the odd lines. So you don't see the entire frame in one TV refresh as you would on the computer. Telecining does this in a certain pattern, and there is no set standard way of telecing video, so some people may mix and match differently, then others...
So DVD2AVI is forwarding at a frame at a time, but the frames have been merged.
As for your problem. If you try FORCE FILM in DVD2AVI and you load the file into Premiere or something else(also make sure your Premiere project is not setup for fields, check Keyframe & Rendering, make sure it's set to 'No Fields'), then your best bet is to just leave it at 29.97 and use a area-based de-interlacer, or you can leave it at 23.98 and do the same. Just it may not have ivtc'd it properly if you still notice lines and may result in jerkiness or something ... I don't know :p
I usually don't deal with ivtc since I've never gotten it to work properly.
~klinky
Pretend TVs display 60 fields a second..
and you have 30frames per second video.
a field is half a frame, either the even or odd lines of the video.
so on a computer since it is progressive and CAN display 30fps, you can see the whole frame. But on a TV you would view it fields at a time.
okay well that's sorta confusing..
What telecining does is mesh, two frames together to make a whole new frame.
So take the even lines from frame A and take the odd lines from Frame B and put then together. If you view this on a computer, then it looks horrid, since you have two frames mangled together, on the TV however you don't notice it because it only displays the even lines.... then the odd lines. So you don't see the entire frame in one TV refresh as you would on the computer. Telecining does this in a certain pattern, and there is no set standard way of telecing video, so some people may mix and match differently, then others...
So DVD2AVI is forwarding at a frame at a time, but the frames have been merged.
As for your problem. If you try FORCE FILM in DVD2AVI and you load the file into Premiere or something else(also make sure your Premiere project is not setup for fields, check Keyframe & Rendering, make sure it's set to 'No Fields'), then your best bet is to just leave it at 29.97 and use a area-based de-interlacer, or you can leave it at 23.98 and do the same. Just it may not have ivtc'd it properly if you still notice lines and may result in jerkiness or something ... I don't know :p
I usually don't deal with ivtc since I've never gotten it to work properly.
~klinky
- klinky
- Joined: Mon Jul 23, 2001 12:23 am
- Location: Cookie College...
- Contact: