Jérôme Lanon's picture
@Jérôme Lanon posted a new Discussion, “Make CMYK Color
jstrecker's picture

If the button presses are coming from outside of Vuo, such as TouchOSC, and each is identified with an index (1-16), you can use Get Item from List in place of Select Input, as shown below and in "Get Item From List as Select.vuo". Get Item from List allows for 16 or even more choices.

If the button presses are coming from Vuo's Make Button node, you can use a combination of two 8-input Select Latest nodes and a 2-input Select Latest node, as shown below and in "Select Latest with names.vuo".

"Select Latest with indices.vuo" additionally shows how to convert a Make Button press to a numerical index (1-16), use the index to check if you should show an image or a movie frame (Select Output), and use the index again to choose the image or movie file (Get Item from List).

Related feature request: Select and OSC nodes with variable number of ports.

cremaschi's picture

Hey followers of this post, none of you wishing to contribute to program this? https://github.com/micrem73/VuoARToolkit

cremaschi's picture

Hi; I succeeded in importing ARToolkit libraries in a Vuo node skeleton, following your suggestion. But, my skills are not enough to get the goal. Shouldn't be impossibile; on ARToolkit website there's a well documented example that could be used as a reference: https://artoolkit.org/documentation/doku.php?id=7_Examples:example_simpl...

So, what I did is creating a github project, uploading my humble start, open to all contributors here from Vuo community wishing to give some help. It's online at https://github.com/micrem73/VuoARToolkit I'll keep it updated of any eventual step forward I'd get.

regards Michele

cwilms-loyalist's picture

Select Input Node... How do I do 16 inputs properly???

OK, I'm running into an issue I can't quite seem to figure out, it may just be that I'm stuck on the way I used to do it in QC with the Multiplexer node where I could pick as many inputs as I needed. Here's the situation, I have 16 buttons on a touch screen, the plan is for each button to trigger an image (composite image) or video to display on another screen. In QC I would have just made each button trigger the corresponding Source Index value of a 16 channel multiplexer and just send the output to the proper billboard.

Pianomatic's picture

Is there room to expand collapsable nodes outside of just type-converters? For instance:

  • Other nodes that have one input only (including lists)? For example, Add, Multiply, Spint Off Event/Value...
  • Nodes where only one input is being sent data? For example, Get Item from List where the List port gets sent data, but Which is entered manually...
  • Chains of nodes that match the above requirements? For example, say some text data comes into an Append Texts node (with a / separator) to compile the pieces of a URL for an image that will be fed into a Make Image Layer node. The first four nodes could be collapsed in this chain: Append Texts>Fetch Image>Invert Image Colors>Convert Image to Layer>Render Layers to Window (As it is now, only the second last node is collapsed automatically.)
jstrecker's picture

Improved email notifications for vuo.org posts

We've improved vuo.org to make it easier to follow discussions and give you control over your email notifications.

You can now choose to follow a specific post, all posts in a section of the site (such as the Composition Gallery), or all posts by a specific user. Following means you get an email whenever someone makes a new post or comment. You can also unfollow posts. To learn how, see the FAQ How can I get notifications of posts on the Vuo website?

jstrecker's picture

Helpful descriptions, thanks. The part about "when the frequency scale of the graph is logarithmic" leads me to believe that the "accumulation modes" are similar to the Calculate Amplitude for Frequencies node's Frequency Bin Averaging options.

Kewl's picture
@Kewl commented on @Kewl's Discussion, “Calculate Node: clamp to one bound?

I looked for that, but it's not explicitly there in the node's description (or at least in a fashion I was able to understand...):

jstrecker's picture

Philip (@Pianomatic), agreed. As part of this feature request, we'll plan to add a right-click menu item to collapse/uncollapse a type-converter node.

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Questions and Answers

Ask a Question


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.

Image CAPTCHA
Enter the characters shown in the image.