Cherry Audio Forums

A while ago I started to use MIDI in VMD and got sticked. Your Beginner's guide helps me to reinforce my former try.
Thank you, Collin.

Roland

I could also see see that even reloading the image or replacing it, lets "image(..)" count up.

As utdgrant mentioned VMD seems to not use real image file name internally.

Hello Colin, thank you for creating MIDI Trap beside your project and giving it to LSSP XL users for free. This module is very helpful. Since Dec 2022 I'm also working on a big VM project. But for me it is only part of my hobby. So I can take breaks any time I want or I need it. I wish you much luck...

A new build of P.moon Oscillator Pack has just been published. Now it looks as it should.

After next Voltage library update buyers should see all three included oscillator modules.
Sorry again for the delay.
I hope you will enjoy the modules.

Roland

Thanks for the interest in the Oscillator Pack . Danny from CA support informed me, that unfortunately included products are missing in the bundle. I don't know, how they could disappear. Anyhow, a new build for the Oscillator Pack is waiting for approvement. So buyers of the pack will get the modul...

Hi, for complex modules it might be helpful to invite users to act as beta testers. For that case manufacturers product page in Nebula offers button "put in beta". Before you can invite beta testers of course you need a forum area. Please contact CA support team. They will create a forum a...

Bundle P.moon Oscillator Pack has just been published. It contains three oscillator modules. Each has these common properties: - Hybrid analog-digital oscillator (analog in audio frequency range, digital at low frequency, smoothly blended between both ranges), - Unlimited pitch input voltage, - Octa...

I see.
Until now that was no problem for me. I know that VM and VMD do "call home" after each start and let them do their things.

Isn't this the option?

Here is the CA answer: Danny L Staff – 10 hours ago via Email Hi Roland, This appears to be a bug - calling GetValue() will return a different value than the actual value if you've called SetValue() with a value that's out of range. In the meantime, we suggest that you bounds-check the values before...