You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Helpful articles for Final Cut Pro for Mac, Final Cut Pro for iPad and Final Cut Camera:
If I start Archive, zip, or tar to "unpack" a zip or tar file, Final Cut Pro slows to a crawl. The beach ball comes up, often just stops spinning, then stutters as it tries to spin.
Is this normal? Is there a fix? Or do I just not run Final Cut Pro and any of the three concurrently?
iMac 24″, macOS 12.6
Tom Wolsky writes, "How big are the zip files?"
The ones that contain .fcpbundle files are about 7 GB to 40 GB, and the ones that contain .mov files are about 1.9 GB.
Even so, we're talking about a near complete halt, not just somewhat slower. It is barely above a complete stop. It would probably take hours to load at the speed it's going. Well, it'd be a long time. Crawl is perhaps an overestimate. Nothing happens during the expand or unpack operation, but the CPU for Final Cut is about 0.7%. Pretty much stopped.
Luis Sequeira1 writes: "Is this with a spinning hard drive?"
Yes, the problem is with an HDD. Its max speed according to Aja is about 100 MB/second. Even so, Final Cut runs so slowly, that nothing happens. The CPU usage of the Final Cut process is like 0.7% when this happens.
I just tried it with the internal SSD, and it works fine except when I want to close a library with two compress operations running. Again, nothing happens until the compress operations finish or are canceled mid-stream.
I meant nothing or next to nothing in FCP happens, CPU is like 0.7% or so; the unpacking seems to work fine.
Maybe it's an I/O thing, and for some reason the I/O from Archive/zip/tar is crowding out FCP. But by this much? FCP pretty much comes to a stop. Even the beach ball comes to a stop at times! Stuttering in an unsuccessful attempt to get spinning. I get the Not Responding in the Force Quit box and in Activity Monitor, which I believe is normal for the beach ball.
I saw similar behavior years, maybe decades, ago -- but not to this extent! I thought the computer designers would have found a way, esp. since macOS is "the most advanced operating system" in the world, or something to that effect. I have a few quibbles with that.
Thanks y'all for chiming in!
To me this seems clearly an I/O problem.
I did not have a chance to try it with an HD. I did zip and unzip a few large folders in my internal SSD, and FCP did not skip a beat, no beach ball in sight.
My guess is just that the drive can't keep it up.
Luis Sequeira1 wrote:
To me this seems clearly an I/O problem.
Agreed. At least in part.
I did not have a chance to try it with an HD. I did zip and unzip a few large folders in my internal SSD, and FCP did not skip a beat, no beach ball in sight.
Me, too.
My guess is just that the drive can't keep it up.
Yes, but why is the Archive/zip/tar process so heavily favored? Maybe CPU usage has something to do with it. I don't know if I/O follows a priority scheme.
I'll have to try it with the slow hard drive, but this time starting FCP first. But it takes a while for the Archive job to stop with the back and forth thing. Not sure what it's doing during all that.
Well, hopefully I'll get my SSD drives back from OWC soon. In the meanwhile, I'll just not do the two things concurrently.
How big are the zip files?
Is this with a spinning hard drive?
Archive, zip, and tar bring Final Cut Pro to a crawl
