As one of Vuo's developers, I work on Vuo's engine (the thing that makes compositions run), work on nodes, and write documentation. You'll see me on the forums answering people's questions about Vuo.
I enjoy using Vuo to make live music visuals. My hope for Vuo is that it will grow into a community of people of diverse backgrounds and identities making lots of different artistic, useful, unique, goofy, beautiful, crafty, wonderful compositions.
Estoy practicando para ser competente en español. Si publicas en el foro en español, trataré de responder en la misma manera.
With time*(index-1), it's taking the input time and spreading it out so that the 1st item ends up with time*0; the 2nd item, time*1; the 3rd item, time*2; and so on. Actually, taking off the -1 might be better. With time*(index-1), the 1st item always sits at an x-position of 1.2, offscreen. If you change it to time*index, the 1st item slowly moves to the left over time. (This is easier to see if you temporarily change Curve : Start Position to 0.9 so it's onscreen.)
GOING INTO THE Y
X+perlin2d(time*speed,X*scale)*amount — OK, let's break it down.
Each image is assigned a different randomly chosen value between -1 and 1 when the composition starts. That's X.
The X+… part of the expression offsets the image vertically. So, rather than being clustered near the middle, the images are spread out vertically.
The perlin2d function takes 2 inputs. We're using the first one to make the image move up and down over time. time makes that happen, and speed is just a parameter that you can change if you want the movement to be faster or slower.
We're using the perlin2d function's second input to make each image follow a different path, instead of all moving up and down in unison. The unique X of each image makes that happen. scale is another parameter that you can change or not. If you make scale closer to 0, the images are closer to being in unison.
The last part of the expression — …*amount — is yet another parameter. It controls the vertical range of movement for the images.
One small suggestion (sorry if I messed this up in my original composition) — to keep extra events from going into the Build List loop and possibly messing up its count, there should be a Hold Value between Change Speed and Calculate.
Here's one way to tightly pack different-width texts into a row — create a layer for each text, scale each to a different width, then combine with Arrange Layers in Row. Then you can similarly pack the rows into columns — scale each row's layer to a different height, then combine with Arrange Layers in Column'.
without the "run vuo in separate processes" preference enabled
Ahh, that's the key. When the Vuo composition is running in the same process as VDMX, VDMX has to provide a graphics thingy (the OpenGL context) for Vuo to draw on. Vuo is expecting the OpenGL context to be in a certain state, but VDMX is providing one in a different state — understandably, since we hadn't documented exactly what state it should be in. We'll take care of this in the next Vuo release.