Terry there are two possible areas to examine:
(1) As Luis mentioned, check if additional Compressor instances are enabled. However, I think that only works for ProRes exports if the input is a single file or timeline. This is an older feature and only works for Max and Ultra machines (M4 Pro unknown, see below). It handles two sub-cases:
(a) If transcoding a batch of files, it will run them in parallel using multiple encoders. Each file is handled separately.
(b) If exporting a single timeline to ProRes, it will segment that and run those segments in parallel, then combine the output to a single file. There is overhead in that process, so the speedup (while useful) is much less than linear. Traditionally, it was difficult to segment Long GOP files so this was only attempted for ProRes.
(2) The HEVC/H.264 segmented export feature, added in 10.7, but only for Max and Ultra machines, which have multiple encoders (M4 Pro unknown). This feature implies the input and output Long GOP files are constructed with "independent" or "closed" GOPs, which do not reference each other. For dependent or open GOP files, I don't think those can be parallelized. There is no visibility or control over open vs closed GOPs. There are also automatic constraints on how long the timeline must be before it attempts this, which cannot be configured. On FCP's export dialog, there's a checkbox for "Allow export segmentation." I don't know about Compressor.
It's interesting you report this on M4 Pro. I thought all previous Mx Pro versions only had a single non-ProRes encoder, but Apple's tech specs says the M4 Pro has a single Video decode engine, two video encode engines and two ProRes encode and decode engines. That implies an FCP on M4 Pro might attempt segmented HEVC/H.264 encoding, whereas regular M4 or prior M1/M2/M3 Pro machines might not.
The M1 Ultra has two decoders and four encoders, plus four ProRes encode/decode engines.
This implies the M4 Pro is a bit unique. Also starting with M4, the non-ProRes encode/decode engines were optimized (details unknown) so that's another variable. While the same FCP software should work similarly on the full range of Apple Silicon Macs, we've had a few bugs that were unique to the Max or Ultra (all now fixed to my knowledge). This implies a possibility of an FCP problem unique to the M4 Pro that only happens in certain export segmentation cases. Such things are rare but not unheard of.
Here is an immediate step to gather more info the next time you can try it on the M4 Pro:
- Get FCP ready to reproduce the problem.
- Get this terminal command ready to run: sudo log show --last 30s > ~/Documents/LogShow30s.txt
- Reproduce the problem in FCP
- Once it happens, immediately run the above 'log show' command. The problem need not happen while running the command, since it looks back in time for 30 seconds, but it must have happened within the previous 30 seconds.
- Zip the log file and send it to me.
Beyond that, anything you can do to narrow down the replication scenario would help, with a goal of sending that to me. That said, this class of problem is typically timing-dependent, so it can be difficult to narrow this down.
I have an M1 Ultra and M4 Pro so I can run tests on those, but it's rarely beneficial to take blind "pot shots" at reproducing it for this class of problem.