The most annoying behaviour of FCPX GRRR how toavoid it

It's not just you! it's me too, I've had it for ages.

I think it has something to do with dual screens, or perhaps spaces.

To make sure it doesn't happen I have to have clicked in the browser on my 2nd screen before hitting the spacebar. I literally today ended up making changes to the wrong project.

This definitely does not happen on single screen setups.

Tom

Thanks Ben and Tom

Ok so I'm not totally alone with this. I had this before on my Mac mini with one screen only...

This is weird.

I'd love to show this to Apple but how to be sure they listen.

Oh wow, ok, I've never had it on single screen, but then I use that less I guess..

I'd love a solution, as sometimes I press spacebar to play a clip in the browser, and instead it loads a different project into the timeline... frustrating

If you filled out the feedback page, they know.

I've had the same shift-F issue for ever it seems. And while I also use the Snapshot approach to versioning, that doesn't help the fact that on a match frame X will on its own change the project. Sometimes.

And yes, you have to press shift-F twice for it to work--sometimes more.

Worse, you can't even see the playhead marker in the browser. If you've got a big screen with 30 thumbnails, it's really hard to make out which clip has been activated by the match frame shift-F command.

And yes, I have asked Apple to improve this--make the line thicker or having a temporary glow on the whole clip--anything to improve usability.

I feel less lonely now

It is yet hard to understand why some get and it and some other not.

Not all bugs are universal. Some that seem so don't manifest exactly the same on all machines. There are so many possible hardware and software combinations, both Apple and third party, not every influence can be accounted for. Part of selecting beta testers is finding folks with very diverse systems to test on. In fact, the majority of bugs are not universal at all. That's the incomprehensible complexity of computer systems. At one time in my previous IT career I ran a beta test program. Very difficult thing, beta testing...

I have had the exact same issue the O.P. describes, and it occurs almost every day. I like to Snapshot a lot as I work, creating "back-up" versions, similar to the method others have talked about in this thread. (I used to go so far as naming the current project "Live Cut" and my Snapshots, "Assembly Edit," "Rough Cut 1," "Fine Cut," etc., but now I just let FCPX timestamp them.)

Getting back to this strange behavior of having a different project open up (and play) while match framing to the Browser... I've had that happen, as well as just when I select a clip to play in the browser. So I'll be skimming clips in the Browser, and then I decide to watch it in real time and hit "L", but instead of playing the clip as expected, a Snapshot project opens up and begins playing. I usually notice it happen immediately, because it's such an unexpected thing to happen, but still annoying nonetheless.

The real problem this creates for me is that I frequently share my workstation and projects with my boss (he'll come in to do finishing after my shift has ended, for example.) As Ben pointed out, you should always be double checking that you're editing in the correct project by looking at the title pane in the Timeline, just to be safe. But imagine if you worked with someone who didn't do this, on a regular basis? More than once, my boss has just started working on whatever Project timeline FCPX happened to open, finishing an old version of my edit. Hard to believe, I know, but I had this happen 3 times over the course of a weekend on one job. It's gotten to the point where I label the active project "EDIT THIS ONE", and add "NOT THIS" to all of my Snapshots!

I guess my point is, besides fixing the glitch, Final Cut needs a way to keep Snapshots or Dupe projects completely separate, or perhaps issue a prompt asking if the user wants to edit a Snapshot. (I've tried keeping them in a separate Event, but the Library Smart Collection foils that strategy. I've even added a qualifier to remove the text "snapsot" from this smart collection, but they're still accessible at the top of the Browser when you click on the Library root.)


Sorry for such a long post, hope I didn't get too off topic.

(Running FCPX 10.2.2, OS X 10.10.5 on a late 2012 non-retina MBP i7, 8GB RAM)

Being able to LOCK a Snapshot would be great. Then if you try to alter it, an alert would pop up, "Unlock this Snapshot in order to make changes, please."