VCV Rack 2.4.0 released

From VCV - Support (vcvrack.com) (emphasis mine):

For assistance with your VCV account, feature requests and bug reports for VCV products, the VCV Library, and business/private requests, email support@vcvrack.com or use the contact form on this page.

I requested this when host came out, hopefully we get one day.

What exactly bug in VCV Routers elaborate please ?

They don’t save state. Take ROUTER 4:1, hit the clock button so output 2 is selected, exit rack, restart, output 1 selected. Literally a five minute fix if someone could be bothered. Thankfully there are better, free alternatives.

1 Like

Very few modules save state. This may be more like a missing feature than a bug?

It was acknowledged as a bug by VCV, then, silence…

Virtually all modules save state, if not, how would shutting down rack without saving, then restarting, produce exactly the same patch (unless using VCV ROUTERs)?

So if I go and try 5 random LFO they will all save the phase, for example?

I don’t know, for what I do things like that are of little concern to me. So long as I can hit a reset button and everything is in sync I’m happy.

“Very few modules save state”, so saving a patch, then reloading it, and having everything as you left it (unless you’re using VCV ROUTERs) is done my magic? All functional modules save state otherwise people wouldn’t use them.

I’m a bit boggled by this, YOUR modules save state.

My modules most certainly do not save state. All modules save a “patch”. Some may go over and above and save what I consider “state”, like LFO phase, current sequence step, etc…

None of my LFOs save phase, and none of my sequencers save the current position. Although, as you point out, they do save enough stuff that is most cases they load up and sound “right”.

Patches loading and not “playing” quite right is an ancient problem, you will find may discussions about it here.

Ok, seems our interpretation of state doesn’t match, so if I replace state with settings are we on the same page? VCV ROUTERs don’t save their settings so are not fit for purpose, Count Modula switches do so I use them instead, plus they have dark panels.

well, my interpretation of state does seem to match how most modules work. Count modula seems to save it (I just tried couple of them). VCV, ML, Nonlinear circuits don’t. Those are the ones I just tried.

My guess is that most don’t. I think if you logged a bug for every module that doesn’t save “state” you would be very busy!

Fun thing however. Knobs position, or selected mode (like in Mutable devices) this is current state, right ? And all this saveable.

EDIT: Although in other hand, being unfamiliar yet with VCV Router modules, i’m not sure, maybe really described feature can be close (by application) to lfo’s phase position example. Then this is not critical.

In the absence of any documentation declaring that the state should be saved, I would definitely classify this as a design issue, not a bug. I suspect the module is doing exactly what the developer intended, so I don’t see how it can be called a bug.

Granted, I think a large percentage of the population does not distinguish between the two.

That being said, the option to save state would be a really good feature to add. I can see situations where sometimes I would want state saved, and others not.

1 Like

Been using VCV for many years now, this is the only one I can recall. I’ll be sure to post if I ever find another.

I agree with what you say. But, I think it’s sort of “documented” that VCV modules are supposed to act exactly like a physical Eurorack module would. Most Eurorack modules “save” a “patch”, because the patch is the state of the cables, knobs, etc… But most Eurorack modules do not save “state”, indeed it would be very difficult and/or expensive to do that.

However, I agree with all of the above, it could certainly be desirable.

1 Like

The highly respected Bogaudio plugin includes 1:8 and 8:1 sequential switches that do not save active channel state. I haven’t looked, but I suspect there are others that do save state.

Trying to argue what should be done is pointless, whether it be physical Eurorack, or virtual VCV. It is a big world out there with tremendous variety, and no one wins those arguments. Even trying to declare what is the norm is typically futile. The answer might change tomorrow.

But stating what you would like to see is great.

2 Likes

For sure. But not knowing what is “often done” can lead to frustration.

1 Like