I attempted your experiment on a 30 FPS project, 29.97 FPS clip, placing the cursor in the middle of the clip and then selecting Freeze Frame. What happened was that the clip was split and the frame was "trimmed out". The "trimmed out" frame could be recovered by simply extending the clip.
I tried the same experiment with 29.97 FPS project, 29.97 FPS clip, placed the cursor in the middle of the clip and then selected freeze frame. The clip was split and a freeze frame added between the clips. This was as expected. What was really interesting is that first split clip had the frame that was to be frozen trimmed out. I am not certain if this is normal behavior.
I am not running any keyboard enhancing software on this late 2016 MBP16. But since I am selecting freeze frame from either the menu or OPTION+F and not seeing any difference not sure keyboard would be an issue. Unless...........
Also, the only addons to FCPX application are: FujiFim LUTs, Leeming Pro LUTs, and Color Finale trial version that is past date. At one point this all worked normally. I have tried clips without the LUTS, but this does not change the behavior. I have yet to un-install Color Finale trial version to see if this resolves the issue.
It is baffling. Other than uninstalling the Color Finale trial I am not certain what to try next short of installing BigSur. But I am waiting for 11.1
As you predicted, MacOS 11.1 (Big Sur) did not resolve trimming of the last frame when selecting Add Freeze Frame. So this remains a mystery as to what is going on with my particular situation. I am beginning to wonder if this is camera dependent FujiFilm X-T3 issue.
Now this is what you call annoying! Sorry Don.
Though the idea about it being footage related got me thinking.
A. It's easy to test whether it's the Fuji footage by importing other footage not from that camera. Do you get normal freeze frame behaviour? If yes it's not FCP or your installation.
B. It might have something to do with how Fuji implements the Long GOP. I'm not a super tech expert but I know that compression can work in a way that the codec saves one full frame and then the next x number of frames it only writes down the changes to that frame. After the x long seq it starts again. Maybe with the Fuji codec a particular frame can't be calculated and therefor causes FCP behaviour. Maybe some more tech savvy folks can chip in here? So maybe try the following: place cursor anywhere in clip in the project you have the problem, then try freeze frame. If it doesn't work undo and move one frame forward and try again. Repeat until you may have one frame where it works. If that happens then the codec could be the problem. If it doesn't work after maybe 30 frames than we're back at square one
Regardless maybe the solution is that you have to transcode to Prores (Transcode optimise) for clips you need to have a freeze frame on.
Wish I know the answer..
Thank you for the suggestions. Here is what I have tried:
Different camera. Unfortunately, the only camera that I have that is 4K is the FujiFilm X-T3. I thought about using my iPhone 8. But that is a true 30 FPS camera--at least according to information panel on FCPX. If anyone can send me a true 30 FPS HEVC UHD Long GOP clip from a camera other than FujiFiim I will be happy to test out this theory.
I did your test of placing the cursor in the middle of a X-T3 UHD Long GOP clip to see what happens when I Add Freeze Frame. If if it trims out the frame, advance to the next frame and repeat. I did this for about 30 frames and all I got was the trimming behavior. As an alternative to this test is to try 30 FPS, UHD, HEVC, All I and see what happens.
I currently transcode (optimize) my HEVC clips upon importing into FCPX. This is where I am running into the issue with the trimming behavior. What I have not tried is transcoding to ProRes in Compressor, importing into FCPX, and then seeing what happens. Even if this works, transcoding in Compressor presents a different problem. It turns out that transcoding UHD HEVC Long GOP X-T3 files in Compressor results in shifting the histograms to the right. See the my topic--https://www.fcp.co/forum/14-compressor/33728-apple-compressor-does-not-properly-transcode-10-bit-420-files-from-a-fujifilm-x
I'll report on All I and a Compressor transcoded ProRes in a my next post.
Ok I suggest you import footage from your iPhone. It doesn't really matter what FPS it has. If that iPhone footage behaves normally for freeze frame in either 29.97 or 30, then the problem is the Fuji footage.
If the iPhone footage shows the same trimming instead of freeze frame behaviour in either project then there is something wrong with your FCP installation.
Maybe there is some metadata in the Fuji footage that gets copied to the Prores optimised version as well, that is causing the misbehaviour? But the above test will give the best indication to whether it is Fuji or your installation?
The plot thickens. I just downloaded a Fuji X-T3 clip which is HEVC UHD (3840x2160) 23.97 FPS (from DPReview side).
This clip shows normal freeze frame behaviour in a 23.97, 29.97 and 30 FPS project.
Can you upload a small Fuji X-T3 clip in your 29.97 format for me to test?
PS the behaviour you described earlier that if you add a freeze frame in the middle of the clip and the frame you're 'freezing' is cut is normal behaviour. FCP replaces the chosen frame with the freeze, it doesn't add the freeze. So the result is ...frame 3, freeze frame 4, frame 5 ..... NOT ...frame 3, frame 4, freeze frame 4, frame 5 .....
I have tried attaching a 28.5 MB zip file that contains the clip. It shows up as an attachment but when I select submit, the attachment disappears. Information on how to add attachments has allowed extensions as .zip. Instructions also states as follows: "Maximum File Size: 78.1 MB Maximum Image File Size: 7.8 MB". Not sure why this is worded as such. Can there be a 28.5 MB zip file attachment?
Yes I have AND I can confirm now the behaviour you're seeing with FUJI X-T3 footage.
Your FUJI X-T3 clip in a 30 FPS project and trying to add a freeze frame in the middle of the clip shows the fault you're described all a long. FCP doesn't add the freeze frame but only only cuts out the frame you're trying to freeze.
So this is a bug!
And it only happens in a project of 30 FPS, not in 29.97 or 23.98!
And it doesn't matter whether it's a HDR or SDR project, only the FPS causes the problem