Blog-posts are sorted by the tags you see below. You can filter the listing by checking/unchecking individual tags. Doubleclick or Shift-click a tag to see only its entries. For more informations see: About the Blog.
Patchers of vvvv!
We've been meaning to share this with you for a while now. It bugs me that it took us so long, because we're using it internally for a few years already, but better late than never... And most of you will not even find it that exciting but everyone should understand that this is an essential thing to improve the stability of vvvv over time:
In order to prevent certain bugs from resurfacing again after they've been fixed, vvvv has a test framework. The framework consists of a couple of nodes and a simple template that test-patches have to follow to test for a specific known bug. Everytime the vvvv build-server creates a new alpha-vvvversion it also runs all available test-patches. If any of the test-patches fails, the build is not being released and the devvvvs are being informed about the problem.
By providing such a test-patch for bugs you find in nodes that come with vvvv or the addonpack you can help ensure that this particular bug will not resurface again after it has been fixed once.
Basically creating a test-patch is not more difficult than creating a help-patch. The Test Framework page explains everything in detail and of course please let us know if you have any questions.
Yes, our buildserver is also running test-patches for .vl already. We'll let you know how to contribute to those when we're opening up the contributions for VL libraries.
So from now on whenever you're writing a bug-report in the forum please consider demonstrating the bug with a test-patch in order to help us identify the problem quicker and also make sure to prevent it from resurfacing again through other seemingly unrelated changes.
previously on vvvv: vvvvhat happened in Jannuary 2017
and there it was already over, weird february..
in our quest to arrive at a more regular release cycle we gave you vvvv 50beta35.2 just about a week ago. it doesn't come with much new stuff but since it has a lot of little fixes it is definitely the version to use now.
vl is going strong. at least on our side. but also more and more of you are eager to get into it as we can see in related forum questions. the discussions there already proof to be valuable sources of knowledge, so we're collecting a few interesting ones for you here:
vvvv/vl skills are in high demand, so get your acts together and apply for one of these:
a few updated:
And quite a few more recent entries to our gallery. Keep them coming!
Anything to add? Please do so in the comments.
You asked for it. And we have heard you.
So we captured the last VVVVORKSHOP about VL hosted by Tonfilm and Elias and you can watch the Youtube-playlist here:
Tonfilm and Elias talked about VL in general and its advantages and guided step by step through a handfull of examples including topics like Loops in VL, Autonomous and Interactive Agents, Connect All, Delegates, VAudio in VL and a lot more.
And we've opened this forum thread for any VVVVORKSHOP II - Video Documentation related questions:
Happy binge watching!
We got more feedback on VL since beta35 and we are really really happy about that! It's true. True!
And since you know how much we dig VL, you will believe me, even though i did everything to sound silly. Besides, also some vvvv issues were reported.
While this is not meant to be the biggest release ever, we still took the chance, addressed some of them and dropped the improvements into a maintenance release, just to make sure to get back to a faster release cycle.
Besides all the fixes that actually make you want to use this release, here are some additional small features:
Irritainment feature and puzzle of the day "Partial Type Annotation":
Check out the Change Log below!
Have a lovvvvely day, yours devs
EDIT: this is a hot fix for beta35.1, thanks eps for reporting, sorry for the inconvenience.
EDIT: this replaces the 35.1 release
It's been a little while again, but here it is, new Directx11 version.
There are many changes around, so I'm not too sure where to start.
First thing, versioning has been updated, no more alpha/beta, that joke about "software is always beta" made it's time, but as we say, shortest jokes are the best, and for many users that sounds pointless and confusing, so now build is adopting a more formal version naming eg : release, with beta and alpha being used for in between releases.
Second thing, build system has been reworked and now uses a build server, which allows direct update to git releases, so users who want to try out early releases can do so much more conveniently viahttps://github.com/mrvux/dx11-vvvv/releases
No more need to build the pre releases yourself.
This also means that users can expect more frequent releases.
Second thing was in the list for a long time, interface has been changed (basically
IDX11ResourceProvider and friends have been replaced by IDX11ResourceHost version and friends. Removing IPluginIO is necessary as it creates some major issues going forward (and never got used anywhere inb the codebase anyway).
For this release ResourceProvider is working alongside Host (it is now marked as deprecated and will be removed from git version pretty much as soon as I finished this post.
Sadly, LayerProvider could not be made to work alongside Host version, so those have been removed already. From what I know there's no custom plugins using it (or they already move to new interface), so on a user perspective there should be no transition issue.
As usual, I think I should have a ready to paste version, and maybe an auto bot to reply in forums, bugs are to be submitted herehttps://github.com/mrvux/dx11-vvvv/issues
Ok now let's go past those (boring) announcements details and go through what every user wants eg : What's new (and download obviously)
New Nodes (or new options in node):
Lot of new examples and help patches (20+ from Assimp, Semantics...)
So for users who did read all and did not scroll hear (or just skipped and went straight into contribution page):
previously on vvvv: vvvvhat happened in December 2016
...and already 1/12 of 2017 has passed, but not idle! we first gave you the numbers of 2016 and then opened the store. devvvv-whise you got an intro to networking and async patching with vl and an outlook on the road ahead plus our first 3 video-tutorials to get you started with vl:
in latest alphas you can also already enjoy these new gems:
and then there've been a range of interesting forum-threads that got nice solutions with VL:
|3 new:||7 updates:|
for years this was high up on the wishlist of many vvvv users: a node that would play back HAP video files. and suddenly there are two solutions on the horizon:
must-watch of the month was the projections for the opening of the elbhilharmonie in hamburg with contributions by vvvv allstars schnellebuntebilder, quadrature, intolight, madhat and lasal. here is a good video summary of the event.
Anything to add? Please do so in the comments.
And have a happy new patch!
Who Sabrina Verhage and Carolien Teunisse
When Sun, Feb 19th 2017 - 12:00 until Sun, Feb 19th 2017 - 17:00
Where FIBER, Tolhuisweg 2, 1031 CL, Amsterdam, Netherlands
Spread the word: Creative Coding Amsterdam is teaming up with Creative Coding Utrecht to share knowledge!
Sabrina Verhage and Carolien Teunisse will teach the basics of vvvv in a sunday afternoon on the 19th of February.
Who schnellebuntebilder, tonfilm, elias
When Sat, Feb 11th 2017 - 12:00 until Sat, Feb 11th 2017 - 18:00
Where schnellebuntebilder, Rudolfstr. 11, Berlin, Germany
Our vvvvorkshop series will continue.
This second session will be aimed at beginners - in VL.
Yes, you read it right, this time we will dive into the next level of visual programming. Tonfilm and Elias are so kind to guide us through all kinds of object oriented spreading strategies and will teach us new ways of solving common patching problems.
What do you need to bring?
There will be a fee of 20,00 € per attendee to pay for the room, we are booking for this workshop.
If you consider yourself a professional patcher or your company sends you here to become one, we use T.R.U.S.T here to encourage you to ask for a professional fee which is 200,00 €.
TIME 12am - 6pm (resp. beer o’ clock)
LOCATION Berlin, Rudolfstraße 11 - Friedrichshain
Please sign up here:
previously on devvvvlopment: vl-networking-and-async
With beta35 (including VL) out in the wild and people apparently starting to use it (see forum threads about it) we're quite happy with the feedback so far. We know of people already including VL in their daily patching and getting the hang of it. Others are still more cautious and are waiting for better documentation or are hoping for node17 to open their eyes. All fair enough, no pressure.. in any case the question is of course:
One of the many aspects that vl will be different when compared to vvvv is its node-library. In vvvv we have a closed-source base-library (written in delphi and closely bound to the vvvv core) plus a wide range of open-source nodes including community contributions (written in c# via a plugin-interface). For vl we'll still distinguish between a base-library and the rest, but all libraries will work the same way, ie not be bound to the core. And not even need a plugininterface. And be open-source.
So from the beginning in vl we separated core from libraries and already have a git-repository including all of VLs libraries organized in neat packages (as you can basically already see in your beta35\lib\packs) that we're ready to open. Why haven't we done so already? Well, by releasing library source-code we're kind of committing to a style that everyone should be able to use to write nodes for vl. Therefore this is really a crucial part that we simply wanted to give a second look.
Remember when at node15 we teased how to define nodes for vl? Everything already felt fairly simple indeed. The typeimporter, a breeze. As mentioned in previous blog-posts we've been continuously importing libraries ourselves since then and noted a few things that we needed to improve to make the workflow for future library developers even more convenient.
So this is what we're reworking at the moment and what we hope to be releasing soon:
This will reduce the barrier for developers enormously because everything they have to do to contribute to the vl nodelibrary, will be very little vl-specific and very close to what any c#/.net developer is doing anyway.
Other than that our focus until node17 will continue to be the integration of vl with vvvv, improving documentation and adding the one or other smaller feature. So, that at node17 we have a strong foundation to teach on and hopefully even already some new, contributed libraries..
Until the next update,
anonymous user login