[Bouke Vahl]

I never seen 50 fps files, but Avid ‘seems’ to like the speed changes my QTchange application can make.
(Also handy to add TC before the import)

The tests were only done on 30 fps material to get it to import as 29.97, so no guarantees.

As it works on the original files, i would suggest you make a copy before toying.

Another option would be to do a QT export (while you’re at it, do it straight to DNxHD with correct settings, will save you some time.
I’ll bet if you set the export to 25, the QT export will just trash half the frames.

Personally i would use AE. AE can create interlaced material, so you have a WAY smoother image.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

Who cares about the 145?
Datarate is still very well managable, and the total amount of data aint that much…
(145 is less than uncompressed 8 bit SD…)

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

I don’t know the bug (but i run MC).

However, it sounds like you’re batch digging a sequence rather than soure clips. This is bad practice.
If you decompose first, you have way more control over what Avid is going to do.
(Select the clips you want to dig, then run the batch command..)

Not sure if that solves your issue, but it’s worth a try.

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

Pat,
Latest version can either strip off the TC, or replace it with a fresh new track.

The version number is at the bottom of the page, and is in the application and manual.
(The download DMG name is the same to keep links alive)

Do me a favour, contact me direct, i’ve go another matter to discuss.
Bouke at videotoolshed dot com.

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

Pat,

Oy, mea culpa…
But you are running an old version of QTchange then.
(i know there was a bug that sometimes a speed change occurered even when you did not ask for it.)

But that was a long time ago (well, in software timespace), the bug was worked out in 0.6, and it’s in 0.7 now.

I still have to figure it out what the speed change does in FCP.
(I know it works fine with Avid, but QT has both play duration and FPS, one would think both are locked, but no..)
So if somebody could eplain this a bit, that would be great.

Btw, latest version can take the time information from the .THM files.
(Even if you have converted them to Prores first, as long as the THM’s travels with the renders.

As for all my software, i update on regular basis, so it can never hurt to have a look every now and then to see if there is a newer version. (QTchange is now in 0.7)

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

Well, according to my math, you’re off 4%
That sounds like a 24 / 25 problem.
Using this logic, if seems you have shot at 25, drag that clip in a 24 timeline and there is a 1:1 frame relation, your material gets stretched by 25 / 24 * 220 seconds = 229 seconds.
There is your 9 seconds difference..

Does the video in your timeline line up with the external audio?
If so, it’s a really weird problem.

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

Depends on your hardware.
You need at least a CC capable monitor / TV.
Then you have to connect that trough some hardware that does not strip of the CC info.
If you use a FW deck to go from FCP to you monitor, and it does not work, make sure you set it to pass trough the info.
(set Blanking off, somewhere in the menu.)

hth,
Bouke

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

Before or after shooting?
If you still have to shoot, make sure the bg around the actor has as little color as possible. This way with an easy soft mask you can desaturate the rest.

Another option is to stack a lot of (chroma, whatever works) keys on the (matted) actor, and key on a desaturated copy of the same clip.
Keys don’t have to be very good, as you’re keying to itself.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

[Jenny Morgan] “s disk space thief”

Excuse me?
24 KB per piece.
That means that on a standard DVD you can put about 180000 of them.
Will set you back a hefty 50 cent plus 10 minutes of your time.
How much do you shoot that this gets an issue?

The file contains a thumbnail image, and a lot of information about your camera, yourself and the settings how you shot the image.
(Of course in some intsances you want to trash them, not to show your client that you did not use manual settings…)

They also contain the time the image is shot. For video, that can be important if you want to sync later on.
I would always keep them, and let them travel with any processing you do on the image. Disk space is irrelevant, as the files are miniscule compared to even Jpeg images.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s

[Bouke Vahl]

David,
Few points

1) you emphatise the least interesting parts of my post.
(thus proving that you indeed did not get my drift 🙂
2) Even if Shane and you are top posters, and have your face up there, that does not make you a VAR who will help you in case of mayhem
3) As for Shane, i like him and do not question his competence, but i also disagree with him very often. (And i mean VERY, VERY often).
Having said that, you’re not the only ones responding, and my remark should have been taken in a more broader view.
4)I totally do not feel like adding something to answer the original question, see point 1) for that.

Peace, (and out)

Bouke

https://www.videotoolshed.com/
smart tools for video pro’s