Cherry Audio Forums

Steve W wrote: ↑Sat Feb 11, 2023 8:04 pm 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.

UrbanCyborg wrote: ↑Tue Apr 11, 2023 7:13 pm The problem with making that the standard is that most people don't have three-button mice.

Reid

ttop wrote: ↑Wed Apr 12, 2023 4:56 am

UrbanCyborg wrote: ↑Tue Apr 11, 2023 7:13 pm The problem with making that the standard is that most people don't have three-button mice.

Reid

It does not have to be standard but it would be very nice to have it as an alternative option.