Cherry Audio Forums

AndyMac, You can create a new product and change the type to preset. Then zip up the presets in their folder(s). So that the zipped up folder structure is like this > file.zip > sub dir 1 > preset 1.voltagepreset -----------------------------> preset 2.voltagepreset -----------------------------> p...

Ok, I have republished this with the package name com.andrewmacaulay.voltmeter which I can live with anyway. There are two versions now showing - the old one (published) and the new one (in development). Two questions: 1. can I add in development modules into existing collections (ready for them to ...

Following on from the bug report and the team's work on it https://forums.cherryaudio.com/viewtopic.php?f=8&t=307, I have just been testing all my modules as I work on some minor fixes and UI improvements, and looked again at the Dual Voltmeter preset loading issue - and it still seems to be the...

Just been testing all my modules as I work on some minor fixes and UI improvements, and looked again at the Dual Voltmeter preset loading issue - and it still seems to be there (the only one which has this issue). I am going to pick this up on the developer forum to try to work out why this is still...

It would be really helpful for the Info... display for a module to honour the formatting and links in the description on the store, or if not able to honour the formatting at least to hide this when the description text from the store is displayed within the application. See e.g. PSP Audio and my ow...

As I was getting ready to reply to this, I realized that there's an important difference between the VM and the module designer: in Voltage Modular, the module won't get calls to ProcessSample until all initialization has taken place, but in the module designer, you can get ProcessSample calls befo...

That's really useful background - and good to understand the differences in behaviour in the current tools, and that you are looking to get this more consistent. Anyway, from this, I don't have to worry about getting current values during Initialise phase (which I had been doing) as long as they are...

Great, and sounds a really flexible implementation. Now I need to work out whether I can migrate my custom code to this (as the custom skew point sounds ideal for my uses) in a way that can maintain existing stored settings/presets for existing users. So, to make it possible to do automatic migratio...

Thanks - I though that there must be a way

Found a workaround - opened the .skin and .skinproject files and replaced the 37 width and height with 25, as the 25px versions of the in-the-box ones are. Would be nice to have option in the skin editor to fix the size of the sockets without having to go into the files directly.