We’re thinking there being 2-3 fixed sizes for things like faders and knobs - instead of there being a kind of infinitely scaleable thing, since it might not look good at really small sizes (you can see how I “redesigned” the small fader to be a kind of uncapped fader vs. the large panel fader on the bigger one).
Yes absolutely.
This is a good suggestion!
Yay! Really looking forward to that!
What do you @robertsyrett and anyone else using Eurorack think about switching over to a more 1:1 1vpo standard for Audulus 4 instead of the 1/oct standard we have now?
All it would take is a redesign of the quantizer. I feel like centering at A4=0 has some advantages, but I no longer think they really outweigh the disadvantage of being easily interfaced with modulars, or being easily understood by modular users who are just using Audulus.
This wouldn’t break any modules - the 1/oct standard could still be used, but I’d switch over the default modules in the library to be 1vpo.
I think it would be far more useful to just change the reference frequency from 440Hz to C1 (32.70Hz). The math is just much easier with 0-1 as an octave.
edit: so converting from 1/oct to VPO would just be to divide by 10.
Oh we’d still use 0-1 as an octave, it would just set 0 = lowest note, which you could switch to be A or C depending on your gear. We’d then still use a converter of x/10 to go out of the ES-8 for example.
exactly.
I suggest the Make Noise LXD for your purposes. It is inexpensive, small, analog, “west coast,” not too intricate, very versatile, and has a sonic character that really stands out when you hear it in person. If one was to build a very small rack, you could use this + an ES-8 and have some serious sound. It pairs extremely well with the Pulp Logic Cyclic Skew, IMO.
Thats a real nice sounding module and a great video! Thanks for sharing 
Here are some rough drafts - don’t take anything from the UI, that will change - this is really just trying to work out what the controls and I/O are for each type of module (also note they’re non-functioning).
Audulus 4 Module Outlines v1.audulus (22.9 KB)
They look pretty good. I notice you’ve gone back to the I/O at the bottom layout as well as more verbose labels. I think both are probably good ideas particularly for newbies. A couple of the labels are a bit obscure. I would replace cut with freq. and I’m not sure what the cosin output on the VCA is for. Cosine perhaps? An interesting idea but probably a bit obscure for a basic unit. (Hmmm, I wonder what you would get if you took an audio signal, multiplied by pi and took the cosine?) 
I think that one way to approach things is to release in flavours or collections. These chainables are really fun. I would like to see more of this.
What is a crossfade VCO? Is that a spline-based wavetable thinggie?
At least one of the oscillators needs a traditional linear FM input with a pretty modest index of modulation. Additionally, bipolar knobs should have some indicator that the default is in the middle rather than at zero.
As a side note I hope we can keep the 1/Oct inside Audulus. VPO is cool and all but it’s another layer of conversion away from Hz, which I notice that pretty much everybody in MAX and Pd use.
For some reason, I made a little demo osc to show what I meant. I forget what you were planning to do with the shapes, so I just did my favorites.
BTW I think this could be a good idea for a give-away. Just post a module with a finished UI but nothing inside and have the contest be to build how you think the module should work. That could just be me being a nerd though.
I second this. The Audulus equivalent of 14HP for the basics modules is really friendly to people learning Audulus. Clear, uncluttered, consistent designs will guide users into the audulus workflow and eventually they will pick up the more compact abstract uModules.
I also agree “Freq” is more common when labeling cut off frequency.
You silly goose, we did that already in 90 degree all pass filter thread. I actually really like the effect.
It’s where you crossfade between two waveshapes at audio rate. I’m actually making it right now and will upload it tonight.
There’ll definitely be more VCOs, including a basic FM one - this is just some of them I was sketching up.
Yeah definitely - these will honestly a lot of them be faders instead of knobs, so they’ll have SVG markings on the side.
I think we should just shift the scaling so that 0 = lowest note, not A440. That way it will resemble VPO more and be easier for others to pick up.
As for Max and Pd - do you mean they use Hz? The only problem with Hz is that it’s non-linear and hard to manipulate with LFOs and simple scaling math.
haha I was just copy/pasting the modules and changing the names of I/O - forgot about that one! And yeah I just did cut cause I was blanking on Freq and looking for something to fit inside the knob. For the most part these aren’t to show what the labels will look like or whatnot, it’s more about the functionality - what can be controlled, what are inputs and ouputs, etc.
That would be awesome!
I think you mean the opposite. Hz is linear and out perception of pitch is logarithmic, so we think about raising and lowering semitones as if they were linear. Max and Pd have no problem making you do the math on hard mode 
, but I think what goes on is that they send around midi note numbers and then convert to Hz right before the oscillator. They use a standard frequency lookup table and adding midi notes is intuitive in the same way as semitones.
That said, the fewer competing soft standards there are within the library the better.
Yeah, but comparatively, jumping an octave in Hz is exponential vs. the linear jump from 0 to 1.
This creates a linear pitch space in which octaves have size 12, semitones (the distance between adjacent keys on the piano keyboard) have size 1, and A440 is assigned the number 69.
From this (describing MIDI): Pitch (music) - Wikipedia
Speaking of which, would it make sense to basically follow the MIDI scheme, where 0 = C-1? I know that MIDI is working in units of 1 instead of 1/12, but it might be a useful reference point. Perhaps is should be C0?
@biminiroad I figured it was something along those lines. @robertsyrett I totally forgot about the Freak Shifter. On the subject of knobs and sliders, I would love to see an option to have one that returned to center when released. Or alternatively the ability to set a knob/slider from an input. Max is very flexible in that area. I’ve been plowing through the Max/DSP tutorials and I see a lot of things that would make programming in Audulus easier. Audulus is definitely more abstract than Max (which is a good thing in my opinion), but there are times when having a defined order of execution would be nice. I think Taylor’s real challenge is keeping the simplicity of the current version of Audulus while coming closer to the functionality of Max/DSP. (BTW the current version of Max for Live isn’t as stable as Audulus despite the huge difference in price.)
That should definitely be coming. It’s essential for pitch wheel type stuff.
What do you think could make that easier in Audulus? Do you mostly run into this problem with feedback loops?
This seems reasonable. That’s what all my other Midi-CV gear does and it seems like the industry standard. The big downside is that there is some rounding to the lookup table. So C9 is 8372.02 Hz, which is obviously not an even multiple of C1(32.70Hz). Since everything in even temperament revolves around the nice even multiple of 440 there will be some minute amount of detuning unless we go with a very accurate measure of low C. The Irony is that I pretty much never tune exactly to low C in eurorack, but somehow when it’s in Audulus I want the pitch to be perfect.
I’m perfectly happy with A440 == 0. It’s kind of an international standard for tuning and the transposition is trivial. Anyone that wants to adopt a different zero point only has to do a simple addition. For Eurorack gear it might make sense but by the time you interpose a scaling module for your ES-8 or similar it really doesn’t matter.
