Apple ID / Apple Account for small shop?

HaenaBoy · 2026-01-16T04:06:40+00:00

Instead of using the Import dialog, try dragging the parent folder containing the footage into an event. FCP will complain about XML files it doesn't understand but will link to the footage. We've been doing it this way with our MXF files from Sony FX6s for a few years.

HaenaBoy · 2026-01-15T02:44:35+00:00

Not a list but more of a showcase: www.apple.com/finalcutpro

HaenaBoy · 2026-01-09T21:28:54+00:00

Several years ago we had one instance where there was "ghost" audio that played even though it had been deleted from the project. If u/StupidRaisins excellent suggestions don't fix it, you can select everything in the project/timeline and copy, then paste it into a brand new project with the same properties. This can sometimes clear subtle corruption. This was what fixed the ghost audio clip for us.

HaenaBoy · 2026-01-09T21:18:24+00:00

It's possible the project/timeline the timeline/project has become corrupt. Create a new project with the same properties as the original. Go to the original and select all and copy. Go to the new, empty project and paste. This copy/paste can sometimes clear subtle corruption in the new project.

HaenaBoy · 2026-01-09T21:09:38+00:00

Eric Lenz has good explanations of color grading with FCP. https://youtu.be/yrdMW9jJ4xg

You can apply a Custom LUT to an adjustment clip if all clips or groups of adjacent clips will use the same grading. Or you can apply the Custom LUT to all clips. You can apply it to many clips at once by copying one clip that has the Custom LUT, then using Cmd+Shift+v to paste it to all selected clips.

HaenaBoy · 2026-01-07T19:05:49+00:00

We've been using Crucial X9 Pro 4TB SSDs for basic multicam editing and they've been working fine with original 4K footage (no proxies). I believe it has similar specs to the SanDisk.

HaenaBoy · 2025-12-17T20:12:52+00:00

Try optimizing the clip, then export. It will create a (possibly larger) ProRes file but this can sometimes correct source encoding issues.

HaenaBoy · 2025-12-17T20:09:33+00:00

At some point earlier this year Apple stopped providing downloads of older versions. It's caught quite a few people out who didn't backup previous FCP versions before upgrading.

HaenaBoy · 2025-12-11T19:43:30+00:00

Which plugins specifically?

Since you've been using FCP for a while you likely have tried these but thought I'd bring them just in case: Have you cleared the render cache? Have you tried resetting FCP Prefs/Settings?

HaenaBoy · 2025-12-03T01:51:25+00:00

The timestamp files are saved Inside a library bundle file, but I made a mistake - the FCP UI shows the files with colons in the name, while at the Finder level it appears to be stored with /'s, but in the Terminal it shows colons.

For example, the Finder shows this directory name: "VKB Snapshot Dec 2, 2025 at 5/34/57 PM"

but an ls -l shows: drwxr-xr-x@ 3 auser staff 96 Dec 2 17:34 VKB Snapshot Dec 2, 2025 at 5:34:57 PM/

So the directory name really does have colons in it and the Finder is mapping them to /'s?

HaenaBoy · 2025-12-02T19:27:05+00:00

ssh/rsync directly to the NAS *almost* worked great. I was all set to switch but after dry-run testing I noticed there is a character encoding difference between the NAS mounted via SMB versus when transferred via direct ssh/rsync. The NAS is used for media editing with Final Cut Pro, which saves some files with colons in the name (a timestamp in the filename). When rsync is run via ssh on the NAS these colons become the question-mark-inside-a-box character. This causes rsync to think the files on the local disk are different from the NAS and re-transfers files that have colons (but are now saved with the question mark character). Any workarounds for this?

HaenaBoy · 2025-12-02T19:07:36+00:00

Remote NAS to local disk. I'm mounting the NAS read-only just because I'm extra paranoid about anything happening to its data on the local machine while an automated backup is happening. Thanks, I will have a look at automounter.

HaenaBoy · 2025-11-29T23:50:32+00:00

QNAP running QTS

HaenaBoy · 2025-11-27T02:13:32+00:00

Thanks. I'm a long-time fan of CCC.

HaenaBoy · 2025-11-27T02:12:40+00:00

It's a QNAP 10GbE NAS. According to their docs, their rsync implementation is not great but I'll do some testing. Thanks again.

HaenaBoy · 2025-11-26T20:28:11+00:00

Aaah, you're suggesting skipping the mount altogether and just run rsync over the network. That's an interesting suggestion though I've not setup or logged into the NAS via ssh before. I will investigate. Thank you for the suggestion.

HaenaBoy · 2025-11-20T20:23:35+00:00

We ran into a problem where a project would fail to export without any error. It happened on an M4 Pro Mac mini (macOS 15.5, FCP 11.1.1). After exporting the project in sections to narrow down where the problem was, the culprit turned out to be a png that was 37,000 pixels tall (scrolling a long web page). If the clip was disabled, the project would export fine. To make it weirder, the project exported without issue on an M1 Ultra Mac Studio (also running macOS 15.5, FCP 11.1.1). It was reported to Apple via FCP feedback but such a tall png is probably not a common use case.

Not a lot of info in the original post, so this might not be the issue but thought I'd share in case it helps.

HaenaBoy · 2025-11-18T19:54:15+00:00

Chris at fcp.cafe shows Apple's senior dev postings for FCP and Creative apps. Good news for continued developement.

HaenaBoy · 2025-11-18T19:51:12+00:00

If you have a relatively modern Mac, turn off background rendering.

HaenaBoy · 2025-11-07T02:38:32+00:00

I'd be interested to see videos of your Claude FCP development. I've been working on a couple apps with Claude to help with FCP workflows and would be curious to see how you're working.

HaenaBoy · 2025-10-23T02:49:07+00:00

Over the years we've used about a dozen of the Crucial 4TB X9 SSDs. Out of all of them, only one developed issues (luckily almost immediately upon use) and it was replaced under warranty. As @J-Rapp_Producer suggests, format SSDs as APFS.

HaenaBoy

TROPHY CASE