This is not about plugin version differences, but about how files are organized in both worlds. Please make a video about the difference, and what are the advantages using vst3 versions of plugins. I have some VSTi plugins in both versions, but see no difference in performance, properties nor system resource usage. So the question is why would a company write plugins in 2 different versions of them ? Thank you.
VST3 is the new "standard" which brings benefits to developers more so than what we as producers would see. Sometimes VST3 can have "slight" performance increase (if any). The biggest difference we probably notice is many times the GUI is resizeable. Also, because VST3 must live in "Common Files" folder, it means it loads from your C:\ which is often a SSD nowadays. Use VST3 if making music.. you can keep VST2 around if the program does not support it. Not much more to it than that from a user's point of view, which is why I explained it the way I did!
VST3 is just a format at the end of the file ".vst3". It just allows developers better access to "features". As the end user, we don't notice much, except for being able to resize the GUI, and maybe a little better CPU performance. Also, VST3 has to live in "Common Files" folder.. that's literally all you need to know. I left a resource to the changelog if you want to get nerdy and see what's all involved with VST3 for developers.
@@itsGratuiTous Thanks. In the video you also said something about right clicking the knobs on vst3 but then you stopped talking about it. What were you gonna say?
@@FinalfixMusic Some plugins act as a real "native plugin" within FL Studio if they are VST3 🙂 .. meaning you can right-click the knobs! To learn professional beatmaking, check out my website.. it's a full-fledged learning platform!: itsGratuiTous.com/
@@itsGratuiTous I personally don't find any use out of them.. I've just, this year, finally started installing them besides my VST2s and I've mainly done it to maintain compatibility. Antares has completely abandoned VST2. I'm honestly not even sure if I have any plugins that actually implement those features in a meaningful way or if Ableton is even setup to take advantage of those features. The multiple MIDI inputs seems to be quite practical but I don't see any application outside of a live performance you'd even use it.
@@JordonRenn93 Yeah, I know with FabFilter, VST3 you can resize it to any custom size (where as VST2 you have to use the pre-set sizes)... so that's useful!
Sorry man, the difference isn't too significant for us as end users, but more for developers. One of the main differences we'd notice is having RESIZABLE GUI's (being able to make the plugin bigger/smaller by clicking and dragging!)
It's better to keep all of your sound files and VST folders on a separate drive. This way if you need to reformat your C: drive (OS drive) then you still have all of your VSTs and folder structures set up on the separate drive. I keep all of mine on a seperate portable SAMSUNG T7 Shield 4TB SSD drive. The portability also allows you to switch between a desktop workstation and a laptop if you needed to.
Ya this is an approach, too.. at the time of the video, 4TB SSDs were not common, let alone external 4TB SSDs! Also, the price was quite steep previously. So this is an option! I do like to have my music stuff stored in the cloud for the sake of easy backups and accessing from multiple computers, so you can always hook your external SSD into the cloud to get that benefit as well! We are not starting to see 8TB SSDs.. but again, quite expensive right now!
Great explanation! I had no idea vst3 only worked out of a specific folder! I might need to go through my plugins and do some reorganising, I think I now know why some of those freebies never showed up in the DAW lol Many thanks :D
Yes, VST3 is .vst3 format, and lives in Common Files folder. VST2 is .dll and can be installed anywhere. Try to use VST3 most often to stay ahead of the curve in regards to future updates etc. (Some programs that use VSTs only use VST2 still, so sometimes you need to install both).
There are some in that folder that didn't have an option to change the install directory but any that asked for a place to install them or any that came in an archive with no installer I put in c:\vst. I just went through to double check and they all work and will load into Cakewalk. Perhaps this is just dependent on how different DAWs handle them. I don't really see a reason why they would have to be in that directory unless your DAW only looked in that place with no way of changing it.
@@dugger0 That's what I thought, too - but in FL Studio, it will not see VST3 when scanning if not in Common Files folder. I would prefer to have everything in my own C:/FOLDER myself for easy backup/organization..
There is no difference in quality - just a new format that gives developers new features to work with from my understanding! (Us as users see very little differences, like being able to resize the VST).
Is the installation folder an FL Studio issue? I'm using Reaper and can install them anywhere. Like you I have a dedicated Music Production folder on my D: drive. In Reaper settings I can enter any paths I want Reaper to find plugins. Maybe FL has a similar option?
Last time I recall, I don’t think FL Studio allows switching VST3 location.. i didn’t like that because I just like having all music production stuff in one folder.. it was forcing VST3 to live in Common Files folder.. wouldn’t find them in other folders.. maybe FL 21 is different..
You could do that.. I recommend creating your own music production folder.. here's more info on that: itsgratuitous.com/podcast/004-a-specific-music-production-folder/
You're welcome! VST2 is .dll, and can typically be stored anywhere on your computer. When using FL Studio, the .vst3 format must be installed in that Common Files folder 👎 Typically a .vst3 will give a bit more intuitive GUI, like being able to right-click in the plugin to access FL Studio functionality.. Other than that, we as end users don't notice much difference.. it's mainly for developers to access different features of the code.. With the new CLAP audio format.. will be exciting how it plays out with its open-source nature 👍👍👍 itsgratuitous.com/
From the end user’s point of view, you won’t experience any difference for the most part.. it just allows developers to have more functionality while coding… what you’ll notice is what I mentioned… maybe being able to scale the GUI bigger.. and you have to store the .vst3 is common files folder.
Yes, folders are important to know about for VST3. VST 3 must live in "Common Files" folder. VST2 .dll could be located anywhere previously. You laugh because you don't understand 🙂
Sorry about that! In short, the only things we as producers will really notice is the ability to resize VST3 windows, and that it lives in the "Common Files" folder with .vst3 format, rather than .dll for VST2.
![A Collection Of 1000+ Instruments [For Free] 🎻](http://i.ytimg.com/vi/os6fg2t8uK4/mqdefault.jpg)
This is not about plugin version differences, but about how files are organized in both worlds.
Please make a video about the difference, and what are the advantages using vst3 versions of plugins.
I have some VSTi plugins in both versions, but see no difference in performance, properties nor system resource usage.
So the question is why would a company write plugins in 2 different versions of them ?
Thank you.
VST3 is the new "standard" which brings benefits to developers more so than what we as producers would see.
Sometimes VST3 can have "slight" performance increase (if any). The biggest difference we probably notice is many times the GUI is resizeable.
Also, because VST3 must live in "Common Files" folder, it means it loads from your C:\ which is often a SSD nowadays.
Use VST3 if making music.. you can keep VST2 around if the program does not support it. Not much more to it than that from a user's point of view, which is why I explained it the way I did!
@@itsGratuiTous Thank you.
@@SonicVisualGR No prob! Reach out any time if you have beatmaking questions over at itsGratuiTous.com/
I still have no clue what vst3 is.
VST3 is just a format at the end of the file ".vst3". It just allows developers better access to "features". As the end user, we don't notice much, except for being able to resize the GUI, and maybe a little better CPU performance.
Also, VST3 has to live in "Common Files" folder.. that's literally all you need to know. I left a resource to the changelog if you want to get nerdy and see what's all involved with VST3 for developers.
@@itsGratuiTous Thanks. In the video you also said something about right clicking the knobs on vst3 but then you stopped talking about it. What were you gonna say?
@@FinalfixMusic Some plugins act as a real "native plugin" within FL Studio if they are VST3 🙂 .. meaning you can right-click the knobs!
To learn professional beatmaking, check out my website.. it's a full-fledged learning platform!:
itsGratuiTous.com/
@@itsGratuiTous Well that's quite a huge and important difference, well worth mentioning in the video!
@@OneEyedWheeler What difference are you referring to?
I'd say the biggest notable difference is that you can use multiple inputs and outputs with VST3 and all the advanced MIDI features
What kind of advanced MIDI VST3 features do you find yourself using? Also for ins and outs, are you talking VSTi’s or effects? Where would you use it
@@itsGratuiTous I personally don't find any use out of them.. I've just, this year, finally started installing them besides my VST2s and I've mainly done it to maintain compatibility. Antares has completely abandoned VST2.
I'm honestly not even sure if I have any plugins that actually implement those features in a meaningful way or if Ableton is even setup to take advantage of those features.
The multiple MIDI inputs seems to be quite practical but I don't see any application outside of a live performance you'd even use it.
@@JordonRenn93 Yeah, I know with FabFilter, VST3 you can resize it to any custom size (where as VST2 you have to use the pre-set sizes)... so that's useful!
This tutorial is more about folder structure and how organize files. Not difference betwen vst2 vs vst3.
Sorry man, the difference isn't too significant for us as end users, but more for developers.
One of the main differences we'd notice is having RESIZABLE GUI's (being able to make the plugin bigger/smaller by clicking and dragging!)
@@itsGratuiTous Got it, thank you ! :)
@@raffa4510 No problem.. reach out ANY TIME for beatmaking training - itsGratuiTous.com 🙂
It's better to keep all of your sound files and VST folders on a separate drive. This way if you need to reformat your C: drive (OS drive) then you still have all of your VSTs and folder structures set up on the separate drive. I keep all of mine on a seperate portable SAMSUNG T7 Shield 4TB SSD drive. The portability also allows you to switch between a desktop workstation and a laptop if you needed to.
Ya this is an approach, too.. at the time of the video, 4TB SSDs were not common, let alone external 4TB SSDs! Also, the price was quite steep previously. So this is an option! I do like to have my music stuff stored in the cloud for the sake of easy backups and accessing from multiple computers, so you can always hook your external SSD into the cloud to get that benefit as well!
We are not starting to see 8TB SSDs.. but again, quite expensive right now!
Great explanation! I had no idea vst3 only worked out of a specific folder! I might need to go through my plugins and do some reorganising, I think I now know why some of those freebies never showed up in the DAW lol
Many thanks :D
Yes, VST3 is .vst3 format, and lives in Common Files folder. VST2 is .dll and can be installed anywhere. Try to use VST3 most often to stay ahead of the curve in regards to future updates etc. (Some programs that use VSTs only use VST2 still, so sometimes you need to install both).
I have all vst in the same place. 2 and 3. Never had issues with them not being detected in Cakewalk
That is interesting - VST3's live in the "Common Files" folder.
There are some in that folder that didn't have an option to change the install directory but any that asked for a place to install them or any that came in an archive with no installer I put in c:\vst. I just went through to double check and they all work and will load into Cakewalk.
Perhaps this is just dependent on how different DAWs handle them. I don't really see a reason why they would have to be in that directory unless your DAW only looked in that place with no way of changing it.
@@dugger0 That's what I thought, too - but in FL Studio, it will not see VST3 when scanning if not in Common Files folder. I would prefer to have everything in my own C:/FOLDER myself for easy backup/organization..
Thank you , very interesting! In terms of quality, vst3 is better than vst2? Many thank
There is no difference in quality - just a new format that gives developers new features to work with from my understanding! (Us as users see very little differences, like being able to resize the VST).
Thank you very much!
No problem… much more Beatmaking training on my website: itsGratuiTous.com
Is the installation folder an FL Studio issue? I'm using Reaper and can install them anywhere. Like you I have a dedicated Music Production folder on my D: drive. In Reaper settings I can enter any paths I want Reaper to find plugins. Maybe FL has a similar option?
Last time I recall, I don’t think FL Studio allows switching VST3 location.. i didn’t like that because I just like having all music production stuff in one folder.. it was forcing VST3 to live in Common Files folder.. wouldn’t find them in other folders.. maybe FL 21 is different..
So I should put vst2 programs in the vst3 folder with the .vst3 files for better organization and having it all in one place?
You could do that.. I recommend creating your own music production folder.. here's more info on that: itsgratuitous.com/podcast/004-a-specific-music-production-folder/
THANKS BRO
You're welcome! VST2 is .dll, and can typically be stored anywhere on your computer. When using FL Studio, the .vst3 format must be installed in that Common Files folder 👎
Typically a .vst3 will give a bit more intuitive GUI, like being able to right-click in the plugin to access FL Studio functionality..
Other than that, we as end users don't notice much difference.. it's mainly for developers to access different features of the code..
With the new CLAP audio format.. will be exciting how it plays out with its open-source nature 👍👍👍
itsgratuitous.com/
why is no one just listing the differences between the 2. half this video is this guy telling us what folder he keeps them
From the end user’s point of view, you won’t experience any difference for the most part.. it just allows developers to have more functionality while coding… what you’ll notice is what I mentioned… maybe being able to scale the GUI bigger.. and you have to store the .vst3 is common files folder.
we here to talk about folders or what 😂😂😂😂
Yes, folders are important to know about for VST3. VST 3 must live in "Common Files" folder. VST2 .dll could be located anywhere previously. You laugh because you don't understand 🙂
Companies are creating an unbelievable mess of spiderwebby files huh. im a bit suprised, but mostly just dissapointed.
What do you mean?
First comment.. 😁❤️💯✨️
😎
I went to another video. You take way too long.
Sorry about that! In short, the only things we as producers will really notice is the ability to resize VST3 windows, and that it lives in the "Common Files" folder with .vst3 format, rather than .dll for VST2.