-
Wish list for 10.0.9
-
Well my point would be that if it makes it a substandard tool for you, because of lack of a particular feature then the multi-cam tool in FCS would be extremely substandard for ME because of it’s lack of my necessary features. Defining something substandard because it’s lacking a particular feature is suspect to me. That was my point about other NLEs and their lack of certain features. Tongue in cheek I guess. Because they’re not substandard tools at all. But by their lack of a particular feature they would be by your definition. Which is just semantics I guess. Carry on. 🙂
-
Doesn’t work that way for me. It brings up the multicam clip. Not the original source clip.
-
Oh, wait. That’s exactly what you’re saying. Well, for whatever reason people want it to bring up the original source clip. I’m sure there are numerous reasons why you might want one or the other. Should be a modifier key. If you could at least dig into the multi cam clip and have the playhead be at the same spot, then you could match from there as a second step. Or, as the case often is, make some sort of alteration to just that bit of the underlaying clip. I often have to steady a particular section of a long hand held interview. If I steady the whole thing, it has to zoom WAAAAAAAY in because it’s based on the movemet across the whole clip. If you slice the clip up into just those particular sections and just steady that, then it does well. You can’t add smooth cam to an instance of the multicam clip in the project (sequence). That would be a nice feature. I think it’s been mentioned.
-
[Bret Williams] “the multi-cam tool in FCS would be extremely substandard for ME because of it’s lack of my necessary features. Defining something substandard because it’s lacking a particular feature is suspect to me.”
About 2 years ago, when X first came out I listed what I thought were the basic and essential features of a multicam tool, in expectation of the time when X would come out with one. These features are independent of any other aspect of the host NLE. Your complaints are about what’s lacking in FCP7, not what’s lacking in it’s multicam implementation.
Is it possible to criticize one aspect of X without criticizing all of it, or do I have to be a member of the club first.
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
Honestly, I’d be a happy camper if they added 3 things:
1) Robust, collaborative workflow, so two people can open the same event at the same time with better network support.
2) The ability to activate or deactivate events and projects so they don’t have to all load.
3) Better media management so you can consolidate a project. -
[Brett Sherman] “Honestly, I’d be a happy camper if they added 3 things:
1) Robust, collaborative workflow, so two people can open the same event at the same time with better network support.”
Agreed
[Brett Sherman] “2) The ability to activate or deactivate events and projects so they don’t have to all load.”
I know it’s a 3rd party app, but Event Manager X is awesome here. Very powerful, and since X opens really fast, it’s not a big deal to me to have it quit and restart if I need to change a set. Best $5 I ever spent. 🙂
[Brett Sherman] “3) Better media management so you can consolidate a project.”
Yes. 🙂
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Charlie Austin] “I know it’s a 3rd party app, but Event Manager X is awesome here. Very powerful, and since X opens really fast, it’s not a big deal to me to have it quit and restart if I need to change a set. Best $5 I ever spent. :-)”
With my backup system, it really F’s it up using the Event Manager X because events and projects can be in two separate locations. The only way to use Event Manager X is to manually backup. Plus quiting and starting is a PITA. I’m using sparse bundles right now, but would rather not.
Plus, there would be other useful features of having X control it. It could activate the events it needs when you open a project. Whereas with Event Manager you have to manually do it. My last project used about 50 events. It just would take a long time with Event Manager to figure it all out.
-
[Brett Sherman] “With my backup system, it really F’s it up using the Event Manager X because events and projects can be in two separate locations.”
Gotcha, I’m using the “Backups” app (works great btw) which sees the hidden folders as well, so that’s not an issue for me…
[Brett Sherman] “My last project used about 50 events. It just would take a long time with Event Manager to figure it all out.”
:-0 Yeah, I can see how that would be a nightmare. I try to have as few Events as possible for each job. FWIW you can set up “sets” now in event Manager to make this scenario a little more uh… manageable. I don’t know how having an event manager style interface in the app would be any better though, unless they make it so you don’t need to quit/restart when you load and unload Events/Projects. Guess we’ll see what’s in store soon enough. 😉
————————————————————-
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
If you could at least dig into the multi cam clip and have the playhead be at the same spot.
That would be a big one for me as well. Same thing when you open a compound clip in its timeline the playhead should be at the exact position where it was on the main timeline.
Reply to this Discussion! Login or Sign Up