Cherry Audio Forums

Thanks, Terry. We're able to reproduce the problem using that code snippet.

Hi Terry.

Could you please send us a small sample project that demonstrates these issues?

Thanks,
Russ

Hi Tobias.

The randomize-controls menu option should be available in the next release.

Hi Joseph. If there's no custom JDK path in the preferences, the module designer will just rely on the OS to resolve the path to java, javac, etc. If you specify a custom path, it should use that. However, there was a bug with retrieving the custom path when checking Java versions at startup. It'll ...

Thanks for noticing this, and sorry for the slow reply. GetBinaryResource is currently set up to only retrieve resources of "binary" type; our thinking when we did this was that there are other APIs for retrieving images and audio. But there are obviously good reasons for wanting to use Ge...

Hi Seal58. There's a compatibility issue with Voltage and version 12 of the JDK that's likely the source of this problem. We're planning to release a new build next week that we expect to take care of it. Until then, the only fix we know of is to uninstall version 12 and install version 11 instead. ...

Hi Terry.

Yep, that's a bug. Thanks for catching it. It should be fixed in the next build.

Hi Gary. When you have the chance, please send us a log file from a session when the compile fails to finish. If you click the "Open Log Files Folder" in the Preferences dialog (on the 'Miscellaneous' page), it'll show you the folder where the file gets created; it'll be called ModuleDesig...

Hi Jack. I assume you mean you want to delete a module you've published from your list of modules so it doesn't show up in Voltage anymore? You can do that from the website, like so: 1) Go to cherryaudio.com and log in to your account 2) Click on the "Your Account" link in the page footer ...

Hi Jack. The 'publish' option should be disabled if you're currently compiling/building or if you're running the debugger or the "run without debugger" option. If none of those are the case, possibly the module designer has gotten confused about its current state; try reloading the project...