Viewing timecode

[Mike Kujbida]

Either run the “Apply Timecode to all Media” script or apply the Timecode FX to your media while it’s in the media pool.
This way, original tape TC is applied to the clip.
If you applied the TC FX while the clip was on the timeline, it wouldn’t have any relation to actual tape TC.

[John Magee]

Mike,
I tried that. I assume you mean “Project Media” (Media Pool is old name?)
I have nothing on the timeline. I have focus on the Project Media tab. I run “add timecode” script. I drag clips to the timeline. Each clip starts at Zero.

[Mike Kujbida]

Sorry John. Yes, I meant Project Media.
I’ve been using Vegas since version 1.0 so old habits die hard 🙂

I just tried it again and it works for me.
The script is called “Add Timecode To All Media” and is one of the stock ones with Vegas Pro 8.

Is this HDV, DV or analog footage?
Was the clock on your camcorder set?

[John Magee]

Mike,
Yeah, I was used to Media Pool too.
So you’re saying that after you run the script, then drag your clips to the timeline, you go from zero to whatever the total length of all the clips is? Rather than each clip starting at zero?

So, I checked the timecode on the tape, Mini DV standard def, playing back in the camera, and it’s continuous, with about 14 clips.
I am stumped. I’m running Pro 8b, I used the script, I also tried the “Show timecode on Thumbnails” in the Preferences/Video tab, but it does the same thing – each clip starts at Zero. Hmmm…

If I understand correctly, Vegas does not recognize any actual timecode from the DV data that comes out of the camera. It just adds timecode to a given clip or group of clips that sit in the Project media of a given project?
If so, it would seem to follow that if I want to have usable timecode for reference,ie, which approximates the “original” TC, I need to make sure all the clips from a given tape are in the pool (it’s easier to say) when I run the script. And that if I bring in other assets later, they will have to be content with starting at zero. Make sense?

[Mike Kujbida]

John, something strange is going on here and I’m not sure what it is.

I wonder if you’re confusing the time display window in Vegas with actual clip timecode.

Here’s an example of what I’m talking about.

Last week, I captured 6 tapes that were used in the production of a student music video. All times were shot on a JVC 550U that was externally timecode locked to a DVCAM deck that was used for music playback. This allows the students to reference the song’s timecode for editing purposes.
During capture (normal, not batch), each tape was given it’s own name (eg. studio-1, studio-2, chromakey-1, etc.) so that identifying individual clips in Vegas would be easier.
After capturing, all the footage was loaded into Vegas and, before putting anything on the timeline, I ran the “Add Timecode To All Media” script.
Now, whenever any clip is dropped on the timeline, the proper timecode shows up allowing for instant synchronization to the master song.
The song’s timecode starts at 00:01:00:02 (drop-frame TC) so I dropped it on the timeline so it starts at that point.
However, since I’m referencing burned-in TC, I could’ve started it anywhere as it’s the TC numbers I’m using, not the time display in Vegas.

Does this make any sense?

[John Magee]

Mike,
I think we are on the same page here.

Vegas has the timeline “clock” that you can dock, etc, that shows where on the the timeline you are. But I am talking about TC that identifies what frame of the captured 60 min DV tape one is looking at. That’s all I need. That TC should go from 00:00:00;00 to 00:59:58:17 or something like that. I should be able to move a clip with a TC of say 30 min to the beginning of the project and still have it labeled in that little “burn in” window as being at 00:30:00;00.

For some reason, when I apply the script to the clips in the pool, each clip, when added to the timeline, begins at 00:00:00;00.

So I just tried doing this: I opened a new project, went to “capture” window, selected a clip from there, viewed the properties and it showed timecode IN and timecode OUT, which cleared up for me that Vegas does know the actual timecodes. I selected two clips to be sent to the Project Media, I ran the script, moved the clips to the timeline, and the window-burn shows 00:00:00;00 instead of the 00:43:24;16 TC IN point.

I should be able to rule out the problem being in the camera since Vegas recognized the TC properly in the “properties” tab of the clip

Thanks

[Mike Kujbida]

I should be able to rule out the problem being in the camera since Vegas recognized the TC properly in the “properties” tab of the clip

Not necessarily. If the date/time function on the camcorder has NEVER been set OR the internal battery (about the size of a dime) is dead, Vegas will still report the timecode from the beginning of the tape and it will seem to be correct.
However, since the camcorder’s clock isn’t working, you’ll never see what you’re hoping to see because it never got recorded in the first place.

You didn’t say if you’ve ever set the date/time on your camcorder or how old it is.
If you have set the date/time, check it again just to confirm that it’s still working and then check the internal battery.
If you have no way of checking it, here’s a workaround.
Take a brand new tape (this is important as it can’t have any old video on it) and record 15 sec. of so of something.
Stop, rewind and play this clip but don’t stop playback until at least 5 sec. AFTER the clip ends. This is so the camcorder won’t pick up the existing timecode. Switch to record mode and run it for another 15 sec.
Now watch both clips in your camcorder.
If the clock has been set/internal battery is working, timecode should reset to 00:00:00:00 on the second clip.
You could also capture these two clips into Vegas and watch it while capturing. If the internal battery is working, you’ll see the “Current location” time reset to 00:00:00:00 when it gets to the second clip as it’s seeing new timecode.

[John Magee]

Mike –
I seem to have worked it out.
I did your Batt/clock test, everything looked good. I ran the script on the test clips and it worked. I grabbed some other clips from capture bins and it worked. I’m not sure what was going on, but OK for now.
Thanks for your time,

John

[Mike Kujbida]

I’m not sure what was going on, but OK for now.

John, that’s very strange behaviour.
I guess Vegas came down with one of those 48 hr. bugs 🙂
Glad to hear that everything is working for you now.

[John Magee]

Well, I messed with it some more and it’s still happening.

It worked OK with a fresh capture, straight from the capture window to project media.

Then I tried it again, with other, older clips I’d captured a few days ago, and the old start-at-zero was back again. (I checked their timecode properties to be sure)

I need further tests, but it seems as if it only works with brand new clips that have never before been added to a project.