Cherry Audio Forums

Any updates on this? Still unable to continue my module development due to the bug...

Great! Thank you!

All right, I sent CA a support request. In the past they have always responded pretty quickly, hopefully now too.

Thanks for testing this & doing some further analyzing! So yeah, seems it's a built-in VMD "feature" instead of something wrong with my system, unfortunately. I just tried publishing a module with "too many" class defs, and interestingly the whole VMD crashes and quits to des...

Some additions: - Attached is a text file with 100 dummy class definitions so you can easily try this yourself (just copy & paste them into a fresh VM project and see if it still runs) - Interfaces also count into the total (in addition to regular / abstract / anonymous classes and enums) - I tr...

Hey, I just ran into a strange issue. Never saw this before, but I can easily reproduce it, and I'm wondering if this is something I have misconfigured in my system and/or something really obvious I'm missing. Simply put, VMD crashes if there are "too many" class definitions in the code. I...

I just ended up having the module presets as a separate download with installation instructions, but agreed, it would be cool if they got downloaded & installed with the module itself. But maybe you could include the preset files into your module resources and then write them out to the presets ...

A new effect module called Infinity is now available! 🔊 It’s based on an ”impossible” auditory illusion where a sound seems to be rising or falling endlessly. It features six different modes with their own distinctive sound, stereo processing, and LFO + S&H + smoother processors. Endlessly tweak...

Thanks, at least this confirms there probably isn't any obvious easy way to do it (which I just missed) :D I did toy with a couple of kludge-ish ideas, although I didn't try either of them: - Build a custom slider using images etc, then put knobs with an invisible skin on top of the slider handles, ...

The heart of the problem is that there's no way to really know when initialization is truly over, and my button notification handlers can, in turn, modify the state of buttons. If I could just tell the handlers to not handle during initialization, all would be well, but that doesn't really work, ei...