Well, the wavetables are saved in the patch, that explains the filesize. You can even save the wavetable to your folder, if you like. Also the sampled noise-source is stored there.
So, I don’t think there’s much headroom for reducing the filesize of patches.
So since the wavetable is saved into the patch, that would imply that you can use presets even if you don’t already have that wavetable? I was thinking about sharing some presets, but a lot of them have wavetables from massive.
For example the developer of Serum posted at KVR, that his wavetables contain a flag signalling that it is a factory wavetable and therefore does not need embedding. But since the number of wavetable in the basic version of Vital is so small, that wouldn’t help much.
Another idea could be, taking inspiration from Reason, having an “export patch” function, which only embeds the wavetable and noise sample in patches meant for sharing. But Reason has also a lot of DRM going on, and I’m not certain Vital’s dev wants that.
I couldn’t load that patch in Vital, due to it being created in a newer version of Vital. Did you update inbetween making those patches? And if yes, how? Although “check for updates” is activated, my version of VItal didn’t update itself. And when I redownloaded the installer, it was exactly the same file as previously.
Thanks @andrew_a, redownloading and installing over the old version seemed to do the trick. Although neither the download page, nor the downloaded installler indicated any version number. It only appears in Vitals info page.
So, here are my first two… Trance Supersaw.vital (170.8 KB) Rhodes-like.vital (256.8 KB) this one has a custom wavetable I created.
For those of you on Windows, you’ll need to create a folder like Community\Presets in your Documents\Vital folder. The “Presets” bit is the important part as Vital seem to use that naming convention to locate presets. Like so: