-
Layers and transitions
-
When you’re working with a client behind you, speed is an issue, going back and forth between 2 programs really isn’t what I want to do for simple compositions.
Chip Whiting
99 Productions LLC
541-343-0099 -
[Tom Wolsky] “No composite modes in secondary storylines. No transitions on connected clips. It’s like each connected clip is entirely separate from the clip adjacent. Not very magnetic if you ask me.”
No transitions between connected clips (that aren’t grouped into a storyline) makes sense, because they have no fixed relationship to each other. They could be pulled apart or caused to collide if the primary storyline clips they were connected to were moved, at which point what would happen to the transitions? A secondary storyline avoids this problem, because the whole storyline has a single point of attachment to the primary storyline, rather than each clip having its own point of attachment.
But while transitions between connected clips are problematic, they could (and probably should) still let you add transitions to the head or tail of a single connected clip, to transition from or to the underlying primary storyline clip.
Blend modes not working in secondary storylines seems like it’s just a bug, because the menu is still available, and opacity still works.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
“because they have no fixed relationship to each other.”
Except that they’re abutting each other. The application is spending far too much energy and functionality trying to protect me from myself and not enough just trying to help me. Because of this behavior we’re constantly having to do workarounds.
The application touts its magnetic properties, which are really excellent. However, if you break something apart it is now completely and irrevocably free-floating, no reference to where it came from, no connection, and no simple way to put it back together again. The application will help you, but if you override it in any way because you have to, like editing video and audio, then it falls apart and refuses to co-operate, like it’s throwing up its hands and saying if you want to do that you’re on your own.
“what would happen to the transitions?”
The same thing that happens in most editors, the transition either disappears or gets attached to the remaining clip that’s unmoved.
All the best,
Tom
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Coming in 2011 “Complete Training for FCPX”
and “Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press -
It all is figured out except for the transitions not using the alpha channel when they are in transition. My background is white on the original storyline and it goes black as soon as a transition starts and turns back to white when the transition completes. Bug?
Chip Whiting
99 Productions LLC
541-343-0099 -
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
-
If you ramp the opacity in the video animation HUD it seems to work correctly.
All the best,
Tom
“Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Coming in 2012 “Complete Training for FCPX” from Class on Demand -
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.
-
In my post with the video link I meant “but not in FCP X”
-
You do realize this is a wholly and completely and irrevocably new application and has zero benefit or basis in any antecedent and has totally nothing at all to do with legacy versions of FCP?
All the best,
Tom
“Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Coming in 2012 “Complete Training for FCPX” from Class on Demand -
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.
Reply to this Discussion! Login or Sign Up