Reinstalled everything and still get the error. No files are being created.

Hmm.. when you say no files are being created I think its safe to conclude that the DGInex is not running properly. And if no files are created by DGIndex then obviously VirtualDubMod cannot run as there is no script created. You can try the following
1)run the DGIndex just manually (not through Steve's exe) and see if it runs or not.
2) Look into the first post from Farnsworth in the other forum. And try running it manually (not using Steve's exe)
3) I hope you did install DGDecode.dll and mpasource.dll in avisynth plugin folder.
4) You would also need xvid/divx.
Xvid is available from http://www.koepi.org/xvid.shtml

Hope this helps.

Ajit B.

I do not know how to run DGIndex. I did try your script with Vegas and files were created but still get the VirturalDud Error (Script error: syntax error).

You can double click on DGIndex.exe to launch it.

I somehow think its due to absence of Xvid/divx. Do you have them installed?

You can double click on DGIndex.exe to launch it.

I somehow think its due to absence of Xvid/divx. Do you have them installed?

Installed Xvid and already had DivX installed. Tried to import the footage again using HDVSpilt, but still getting the error.

If you have no files being created, it sounds like DGIndex is failing long before you get to VirtualDub.

Can you try manually running through the DGIndex and see what error that application is raising to you? My app will get the process exit code from DGIndex and if it is non zero (error code), then it should not proceed to VirtualDub. So odds are it may always return zero on exit. Manually running through it should help identify the problem though.

--Steve

Opened a few clips with DGIndex. 1st gives error, File contains all nulls! 2nd, No video sequence header found! Got one to open and the aspect was wrong.

I cannot think of what else could be wrong! Did you try launching DGIndex manually?

I didnt get the HDVSplit issue! I thought you already captured your footage from the camcorder, right?

Anyway I am listing my setup below. Try finding anything that could be different than yours.

1) My Machine is Win XP sp2.
2) In C:\Program Files I made a directory called "HDV Utilities" in which I have HDVSplit.exe, DGIndex.exe, hv20pulldown.exe and template.avs
3) I also installed avisynth- which got installed in C:\Program Files\Avisynth
4) Copied the DGDecode.dll and mpasource.dll in C:\Avisynth\plugin also the TIVTC plugin.
5) Installed VirtualDubMod in C:\Program Files\VirtualDubMod.


And this is the way I run:

1) Capture m2t files first using HDVSplit to D:\video\capture
2) Launch hv20pulldown -- specify all the paths and working directory as
D:\video\pulldown
3) load the clips and run.

I hope this would be of help.

Ajit B.

Opened a few clips with DGIndex. 1st gives error, File contains all nulls! 2nd, No video sequence header found! Got one to open and the aspect was wrong.

Can you play your clips correctly with some other player ?

I cannot think of what else could be wrong! Did you try launching DGIndex manually?

I didnt get the HDVSplit issue! I thought you already captured your footage from the camcorder, right?

Anyway I am listing my setup below. Try finding anything that could be different than yours.

1) My Machine is Win XP sp2.
2) In C:\Program Files I made a directory called "HDV Utilities" in which I have HDVSplit.exe, DGIndex.exe, hv20pulldown.exe and template.avs
3) I also installed avisynth- which got installed in C:\Program Files\Avisynth
4) Copied the DGDecode.dll and mpasource.dll in C:\Avisynth\plugin also the TIVTC plugin.
5) Installed VirtualDubMod in C:\Program Files\VirtualDubMod.


And this is the way I run:

1) Capture m2t files first using HDVSplit to D:\video\capture
2) Launch hv20pulldown -- specify all the paths and working directory as
D:\video\pulldown
3) load the clips and run.

I hope this would be of help.

Ajit B.

Thank you for your help. Tried to duplicate what you did and still get the error.

Thank you for your help. Tried to duplicate what you did and still get the error.

I think there is something very trivial which is causing all the problems. If your clips open fine with other viewers/NLEs Than I would think it has to be DGIndex.

If the clips give some problem with other viewers/NLE's it has to be the capture process.

Hope you can fix it soon!
Good Luck!

It certainly sounds like there are some problems with the original clips themselves.

I did find a couple threads about some of your errors though, maybe one will help resolve the problem.

http://forum.doom9.org/showthread.php?t=113811

http://forum.videohelp.com/topic329046.html

http://www.videohelp.com/forum/archive/choppy-output-from-ffmpeg-t325577.html

--Steve

Steve, thanks for those links. Will read them over to see if anything can help. Tried to tape some more footage and it did not work either. I hope I can figure this out.

Duane, do any of your directories or filenames contain any spaces? Try it with a straight file with a short name.

hey everyone, how do.
i recently got an hv20 and have been lurking trying to absorb all the knowledge i could. today i chanced across a 1394 cable and finally got around to capturing some video. the capture process over hdvsplit couldn't have been smoother, i can watch the .m2t files via videolan/vlc just fine, and i can manually demux them with dgindex with no error. however, when i try to run a clip through hv20pulldown.exe, it crashes in-between dgindex and virtualdub, throwing this error:

"Avisynth Open Failure:
TFM: d2v file is not a d2v file or is of unsupported format!
(C:\HV20\work\test_.avs, line 4)"

now, when i run the m2t file through dgindex manually, the resultant video file is around 50 megabytes. when i attempt to use this app, the file comes out to 1k. the audio file is around 775kb each time. clearly something is affecting the way dgindex is handling my video. what gives, a/v jedis? anyone have any suggestions? is this what happens because when i manually try dgindex, i choose "save project and demux video" and pulldown.exe just saves the project? can i try and convince pulldown.exe to do so?

many thanks in advance.
(i would sign my name, but it's right over there...)

Did you copy the DGdecode.dll to avisynth plugin folder?
I think thats the problem.

thanks for the überfast reply! actually, i just did a little searching and it says tivtc (http://megui.org/auto/TIVTC-1.0.1.zip) must be v.1.0.1 and not v.1.0b4... silly me. crisis averted, but your assistance is much appreciated :)

Bitte! (It seems you speak German!)
Oh Ya! That version problem is there too!! Great that its working for you now!
Enjoy!

You can find the correct version of the TIVT plugin (TIVTCv101.zip) here: http://bengal.missouri.edu/~kes25c/old_stuff/

But I have a new problem. It says:
Avisynth open failure:
Script error: Invalid arguments to funtion "Delay Audio"
(E:\ViedeoPulldown\CFHDCap_.avs, line 7)

Has anybody any clue what that is and how to fix it?
Thanks,
Matthias

Make sure your using VirtualDubMod and not VirtualDub, though I don't think thats necessarily the problem. VDub regular errors out earlier than that on the stream items.

In your CFHDCap_.avs file, what is the line that contains DelayAudio? It should be a number..

Steve

finally found it. It says: "DelayAudio(0,003)"

Ok, that certainly doesn't seem right. I noticed you have a .de email, are you running German version of Windows? I'm thinking that the globalization features of .Net are causing the issue with the delay audio setting for you. The value should be in total milliseconds, so no ',' mark. Now, if you could find a german version of DGIndex... ; )

I updated my executable to force a specific globalization. I don't have a "language" machine here to validate on, but it should force it to use the English notation.

Try the updated exe at: http://www.szudzik.net/vegas/scripts/HV20Pulldown.exe

If that doesn't work, then I'll just brute force it for you. Let me know..

--Steve

Steve, downloaded the new .exe - and it works!!!!
While I'm German I don't use a German Windows version anymore, I bought my current XP here in NYC. But some of my language setting are for "Deutsch" like in Word. Maybe that was the problem? Who knows... Thank you so much, great work!

Glad that took care of it. I guess your my first "localized" customer! Who knew Windows would make it so easy ;)

Hello,

I was able to get 24P Pulldown to work fairly easily, but when I use Lagarith Lossless, the resulting file is distorted and the video is slow, almost choppy. The audio plays normal in the background, finishes, then the video is still playing. I tried opening the file in Vegas Movie Studio and rendering it as a WMV, which helped the slowness, but not the distortion. I am only using Movie Studio 4.0, and thinking maybe it's not recent enough to support my HD needs?

Does anyone have any suggestions? I've heard that using uncompressed AVI is generally fine as far as quality, but for right now, disk space is at a premium.

Rick, try reencoding in XViD HiDef profile with 4000K bit rate. This encodes a lossy method but lets you see motion. Check if you can still see the distortion. Can you describe it?

When you say reencode, do you mean taking the raw .m2t file and running it through 24p Pulldown again? I don't have an option there for XVid HiDef, do you know where I could find that? Is it a settings profile or a codec?

The distorition is like something was filmed in widescreen and now you're watching on 4:3 but the aspect ratio is messed up, and everything was squeezed in from the sides, resulting in an elongated picture.

Rick,
I think I know what you are talking about. I have also seen the same thing (video moving slow; audio finishes but video continues and the frames look 4:3 i.e. squashed) while using Lagarith Lossless codec.
What you could do is to read the avi file in NLE (say vegas), drop it in the timeline, right-click property and fix the pixel aspect ratio. I did that and the footage is fine.

When you say 'fix the aspect ratio', I only see a checkbox for 'maintain aspect ratio'. I tried on and off, neither made a difference. Does the fact that I am only using v.4.0 make a difference? I keep seeing people using 7.0 and wonder if my version is not quite ready for HD. If that's the case, would the $100 version of 7.0 suffice?

As an aside, I went ahead and grabbed the Huffy codec and the output is exactly the same.

Just try to do the following..
1) Open the output file in VirtualDub (it should also look squashed)
2) Right-click and change the aspect ratio from "free" to "16:9" and then play it.
3) If it now looks OK. That would mean you had the same problem as mine. And this is how I fixed it.


Well what I meant by fixing aspect ratio is that..when you code it using those codecs, somehow the resulting file does not have the information that its 16:9 and the pixel aspect ratio is 1.333
So what you have to do is to tell your NLE that your clip is 16:9 and the pixel ratio is 1:333 instead of 1.0 or 0.912. And the way I do it is to right click on the clip, go to properties, it would tell what kind of clip it is (1440x1080, frame rate : 23.976, progressive, pixel aspect ratio..etc. etc.) there you change the pixel aspect ratio to 1,333 to fix the problem.


I am afraid I dont have any experience with Vegas 4.0 or the cheapest Vegas 7. Hopefully someone can help you with that! Sorry!

There could be a setting that I can provide to the VDub script file to force those settings. I'll check on that later tonight when I get home and see if that will help fix this..

--Steve

There could be a setting that I can provide to the VDub script file to force those settings. I'll check on that later tonight when I get home and see if that will help fix this..

--Steve

Oh that would be great Steve!

Just want to say thanks to Steve Szudzik, Farnsworth & Mike Dulay for the time and effort put into these scripts and workflows.

Rastus

Ajit,

We're getting closer. I'm even further intimidated by the wealth of options this program provides, but changing to 16:9 does fix the aspect ratio......except when I play either the file itself or preview the output, it's choppy. This goes for Media Player as well. This is regardless of whether I use Lagarith or Huffy, running HV20 Pulldown on a raw .m2t file. I went ahead and fixed the aspect ratio, then did a SAVE AS and renamed the file, and viewing that in Media Player is choppy. Am I missing a step?

And I appreciate all the info, very useful. I'm learning a lot. :)

Ajit,

We're getting closer. I'm even further intimidated by the wealth of options this program provides, but changing to 16:9 does fix the aspect ratio......except when I play either the file itself or preview the output, it's choppy. This goes for Media Player as well. This is regardless of whether I use Lagarith or Huffy, running HV20 Pulldown on a raw .m2t file. I went ahead and fixed the aspect ratio, then did a SAVE AS and renamed the file, and viewing that in Media Player is choppy. Am I missing a step?

And I appreciate all the info, very useful. I'm learning a lot. :)

Rick,
I would suspect that this choppiness that you are seeing in your video is merely due to its size! If you are making it of correct size using VirtualDub. Try resizing it at a small size (say 640x360) and save it with Xvid compression. Try playing the resultant file and it should not look choppy.
If the above mentioned thing is true for your video. Then dont worry about the choppiness. Go ahead with the original size files, edit and then go for making your final product.
As in my case its going to be a normal DVD (with the HD files saved for later when HD-DVD writer/players are a bit cheaper).
But in case your resized video also does not play smoothly than I would guess that problem is somewhere else. (excessive motion in video, shutter speed etc. etc.)
Hope this would help you.

Rick,

I have seen some choppiness viewing the output files through WMP as well, but when I put them onto a proper 24p timeline in vegas and play them, they play very smoothly. After re-rendering them back out of Vegas, in my normal output format, the previous stuttering they showed is gone.

As for the pixel size (forcing the squished aspect ratio), I didn't see anything specifically related to that that I can control from VDub. The closest I could find would be do force a resizing. I've grabbed a few samples for that and am playing with it right now. I've been trying to put together my kids little league DVD this weekend, so haven't had as much time to investigate this issue yet. On another forum regarding this issue, one person said that they were able to work around it by installing XVid. I cannot account whether that really resolved it one way or the other. I have that installed myself and at least all of my Lagarith compressed files show the proper apect ratio. It could be that, but I certainly cannot confirm that it really is the case or not...

--Steve

My movie files don't get choppy until I run them through HV20 Pulldown to remove the Pulldown.....what exact kind of difference am I supposed to be seeing after I do this? The only thing I see in my 24P videos that I don't really like is the blurring when I move the camera, is this supposed to take care of it? I want to do the right thing and make the videos as good as possible, but is the difference even noticeable?

Resizing doesn't help....once I put it through HV20 Pulldown, it seems the choppiness is here to stay. Steve, I have Vegas 4.0, and keep hearing about this 24p timeline, but can't find it. Do I need to upgrade?

Also, what is xVid? Do you have a download link? Where is it used?

XVid is yet another codec and can be found here: http://www.xvid.org/.
Since the Lagarith codec has nothing to do with the XVid codec, I don't see that having it would have any impact personally, but somebody on another board mentioned that after installing it, it had helped them. Shouldn't hurt to try.

Vegas 4.0 might not have the 24p timeline. Does Vegas 4.0 even do HDV? My first version of Vegas was 7.0, so I don't have any experience with the older ones, except for what I've read & heard in the boards.

Steve,
I do have Xvid installed my computer and my clips behave exactly the way you mentioned. The choppiness is not there when taken to vegas etc. and also in the the final output. But the avi file does judder a bit when viewed directly with vlc, wmp or virtualdub. But when re-encoded to a smaller size resultant clip does not judder.

@Rick, in case your still have choppiness in your video after installing xvid and resizing please try to check your shutter speed. I was wondering if you could upload a small sample clip for us to see.

Hmm....I think I need to re-summarize what I'm experiencing. I may have confused the issue.

Any video taken directly from the camera, is fine, even when I rename it to .wmv. It looks great to my untrained eye. If I want to do a little editing in Vegas 4.0, I can work with the .m2t file, then generate a WMV from that. I do notice a tiny loss of detail doing that. But the result is fine.

If I take an .m2t file and run it through HV20Pulldown, I get this:

<A HREF="http://www.barr26.com/personal/movies/cosmote after 24p pulldown - lagarith.wmv">After 24p Pulldown using Lagarith</A>

You can see that the video is not choppy, but the perspective is lost, it's no longer 16:9. It's when I open the above file in VirtualDub that it gets choppy. Simply opening the file and trying to play it is bad. I went ahead and changed the perspective to 16:9, then did a SAVE AS and chose a different file name, no other options. The resulting file was too large to put up here, but it was basically very choppy AND had lost the perspective fix I had put on it. I opened that in Vegas, rendered as a .wmv, and it wasn't choppy anymore, but was also not 16:9.

I think I could do away with VirtualDub if I could just get HV20Pulldown to not mess with the perspective of my files. As for xvid, I installed the program, but was there a simple codec that comes with it that I can install and use with HV20Pulldown?

And it sounds like I may have to bite the bullet and upgrade my Vegas. :)

Rick, I know what you mean in regards to being choppy. I think it's probably a combination of the file being so large (once rendered through pulldown.exe)and the computer processor you are using. I have a core duo 2.4 with 2 gigs ram and mine also plays back choppy when rendered out to a huge AVI file. Once you go back into the Vegas timeline and render out a smaller (more manageable) file then it plays smooth. V-Dub also screws with the aspect ratio. I just fix it when rerendering in Vegas.

Hmm....I think I need to re-summarize what I'm experiencing. I may have confused the issue.

Any video taken directly from the camera, is fine, even when I rename it to .wmv. It looks great to my untrained eye. If I want to do a little editing in Vegas 4.0, I can work with the .m2t file, then generate a WMV from that. I do notice a tiny loss of detail doing that. But the result is fine.

If I take an .m2t file and run it through HV20Pulldown, I get this:

<A HREF="http://www.barr26.com/personal/movies/cosmote after 24p pulldown - lagarith.wmv">After 24p Pulldown using Lagarith</A>

You can see that the video is not choppy, but the perspective is lost, it's no longer 16:9. It's when I open the above file in VirtualDub that it gets choppy. Simply opening the file and trying to play it is bad. I went ahead and changed the perspective to 16:9, then did a SAVE AS and chose a different file name, no other options. The resulting file was too large to put up here, but it was basically very choppy AND had lost the perspective fix I had put on it. I opened that in Vegas, rendered as a .wmv, and it wasn't choppy anymore, but was also not 16:9.

I think I could do away with VirtualDub if I could just get HV20Pulldown to not mess with the perspective of my files. As for xvid, I installed the program, but was there a simple codec that comes with it that I can install and use with HV20Pulldown?

And it sounds like I may have to bite the bullet and upgrade my Vegas. :)


Rick,
I think I understood what you are saying. Its just a small issue which you can fix without upgrading.
The information that is lost while doing hv20pulldown removal is that the pixel ratio is 1.333 and nothing else. So do the following...

1) take a clip (*.m2t) and run it through hv20pulldown.
2) Open the resultant .avi file in virtualDub.
3) right click and tell the aspect ratio to be 16:9 (not required)
4) Go to video -> filters ; choose resize and give this 640x360 size (output)
5) again in video go and choose some compression you like (I selected xvid)
6) Save as avi. (new file name)
7) Play the resultant file.
8) It should have correct aspect ratio and no choppiness.


Let us know.


Edit: I think Ian is correct. Thats why this resizing is going to reduce the load on your computer and should play smooth.

One other option is that when you bring the AVI back into Vegas, make sure you have the pixel aspect ratio set to 1.333 before you re-render out to your smaller file. My guess is that VDub winds up setting it to 1.0 for square pixels. I'm still trying to find a way so that it will not do that.

As far as HV20Pulldown.exe messing with the aspect ratio, it itself doesn't have anything to do with that. The automation exe only automates the process of ushering your clip through DGIndex & VirtualDub. It by itself doesn't touch the video files in any way at all. The closest that it does to that is by selecting one of the compressor scripts (which just came out of VDub) or by altering the DelayAudio setting in the .avs template produced by DGIndex. It absolutely will not do anything other than that.

For the re-sizing, you can have the exe automatically do that as well. Just add the resize VDub call in the compressor script that you are sending into VDub. WIth the last update of the exe, the templates are stored in a .XML file that you can update as you see fit.

-Steve

Ajit, that worked great, thank you! The resulting AVI file has decent filesize and looks terrific. The only problem now is that when I try to open it in Vegas for editing, only the sound portion is available, the video never shows up. What's going on there?

Steve, I like the idea of being able to fix this in the script itself so I don't have to go back into VirtualDub and wait a second time for rendering. I'm just not sure which parts of it to edit. Here is my default script for Lagarith:

<Name>Lagarith Lossless</Name>
<Script>VirtualDub.RemoveInputStreams();
VirtualDub.stream[0].SetSource(0x73647561,0);
VirtualDub.stream[0].DeleteComments(1);
VirtualDub.stream[0].AdjustChapters(1);
VirtualDub.stream[0].SetMode(0);
VirtualDub.stream[0].SetInterleave(1,500,1,0,0);
VirtualDub.stream[0].SetClipMode(1,1);
VirtualDub.stream[0].SetConversion(0,0,0,0,0);
VirtualDub.stream[0].SetVolume();
VirtualDub.stream[0].SetCompression();
VirtualDub.stream[0].EnableFilterGraph(0);
VirtualDub.stream[0].filters.Clear();
VirtualDub.video.DeleteComments(1);
VirtualDub.video.AdjustChapters(1);
VirtualDub.video.SetDepth(24,24);
VirtualDub.video.SetMode(3);
VirtualDub.video.SetFrameRate(0,1);
VirtualDub.video.SetIVTC(0,0,-1,0);
VirtualDub.video.SetCompression(0x7367616c,0,10000,0);
VirtualDub.video.filters.Clear();</Script>

What would I need to do to set the resolution to 640x360 and using xVid, or any other compression?

Ajit, that worked great, thank you! The resulting AVI file has decent filesize and looks terrific. The only problem now is that when I try to open it in Vegas for editing, only the sound portion is available, the video never shows up. What's going on there?



You are welcome Rick!
Well let me tell you that this resizing was just a test showing you that nothing went wrong with your footage or conversion. Its just that a little information missing from the big avi file (aspect ratio) that is creating all the problem.

And NO you don't have to create that particular size (640x360). That size was a very small one that still maintained the 16:9 ratio (so was very easy on your computer not choking it to show the choppy video).

now to edit in vegas, I would ask you to do the following steps--

1) Take the original avi file in vegas.
2) set the properties of the project (File->properties) to 1080HD-24p ( I dont remember the exact name; can tell you later when I get back home)
3) drop your avi files into the timeline
4) righ click over the clip on the timeline and get into properties
5) define pixel aspect ratio as 1.333 (HDV).
6) Output from vegas as you wish, and try to play that. (It would have correct aspect ratio but might be still choppy due to the file size).


On a general note, I would like to tell all these are problems of HD. the HDV format (*.m2t files) have the same bit rate as DV and thus can be edited (and played) without problem.
But as soon as you convert them to some other format (like avi) they become too big (thats what we need to do while removing pulldown) and handling them smoothly needs a hell lot of computer power.


@Steve, Sorry for my previous post which sounded as if your exe is messing up the aspect ratio. What I wanted to mean is that the hv20 pulldown process messed it up not your hv20pulldown.exe!!

Ajit,

I'm going to save this info, but I think I am going to need to upgrade. I just don't have those exact options in Vegas 4.0 (this is seeming to be more of a problem as we go along). In my project properties, I have:

width
height
field order
pixel aspect ratio
frame rate

There are a bunch of templates available, but none for HDV. Should I just set my height and width to widescreen equivalents until I can figure out how to upgrade?

Ajit,

I'm going to save this info, but I think I am going to need to upgrade. I just don't have those exact options in Vegas 4.0 (this is seeming to be more of a problem as we go along). In my project properties, I have:

width
height
field order
pixel aspect ratio
frame rate

There are a bunch of templates available, but none for HDV. Should I just set my height and width to widescreen equivalents until I can figure out how to upgrade?

Rick, I see if you dont have any HD or HDV templates probably you would need an upgrade.
Anyway in the "project properties" (File -> Project properties) you can set
width -- 1440
height -- 1080
field order -- none (progressive)
pixel aspect ratio - 1.333
frame rate - 23.976


Edit:- The above setup would be the template HDV 24P; and in case you set width 1920 and pixel aspect ratio 1.0 it would be HD 1080 24P

and if you go to clip properties (by right-clicking on any 24p clip) and then the media tab (hope they are there)
you can set

All the above parameters exactly the same and hit "apply" to get perfect video!

If none of this options are there than you would need an upgrade soon!

good luck!

Ajit, that worked great, thank you! The resulting AVI file has decent filesize and looks terrific. The only problem now is that when I try to open it in Vegas for editing, only the sound portion is available, the video never shows up. What's going on there?


Vegas does not like the XVID fourcc and is misdetecting which codec to use. You can fix that by changing the fourcc to DIVX when you encode. Go to Virtual Dub -> Video -> Compression -> Options -> Advanced options. You should find an option fourcc (4cc). If you've already encoded, you can change it with the Nic's fourcc changer which should have come with your XviD install. Xvid is still doing the encoding not Divx, it's just masquarading itself.

Steve:

I'm using your HV20Pulldown.exe program.

Looking at the Script Editor it appears that the line:
VirtualDub.video.SetCompression(0x75796668,0,10000,0);
is the one responsible for the codec that's used for compression.

How do you figure out the codec information that's in the parentheses?
i.e. Lagarith (0x7367616c,0,10000,0) Huffyuv (0x75796668,0,10000,0)

Does VirtualDub have the ability to render out files based on quicktime codecs? Specifically the Avid DNxHD codec http://www.avid.com/dnxhd/index.asp.

Thanks,
Rastus

Rastus,
Capture the avs/d2v/mpa files generated by the exe and then feed the AVS directly to Virtualdubmod. Set the compression to the QT codec with all the settings you want. Then go to File -> Save processing profile. This generates a VCF file. Open it up. You can copy and paste this to a custom profile in HV20Pulldown.exe so you can use whatever codec you want.

Mike:

Thanks for your reply.

The Avid DNxHD codec does not show up in the VirtualDub compression dialog box.

Does VirtualDub does have the ability to render out files based on quicktime codecs? I'm not sure it does, but I have little to no experience w/ VirtualDub.

You wrote, "Set the compression to the QT codec with all the settings you want." I assume you mean VirtualDub -> Video -> Compression as you mentioned in post #25? Is that correct or is their another place to do this?

Thanks,
Rastus

Rick, I see if you dont have any HD or HDV templates probably you would need an upgrade.
Anyway in the "project properties" (File -> Project properties) you can set
width -- 1440
height -- 1080
field order -- none (progressive)
pixel aspect ratio - 1.333
frame rate - 23.976


Edit:- The above setup would be the template HDV 24P; and in case you set width 1920 and pixel aspect ratio 1.0 it would be HD 1080 24P

and if you go to clip properties (by right-clicking on any 24p clip) and then the media tab (hope they are there)
you can set

All the above parameters exactly the same and hit "apply" to get perfect video!

If none of this options are there than you would need an upgrade soon!

good luck!

Thanks Ajit, and Mike. I don't have those options. Sadly, I think my version of Vegas is simply too old, and in light of that, I am going to lay off a bit on trying to perfect my process (I'm keeping this thread handy, however, you have provided a ton of valuable information). Frankly, the video that I am taking and editing looks great to me, with the exception of some slight detail loss after I render in Vegas.

What exactly does removing the 24P Pulldown do to videos?

Rick, the pulldown removal process basically strips the interlaced frames out of the 24p footage and leaves only the progressive frames behind. This gives you a pure progressive clip. You can leave the interlaced frames in there and do some blending etc, but often what you will see will be some "ghosting" in the final output file. Depending on the clips it may or may not be noticeable.

--Steve