3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
The most annoying behaviour of FCPX GRRR how toavoid it
After years of use of FCPX there's one thing that keeps creating me trouble and trouble and trouble.
I work a lot by iterating projects: V1, V2, ... V5 etc
When I am for example on V5 and I match-frame a clip and play it, FCPX actually a former project (for example V4), and most of the time I don't notice it
So I keep working and then I find out that I've been editing in V4 instead of V5
Am I the only one having this issue ? It happens to me all the time in all kind of projects
PS: another thing I noticed, when doing match frame, is that I need to press shift-F TWO times in order to actually see the clip. The first time it opens the event browser but does not set the cursor on that specific clip. Can it be linked ?
Thank you !!!
Please Log in to join the conversation.
I've never had issues with Shift-F. But then, I've never duplicated and renamed Projects like you're describing.
I may have to test this out some time, though. Sounds interesting if it is a bug.
Please Log in to join the conversation.
- Scott Markowitz
-
- Offline
- Elite Member
-
- Posts: 161
- Thank you received: 31
Ben is corrects about Snapshots. If you're making a progression of the same project, then duplicating is not what you want to be doing. Duplicating will not protect your nested compound clips and multicam clips like a snapshot will do.
Where I see this issue pop up is when I want to start a whole new project and I duplicate an old finished one to use as a spring-board point or a straight-up template.
The problem is caused by not double checking that you've opened the newly duplicated project. Only editor paranoia will completely fix this.
Try getting more stress and less sleep.
Please Log in to join the conversation.
I do agree that Snapshotting is a great way to keep updating so that the edit you're working in always stays fresh and the snapshots can act as output records of what I sent my client. I actually Share the Snapshot with them, with all of the time/date stuff in it. It's a good way for everyone to know which WIP it is.
One issue I do have with Snapshotting is that the name has a bunch of Unix unfriendly symbols in it like ' / & : etc. If I put the file into Dropbox, I've had Windows users tell me that they don't even see the file unless the offending symbols are purged. Does anyone know how to change the snapshot naming behavior other than manually adjusting during the Share output? I know it's a minor issue, but it's sometimes a PIA/time suck to strip all the offending characters in the name.
Please Log in to join the conversation.
I've found it frustrating at times, but I've been very diligent to look at the name of the comp I'm inside. It's the same as After Effects to me (even though it has tabs). You can still easily get lost on the wrong comp unless you make sure first.
Please Log in to join the conversation.
davechap wrote: This is really interesting. I've never thought about using the snapshot as the backup and continuing with the original. What is the naming scheme like with this?
I generally start with Blah Blah v01. I keep working in 01 and as I send edits out to client I make snapshots. I don't version up until either I get edit notes from the client or I try a completely different structure to my edit.
My V02 cut reflects the client requested changes to V01. V03 is made after I get notes on V02. That way, I can easily tell if we're making progress and when.
The great thing about Snapshot is that it really keeps a record of what was there, unlike After Effects, where versioning up means you have to version up all your subcomps or the lower version quickly loses meaning as a record of where you' were at. FCPX really makes it easy to go back in time and pick up where you left off.
One thing that folks don't use as much as they should is the Notes column next to the edit, so you can say stuff like "music only version" or client's alt suggestion without having to include it in the file name. It really helps keep good records (especially where the client changes his or her mind a lot!)
Please Log in to join the conversation.
Please Log in to join the conversation.
So I'm going to indeed try this approach, snapshooting and actually working on the original.
However, there might be many people still doing my way and getting frustrated with it. So maybe Apple should know. I don't know if it's a bug or a bad behaviour.
Please Log in to join the conversation.
If the new duplicate automatically opened in the Timeline pane, I can see someone complaining they don't like it. Cause the make a duplicate, name it, and want to keep working on the original, not the duplicate.
Honestly, what Project is active in the Timeline pane is simply paying attention. But tabs would be nice...
Please Log in to join the conversation.
You OPEN V5. So you're in V5.
When matchframing and playing the clip, V4 becomes active automatically, without you noticing. And there's no justification for that.
Please Log in to join the conversation.
I place my playhead over a random clip.
I shift-F and match frame back to the original in the Browser.
Works just fine.
In the Browser, I made a duplicate of the Project (cmd+D).
I opened the duplicate Project into the timeline pane.
I placed my playhead over a clip in the new duplicate Project in the timeline pane.
I shift-F to match frame it back to the original in the Browser.
The duplicated Project is still open and active in the timeline pane.
Works just fine.
OK, I'm not seeing any of these problematic behaviors.
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
manoucho wrote: …
When matchframing and playing the clip, V4 becomes active automatically, without you noticing. And there's no justification for that.
No duplicates at hand, so as a question:
Are V4 and V5 in the same Event?
Or is clips source and V4 in Event A, but project V5 in Event B?
… and I learned, versioning = snapshots, alone to avoid trouble with compounds ......
Please Log in to join the conversation.
But I'll try to make a video capture of the problem to show you what happens on my system.
Please Log in to join the conversation.
Are the clips in the same Library and/or Event?
Are the Projects in the same Library and/or Event?
Please Log in to join the conversation.
I will show you, I will take some time to make the video
Please Log in to join the conversation.
So, after doing Shift-F, I press SPACE to play the match framed clip. That's when things go wrong, it actually opens V1 and plays it.
What I want to do is playing the matched framed clip, and of course stay in V2.
Please Log in to join the conversation.
What keyboard/language are you using?
Are you using a custom command layout? Verify in the command layout that space bar is set to play, not do anything else.
That is very odd, I've never seen it, and can't replicate it on our 3 Macs.
Please Log in to join the conversation.
Please Log in to join the conversation.
BenB: wow, I am surprised (and somewhat relieved that it's not standard behaviour).
I am using U.S International - PC as an input. On an US keyboard... I've just tried regular US keyboard, same problem.
I've had this problem as long as I can remember. In my years of FCPX I've also clean-installed and chenged machine. Always had this.
So when you do match frame and press space, what does play, the match framed clip ?
I have also noticed that when my library is big, I need to match frame TWICE to see the actual clip in the browser (the first time is selected but somewhere up and down and I can't see it) - what about you ?
Please Log in to join the conversation.
Please Log in to join the conversation.


