Final Cut Pro - slow on timeline after cutting and skimming

Hi there guys. 
I have weard problem with my Final Cut. Im on edit and sometimes UI is getting laggy - like 1-2 seconds for work again after cut. Somethimes its going longer 

Im editing diffriend files but results are the same:

h264 from A7iii, h264 from Sony A6300 and h265 slog from FX30. All the clips are on diffriend projects and results are very similar. Ive change my MacBook Pro M1 to Mac Studio M2Max 32/512 and I thought it will be better : ( 

I have all the clips on T7 SSD (500gb free space), Cashes are on internal SSD (180gb free space). 

I don't use third party plugins
I use luts on slog applied on adjustment layer, footage from a7iii and a6300 are straight out of camera on timeline 

Im little bit worry : ( I don't like this while im cutting
Maby you could help me 

Is there any chances that's the file system fault?

I don't know why im using in T7 ExFAT, on another SSD from Samsung and external enclosure I have Mac OS Extended > <

Any idea?

szulzykk wrote:

Is there any chances that's the file system fault?

I don't know why im using in T7 ExFAT, on another SSD from Samsung and external enclosure I have Mac OS Extended > <

Any idea?

Your drives should have at least 20% free space available. Depending on the size of the drive that amount could get used up quickly for various cache files.

All drives used with FCP should be formatted APFS for SSDs and HFS+ (Mac OS Extended w/Journaling) for HDDs.

Though FCP supports various flavors of H.264 and H.265 media, things always work better if you use ProRes proxies or optimized files.

That's why I have cashes on internal SSD not external.

Ive solved the problem - ive erased ssd and change exfat to Mac OS Extended and everything is going great.

Don't get me wrong but sticking to Prores or proxies with these machines are nonsense and sorry...little stupid. They have so much power and they are great at editing without creating prores or proxies etc - these kind of files can handle 10 years Macs or PC's so it not makes any sense to me to buy new Mac and still makes optimized media files - where is sense right there. My old MacBook M1 was a beast on h264 and colorgrading so that's why I didn't know where the issue is - 5x better Mac Studio have problem with 1080p!

Anyway I solved it and now FCP doesnt think after cut on timeline or skimming - everything runs flawlessly.

Thanks : )

szulzykk wrote:

....sticking to Prores or proxies with these machines are nonsense and sorry...little stupid. They have so much power and they are great at editing without creating prores or proxies etc ...it not makes any sense to me to buy new Mac and still makes optimized media files...

That is not universally correct. I have a top-spec M1 Max MacBook Pro 16, and top-spec M1 Ultra Mac Studio, and have edited vast amounts of multicam Sony 4k XAVC-S material, both 8-bit 4:2:0 and 10-bit 4:2:2. Even on the M1 Max, multicam 4k XAVC-S can be a bit sluggish. The M1 Ultra has parallel decoding engines so it handles it a bit better. Despite that I will sometimes generate proxies if I am editing three-camera 4k XAVC-S on my M1 Ultra. 

I am currently editing some 8k/23.98 Canon Cinema RAW Light from an R5C, and that is really sluggish, even on my M1 Ultra. Multicam RED 8k/23.98 R3D is also not super smooth, but it's better than the Canon's Cinema RAW Light.

Supposedly there was some mild performance issue with the M1 Ultra that impacted parallel encoding (not decoding) of H264 and HEVC formats. Allegedly this was improved in the M2 Ultra, but no reviewer has extensively investigated this. There was a separate design issue regarding the M1 Max and Ultra GPUs that in some cases seemed to limit GPU multi-core scalability. That was also supposedly addressed in the M2 Max and Ultra, but (again) there has been little authoritative technical investigation by 3rd parties.

So it's quite possible that the M2 Max is faster at exporting some H264 codecs than the M1 Max or maybe even the M1 Ultra. However that would be unique to the M2, not a general statement about Apple Silicon in general or even the M1 Max/Ultra. Regarding the decoding side, that is less understood. The exporting (or encoding) side is easier to test, so reviewers often do timed exports. The playback side is harder to test, and I haven't see any reviewer do latency or frame rate tests specifically targeting decode performance, much less parallel decode performance on single stream vs multi-stream input.

szulzykk wrote:

Ive solved the problem - ive erased ssd and change exfat to Mac OS Extended and everything is going great.

Just a quick note to follow up on Dave's post - HFS+ (Journaled) AKA Mac OS Extended is optimized for mechanical media, whereas APFS is optimized for SSDs.  While you can certainly use either, APFS offers advantages in R/W strategies and storage optimization.  Unless you need to connect that drive to an older Mac running High Sierra or earlier, APFS is a better option for your SSD.  Should you decide to reformat, also double-check that your partition format is GUID and not Master Boot Record (MBR).