Rack: Add patch "Import"

Created on 23 Sep 2017  路  8Comments  路  Source: VCVRack/Rack

Would it be possible to load multiple configurations into the same environment?

feature request

Most helpful comment

Perhaps I could add an "Import patch" feature that loads a .vcv file without clearing the existing Rack. It could plop it down at the bottom of your existing rack.

Seems like patches have nothing to do with this, if by "patch" you mean "stored knob position files". What do you mean by "patch memory module?"

All 8 comments

I think this could be implemented with patch memory module.

Perhaps I could add an "Import patch" feature that loads a .vcv file without clearing the existing Rack. It could plop it down at the bottom of your existing rack.

Seems like patches have nothing to do with this, if by "patch" you mean "stored knob position files". What do you mean by "patch memory module?"

Perhaps I could add an "Import patch" feature that loads a .vcv file without clearing the existing Rack. It could plop it down at the bottom of your existing rack.

This is exactly how I originally imagined it. but #132 is blocking this.

But patch memory module would also be very nice, I just thought that it could also remember the modules used, not just their parameters. But I guess this makes it all too convoluted: with a patch memory module I would like to have a V/OCT input to be able to fade between 2 patch memories.

It's not really blocking it because for most people and in most audio device configurations, using a duplicate audio device just silently fails.

I'm still not sure what your patch memory module idea is. Is it a module that inspects the existence of other modules around it? Doesn't that break modularilty? Or is it like a "folder" where other modules "live inside of it", like Ableton Live's macro effect/instrument?

As for fading, could use add two of these macro modules above and put them through a crossfader?

It's not really blocking

It is blocking it, because currently if you just dropped a second vcv file (with its audio interface) in the same rack, the program would crash, and you would need to go manually delete the autosave file.

As for the patch memory module: I think we should move this discussion to a different ticket. Yes, it would break the modularity. But it has been done in the hardware world, see https://en.wikipedia.org/wiki/Synthesizer#Patch and https://www.youtube.com/watch?v=T7vDO7Uw20M (This is a joke, but we still can take inspiration from it.

Is this still on the TO DO?
I am just commenting here because I think integrating patches into each other is a really important feature

@AndrewBelt is there any chance to get the "Import" feature into v1 release? Is implementing it without clearing the whole Rack complex/unstable? Posting here just to let you know this would be a great addiction to Rack projects scalability.

Pack-one has this feature covered with the module Split.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jaffasplaffa picture jaffasplaffa  路  7Comments

Coirt picture Coirt  路  7Comments

dilom picture dilom  路  7Comments

LazyPike picture LazyPike  路  6Comments

oblivionratula picture oblivionratula  路  7Comments