#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!

#212

Yes you’re right, in doubt, best to assume they aren’t reverse protected. :slight_smile: Maybe he revised his hardware since I spoke with him (roughly 8 month ago)

#213

How are you getting on with the Harlequin… managed to pair it with mungo yet?

#214

I actually haven’t put it in the case with Mungo at all, sorry, I’m focused mostly on using it with other Select Bus modules as I’m still working any kinks out of that functionality.

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?

The Omnimod does that regardless of whether you’re using a master module or not. It does that by default, whenever you change any parameter/value on it. So the answer is yes, it does it with Harlequin, with Melisma, with anything really.

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.

Hm, to be honest I don’t know but I don’t see why there would be a limit. I have the Storage Strip in a case with three modules (d0, malekko quad vca, Disting mk4) so I never reached that limit. Strangely enough with the Melisma it was also less than two modules (Omnimod, SSM), but I can’t see why it would be an issue with 5 modules. The message should travel in the bus and reach all modules plugged and ready to receive.

:expressionless: Now I need to check!

Sorry for being late to respond, too many balls in the air lately!

2 Likes
#215

The issue with adding more modules to the bus is that each module’s input take a certain amount of current to reliably drive, and the Storage Strip could not source adequate current to drive >3ish modules. When this happens, the signal voltages sag and can cause communication issues when they do not reliably cross certain thresholds.

A truly frustrating design decision :expressionless: My “fix” is to use the second bank of the Storage Strip so the Omnimod autosave isn’t constantly overwriting my first slot.

1 Like
#216

bumping this thread for a minute to take the pulse of c1 users (@desolationjones? @Net?)
still digging it?

i’ve recently gone down this rabbit hole lately of using ableton’s vocoder on my set’s send and processing a bunch of guitar loops on multiple channels, and then using a channel at random as the vocoder’s carrier…so really less for true vocoding and more for spectral processing i guess. perhaps it’s also worth a mention that in this paradigm i have control over the vocoders formant as well as the w/d mix via m4l lfos…

so this got me to thinking how i’d really like to incorporate something similar in my euro rig. true vocoding seems to run big and expensive and power hungry, and i’d prefer not to go that route…so i landed scoping things like warps, but also c1 and v0.

anyone feel like weighing in on the benefits of c1 or v0 over the other for a set up like this? leaning towards the c1’s live convolving, but v0 seems like it would also yield interesting results, except theres just so few demos of it out in the wild (whereas c1 demos from mungo as well as here in this thread seem to scratch the itch)

anyway, either is a bit of a plunge cost wise, so i’d like to see if i can narrow down their usefulness as much as i can before taking said plunge.

#217

I do hope someone here is able to weigh in a bit on v0. I felt that John’s two demo vids give away tantalisingly little about its spectral processing capabilities, at least from my perspective.

I’ve found c1 to be a serious mangler, capable of a quite baffling range of results thanks to the available parameters. The bucket-brigade delay is fantastic as well, like a gritty d0. Some of its spectral processing can be very nice; I’ve been enjoying some of that lush muffly stuff that sounds a bit like compressed MP3s. Very into that at the moment. The module doesn’t entirely scratch my FFT itch though when compared with e.g. DtBlkFX, mmorph, Ableton’s vocoder or, outside DAWs, that enormous resynthesising Rossum eurorack module for instance (I nearly impulse-bought that one a month ago despite having no rack space for it; silly GAS). But the live convolution is always interesting and always weird. I love the module. My long journey of morphing choirs with field recordings continues.

A downside of c1 is that the output can be very complex and difficult (for me) to EQ.

Edit: I’ve not much tried using c1 as a vocoder, and would like now to give it a go. If I succeed in producing any useful results tonight, I’ll share them here.

2 Likes
#218

uh, yes, hello. this is exactly what i am after.

and this is currently how i am doing (or trying to) said thing.

thanks for the insight!

3 Likes
#219

I’ve had some good results with this by convolving a signal with itself. I’m about to try it with an LPF in the feedback loop.

A crude and no-budget and quite fun way to do this, which I’ve little doubt you’ve thought of already, is of course to use actual MP3 compression! Occasionally I’ve used audacity to create e.g. 16kbps MP3s for sampling.

But one appreciates being able to do something like it in real-time as well. The Rossum module sounds amazing at this from the demos.

You’ve got me all fired up for Mungo action. I was just reacquainting myself with d0 last night as well. I hope I finish up with some c1 recordings worth sharing here.

2 Likes
#220

yup, totally. my go to for that in audacity, when i’m not concerned about live processing (which is the goal in the case of the c1) is to use a brutal amount of noise reduction with 2 (or fewer, depending) frequency smoothing bands. instant ‘double digit’ encoding sounds.

the rossum is great (so far, anyway…i haven’t done a super deep dive of it yet) but it has the tendency to get really…mmm…same-y? whereas elsewhere you aren’t limited to just a single (and fixed amount of) waveform(s) at a time and more of the source harmonics travels through (and perhaps this is still an achievement left to be unlocked for the rossum, more experiments are required there)

but yes! and demos of it in action, especially in the vein of what we are getting at here would be greatly appreciated

1 Like