-
Interesting notes about fcpx plugins
Check out this video sent to me over the Twittersphere.
I don’t use Magic Bullet Looks, but there’s some general interest comments in here:
Jeremy
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
53 Replies
-
-
Fixing that bug must be the big update at the first of next year that was mentioned earlier…
-
Of course.
A bug that affects “round tripping” from FCP-X to a “plug in” that so far nobody owns?
That’s clearly what they meant by the Apple announced 2012 update when they elected to use code words like “multi-cam” et al.
I hear Red Giant’s pain. They came across a bug that’s slowed their finalized development and that’s caused them not go get to market as quickly as they might like. Might even screw up the “Holiday Season” gifting period when some App Store customers might have bought the new MB package for a FCP-X editor they knew. That’s a shame. But hardly a disaster. The engineers will track things down like they always do. And if their product hits it’s target market then it will sell fine.
(I personally hope this doesn’t drive the already vastly overused “vignette” look onto a zillion more marginal videos, but, if so, such is life! – it took half a dozen years for typesetting to recover from the original Mac type capabilities – so it’s not like we haven’t trod this path before! (raising a glass to the San Francisco bit mapped font of my editing youth!)
Work in progress? Absolutely. But in an increasingly large number of situations for an increasing group of users, software that seams to have 99.9% of it’s feature set working solidly given the correct hardware and OS configuration – just like most other useful software.
So the rest will get sorted out over time while we get our work done.
That’s all that really matters to most “early adopters.”
FWIW.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
I’m really impressed with the brief Looks demo on the video.
I had wondered how Magic Bullet Looks was going to be crammed into the effects inspector but through launching an overlay window they have got round this restriction. To my knowledge no other plugin provider has come up with this solution before and I’m sure many will follow.
I actually think that the FCPX designers took a lot of ideas from Magic Bullet Looks when they developed their colour correction shape masks.
Once the technical bugs are sorted Magic Bullet Looks 2 will really enhance the capabilities of FCPX. Colorista 11 is now included within the software and so we will get our colour wheels back and the ability to really refine colour correction without round tripping.
-
[Mark Dobson] “I had wondered how Magic Bullet Looks was going to be crammed into the effects inspector but through launching an overlay window they have got round this restriction. To my knowledge no other plugin provider has come up with this solution before and I’m sure many will follow.”
That’s what I took from it as well, the custom UI for plugins might be available, yet.
Jeremy
-
[Lemur Hayop] “Certainly the snafu mentioned in the clip adds fuel to FCPX naysayers.”
And here are you waiting for them, don’t you?Serious FCPX critics are not based on bugs or operational shortcomings.
If was for bugs or shortcomings on the first versions they would be no NLEs.
rafael -
It is my understanding from developers that there is no FCP X plug-in architecture. It only exists via Motion presets. The architecture is FxPlug2 based on Motion5. In addition, custom GUIs are not permitted and Apple has directed developers to simplify effect UI control as much as possible within FCP X. Unless this changes, you won’t see a filter like Colorista II available inside FCP X. Fixing the roundtrip issue will help not only RGS, but also, DFX, Tiffen and GenArts. Right now, if it can be done with a slider it can show up in FCP X (assuming FxPlug2 compatibility). More than sliders? Nope.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “Right now, if it can be done with a slider it can show up in FCP X (assuming FxPlug2 compatibility). More than sliders? Nope.”
Didn’t this video just disprove this to some extent? Sure, it’s going to another inteface, but it’s there. How did Looks work in FCP7? Was that interface wrapped in to FCP7s filter window somehow?
-
Go back and look at that video again. The plug-in exists as a Motion plug-in/template. The actual controls in FCP X are only sliders. The output to a separate app (Looksbuilder) is via the HUD overlay button, which is technically legal. That’s how Looks has always worked. Note that this does not allow something like Colorista II to work unless Apple allows the color wheels and curves to appear via a HUD overlay as well. I would think that requires an architecture, which doesn’t currently exist in FCP X. Or hasn’t been exposed, yet. Right now, the mentioned bug keeps even this method from working. Likely that’s also what’s keeping GenArts Sapphire Edge stuck in beta.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I think I know what you’re getting at (no color wheels in the effects pane), but if you have to open a new window, is that such a big deal as long as it will theoretically work with the theoretical video out and the frame cache gets fixed?
And why are Motion plugins bad?
Reply to this Discussion! Login or Sign Up