How can I fix overexposed footage in Final Cut Pro? (codec issue)?

Hi there,


I shot a short film on an iPhone 16 Pro Max with Moment lenses in 4k, at 24fps and using Apple ProRes. But when I import the footage, it looks 'hot' or overexposed in the brighter areas, like on the wall behind his head and on the door in this screenshot. It's in all footage.



The original footage looks fine, (example still has ProRes on) just not when imported.



I imported using the 'Set based on first video clip properties' ...



And when I clicked 'use Custom settings to see what my default settings were, it showed this...



...which is what I shot on.


My footage and FCP are stored on a new 24TB RAID drive. My computer is an iMac 3 GHz 6-Core Intel Core i5, Sequoil 15.4.1 OS.


Does anyone know what I did wrong and how to fix this, please? I have the eye and skills to edit, but sorely lacking on the technical side when confronted with a problem/troubleshooting like this.


Thanks so much.


Julian


[Re-Titled by Moderator]

iMac 27″, macOS 15.4

Posted on May 19, 2025 4:59 PM

Reply
Question marked as Top-ranking reply

Posted on May 20, 2025 9:09 AM

The Quicktime Player video details and visual appearance indicates it was shot using ProRes 422 HQ using the AppleLog profile. The NCLC tags are 9-2-9 (see attached table), which means Color Primaries: ITU-R BT.2020, transfer function undefined, and YCbCr Matrix: ITU-R BT.2020. That means it is wide gamut but not defined as HDR.


That is no different from shooting Sony S-Log3/S-gamut3.cine which is also wide gamut but not defined as HDR. That is generally what we want, since in-camera HDR (e.g, recording Rec.2020 HLG) ties our hands as colorists and reduces dynamic range releative to a log format.


Similar to Sony or Canon log material, the iPhone AppleLog material captures high dynamic range and is capable of being used in an HDR timeline, but it is not defined as in-camera HDR. Technically, we would describe the clip as wide-gamut, but not HDR-signalled.


Typically this material would be used in an SDR library and timeline if you didn't have an HDR monitor and did not intend on producing an HDR product.


You have already indicated it's in a Rec.709 SDR timeline. To verify that, select the project icon in the left sidebar, then inspect the project properties in the Project Inspector in the right sidebar. It should say Rec.709. If it does not, create a new Rec.709 project: File>New>Project, select "Custom Settings." Verify the color space is Rec.709, then add your Rec.2020 iPhone clip to that project.


Verify your library is SDR. Select the library in the left sidebar, and in the Library Inspector in the right sidebar, it should say "Standard Gamut SDR." If it does not, either create a new SDR library or click modify to change this library to SDR.


Verify that FCP has applied the standard AppleLog conversion LUT to the clip. Select the clip, then in the Inspector "Info" tab, ensure the "General" view at bottom is selected. Then inspect that Camera LUT is set to Apple Log.


Verify in FCP Settings>General>HDR that "Automatic Color Conform" is enabled. Likewise, with the clip selected, look in the Video Inspector and verify that Color Conform is enabled, and type = Automatic. This will avoid later problems if you inadvertently mix HDR and SDR material.


Select your clip in the timeline and see how it looks. If it has effects on it, turn those off in the Video Inspector.


Enable scopes via CMD+7, and in the upper-right View menu, select "Waveform" and "RGB Parade." This shows whether the primary colors are out of limits. You can also verify that by enabling FCP's built-in range check. In the upper-right of the Viewer, select View>Range Check>All. That will show a zebra pattern if either the luma or saturation is out of limits.


If either is out of limits, fix the underlying issue, or as a stopgap, you can apply the FCP built-in Broadcast Safe effect. Increase the slider if needed to eliminate the zebra pattern. At that point, both luma and saturation are within limits.


After doing the above, evaluate the image and tell us how it looks.




Similar questions

8 replies
Question marked as Top-ranking reply

May 20, 2025 9:09 AM in response to HindsightFilms

The Quicktime Player video details and visual appearance indicates it was shot using ProRes 422 HQ using the AppleLog profile. The NCLC tags are 9-2-9 (see attached table), which means Color Primaries: ITU-R BT.2020, transfer function undefined, and YCbCr Matrix: ITU-R BT.2020. That means it is wide gamut but not defined as HDR.


That is no different from shooting Sony S-Log3/S-gamut3.cine which is also wide gamut but not defined as HDR. That is generally what we want, since in-camera HDR (e.g, recording Rec.2020 HLG) ties our hands as colorists and reduces dynamic range releative to a log format.


Similar to Sony or Canon log material, the iPhone AppleLog material captures high dynamic range and is capable of being used in an HDR timeline, but it is not defined as in-camera HDR. Technically, we would describe the clip as wide-gamut, but not HDR-signalled.


Typically this material would be used in an SDR library and timeline if you didn't have an HDR monitor and did not intend on producing an HDR product.


You have already indicated it's in a Rec.709 SDR timeline. To verify that, select the project icon in the left sidebar, then inspect the project properties in the Project Inspector in the right sidebar. It should say Rec.709. If it does not, create a new Rec.709 project: File>New>Project, select "Custom Settings." Verify the color space is Rec.709, then add your Rec.2020 iPhone clip to that project.


Verify your library is SDR. Select the library in the left sidebar, and in the Library Inspector in the right sidebar, it should say "Standard Gamut SDR." If it does not, either create a new SDR library or click modify to change this library to SDR.


Verify that FCP has applied the standard AppleLog conversion LUT to the clip. Select the clip, then in the Inspector "Info" tab, ensure the "General" view at bottom is selected. Then inspect that Camera LUT is set to Apple Log.


Verify in FCP Settings>General>HDR that "Automatic Color Conform" is enabled. Likewise, with the clip selected, look in the Video Inspector and verify that Color Conform is enabled, and type = Automatic. This will avoid later problems if you inadvertently mix HDR and SDR material.


Select your clip in the timeline and see how it looks. If it has effects on it, turn those off in the Video Inspector.


Enable scopes via CMD+7, and in the upper-right View menu, select "Waveform" and "RGB Parade." This shows whether the primary colors are out of limits. You can also verify that by enabling FCP's built-in range check. In the upper-right of the Viewer, select View>Range Check>All. That will show a zebra pattern if either the luma or saturation is out of limits.


If either is out of limits, fix the underlying issue, or as a stopgap, you can apply the FCP built-in Broadcast Safe effect. Increase the slider if needed to eliminate the zebra pattern. At that point, both luma and saturation are within limits.


After doing the above, evaluate the image and tell us how it looks.




May 19, 2025 8:46 PM in response to HindsightFilms

Hi (bonjour),


Check the colour processing option for your library, it should be Wide Gamut HDR as you iPhone shot material is HDR. From FCP user manual:


« You can choose between two library color-processing options in Final Cut Pro:


•Standard: Sets the working color space to linear RGB with Rec. 709 color primaries, the space that previous versions of Final Cut Pro have used. Rec. 709 is the current standard for HDTV projects, including HD cable, Blu-ray discs, and most streaming video today.


•Wide Gamut HDR: Sets the working color space to linear RGB with Rec. 2020 color primaries, a color space with a wider range of colors than Rec. 709. Rec. 2020 is useful for 4K and 8K UHDTV and HDR projects. In a Wide Gamut HDR library, the built-in camera LUT settings preserve the full dynamic range of log source media when converting to the working space.


Note: To view the wider range of colors in Rec. 2020, it’s recommended that you use a wide-gamut HDR external monitor and video interface. See Play media on an external display. For tips on color correcting wide-gamut HDR projects with Mac displays, see Wide-gamut HDR tips. »


Michel

May 20, 2025 6:18 AM in response to Michel Boissonneault

We do not know if the iPhone material is HDR. The iPhone can shoot various formats. The OP said the original footage was ProRes, and it appears to be a log format, but that is different from in-camera HDR (which the iPhone can also do).


If it is ProRes using AppleLog, it should work OK in an SDR library and Rec.709 timeline, assuming FCP is properly configured. That is similar to any log format such as S-Log3. Using this material there are two options:


(1) Grade and output for SDR using Rec.709. The Rec.709 option simply requires the appropriate log-to-Rec.709 conversion LUT, which FCP often applies automatically.


(2) Grade and output for HDR, using the same log material since that has latent HDR ability (14-15 stops dynamic range, vs 6-7 stops for Rec.709). To produce an HDR product, the same log content can be put in a Wide Gamut HDR library and graded on a Rec.2020 HLG timeline, then exported using the FCP Rec.2020 HLG Dolby Vision 8.4 preset. Unlike Rec.2020 PQ, HLG material is backward-compatible with playback on SDR devices.


If the iPhone material is actually recorded in an HDR format such as HLG (ProRes, HEVC, etc), there are also SDR and HDR grading/export options. However this may be less desirable for editing since it "bakes in" a specific look, and you lose some of the original dynamic range (about 10-12 stops vs 14-15 stops from a log format). That method works well if it won't be graded very much and if the intent is mostly to upload or distribute it "as is." Grading/export options for Rec.2020 HLG material:


(1) Use an SDR library and Rec.709 timeline (for Rec.709 export). If properly configured, FCP automatically remaps the Rec.2020 HLG content to Rec.709. This would be used if the colorist did not have an HDR display, so they could not properly grade HLG material.


(2) Use a Wide Gamut HDR library and Rec.2020 HLG timeline (for HDR export that is also backward-compatible with playback on SDR devices). This preserves about 80% of the dynamic range available with log material, but is better than Rec.709. However, the Rec.2020 HLG material cannot really be graded properly without an HDR monitor.

May 19, 2025 6:46 PM in response to HindsightFilms

Play the original iPhone video in Quicktime Player, do CMD+I, then do a screencap of the "General" and "Video Details" sections and upload those here.


The attached example shows the attributes of an iPhone video I shot and imported to FCP. Yours need not have these exact settings, but these are the areas of interest.


In MacOS System Settings>Displays, what color profile or preset is selected for your monitor?


If you shot the iPhone video as ProRes and AppleLog, upon import, it should look OK. Your posted image looks like some kind of double conversion, such as another LUT or effect on top of the FCP automatic AppleLog LUT. For test purposes, temporarily do not use any third-party effects or color tools.


This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

How can I fix overexposed footage in Final Cut Pro? (codec issue)?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.