Reveal Sound Spire v1.5.11 CE-V.R

quote by GokhanH33So does the VST3 crash or not? Some say it crashes be careful, some say doesn't crash.

broken in FL Studio when save project and open later

VST2 work fine

If you're like me and want to backup your newest or custom soundbanks, they are located at C:\Users\<username>\AppData\Roaming\RevealSound\Banks
then just sort by date modified to find your latest added soundbanks.

V.R + TCD presets Incl. "workspace.db"
https://peeplink.in/c3733f7525ed

No need to reindex (I hope)

back to "old" Reveal.Sound.Spire.1.5.11.5227.x64.VST2-ArticStorm release. Get a database update fail on V.R release, both with vst2/vst3 and running DAW as admin

Had to set my virtual memory to 16gb (fixed) in order to finish the scan. Live was crashing.

It seems this one includes VST3 64 and doesn't include VST2 32 anymore.

Sorry but this is all B*u*ll*sh*it talk. No problems at all, at least with new projects (older projects I can't confirm because I doesn't have one with Spire). I even moved presets folder from one disk to another (both NVME disks, one of them really fast with up to 7,3 GB/s) because it has a lot of small files I didn't want on my main disk. I created a symbolic link to that disk.
Uninstalled the old 1.5.11 version from R2R from April last year. Uninstaller deleted workspace.db but didn't remove my huge presets library from user folder, I moved it to the new location on the other disk and in the original user folder I created a symbolic link to that disk.
Then I installed this new version from today. First, it is simply not true that it doesn't install VST2. If you mark both VSt2 and VST3, you get both VST's installed! I installed both versions because of the rumors here that VST3 doesn't work correctly. And there wasn't any problem with my symbolic link folder for user presets.
Then I started my DAW, Studio One latest version 6. When it came to scanning the VSTs, it needed a while to scan Spire, something between 5 and 10 minutes. I opened a new song, created 3 instrument tracks with different VSTs, one of them Spire VST3. When I assigned Spire to one of the tracks, it needed another at least 5 minutes, during this time Studio One was not reacting to any mouse clicks.
Just recorded a few beats on every tracks and saved the project. Closed DAW and re-opened the project, no problems at all to access the Spire track and add something.
DAW opens as fast as always normally and also opening a new project with Spire doesn't cause any delays now.
So for whatever reason it needs two initial scans of your presets, depending on your computer this can also take a lot longer.
In any case there is no need to go back to older versions, this one works without problems, it just needs his time to initialize the presets folder on first running, after that it loads as fast as any other VST3. But depending on your PC you need some patience for the first two initial scans that quite a few of you probably didn't have.
if your DAW supports VST3 there is no reason to install VST2 version, with one exception.
Projects saved with an older VST2 version and now opened with this one here will need VST2, though I can't confirm if there will be a problem or not. Otherwise I don't see any problems at all.

So good, thanks VR!

I am having a recurring issue across Spire releases (VR & R2R) and Win 10 & 11. Any help would be appreciated...
When I am browsing presets the browser often stops responding after changing the search term. It freezes and does not return a search. Perhaps it has to do with the volume of soundbanks in this release, but I've not heard of others experiencing this quirk.

I've rebuilt the database, re-scanned etc & tried relocating banks to a secondary drive (both my drives are PCIe 4.0). Same issue in various DAWS. I'm thinking I'm just lucky

Any input would be valued

When i load VST 3 plugin sometimes Cubase shows +100 dB clip for random patches, later it stops.