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.
Hello Jamie, can you please add one more BPM range to the Node? i need 150 to 250 bpm. because i am working for a standalone lightshows for psychedelic ultrafast music and speedcore festivals up to 250 bpm... til 190 bpm it works fine with 120-180bpm setting... and then faster it brings just errors. i am also ok to pay for it a small fee <3
Hi Jaymie, Thank-you for the detailed response. I look forward to testing these options as VUO seems to be a great solution! Unfortunately I no longer have the OS installed (just a test computer) so I can't provide a log report. However, I don't think VUO was the cause as I had VUO running for hours with no problems. However, if I do observe a problem, I'll provide a log.
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?
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.
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 (
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.
@lhepner, it's possible to output video as an image sequence with the
Save Image node. Here are a couple of examples.
Option 1: save-image-sequence.vuo — Saves an image sequence in realtime. Since it's realtime it might drop frames.
Option 2: convert-movie-to-image-sequence.vuo — First use Vuo's File > Export > Movie, then run it through this composition which will extract the movie's frames to an image sequence.
(Both compositions save the images to the same folder as the composition.)
Not that I know of. It could be done if there were an
Invert Transform node (matrix inverse) and a
Transform Point node (applies a transform to a point, and outputs the transformed point). Converted your question to a feature request, opened for voting.
Hint to anyone who might want to implement these nodes yourself: There are already functions to invert a matrix and transform a point in
Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.