Sorry for the dumb question. What is the difference of purpose between a VST Sound file and vst3 files? I’ve noticed that vst3 files are few in number, but soundfiles are many. Here’s a scenario - you want to pull in someone else’s project, and they’ve got custom sounds… does that mean you have to get a vst3 file from that other installation and copy over, or you just need individual sound files to copy over?
VST3 are the plugins…they can be effects or instruments. VST sounds are things like loops samples etc that can load into some of the instruments.
You will need same plugins and same vst sounds to be installed and activated on both computers.
Just to note that many instruments don’t use any samples and any customisation of these sounds or any further customisations to sampled sounds will be saved with the project.
2 Likes
I’m oversimplifying for purposes of illustration, but hopefully this will help.
Consider a “VST” as an app specifically written to run inside of a DAW environment. VST3 is the “current” standard, though some people use VST2. Apple’s “AU components” are also “host dependent” apps, as are Avid’s AAX “apps.”
Logic Pro, Cubase, Live, Protools, Reaper, etc can ALL “run” these VST3 “apps.” So you can buy Serum from “XFer Records,” and have that single “Serum.vst3” app run in all the DAWs. The “VST3” is an “app” in this example, but it requires a “hosting DAW” to run them in. Some VST3 purchases also include “stand alone” apps that can run by themselves, like the Vital synth. But that’s different.
Now let’s examine the kinds of files requires by the VST3 to fulfill their purpose: Those can take many forms, but the VSTSound file you’re talking about is a proprietary format of “sound” file that Steinberg uses as containers for their sounds. Just like Ableton uses .aif files that are proprietary, Steinberg uses VSTSounds as the libraries for various instruments and plugins they write. The main purpose for this is “copy protection” so that they don’t spend thousands of dollars creating amazing quality sound libraries for sale that other people can just copy and use for free. Juxtapose this with my Serum example, and you’ll see 3rd party creators of “Serum” presets (e.g. Surge Sounds) just trust that when you buy their presets you won’t be a schmuck and give them away. But you COULD.
On to your example: Say you’ve created a project and used Pop Guitar 2 samples in it to write a song. You could certainly copy that project and give it to someone else, and you could even copy the “Pop_Guitar_2.vstsound” file and give it to them, but it won’t work unless the system that you have copied it to is licensed to use Pop Guitar 2. Not just “Cubase,” but that specific commercial library.
Depending on the project and the use, what you would have to do is bounce the audio file itself to a generic WAV (or similar) and copy that file over to the new project.
Hope that helps without making things too complicated 
2 Likes
These 2 replies are very helpful!
I asked Copilot to describe VST
Describe the scope of Steinberg’s VST spec
The Steinberg Virtual Studio Technology (VST) specification is a widely adopted standard for integrating software audio synthesizer and effect plugins with audio editors and recording systems. Here’s an overview of its scope:
- Plugin Types: VST supports both instrument plugins (like synthesizers and samplers) and effect plugins (like reverb, delay, and equalizers).
- Cross-Platform Compatibility: VST plugins are designed to be cross-platform, meaning they can run on Windows, macOS, and Linux.
- Real-Time Processing: VST plugins are optimized for real-time audio processing, making them suitable for live performances and studio work.
- Automation: The VST spec includes support for parameter automation, allowing users to create dynamic changes in plugin settings over time.
- MIDI Integration: VST plugins can be controlled via MIDI, enabling them to be used with MIDI controllers and sequencers.
- Modular Architecture: VST plugins follow a modular architecture, allowing for flexible and scalable audio processing setups.
- User Interface: The VST spec includes guidelines for creating user interfaces, ensuring a consistent look and feel across different plugins
There’s a tendency to associate VST mostly with plug-ins because of the huge number of them that exist. But it is really a much broader & deeper specification. Think about it the Cubase Audio engine is VST compliant.
However, I’m really not so sure that item 7 is up to the task.