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, agreed. As part of this feature request, we'll plan to add a right-click menu item to collapse/uncollapse a type-converter node.

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

Instead of the two-sided limit with clamp, you could do a one-sided limit with min or max — for example min(value, highLimit).

Kewl's picture

Thanks for the info. Depending on what type of audio data you want to show, both white and pink bias are useful.

From Waves' PAZ Analyser user manual:

Pink noise is defined as noise that has constant energy inside any frequency band with a constant Q (i.e. frequency/bandwidth=a constant value). Pink noise is an important audio signal since it represents the average spectrum of a typical audio signal, and because the ears analyze the sound in approximately constant-Q bands. Because PAZ has almost constant-Q bands, a pink noise input will show up as a flat spectrum when no weighting is applied.

And from Metric Halo's SpectraFoo user manual

EQUAL POWER PER OCTAVE AND EQUAL POWER PER HZ ACCUMULATION MODES: SpectraFoo’s underlying FFT generates more data than can be displayed on screen at once. The way that this data is treated when the system computes the trace is called the accumulation mode. SpectraFoo provides two accumulation modes that you can choose using the Spectragraph Controls window: 1. When the Accumulation Mode is set to White Noise is Flat, the Spectragraph shows the maximum power of all of the spectral lines in the FFT that fit into each point in the displayed trace. This has the effect displaying white noise (or noise that has an equal amount of power at each frequency) as a flat line. This mode is traditionally used when the frequency scale of the graph is linear. 2. When the Accumulation Mode is set to Pink Noise is Flat, the Spectragraph shows the sum of the power of all of the spectral lines in the FFT that fit into each point in the displayed trace. This has the effect of displaying pink noise (or noise that has an equal amount of power in each octave) as a flat line. This mode is traditionally used when the frequency scale of the graph is logarithmic and corresponds to the type of display available on a traditional RTA.

So I think both "accumulation modes" are useful and that's why an option would be interesting. But, if it's not possible, I'll happily live with the new bias. The new scaling is the big progress anyway and fits better with other data processed by Vuo.

Thanks!

jstrecker's picture

The values scaling is different: is it now between 0 and 1?

Yes, assuming the input audio samples are between -1 and 1, the output amplitudes are between 0 and 1.

But the frequency bias has also changed: before, it was "pink is flat" (equal energy per octave), now it's "white is flat" (equal energy per frequency interval).

When Frequency Bin Averaging is None, isn't "white is flat" always the correct behavior? My understanding of white noise vs. pink noise is that white noise should (ideally / on average) have an equal amplitude for every frequency bin, and pink noise should have decreasing amplitudes as the frequency increases.


If you do want to go back to the old behavior, you can still use the old version of the node. In Vuo 1.2.3 and earlier, the Node Library lists vuo.audio.analyze.fft. In Vuo 1.2.4 and later, it lists vuo.audio.analyze.fft2, but vuo.audio.analyze.fft is still installed. If you create a composition in Vuo 1.2.3 containing vuo.audio.analyze.fft (the deprecated node) and open the composition in Vuo 1.2.4 or later, it will still contain the vuo.audio.analyze.fft node with the old behavior.

Or you can paste the old node directly from Vuo 1.2.3 to Vuo 1.2.4. Or just paste the following text onto the canvas:

digraph G
{
CalculateAmplitudeForFrequencies [type="vuo.audio.analyze.fft" version="1.0.0" label="Calculate Amplitude for Frequencies|<refresh>refresh\l|<samples>samples\l|<frequencyBins>frequencyBins\l|<frequencyBinAveraging>frequencyBinAveraging\l|<amplitudes>amplitudes\r" pos="459,67" _frequencyBins="\"255\"" _frequencyBinAveraging="\"quadratic\""];
}

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 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. Typically a few emails per year.