I am the Senior AV Broadcast Technology Analyst at Loyalist College where I primarily design, install and maintain campus AV, Digital Signage and Broadcast systems and equipment. I have also do some teaching for Camera, VFX and Audio/Video editing as well; I love my job. My background includes Broadcast Television, Video Production and Technical work. My passions include traditional and digital drawing, fictional creative writing, VFX, and cinematic video projects. I have also recently rekindled my interest in robotics and have tinkered with Arduino and Raspberry Pi and a few programable robots.
I find I most comfortably find myself in the chaotic limbo between the artistically and technically creative, believing one can indeed excel at both. Which is probably why I am loving VUO! :)
@Jaymie, It's a little different than I was thinking, the Blender video link shows pretty much how I was thinking it could work. Functionally I guess the two methods might be the same. Will a composition-local sub composition like that also be precompiled the way a regular sub-composition is? If so, there is a potential performance improvement doing it your way over the way I was thinking.
I think my main concern with sub compositions stems from my experience so far with them. I've found they sometimes don't work how I think they are going to work. For instance I will take a specific set of nodes out of a working composition, make them into a sub composition and publish all the inputs and outputs I need to use, place my newly created sub-composition back in my main composition and it won't work anymore. However if I copy those same set of nodes and place them back in the main composition and reconnect them functionality returns. (Either I'm not understanding how they work or it may have something to do with how events flow... https://vuo.org/node/1281). I guess I was thinking that grouping a set of nodes the way Blender does it would be a simpler procedure than the process of making a sub composition and things would continue to work the way I expected them to.
Ideally the way I would LOVE to see it work would be to group them the way I was suggesting and once things are working correctly you could right click the group and save that as a sub-composition that could be also used in other projects. Maybe a right click menu with "Save Group as Sub-composition" and "Save and Replace Group as Sub-composition".
Yes the "Chosen to be implemented" Status is great and appreciated information!
I was thinking though that some of those features are much longer term projects and that a short list just to identify which of those items are planned for the next immediate release would be helpful, both for current users and potential users. I understand that sometimes it may not be clear whether a feature will be ready in time for an upcoming release but that the list just shows the features that are pretty much a sure thing. I'm sure everyone still like the occasional surprise slipped into the next releases too. :)
I realize not all of the "Chosen to be Implemented" features have an exact schedule for which release they will arrive in but I was wondering once you know for sure which features are coming in the next release could they be added to a "Coming Soon..." or "Coming in Next Release" section under the Released tab? We're alway happy with surprise features being snuck in too but I often find myself scouring the Feature Request list to see if there is a solution coming solve a problem I'm running into. Then if it's not there I know I need to go vote on something. :)