Audulus to Bring Familiar Rack-Mount Design in Upcoming Release

To the left is the current Audulus interface. According to the Audulus forums those that prefer a more traditional interface for modules have something to look forward to:

"I am building a library of basic synth modules that will bring a more familiar rack-mount modular look to Audulus for those who may be at first a little overwhelmed by building patches from nodes alone.

Some of these are just a node + a standardized package (like the keyboard module). The ones that have my name on them go beyond the simple function of the node itself, like the Bimini Road Dual Dark Delay which has LPF on each delay line, stereo mix outs, and separate outs for delays only to process them independently of the original signal. There are also some others, like the Rotating Clock Divider, that are clones or workalikes of existing analog modules (in this case, the 4MS RCD).

The nodes are small and the UI for each panel is condensed to allow more modules to fit in a single window view while still being easily controllable.

Over time, I will add more and more modules to this collection. If you have a module that you would like have included in this collection (after 3.0 is officially released), try to get it close to the standard "look" of these modules and send it my way via comment below, PM, or biminiroadelectronics@gmail.com. I will tweak the look and layout if I think it needs it, but the functionality will remain unchanged, and you will of course retain credit (i.e. JDRaoul - Amazing Creation Module).

If you have any suggestions for modules, please leave them in a comment below.

All future updates of this library will be indicated in this thread in this top post - if the library is updated, I will leave a comment to push it up in the forum, change the version number in the title, and the newest version will always be available in this top post.

My custom modules will always come with commentary that illuminate my thought process for and execution of each patch. If you'd like your module to be considered for this collection, I'd encourage you to do the same, but I won't make it a requirement.

This isn't *the* standard, it is merely *a* standard. These patches will all be very neatly laid out on the inside so the signal flow is easy to study.

Attached is a screen shot of the growing list of modules. Check back often for more updates.


List of Patch Standards & Practices for inclusion in the Library:

So that all these patches "play nicely" with one another, they need to be standardized. Here is an ongoing list of standards I'm using.

UI Standards:
- All modules must be the same height, unless the functionality of the module requires it to be larger.
- The inputs and outputs define the width of the module (i.e., they are the furthest elements to the left and right).
- If it's a small module, the label goes in the center. For larger ones, the label goes in the far left corner).
- Custom patches are labelled as "[Creator] :: [Patch Name]" The patch name should include its function.
- Inputs and outputs are labeled "In" and "Out" unless they need to be something else for clarity.
- Inputs and outputs that require or produce a polyphonic signal should be labelled "In/P" and "Out/P"

Signal Standards:
- LFOs should output between 0 and 1 (DC). Making an AC signal is easy: just subtract .5. LFO inputs should also be between 0 and 1 (if you need AC signal input for your design [as you'd need for a vibrato], do this on the inside of the patch).
- Modules should adhere to the 1/oct standard. 0 = reference note (440hz, for example). -1 is one octave below 440, 1 is one octave above."