A few small utility sub-patches
• I've been going patch crazy the last few days converting all my old Max/Pd/Reaktor to Audulus.
I plan on cleaning them up over the next few days and posting them here.

To begin, two small patches for converting Hz to note names and numbers.
• good utility, thanks.
• Updated.
• Thank you for the patch, its works well on audulus 3
• Updated.

Added [ Hertz -> 1/Oct ] and [ 1/Oct -> Hertz ]
• Hello @ToyDivision,
If I well understood the module 1/oct-->Hertz, is used to increase by 1 the octave by doubling the frequency. Do you have a pacth which give some examples for the using of this module?
• @jpalluin - yeah, that's pretty much it.

In Audulus a value of 1 @ 1/oct is equal to 880hz or the note of A5.

A6 = 2 = 1760hz
A5 = 1 = 880hz
A4 = 0 = 440hz
A3 = -1 = 220hz

It get's a little harder to calculate when you're not using A.

(updated: thanks @jpalluin)
C4 = -0.75 = 261.626hz
D4 = -0.583333 = 293.665hz

I'm not sure if they'll be of any use to others, but I've found as I'm exploring all of the modules in Audulus it's been handy to be able to convert between the different measurements and to get visual confirmation as I'm designing patches.
• Thank you for the explanations and demo patch.
I'm a bit confused with the frequency of A4 = 440 Hz (I thought that A3 = 440 Hz which corresponds to the French/Latin note LA.
Sorry for beeing a newbie, but where are coming the numeric values (60 for C3 for instance) from ?
• forget my last question, I am stupid lol

the numeric values are coming from the formula (440 / 32) * (2 ^ ((x - 9) / 12)) you put in the module.
• By all means please double check my maths, I'm certainly no expert in this.

I used this for reference -

http://www.electronics.dit.ie/staff/tscarff/Music_technology/midi/midi_note_numbers_for_octaves.htm

I'm pretty sure everything checks out.
• Yes, I had a look at the link: It is written that the MIDI note 60 is for C5 (not C3).

I think I've been staring at the screen too long.
It's worth noting that there are conflicting opinions on which octave a note belongs to:

http://www.electronics.dit.ie/staff/tscarff/Music_technology/midi/midi_note_numbers_for_octaves.htm
https://newt.phys.unsw.edu.au/jw/notes.html
http://www.tonalsoft.com/pub/news/pitch-bend.aspx

All have different values...?
I think https://newt.phys.unsw.edu.au/jw/notes.html is the most common?

I've updated my previous post and here is a new demo for those interested.
• Regardless of what you choose to call it, I think the important thing here is that the maths is correct.

I think it is... = )
• in fact, The MIDI 60 is for C3 and MIDI 69 is for A4 (which is well 440 Hz as you said).
Sorry for the waste of time....
• Do you mean:

B3 = 59
C4 = 60
D4 = 62
E4 = 64
F4 = 65
G4 = 67
A4 = 69
• Yes, exactly!
• That really twisted my brain for a few minutes...

I'm pretty sure we were always on the same page though. = )
• I have checked 3 different sources on the Web....
Thanks to your small modules, we no longer need to look for the formulaes in the internet.
• Yeah, it makes sanity checks so much easier when you can just plug a patch cable in and see the results. The power of visual programming!
• visual programming is not a new concept. I have learned to sketch electronics logical circuits in the 80's (on the paper) and then came the 2nd generation of PLC in the industry (Siemens S5 for example) which allowed to assemble the logical modules together graphically with a computer. The Grafcet is for me the father of the visual programming.
• I had to google Grafcet. Visually it reminds me of Pure Data. Is it used mainly for industrial design?

I'm unsure why visual programming isn't more prevalent in traditional programming circles, although I expect that to change. The work of Chris Granger on Eve (http://witheve.com/) is a good example.
• GRAFCET is used only in industry, it has been created to make easy the programming of automatic machines( mainly in automotive). In the past, we use to sketch the grafcet on the paper and then to write the boolean equations from it ( there are forgotten rules for this, I'm a dinosaur). The last step was to enter the equation in the PLC. The PLC is a kinda box with inputs and outputs. You connect the sensors of the machine to the inputs and the outputs are connected to the actuators (relays for instance). Later on, there was no more need to enter the boolean equations thanks to visual programming (you can connect some modules together directly on a screen).
For me, programming means to set up algorithms in order to get expected results according to the imput data or events. The evolution of the programming langages allows us to work more friendly.
But a program is not enough by itself, the user must enter data and it can become tricky. That is why the concept of HMI (human machine interface ) was introduced. For me Audulus is a HMI.
This HMI could be encapsulated (in the future ) into something which will allow the user to customize the apearance of the final product (a complete synth with nice keyboard for instance).
But at the end, the processor will always see binary information.
• National Instruments 'Labview' is a graphical programming language that has been around for awhile. It makes communicating between hardware peripherals easier for non programmers.
• It is the first time I heard Labview, maybe because I am in France...