Who a a a a, sebl, joreg, david
When Wed, Aug 8th 2018 until Sun, Aug 12th 2018
Where Grüne Hütte, Brandenburg, Germany, Germany

Good News Evvvveryone!

The number of applicants to LINK has not exceeded 25 yet. So since we have a few spots left,
we're hereby extending the call for applications until May 31st!
____
So if you were in doubt if this thing is the right thing for you, let us try again to get you convinced and interested: LINK is a summer camp open for evvvveryone. A quality place and time for your projects on, with and for vvvv/vl. From patching or coding research projects, community & diversity building projects or software and usage concepts, design and development what comes to your mind that you think is needed or missing in the vvvv community. Anything goes and like always, evvvveryone is welcome! users, patchers, developers, thinkers, beginners, experts of any age.

Only be quick to apply because if in doubt we might sort to a first-come first-serve order of accepting your applications...

For all information and application, see:http://link-summercamp.de/
for any questions, please don't hesitate to write us to post@link-summercamp.de

Looking forward to your hot patches,

Greetings from the summer camp team:
ann-katrin, david, joreg, julia, laura, sebl

helo teachers, tutors and students,

we'd like to assemble a list of your educational institutions that teach vvvv in order to:

• give people interested in vvvv an overview of opportunities
• be able to reach you with information about courses and workshops that could be interesting to students

for 7 years (i just checked my notes) we planned to build a system into the website (similar to the businesses) where you could manage your own little profile of your institution. apparently that didn't happen...so let's try it the oldschool way. there are two ways to add your institution:

• go modify the wiki-page Educational Institutions yourself
• or send us an email to edu at vvvv.org and we'll fiddle with the wiki for you

in case you send an email please include the following information:

• name of institution
• website
• country, city
• notes
• contact (can simply be your username on vvvv.org or a link to a page at the institution with further information)

to give you an idea how the information will be presented, see this example:

whenever you have an update, simply modify the wiki-page or send us another email. we'll also periodically send out an email to ask you to confirm your information is still valid, to keep the list up-to-date.

so if you're a teacher, please send us your information, if you're a student please ask your teacher to do so. if you know someone who should be on the list, please let them know about this.

thanks for spreading the word!

Or microdee's keynode aka long article about what's going on aka "oh no microdee's hyping his own stuff again".

Hi all!
Since September in my freetime I've been working on major refactoring of my packs to be more accessible and more organized and also writing more documentation, help patches and more understandable girlpower while also improving on features and fixing bugs. This all started with unifying semantics and pipelines in mp.fxh and mp.dx shaders but because of my slight bipolarity I've finished a lot of things since then except that. So there are still some inconsistencies on that side and the fate/direction of the rendering part is still hanging up in the air (that PBRBase thing and the Disney shading). I'm a single person on this so it'll take some time.

Meanwhile I've started to make my C# backends 99% independent from VVVV*, started to properly build them on Appveyor and properly publish them automatically to Nuget. The first materialized result of this is md.stdl (microdee's standard library) which is a collection of some common functionalities used often during development (sort of like the VVVV.Utils library, just on my own). More and more features will be ported from mp.essentials nodes to md.stdl. An exciting side-effect of this that md.stdl can be inherently used in VL by its magnificent Nuget support (though I didn't have the arriving to test it properly yet).

• currently md.stdl still depends on VVVV.Utils with Mouse and Keyboard devices. All it does though that it provides some classes to act like the Desktop Mouse and Keyboard nodes. Also provides interoperability extension methods for VMath vectors and System.Numerics vectors.

Another library, which was separate, then merged into mp.essentials, then grown out of mp.essentials again but this time properly and has its own Nuget now: is mp.pddn (mcropack pin dictionary dynamic node) which is an extension library for creating VVVV nodes with highly dynamic pin management. One of the direct results of this were the introduction of the truly generic VVVV node pattern in mp.essentials and Notuiv (see below) where you can still be type-safe but can manage any type with a single node without the need for VL or C# code.

Meanwhile I've joined the forces of MESO and priorities slightly shifted for me from graphics to re-usable subsystems (of course while directly developing projects). The first bigger realization of this shift became:

₪i or Notui by MESO

VVVV is used to create large scale user interfaces a lot. Anything requires a screen and user interaction VVVV scales in size like no other package does from lot's of tiny screens to huge LED walls the size of a building (or your mom), VVVV can handle that with breeze. Except any professional will know that developing UI logic which people are taking as granted from browsers or smartphones are painful to develop in VVVV's dataflow environment. The shear presence of overlapping UI elements can make your brain explode in pure VVVV. In the past I had several attempts to solve it and they all failed for various reasons (khmvobjectskhm khmvoogkhm). Those shalt be forgotteth and shalt be never spoketh thereof. Learning from those mistakes, and still repeatedly fighting with the above mentioned incomprehensible logic cobwebs suffering from deadline induced chaos and doom, I came up with Notui.

Notui is a UI behavior package written entirely in C# providing a robust skeleton for your UI elements. The intention here was to keep VVVV's vast drawing capabilities while eliminating the above mentioned horror with logic. The result is a mostly dataflow friendly system which separates structure, stateful-logic and rendering. Note also that Notui is a C# library first and Notuiv is its VVVV implementation. This again means all the features of Notui theoretically can be accessed in VL and simply fetched from Nuget.org. This also means that you can patch your own element types and behavior delegates in VL, but I'm ahead of myself.

I hear you saying "Yeah, yeah tl;dr, big words, etcetra etcetra, What are its features?"
For a quick demonstration this can be your typical Notuiv app structure, greatly simplified though (one of the girlpower examples):

Which yields this result:

Expand that patch to see how simple it is to set up this 2 draggable windows with stateful content and animated declarative transitions patched 100% in VVVV with Notuiv:

Read the complete list of features and download on the contrib page: Notuiv
Now at MESO we decided to release Notui and Notuiv as BSD 3-Clause open-source libraries. Which also allows you to use it in your own commercial project without any hassle or royalty whatsoever. So grab the sources here:

https://github.com/meso-unimpressed/Notui
https://github.com/meso-unimpressed/Notuiv

An elephant in the room: "But have you heard of CraftLie?"

CraftLie is super great and tonfilm even created pure C# VL.UI.CraftLie https://github.com/tebjan/VL.UI.CraftLie which at first glance does very similar things as Notui. Unfortunately though the scope is quite different. But nothing stops you to combine CraftLie and its UI thing, VL and Notui to have a powerful system, if you install Notui into VL through Nuget, or just reference Notui.dll from vvvv/packs/Notuiv/nodes/plugins folder. This is kind of untested area yet, so please give me feedback how it went.

Side note: Now for those who want to use Notui outside of VVVV don't get fooled or intimidated by the lines of code count of Notuiv implementation, that amount of boilerplate code is not a Notui specific phenomena . It's an inherent structural issue with how VVVV works. It's a general rule of thumb that if you want to implement a large library solving a big set of problems in a very modular way with lot's of information on their building blocks, VVVV's plugin interfaces requires thousands if not ten-thousands of lines boilerplate to deal with all the conditions a plugin can have. This is 100% solved in VL though.
Disclaimer on the logo: Notui have nothing to do with Israel's new shequel. That symbol just looks great and resembles an 'n' and a 'u' interlocked, throw in an 'i' and you'll get Notui \o/. But if anybody feels offended by this for any serious reason (like if an Israeli person really feel like their national currency symbol is being abused by random UI libraries for simply aesthetic reasons which has nothing to do with it, or with Israel) I'll immediately change it.

A bit more on md.ecosystem

Almost forgot you can get mp.essentials and mp.dx from here: md.ecosystem
or through Github releases:
https://github.com/microdee/mp.essentials/releases
https://github.com/microdee/mp.dx/releases

There are couple of smaller important thoughts as well:

First: FBX4V will be open-sourced soon and will become part of mp.dx, and maybe I'll find some time to fix some crucial issues with it during the process.

Second: the refactoring also ended up in a more modern way of deploying my packs. (like how Velcrome's messages and Vux's DX11 packs are doing for ages. All md.ecosystem packs are still available from vpm, but their binaries are finally not stored directly in their repo, and they are available from Github releases for those who are not happy with vpm. vpm itself will be revisited soon as I need to sort out couple of things to fit more into automatic deployment schemes. Also finally because of Appveyor they're all generating version.info files now and also they have About nodes with detailed versioning info too.

2.5th: During this transition I'm also creating nice and tidy help patches with lot's of reading materials where it's suitable and the node has a decently isolated function. So hopefully it will result in less confused patchers.

Third: A reminder that all of my stuffs are open-source on Github, one can easily fork it and send me pull-requests. Yet I can count on a single hand the number of occurrences this happened. If there's no active project with a deadline MESO embraces open source development which can help faster realization of future projects (the reason you have Notui now) so funding wise I'm ok, BUT I'm a single guy maintaining this entire thing, so if you're bored and can do vvvv patching you'll make me the happiest guy on earth if you send me pull requests to my repos fixing minor issues I haven't noticed or improving on my crappy code/patch.

Thank you for reading this through, I hope my packs provide you as much productivity as they do for me. If you have any questions I usually answer them.

Cheers and happy patching!

Welcome dear patchers to a new episode of devvvvs giving you control over your PC mainboard.

When you work in vvvv or VL the evaluation of your patch is automatically driven by a mainloop. It executes the nodes in your patch (usually) 60 times per second and by this allows changes to happen in your patch over time.

If you have a look at the PerfMeter in a renderer with a mainloop timer without any tweaks you will see lots of flickering like this:

Those flickers indicate that the time between two frames of the mainloop is changing a bit every frame. In an ideal world those flickers would not be there and the time between two frames would always be the same. An unstable mainloop like this creates jitter in animations, drops video frames and lets the visual output of your patch look less smooth.

It's quite a difficult task to get high-precision timer events on a modern computer architecture. Timers and me go way back to the early vvvv days at MESO when i worked on the vvvv mainloop and the Filtered time mode. Since then we could improve the vvvv mainloop time stability quite a bit by doing tricks like changing the windows system timer resolution and introducing a short busy wait phase at the end of the mainloop. The result of this work looks like this:

The experience gathered from the vvvv mainloop improvements is now available in the VL library, so you can build your own sub-mainloops.

But why would you need your own timer at all if you have a good mainloop already? There are a few reasons:

• Have a second mainloop on a different thread to split performance or don't block the mainloop
• Process something at a slower rate as the mainloop to save performance, e.g. web requests every few seconds
• Process something at a higher rate as the mainloop, e.g. output to a micro controller or servo motor
• Run parts of your patch in it's own mainloop to avoid blocking user input from vvvv

General Node Design

In VL the patch of a process node by default has a Create and an Update operation. Create gets called once an instance of the process is created and Update gets called periodically by the mainloop. In this process node patch you can place other process nodes that 'plug into' those two operations by placing their own Create on the Create of the surrounding patch and their Update on the Update of the surrounding patch.

This is the same for stateful regions like ForEach [Reactive], only that the Update of the ForEach region doesn't get called automatically by the surrounding patch but gets called by the events of the incoming observable. More on that in this blog post: VL: Reactive Programming

There are many sources of observable events. For example Mouse, Keyboard and other input devices as well as AsyncTask or MidiIn. The timer nodes work in the same way. The output is an Observable that is on a new thread and either sends the frame number (for the system timer nodes) or a TimerClock (for the MultimediaTimer or BusyWaitTimer). A patch would look like this:

The use of observables also makes it easy to swap one timer for another if neccessary.

Basically there are 3 ways to setup timers in windows and now VL has them all!

System Timer

This is the most common timer but it usually only has a precision of 16ms. It can be used for recurring events when accuracy is not the most important issue and the interval is in the seconds range or a higher millisecond range. Nodes that use these timers are for example Interval and Timer in category Reactive:

Multimedia Timer

This is a dedicated timer for applications that do video or midi event playback. It is fairly accurate to about 1ms and doesn't need much CPU power. So it can be used for most time critical scenarios. To use this timer, make sure you enable the Experimental button in the VL node browser and create the node MultimediaTimer:

So that's nice, but it has two little draw backs. You can only specify the period in whole milliseconds and as you can see there is still some flickering in the measured period times. The flickering is well below 1ms but still, we can improve that:

Busy Wait Timer

Since its possible to measure time with high accuracy, one can write an infinite loop that always checks the time and executes an event once the specified interval time has passed. This timer always uses 100% of one CPU core because it checks time as often as it can. But hey, how many cores do you have these days? With this method you can achieve precision in the micro second range, which is insane!

If any patch processing is happening on the timer event, the power of your core is of course shared with the busy wait. Just make sure that the processing doesn't take longer as the specified period:

This timer has an option to reduce CPU load for period times that are higher than the accuracy of your system timer. You can specify a time span called Wait Accuracy. This is a time span before the desired end of the period that specifies when the busy wait phase should start. Before that time the timer is set to sleep for 1ms periodically. 16ms is a safe value, but you can decrease it until the Last Period starts to jump in order to reduce CPU load even more.

Threading

Both the MultimediaTimer and the BusyWaitTimer start their own background thread with priority AboveNormal. The thread priority setting might become an input pin in the future.

So now download latest alpha, enable the Experimental button in the VL node browser and give it a shot. If anything unexpected happens, let us know in the forums.

yours,
devvvvs