time code bug in Pro 10.0c
 

For those of you who rely on being able to see time code on your clips, be advised that the most recent update changed this capability.
Instead of displaying true time code, it now resets to 00:00:00;00 at the start of every new clip.
It was reported on the Sony Vegas forum yesterday and has been confirmed by several users, myself included.
Sony has been made aware of this problem.

What a snafu! Has Sony's qa team become incompetent to roll something like the avc fix?

Consistent timecode performance is so basic to my multicamera and log-in-the-studio workflows, I guess I'll stay on 10b, since there are so many other methods and I rarely need Sony's AVCHD.

Gotta' be a stinker for those using TC and going out to PS3 / bluray though...

Seth, this isn't the first time Sony has messed up an update.
Remember all the issues with Pro 9 :(
I periodically do window dubs and being able to see source timecode is a "must have" requirement.

RAOFL!
O my, this is becoming quite embarrassing now.
Fast forward a few weeks.........
(inside a dark boardroom late one night, 4 hours after the release of 10d...)
"What do mean, you forgot the preview monitor ?????".
"You're fired"!!!!!

It gets worse.
The bug is in 10.0b too :(
10.0a seems to be OK.
I haven't confirmed it but other users have said that it does work on that release.

Well, yes, but, the 10b and 10c slipups seem worse, somehow. I used to be a Sony apologist. I do enough software work to know that it takes considerably more effort than most people think! But this strikes me as a substantial management problem. You gotta' have the people and you gotta' give them the time to do effective QA.

Thanks for that - I'd only done a few projects on 10b, all single cam, no window dubs needed. Guess I'll have to fall back to 10a when I need camera timecode - ugh.

Re: time code bug in Pro 10.0c
 

OK, I thought I was going crazy. I'd been so pleased when Sony Vegas 10.0a finally had support for AVCHD timecode. Usuially I don't need timecode as I can sync pretty quickly on the sound, however yesterday I did a shoot where the mic was off on camera 2 and I was counting on using timecode to sync.

I didn't realize there was this bug in 10c, and I've wasted most of a day trying to figure out what I'd done and why timecode was suddenly not working.

Thank goodness that I could search this forum and find out that the bug in 10c is a know issue.

Since this thread is old, any news on when this issue will be resolved or when 10d will be released?

What is the best way to go back to 10a?

Re: time code bug in Pro 10.0c
 

For anyone else who has this issue or may need to use source timecode:

I have not yet heard back from tech support, but I did find that I had the original installation file for 10.0a on my computer. I uninstalled 10.0c and reinstalled 10.0a.

The source timecode is now visible and works fine.

So this confirms that the bug is not in version 10.0A but is present in 10.0C.

I'm not sure what other issues or fixes I may be giving up by reverting to an earlier version, but for me timecode is probably more important than other stuff.

Hopefully (when it comes out) 10.0d will fix this issue without introducing additional new bugs.