Mechanica's picture

Hypothetically, I've figured it out. It had to do with one of my subcomps using an unnecessary "fire on start". This is the second issue I've solved by removing unnecessary "fire on start"s. Be careful with those everybody!

Mechanica's picture
Mechanica commented on Mechanica's Discussion, “Crashing Subcomposition

So, it looks like the crash was being caused by the chain of "add" nodes. The first was being triggered by the "fire on start" and then passing the event on to the next add block. I guess that was unnecessary, but for whatever reason it was making it crash. Anyway glad to have found the culprit.

Bodysoulspirit's picture
Bodysoulspirit commented on Mechanica's Discussion, “Crashing Subcomposition

Okay, that makes sense. I just went ahead and upgraded to Pro and the beta, so hopefully I'll have better luck now.

Ah cool ;) In Vuo 2, sub-compositions don't need to be installed strictly in the Vuo Application Support library, they can for example be shared alongside a composition, like I did, in a modules folder next to the composition (you can still install those if you wanna use it across several compositions).

And in Vuo 1, the whole sub-composition was updated when any port was updated, in Vuo 2 not the case anymore, ports get updated individually.

Mechanica's picture

Lots of crashes when trying to view port data

Hey all, So I just upgraded to pro and updated to the beta. I'm having issues with trying to run some of my compositions containing nodes I created on the previous version (as is to be expected). A lot of it seems to be connected to the new way subcompositions handle event flow. I'm trying to debug them and figure out what needs be changed, but Vuo keeps giving me the beachball of death when clicking the data ports of some nodes in the broken subcomps in question. Particularly while the comp is running. This is making it pretty tough to sort out what's going on.

Mechanica's picture
Mechanica commented on Mechanica's Discussion, “Crashing Subcomposition

Aaaahh haha! That makes waaaay more sense!

cremaschi's picture
mic commented on wmackwood's Discussion, “VUO and QLab4 . . .

Dear William , as a user of both softwares, I'd love the possibility to create Vuo plugins for QLab too. Unfortunately it's not just a matter of port names. QLab actually allows just QC plugins; not Vuo's. The possibility to have inputs and outputs names beginning with _ wouldn't be enough. QLab should develop the necessary support for Vuo plugins, that in term of coding is something really different from actual QC support. I posted a feature request years ago in QLab users group properly asking for that development, but at the moment there's no feedback on that.

cremaschi's picture
mic commented on Mechanica's Discussion, “Crashing Subcomposition

Sorry, i meant 10.14.6.

Mechanica's picture
Mechanica commented on Mechanica's Discussion, “Crashing Subcomposition

Oh right! I was a little confused by mic's comment I guess. OS X 10.4.6 was quite a while ago!

Okay, that makes sense. I just went ahead and upgraded to Pro and the beta, so hopefully I'll have better luck now. Thanks so much again for the help!

wmackwood's picture
wmackwood posted a new Discussion, “VUO and QLab4 . . .

VUO and QLab4 . . .

Hello VUO team,

Thank you for all your great work on Version 2. I'm enjoying all the improvements.

One of the most popular programs for delivering sound/projections/lighting for live performance is QLab4. QLab has always offered the option of using a custom patch from Quartz Composer to manipulate images. However, the requirement are as follows:

(Your custom composition must publish an input named "_protocolInput_Image" and an output named "_protocolOutput_Image".)

Bodysoulspirit's picture
Bodysoulspirit commented on Mechanica's Discussion, “Crashing Subcomposition

Mechanica

Vuo is Mac only for now, Linux and Windows versions are still on the roadmap.

If you got errors for Render Scene and Draggable Camera it should mean you're using Vuo 1.2.8, sorry, my uploaded version was for Vuo 2 beta.

Although I get no crash using your composition both in Vuo 1.2.8 or Vuo 2, I couldn't get the shader to work in Vuo 1.2.8 by quick testing. Going to work now, will check it later again, but even when you set a shader on the parent node, and feed a shader into the sub-composition for one of the cube sides, for me the sub-composition still says "no shader".
In Vuo 2, how the events flow through sub-compositions have changed, and there it works.

I switched the true / false input selector though in the sub-composition, as I understand you wanted to display a wireframe shader if no other shader is provided ? (see screenshot, all sides except front has color shader, front has wireframe)

Will check later

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.