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

Blog

new post

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.

  reset tags

addon-release core-release date devvvv gallery news screenshot stuff
delicious flickr vimeo
Order by post date popularity

bonjourbonjour,

Following tests from a few months ago regarding publishing your shiny VL nugets with Github Actions, we now have a dedicated action ready to be used!

Nuget what?

For more informations on nugets, please refer to this section of the Gray Book.

Github what?

Github actions are small scripts with a specific purpose, allowing you to automate tasks on your repos. They are actually the building blocks of what's called a workflow : you chain several actions one after the other in your own small script, and decide under which condition the workflow is triggered (a new commit on master, a new tag, etc).

There are already tons of actions allowing you to do all sorts of things from creating issues to running unit tests, and even make phone calls with a predefined text!

The PublishVLNuget action

This action allows you to easily do the following tasks :

  • Build your Visual Studio solution, if your plugin has one
  • Download a package icon from an external url if you don't want to commit it to your repos every time
  • Pack your nuget either using a nuspec or a csproj file
  • Publish it to nuget.org (or any other feed)

In other words, you just have to push your code/patches and nuspec to github, and the script takes care of bringing it to nuget.org for you.

You can find the list of input parameters the action expects here.

How do I setup a workflow?

To get started with workflows, head over to the Github documentation.

Use cases

The action can adapt to many different scenarios. Let's cover three cases so you get an idea of how the action works, and how to adapt it to your needs.

My plugin does not have a visual studio solution

So your plugin solely consists of one (or many) VL documents and some help patches, plus your nuspec file that describes how your package will be structured.

(...) 
     - name: Publish VL Nuget
       uses: vvvv/PublishVLNuget@1.0.28
       with:
         nuspec: deployment/VL.MyPlugin.nuspec
         nuget-key: ${{ secrets.NUGET_KEY }}

Here, we are just using the nuspec and nuget-key inputs of the action.

My project has a Visual Studio solution and no nuspec file

Your csproj file can also describe how your nuget will be packed. In that case, simply omit the nuspec input. Note that if you provide a nuspec file anyway, it will take priority over your csproj.

I want to push to another nuget feed

By default, the action will push your package to nuget.org. You can simply use the nuget-feed input to push to a different feed.

Regarding external icons

I want to use an external icon, and my plugin has a nuspec file

The icon must be downloaded to an existing folder in your repo. We suggest you simply download it to its root :

(...)
- name: Publish VL Nuget
    uses: vvvv/PublishVLNuget@1.0.28
    with:
    (...)
    icon-src: https://wwww.url.to/nugeticon.png
    icon-dst: ./nugeticon.png
Paths in the workflow file are relative to the root of the repo!

Here, we ask the Github Action to download the icon from our URL and place it at the root of the repo.

Then, in the file section, your nuspec file must reference it from where the action will download it (src attribute) and place it wherever you like (target attribute), making sure target matches where the metadata section expects it.

(...)
    <metadata>
        (...)
        <icon>icon\nugeticon.png</icon>
    </metadata>
    <files>
        (...)
        <file src="..\nugeticon.png" target="icon\">
    </files>
(...)
Paths in the nuspec file are relative to where the file itself is placed!

I want to use an external icon and my plugin does not have a nuspec file

You can setup an icon for your project inside Visual Studio. The tricky part here is that you'll have to specify a path to a file that does not exist yet, since the Action will take care of downloading it later on. This can feel weird since Visual Studio's UI gives your a Browse button for you to pick a file. Simply fill the path manually to match the icon-src property of your workflow file.

For instance, your workflow file would look like this:

(...)
- name: Publish VL Nuget
    uses: vvvv/PublishVLNuget@1.0.28
    with:
    csproj: src\Whatever\Whatever.csproj
    icon-src: https://wwww.url.to/nugeticon.png
    icon-dst: ./deployment/nugeticon.png
    nuget-key: ${{ secrets.NUGET_KEY }}

and your VS package settings :

Thanks for reading, hope you'll enjoy using this one! If you are stuck or want more precision, don't hesitate to shout in the comments or in the forums.

Cheeeerz

sebescudie, Friday, Sep 25th 2020 Digg | Tweet | Delicious 0 comments  

Hello everyone,

Introduction

I'd like to give you an update on the toolkit front, that vvvv has always been. While vvvv beta can be described as a dynamic system, mutating while you mold your patches, vvvv gamma and its workhorse VL are of a different kind. With VL we embraced features like

  • static typing with its ability to detect errors early,
  • .Net DLL import opening a universe of possibilities,
  • user-defined data types that interplay with those defined by others,
  • compilation with its ability to export an app as an executable...

In short, we embraced robust software developing strategies that at first seem to contradict the idea of a playful development toolkit that allows you to mold your app. We went for compiled patches, running, and hot-swapping them while you are building them.

But we envisioned vvvv to be both

  • the playful toolkit you fell in love with
  • combined with the promises of a compiled language

While my last blog post was about the language, let's focus on the toolkit this time.

Toolkit

Let's have a look at some features that allow you to interact with the VL runtime, the system that runs your patch while it allows you to edit it. The features here empower you to enrich the patching experience. We understand that these improvements need to "trickle up" into the libraries and only thereafter will have an effect for all users.

So the following is probably mostly interesting for advanced user and library developers.

Tracking Selection within the Patch Editor

You now can react to a selection within the patch editor. The more libraries do this the more playful the environment gets. We still have to figure out all the use cases, but here is a list of what's possible already

  • separate the core functionality from its Editor UI. Imagine a TimeLine node that is decoupled from the timeline editor.
  • an Inspector for nodes or pads
  • a Preview like this:
preview nodes
  • even the help browser itself uses the feature to provide help for the selected node.

And there is more:
You can get a Live Element for a certain Pin or Pad.

  • Copy the permanent identity of the element into the clipboard by CTRL-SHIFT-I (I stands for Identity).
  • GetLiveDataHubForSerializedID hands you the pin or pad.

useful for the cases where you want to always inspect a specific pin or pad of some patch. This can be helpful for debugging.

Let the Patch Editor navigate to a Patch

When a Skia Renderer is your active window, Ctrl-^ let's you jump to the patch in which it is used. This is handy when you opened a bunch of help patches and you want to see the help patch that is responsible for the output.

You can use the node ShowPatchOfNode to do the same trick.

Tooltips for your own data type

Here you can see a custom tooltip for a user patched type "Person".

A european

You now can patch your own tooltip with RegisterViewer. This way the patching experience will be so much more fun. We're in the process of adding more and more viewers for our types.

Runtime Warnings

Up to now, we had

  • Red elements: Static errors. (E.g. a node that can't be found) These errors make the compiler ignore certain parts in your program as they are currently in development. The rest still runs. (Something what C# and others just can't)
  • Orange socks on links: Static warnings, potential problems. Something to look at when searching for a bug.
  • Pink nodes: Runtime Errors. A problem that only got detected during runtime and which is such a big problem suddenly that the system can't work as planned. Some patches don't run as planned. There are different ways how to handle these, pointing you at problems at runtime, but they can be painful.

And now we introduce to you:

  • Orange nodes, Runtime Warnings: They show you a problem at runtime. But it doesn't harm your system as pink nodes do. Orange nodes are runtime warnings. Library developers can put warnings on their nodes in order to communicate to the user that something is slightly off.

You can try it yourself by using the Warn or the Warn (Reactive) node.

just a reminder

The warning will not only show up on the Warn node, but also on the applications of your patch.

S&R nodes

Sometimes it's just convenient to be able to send data from one patch to another without the need of feeding the data via pins. We now have send and receive nodes, like known from beta.
Features:

  • The channel can be anything. It doesn't have to be a string.
  • They have several warnings. E.g. for when none or many senders are on a channel that a receiver is listening to.

Descriptive Tree patching

Some libraries focus on a simple idea:
Let the user build an object graph that describes what he wants in a declarative manner and the library will do the hard work to follow that description.

a tree

Examples for this approach are

  • VL.Stride
  • VL.Elementa
  • to some extend VL.Skia

VL.Stride and VL.Elementa have in common that they focus on a very certain type of object graph: A tree made out of entities and components.
Libraries like these can now talk to the user and enforce the user to not build any kind of graph, but a tree-shaped graph (where one child doesn't have many parents).

VL.Stride uses TreeNodeParentManagers, Warn nodes and S&R nodes internally to the deliver this feature:

no tree. we get a runtime warning

You'll very soon be able to inspect those patches.

Help patches to all those topics will show up in the CoreLib API section (at the bottom of the listing).

We hope you'll enjoy these ways of integrating with the development env.
Thank you and we'll see you soon!

yours devvvvs

gregsn, Wednesday, Sep 23rd 2020 Digg | Tweet | Delicious 5 comments  

Helo evvvveryone!

Are you teaching or studying vvvv in an educational institution? Want to join NODE20 with a group of students? Please get in touch, we want to offer you a discount!

  • Email edu@vvvv.org
  • Tell us about your institution and how many students want to join
  • We'll get back to you with an offer

NODE20 features 25+ online vvvv workshops on various topics covering the needs of beginners and advanced users. This means the week of October 2nd to 8th will be a very good moment to divvvve deep. Besides, there'll also be a rather fine conference program you'll not want to miss.

vvvv in education

You may say we're biased, but we believe that vvvv is one of the more suitable ways to get people in touch with topics like creative coding, generative design, computer graphics, interaction design, data visualization, computer vision, physical computing, machine learning and similar. This is even more true for the all-new vvvv gamma. Why? Here is a list of pros and cons with a focus on use in education:

Pros

  • It is free for non-commercial/educational use without any restrictions or registration
  • It is quick and easy to install
  • Its visual live-programming approach allows you to get to results and iterate quickly
  • It comes with a HelpBrowser that makes it easy to find tutorials and documentation on various topics
  • It is easily extendable with custom nodes by writing standard C# code or using almost any .NET nuget
  • All of its libraries are open-source, meaning they can be explored, learned from and extended
  • It uses industrie standard programming concepts known from object-oriented programming that once understood, can also be applied in other programming languages
  • The core developers and fine community of users offer direct help support via chat and the forum basically 24/7/365

Cons (status fall 2020)

  • It runs on Windows only
  • It cannot export to mobile, the web or microcontrollers

Have more? Let us know in the comments.

Hope to see you at NODE!

joreg, Monday, Sep 21st 2020 Digg | Tweet | Delicious 0 comments  

Did you ever wonder what the first things were, that the cool kids in the VL.Stride EarlyAccess program created with the new 3d rendering engine for vvvv gamma?

It's been only a few weeks, but stunning pixel combinations got posted into our early access chat room.

And we collected them in a gallery for you:

A big THANK YOU to everyone involved!

We can't wait to see what you will create with it. And don't miss the workshops at NODE20 if you want to learn how to use it.

We are looking forward to the public release as much as you do,
yours devvvvs

tonfilm, Sunday, Sep 20th 2020 Digg | Tweet | Delicious 0 comments  

Who Takuma Nakata
When Mon, Sep 28th 2020 - 17:00 until Wed, Sep 30th 2020 - 20:00
Where Gray Area Online, United States

Workshop

In this two-day workshop, learn to create generative graphics using node based programming language called vvvv. During this session you will learn to build an immersive visual system, by applying various visual effects on a 3D animated character exported using Adobe Mixamo. This session will be a practical introduction to vvvv, with focus on 3D graphics and using data. For those who are interested in creating immersive visuals through code with the flexibility of creating interactive, physical experiences, this workshop is the perfect place to start.

Workshop Logistics Dates:
Monday September 28 &
Wednesday September 30

Times: 5 – 8pm PST

Cost: $120 Experience

Level: Beginner to Intermediate.

Requirements:
• Windows PC with a microphone input and a mouse (both necessary for this workshop)
• Install vvvv beta 64bit version.

Workshop Outline • Introduction to vvvv
• Installation vvvv and packs
• Importing Animated 3D character
• Tweaking vertices
• Making it audio reactive
• Learning DX11 Particle Packs
• Applying particle effects to the character
• Introducing https://visualprogramming.net/

Online Workshop This 6 hours online workshop will be held as two 3 hours workshop over two days via video webinar. We will have an online community chat to share your questions during and beyond the workshop. Please contact us if you have any additional questions at creativedev@grayarea.org.

https://grayarea.org/workshop/generative-graphics-workshop-with-vvvv/

Takuma, Thursday, Sep 3rd 2020 Digg | Tweet | Delicious 0 comments  
The vvvv workshops worldwide broadcast needs your help!

This NODE's extensive workshop program will be held as interactive online webinars. In addition we will also live stream all sessions for the worldwide community.

You can now join the NODE team on-site in Frankfurt (Germany) for the duration of the festival week. We are looking for committed people who want to get involved in our braodcasting studios for webinars.

For full details and how to apply, please see the Call for Tech Support.

nodeforum, Wednesday, Sep 2nd 2020 Digg | Tweet | Delicious 0 comments  

Previously on vvvv: vvvvhat happened in July 2020


Swoooosh,

and another month has passed... We're happily running the VL.Stride EarlyAccess program and at this point want to say HUGE THANKS to those who joined us. Development is in overdrive to make sure we can soon release a public version for all of you to patch with. If you can't wait, you can still join the program!

Also, lots of work goes into preparing for the upcoming NODE20. A growing team of now about 50 people is working behind the scenes trying to make this special version of NODE worthwhile even though we can not mingle in person. Workshop-wise we're still not complete. Here is where you get the best overview of what's coming your way:

Convinced? Show the team your support and get your ticket now.
Or, for a free ticket contribute in a different way:

In other news: If you're interested in machine learning, you may want to test this new pack we just released: VL.RunwayML allows you to run any model provided byrunwayml.com directly as a node in vvvv!

Gallery

data sculpture by Nils Schack
Jugend Hackt in talks with timpernagel about "Beethoven Recomposed"

Contributions

Updates

Also takuma is running another online workshop before NODE20. So if you can't wait, check this out!

Jobs


That was it for August. Anything to add? Please do so in the comments!

joreg, Tuesday, Sep 1st 2020 Digg | Tweet | Delicious 0 comments  

Contribute to NODE20’s conference and present your work in our broadcast stream – and get a ticket for free!

Every NODE festival needs some live input of content from its community – be it improvised lectures on screen, unplanned live A/V performances or a showcase of your work/studio. Shelter-in-place NODE20 needs to continue this tradition. Therefore also this year we want to provide a space for the vvvv community to present itself.

In between our sessions at the Emergency Broadcast Studio, we provide you slots to either present yourself, or have fun with the community. Pre-recorded showreels and performances are a good chance to safely submit your work and maybe stick around in our Festival Hub’s chat while it’s being broadcasted.

Available Slots

  • 30 minutes long breaks between lectures of our program timetable
  • 2 hours slots after 10pm for Monday, Tuesday, Wednesday

What can I submit?

  • Pre-recorded showreels, max. 10 minutes to showcase your work or studio.
  • Pre-recorded AV performance sets, between 10–20 minutes. Pre-recorded showreels and performances are a good chance to safely submit your work and stick around in the chat while it’s being shown.
  • For the brave: Live streaming of your AV performance in the evening slots where live patching is strongly encouraged. Duration to be discussed. The live streaming option is primarily for people that have live streaming experience and working set ups tested. Technical details have to be discussed with our team.

Further Process

  • The NODE team selects the featured works.
  • If your work is selected, we will contact you to proceed focused planning of your video contribution or live stream during the festival (approx 1 week before the festival) and send a free ticket to you via email.

How to submit?

Fill out this form until September 13th, 2020, and upload your pre-recorded files or preview for live A/V sets here.

nodeforum, Monday, Aug 31st 2020 Digg | Tweet | Delicious 0 comments  

Who takuma
When Fri, Aug 21st 2020 - 17:00 until Fri, Aug 21st 2020 - 20:00
Where online webinar, Germany

Learn from the creator of the vvvv beta video tutorial series takuma:

vvvv is well known for its realtime graphics powers. If you want to understand the proper workflow on how to achieve procedural realtime visuals you have to understand the packs and contributions and their most important nodes. This webinar takes you there.

We will be learning how to create a procedural graphic using vvvv beta. In combination with FieldTrip and some other interesting packs and nodes such as spline buffer Matcap and so on, we will develop an artistic good looking visual in a dense quality and color which can be used as a poster, wall paper or whatever.

This course is a good basis to dive deeper into the scene at this years online edition of NODE20 – Forum for Digital Arts. Prepare your neurons and get ready.

Details and Tickets

joreg, Tuesday, Aug 18th 2020 Digg | Tweet | Delicious 0 comments  

Previously on vvvv: vvvvhat happened in June 2020


Boooom!

Right in the sommerloch we finally have an earlyaccess release of VL.Stride. For now, this is limited to owners of a vvvv gamma license. So if you always thought about supporting the development of vvvv, now is a good moment. Insert coin, get a vvvv gamma license at 20% discount and get access to the VL.Stride preview right now!

Further:

Coming up: NODE20

Wtih many things now falling into place for vvvv gamma, we're really happy to have NODE20 - Second Nature coming up soon (October 2nd-8th). This will be a full week of interesting discussions, sharing knowledge and learning about the future of visualprogramming (as we like to call it). Hope to see all of you there! If you haven't already, watch the recording of the 5th worldwide vvvv meetup where you get a preview of what's going to happen during NODE20...

Contributions

A new work-in-progress

Updates

Gallery

SOLID by F3

Jobs


That was it for July. Anything to add? Please do so in the comments!

joreg, Saturday, Aug 8th 2020 Digg | Tweet | Delicious 0 comments  

anonymous user login

Shoutbox

~2d ago

joreg: @barbarerik maybe this one helps: vvvv-beta\girlpower\VL\Curves\SplineTree

~3d ago

barbarerik: Can somebody point me to example how to Bezier in Gamma? some example of how to connect nodes. Thanks

~3d ago

karistouf: @joreg, thank you

~3d ago

joreg: @karistouf there are no freeframes in x64 but you can use Contours via VL.OpenCV in VL!

~3d ago

karistouf: is there any contour.dll (FreeFrame) in x64 ? thank you

~5d ago

joreg: @qoupas i'm afraid this is a rather unspecific question. please start a forum thread with more details so we can help you.

~5d ago

qoupas: Hi, which nodes to use to parse real time data from a webpage ?

~10d ago

joreg: Happy and new, the #vvvv gamma 2021.4.4 release is out now: https://thegraybook.vvvv.org/changelog/2021.4.html

~21d ago

skyliner: happy new year evvvveryone!