Can't edit project aspect snapshot

Question

When I select project>snapshots in the inspector I can create and delete snapshots with no problem. However I can not edit any existing snapshots when ever there is more than one snapshot existing (edit button obviously dimmed if only one snapshot exists). Selecting a snapshot to edit and clicking the edit button brings up a window with a button labeled 'Stop Rig edit mode'. I trashed Motion prefs but no change. Is this me only or a known issue?

Answer 1

I find that floating rig edit mode button a major annoyance, so much so that I personally try to avoid having to deal with snapshots: for the past few years, I've only dealt with 16:9 (HD or anamorphic SD) and I don't have an iPhone/iPod Touch... I have no real use for alternate snapshots. Quite frankly, I don't even know why 3:2 aspect is one of the options. As far as I can tell, there is no 3:2 aspect project available in FCPX (maybe that's something coming up in the next release? Or I'm missing something?) I know 4:3 isn't obsolete—there are 4:3 variants in 2K and 4K, so it will outlive SD. I've done a couple of projects with snapshots...back after M5 was first released; and honestly, I had completely blocked that floating button thing out of my memory! All I can say is: if somebody wants a 4:3 variation for a template I developed, they're going to have to make it worth my while (probably not anything I'll ever have to worry about ).
Glad you were able to figure it out! Sorry I missed the specific point (blocked memory and all...) I know way too many ways to blow up a Motion project, and the mere mention of a Rig? I see red flags everywhere. And you're right: that button is entirely misleading. What it probably means is there is an underlying Project (master) Rig that is inherent in every project (a "base" Rig object, if you're familiar with object-oriented programming), that we don't have access to, used to record all parameters. The Rigs *we* get to create are just "child objects" used to override selected parameters within the master rig. And that could very well explain why deleting a rig object/widget without removing parameters will keep those parameters tied up as if they were still connected to a rig, even one that apparently doesn't exist anymore. Adding parameters to a user created rig creates a "road" into the master rig, and trashing that user created rig with connections intact is like blowing up a bridge that connects the two points: the road is still there, but there's no longer any connection (and if you've gone past the ability to Undo... there's no way to repair that bridge either.) [I could be wrong... it's the way I would have designed it if I had written the app... except in my version: deleting a child rig would automatically disconnect all connections from the user to the master object *before* the child Rig was "garbage collected." There's really no excuse for that bug...]