Well, i’ve deleted the plugins folder and reinstalled it, deleted vcv rack and reinstalled it, tried to turn my vcv rack 1 file into a vcv rack 2 file, and still some of my plugins arent downloading. I honestly don’t know what to do.
ya so, no…
I installed, the app launches a modified version that wiped a bunch of plugs, and wants me to update. when I use the old alias to lauch, I launches 1.1.6, but I cant find that.
so im in the process of fucking up a bunch of projects. 
Mac 
actually installing new, while launching from alias does bring up 1.1.6, it REMOVED a bunch of plugs from old projects. thanks dude…your advice wrecked a bunch fo projects. 
Ill assume if I make a new folder with all the old plugs, id be able to redirect where V1 looks for the plugs?
Yes, you can tell Rack where to look
2 Likes
thanks man
1 Like
I’m running V1 and V2 in parallel no problems so it can definitely be done. The project files aren’t going to be changed, it’s just a question of getting the right version of each plugin in the right place. So not to worry!
but
hey, this stuff is moving really fast, the servers are still on fire, and we’re all just trying to figure it out together. I am 100% sure that @scook was just trying to help.
I’m happy to pitch in myself; preliminarily, what do you see inside your V1 and V2 user folders? If I’m not mistaken, V1 (\Rack) should have \plugins-v1 with whatever you had before, and V2 (\Rack2) should have \plugins with Fundamental (installed with the main download) plus anything you managed to get off the Library server.
1 Like
Are you sure they exist for VCV 2.0? Which plugins aren’t coming down?
the V1 plugs are still there, in the V1 folder. they still show up in the V1 selection list. but some have been removed from my projects. 
doesn’t matter tho. I’m over it. sorry @scook
my projects are trash anyways. so no biggie. I was initially crushed…but the water has pass under the bridge. 
V2 looks GREAT! nice work
I kinda like the current reduced plug selection. less overwhelming 
1 Like
So the plugins are still in V1 but the projects themselves have changed when you load them in V1? If that’s what happened it’s a major bug. Happy to work with you to find and try to fix this–if you want, send me the file of one that’s missing modules as well as a screenshot of what it looks like when it loads; I can inspect it manually and see what might be going on.
And I’m sure they’re not trash btw!
I feel that! I actually kind of enjoyed being stuck with Fundamental while I waited for my turn at the Library server earlier I think that being able to only load some modules from within a plugin will actually be one of my favorite V2 features.
It sounds like you perhaps tried to open your v1 project in v2, for which some modules were not available, and then it autosaved the patch with the modules missing. If you are going to open a v1 patch in v2 you’d be best off making a copy of it first. And its generally a good idea to save lots of versions of patches so if one gets corrupted somehow then you have lots of previous versions you can return to.
1 Like
Ah–that’s possible. I’m going to try that.
Totally agree this is good advice but at the same time if VCV V2 is doing that I think it’s a major error (in that it violates all reasonable user expectations) and a harmful one at that. I myself have opened V1 instead of V2, and vice versa, a few times now, and if that innocent mistake can corrupt existing patches, yikes! @phaelam is not going to be the only one bitten by that.
Testing now and will submit a support request if I can reproduce.
Might be wishful thinking but its worth double checking the patches are really lost - I just checked and Rack autosaves to a separate autosave file and it doesn’t overwrite the original patch until you actively save again I think.
Could it possibly be that @phaelem opened a v1 patch in v2, saw modules were missing, quit Rack, launched it again, (which opens the autosave) and presumes the patch is ruined?
Might opening the patch in v1 using file > open reveal the patch is actually OK? I think it should be unless it was actively saved over?
2 Likes
Of course you’re right about the auto-save behaviour–I wasn’t thinking that through.
So maybe they’re still OK–I hope so! @phaelem, if you haven’t, can you try to open the original files in V1 from the File menu? You might still see everything there.
The problem is that when V2 opens a V1 file with missing modules, it actually drops the missing modules from the JSON representation (rather than leaving them in to be loaded later), presumably because it fully loads the JSON into the scene (which has no representation for the missing modules) and then fully writes the scene back into the file.
So, if you accidentally save the file in V2, it fully overwrites the original V1 module with the new V2 compressed format, so you can’t even go back and get to the hollowed-out V1 file without additional work.
Basically, in my opinion, V2 shoudn’t:
- Remove references to V1 files from modules on load; or at a MINIMUM:
- Be allowed to overwrite V1 patch files (at least without a SERIOUS warning to the user).
This is especially iffy now because major V1 modules, like Recorder and Chronoblob, aren’t in the Library yet. I think I should make a new thread about this as well as submitting a support request–@steve, do you agree?
Strikes me that the simplest short-term fix would be for V2 to postpend some token (like _V2 or _conv_from_V1) to the patch name whenever it loads a V1 file. If the user wants to override that, it’s up to them.
This makes a lot of sense I think.
1 Like
no problem at all with reaper on linux. at the moment I can’t try on windows because I’m working (I should be…).
are you sure you have followed the instructions?
Everithings fine on my windows 10 , Thx vcv <3
That’s actually not the case. I am opening V1 projects in V1…and some plugs are have been removed from those projects.
But what I’m going to do is, not look back. And just use what’s available in V2. So problem solved. Limitations can be good.
Now…I’ve read that V2 will not work on Mac silicon? I don’t have one yet, but will soon as my box is old. I this the case?
1 Like
Hi @phaelam, thanks for the followup. It looks like there is indeed an issue when V1 files are opened and saved in V2 and I’m going to get a thread up/put in a request ASAP so that hopwfully what happened to you doesn’t happen to anyone else 
1 Like
I see “march=nehalem” on compile file 
Nice, so at least we have SSE4.2 
Are there any updates about the Aria modules?