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.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Project isn't updating to reflect changes in Multicam

Hi folks! Finally getting back to my project... :-)


Question: I created a Multicam and added it to two Projects in my Library: "Main Project" and "Raw Project". I did some editing in each of the Projects.


Then I went back and added a new Angle to the Multicam, which shows up properly in the Angle Viewer for the Multicam. The problem is that when I enter the Angle Viewer in "Main Project", the new Angle does not appear. It's like that Project is not updating to reflect the new Angle. Strangely, though, "Raw Project" does reflect the new Angle.


I've tried restarting FCP, but that didn't help.


Any suggestions? I need to use this new Angle in "Main Project". Is the Multicam in this Project somehow unlinked to the main Multicam? If so, I do I re-establish the link? Or did I do some edits in this Project that prevent new Angles from appearing? Is there a way to "refresh" the Multicam within the Project to get it to see the new Angles?


Thanks in advance!


Dave

Mac mini, macOS 14.6

Posted on Aug 29, 2024 5:46 PM

Reply
Question marked as Top-ranking reply

Posted on Aug 30, 2024 9:12 AM

That's odd. You're positive it's the same multicam in both projects? Park on a multicam frame on the Raw project timeline and press Shift-F. That will match frame to the multicam in the browser. Note the multicam. Do the same for the Main project. Does it also matchframe back to that multicam?


You could try resetting FCP preferences/settings. Hold option and command when launching FCP and choose Delete Preferences... (or Delete Custom Settings depending on the FCP version). FCP will then open the default Untitled library. Reopen the library you were working on, set the preferences back to the way you like (turn off background rendering, etc.) and see if the issue has been resolved.

15 replies
Question marked as Top-ranking reply

Aug 30, 2024 9:12 AM in response to Dave Kitabjian

That's odd. You're positive it's the same multicam in both projects? Park on a multicam frame on the Raw project timeline and press Shift-F. That will match frame to the multicam in the browser. Note the multicam. Do the same for the Main project. Does it also matchframe back to that multicam?


You could try resetting FCP preferences/settings. Hold option and command when launching FCP and choose Delete Preferences... (or Delete Custom Settings depending on the FCP version). FCP will then open the default Untitled library. Reopen the library you were working on, set the preferences back to the way you like (turn off background rendering, etc.) and see if the issue has been resolved.

Sep 1, 2024 5:52 PM in response to Dave Kitabjian

I think you've now got the concept that creating a project snapshot separates itself and references new parent compounds and multicams. I typically only create snapshots as point-in-time backups in case something goes wrong and need a way to get back to a previously edited segment.


As for why Apple made the snapshot UX decision to instantiate new parent compound and multicam clips in the browser only when the clips are referenced/needed rather than dump them all in the browser at snapshot creation time, my guess is they didn't want to unnecessarily clutter the browser since there could be many dozens in a large project.

Aug 31, 2024 2:14 PM in response to Dave Kitabjian

If you created a snapshot of the Raw project and then renamed it to Main project, Main will reference its own parent copy of compounds and multicams.


Duplicate projects and clips in Final Cut Pro for Mac - Apple Support (English)

"When you duplicate a project as a snapshot, Final Cut Pro embeds copies of compound or multicam “parent” clips in the duplicate, so any changes to other instances of those clips do not affect the duplicate."




Aug 31, 2024 10:20 AM in response to Dave Kitabjian

Dave Kitabjian wrote:

But I'm quite certain that Untitled Multicam Clip 1 didn't exist until pressed Shift-F! I never saw that before! I could be wrong, I guess. I'm trying to prove I'm not insane by restoring the project from Time Machine, but at 95GB it's going to take forever (currently about 10GB restored...)

Okay, it turns out I'm not insane :-)


I restored the entire project and then retraced my steps, and sure enough "Untitled Multicam Clip 1" appears out of thin air! I recorded my screen session so you can see it for yourself. The full video is linked below. But I'll put a trimmed portion right here as a GIF.


https://www.dropbox.com/s/izzicpv05i7ztj1/magical%20appearance%20of%20mulitcam%20clip.mov?dl=0



Aug 31, 2024 8:36 AM in response to terryb


terryb wrote:

...press Shift-F. That will match frame to the multicam in the browser.

Aha! Magical trick! I will note this! (I now see that you can right-click on the multicam in the project timeline and do Reveal In Browser. Handy!)


And sure enough, you're right. Sort of.


When I did the Reveal in "Raw Project", everything works as expected. FCP selects "Untitled Multicam Clip" in the Browser. But when I did the same in "Main Project", it took me to "Untitled Multicam Clip 1" in the Browser! And that one is missing the Angles.


But I'm quite certain that Untitled Multicam Clip 1 didn't exist until pressed Shift-F! I never saw that before! I could be wrong, I guess. I'm trying to prove I'm not insane by restoring the project from Time Machine, but at 95GB it's going to take forever (currently about 10GB restored...)


But meanwhile, I wouldn't have created a duplicate Multicam intentionally either way. How could this have happened? If I duplicate a Project, it wouldn't duplicate included Multicams, would it? I thought they both linked back to the common Multicam.


Hmm, maybe I did a snapshot:


Duplicate projects and clips in Final Cut Pro for Mac

Duplicating projects and clips is a fundamental technique in your editing workflow. For example, you can duplicate a project to work on a new version of it. You can also duplicate a project and change its settings (such as the aspect ratio) at the same time.

If you work on projects that contain compound clips and multicam clips, you can use the Snapshot Project command to create a self-contained backup version of a project that includes referenced compound clips or multicam “parent” clips. Changes you make to other instances of the compound clips or multicam clips do not affect the versions in the duplicate, so your project is protected from accidental changes. 

I still don't get why I couldn't see it before. But maybe I'll check the Time Machine to see if I just missed it down below in the Browser list...



Sep 1, 2024 8:16 AM in response to Tom Wolsky

Tom Wolsky wrote:

You make a feature request for it. It’s not a bug.

So just to be clear we're on the same page, you're saying it's normal for a multicam to be completely invisible in the Browser until you find it in use on a project timeline and then do a Reveal In Browser, at which point we should expect it to magically pop up in the browser? I don't see that mentioned anywhere in the manual, but if you say that's normal, I'll refrain from reporting it as a bug.

Sep 1, 2024 8:42 AM in response to Tom Wolsky

Tom Wolsky wrote:

That only happens with a snapshot in the same library. A simple duplicate will have both projects referencing the same multicam clip.

Ohh, I see. Hmm. Apple says "You can create a “snapshot” backup of the entire project to protect it from accidental changes." Sometimes I have used this as a way to fork a project into two different projects, as suggested in various places in the forums. But I wonder if Apple is quietly assuming you're not going to modify the snapshot, and therefore hides the snapshot's clips in the browser (until your explicitly Reveal it).


I'm thinking that's their rationale and that it's by design. I could probably live with Duplicate and not be afraid of damaging the original content if I knew exactly what was pointing to what. Eg, I'm pretty sure cuts-and-switches belong to the project and don't affect the source multicam. But I think adding/removing angles and changing their sync belongs to the source multicam.


All the pointers in FCP can be great for managing file size and reusing edits, but it does make it hard to understand when you're dealing with a true copy of something vs. a link to the original, all of which can get you into a lot of trouble if not done properly.


Thanks again. This has been very informative!

Project isn't updating to reflect changes in Multicam

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.