cwilms-loyalist's picture

Chris (@cwilmsloyalist)


  • Vuo Founder
cwilms-loyalist's picture
Chris commented on Team Vuo's Feature Request, “Load and play animated 3D meshes

Not sure where you are getting that from Benedikt, as I understand it the Vuo Team is currently preparing one of the next releases to fully support compatibility with new Apple Silicon / ARM64 / M1 Macs, not just under Rosetta. They've added several new nodes and updates back in October and followed with a stability release just before Christmas. Vuo has often had longer waits between releases when they are implementing big new features or making core changes that require longer development cycles. The Vuo Team can speak better into this, but I see no reason to jump to the conclusion you made.

Update: (Some Vuo roadmap info - doesn't sound like "dead" at all to me, just a challenging update...

cwilms-loyalist's picture
Chris commented on jvolker's Feature Request, “Option to temporarily disable/turn off nodes

What if it were 2 nodes, one node would be for events only and the other could be a generic type?

It could look a little like the Select Event Output node, where there is an In port and 2 possible out Options. Along with the In port, there is also a Boolean Which port to choose which output (true or false) the node is passing through to. The only thing would be that it would have to block any events coming through the which port to not pass them on, only events coming through the In port would be passed on to whichever out Option it's currently toggled to.

It could act as a BlackHole when needed by not having anything connected to one of the out Options.

It might make sense to also add a "Changed" port so that it could be used to reset something in your composition whenever the out Option was toggled.

cwilms-loyalist's picture
Chris commented on Bodysoulspirit's Feature Request, “Code sign and notarize exported apps

I would like to see this too.