[Bouke Vahl]

Well, since the 5D files don’t have TC to start with, make sure the files have it before you render.
You can use QT change to add timecode. Then, also export the attributes.
Move the attributes files (*.att) to your renders, use QT change again with the option to use the attributes.
Select the add timecode function, and you’re done.

hth,

Bouke

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

[Bouke Vahl]

Mike,
QTchange can do this.
Load the clips (set your FPS first!), then save attributes.
Next to your clips a small file called ‘filename.att’ wil be saved.
Then place these att files next to your rendered files (the renders should have the same filename, or a longer filename, the beginning must match)
In QTchange, select the ‘use tc from attributs’, then load the renders.
Highlight ‘refresh timecode’, and press ‘do it’.

Should do the trick.
Get QTchange here: (there is a free demo)
https://www.videotoolshed.com/product/42/qtchange

hth,

Bouke

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

[Bouke Vahl]

If you’re expertise it IT,
then look into FFMBC / WriteAvidMXF (Ingex project on SourceForge)
That will create Avid MXF you can mediatool into your bins, and you can customize it to your liking.
No need to tie up an Avid, and get any el cheapo PC / Mac to work 24/7

Bouke

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

[Bouke Vahl]

Why on earth would one want to use PluralEyes when there is common timecode?

You can sync them in the bin without any effort.

Bouke

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

[Bouke Vahl]

John,
If you have added a TC track (note, it’s a QT track, not channel)
you can mute it.
Just open it in QT pro and go to properties.
Select the track (probably the lowes one), and select the ‘audio settings’ tab. Then mute it.

hth,

Bouke

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

[Bouke Vahl]

a quicktime TC track can have a different framerate as the video fps.
If you have FCP, you can use ‘modify timecode’ and refresh the TC track.
If not, you can use QTchange (the free demo will do just fine)
Make sure you set the FPS right before doing so, or you end up with the same problem!

Bouke

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

[Bouke Vahl]

Beside Andy’s options, there is also this if you insist on SMPTE tc
https://www.videotoolshed.com/product/44/ltcgenerator

However, since you don’t have tc breaks it is overkill imho.
(only reason would be if the transcriber insists on one large file)

I’ve got a few other options as well, but best is to first check with the transcriber on what he / she wants.

Bouke

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

[Bouke Vahl]

Well, if they ask for “quicktimes”, they aren’t very descriptive.
So there is no guarantee they have the Avid codecs, and chances are they start bitching about that…

So, get more detailled specs, or use a codec that everyone can read (Animation @ 75% is usally good)

Bouke

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

[Bouke Vahl]

Michael,

[Michael Phillips] “You can create interlace looking footage from your progressive footage by applying the motion effect at 100% with progressive as input and interlace as output.”

Eer, what would that do? (My avid is busy at the moment…)
The other way around is a quick and dirty de-interlace trick, but this ‘should’ do nothing…
Or am i missing something?

[Michael Phillips] “It would be great if Avid offered a option when rendering effects while in an interlace project to be frame based or field based. Right now, the project types defines that.”

And what would be the point of that? I can imagine an option where you can set the p or i per render, but overall, for broadcast / dvd / BluRay select I, for other stuff, use P if the footage is P.

For Marc,
If your input is XDcam, it’s long GOP MpegII.
Avid cannot export same as source, as that would mean I frames are lost (you did not cut on exact i frames…)
Quickest way is to export to XDcam. You end up with an MXF file that is good enough for rock ‘n roll (not uncompressed, but same codec, same as source isn’t uncompressed either.)
All half decent systems / software accept these MXF’s, and no worries about color space / gamma / levels yadda..

Bouke

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

[Bouke Vahl]

If the footage is shot 25p, your output will be 25p, even in an I project.
EXCEPT some effects! If an effect has motion (dve, wipe), those parts will be interlaced.

For broadcast, i normally edit P in an I project, as i like my (rolling) titles in i, while the director (never understood why) prefer P to shoot.
If the output is internet / big screen / computer monitor, it’s of course wise to stay P all the way, so you don’t have to deinterlace the final output.

hth,

Bouke

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