Beginner questions

#1

As a newb, I have been wondering if there is a cheat sheet/quick reference somewhere that I have missed that explains what some of the common abbreviations mean that people use in the posted patches here.

There is often an ‘o’ or an ‘a’ or a ‘g’ in an input/output glyph – and probably other letters as well – it would be nice if there were a cheat sheet of basic things like this and other things that newbs might need to be reminded about. Maybe something in the Audulus directory that gets installed with the app. (I’m using it on iOS).

New to the Audulus forum? Read this first!
#2

Btw, I think that I have pieced together that ‘0’ is 1/octave for note input. ‘g’ is gate and ‘a’ is maybe audio. Is ‘m’ modulator?

#3

https://forum.audulus.com/t/audulus-3-library-reface/1455/87

This is the ongoing project to fix the confusion. These new modules will be more well labeled and easier to comb through. Download the latest zip and try a few of them out!

Basically g is gate, a is audio, m is modulation, o is 1/octave. Connect like to like generally :slight_smile:

#4

What is ‘z’?

#5

Is there a module with a z?

#6

z
z.PNG2048×1536 297 KB

#7

That’s the indicator for a feedback loop. It shows you where the feedback delay is present. z is a variable for delay, so z-1 is a single sample delay, for example.

It’s not a letter that is put there with a node like these others were, it just automatically appears. If you use the FeedbackDelay node or the UnitDelay node, you can explicitly determine where the delay occurs. If not, Audulus will just try to guess where to put it.

You need a feedback delay because you can’t compute a result that depends on itself instantaneously. Like create an expression node where 1+x=x and attach a value node - you’ll notice it count up really quickly - that’s because there’s a small delay in the calculation of the input x and the output of the 1+x expression. Use a UnitDelay between the output and x and it will count even faster.

#8

So Audulus has already made the adjustment to the sequence and if I wanted to I could use the feedback delay node to specify the input for the single sample delay to occur?

#9

The feedback delay node will put the feedback delay in a particular point in the feedback loop, which you need to do to get certain things to work, like a change detector. A unit delay acts like a feedback delay node but it tells audulus to process everything in that loop in single sample mode. This means that instead of calculating outputs in batches of ~300 samples, it calculates every single sample and reevaluates the entire loop. This is important to do in situations where feedback is normally instantaneous like in an analog filter. It will never be exactly like analog, but the small time delay approximates it. This is also why a higher sample rate can improve sound quality in a modelled filter, as it is more closely approximating the real thing the faster the calculations get.

So you use one or the other, not both. You want to avoid using unit delay when it’s not impotant for the processing to happen quickly, like in a flipflop or a counter. Just where it needs to happen at audio rate, like in a filter or feedback distortion.

#10

“Look a loose thread. I’ll yank on it…Oh no, the Universe!”

It was nice having a glimpse at the dense forest from a hilltop.

I pulled the cable out of the linear fm input, which of course made the ‘z’ go away.

#11

Is there a simple tutorial video or Audulus project that demonstrates the basics of using the sequencer modules (for example, the 4-step rnr and the basic random chance 4-step sequencer)? My main questions are:

  • how do you set the pitch range of the sequencer
  • simple example of the care and feeding of the r and rs inputs

It would also be helpful if some of these modules had tips inside about common connections.

I have found a number of examples that use them, but they are somewhat daunting for a newb. Maybe, I’ve overlooked some resource. The module docs gives an idea about the reeding the rs with output of a clock divider (helpful) but not about pitch range.

Thanks for the help and great supports.

#12

Is there some trick when you group a couple of subpatches that have used-interfaces to keep the exposed elements exposed? I haven’t figured out how to propagate the u.i. From a group made up of suboatches to the parent.

#13

There’s no automatic way to do this (although apparently it will be possible in the next version of Audulus).

The UI elements need to be recreated. For example if you have a frequency knob in a sub patch, then you would have to create a frequency knob in the top level patch and connect it internally to the sub patch frequency knob.