MacBook Pro M4 Max (16/40) can't handle simple cross dissolve in Final Cut Pro

[matthewpomar]

I am migrating from a 16" MacBook Pro (last Intel version) to the new M4 Max MacBook Pro with the upgraded (non-binned) M4 chip. It was custom ordered with 64GB of RAM and a 2TB SSD.

I have a very simple Final Cut Pro project with 4K GoPro 12 LOG footage, the GoPro custom LUT, light Noise Reduction and when I play back video on the timeline where one clip transitions to another with the Cross Dissolve transition, Final Cut Pro goes down to about 2-3 FPS. I do have the Viewer set to Better Quality and if I change to Better Performance, it works fine (but so did my Intel Mac).

I am not using Rendered nor Optimized media, but in my research, I concluded this new M4 Max chip could handle simple transitions and noise reduction without pre-rendering the clips.

There's no memory pressure whatsoever, but the GPU maxes out when playing back the clips.

Should I be getting better performance here? If I have to edit in low quality or pre-render clips, I could do that with my old 16" MacBook Pro.

Thank you.

 

[R S K]

Which noise reduction. Which codec exactly? GoPro's own crappy one? You need to be much more specific.

But let me guess: not FC's own NR? If it were, then the GPU would most certainly not be "maxing out" since it's nearly irrelevant to FC's standard frameworks. This isn't your grandmother's Intel.

That reeks of a very poorly (if at all) optimized 3rd party plugin somewhere in the pipeline. Which M4 is also irrelevant (binned, non-binned, bla) since it's not Apple Silicon's fault if you throw shoddily made 3rd party stuff at it.

EDIT: I've come to find out that Apple has made relevant changes to the way their NR filter works. See below.

 

[matthewpomar]

Which noise reduction.

The built-in, OOTB Noise Reduction.

Which codec exactly?

I'm no expert, but I'm using the GoPro LOG 10-bit file format. As far as I know, there is no codec with the GoPro LOG files.

But let me guess: not FC's own NR? If it were, then the GPU would most certainly not be "maxing out" since it's nearly irrelevant to FC's standard frameworks. This isn't your grandmother's Intel.

Yes, it's the FC's own NR, which is why I am surprised/confused/disappointed...

That reeks of a very poorly (if at all) optimized 3rd party plugin somewhere in the pipeline. Which M4 is also irrelevant (binned, non-binned, bla) since it's not Apple Silicon's fault if you throw shoddily made 3rd party stuff at it.

Nothing stinks here... just a brand new computer with a fresh install of FCP, no third-party plugins, and a very simple project and timeline.


Thank you.

 

[iMacDragon]

There is always a codec, real raw video is completely impractical in any modern computing use.

 

[matthewpomar]

There is always a codec, real raw video is completely impractical in any modern computing use.

Thanks for the reply. I checked the Codecs attribute on the LOG video file, and it shows: HEVC, MPEG-4 AAC. Should the M4 Max be able to handle/process this codec without pre-rendering?

FWIW, I turned on background rendering and it's working fine, unless it hits a clip that hasn't rendered yet, the FPS drops again. Down side is this at least doubles the size of the project.

 

[R S K]

The built-in, OOTB Noise Reduction.

I have no clue what "OOTB Noise Reduction" is.

I'm no expert, but I'm using the GoPro LOG 10-bit file format. As far as I know, there is no codec with the GoPro LOG files.

LOG has nothing to do with compression. The codec does and is one of the main factors that determines how the video plays back. With or without filters. Every clip uses some kind of codec.

Yes, it's the FC's own NR, which is why I am surprised/confused/disappointed...

Me too, at first, since FC's noise reduction used to be real-time by not actually reducing noise when playing back. Only when either paused or subsequently rendered so as not to affect playback while working. But having just checked it for the first time in a while, it would seem that they have changed that, at least for the high-quality playback.

But then being "surprised/confused/disappointed" only shows that you don't understand that noise reduction is by far one of the most computationally intensive things you can do in video! So, if you think that is "disappointing," try the same with any other NLE or app and show me one that will do it for you full rez and final quality in real-time or even render it anywhere close to the speed that FC does.

Spoiler: there is none. Therefore, one might want to adjust one's expectations.

Nothing stinks here... just a brand new computer with a fresh install of FCP, no third-party plugins, and a very simple project and timeline.

An M4 can, without question, playback that kind of material without breaking a sweat. Even multiple streams at a time. But again, use one of the most computationally intensive filters, especially paired with one of the computationally most intensive codecs, and surprise, surprise, that can and will change very quickly. Even with the most powerful chip on the market.

On the other hand, I don't understand why, if it's fine when set to "Better Performance," you wouldn't just use that? That's what it's for. Or just set up the noise reduction and turn it off until you export.

I turned on background rendering and it's working fine

Of course, it is. Because all the calculations have been done and are baked into what is then just a normal clip!

Down side is this at least doubles the size of the project.

If you have the space, so what? You can always delete any and all generated files when finished with just 2-3 clicks. They're only temporary.


Bottom line:

Should I be getting better performance here? If I have to edit in low quality or pre-render clips, I could do that with my old 16" MacBook Pro.

Nope. And feel free to edit, playback, and render the same project on your old (Intel?) MBP. Be sure to keep a stopwatch handy and let us know how much you want to go back afterward. 😏