Cherry Audio Forums

VCO2 - double click fine tune for default goes to 0.06 not 0. VCO goes to 0. Is this a defect or a replica of some behaviour?

Have you had a look at the SynthVoice module?

Happy to report 2.0.17 has apparently fixed this issue. Thanks CA!

VM is just brilliant. All the recent clearly hard work is so much appreciated.

Now all we have to do is move to Discourse and my happiness will be complete!

Linux kernel numbering is such that an even minor version number is stable, and an odd development. Thought you may be following a variant of that. [It's not that I was wondering what happened to 2.0.16.]

Hi CA. What is your release numbering schema? Seems you only release on odd dot dot numbers. This is common in open source, just wondering if you follow this convention. Some people may wonder what happened to 2.0.16.

From September 2019, but nevertheless of interest:

https://happymag.tv/modular-for-the-new ... rry-audio/

The About page on the website is entirely impersonal, so it's nice to put a 'face' behind the company.

Google bots take a while to crawl sites. Give it time. i would not regard google as the primary index for CA docs, though, in any case. You cant force google to update for your site changes. You just have to wait. Sometimes quite long. With a trillion pages to index, it's quiet complex.

Yes, Andrew said to me he is fixing that now.

Testing my module development. on WIndows 10 if I minimize VM for half an hour or so and then bring it back, all signal paths are dead and everything has stopped. Only restarting corrects this. Happens on two very pristine Windows 10 systems.

Am I alone in observing this?

Clock signals as gates from various sources are of varying quality and shapes, and do not necessarily instantaneously rise from 0.0 to 5.0 volts, even though digital. What general techniques do you use to do rising edge detection on such gate signals, or indeed square wave output of LFO's? The obvio...