Clouds Parasite: an alternate firmware for Clouds feat. the Oliverb and Resonestor

@AXXON I notice it occasionally too. It sounds to me like the CPU can’t keep up with the current computation. When I understand interrupts on the STM better I’ll see what I can do, but it’s gonna be a difficult one I think. Did it happen at all in the default firmware?

pichenettesmqtthiqs ok, I guess I’ll try now! thanks for the feedback!

@rumpelfilter cool, tell me what you think!

I didn’t spend a long time (have spent longer with Parasites) but I think it might have happened in the original software, it’s rare, but super annoying if you’re recording because it’s really out of place and noticeable

Additionally my setting are not being saved on shutdown and re-power. Blend/Dry_Wet fully off powers back on Fully On 100% wet.

@AXXONN I found the same thing with the Wet/Dry knob with the standard Clouds firmware.

a|x

If the problem you report is the following: when you press the pushbutton to select the function of the blend parameter, sometimes the module freezes for half a second… Then it’s normal. This setting is saved to flash memory, and once in a while it is necessary to erase a page of memory to save the setting. There is no solution since the processor is completely frozen while a page erase happens.

@pichennettes and that’s would result in a small audio glitch/beep in the audio?

Still wondering why when I power down my modular (blend dry/wet at 0%) that when I power on it’s at 100%?

> and that’s would result in a small audio glitch/beep in the audio?

As I told you, the module freezes for half a second, so you get a glitchy tone for that duration.

> Still wondering why when I power down my modular (blend dry/wet at 0%) that when I power on it’s at 100%?

Because I’m an idiot.

@pichenettes you’re definitely not an idiot, but does that comment mean it’s a firmware glitch, that may be fixed in an update?

a|x

It will be fixed at some point. But to me, not important enough for an update.

Olivier, if you have the patch you can send it to me I could include it in the next version of Parasite.

@pichenettes thanks for confirming both of those, good to know.

The last 3 numbers of my serial are 218 .Should be ok to install?

You should be fine yes: Olivier mentioned that units < 020 could have problems. It’s not your case.

Thanks mitthiqs .time to install (fingers crossed) :slight_smile:

Well i took the plunge and installed the alt firmware …bingo all went well Thanks MQ for these super additions to an already incredible module :slight_smile:

Yay! Have fun!

me too, all good - thank you very much for a great update!

Hello guys,

To begin with, I need to say that I did not calibrate Clouds after I did the firmware update. (1.3 Parasite)

I have a very glitchy sound on Oliverb and Resonestor regardless of the settings. I also have this issue in the default looping delay mode, where I can’t get a clean sound. To be honest, I never tried the looping delay before I updated to parasites so I do not know if I had the problem before updating or not. In doubt, I’ll post there.

This video shows what I get with Oliverb. It starts with a dry signal only (using Blend 1 knob)

Could calibration solve this ? Or is it a different issue ?

Thanks for your help.

> Could calibration solve this ? Or is it a different issue ?

Definitely a calibration issue! There’s a quantizer on the Disting, with a bit of trial and error I’m sure you can use it to calibrate Clouds.