Audulus 4 Released, now Freemium - Ask Us Anything!

espiegel123

@Audulus_Mark : one of the nice things about streambyter as a midi monitor is that it includes timestamps. It is what I used when I was first exploring the jitter/value skipping mystery that I mentioned a while back on the Discord.

Audulus_Mark

@espiegel123 said:

@Audulus_Mark said:

@espiegel123 said:

@Audulus_Mark said:

@espiegel123 said:

@Audulus_Mark said:

@mojozart said:
Speaking of MIDI interest, as some were a couple days ago, I am interested in creating simple MIDI adapters and transformers in Audulus. Scale quantizers, channel filters, arpeggiators, loopers, velocity dampers, CC modulators.

The kind of thing I might grab StreamByter or Mozaic or Rozeta for now. Not that I want to replace these fine tools, but if I'm in an Audulus frame of mind, I don't want to leave it, and I think that if I knew how to tweak MIDI in Audulus then it would be a small step to MIDI generation - which I am also interested in.

You can send MIDI out of Audulus right now as note and CC's, but as of this moment, it broadcasts on the global channel (that is, you can't yet select individual channel outs). I think this will change in the future, I've been talking to Taylor about how I'd like to be able to send on/off light messages to my MIDI Fighter Twister and be able to make it light up as a matrix sequencer.

That said, if you don't mind it going out on the global channel for your purposes, everything is right there to be used - if you need help building something specific, let me know!

midi events from audulus are currently sent on channel 1 (literally channel 0 but people refer to midi channels by ordinality). Midi doesn’t have a separate global channel.

Ah I mispoke I meant Omni, like sending to them all at once. I read in the manual of the MIDI fighter twister that channel 4 changes the page of the controls, and that was the only thing I could do from Audulus.

Anyway not even I know everything about Audulus - and MIDI is definitely a personal weakpoint for me. My new year’s resolution is to fix that and get better at understanding it and showing it off to people!

Omni is a receive mode that means "receive midi from any channel".

Audulus sends all events on channel 1. You can check this with a MIDI monitor. It (thankfully) does not send copies of events on each midi channel. A MIDI event has a single channel assignment of 0 to 15 (which we call channels 1 to 16). Audulus currently sends all events on channel 1.

Ok, good to know! I thought it was odd though that if it's sending on 1 that it would reach a function that's only on channel 4, so that's why I figured it was sending it out on all at once.

I suspect that the MIDI Fighter Twister was in omni mode. What that would mean is that it ignore the channel number of incoming signals -- it would still use the assigned channel for outgoing messages.

On iOS, the free Streambyter app is a convenient tool to have as it can load as a standalone app or AUv3. While it is intended as a MIDI manipulation/scripting app, it also is a great MIDI monitor. You can send output from Audulus to it to confirm what I've said.

Awesome thanks for the tip about Streambyter! I'll check that out Makes sense about the MIDI Fighter Twister.

mojozart

@Audulus_Mark and @espiegel123 thanks for clarification. That is enough to get me started.

mojozart

Some observations using Audulus AUv3 in apeMatrix.

I was seeing some AUv3 crashes in apeMatrix. At the time I was using Input and Output nodes.

Then I tried the same in AUM and the I/O nodes didn't seem to work (no sound, but no crashes) so I switched to Input and Output modules, and that worked.

So then I tried I/O modules in apeMatrix and that worked and didn't crash...

However, in apeMatrix I noticed that simply moving a knob to control the time of a delay line would cause audio glitching. Why? Related to buffer size, or is it something about apeMatrix?

espiegel123

@mojozart said:
Some observations using Audulus AUv3 in apeMatrix.

I was seeing some AUv3 crashes in apeMatrix. At the time I was using Input and Output nodes.

Then I tried the same in AUM and the I/O nodes didn't seem to work (no sound, but no crashes) so I switched to Input and Output modules, and that worked.

So then I tried I/O modules in apeMatrix and that worked and didn't crash...

However, in apeMatrix I noticed that simply moving a knob to control the time of a delay line would cause audio glitching. Why? Related to buffer size, or is it something about apeMatrix?

What buffer size are you using? Do you get a different result if you change the buffer size?

Input/output nodes don't send audio out of Audulus -- those are how you pass data into and out of submodules. The nodes for getting audio input and sending out audio from audulus are the ADC and DAC nodes.

Audulus_Mark

@mojozart said:
Some observations using Audulus AUv3 in apeMatrix.

I was seeing some AUv3 crashes in apeMatrix. At the time I was using Input and Output nodes.

Then I tried the same in AUM and the I/O nodes didn't seem to work (no sound, but no crashes) so I switched to Input and Output modules, and that worked.

So then I tried I/O modules in apeMatrix and that worked and didn't crash...

However, in apeMatrix I noticed that simply moving a knob to control the time of a delay line would cause audio glitching. Why? Related to buffer size, or is it something about apeMatrix?

Look inside the delay module and you will see a slew limiter between the time control and the delay line node. This is because if you instantaneously change the delay time of a delay, it will cause discontinuities that create a crackling sound. Just imagine it for a second - you have a sound playing and then all of a sudden it’s x2 speed, no ramp up.

Because there’s only finite resolution to the knob, you have tiny little jumps in time from one to the next thet introduce that crackling.

All digital delay effects that you hear have some kind of smoothing (slew limiter) on their time controls to prevent this - it’s just happening inside the effect.

Audulus gives you tools to create things from the ground up, so this is like the elemental piece of a delay, the delay line - it’s not a digital delay effect.

If you have an effect where you don’t plan on modulating the delay line, perhaps you can save some CPU by leaving that out, or perhaps you leave it in for a nicer UX, up to you.

As for the crashes we found some bugs and are fixing those, it will be more stable soon. @espiegel123 is guiding you correctly about the I/O - what you want is the input-output modules, not the nodes, or the ADC DAC nodes if you want to use those. The modules are just those nodes with convenient controls added.

Hope that helps!

mojozart

@Audulus_Mark & @espiegel123 thanks again for explanations!

With the current version 4.0.2, I can't get through SFM Tutorial 8 in apeMatrix without a crash.

Audulus_Mark

New episode of Wired Up with Mark! This one goes on a real deep dive into a counter, which is the heart of a sequencer.

Audulus_Mark

michael_m

The tutorials are really appreciated Mark - I just can’t keep up with them though! Definitely helping me out with the way that Audulus does things under the hood.

maschinelf

Apologies if this was asked before, but is there any sort of upgrade discount for older versions of Audulus, since I bought Audulus 2 way back.

Even the full price is very reasonable and I will probably purchase it eventually anyway. No rush though since voltage modular is keeping me busy anyway. But yea would certainly buy it sooner with a discount.

Audulus_Mark

@michael_m said:
The tutorials are really appreciated Mark - I just can’t keep up with them though! Definitely helping me out with the way that Audulus does things under the hood.

Thank you! To clarify, by “keep up with them” do you mean I’m making a lot and you don’t have enough time, or you find them difficult to follow?

Audulus_Mark

@maschinelf said:
Apologies if this was asked before, but is there any sort of upgrade discount for older versions of Audulus, since I bought Audulus 2 way back.

Even the full price is very reasonable and I will probably purchase it eventually anyway. No rush though since voltage modular is keeping me busy anyway. But yea would certainly buy it sooner with a discount.

We’d love to be able to give discounts but Apple doesn’t allow it, sorry! It would be nice if they developed this kind of infrastructure because it would be good to reward long time users.

michael_m

@Audulus_Mark said:

@michael_m said:
The tutorials are really appreciated Mark - I just can’t keep up with them though! Definitely helping me out with the way that Audulus does things under the hood.

Thank you! To clarify, by “keep up with them” do you mean I’m making a lot and you don’t have enough time, or you find them difficult to follow?

I mean I don’t have the time to stay with your rate of work - you’re producing them faster than I can spend time watching them and then spending time on the concepts myself. Not complaining though, as it’s always good to have something ahead of me.

NeuM

@Audulus_Mark said:

@Ailerom said:
I accidentally bought this yesterday, which is probably a good thing, but thank goodness for the tutorials. A lot to watch just for a basic understanding. Such an amazing beast though.

That's awesome! Yes, it is a very deep program, and there's a lot you can do with it, but it doesn't mean you have to do everything that you could do with it. I plan on making some more just plug 'n' play synths that you can open up and jam with also, no connecting anything required.

A “library” of synths as a starting point I think would be a real time saver for people.

espiegel123

I hope it is ok to post this here. This is a preview of a system of modules that I have written in Audulus for exploring similar territory as the early Buchla music systems. I'll be making it available after I make a few more tweaks.

(this is a more sedate and tonal application of the system than I usually explore)

Audulus_Mark

@espiegel123 said:
I hope it is ok to post this here. This is a preview of a system of modules that I have written in Audulus for exploring similar territory as the early Buchla music systems. I'll be making it available after I make a few more tweaks.

(this is a more sedate and tonal application of the system than I usually explore)

Hah I was just about to post this here! So cool, listening to it now

Audulus_Mark

@michael_m said:

@Audulus_Mark said:

@michael_m said:
The tutorials are really appreciated Mark - I just can’t keep up with them though! Definitely helping me out with the way that Audulus does things under the hood.

Thank you! To clarify, by “keep up with them” do you mean I’m making a lot and you don’t have enough time, or you find them difficult to follow?

I mean I don’t have the time to stay with your rate of work - you’re producing them faster than I can spend time watching them and then spending time on the concepts myself. Not complaining though, as it’s always good to have something ahead of me.

Cool, thank you! I understand it's a lot but don't worry, just watch whatever topics interest you I'm about to do a stream soon on matrix sequencers!

Audulus_Mark

@NeuM said:

@Audulus_Mark said:

@Ailerom said:
I accidentally bought this yesterday, which is probably a good thing, but thank goodness for the tutorials. A lot to watch just for a basic understanding. Such an amazing beast though.

That's awesome! Yes, it is a very deep program, and there's a lot you can do with it, but it doesn't mean you have to do everything that you could do with it. I plan on making some more just plug 'n' play synths that you can open up and jam with also, no connecting anything required.

A “library” of synths as a starting point I think would be a real time saver for people.

This is a good idea and I will work on it - there is one that I made as a proof of concept, but it still requires that you plug it in with at least the MIDI input and audio output to work. Can definitely do this though, thank you for the suggestion.

Audulus_Mark

You can download this new Buchla-inspired 5x5 Matrix Mixer over at our Discord now! I'm still working on finalizing the innards and documenting it all, but you can at least have fun with it now!

NeuM

@Audulus_Mark said:

@NeuM said:

@Audulus_Mark said:

@Ailerom said:
I accidentally bought this yesterday, which is probably a good thing, but thank goodness for the tutorials. A lot to watch just for a basic understanding. Such an amazing beast though.

That's awesome! Yes, it is a very deep program, and there's a lot you can do with it, but it doesn't mean you have to do everything that you could do with it. I plan on making some more just plug 'n' play synths that you can open up and jam with also, no connecting anything required.

A “library” of synths as a starting point I think would be a real time saver for people.

This is a good idea and I will work on it - there is one that I made as a proof of concept, but it still requires that you plug it in with at least the MIDI input and audio output to work. Can definitely do this though, thank you for the suggestion.

And if you have some very complex custom instruments, you could always turn them into in-app purchases for a little extra revenue. Ask people here what they'd be willing to pay for.

Audulus_Mark

@NeuM said:

@Audulus_Mark said:

@NeuM said:

@Audulus_Mark said:

@Ailerom said:
I accidentally bought this yesterday, which is probably a good thing, but thank goodness for the tutorials. A lot to watch just for a basic understanding. Such an amazing beast though.

That's awesome! Yes, it is a very deep program, and there's a lot you can do with it, but it doesn't mean you have to do everything that you could do with it. I plan on making some more just plug 'n' play synths that you can open up and jam with also, no connecting anything required.

A “library” of synths as a starting point I think would be a real time saver for people.

This is a good idea and I will work on it - there is one that I made as a proof of concept, but it still requires that you plug it in with at least the MIDI input and audio output to work. Can definitely do this though, thank you for the suggestion.

And if you have some very complex custom instruments, you could always turn them into in-app purchases for a little extra revenue. Ask people here what they'd be willing to pay for.

That's a nice thought, but I think unless we offer some really new powerful node that took a lot of time and money to develop - we might charge for that, it's really Taylor's choice - but I think the plan is for now you paid your $20, you get Audulus 4 and all its updates forever for free

Audulus_Mark

Matrix Sequencer Demo - this patch is pretty intense so it may not run on your iPad if it's older. You can download it at our Discord. Here's an invite link to the Discord:

https://discord.gg/aPkQtDWfUP

Audulus_Mark

https://www.instagram.com/tv/CnfIKoroW4a/?igshid=YmMyMTA2M2Y=

Finished the Matrix Sequencer!

I will make 2 videos - one for how it to use it and one to show how it works.

You can download it now at our Discord! Will be included in a future update as well.

u0421793

What I want is a ‘stop’ button

Too many times I open up a patch and it immediately makes unwanted sound, but there’s no stop button, and as I’ve only just opened it, I’m not going to start looking at every little knob and switch on every module to try and understand what’s making the thing clock through on it’s own, I just want it to shut the fuck up

Then it can begin when I say it can begin

Audulus_Mark

@u0421793 said:
What I want is a ‘stop’ button

Too many times I open up a patch and it immediately makes unwanted sound, but there’s no stop button, and as I’ve only just opened it, I’m not going to start looking at every little knob and switch on every module to try and understand what’s making the thing clock through on it’s own, I just want it to shut the fuck up

Then it can begin when I say it can begin

There is a stop button on Mac at least - you can use spacebar. We added that because you can have multiple patches opened up at once.

However, on iOS, usually the “stop button” is to stop the clock that’s running everything. It’s almost always the leftmost module and has a button that says Run on it that you can toggle on and off.

On the other hand, if you’re opening a patch that’s autoplaying and making an unwanted sound, why not just turn the volume down a bit until you figure out what’s going on?

The problem you may not have considered is that if it doesn’t autostart, then how would you know how to start it? A new user would have the same problem in reverse.

u0421793

It’d need an app-level permission – a single easy to see play/pause button ⏯️ somewhere predictable & always in the same place – all concerned patches can (should) gate their activity from that

Audulus_Mark

@u0421793 said:
It’d need an app-level permission – a single easy to see play/pause button ⏯️ somewhere predictable & always in the same place – all concerned patches can (should) gate their activity from that

I think it would be more likely that we'd just implement the start/stop processing feature that's already on Mac - I'll add it to the feature requests

Audulus_Mark

New Wired Up with Mark!

rheslip

@Audulus_Mark said:

@maschinelf said:
Apologies if this was asked before, but is there any sort of upgrade discount for older versions of Audulus, since I bought Audulus 2 way back.

Even the full price is very reasonable and I will probably purchase it eventually anyway. No rush though since voltage modular is keeping me busy anyway. But yea would certainly buy it sooner with a discount.

We’d love to be able to give discounts but Apple doesn’t allow it, sorry! It would be nice if they developed this kind of infrastructure because it would be good to reward long time users.

A lot of devs offer a bundle with the previous version to effectively discount the new version for their loyal customers. I bought Audulus 3 but it’s gone from the App Store now. I’m sure you have your reasons for abandoning it but as a consumer I feel ripped off - it was not inexpensive.

Not cool.