vegas no longer sending timecode through 1394

DJPadre wrote on 7/12/2006, 6:58 AM
This is a wierd one..

ive never had issues with Vegas or through previewing out with firewire. Infact i rely on it to be able to view my timecodes to set multicam syncs with 2 and 3 cameras..

BUT today, i turn on teh cam, what have we here..

Nothing, Nada Zilch...
The video plays back, but any clip information such as timecode is gone. All newly rendered clips SHOUD have a timecode and date of the day in which they were rendered, but Nup.. not that either..

anyone have any ideas??
Nothings been changed mind you.. on teh camera side of things and on the NLE.. nothings changed.. jsut today though its decided not to show me timecode.. :(

any help appreciated

Comments

DJPadre wrote on 7/12/2006, 7:46 AM
Ok well, i sorted out the problem, and i think i know why...

I had the Video scopes turned on in the program.. then when sending out to 1394, those live scopes (histrogram in this case) continued to tweak and adjsut while teh video played back on the camera..
turn off the scopes, and voila, my timecode is back...

I think this was done in teh assumption that those runnign an external monitor wouldnt need scopes, but i think maybe in V7, we could have the scopes running while we externally preview.. this way we will know TECHNICALLY what were doing as opposed to relying on an outside source for accuracy..
johnmeyer wrote on 7/12/2006, 7:47 AM
All newly rendered clips SHOUD have a timecode and date of the day in which they were rendered, but Nup.. not that either..

When you render anything in Vegas, say goodbye to everything in the original video file except the video and audio. Amazing, isn't it? I've been complaining for years, and have offered at least one solution (to specify a "master" track from which all timecode, cc, camera settings and other embedded DV information would be taken), but so far no interest (not even a little) from Madison. Too bad, because the way it works now, quite simply put, is wrong.

farss wrote on 7/12/2006, 7:53 AM
Running scopes with realtime update is a HUGE CPU guzzler.
I suspect that might have something to do with the problem although as John has said I didn't think it ever sent real TC out, period.

Bob.
DJPadre wrote on 7/12/2006, 7:38 PM
just checked it now..
heres the deal from what i can gather..

it sends time and date data back through firewire for cuts only work. If u run a filter or change anything, then that data is gone...
When u render out, it uses ur PCs time base as a "date and time" stamp, but alas, not actual timecode,

Funny though, as with teh DVX, when i use THAT to preview (not that i do, but i thought i had a camera issue) it shows up camera settings, such as Fstop, focus setting, gain, stabiliser, WB setting etc. so i can bust my shooters balls when they stuff up as i have the evidense there..

I cant get this info on the Z1...