Leading edge trim for certain types of events

Jack S wrote on 10/19/2024, 8:30 AM

@jetdv Edward, I wonder if you could help me with a problem.
One of the tools in my extension allows the length and/or leading edge trim to be adjusted for selected events.
During my extensive testing, I found that empty video, empty audio or adjustment events were causing Vegas to crash when the tool was applied. After many hours of debugging, I found that one line of code was causing the crash. This is the line:-

myEvent.ActiveTake.Offset = myEvent.ActiveTake.Offset + timecodeLeadingTrim;            //Trim the leading edge

The code works OK for any other type of event. It's just the three types I've mentioned that gives the problem. I've worked around it by enclosing the code in a try/catch block so I can display an appropriate message.
Is this line of code the correct way of trimming an event at the leading edge (it seems so, as any other event type is trimmed correctly)?
If it is, there's a problem which could affect anyone trying to apply a leading edge trim to one of these types.
That's the background. My question is, do you have a way to test an event to see if it's any of the three events mentioned? If, you do, I could test for these and take the appropriate action.
Many thanks for any help you can give me.

Comments

jetdv wrote on 10/19/2024, 9:08 AM

Yes, that is how you trim the "front" and then you have to shorten the length too. Take a look at myEvent.Takes.Count and if that is zero, there is nothing there to adjust and you can bypass it.

You might also look at the .AdjustStartLength to see if that causes an error. I have not tested to see if this works with empty/adjustment events. Here's an example of reducing the "head" space (OverDist is the time to cut off the front):

                double dStart = MyEvent.Start.ToMilliseconds();
                double dLength = MyEvent.Length.ToMilliseconds();

                dStart = dStart + OverDist.ToMilliseconds();
                dLength = dLength - OverDist.ToMilliseconds();
    
                MyEvent.AdjustStartLength(new Timecode(dStart), new Timecode(dLength), false);

Alternately, you could "split" the event at that point, delete the left part, and move the right part to the left.

Jack S wrote on 10/19/2024, 9:18 AM

I'll have a look at AdjustStartLength, see if it still throws an error. To be honest, I don't see anyone wanting to trim any of these event types, but I have to assume that it will happen sometime.
Thanks

Jack S wrote on 10/20/2024, 9:51 AM

I've used the myEvent.Takes.Count to test for any of the events that were causing the crash and that's solved the problem. If the count is zero, I bypass the trim code.
Thanks for your help with this. I appreciate it.