[Bouke Vahl]

Perhaps i’m missing something, but:

Rendering a HD clip with HD burnt in TC makes no sense to me.
(the render has to be done in HD and that will be way slower compared to rendering in the output resolution.)

Since QT can hold TC, i would not even render the TC into the clip, but have the producers use a special player that shows the QT tc.
(QT player can do so, so can my logger application, and that one can load the next / previous clip with just one keystroke:

https://www.videotoolshed.com/product/24/rs422-file-logger

If i had to render stuff like this, i would use a PC with FFmpeg / Avisynth to do so. (Would be way faster than RT).
FFmpeg runs on Mac as well, but Avisynth will not..

A few other options:
Paste a pre-rendered TC file into a QT clip. (Needs some scripting)
Or, create a custom Subrip subtitle file containing TC (not per frame, per second will be enough.)
Using this file and VLC, you can burn in your TC (VLC will think it are subs…), or just let it be next to the file and VLC will display it on the fly.

Hmm. I’m making this up while i write, but this sounds actually good…
I’ll have a try making an app that generates the Subrip.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Why not simply switch the sequence settings and remove the scale effects?
(Or, remove them with an XML roundtrip)

Uprezzing your SD will suck big time compared to this…

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Get the actor in the studio and dub.
A decent actor can dub his own voice very accurate.
It will be way less work and you end up with way better results.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

[Shannon Bedford] “One query on this; When exporting the SD, the only xd-cam option is HD.”

No, SD/HD isn’t an option. Datarate is…
Never thought about it, but probably your sequence (or project) settings are set to HD.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

[John Ranta] “Bouke, you may yet have one or two things to learn, yourself…”

Oy…
Yes, you’re right, I’ve got lots of things to learn.
But i do exactly that, not by asking others to read the manuals for me.
(and yes, it takes time and effort, hoping that this is correct English.)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

If you want it easy, export to XD-cam.
No codec hassle, no gamma issues, fast import (native) on Avid,
very decent quality.
Export SD as SD, HD as HD, and let the Avid editor worry about up/down convert if needed.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Sorry, but you TEACH video production?

I would recommend you get some education first, to know the basics.
(and that includes a tech background and knowing how to read manuals, test and experiment before asking others.)

I’m out of this thread.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

check the specs for the playout system.

You can export from FCP to XDcam in MXF, using the (free) Sony XDcam transfer application.
This is in fact MpegII, but another style as you would put on a DVD.
(and way better looking)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Personally, i don’t like the black box, but the DH_subtitle plugin, as well as the Spherico subtitle plugin are able to do it.

To get the timing done, you could use my subtitle prep tool and export to XML (it can use both plugins mentioned, or render to PNG’s with a box behind them and export those (with timing) to FCP.
(demo is free from my site)

If it is just 2 minutes, this might be overkill and you could do it in FCP also, especially if you already have the text translated.

However, when you want to move parts of text from one title to another, a dedicated subtitle editor will be way faster.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

BWF does NOT have timecode.
It has a timeSTAMP, measured in samples.
Thus, TC 00:00:01:00 on a 48Khz file is notated as 48000
Now this means that depending on your software frame rate setup, the calculated timecode from the BWF timestamp is shown, and this will vary if you change settings.

So all programs that work with BWF MUST ask you for a desired setup before they can calculate the timecode!

Besides that, FCP needs a restart between toggeling the DF / NDF BWF import.
(that is a big gotcha..)

Have a look at the numbers and do some math, you probably will find out what went wrong where.

Bouke

https://www.videotoolshed.com/
smart tools for video pros