Voltge Modular update?

[Jo Beatz]

Hi,

I wonder when Voltage Modular will be updated? In the meantime, some improvements are pending.

Best regards

[woau]

Would be cool to, next to maintanance and maybe bug fixes updates, see some new functions being added.

[huggermugger]

When booting VM, Browser needs to refresh/validate in the background without interfering with use of the program or a system needs to be devised that stores validation locally.
Module updates need to include name of module to be updated.
Favorites needs sub-categories.
Remote Control module stored in a Cabinet needs to remember its mappings.
All modules need option to Copy/Paste Settings.

[UrbanCyborg]

Copy/Paste Module settings can't be implemented on the host side; it would require rewriting every module existing for VM.

Reid

[ColinP]

Copy/Paste Module settings can't be implemented on the host side; it would require rewriting every module existing for VM.

I don't understand why this would be the case, providing that the source and destination are the same type of module.

When you duplicate a module it copies the settings from the old module to the new. And the variations feature has similar functionality.

My understanding is that these are implemented using calls to the Get/SetStateInformation() methods.

One caveat is that the implementation does appear to be a little buggy (i've had rare/intermittent problems with duplicate and variations and Rob of WI found that resources weren't handled properly too) but in principle I think copy/paste settings should be feasible without any mods to the modules.

[honki-bobo]

Copy/Paste Module settings can't be implemented on the host side; it would require rewriting every module existing for VM.

Reid

You can - indirectly - do that already. Right-click on a module and select "Module Preset -> Save As...", then store it and open it in the module that you want to "copy" the settings to.

I suppose this function is actually calling Get/SetStateInformation() to store and restore the mudules state.

[UrbanCyborg]

Okay, I stand (well, sit) corrected. Still, it kind of leaves you at the mercy of the module writer's skill in correctly implementing the save/restore functions, and I'm not entirely sanguine about that.

Reid

[ColinP]

I forgot about Module Presets!

Reid, a lot of modules don't need to implement Get/SetStateInformation() methods anyway as their control settings are automatically saved and restored.

If you'll forgive me for plugging one my modules, another approach is to link controls so that adjusting one automatically adjusts a matching control on another module.

https://store.cherryaudio.com/modules/tandem

Each linked control requires its own Tandem module so setup can be a bit tedius but once it's done you can move the Tandem modules to the edge of a patch and pretty much forget about them.

In the illustration below the Envelope Generator on the right automatically mirrors the settings of the left-hand one...

tandem.png (212.45 KiB) Viewed 9491 times

[UrbanCyborg]

[Darth Vader voice] Impressive; most impressive! I'd forgotten...wait a mo...[\Darth Vader voice]...there, that's better...ah, yeah, I'd forgotten about your Tandem module. Killer piece of work, that.

I was really channeling my trepidation concerning my own work, where I have some custom controls that don't get automagically restored. I do handle them in Get/SetStateInformation(), but I've seen some glitches due to the way I implemented the controls. I'm waiting for some feedback from the Devs on that, mostly to do with how the controls respond to Undo/Redo, but Save/Restore, as well.

Reid