Misha Aranyshev
Forum Replies Created
-
I seem to remember this “investment” was a fee said OS maker had to pay to get its web browser as default on Mac OS.
-
It only works with playhead. You can have marks on either source or master, not both.
-
[Craig Seeman] “And how have you managed to set an Out without an In, in FCPX?”
Bingo! I didn’t manage. No way. Thats’ why they had to come up with Shift-D to emulate this scenario. The problem is Shift-D doesn’t work right too.
-
[Craig Seeman] “Replace from Playhead which is ONE aspect of Replace.”
Which is one that’s missing. Which is one that’s really so different from overwrite to be worth of a separate command.
-
[Craig Seeman] “Neither Replace from Start nor Replace from End ripple.”
But Replace does.
[Craig Seeman] “D key works fine for me.”
Set one IN and two OUTs. See what happens.
-
Oh, sure. They had time to implement two half-baked flavors of overwrite and half a dozen of “repalces” but didn’t have time to implement stuff people actually use?
-
[Craig Seeman] “Please read the entire thread.”
It would be nice if you followed your own advice. FCPX “Replace” isn’t Replace we’re talking about.
-
I saw the potential in CoreData right when they started to talk about it developing Tiger. Not so sure about AVFoundation. Too many changes along the road — Quartz, CoreVideo, QuickTimeX. Still no higher bit depth display and apparently no baseband video out after all work.
-
It’s replace in the name only. And it ripples! Useless crap. They screwed up Overwrite too by the way. Haven’t you noticed?
-
[Christopher Travis] “Until I’ve really road tested it, I’m going to assume that the functionality is there, just hidden under a new name.”
No. It isn’t there. There is something under the same name but it’s totally different. It doesn’t replace on a frame, only on in or out point. And it ripples.
[Christopher Travis] “I thougth the WHOLE POINT of the new FCPX UI and ALL of the controversy it has caused was that it was supposed to make timeline editing faster, at the expense of certain more high end I/O workflow features.
“No, the point was preventing casual users from creating flash frames and short gaps at the expense of everything else that makes an editing app an editing app.