Comments

BrianStanding wrote on 1/16/2004, 8:47 PM
John Meyer, you rock my world! The "audit" scripts are exactly what I've been pining for!

Thanks, tons!
MyST wrote on 1/17/2004, 6:30 AM
Where can I find info on how to install/use scripts?

M


Oops, never mind, I just woke up and opened the help file in Vegas. That'll teach me to post before having my morning coffee.
RexA wrote on 1/19/2004, 12:08 AM
John,

Here's another thank you for the excellent work on these scripts.

I just tried the gap audit and it found lots of little problems in a project, that I had missed. It took me a while to realize that what it had done was add markers at the problem points, but once I figured that out, it was incredibly useful in finding things I had missed and ensuring the problems were really solved.

One question on the event levels script... It tells me to check the track header levels. Perhaps I am dense. What do you mean by that?

Now, if you could just work out a script that could psych out that I have split out an event one frame off from where I really wanted the cut.
farss wrote on 1/19/2004, 12:12 AM
The track 'header' is the rectangle to the left of the track. I think what it's telling you is you've set the composite level (just labelled "Level")to something other than 100%
johnmeyer wrote on 1/19/2004, 12:20 AM
One question on the event levels script... It tells me to check the track header levels. Perhaps I am dense. What do you mean by that?

RexA,

farss is absolutely correct, as usual. The "track header" is that area to the left of where you place the events. The "track level" is that slider that sets the overall "Level" (for video) or "Vol" (for audio). The video should normally be set to 100% and the audio should normally be set to 0dB. However, if you use a lot of keyboard shortcuts you will find that Vegas constantly puts the focus on the track header, and when you press the arrow keys thinking that you are "scrubbing" across the track, you are instead changing these levels (Sony, can this be changed?).

Unfortunately, there is no way to check or set the track levels, either for audio or for video. Thus, all I could do was put a reminder at the end of the script. If any track level is set at other than 0dB (for audio) or 100% (for video), Vegas will force a re-render, thus needlessly losing time and quality.
RexA wrote on 1/19/2004, 12:49 AM
Thanks, John and Farss,

That is what I thought you were talking about. I don't think I have accidentally adjusted one of these levels yet, so that hadn't occurred to me. I can see how that would be easy to do, though, so I'll look for it.

On audio, I do frequently set these levels on different tracks to balance things out. That's why I was confused about the message. Accidental level adjustment wasn't in my experience. I guess if one is deliberately mixing there is always a render time incurred but that's just the nature of the game.
johnmeyer wrote on 1/19/2004, 7:52 AM
there is always a render time incurred but that's just the nature of the game.

But of course, render is not necessary if you don't change anything. The difference in time between needing to render and not rendering is huge. If most of your video (mesaured by running time) is cuts-only, it's a shame to waste time rendering for no reason.
DGrob wrote on 1/19/2004, 9:06 AM
Man, that gap audit is soooo good. DGrob