[David Lawrence] “No. With overwrite, nothing on the timeline should move in either direction, except the object you’re dragging with your cursor. You might cover objects to the left or right with the object you’re dragging and shorten them, but they should never change position on the timeline or lengthen.”
Which is exactly what happens in my first video, also in the second video no edit points change position as well. The only thing that happens is that the clip to the right of the gap is lengthened as the gap clip moves, the original edit frame in that clip stays in the same position.
[David Lawrence] “But if you move a gap with the Position Tool, even one frame, the timeline incorrectly assumes the intention is to remove the gap so it ripples shut.
The correct and consistent behavior would be for gap to be left behind. Simple. It should work exactly the same for gap objects as it does for clip objects. This would fix the problem be consistent with the Position Tool mode. I don’t think I’m out of line here.”
This is true, and it’s either a bug or the end of a logic chain in the programming that assumes you don’t want to create a gap by moving another gap, either way it’s inconsistent behaviour I’ll give you that. That’s why we don’t use gaps in that way when editing in FCPX, as I explained previously.
I demonstrated the way you can achieve what you were trying to do without moving the gap clip, call it a workaround if you want,
[David Lawrence] “Steve, I respect your insights but there’s more going on than “You’re holding it wrong.””
For whatever reason, correct usage of FCPX if you want to avoid this behaviour, is to avoid moving gap clips with the position tool. Your example demonstrates using the tool incorrectly based on FCPX at this time. That doesn’t mean it doesn’t highlight the issue with gap clips though.
I will not agree with your statement that the entire timeline is “ripple only”, because apart from the gap behaviour, when you use the position tool, it isn’t.
What I can say, through my months of experience with FCPX on a range of projects, is that the issue doesn’t affect how I edit in FCPX at all.
I may disagree with some of your logic but I have a great deal of respect for the way you approach things which makes me question and re-examine the way I work in FCPX, every time you pursue an argument like this I learn something new and that’s certainly a good thing.
Steve Connor
“FCPX Agitator”
Adrenalin Television