vvvv_50beta37September 5, 2018
This release comes with a cleaned up VL core library. We also made sure that the node set feels more explorable just by making basic nodes more visible than others. Advanced, *experimental * or obsolete nodes now don’t hide in different packages but can be opted into the list of nodes, while browsing the library.
But this release also comes with features for you to clean up. Frames help to structure VL patches in a visual way, groups, and categories in a structural way. You even can tweak the visibility of your nodes in the node browser and by that distinguish rather advanced or still experimental nodes from the daily node set. Library developers will also love the feature to make certain helper nodes internal so that they are free to change or delete them at any time in the future.
A lighter VL
Less VL documents get opened by default, leading to a faster startup and making the navigation menu more meaningful. Less “.Net Packages” get shipped leading to a smaller download and a lighter “.Net Packages” dependency menu. Process nodes now are lighter in terms of memory allocation.
Entry points and document management
We introduce a new way of making a VL patch run. Up to now you always had to drop a VL node into vvvv to make it actually run. Now you can define an “entry point” in VL, leading to one running instance of that patch.
This is the first release that supports the VL.Skia library. It comes with a huge stack of example patches.
Debugging should feel much more intuitive, as it now allows to inspect the exact state of the patches for the moment when something went wrong.
Baby, don’t make me spell it out for you
All in all this release makes VL easier to learn, use and develop for.