I ported Bidoo modules

Bidoo as per request of @offthesky (speaking of, Bar does sound really good, but a little CPU heavier than I’d like around 33%)

You must be on v2.0.0 dev12.2. - no earlier versions will work

Download here: Bidoo - MetaModule - Google Drive

A couple modules are missing, mostly the giga large sequencers and samplers due to some technical limitations.

I also had to tweak Spore to use fewer grains, but it still sounds pretty good to me.

6 Likes

awesome and im p sure i can speak for all of us here, we really appreciate u doin’ the lords work here! but yeah that’s too bad bar is such a hog. it just motivated me to do a quick dirty shoot out with all the stereo comps under the ‘compressor’ tag in vcv(im subscribed to all brands so i think i caught them all here), and with my cpu turned down to 0% in windows so i can see a better cpu usage range in vcv, i found the squinky labs one to be real winner in terms of sound/cpu usage:

i never actually noticed the squinky compressor before this, will be using it from now on i think. always just used bar as it sounded really smooth. but the squinky one is sounding just as good if not better to my ears.

i will add that bar handles extremely loud signals better than squinky comp (and still sounds good) so maybe a better smooth limiter there for wild feedback, whereas squinky one- after you push so much into it the volume out just increases to suite (in my patch, i changed the airwindows purest gain to a bitshift gain which pumps out very loud signals). dynamo and manic compressor both sound v distorted with that much gain into them.

also im noticing the mono “dimit” by wildergarden (added to the library quite recently, a couple weeks ago) is handling super high input gracefully without distortions(unless you turn up the grit knob of course) and yet very low cpu. i even duplicated the bitshift gain into this one and it still sounded good. this one could actually be the best ive seen for big feedback loop experiments.

vcv comp limiter test.vcv (3.5 KB)

just attempted a little extreme gain test with dimit:

wildergarden dimit extreme gain test.vcv (2.3 KB)

seemed to hold up w very little cpu usage

looks like he’s using a [GPL-3.0 license]
https://github.com/ArdenButterfield/wildergarden-vcv

so possibly maybe we could see it for use on mm one day :]

1 Like

Ok it’s on the list, thanks for sharing!

Squinky I was working on for a bit, but they have a ton of menu UI elements where you need to click and pick an item from a list, which will require a bit more work to translate to the MM.

1 Like

awesome ty for considering! even though it has no controls, dimit seems to really be smooth sounding(unless turning up the grit knob)

and squinky would be great to have too. looking fwd to those one day!

any chance of getting the Bidoo OUAIve to work?

the sample players in the bidoo line are actually really great!! some of the first ever in vcv. been using Canard like crazy for many years now, mainly via veeseevst (a not well known pre vcv 1.0 vst plugin)

1 Like

Let me try. I think doable.

Bidoo includes sequencers inspired by Intellijel Metropolis (dtroy and bordl)

I think OUAIve is working, and I got Edsaros in as well. Will slowly chip at the other ones.

If they crash after a few samples playbacks let me know - I should’ve fixed those up.

Grab the updated one here

https://drive.google.com/drive/folders/1pH9xZ4PtMvs-GsWywfCMbih0dmzHGvrr?usp=drive_link

thank you! I’d have a go today. yes they load now in MM and I used one kick, one snare and one hi-hat as samples playing. they do play fine for a while but if I start making edits to the parameters, i.e. clock divisions going into OUAIve, the screen froze [is that a module induced crash (MM CPU was like 34%) I’m not sure] and the only way out is to reboot the modular case.

EDIT: after more attempts the patch plays and freeze without my inputs. YML below.
Time is Up.yml (14.5 KB)

1 Like

Great thank you. Taking a look. I fixed some crashes with edsaros but didn’t see similar behaviors in ouaive yet, but I’m sure there are issues.

edit: @Starscream I updated it again, I was messing with your patch and a standalone Ouaive, it seems fairly stable to me. But it does crash when I turn up mult/div #6 all the way up, even with no samples loaded. I think if you feed insanely fast clock to Proteus’ new sequence jack it crashes, which might be a separate issue. Perhaps we don’t need audio rate new sequences? :smile:

Uploaded again to Drive.

@offthesky

Give Canard a go as well, it’s also in there. Really cool that we have an auto slicer now, it works although sometimes not as sensitive as I’d like (maybe I can adjust that threshold)

Also unfortunately, since usually you need a mouse and keyboard to interface with it, add slice/delete slice doesn’t work. But maybe still useful for you?

Audio rate sequences beyond human hearing, what a neat concept!.. but yes point in case we won’t need it. I have removed the Nano Performance Mixer to cut down CPU and it seemed to work a little better. However, instead of screen freeze, now I get a case shutdown (entire case went into reboot). I am using 4MS POD 64X.

gave it a shot, i can load a sample into the module and see the purple waveform (in the modules’ param view), but when i hooked up the bog llfo to the gate input (In4) of canard, nothing happens. whereas in vcv, the llfo into the gate input causes the sample to play no problem

- canard test.yml (1.8 KB)

also thought maybe it could have just been the sample so i tried loading a few different samples. after about the 3rd sample load attempt, the mm froze. these are not large samples, at most 4mb (all 48khz/16b)

That is really unexpected. I don’t know if anything that could cause excessive power draw like that simply from the code? It would just cap out the CPU I thought

Hmm, yeah that sounds very wrong.

Thanks for your patience, looks like these are expectedly trickier to get right. However, I am seeing something weird - in VCV rack I also cannot get the sample to play with an LFO into gate. Could you share with me a VCV rack patch?

I thought it was working as intended because of this.

edit:

@offthesky - I actually think there’s a bug in the VCV version. If you start with a voltage source connected to the gate, you are never able to get it to play. I actually managed to fix this in the MM port ironically, I will push a fix update in a bit.

regarding the sample crash, I can also crash the MM if I pick an audio file with a non supported extension, like an mp3. Do you recall/can you share the sample that crashed for you?

edit2:

Safe version of Canard hopefully! I fixed a VCV rack bug lol and also added some guards to prevent you from loading in non-wav or non-aiff files. If you broke it with anything else let me know.

My initial thoughts too, i.e. should be hardware, power related (though it ain’t the first time the case rebooted). I have a different case coming so I’d make sure to try that to self-satisfy what could be the issue. The other thought here would be the dev firmware but it ain’t official release.

using

awesome this seems to be working ok on the mm now! i look forward to testing the module out in full soon.

here’s the file i loaded before that causes the mm to freeze. i just tried loading it again and it seemed to play for a second then the mm froze:

is just a stereo pcm signed .wav file, 48khz, 16b. nothing fancy

edit:

ah yes i am now noticing this in vcv… trying to get samples to autoplay on patch start. but super cool it will work on mm! def what matters most here imo

playing around with canard some more, im now noticing the gate isn’t working at times: i hooked a 4ms atvert (with offset all the way up) module with gate out to the gate in(in 4) of canard and when the patch loads, i see the sample wave form in the display, and the bar scanning across it, but no audio is coming out of canard’s L/R out
- canard 1x test.yml (1.5 KB)

also with the EOC out on canard hooked up to the trigger in(in 3), on mm it doesn’t seem to work to create a loop (but in vcv this does work and the sample will loop)

It looks like you are porting a ton of modules. Any way to incorporate them in the MM repository? Maybe that is a question for @danngreen.