#101

ah ok thanks, makes sense!

have you tried with different clock sources? i had the same problem when i used a r*s ssg as clock, it was jittery and the d0 picks up the slightest variations, however when i use my main clock from the e-rm multiclock i have no problem dividing it down.

#102

I’ve tried every module I have that can produce a clock (Batumi, Noise Tools, Time Wizard, Dixie, EOC out of Miasma, Disting, SQ-1) and so far they all cause the jitter on divided clocks. Tried attenuating them first, too, but that didn’t seem to do anything. I wonder what it is about the e-rm’s signal that’s working better for you.

That being said though, at these ridiculous lengths it is best suited as a looper like you said, so turning the slew all the way down and not messing with the time is still totally fine. I’ve been using it that way this week with a Three Sisters and Tallin in the feedback loop and it sounds so good as the repeats slowly degrade.

#103

ho,
may i ask how do you mean wav a 500 000 samples?
just put all the samples behind each other to make a long sample?

thanks a lot for your music
recently played some of your sounds at a tiny festival and it was just magic

#104

thanks, that’s nice to hear!

500’000 samples as in smallest unit of audiolength. the g0 is sample rate insensitive, that means 500’000 samples can be appr. 11 seconds IF the audio file is at 44100 Hz sample rate (500’000 / 44100 = 11.3…seconds) if you lower the sample rate the audiofile can be longer, with higher sample rate the audio file gets shorter. that means you can for example load a 2.5 seconds long recording of a bat recorded at 192 KHz but then “downsample” it with the g0 to hear the bats artefact free.

on the sd card you can put 10 wave files, W0.wav…to W9.wav. i have quite a few very small sd cards, 250 mb or so, the g0 isn’t designed to change audiofiles fast anyway, it always needs time to load the file into the buffer and you hear that loading process, so changing on the fly isn’t really it’s strength!

#105

that’s really weird, i wonder if it is the internal clock dividing or just the slow clock in general? if you clock it with a really slow clock without dividing it, does it behave jittery too?
i just wondered how much longer the delays could be if the modulation inputs all have 10v offset plugged in, must try that, maybe it gets quite a bit longer that way…

#106

seems to just be the internal division. If I send it a slow clock it sounds fine if I have the time knobs anywhere left of noon.

I hadn’t even thought to try and send it some offsets to stretch out the time, but yeah I wonder how it’ll respond to that.

#107

Just checking, anyone keep getting white/digital noise from the mungo?
If I turn plug in enough feedback to have an effect I get quite an amount of noise.
I read that the slew has an effect on the noise but I can’t get rid of it for the life of me.

#108

Probably coming from the modulation inputs. If nothing is plugged into them they can pick up noise that has a pretty profound effect on the sound, hence why the slew can help, smoothing out the modulation inputs so the noise can’t have as drastic an effect.

You can try zeroing out the modulation attenuvertors, which can be a little difficult since they’re so sensitive, or plug dummy cables into them and that should get rid of it.

Also worth pointing out that the d0 doesn’t have a filter like pretty much any other delay would (to remove this type of noise or noise from the clock), so if you’re working with a lot of feedback you might want to try some filters in your path too.

#109

I’ll try the dummy cables. Also, I do notice a small effect with a certain slew setting but any recommendation on how much I should take it CCW?
For feedback patching I’ve used filters but for “normal” delaying not really.

#110

Depends on how strong the noise signal coming in is, but I typically find the noise stops being an issue between 11 and 12 o’clock. But I always make sure that I turn the modulation knobs close to zero when I boot it up, so the noise is already lessened.

#111

This video makes it look like d0 could output a stable 90 degree phase shift of an arbitrary waveform by clocking to the input signal…

So it could be used like a Dome filter as part of frequency shifter!

Other ingredients: a quadrature VCO and some 4-quadrant multipliers. I’ll test it out this weekend with Polaris or Shapeshifter as quadrature VCO and Blinds as multipliers. Blinds should provide enough multipliers to achieve both up- and down-shifting for barberpole effect. Has anyone tried this?

4 Likes
#112

I have not tried this but I’d love to hear what you get and try it out myself. Can you explain the full patch in more detail?

#113


or
https://www.muffwiggler.com/forum/viewtopic.php?t=81591

2 Likes
#114

Could someone give me a hand in using the midi program changes and how to play the D0 with midi?
I’m quite lost in how to save presets and to send midi note data to it.

#115

I will lend a hand just as soon as I can get my d0 responding to save messages at all :frowning:
Pasting my email to John here in hopes of someone having had this issue before me:

My d0 is reacting a bit strangely to my new Storage Strip. Hopefully you can help me determine which module is the culprit!

My understanding is that the d0 stores internal save states for the whole state of the module’s controls (or at least the 6 knob positions; I am unsure regarding whether the DC cut, A+B mix, or any tuning functions are meant to be saved). The Storage Strip gives MIDI messages over the select bus correlating to “save slot X” and “load slot X” for 16 such slots.

My d0 is apparently not responding to save messages. The load messages for slots 1 and 2 of bank 1 load a really short delay for both A and B, but all the other 14 slots load with the tuning hum active! Pressing the tuning button stops the hum.

I also have a new Dynamic Destiny which is responding appropriately to both save and load messages. So it appears that the save messages are getting sent, which causes me to suspect the d0.

Anyone had these issues? The module works fine otherwise…

#116

Fixed, apparently you must hold the zoom + while saving!

#117

how steep is the learning curve with d0 actually? I’m eyeballing one, but slightly afraid that i would just find in too cryptic… is one still able to satisfy ones basic delay needs with it pretty easily, or does everything require long and patient manual studies?

#118

I think the curve with it is pretty exponential as in, once you understand the fact that you have to patch most things outside of the module, it actually opens up 100x more options for how to mess with the delay chain, specially in the feedback path.

I spent a day trying to figure out why it only introduced latency on my signal before learning, on this very thread, that I had to patch the feedback path myself as well as the dry/wet signal.
In a way, it’s the most modular delay I’ve used, the problem was, I wasn’t used to that concept.

If you really just want a delay, I’d go for something more like DLD, which is pretty deep but in the more traditional delay sense.(Well you can do some crazy looping things)

1 Like
#119

Some aspects I failed to fully appreciate before getting the d0:

  • Buffer playback is sped up or slowed down to follow a changing delay time, creating Doppler pitch shifts only while the delay time is changing ala tape echo. It is not possible to achieve buffer-length-changing “looping delay” ala DLD, nor constantly-pitch-shifted echoes ala Echophon or Magneto in shift mode.

  • There is no quantization of time ratios when you are clocking externally (i.e. you must dial in synced echos by ear). This is where DLD shines.

  • The V/O inputs are very nearly misnamed: they track X volts = 1 octave and to achieve the expected 1 volt = 1 octave involves tedious adjustment of the attenuverter until X = 1. Essentially a calibration. This must be done every time you want 1V/O tracking unless you save the settings using the Select Bus. Or just clock to an external VCO like I do :slightly_smiling_face:

  • The V/O input attenuverters have gain and will amplify noise at an empty V/O jack unless you close the attenuverters.

  • The state of all 6 knobs is set via Mungo’s ingenious zoom system (familiarize yourself with this demo). The 2 HP zoom expander should be considered mandatory. Or you can use the zoom buttons on a Storage Strip. Or you can drill a hole and put the zoom switch right in your d0’s panel :slight_smile:

  • Slew setting is critical to achieving your desired sound at low noise. When I say “noise” it’s usually the crackly type; d0 can crackle but it can also HONK :anger::duck::anger: if you make a big, sudden delay offset. Both delay channels share a slew setting but nothing’s preventing you from using external slew rate limiters on your V/O signals.

  • Mungo modules are incredibly sensitive to ESD! The MW thread is a long saga of dead d0’s. Combine that with the d0’s tendency to straight-up not make any sound at extreme setting combos (which you will find quickly as a noob) makes for some scary “did I kill it?” type thoughts.

If none of that is a deal-breaker, then I wholeheartedly endorse the d0 for your delay needs!

8 Likes
#120

Wow this was really helpful, thanks. What would you say is the main thing where d0 really shines, compared to your conventional delays? Physical modelling seems to be the thing, right? I am not actually looking for “normal” delay that much… but rather a tool for experimenting and soundscaping …