Really loving VUO for dome work… congrats and keep up the development happy to support
@alexmitchellmus, since this is getting into a separate topic, I copied your comment over to How to make an app store fund itself and further Vuo development? and will reply there.
Chosen to be implemented.
so pleased this will be added. opens a lot of doors for personal use as @alexmitchellmus has pointed to and also commercial potential for our code. thanks for taking this on Team Vuo!!!
1 Like
Just to clarify: Currently one needs to generate with Apple Motion an FCPX plugin. Can we keep that workflow? (I don’t think we need any special wrangling of FCPX plugins)
@alexmitchellmus, our plan is for Vuo to generate both an FxPlug and a Motion template, so that you can export a plugin from Vuo and immediately open it in FCP X. Thus it won’t be required for Vuo users to wrangle the plugin in Motion. However, for those who want to, the FxPlug and auto-generated Motion template could be opened in Motion.
1 Like
Ok @jstrecker, that sounds like more work for you guys but also sounds better for end users. There are lots of complex things that Motion can do (as you would know) like making rigging sets etc, and publishing specific variables. Lots of FCPX effects are actually just Motion effects anyway! :-)
I haven’t looked at Motion in a long time, but does it allow for more interaction with effects than just the basic inputs of numbers, index, string, image and so on? Will modal dialogues be possible to load files or do complex interactions to setup something with a preview window or the like with Vuo FX plugins ?
Also one thing that really limited QC was the inability to programmatically control published inputs. One can’t show/hide inputs depending on relevance to other settings, one can’t change named index list items depending on state (enumerated lists), one can’t change the min/max/step-size settings on sliders depending on other settings programmatically. Will Vuo also be bound by such limitations or are there ways around. Sorry, I would love to simply fire Vuo up and just see for myself but I’m still largely unfamiliar with the basic node set and nuances and it’s a bit harder to push towards a goal as a novice in Vuo than QC in my humble opinion, even with a wealth of QC experience, just because the flow paradigm is less simple (but obviously more powerful with it).
There are a couple of ways that plugins exported from Vuo may be able to pop up additional UI elements like a preview window. The first I’m not totally sure about since I haven’t tested, but it may be possible to just add a piece in your Vuo composition that displays a window as usual. The second possibility would be for Vuo to support the FxPlug onscreen controls API. I would say put onscreen controls on a separate feature request if you want it, since it goes beyond the basic ability to export Vuo image filter/generator compositions as FxPlug plugins.
Your suggestion about programmatically showing/hiding published inputs could be built on top of the proposed UI for storing and editing published input port values. Again, separate feature request. Please create if you’re interested.
P.S. — If it’s been a while since you last tried Vuo or looked at the tutorials and manual, I’d encourage you to take a look at what’s changed. We still have a number of event-related usability improvements slated for Vuo 1.3, but in the meantime I hope that the great tutorials by Vuo community members, the improved documentation, and the added example compositions can help demystify events for you. If you have specific questions about events, please ask!
1 Like
Is there any further update on the status of this feature (FxPlug plugin generation) beyond “Chosen to be implemented” ? I have a lot of experience creating visual effects plugins for video editors and compositors (most recently using Quartz Composer and Motion to create effects for Final Cut Pro) and I would be eager to give feedback on the Vuo implementation as soon as a usable build was available. I’m also eager to replace Quartz Composer with Vuo wherever possible so I expect I’ll be making use of this feature. Thanks.
Hi Kingluma, I’d love to see what kinds of plugins you make, do you have them online?
Do you use the Noise Industry ProEffects to finish your plugins? I’ve been thinking to get, but possibly seeing as Vuo wont work with that i just need to rebuild effects in Vuo where possible.
kingluma.com
yes, FxPlug integration (when necessary) and distribution through Noise Industries FxFactory
- previously I was @ BorisFX for many years
@kingluma, no updates yet. Thanks for offering to test! We’ll keep you in mind if we do an alpha/beta release.
Ah @kingluma I know you as Boris Effects… much respect to you! I also recall you organised someone within Apple management to address a bunch of unfixed and showstopping bugs in one of the more recent releases, thanks heaps for that, was embarrassing that they disowned QC for so long.
allright, N O W would be a good time for this : )
1 Like
yes agreed :) they should deploy this asap
Resolved in Vuo 2.0 beta.
1 Like
I think this is included in the main release now. If so, please update the marketing on this Vuo webpage!
Speaking of which the feature comparison with other graph composing softwares doesn’t mention Metal, which Vuo is native on since the latest release. It’s probably worth having a tab in this table of comparisons on graphics frameworks to highlight that Vuo is native to Metal now.
Somebody actively developing a QC-like technology told me the other day they need Metal rendering when I suggested Vuo and he didn’t realise Vuo is now native to Metal.