- Posts: 10
- Thank you received: 1
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
fcpx m1 projects doesn't match fcpx intel projects
I normally apply color correction via color finale (a software already updated to the m1).
My surprise came when i open the projects that i was working on my intel iMac, they show completely different color correction (i already checked the automatic out that final cut applies and already turned it off). So i really don't know what to do.
Some examples from the difference between opening the project in the m1 and in the iMac.
The log is still intact. if i work the color correction all over again i can match the look i want, but it's completely crazy that i don't get the same image from the exactly same project.
It's a waste of time, when this is all native apps from apple.
Thank you very much for your help.
GF
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
I just did a test opening the same FCP project on an M1 MBP and on an Intel MBP. Different log clips with multiple native Apple color corrections. I can see no difference between the colors on the M1 and the Intel computer. Nor have I heard anyone else reporting such an issue.
You could do the regular thins like resetting your preferences but I don't think that will make a difference here.
I think you might get in touch with Color Finale. That is not a native Apple plugin, so the issue might be there. They have indeed released a version that is compatible with the M1, maybe check if there is a difference between the older Intel version on your Intel Mac and the new one on the M1?
- Ronny
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
- Ronny
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
scriptfactory.wetransfer.com/downloads/3...0210604152641/a9bf8c
it's different from the stills because that clip was very big. this is a 6 second clip. has the same problem. applied simple color correction (no plug in from the fcpx) in the intel mac. open the same project im m1. completely different image. i noticed something in the m1, the color correction was with completely different highlights from what i just set before in the same project in the iMac. it just changed them. surreal. notice that i already tested with sony footage and with clog 1 from c100 and this does not happen. it's only happening with c-log2 from c300mkiii.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
The difference is even more pronounced when the LUT is applied. The M1 file looks like it's HDR in Rec 709 library.
Please Log in to join the conversation.
Any suggestions on how to solve it? (don't know how to update the canon playback plugin - first time i hear of it lol).
The reason i have a 2nd computer is to switch from one to another in a regular basis. if i have to color grade all the project every time i switch computers i'm going to loose my mind at the end of the year
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
I get the same results here and I agree with Tom. The same clip without any LUT or corrections appears brighter in the FCP browser on the M1 than on the Intel, as you can see on the scopes in this screenshot. On the original clip, highlights on Intel are around 88%, on M1 they are close to 100%:
When I color correct the clip on Intel and I send the XML over to my M1, everything comes over exactly as it was on the Intel including the color corrections. But of course the picture still appears brighter on the M1. The difference in the highlights is very notable, see screenshot:
This test is not influenced by monitor calibration: I'm using the internal FCP scopes to measure the difference.
I have checked the Canon site and the Canon plugin for FCP is from November 2020, the specs don't mention compatibility with Silicon Macs. I don't think this would cause the issue anyway as IMO the plugin only works with Canon RAW formats (CRM) and you don't shoot RAW.
As it only happens with this specific format, I think you should report this issue to Canon. I have submitted a report for FCP but it's unlikely that Apple can solve this.
- Ronny
Please Log in to join the conversation.
I found this app. Can't vouch for it's quality but worth a try on a sample (use the free trial)- www.appleproresconverter.com/guide/mxf-t...to-fcp-x-prores.html
EDIT: It looks like Compressor can convert it as well if you have that, but I bet Compressor will have the same issues. I'd try converting it on the Intel Mac. I'd also recommend turning OFF the LUT when converting.
Please Log in to join the conversation.
- Tom Wolsky
-
- Offline
- Moderator
-
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
I have done the test. I have imported the clip in a Library on the Intel machine and have measured the original image using the scopes: whites were at 88%.
Then I have created optimized media for the clip (which is ProRes) and have measured the original image using the scopes: whites were at 100%!
Then I have sent the Library over to M1. Here, I got no difference in the highlights between the original clip and the optimized clip.
So I'm afraid the problem is with the Intel Mac: it shows the highlights of the canon c-2 log footage too low. On the M1, I don't see a difference between original and optimized c2-log footage.
- Ronny
Please Log in to join the conversation.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
As the problem seems to be with the Intel and only with this specific format, I don't think either Canon or Apple will solve this any day soon.
For your workflow, I would advise you to optimize all the c2-log clips on your Intel Mac. You probably will have to re-adjust the current color corrections by adding an adjustment layer above the c2 clips and bringing the highlights on the adjustment layer down by around 12%.
If optimized files are too heavy to take on the road with your M1, you also can create ProRes proxy media to edit on the road. I have done the same test with proxy media and it gives the same results: original clip on the Intel is incorrect, with proxy media it is correct.
- Ronny
Please Log in to join the conversation.
Please Log in to join the conversation.
- ronny courtens
-
- Offline
- Moderator
-
- Posts: 4455
- Thank you received: 962
So there are two solutions you can use:
1. Convert after importing (existing project)
Optimize all the c-log2 clips that you have imported into FCP on the Intel Mac (or create proxy media). You can convert all the clips at once, no need to do this clip by clip.
When you copy the Library over to your M1, the clips will look exactly as on your Intel. Even if you already have done color corrections on the Intel.
The only disadvantage of this is that your Library will have all your original Canon clips as well as the transcoded versions. This will take more place in the Library.
2. Convert before importing (totally new project)
Don't import the c-log2 clips in FCP. Instead, convert all your c-log2 clips to ProRes 422 outside of FCP, using a transcoding application such as Compressor, Handbrake, etc...
Then import the ProRes 422 clips into FCP on your Intel Mac or on your M1 Mac, it does not make a difference. Wether you work on Intel or M1, the colors will always remain the same.
The advantage here is that your Library will be lighter because it only has the ProRes 422 clips, the original Canon clips are not imported.
Don't hesitate to post back if you have any further questions.
- Ronny
Please Log in to join the conversation.



