» vvvv_50beta38
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

vvvv_50beta38

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:

.vl documents saved with beta38 are not backwards compatible with beta37!

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.

Elias, Tuesday, Nov 20th 2018 Digg | Tweet | Delicious 4 comments  
velcrome 23/11/2018 - 02: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 - 05:20
velcrome said
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.

@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 - 14:33

ok, so only as usual. must have misread that, never mind then.

joreg 24/11/2018 - 16:03
velcrome said
ok, so only as usual.

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.

  • 1

anonymous user login

Shoutbox

~12h ago

~3d ago

joreg: Two #vvvv workshops this week in #berlin: Friday: Physical Computing, Saturday: Computer Vision. Tickets: upcoming-full-day-vvvv-gamma-workshops-in-berlin

~3d ago

joreg: @cznickesz also feel free to join our chat for such questions: chat

~3d ago

cznickesz: @joreg: Yeah, I´ll give it a try! Thx

~3d ago

joreg: @cznickesz: we're hoping this week. but depends on feedback. please test your project and let us know if it works.

~3d ago

cznickesz: @joreg: I should stop asking my questions so cryptic ;-) So right away: is final Beta39 hours, days or weeks away?

~3d ago

joreg: @cznickesz: the idea of an RC is exactly to make sure your projects will work with it. your last chance to report problems with b39.

~3d ago

cznickesz: So how "RC" is the "RC3"? I have to update an old project soon and I´m wondering if I should wait and directly update to Beta39

~4d ago

joreg: @takuma, the "one frame" issue was fixed in RC3 for beta39, see: beta39-release-candidate

~4d ago

Takuma: @joreg thank!! Ill try this. Are there a way to send video texture from vvvv to vl? fromimage node in vl somehow only sends 1 frame