timecode FX bug in VV3

MGalway wrote on 1/22/2002, 6:37 PM

My first post to this forum...

I've been using VV3 for 2 days and spotted a pretty simple bug already. When you turn on the timecode video FX plug-in, it doesn't do what it's supposed to.

It's supposed to display the cursor's timecode position off the ruler - so the ruler start is all-important. A lot of video projects will start at hour 1, or 00:59:59:30 for example.

The video timecode FX plug-in prints the offset into your project from 00:00:00:00 - it ignores what your actual ruler start TC is. Totally useless unless your ruler start is, in fact, 00:00:00:00.

I spoke with their product support, and the workaround is (strangley enough) to make your ruler's start TC 00:00:00:00 and simply push everything to the right so that it starts around the hour 1 position like it's supposed to.

upside: it works
downside: you have an enormous hour-long gap.

Just thought you should know...

Comments

Chienworks wrote on 1/22/2002, 9:36 PM

Just out of curiosity, why would you start a project at hour 1? Why wouldn't
you start it at 0:00:00;00?

Cheesehole wrote on 1/23/2002, 7:06 AM

my guess is so you can have 30 seconds of lead-in time, but still have timecode that makes it easy to tell how far along the program is. otherwise, the actual program would start at 30 seconds, and you'd have to do the math every time you check the time-code. i'm thinking, of videos that would be used in a live production environment like a 30-min spot for a TV network.

or maybe there's some other reason.

kkolbo wrote on 1/24/2002, 1:26 PM

Mostly you are right. The one hour start became a standard so that time code would be valid before the start of the content. There is often a lot of stuff before the content, bars tones, slates.