jstrecker's picture

Jaymie (@jstrecker)


  • Vuo Founder
  • Team Vuo
jstrecker's picture

Alastair (@usefuldesign), to understand meshes it helps to understand the OpenGL rendering pipeline.

Can anyone suggest a good reference for beginners on the OpenGL rendering pipeline with lots of diagrams?

jstrecker's picture

This is an open-ended feature request, but I agree that there's plenty of room for more documentation on data types.

  • The manual could talk more about the widely used data types like objects and layers.
  • The node documentation could talk about types that are specific to node sets.
  • The tutorials perhaps could provide more information about data types.

I like the idea of documentation being originated by the community. That way it answers the questions that people really want to know about.

… like the nice diagram by Magneson (@MartinusMagneson). Good that it will be here as a reference until we are able to add more official documentation.

I've opened this feature request for voting. Since it is open-ended, I think what we'll do is make an initial pass at the manual and/or node documentation. From there, the community can create more specific feature requests as the need arises.

jstrecker's picture

Those extra events going into the Build List loop in the section from punto attivo to Combine Layers make me suspicious. Especially the continuous stream into Time of Smooth with Duration.

jstrecker's picture
@jstrecker commented on @loddie's Discussion, “Simple Video Delay

Both Receive Live Video and Receive Blackmagic Video use CPU RAM to read the image from the capture device — because that's how the capture devices provide it — and then Vuo transfers the image to VRAM.

Also, I did have the Get First From List node installed as Jaymie did, but it automatically disappears after connecting to Render Image to Window.

Yep, that's fine. It's called a collapsed type-converter. The idea is to make the little helper nodes smaller on the canvas to focus attention on the interesting nodes.

Also, if I tried to Run without a Calculate (delay) value other than 0 seconds, it wouldn't stream video - but after running I could it back to 0.

That's because of the Enqueue node. If its Max Item Count is 0, it outputs an empty list. (You can find this out by clicking on the Enqueue node and looking at its documentation in the panel below the node library.) To allow a delay of 0, you'd have to add a second path of nodes that bypasses the Enqueue node. The Select Output node might be helpful here.

If the audio/video sync drifts, can the delay be adjusted in real time or will the composition have to be stopped and restarted?

It can be adjusted in real time. I'm guessing it would either skip frames or repeat frames, depending on the adjustment.

After editing the Calculate input, be sure to fire another event into the node. An event is necessary to make the Calculate node execute and send its output along to Enqueue. Right now the only event it gets is the one from Fire on Start. You can right-click on an input port of the Calculate node and select Fire Event.

So far, I've only tested with Seconds as the delay value. Can it also be delayed by number of frames?

Yes. The Calculate node is calculating a number of frames. So actually, you can take that node out and enter the number of frames directly in the Enqueue node's Max Item Count port if you want. (In that case, you don't need to fire an extra event, because there are already events from Receive Live Video hitting the Enqueue node every frame.)

I did leave it running overnight and the computer had crashed the next morning, but I'm not sure if VUO was the cause.

Is there a crash report dated that night in Console.app under User Reports, with Vuo or your composition identified as the application? If so, feel free to file a bug report.

jstrecker's picture

This I assume is in addition to the Get Items from Dictionary and Make Dictionary nodes?

Yes. The current, very limited support for dictionaries is just enough to enable a few specific nodes (Calculate, Get Tree Attributes).

The idea of this feature request is to support any key and value types and to provide basic nodes for creating, modifying, and accessing dictionaries.

Make Dictionary can't take Single Key inputs and apply them to lists of values.

I'm not sure what you're ultimately trying to accomplish, but maybe Magneson's List Tools would help.