Cracking the Code on Complex Guitar Pedals

Thanks for the heads-up regarding the Looper post. It’s fixed. The simplest approach to a switched input is a crossfade node with a trigger attached to the “c” input. Set the trigger to toggle mode. When the trigger is high, input b will be connected to the output and when the trigger is low, input “a” is connected. In your case, connect your input to “a” and the output to the delay. When you switch the toggle on, your input will be disconnected. Of course you can group the Trigger and Crossfade if you like.

1 Like

I’ll take a look at syncing the reverse delay. I’ll have to see how @biminiroad approached it.

2 Likes

We’ve Got to Go Back 2.audulus (197.4 KB)

Lot’s of potential with the Flux Capacitor module! :zap:

(I was just playing with the gain staging on my Apogee Jam interface, the volume on an iPad, the level out on the module, and the output volume. It seems like getting a lot of this right on “guitar pedal patches” is important. I highly suggest lots of adjusting in Audulus; headphones vs. speakers will make a difference, wet/dry levels. I think we are all used to having things mastered but I would treat most Audulus patches like a guitar and amp where you are always trying to dial the tones in, especially with other people’s patches.)

3 Likes

Deleted original entry here. Just looking to make some sweet spot presets.

The real challenge is metering. Ideally you want the level into Audulus at about -6 dB or so for the peaks. Unfortunately Audulus is a bit lacking in the metering department. I build some VU meters but they’re a bit of a hack. They might help anyway
uVU meter mono V1.1.audulus (12.7 KB)
uVU meter stereo V1.1.audulus (24.2 KB)

2 Likes

I am just going to go ahead and keep moving simple, mainly because I want to figure out the best way to use Audulus in a looping scenario — trying to work from strengths and see what could be considered. As more modules get hooked together, particular workflow challenges arise. Here are a few:

I think that it is really nice to have very few features baked in, but lots of availability for adding them as needed. So I like how the clocking is all being done in the patch below. At the same time, while the way the rec/play/dub button on the looper module works is very clever, when I use the gate input from the clock for a count in style transport, it ends up then switching back again. (It will make sense when you see the patch). I feel like there are several possible solutions here but I am wondering which way you might approach it. I am wondering if there should be a “one shot” feature with a count selector baked in, or should I just put a one-shot gate between the bar gate from the clock and the gate input on the Rec button?


Looper patch #1.audulus (778.7 KB)

Also, any thoughts on the audible pitching when the delay time sync knob is shifted among the division parameters? It would be nice to get a clean snap.

I’m not sure exactly how you would like it to work. I chose the record/play/dub since it was similar to a hardware looper pedal but it could certainly be changed. The pitch shift when changing delay times is pretty difficult to get around. In fact it was the biggest challenge in building the looper.

1 Like

I really like what you did. I think it is a matter of plugging in a guitar and trying the patch out. My challenge is a very simple and could probably be augmented with tools/modules we already have.

Syncing is really important. It’s important in the sense of wanting to get a loop to start when the clock starts but then also play back in the next measure. I mean it’s damn close and exciting as hell.

I thought a one-shot gate between the whole note output on the clock and the Rec/dub gate input on the looper might make it possible to fall into perfect alignment without inadvertently retriggering the Rec/dub button when the whole note gate fires again.


But then I also realize that one would probably want to get that to flip over to play back. It’s not easy to describe. But functionally, what I have done in the past is physically disconnect the clock output from the looper input before it cycles again to stop it from unwantingly flipping between modes.

Is there such thing as a 2-shot?

I think in a looper pedal you can put it in a mode where the Rec/play/dub button simply quantizes to the measure, so you can hit the button within so many seconds before it starts dubbing again, but it will delay that gate until the perfect moment when it actually does.

I believe the Jam man and the boss loopers do this. Why does all this matter? I can produce whole tracks in audulus without using a daw at all. I think that makes your looper entirely unique in the industry. How’s that?

  • again, I think it’s a challenge with maybe 4 or 5 possible solutions but a couple will be really key for the user.

What about a separate tool that allows a person to create a count in for the looper between itself and the clock, but also set the loop length by utilizing the master clock bar gate outputs?

Just thinking further, one issue with a count between the clock and the Rec/dub on the looper is it would put the looper 4 or 8 beats out of alignment with the clock measures. Alternatively, you could put a count in ahead of the clock and looper hooked up the start and Rec buttons, respectively. Again it may just be a matter of trying it in the patch above to see what I mean.

With a counter you could have a clock out on at any specific beat. So maybe the first pulse at say 4 beats the the second 16 later etc. I’ll put something together with say 4 outputs. Let me give it some thought.

2 Likes

This technique has been shared before. I find in Audulus one needs to tweak a lot to get the sweet spots, so it might need to be adjusted for you setup. It’s @stschoen’s Audio Gate controlling a VCA with an envelope. This gives that pad-like effect where you have a slow rise attack.


Ambient Guitar.audulus (134.2 KB)

Episode 2? “Not only can you save your loops but you can save the whole layer stack.”

Just gathering tools. Pitch shifting with Wormhole.


Horray Wormhole.audulus (214.5 KB)

My God Wormhole!!!.audulus (225.1 KB)

1 Like

Here’s a multi-trigger you might find useful. It counts the incoming clock and gates it through on the count selected. There are 4 outputs each of which can be set to 1, 4, 8 … 64 counts in multiples of 4. The counter doesn’t loop. Clock and reset inputs and 4 trigger outputs. Let me know if there are any modifications you might need.
Screen Shot 2020-03-06 at 8.33.16 AM
Multi-trigger V1.0.audulus (24.4 KB)

1 Like

@J031 has officially tipped the scale. By eliminating some pesky clicks, IMO, he has managed to provide a module so wonderful I think Audulus may be the front runner :running_woman: for guitar :guitar: pedals today. Wow.

Again keeping it simple to expose the large possibilities with very few connections. Plug something in, even just speak into your device.

Wormhole Cracks the Code.audulus (329.6 KB)

In the patch, feedback is turn all the way down, because I get a static crunch from my audio interface when I open a patch. This way the jolt doesn’t get caught as an infinite loop. So crank the feedback all the way to initiated once you are in there.

2 Likes

I am just discovering this myself with my new rack with the couple modules I put in it, the MOTU m4, and the Indio (Telecaster style) guitar I bought on sale from Monoprice. I am so glad that I listened to the advice of my peers here, and stuck with the bare minimum, rather than blowing my whole savings account for a bunch of stuff I now have the knowledge to explore and create with.

The only thing left which I may buy is the EuroBuro module for my rack from Empress when that comes out officially for everyone. That thing is beyond sick, but that is down the line and really a whole other discussion.

My point being that you are absolutely right, and if people have access to a computer or iPad/iPhone can save like $10,000 over buying the hardware versions of what we build to use case all the time. Some of the stuff just can’t even be done with hardware, and vice versa, but I think the favor swings far more toward A3/A4 coming vs. hardware everything. :slightly_smiling_face:

Wow! Thanks for the compliment.
I’m glad to hear that you like it :smile:

1 Like

I would suggest an ES8 used — I have seen ES9’s used. I think you might enjoy Audulus more as a tool. I am hoping @taylor has got his head around 2 way Midi for Audulus 4. The the Might Fighter Twister and the MIDI Fighter will give us some nice hands on control with colour feedback.

With this setup the you get loads of ins and outs and access to a desktop controller with a touch screen interface for node based routing schemes.

Obviously with the combo you can control your rack through the es8/9 with a midi controller. Seems to me the real question has to do with managing cpu. The nice thing is people are still buying phones which will improve the chips, without dating the other devices.

1 Like

Yes, this is an issue I have found myself running into from time to time, as I didn’t think to upgrade the CPU when I bought my iMac ~2 years ago. It has run up against the limitation only 2x I can recall recently, but it was enough to make me start looking at what kind of hardware supplement I could get to take places with me, in the event that my iPad Pro and my older (and nowhere near as powerful as the iMac) MacBook Pro choke on what I am trying to do with software. A hardware supplement that can do some of the Audulus work for $500 is not a bad deal, IMO. I dunno if you have watched the videos of the ZOIA (guitar pedal version of what will be the EuroBuro) and there is like nothing this thing cannot do.

Also, I don’t want a $500 sound card, at least at this time, which is why I ended up going with the MOTU M4, and it has 4 of each DC coupled ins and outs, which I figure will be enough to help me to understand if CV I/O is something I will be using a lot. This saved me from having to blow the big bucks on the ES-8/9 (although I did think ahead and bought the CRE8 Audio rack starter kit, as it is deep enough to fit either one of those sound cards, and really not much can’t fit in it, if I am not mistaken, it is almost 60 MM deep!). :smiley:

1 Like

TBH, some people buy the intro things and then decide if they like a hobby. Other save and save for the red bike in the window. You can spend a lot getting “deals.” Also remember, you can move gear on reverb. I sold an Analog Four I bought a year ago and made $200 on it. Then I found a digitakt floor model for $200 less than new. It only took me 4 days to sell the Analog Four.

I didn’t realize the MOTU had 4 ins and outs for cv. That’s good. I am sure you will figure all that out. One thing I would say is, for me, mostly the key seems to be understanding what I am doing. This is why I am more taken with @stschoen’s array of FM/PM synthesis modules than I am with, say, the elektron model:fm synth thingy. That is, I spent hours and hours trying to figure out how it all worked. Seems when you know what’s going on, you hear more in it. @RudigerMeyer’s work on Hordijk’s stuff is a great example of this. At the same time, I wish I was working harder at the techniques, getting quiet and digging around in Audulus, but not necessarily opening the modules to look at DSP algorithms, but remaining at the level of simulation, so that I understand “synthesis” no matter what gear I am using.

1 Like

I had posted some videos on Dark World from Chase Bliss Audio on a reverb thread, but this video from Knobs has me inspired to try some things. For me, the forum is like a scholars library where things are underlined in books. So to work on something often involves reconsulting these threads and building out ideas. Kind of strikes me that this is very new territory — to be so digitally equipped. To go back to an idea from a year ago and be able to read what was thought.

Just collecting and appreciating, drifting along with Knobs. So nice :slightly_smiling_face:

I think what has occurred to me just now, is that it isn’t so much a special algorithm, it’s more about experimenting with node logics (by node logics I am thinking broadly of Deleuze and Guitarri’s rhizome) getting character and movement out of the reverb.

But that’s a lot of talk. I just looked at the patch a few posts ago. That oscillator bassline was an interesting idea but did not quite fit the mood. So I just deleted it from the patch and went simple. Kick, hats, looping ukulele with effects. I am trying to make the case for how easy it is to create some soundscapes with some looping and delays in Audulus — this one with the Flux Capacitor. Love how I can get some FM tones out of a ukulele.

https://soundcloud.com/futureaztec/looper-experiments-1-1/s-lwvQ7

Looper patch #1.audulus (1017.8 KB)

  • looking forward to getting home and working on something much better — it’s a private share. It’s okay to share ugly drawings.:rofl:
2 Likes

Had to…rhizome…