-
Wish List For Final Cut Pro X
-
There’s always bizarre exceptions and you can play devils advocate to anything. But I wouldn’t say superimpositions are analogous to multiple audio channels. The result of superimpositions us still one linear video image. Where multiple audio tracks can still output as 5.1 for example. One is actually mixed together while the other just sounds mixed together.
But anyway, just my opinion and reasoning for my requests. I could actually survive without audio tracks too for my work. I have once made pseudo audio tracks with secondaries. Sometimes for video too just for organization. Just make an empty secondary that spans the whole project.
-
[Bret Williams] “I wouldn’t say superimpositions are analogous to multiple audio channels.”
Bret,
Superimpositions and multi-frames would be analogous to parallel audio techniques (ie. mixing).
A multiple-screen video installation would be analogous to multiple audio channels.
Additionally, 3D “placement” work is maybe an interesting parallel with mixing, though I have no experience with it (so I’d be interested to hear from those who have done more work changing convergence or placement in space, for example.)
I wouldn’t dismiss these examples as particularly “bizarre”, though multiple-screen video is perhaps more exceptional.
Franz.
-
The ability to color code individual clips in the timeline. A function available in Logic Pro……brass tracks are light blue…..drums are red……. This would give one the ability to quickly view the locations of specific characters, scenes in relation to the overall timeline.
K
-
I have 3 wishes (one was already in before):
1. import right into a keyword collection
2. send to motion
3. colourcoded rolesThere are many others, but these 3 are the top for me.
-
I mean selecting more then one at a time to export
Fcpx
10.7
FCP 7.0.2
FCPX 1.0..4
3 x 4TB Thunderbolt R4
VC100
3 x ioXT
MicroHub
Ultrascope
SmartViewCheck out the free iBook broadcast delivery 101 on itunes
http://Www.delivercommercials.com
-
[Craig RussillRoy] “I mean selecting more then one at a time to export”
Given the way the Project timeline works, my guess is something like that would actually have to be done through the Project Library instead. That could be a nice sequence but I believe FCPX is still doing sequential rather than parallel encoding. That kind of batch export would be much better if one could cluster with other machines or create some internal parallel encoding much like Telestream Episode Engine does.
For example, you could have 8 cores assigned to 4 parallel encodes or would otherwise cluster with other Macs on your network.
-
[Bret Williams] “As for paste content- that’s a function they haven’t brought back yet.”
Bret, I don’t know if you’ve played with it or not, but Paste Content is essentially how the current Replace Edit works. Select clip in timeline, matchframe, select destination clip, Replace from Start.
[Bret Williams] “Say you create 3 Keyframes to a clip. Maybe a jitter move. Now you want it to occur 20 more times. In just about any other app (avid, AE, motion, premiere) you’d highlight those three Keyframes and copy and paste them a few times. Then copy and paste that result a number of times. “
The kind of effect you’re talking about could be accomplished with a Motion effect right now. And if they put Send To Motion back in the program, I don’t see them developing the transform keyframing too much. I feel like they want animations like that to flow from Motion instead of making the same feature available in two places.
[Bret Williams] “BTW- you can change timeline clip views with keyboard shortcuts.”
Well, that’s some good news. I haven’t downloaded 10.0.8 yet. Guess I should.
Andy
https://www.timesavertutorials.com
-
Truthfully, copying and pasting Keyframes is possible in motion, but compared to AE and premiere, it’s keyframe engine is pretty much a dog in my book too. But at least useable. But they don’t make it easy.
And really, you’re going to send to motion for basic keyframing tasks? To me that just over complicated the project. Now what do I do if I want to copy and paste that key frame motion to another clip in the timeline? Send another clip to motion and copy and paste there? I dunno, since other apps have been doing this basic 101 task for 20 years, perhaps leaving out that feature isn’t the way to push users to your other app. Not really a selling feature. Still, would be nice if that feature (send to motion) actually existed!
-
I do it all the time. I make a folder in the project window and essentially is the project. Then within that folder I have the actual project, and the versions. The versions don’t have media dupes or rendrers.
I never did a save as in FCP legacy. That wasn’t a good idea. WITHIN the project, I would version sequences. But doing a save as would also duplicate bins and would call the project something else. That would create new scratch folders with different names and generally create a mess. If you were looking for backups, then autosaves performed that task.
To me, keeping the project and events separate is safer. You just version the project within the folder. So that accomplishes two tasks. It versions the project (sequence) and it provides separate projects so that if one gets corrupt, hopefully the previous is ok.
Not sure what happens if an event gets corrupt. The media in an event can be rebuilt easily enough, but if you had and compound clips in the event, they’d be gone.
There’s nothing to save in X. There are sequences(projects), and bns(events). Both are databases that are updated instantly with every change. So save as would be akin to duplicate. Which you can do. You can duplicate either with many different options.
-
[Bret Williams] “And really, you’re going to send to motion for basic keyframing tasks?”
No. But you weren’t talking about basic keyframing. Basic keyframing is currently possible in X. You were talking about 20-30 keyframes placed in random order on a clip. Something which can be handled quite easily with a behavior in Motion. You don’t even need to send to Motion because you can build a jitter effect and publish it and just lay it on clips in X. Then you can lay it on as many clips as you want.
So, since basic keyframing is handled, I just feel that Apple wants more complicated keyframing or moves to be done in concert with Motion. And as long as a “Send To Motion” feature doesn’t require an export (in other words, it uses an updating placeholder clip in X), then sending to motion won’t be overcomplicated at all in my opinion.
https://www.timesavertutorials.com
Reply to this Discussion! Login or Sign Up