The Clock Divider module with 2 inputs and 8 variable outputs And now that we're including GLSL shader and a Lua canvas node, it's got several new layers of complexity to contend with. It really is a visual programming language, after all, even if it's geared towards making music. However, for a program like Audulus, refining the onboarding process could only go so far. The innards of a clock divider module that first chooses a series of divisors then rotates them to each output And perhaps there is some on-boarding that could be written into Audulus that would gameify the initial learning process and make it more user-friendly.
Create synth audulus 3 manuals#
In an ideal world, every feature of a program would be discoverable, and these manuals would sit untouched, collecting digital dust.
Create synth audulus 3 how to#
To get people on board, we need to explain how to use Audulus in a clear, concise manner. To grow Audulus, we need to get people on board and help them understand why it's such a special program. Now, I've shifted careers to become a programmer and working harder than ever to help Audulus reach its potential. The more I built in Audulus the more curious I got about how it works under the hood. In my case, my passion for coding was ignited by Audulus. My job as an educator is to get people to understand that Audulus is not easy, but it is easier than it looks, and that investing time in understanding it can be a rewarding, even life-changing experience. It's pretty, sure, but also pretty complex. This in an example of a random melody generator.Īudulus may intimidate some new users. In Audulus, nodes are used to create modules, which are in turn used to create music. After all, the node documentation is there for a user when they're in the middle of building something and need a reference, not a lesson. Explain each input and output and what the node does. The new documentation for Audulus 4 is much more streamlined. Work in progress of the new nodes reference written in Markdown with a little HTML sprinkled in There is a place and time for diving into the equal power pan law, but it is not while explaining how an audio output node works. What seems obvious to me now is not that Audulus needs less documentation, but that it needs its documentation to be more focused.
The entry for the oscillator node is over 10 pages long and tries to explain Fourier series! No one needs to go that deep when they're just trying to understand how your product works. Looking back on my old work, I saw that what I'd tried to do with the documentation was put as much information as possible about everything into each entry. If you need a picture of an old dead mathematician to explain your iOS program, maybe you've lost the thread.
Create synth audulus 3 for mac#
A couple days ago, I started work on the rewriting all of the documentation for the upcoming release of Audulus 4, a modular synthesizer visual programming platform for Mac and iOS.
0 kommentar(er)
