I've done this dozens of times: tc burn-in effect on top video track. Video mixdown. Use mixdown for client viewing or audio reference.

Out of the blue, when I do the mixdown the display shows "N.A." instead of the code, even though the code displays correctly in the timeline. Have rebooted, tried changing project format, fresh tc burn-in effect.

It seems to work fine if I render the whole effect before doing the mixdown, but it's a huge timewaster.

Has anyone had this happen? Suggestions would be welcome. Thanks.

Are you sure the mixdown is on the same V-track number that the burnin effect is reading from?

Yes. If I render the effect it's correct. If I do a mixdown after the render it's correct: Master TC in this case.

I just experienced the same thing. Typically, if it's working during playback the video mixdown will render it, but in this case everything looks fine in realtime playback but the video mixdown doesn't render correctly until the generator effect is rendered. 

This must be a bug. For window burns, this effectively doubles your export time. 

-Robert

Vinnie on the Avid FB page said it was a logged fault, so I rolled back from 1018.12.3 to 2018.12.1, and it's working fine now.

It's really puzzling that something like this would get broken with an update.

Yes, it's puzzling - and stealing time from us....

.

experiencing similar problems with TC-burn-in effect, getting error messages when try to display TCs from Audio Track/ Aux TCs etc.

Can someone from Avid confirm that this is a bug. Can you please solve this? thank you!

Michael

I'm getting the same error. On 2019.12.5. But you don't see the problem until you've done a 35 minute render. Agggg.

I've just found out something. I got the same N.A. described above suddenly, but only with fresh mixdowns.

I have a few videomixdowns and burn-in works with some of them but doesn't with others.

I investigated further and found out it doesn't work with mixdowns with TC tracks (V1 TC1 in bin column "Tracks").

Does anyone know hot to mixdown without TC track?
I have 2 mixdowns with V1 track only.

I downgraded from 2019.12.0 to 2018.12.12 and it seems I made a "proper" mixdowns with 2019 version and "wrong" with 2018.12.

I've found I have had to render first for a while now.

Pat Horridge:

I've found I have had to render first for a while now.

You could try disabling the frame cache & video cache? We use the timecode generator as an 'auto-slate' &, on some versions of MC, the caches hold incorrect frames - disabling them is the workaround. (MCCET-2503 | MC Timecode effect render does not invalidate when parameter changes are made to the effect - fixed in 2018.12.2)