Is there anyway to force Rack to always open with a blank template?
Thanks!
Is there anyway to force Rack to always open with a blank template?
Thanks!
delete all modules, save the empty patch as a template?
you mean , do not open the last session? I would like that too I afraid is not possible
Thatâs what iâm after, yes.
Had a feeling you couldnât but always worth asking.
Change your shortcut to Rack to include the patch you want to open, e.g.
âC:\Program Files\VCV\Rack1\Rack.exeâ âc:\Users\paul\Documents\Rack\blank.vcvâ
Then when you run the shortcut it will open that patch.
cleaver!
a similar thread from the past
@PaulPiko wouldnât this result in saving over the blank.vcv file the first time you press ctrl+s?
Sure. Youâd need to ctrl-shift-s before you ctrl-s
Maybe set the blank.vcv to read-only before you use it.
Finish with a File > New patch then when you quit it saves that and will open with a new blank patch.
Thatâs what iâve been doing.
Iâm doing the following (on Windows 10 Pro):
So I can open Rack with the last patch by click on the taskbar Rack item, or with right click on the taskbar Rack item I can select one of my pinned initial panels. The initial panels are read-only to protect against overwriting. Normally Windows software grumbles with a âSave asâ dialog, if You want to save a read-only file. But VCV Rack doesnât ⌠it saves a tmp file, but doesnât overwrite my original starting panel. And this is perfect for me From time to time I remove temp/tmp files anyway.
btw: The tmp file is a vcv patch file, so modify the file name and extension ⌠just in case.
Just as an idea
it might be a good idea to at least leave some audio8 still in there as due to some bug vcvrack might eat a lot of cpu if no audio interface is defined in some situations
Maybe Iâm misunderstanding the question, but woudnât you be able to do what you want by:
template.vcv
file a blank patch in the Rack binary directory, andautosave-v1.vcv
file in the user Rack directory upon start-up?Of course, it wouldnât auto-save for you anymore, but the autosave behaviour in rack is a little counter-intuitive IMO, so that wouldnât necessarily be a bad thing.
why do you thing it is counter-intuitive?
Most software asks you if you want to save your work if you try to quit with unsaved changes. Rack doesnât. It just saves the state instead, restoring it when you log back in.
Itâs different behaviour then most, so itâs counter-intuitive to me. It took me a little while to adapt my workflow to it, as I would come to a point and think âhmm, this isnât working. Iâll just quit and log back in to restore my last âgoodâ save.â Rack doesnât quite work that way.
Autosave is its own file but when you save an opened autosave it overwrites a concrete patch, that you have possibly forgotten by the time you are there to press ctrl+s.
To be clear, I like the fact that Rack doesnât question me when I want to quit, but I want it to prompt me when Iâm manual saving the first time after opening the autosaved state.
I am hoping someone could offer some knowledge that I have been unable to locate using our friend Google. Is it possible to turn off autosave? I have tried changing âautosavePeriodâ in the settings-v1.json file to zero but it doesnât seem to stick. I am also curious about having a blank template loaded each time. I have recently run into several occasions where a patch has crashed VCV Rack and, because the file was autosaved, I could not get it to load again. In all cases I have been able to determine the cause of the crash but have, on a few occasions, had to recreate the patch from scratch.
Are you editing settings.json
while Rack is open? You need to close Rack before editing this file.
To save a template patch, choose File > Save template
. You can delete all modules from your patch and save it as the template patch.
Ahhh. Thanks. I was editing while rack was open. Sometimes itâs the simple stuff that gets you.