Pro Res 4444 24 – 25 problem

[Gary Adcock]

[Marcus Vasques Osorio] “Am in the middle of consulting on 3 drama series shot on ALEXA, all on the PRO RES 4444 direct to XsX. Anyway a small bug has appeared where the fps can change randomly from 24 – 25 fps “

It’s operator error.

The Project timebase is not set correctly.

The project settings will override the fps settings especially when you have the “Link Sensor to Frame Rate” setting chosen.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

https://blogs.creativecow.net/24640

[Marcus Vasques osorio]

no this is not the case as it happens randomly, i have also been there and checked the timebase of the project….

cheers

marcus

[Gary Adcock]

[Marcus Vasques Osorio] “no this is not the case as it happens randomly, i have also been there and checked the timebase of the project….”

Marcus,

It is an issue with the MENU > Project > timebase
This setting is different than the frame rates available to Menu > Recording > Monitor out- which can be set differently

OR

The Sensor is looking to lock to the External sync via the external link settings.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

https://blogs.creativecow.net/24640

[Neil Sadwelkar]

[Marcus Vasques Osorio] “unfortunately when I have tried to zero the timecode the clip becomes corrupt.”

If the clips are on a NTFS drive or a shared network mounted drive and you’re try changing TC with QtChange on a Mac, the clips can become corrupted. I think Bouke has mentioned it on his site. Or maybe he’s fixed it on a newer release.

———————————–
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India

[Neil Sadwelkar]

Ok I came across the same problem. On a shoot I got clips with mixed frame rates.
When I conformed the 24 clips to 25 in Cinema Tools the conform went fine but any TC change or TC rate change in FCP corrupts the clip. I\’ll sort this out at the edit anyway but…

So I\\\’ve advised the camera crew to set the \\\’Link sensor to REC OUT\\\’ to off. It was on.

———————————–
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India

[Gary Adcock]

[Neil Sadwelkar] “Ok I came across the same problem. On a shoot I got clips with mixed frame rates.”

Neil,
there is a known issue contact your local arri rep.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

https://blogs.creativecow.net/24640

[Bouke Vahl]

As the maker of QT change (and a few other apps that work with these files), i know for sure there is a problem.

My findings so far:

Alexa’s 444 files are flagged as ‘read only’.
You must change that in order to work on that. But even reading the TC track will result in a corrupt clip.

Making a copy of the clip does not help.

What DOES help is to make a copy using QT.
If you open a read only original in QT pro, and save it under another name, you end up with a file that works as it should.
(Mind you, this is NOT a render, just a ‘save as’)

And yes, ARRI is aware of the problem.

Now in the meantime, use any QT flatten tool to batch copy your files before feeding them to any other application.
(No idea what is around nowadays, i use my own tools)

I could build in a ‘flatten’ tool in QTchange if needed, no idea how badly a fix is needed. Just contact me direct if you have an urgent need for it.
(In that case i’ll take a box of beer out of your hands…)

Bouke

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