Hey guys, I have the V-collection 6. I’m thing about upgrading to X this Black Friday including a new macbook pro m4.
However, if I decide to upgrade my v-collection I don’t really feel the need to install an “outdated” version since I have the newest one. But the question is: will it open up all projects where I used plugins from the V-collection 6?
For example: I’ve used a DX7 plugin from V-Collection 6. Will the V-collection X open up my project with the DX7 plugin with the correct preset and everything? Or do I have to have ALL V-collection versions that I own installed in order for the projects to open correctly? Thank you!
I can’t say for your project but I can let you know of my own experience. I was doing some work with a friend using one of his older logic songs. he had linked Arturia’s (Moog) Mini V3 instrument inside the project. Well, downloaded the demo but it was the V4 version and of course Logic came back saying it could not find the instrument plugin. As I didn’t have a V3 and didn’t know what patch or settings were associated, it sort of left me stuck. I ended up just forcing it to use the V4 that it took as a new instrument so I just picked a patch that sounded good and went with it, I later found out I could have loaded the V3 of the plugin to get it to recognize the instrument. So I will hazard to guess NO it won’t just load a newer version of a plugin and work, but that might be a Logic Thing if you are using that DAW.
You should retain the ability to install older versions of synths from V Collection 6. Synths like the Minimoog, CS80, Jupiter and Prophet have been re-engineered in later versions of V Collection and are incompatible patch wise with earlier versions. I personally have Minimoog V3 AND V4 installed.
HOWEVER, the issue is I have upgraded from V Collection 9 - 10 and both those are compatible with Apple Silicon M Series. The much older V Collection 6 is likely not and at best will run in Rosetta mode on an M series.
You really need to clarify your particular circumstances with Arturia bofore opening your wallet.
If it does work for you, remember to check the box in Analog Lab for Legacy sounds. This will ensure the patches for older versions are available.
Thanks for the response guys! I just wished that they would’ve made it possible for all legacy plugins to be opened with the newest version, but also still give people the option to install it separately for whatever reason people might need or prefer the legacy version.
I now have 10 plugin manufacturers, that I have to have 10 plugin collections installed in order to be able to open my older projects. Which sucks, because I pretty much only need the latest version. Native Instruments, I have all plugins from the Komplete bundle version 5 till 15 installed. Same goes for the iZotope plugins. Same goes for Arturia. Not only does it take up zillions of gigabytes extra on your harddrives, its also very cluttered and older versions stop also stop getting support like you said with the Mac intel/M series etc.
Final question though: I’ve worked in a studio where they had the Arturia V5 bundle. Some of my projects contain plugins from that bundle. If I purchase the X bundle, will I automatically also own all legacy bundles or just the X? If not, can I buy the legacy bundles separately? Thanks!
The versions that have the same version number in VC-6 and in VC-X is the same. You will not have multiple plugins of the same versions installed. So do not uninstall your VC-6, as that’s not needed, if you already have it installed.
So for example if a instruments is a V3 version in both VC-6 and VC-X, then it’s the exact same. And it will run natively on M processors, as it has been updated to do so - also in your VC-6. So to answer the topic question, then your VC-6 applications should all the time have been updated for free - but not upgraded and not to include new instruments. In this case there is a difference between update and upgrade.
Only the old versions of instruments that was upgraded to another version - like from a V3 to a V4 version - before it was updated and made M1 compatible will not run on M1 processors.
As @Funtmaster say, then you can install an old version alongside a new, when they are not compatible.
Converting tracks to audio is the safest way to keep a certain sound over time.
New versions of instruments can have huge sound differences and have other presets. There are good reasons when they can’t replace an older version in a project. If it can it will keep the ID and also replace the old version when a new version is installed.
No you do not own legacy bundles beside those you already own, just because you upgrade to VC-X.
Legacy instruments are discontinued. But again. Some of the instruments in VC-5 is the same in VC-X - just with updates. Again - only the upgrades from one V number to another V number is/ can be different.
It’s really not as bad, as it look like you think it is. But it can be complicated to understand all this i admit.
Questions like this have been answered several times in the forums. Perhaps there are further informations to find already if needed.
I wonder how much of the older project do you need? and in what form do you use them? I ask as if you could bounce the old instrument tracks to wav, then you have an analog sound form that is the record of what was recorded or used if the project has gone out for release. once bounced you can retrain the midi component so you have the actual keys and other CC data there for record stake, and if you are ever looking to re-release a new version you have that data to put in a new instrument into, or the option of re-loading past versions of the plugin. But if you are using just the sound output, then a bounced wav track will give you the sound without the need for the actual old plugin
Here’s the comparison between VC6 and VCX.
Please note that in Analog Lab Pro, you can enable the “Include Legacy Sounds” option, so it will still show presets from both the current version and the previous version of the instruments that have been redesigned.
@innovationsinm bouncing ALL projects to WAV files is a very tedious task. However, I do agree that this is the best method to go about this problem.
I’ve also received an email from the support team that said if I purchase the X collection, and I was in need of any of the legacy products they would be kind enough to help me with that. So that’s very generous! I’ll get the X collection this week.
Thanks for all the feedback everyone!
2 Likes
_Need help ?
When you can't find the answer online or in the product manual, the Technical Support Team is here!.
_Stay tuned
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.
