In the next version, the settings loader will fall back to settings_default.json when settings.json does not exist, yet. I also removed settings.json from the distributable.Funkybot's Evil Twin wrote: ↑Thu May 23, 2019 7:20 ambsp804, is every new install of this supposed to reset our favorites? That's been my experience. I'm assuming it's the settings.json in the distribution that does it. If so, would it be possible not to include that in future distributions so people like me don't keep overwriting our settings files with yours? I'm assuming if none exists, VCV would create a new one.
I appreciate everything you do and ask quite humbly just to make things a bit easier on me. I'll try to avoid installing that file in the future and see if that solves for it.
In other words: It will be safe to copy a new vst2_bin folder over the old one and you won't lose your configuration again.
Since a lot of documentation (posts, text files) already reference the "vst2_bin" folder I won't rename it.
However, you can always rename the folder locally however you wish.
Well, first and foremost it's a (copyleft) source code license and as long as you somehow obtained a (GPL compliant) binary, you are free to run it, even if you don't know about or don't agree with the GPL.vortico wrote: ↑Thu May 23, 2019 9:33 amThat's why I think the FAQ is poorly written. The GPLv3 releases all copyright limitations for using the software in section 2: "This License explicitly affirms your unlimited permission to run the unmodified Program." And a redundant clause in section 9: "You are not required to accept this License in order to receive or run a copy of the Program."
Which makes me wonder why some people are creating installers which present you a copy of the GPL and require you to click the "I Agree" button
no problem, CC0 it is. I'll let you know when it's done.