Voltage Modular Feature Requests

[PoohBear]

Merge patches.

Cabinets remember remotes.

I caught your request for inserting modules where the cursor is in your latest video. Adding it to the list.

Thank you

[ChR_is]

Here's a big one for me: fix the SVG render code in VM and VMD so that it renders files from programs other than Illustrator correctly, like nearly every other renderer does. I've been tearing my hair, and wasting inordinate amounts of time trying to do simple modifications of existing, working control art using Inkscape, to no avail. I've even taken to hand editing the SVG files to the point where there are only trivial differences, and they still won't correctly render. If you know where to look in my released modules (I ain't'a saying where ), you can even see some of what I'm talking about.

Reid

i use affinity designer and have 0 issues. i also used inkscape in the beginning and had some minor issues here and there, but i think they were my own fault.
make sure to render text/fonts as curves, set the svg size to the correct size for the module, have 300dpi for rendering non-curve stuff (and have as few non-curve elements as possible or even better have none) and you should be set.
also make sure to only use features supported by standard svg. stuff like gradients and shadows are troublesome.

[UrbanCyborg]

Yeah, I kind of think gradients are the thing biting me. Still, I only have the same gradients as were already in the control, just shifted in hue. At least, that's the latest problem I've run across. Drawing original controls, even with no gradients in Inkscape usually results in objects displaying with confused z-values, no matter how I arrange them. The truly annoying thing is that I can open them up fine in, say, MS Explorer's handlers (just double-click on them). It's only VM and VMD that get them wrong.

Reid

[terrymcg]

Here's a big one for me: fix the SVG render code in VM and VMD so that it renders files from programs other than Illustrator correctly, like nearly every other renderer does. I've been tearing my hair, and wasting inordinate amounts of time trying to do simple modifications of existing, working control art using Inkscape, to no avail.

This, please. I'm using CorelDraw, and the curved buttons for ERings were an absolute nightmare to get correct.

I'm with you on the cables for pictures thing too... having to trash my debug setups in VMD just to get a cable (and dot) free image is a drag.

Cheers,
--
Terry McG

[BetterAngels]

I'm not sure if this has been talked about before, but one point of friction for me is that whenever I initialize VM in Ableton on Windows 10, the preferred patch cable color, patch cable transparency and window zoom have not been saved.

This might just be a software issue of some kind on my end, but having this fixed would get a big thumbs up from me.

[GusGranite]

I'm not sure if this has been talked about before, but one point of friction for me is that whenever I initialize VM in Ableton on Windows 10, the preferred patch cable color, patch cable transparency and window zoom have not been saved.

This might just be a software issue of some kind on my end, but having this fixed would get a big thumbs up from me.

Added

[GusGranite]

Hi,
I noticed that when I turn on the filter on manufacturer and sometimes at other times, the selection of modules when scrolling returns to the beginning by itself, which sometimes I don't want when browsing for a longer time. Can it be turned off somewhere? if not, I would like to remove this feature

Oh, this one bugs the bazoogaz out of me! Adding

[GusGranite]

Adding - Filter library by module bundles (such as Nucleus) etc. Would be great way to make patches for bundle owners and spread the love etc.

Courtesy of @agentslimepunk

[Steve W]

Adding - Filter library by module bundles (such as Nucleus) etc. Would be great way to make patches for bundle owners and spread the love etc.

Not sure if I mentioned this before, but I would like to see the ability to filter the library not just by bundles (VM base products such as Nucleus, etc. and other bundles such as FM Bundle, Control Freaks, etc.) but by unlimited user definable and nameable groupings.

[Steve W]

The ability to revert and lock builds of modules on a module by module basis so that if a later build of a module doesn't work VMers can use presets that previously worked.

Background: Several days ago I ran into a problem that some multi-channel, multi-timbre patches no longer worked. It seemed that one module was changed so it only responds to midi channel 1. Over the span of several days (don't ask how many hours), I was able to make it work with an older version of a companion module.

However, at present VMers do not have the ability to say no to updates on a module by module basis. Either we say yes to all updates or no to all updates.

I would rather make music than spend more than an hour or two debugging a new build of a module that used to work. With the current issue, it was way more than a couple of hours (estimated 15-20 hours, including documenting the problem with video captures, uninstalling VM 2.7.0, installing VM 2.5.5, and then reinstalling 2.7.0 to try to track down the source of the problem).

I now have the builds set up so that a series of patches work, but I would like to keep them working by locking in the builds for 2 modules and still have the ability to update all my other other modules.

And no, I do not want to spend even more time to write up the details of the problem so others can try to guess what the issue might be. Its nice that developers want to enhance existing modules for new users, but there should be a way that we don't have to totally redesign patches that used to work before the changes.