Misha Aranyshev
Forum Replies Created
-
Set IN. Set OUT. Select In to OUT.
-
[Craig Seeman] “Maybe you’ve always been perfect at that but I don’t want editing to be hampered by my hand eye coordination or lack thereof.”
Never tried to perfect this type of the skills. Too dangerous for your wrist. There is a keyboard. It is fast and precise.
-
[Jeremy Garchow] “although I am missing your point about two overwrites.”
Backtimed Overwrite is a separate command in FCPX. And it doesn’t work if you have some ranges selected both in source and record. And it’s rather hard not to have ranges selected unless you’re working exclusively with the mouse and by throwing everything on the timeline first and then just trim by dragging edits.
-
Yes. It is a mess. Replacing IN in OUT with “Ranges” forced them to create two “Overwrites” instead of one and still you have to constantly look for unwanted ranges because they will mess your edit. Very bad design.
-
[Craig Seeman] “A big advantage of clip connections is that it becomes easy to move a complex stack related to a clip”
So before FCPX it was hard?
-
Yeah, right. But they split it in two flavors, D and Shift-D and you cannot set an IN without the app setting out so it is a mess.
-
I was.
-
[Craig Seeman] “It was designed to handle DV and Firewire”
Not true.
-
[David Battistella] “They broke down the tasks and freed things up. “
Like separating Overwrite form Backtimed Overwrite? Are you kidding?
-
We have a perfect clue. It’s right there in FCPX. All the design choices they made serve single purpose — prevent a casual user from making flash frames and single-frame gaps in their edit. That’s why the whole thing is in permanent ripple mode. That’s why there are two half-baked “Overwrites” and half a dozen of “Replaces” in the thing. That’s why a guy who edits full-time finds FCPX pathetic.