Need urgent help: conforming for DCP

23.98 and 23.976 are the exact same frame rates, just rounded differently.
So, you should mix in Pro Tools at 23.976 fps.

Thanks
But what is the work flow to get 24 fps and 25 fps pal?
I will edit and mix at 23.98 ( 23.976) then export QT 23.98

And drop it on fcpx time line 24 fps?
To get 24 fps movie?
Is it true?

If that how can I get the 25 fps pal?
Thanks again

The best way is to do it in Compressor. Choose your output format, and then in the Inspector, under the video tab, choose your frame rate (24). Then, in the General tab under Retiming, choose "So source frames play at 24 fps".

For 25 fps, repeat the exact same procedure, but choose 25 as the frame rate in the video tab.

Doing it in FCPX is sort of possible, but it will change the audio pitch so I wouldn't recommend it.

Hey the Geek in me really enjoyed this thread.
Rarely have done DCP and never a PAL video.
One question for clarification… Does pitch really change going from 24-25fps if preserve pitch is on? My experience and understanding is that the algorithm for pitch is independent and does a pretty decent job except in extreme misuse. At least in Logic Pro X, with high bit and sample rates, it does. Is the pitch not preserved when going from NTSC to PAL?
Appreciate any feedback
Happy Editing, Greg

For 23.976(23.98) to 24 conversion:
just copy paste everything into a 24 fps project.
Even if there wouldn't be a pitch correction you won't hear a 1000/1001 difference.

25/24 or vice versa: often enough people don't care.
Speed difference of 4%.
For film audio, video are different files anyway: so change audio sample rate.

VidGreg wrote: One question for clarification… Does pitch really change going from 24-25fps if preserve pitch is on?

When using the retiming functions in FCPX, the preserve pitch setting does in fact do a great job of doing just that. However, when conforming between frame rates that are close to each other (like 23.98, 24 and 25), FCPX does not really use retiming, it just plays back the video at a faster or slower rate which changes the pitch (like Cinema Tools did way back when). When conforming 24 fps to 25 fps, the speed is still given as 100 % in FCPX; the actual conform is only indicated in the video tab of the inspector. It's a bit tricky to explain, so if you really want to geek out, create a 30 second 24 fps clip with a 440 Hz tone for audio and then drop it into a 25 fps project. The pitch will rise noticeably, and the clip will be shorter. The retime tools will still show the speed as 100%, though.
I would say that this is not the most clear and intuitive solution that Apple could have chosen, there should at least be a way to preserve pitch when conforming in FCPX.

Andreas Kiel wrote: For 23.976(23.98) to 24 conversion:
just copy paste everything into a 24 fps project.
Even if there wouldn't be a pitch correction you won't hear a 1000/1001 difference.

25/24 or vice versa: often enough people don't care.
Speed difference of 4%.
For film audio, video are different files anyway: so change audio sample rate.

If just going 23.98 to 24, then maybe I would agree. However, the pitch difference is quite noticeable when going to 25 fps. The audience might not care, but I suspect the filmmakers would want the audio to sound as intended. So, if you are going with Compressor for one conversion, you might as well do it for both.

I'm not sure what you mean by different audio and video files for film. If you are implying that the rate conversion should be done separately for video and audio, that would be way trickier and more error prone than simply doing it once with a single file.

fb_527411383 wrote: I'm not sure what you mean by different audio and video files for film. If you are implying that the rate conversion should be done separately for video and audio, that would be way trickier and more error prone than simply doing it once with a single file.

For DCP you will deliver an image sequence (or JPEG 2000 file) and an audio file.
If you correct the audio running length with pitch correction it's easy with not a lot of error options