Hi I edited this bug report because it's apparently due to bad module(s) in the user/library/applicationsupport/vuo/modules folder. I removed that folder and it opens ok. So... I guess the thing would be to modify the next version of Vuo so that it doesn't crash but instead blocks the bad nodes and gives a useful error message.
This is a composition created for use in Resolume (etc) as an FFGL plug. It's designed to be used on a channel with a moving image and a lot of clear space (ie zero opacity). The feedback fills up in the clear space and then is automatically masked so that it has a "decay" and you can still see any background layers beneath.
I'd love some feedback (ha). I suspect this qualifies as a thoroughly noob composition. I'm sure there must be simpler ways of doing this.
●○○○ — Not much; I'm just letting you know about it.
Steps causing the bug to occur:
Open a composition that contains both uninstalled nodes (here a sub composition, don't know about real Vuo modules/nodes) + 3rd party nodes that have not been updated for Vuo 2.0
Not able to click ok, or cancel, or close or quit the Vuo Editor, you have to Force Quit it
Create a text layer with revealing characters (cut text increasing)
Align it for example left to the window
Notice how as characters are revealed, the layer moves (see joined video & composition in the .zip)
Could this have anything to do with pixel alignement ? This video was captured on a non-retina screen.
Which lead me to question 2, could or should I create a feature request (would it make sense) to optionally enable / disable pixel alignment for "Make Text Layer"?
Because for scrolling very big text sizes, Jaymie's fix to use Make Text Image instead, result in huge image sizes (can even outsize the max image width) (see topic Simple text scrolling is not consistent or smooth)
I wonder though for what hardware range / year this request would be useful for though, since Kewl on that topic noticed the composition I shared there ran smoothly on his hardware
