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.
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,
Dear commercial users of vvvv,
dear devvvvelopers of contributions
and of course everyone else,
we hope to interest you in the following:
a) Short Story
We have a store now! Well more of a store-front really, but nonetheless. Consider this a start.
Here is how it works:
Here you go: Store
As you all know, vvvv's business model is what others would call non-sustainable. It is a weird mix of being half-opensource and completely free for anyone to use without restrictions (how can you!?) unless their application is a commercial one, then pay! The whole model is based on an ancient social feature and we call it T.R.U.S.T We want to trust our customers as much as they have to trust in us. All nice and shiny, but does it work? Read for yourself.
Since the early days though, it was clear that the success of vvvv does not only stem from the fact that we're such genius programmers (citation needed!) but also from the fact that a lot of its users readily shared, first their patches and modules, later individual plugins and finally indispensable whole packs of nodes that extended the possibilities of vvvv enormously. And they did all that for free!
To at least symbolically support those developments and allow users to tip others, a few years ago we introduced a micropayment service called flattr. It was an experiment that pretty much failed, for different reasons I guess, not least because flattr itself still struggles to find its way...
Then of course the idea of a sorts of "appstore" for vvvv contributions always seemed obvious. We've had a few developers asking for it over the past years, not enough though to justify an investment in the fully-fledged webshop that was always requested. When recommended by us to run their own little webshop we got mostly two answers:
All comprehensible thoughts, but here is the rationale why we are not afraid of this and why we now finally take this first baby-step in creating the Store page, which for a start at least is a central place to promote commercial contributions. Also note that contributions vvvv-message, dx11.pointcloud and automata-ui already charged for commercial use for a while now, if you read the fine-print, so this is really mostly to endorse that practice:
First: Money has always been part of our community in two ways: vvvv itself costs money (for commercial use) and hopefully users who create patches for commercial jobs always charge a lot of money. So far many contributors who gave their valuable stuff for free probably did so because they knew they can get enough paid patching-gigs they enjoyed in turn, so it didn't worry them too much. But preferences change and in a good economy it should be possible to contribute in different ways. If someone doesn't want to do patching-gigs or at least not only, as they more enjoy creating and perfecting libraries, then this should also be possible to make a living from, in our community. And of course it should be obvious how this is to the benefit of all participants of the equation. Plugins/Libraries that so far have been left unpublished because of uncertainty regarding commercialization, now have a clear endorsement which can only strengthen the ecosystem of vvvv as a whole.
Second: Will using vvvv become more expensive overall? Using vvvv has primarily become more and more cheap over the years since we haven't changed its pricing in 15 years and computers can run more and more outputs from one license. So paying for additional commercial contributions will merely bring its costs up to a more realistic level.
Third: Will everyone now charge for all their contributions? We hope that with the T.R.U.S.T business model (as elaborated above) we can be a role model and convince contributors to join our experiment and also still give their stuff away for free for non-commercial use. Like this, not much would change for the casual user and even for the commercial user who quickly needs to test options. Only when buying a vvvv license users will also be asked to buy licenses for contributions they use. Still we won't enforce the T.R.U.S.T model.
So yes, there is still the obvious inconvenience for developers to handle their own licensing but at least we hope by promoting commercial contributions through the Store we don't hold anyone back who didn't dare to offer their contributions for money.
Let's see where this goes..
The ribbon is cut, welcome to the Store
previously on VL: vl-progress-report-4
the vivid blog reader already knows the drill: everything stays the same if you liked it just the way it was.
Specify remote host (IP address), a nice port number, connect some data and bang the send to let your UDP packets travel over the network. Or open a server to receive bytes arriving on the specified port. The only difference to vvvv you might see is, that here you also get infos about the sender of the packets via the Remote Endpoint output (which is an IP Address and a port)
same same for the TCP nodes: The client will try to connect to a server. And once the connection is established, you can send and receive bytes.
The TCP Server awaits incoming connections to talk to. The subtle difference here is the Tuple input, where you would expect the data pin. No one ever requested it, but now you can decide which packet should be sent to which client by specifying IP address and port together with the message. In case you still want to send the same packet to all of your clients, just set the address to 0.0.0.0 and port 0
so why did it take so long, what's the goodies behind that?
Unlike the monolithic networking nodes in vvvv you can peek inside the VL ones. The goal was modularizing on a much lower level to be able to provide the very basics as nodes for the patcher:
Who id144, maarja
When Thu, Jan 26th 2017 - 18:30 until Sat, Jan 28th 2017 - 16:00
Where Bartlett School of Architecture, 22 Gordon Street, London, United Kingdom
DUST aims to spark a dialogue between digital technology and performing arts, and transform the way people see and experience contemporary dance. It is produced by Carmen Salas, and supported by Arts Council of England and Rambert Dance Company.
There are 3 occasions to get to know more:
26 JAN 2017 6:30-9:00 PM @ Bartlett School of Architecture, London
PIxLS public lecture together with Memo Akten, Patricia Okenwa from New Movement Collective and Syuko Kato
27 JAN 2017 1:00 PM @ Pervasive Media Studio, Bristol
28 JAN 2017 1:00-04:00 PM @ Victoria and Albert Museum, London
anonymous user login