Why does 720 24pn change to 720p60 inside FCP?

Overlook

Active member
I shot some clips at 720 24pn. I loaded them into FCP and in the FCP bin the properties are listed as 720 p60.

Why does FCP do this?
 
Overlook said:
I shot some clips at 720 24pn. I loaded them into FCP and in the FCP bin the properties are listed as 720 p60.

Why does FCP do this?


That's the compressor, not the frame rate.
 
Oh, so it is like the 720 p60 compressor is used for a variety of frame rates, all derived from p60 activity inside the camera?
 
If you create a 24p sequence, do your 24pN clips load onto it without needing to be rendered? If so all is well. And like mentioned, make sure you're not confusing compression/codec for frame rates. It can be easy to confuse because the DVCPro HD codec called DVCPro HD 720p60.

Ah by the way, be careful using P2 and FCP 5.0.4. I know many have managed to go unscathed with that combination, but Apple has an official white page stating that there is a P2 related bug in 5.0.4. You want to upgrade to the universal binary 5.1 and then update that to 5.1.2. You will however need to re-load P2 footage. Simply upgrading doesn't help you. Any footage loaded under 5.0.4 is tainted.

cheers.
 
The "Compressor" is the encoding engine used for that specific footage and can handle a variety of flavors.

The "Vid Rate" is the frame rate, and is different from the Compressor setting.

Varicam, can you post a link to that Apple white paper?
 
Can't find the same one I recall reading from a while back, but I believe it talks about it in the FCP 5.x white page document. Its that render issue or whatever it was (forget the exact issue now and never was one for me as I was on 5.1.1 when I first touched an HVX).

Late Breaking News About Final Cut Pro 5

cheers.
 
That claims the solved the P2 issues in 5.1.2, but they haven't...

I and many others still have import problems...
 
Yah and its why I feed everything we shoot on it to the AJ-1200. I don't trust the tapeless workflow at all. Only reason we use the HVX200 is because it looks fairly close (at least versus say using a Sony or Canon camera) to the Varicam, and there are just times where we need a small sized camera.

Hopefully Apple will resolve the issues soon. What would be great is if they'll read the native MXF so you don't have to create the redundant MOVs along the way. But guess we'll just have to wait and see what happens with the next update.

cheers.
 
Yah, riddle me this VaricamLife or BenB, 1st time cutting some HVX footage that the shooter has dumped to dvd (10 of'em)...I've got some clips that I'm checking in QuickTime that are obviously overcranked and slo-mo'd somehow. Thought get info in QT would tell me what framerate he shot it at. That 720p60 thing was confusing me too. Came here trying to figure out how to use 60p footage. QT is saying its' FPS is 23.98. Does the HVX allow slo-mo effects or settings while dumping footage? And thus I'm assuming I should just use the clips in a 24p timeline? Thought I was gonna have to use that VideoFramRate plugin from the Panny site. Thanx,
 
The HVX 200 is a variable frame rate camera. It can shoot from ah 12 fps to 60 fps (and can be 'hacked' to shoot less fps I believe). When you shoot one of the variable frame rate ones, any of them, it contains them in a 60 fps "shell" (adds duplicate frames). So with FCP, yes you need to use Panny's frame rate convertor tool (also on your FCP 5.1 discs). It will extract the duplicate frames for you and make it a 24fps file (which will then play back in either slow or fast motion depending on the frame rate). Good luck.

cheers.
 
Double check your Capture and Sequence settings. HD is 60, but if you shot 24PN, you have the options to capture 60 or 24.
 
Back
Top