Calculate Amplitude for Frequencies node needs a continuous series of audio buffers to analyze; if you skip buffers there will be discontinuities in the audio signal; if it were audible there would be clicks/pops. In FreakCity, swapping the order (
Receive Live Audio ->
Calculate Amplitude for Frequencies ->
Hold List) should give better analysis results.
Thanks for letting us know. Right now we don't have enough information to figure out the problem. If you can give us a precise set of steps that always (or almost always) cause it to crash, including the composition and all its subcompositions, that would be of great help.
Here's Magneson's solution as a
Receive Mouse Moves on Layer subcomposition for easy reuse. You could make a similar subcomposition for
Receive Mouse Clicks on Layer.
Since that seems to solve the problem, I'll mark this feature request "Withdrawn".
Could you please send us the debug-mode-enabled console output when running a composition with that camera selected?
defaults write org.vuo.Editor debug -boolean true
defaults delete org.vuo.Editor debug
Have you seen the Feature Requests for these audio FRs: Node set for audio synthesis, filtering, and sequencing and Ability to use audio plugins in compositions (VST, VSTi, and AU)?
Second issue first, you just feed the value from the Midi Event out to a Hold node, and retrigger its output at the rate you want on the event in on the hold node.
As for the first issue, the way these counters work is that they take whatever last updated count of what something was, and apply a calculation adding or subtracting a fragment of the daily change every tick. They are more of an art piece than an actual counter of sorts. So to be as efficient as possible, you can do the same and not bother about reading the details from the website! :D
To set up a tick per baby born per day for instance, you just use a divide node, and divide 86 400 (seconds in a day) by 385 000 (babies per day according to Google according to UN) and feed the result to a Fire Periodically node. It should be a tick every 224ms or around there somewhere. Remember to use a Fire on Start to trigger the calculation in the divide node going to the Fire Periodically, if not it will be set at its default rate.
To also keep it in sync with the page you can possibly use a Fetch Tree node from the webpage, making sure it pulls the starting number from the page every time you restart the composition (provided you have an internet connection). In Chrome, you can see what to look for in the tree by marking the text you want to find, right-click and inspect. From the code in the webpage, you should search for rts-counter, births today, and rts-nr-int; rts-nr-10e3 and rts-nr-10e0.
Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.