VirtualDub and AVISynth -- frame numbers

[phinsman]

Hello all...

Some background info: I do captures of football games weekly, edit out commercials, encode to MPEG2, and burn to DVD. I break the games up into 4 quarters and also do highlights for the game, usually around 10. Sometimes I even put select commercials on there...I'm a nostalgic guy, what can I say?

By the way...I don't do this to sell them. I'm just a big football fan and want to archive my games. If I had the use of this technology 20 years ago there's no telling how many games I would have. VHS tapes are too hard to keep.

I prefer using AVISynth for my clips because of the neatness of it. However, I use VirtualDub to get the frame numbers when editing out commercials, producing highlights, etc.

I did write a little C program that helps me. I just do all my commercial editing, then save settings from VirtualDub. The resulting .vcf file has all the frame information, although it saves it differently than used in AVISynth. My program parses the text file and produces another text file with a series of Trim(x,x) statements. Then I add my AVISynth statements and I'm good.

It works for this one big clip, but when I want to do highlights it's just easiest to manually type the frame numbers in.

I'm wondering if there's any tricks others would like to share about getting the frame numbers from VirtualDub.

Dale

[Tommyknocker]

Sounds like a great idea for a guide, especially if you are willing to share your program with the masses.

[Gees]

You might also want to look into the newly-created Programming Forum on this site to confer about your work. :c)

[Ejoc]

Parsing the vdr sounds like best/only way to extract frame #'s automaticlly from VirtualDub.

[phinsman]

Sounds like a great idea for a guide, especially if you are willing to share your program with the masses.

Yeah, I would be willing to do that. It's just a simple program, really, but it works for what it is. I'll clean up the code a little and post it. I made a modification recently which didn't work exactly right, so I'll have to fix that first.

Dale