I have been rendering my files as avi in VV3 then using TMPGEnc to encode to mpeg1/2, they have some really good filters there.

<<I have been rendering my files as avi in VV3 then using TMPGEnc to encode to mpeg1/2, they have some really good filters there. >>

Where is this TMPGEnc available? Is it a stand-alone, or a plug-in?

Thanks,

Steve

You might try DVFilm Maker (www.dvfilm.com). It's a $100 stand-alone program that uses an intelligent deinterlacing algorithm and does a great job -- the only areas of the frame that are affected is where there is movement, so you don't lose resolution as with other deinterlacing methods.

I generally use it after all of my editing as it also does letterboxing and simulated film grain.

Go to:

http://www.tmpgenc.net/

and

http://www.pegasys-inc.com/e_main2.html

It is $48.

<<You might try DVFilm Maker (www.dvfilm.com). It's a $100 stand-alone program that uses an intelligent deinterlacing algorithm and does a great job -- the only areas of the frame that are affected is where there is movement, so you don't lose resolution as with other deinterlacing methods.

I generally use it after all of my editing as it also does letterboxing and simulated film grain. >>

Jonnymac,

I've seen that site before, and it intrigued me. Am I correct in understanding that you first complete your editing in VV3, output as an .AVI, and finally deinterlace in DVFilm Maker? Does this program permit conversion of the deinterlaced .AVI files as MPEG 1 / 2?
Also, can one deinterlace VV3-edited and rendered .AVI segments in DVFilm Maker, and use them again in VV3 as "pre-rendered" .AVI components to be assembled in the timeline? Or would I simply have to render a 2-hour production as an example, in its entirety as a huge .AVI file from VV3, (which would take hours) then open and deinterlace said massive file in DVFilm Maker, finally outputting (which would also take numerous hours) as a full-length MPEG 1 / 2?

Thanks,

Steve

PS - Thanks to all for the web URLs and deinterlacing info! I will look into each suggestion.

I've been using DVFilmMaker for about a month now after seeing it mentioned somewhere here. It only renders your AVI to another AVI. That AVI can be used in Vegas, BUT (and there's probably something I don't know here), when I try to Print to tape with the DVMaker AVI I get no sound). So I re-render it once more and that fixes it. (It does play sound from the timeline, but just not through firewire until re-rendered with the standard DV-NTSC template).

Anyways, I use it because it only de-interlaces when it sees a certain amount of motion. If you deinterlace from the timeline you lose a lot of resolution. DVFilm Maker processes it in such a way that you don't lose any resolution, but when there's motion you get that film-motion look. I've been very pleased with the results and regard it as the last step in my production, before creation of the MPEG2 files from the Vegas timeline. P.S, as we speak I'm encoding with it in the background.

<<I've been using DVFilmMaker for about a month now after seeing it mentioned somewhere here. It only renders your AVI to another AVI. That AVI can be used in Vegas, BUT (and there's probably something I don't know here), when I try to Print to tape with the DVMaker AVI I get no sound). So I re-render it once more and that fixes it. (It does play sound from the timeline, but just not through firewire until re-rendered with the standard DV-NTSC template).

Anyways, I use it because it only de-interlaces when it sees a certain amount of motion. If you deinterlace from the timeline you lose a lot of resolution. DVFilm Maker processes it in such a way that you don't lose any resolution, but when there's motion you get that film-motion look. I've been very pleased with the results and regard it as the last step in my production, before creation of the MPEG2 files from the Vegas timeline. P.S, as we speak I'm encoding with it in the background. >>

Paul,

I’m a tad unclear here please forgive me. I now understand that DVFilmMaker only renders .AVI to .AVI. As such, I would assume that you would choose to deinterlace your “raw” video footage FIRST, and then open and cut the “cleaned” footage in the VV3 trimmer – adding cut segments into the timeline. In this instance, it would seem to make sense to create duplicate files of the original footage, as to extract “video only” from the deinterlaced file for the timeline, and “audio only” from an unprocessed duplicate – thusly adding untouched audio to the timeline (assuming you were to actually use the original audio, i.e. a wedding video).
Perhaps I’ve misconstrued your response, but I’m lost as to why you would need to render a project twice (which, as we all know can be inordinately time consuming) to obtain an audio signal through the firewire, if you could instead simply create and extract separate audio/video files.
Additionally, I’m further unclear as to why you would deinterlace your video as a final measure, rather than “cleaning” it before editing in VV3. Is there an advantage to creating a complete project in VV3, rendering it as an .AVI and then deinterlacing?
Finally, how do your MPEG-1 files look after the deinterlacing process using the “Main Concept” compression included in VV3, as compared to interlaced MPEG-1 files rendered directly from VV3?

Thanks,

Steve

But my Virtualdub only renders 9995 frames and then stops.

DVFilmMaker makes clear that they want interlaced, not deinterlaced footage to work with. Interlaced contains all the original info. If you deinterlace in Vegas you're losing half the lines of info. DVFilmMaker looks at each frame and determines how much motion is in it, then averages the interlaced frame to give a deinterlaced look in that portion, but leaves the sections with little motion alone. At the end you have an interlaced render from DVFilmMaker that has processed scenes with lots of motion to "look" deinterlaced. Thus you should never at any stage deinterlace your footage with Vegas. And after DVFilmMaker leave it interlaced, because it now has the film look that DVFilmMaker has given it.

As to why I have to take the DVFilmMaker end product and render it again, I don't know. I'm trying to solve this right now. (By the way, again, when I render the DVFM end product I leave it interlaced). The only reason I render it again in Vegas is because it works. If I don't I don't get any sound through the firewire. If I do and use the new Vegas-rendered file, I do get sound through the firewire. Maybe it has something to do with the Quicktime codec that DVFilmMaker uses.

Your point on creating a separate audio file and then using that may work. I just took the audio file from the DVFilmMaker product and rerendered that as a wav, but that didn't work. Maybe if I render the original audio, before DVFM that might do it, so I'll try that.

As far as how do my mpeg files look, they look as good as the original footage, and I think much better after DVFilmMaker. I render the avis to mpeg2 and then create DVDs with them.

If anyone on the forum has DVFilmMaker and knows the answer to this audio problem I would love to hear it.

steve724:

I'm curious about the artifacts you are seeing on render. Vegas does a pretty fine job of deinterlacing interlaced sourced when rendering to progressive format, such as MPEG-1 or WMV. There are two methods to choose from (project properties, advanced). Make sure your source media properties have the source footage set to interlaced or it won't deinterlace it.

///d@

Dennis,

The most prevalent artifacting that I notice in VV3 rendered MPEG-1 files is horizontal "combing", also referred to as "mouse tooth." This artifacting is most discernable between straight cuts, and at points where axial movement occurs. I also notice in addition, that simple cross-fades look abysmal, and take on a black mesh-like appearance instead of the smooth dissolving effect between segments as visible in VV3 rendered MPEG-2 files.
As for .WMV files, the "combing" is not as great a concern as with the MPEG-1 files. I do find however, that .WMV renderings even at relatively high bitrates, e.g. 512 kbps (which, at this point seems to be the maximum rate most pc users I know of can use with Winplayer devoid of problems) appear somewhat pixilated, and lossy - not nearly as crisp as compared to an MPEG-2.
All of my raw footage is captured in VV3 via firewire, directly from a Sony PD-150 (shot in DV CAM). I have been using the standard DV template (program recommended) for my projects, and I use the Main Concept MPEG-1 template for rendering without any manual adjustments. I have not used the VV3 deinterlacing filter in this process as yet. In fact, I don’t recall seeing the option in the course of actions I’ve just described. These issues, (as they are critical to quality output) really should be more clearly defined and outlined in the program’s documentation.

Sorry, my english is not that good; What does it mean:

" Make sure your source media properties have the source footage set to interlaced "

Do you mean text?