Joshua David
Forum Replies Created
-
Yeah man, what they did needed to be done otherwise video editing software would become a huge mess in 20 years with tools skeuomorphic to things people never even heard of, would become bulked up with cruft, and computers are fast enough now that they are able to streamline processes that were clunky as a result of slow hardware in the past. (Avid and Adobe might be forced to make similar moves in the future)
Initially I thought this was a bug they should look at, but now that I think about it, it should have behaved this new way in all previous versions too, because a dissolve should be for 2 clips butted against each other, not a cheater opacity ramp for layered clips, which is how i’ve used it in the past. I sure am going to miss it though.
Ahh the cognitive dissonance of it all.
Thanks Tom, I was about to post this in the apple discussions and I saw your name in there answering questions to similar issues.
I just realized you wrote those books in your signature! I wanna get those! I wish I could get a signed copy of the new one.
-
In my post with the video link I meant “but not in FCP X”
-
I realize I can ramp the opacity with keyframes to get the same result, but that is an extremely tedious workaround to something that took one click in FCP 7. Especially If someone has many clips to do this to. It is not very Apple-like to make something take up to 8 clicks to do in the new software that took 1 or 2 clicks in the previous version. It must be a bug.
They probably didn’t follow the same parameters when they were writing the new code for transitions. They were supposed to get rid of cruft when they made this version, not make more. A workaround that takes 8 clicks in place of something that took 1 must be indicative of a bug. Didn’t people used to get fired from Apple for stuff like this.
-
I’m having a similar problem, here is a video of FCP 7 working great, and then trying to get the same result but not in FCP 7