[Matt Carlson]

I am glad it worked. No beer is necessary :). I have stared down the barrel of an annoyingly repetitive editing task before and know what a relief it is to have a one button push answer.

[Matt Carlson]

Here is the next version. It will close gaps, delete markers, and hopefully delete all the right audio events.

7292_keeponlyframesatmarkerspluscleanup.cs.zip

I am not sure if you saw the last edit of my previous post about all of your markers being at intervals. There are always dozens of ways to skin a cat programming wise. As your need to automate tasks grows graduating from using scripts to using extension windows will save you a ton of time.

Send me an email at

blackstingproductions@gmail.com

if you need more revisions or want to discuss what you think you need from a script and what you actually need from a script.

[Matt Carlson]

Do you mean close the gaps between the events that remain?

Also you might as well throw it all at me…

Do you want the markers removed etc?
Are there audio any audio event considerations?

Your timeline looks like all your markers are at equal intervals. If you just want to grab every nth frame from an event and string them together the script can be simplified and markers could be taken out of the process completely.

[Matt Carlson]

No you did not screw it up I did. The new changed line somehow has an extra parenthesis.

It should read:

backhalf.Split(Timecode.FromFrames(FRAMELENGTHTORETAIN));

Note the one left parenthesis in front of FRAMELENGTHTORETAIN.

The line I gave you was:

backhalf.Split(Timecode.FromFrames((FRAMELENGTHTORETAIN));

which has two parentheses before FRAMELENGTHTORETAIN. I am not sure how that happened but that creates the odd number of parentheses that caused the error.

Here is the working script with the change (I should have just done this originally….)

7291_keeponlyframesatmarkers.cs.zip

[Matt Carlson]

I understand the problem. My methodology was off because splitting events is a tricky thing. In my test I had all of the markers over different events. I see from your timeline that the first split would invalidate the rest. It is an easy fix (although it makes the actual script far more clock cycle intensive.)

search for and find the line

backhalf.Length = Timecode.FromFrames(FRAMELENGTHTORETAIN);

change it to

backhalf.Split(Timecode.FromFrames((FRAMELENGTHTORETAIN));

Everything will then work as planned. Sorry for the mistake. I assumed incorrectly you were taking 1 frame from different events… not many frames from a single event.

[Matt Carlson]

Here you go. Tell me if there is something I missed and I will fix it.

7288_keeponlyframesatmarkers.cs.zip

[Matt Carlson]

This is possible with extension programming as I already have this working with my Black Tools extension. With each project you can set what new events will default to for Loop, Resample, and Maintain Aspect Ratio. It requires a bit of infrastructure, though. For the programming guns wishing to go down the road here is a little road map.

On project open catalog all events. (For extremely large projects this takes a few seconds more but it is not too bad.)
On event count change modify any event not found in the catalog and then add to the catalog.

In Black Tools you can even set the option to ignore Split Events (it works by checking to see if the new event added is in direct relation to its predecessor on the track.)

It would be nice if Sony would just include a default event state option.

[Matt Carlson]

Excellent news. I think Vegas 11 needs to find a home in the country somewhere to live out the rest of it’s life in peace far away from people.

[Matt Carlson]

I am using Vegas 12.

There is one more thing you can try. Turn GPU acceleration off. Vegas 11 was known for being extremely buggy in that area. If the preview window is pushed solely through the CPU it might not miss frames.

[Matt Carlson]

From my experience Twixtor does not work well if the Vegas project settings are greater than the frame rate of the event the plugin is on. It will create a bunch of clumped static frames at intervals. Because of this using Twixtor solely as a standard frame retiming plugin seems like a bad idea.

If you are dead set on Twixtor because you are not happy with any other frame generation plugin’s output the only solution I can think of is a ton of work. Set the project properties to 23.976 and size the event to the amount of frames it would be at 29.97. Set Twixtor to 80% and render the event as an image sequence and re-import at 29.97 after changing the project properties back to 29.97. Twixtor will not have any static frame clumps that way and the extra frames generated will be better than Vegas’ native resample. If you have a lot of 23.976 events then this is probably more work than you are willing to do.