#192

Is anyone making something like the macromachines storage strip module for use with the mungo modules these days?

#193

There’s nothing quite so direct. The upcoming Harlequins Context from Shakmat comes close; it’s a select bus-enabled modulator. Also some Malekko modules and SDS Digital modules can send on the bus (@ParanormalPatroler I think has the Melisma…).

1 Like
#194

yeah i’m not an expert but every definition i found speaks about simultaneously played samples, i think even the very first compositions with granular synthesis has this ‘cloud of grains’ sound…
but i’m not sure

#195

The Melisma can act as a master or slave, and so can the Harlequin. Funny you should mention, I was testing their interaction just yesterday! Either of those would be able to control the Mungo modules. I did not explicitly test with the d0 (I managed to get a storage strip for that case), but I have tested with the Omnimod and it works.

No idea about Malekko modules that can instigate the change although I do know their sequencers can control the Select Bus. I also know MakeNoise has modules that can act as masters, for example the Rene can control Tempi via the Select Bus. I recently read there is some very basic incompatibility between how MN and Malekko are handling the signals: something to the extent of one requiring a Start message before receiving CC. If I recall correctly the newest Disting EX (the big one) can also send messages on the Select Bus. The previous version, mk4, can only receive messages.

Hope this helps.

#196

I’m impressed by what I know so far about both Melisma and the forthcoming Sequarallel. Some of it I’ve found difficult to grasp, including select-bus stuff. Would you give an example of how Melisma might control a Mungo module? I would guess that sequence and note data for instance can be transmitted but don’t quite understand where or how this ties into e.g. state save/recall.

1 Like
#197

I haven’t had my hands on a Sequarallel yet, but it sure is a crazily powerful design. The Melisma, well, what can I say, the module keeps blowing my mind every day! It’s like having a pianist in 8hp, under CV control. And this is pure praise, no pitching or trying to sell the module at all. I simply love it. It could be seen as a deep module since it has a menu system so some people might find it too complex, but if you feel ok with handling Mungo this shouldn’t be hard to wrap your head around. Different but not more or less difficult. Personally I don’t have any problem working with it, but I worked on the module since day -1 so that’s expected. If you have specific questions I’ll be happy to answer them. There’s a dedicated Melisma thread on lines, where I can answer any questions all day, and we don’t derail this one with me being excited.

In regards to the Select Bus and how Melisma can control the Mungo. I do remember the Mungo d0 has an option to receive MIDI notes, right? I haven’t looked into that at all but I’ll check, so let me get back to you on the note data and if that’s a control option. If anyone else can chyme in that would be great!

As for the actual Select Bus control, it’s super easy. You can use the Melisma to save/load states (call them save locations, programs, states whatever), and each one is tied to all other “states” on modules that use the Select Bus. Up to 64 states on the Melisma, other modules have less. I think the Omnimod has 32 for example. So you can change the state and all other modules will also change state accordingly. The same applies to d0, it can save its state (all on-board parameters) and change according to what the Melisma state is. That is what the Select Bus is essentially: you save states on modules and one acts as a master, controlling when states are changed on all slave modules on the system. When you save a state on the Melisma, the d0 would also save its state. When you change state on the Melisma, the d0 would also change state.

And a bit more detail. The Melisma can assign a different select bus state number on the different programs (chord information etc). You can even assign the select bus state on a customizable CV input and knob, so you can just send CV and have it change states on all other select-bus compatible modules on your system. Here I am controlling the Melisma’s select bus parameter via MIDI from the VCMC, and I’m changing states on the Omnimod, and the WMD SSM, from a single slider.

It’s easy to set things up. Let me know if the above don’t make sense or if you need any clarification.

1 Like
#198

The thing I’m keen to test is Disting EX with recall via teletype ops. I also have a storage strip but because I’ve got more than 3 mungo modules in the case the SS stops working (known fault).

#199

Thanks for the detailed explanation. I can appreciate better the importance Melisma might have in a rack (and Sequarallel too). I can see how saving and recalling states on Mungo modules would be extremely useful, perhaps especially in live performance, and generally massively open up a rack to practically any number of specialised uses.

Still it isn’t something I would really need - this is what I’ll tell myself to keep GAS at bay anyway. :thinking: I enjoy preparing Mungoes for use each time, even with six of them here. I know some have complained about the modules’ scant if any visual feedback or of their not recalling states by themselves. But I find the ranges easy to control and recall with zoom and love that there are no menus to deal with. My main problem is truly my lack of imagination in coming up with novel patches - @smbols’ various d0 patches earlier in the thread were really eye opening. And it never occurred to try g0 in a feedback loop, as @kilchhofer did earlier. Gonna have to try c1 in a feedback loop now.

#200

Yes, MIDI note data is added to the delay offset and time of both channels. It requires a button combo, per the manual:

Tune Button, generates a C4 reference square wave on both outputs. Feeding back this to the A input calibrates the delay transit time for tuned feedback. Holding zoom +/- while pressing this button sets the delay time of both channels to track midi note data.

1 Like
#201

Just wanted to share a video of the Harlequin in action. This will be amazing with a Mungo on the same case, need to try this out.

https://www.instagram.com/p/CHqnmRtBJEf/?igshid=19urn3jozyzjg

https://www.instagram.com/p/CHqnmRtBJEf/?igshid=19urn3jozyzjg

4 Likes
#202

That looks very cool.
So each scene selects presets on select bus? And with that you also get different kinds of modulation from the Harlequins own outs? That sounds very powerful if it works changing presets on the mungo modules!

#203

Exactly, and with each “scene” you get four modulation sources which can be completely different between each scene, but which can be interpolated. The best part is how easy it is to play, as you can see on that video. This, with a d0 will be a crazy thing but I’ll need to finish testing stuff before I can move it to that case and make a video.

This feels more like an extension to the Mungo right now. You change a scene, set your Mungo, set your modulation, save, next scene, etc. Could get really interesting for performance.

I knew about the Harlequin beforehand but it’s more fun in real life than it is on paper! And that says something.

3 Likes
#204

That is extremely interesting. Let us know when you’ve tested this in real life in mungo modules. Are the harlequins available yet, our do you have privileged access? I can’t seem to find any info on release (I’m not a pro googler).

#205

Apologies, I forgot to add a disclaimer: I’m beta testing the Select Bus functionality, and other stuff as well, obviously, but mostly trying to focus on that. The module will be out soon I guess.

My enthusiasm is 100% real though, I did not expect this to be so much fun! :smiley:

2 Likes
#206

This is very cool - can you sequence through presets?

Out of interest I seem to remember the omnimod doing an irritating auto-save every 30 secs when I used it with macro machines storage strip, does it do that with the Harlequin?

I wonder too whether the Harlequin has a hard limit on the number of modules it can work with. The storage strip could only manage to save states for 3x mungo modules. I have 5, this could be the missing link for me.

Keep us posted for sure.

#207

Do these still lack reverse current protection? That’s a major reason I have never bought them (as well as the greater occurrence of issues involving electrostatic charge).

#208

The latest module (c1) and at least the latest revision of d0 are reverse protected. Owing to carelessness, I once blew up two mungoes and had to send them off for repairs. :see_no_evil: A real waste of time and money. Now I double check ribbon orientation every time. I think the need to make such checks is less of a chore than it might seem, especially for the pleasure of using these modules.

#209

That’s good to hear, it’s not out of annoyance at having to check that I wouldn’t buy them, it’s just that I don’t trust myself… at all. There is a 100% chance I would 'splode the module the first time I put it in a different case.

1 Like
#210

Last time I met with John, C1 ans D0 weren’t reverse protected.

#211

Thank you for this. It prompted me to dig up email correspondence with John. I found the following: In an email dated 8th August, he stated to me that c1 is reverse protected. If this contradicts what you’ve heard from him, it is of course best supposed that it isn’t protected, just in case.

In further correspondence dated 2nd September, he mentioned that it is the MIDI connection on the modules (presumably all of them although he wasn’t explicit) that cannot withstand reverse connection, and that if it is isolated the module goes undamaged.

Reverse protection on d0 specifically wasn’t mentioned, and therefore I misremembered it. I’m sorry!