vvvv_50beta38

November 20, 2018 posted by: Elias

Surprise!

Another release just out of the gray only 2.5 months after the previous. How come?

The last beta37 release proofed to be quite stable, hardly any too concerning bug reports, but we have a breaking change to introduce and think this is a good moment. Hear us out:

If you’re a vvvv-only user, you’re safe. This release only has minor changes compared to beta37, so there shouldn’t be any reason for you not to upgrade. Horray!

If you’re also using VL, we’re afraid, but swallow this:

Since there are hardly any other changes, we recommend you also switch as soon as possible and never look back…

So why the breaking change?

It’s about how values get stored in IO boxes and pins. They now use the same serialization technique we already introduced as a node set for beta37. This means that we can store any data inside patches for which a serializer is registered - be it a spread of values, a dictionary or even a custom record: A spread of values in b37 and b38

And as a second example a dictionary from string to value

A dictionary of values in b37 and b37

It might not look as much yet but it is a first step to get proper IO boxes back.

So apart from that another worth mentioning improvement is a new short cut called Ctrl+K which creates pins for the selected pads and puts them on the Create and Split operations of the containing patch Ctrk+K

All other changes can be found the as usual in the Changelog.

Yours, devvvvs.

Download


Comments:

Comments are no longer accepted for this post.

velcrome
23.11.2018 - 01:02

cool for the auto-init/split and all, also looking forward for the progress you’ve made with xenko.

but the backwards-incompatibility is a shame. especially because I don’t get why going from “single-value” to “single-value-or-many-values-or-xml” would stop parsing the old version.

I hope you find a way to mitigate that, maybe provide a converter of some sort. Not being able to upgrade any vl project is a slam in the face.

tonfilm
23.11.2018 - 04:20

@velcrome it sounds like you think you cannot open your old projects with beta38, but its the other way around: if you save a vl document with the new beta38 you cannot read it anymore with beta37, so all older vl documents open just fine with beta38 and since there is almost no other change it should be a no brainer.

velcrome
23.11.2018 - 13:33
ok, so only as usual. must have misread that, never mind then.
joreg
24.11.2018 - 15:03
no! usually there are no breaking changes from one release to the next. ie. usually you can open documents saved with a new version still with an older version. we take a lot of care to not cause such troubles. in the rare cases it happens, we are extra explicit about it (like above) so everyone knows and can prepare. hope this clarifies.

Contact


Imprint

vvvv - Dießl & Gregor GbR
Oranienstrasse 10
10997 Berlin/Germany
VAT: DE275566955

groupӘvvvv.org

Follow us

Mastodon.social
Github
Vimeo
Youtube

Sign up for our Newsletter

Your subscription could not be saved. Please try again.
Your subscription has been successful.