Spire Synthesizer

[fgimian]

I'm getting CPU huge spikes when changing presets here on 1.5.2, anyone else? I rolled back to 1.5.1 and it is significantly less extreme when changing presets.

I even checked v1.1 and that matched 1.5.1, but 1.5.2 almost pushes my CPU to the red each time I change presets.

Every time I save my project, I get a huge spike too.

Cubase 9.5 x64 / Windows 10 2004 / Focusrite Clarett 2Pre Thunderbolt

[frag]

I'm getting CPU huge spikes when changing presets here on 1.5.2, anyone else? I rolled back to 1.5.1 and it is significantly less extreme when changing presets.

I even checked v1.1 and that matched 1.5.1, but 1.5.2 almost pushes my CPU to the red each time I change presets.

Every time I save my project, I get a huge spike too.

Cubase 9.5 x64 / Windows 10 2004 / Focusrite Clarett 2Pre Thunderbolt

Let's wait for vega555 - it's possible that some of the old code got into v1.5.2 accidentally.

Anyway, it seems that Preset Manager needs a couple of more updates to be really stable... Once you try it, it's difficult to go back to v1.1.17, everything is so much faster and more intuitive!
But, the "bugs" have to be eliminated.

[claudedefaren]

...

[the.new.me]

Ok, hmm how to save the preset?

If i press on edit name and rename it, "save" is greyed out and says "init already exist"

ok so im able partialy to save presets, its very random (maybe there is some pattern to that i dont know), sometimes it does sometimes it doesnt. Also if i press INIT Spire creates new init preset.

Yeah i think its better to revert back to 1.17 till browser issues will be fixed

[KrisWV]

Gorgeous synth! Its pads has a warmth and breadth that I didn't found anywhere else.

[vega555]

For all users who are having problems with 1.5.2:
We recommend refreshing the preset manager, to do that please delete the workspace.db file.
For Windows it is located in C: \ Users \ "Username" \ AppData \ Roaming \ RevealSound \ Banks
For Mac OS it is located in / Users / "Username" / Documents / RevealSound / Bank

If any problems still persist please contact our support@reveal-sound.com with detailed information. The most helpful will be a video with the steps and the issue itself.

Important note: It is not recommended to use versions 1.1 and 1.5 at the same time. Otherwise, the "Old Projects Presets" folder will grow and load the system.

First of all, we intend to correct all existing errors. We will do our best to add all the proposed "improvements" after all corrections and bugfixes.

[frag]

For all users who are having problems with 1.5.2:
We recommend refreshing the preset manager, to do that please delete the workspace.db file.
For Windows it is located in C: \ Users \ "Username" \ AppData \ Roaming \ RevealSound \ Banks
For Mac OS it is located in / Users / "Username" / Documents / RevealSound / Bank

If any problems still persist please contact our support@reveal-sound.com with detailed information. The most helpful will be a video with the steps and the issue itself.

Important note: It is not recommended to use versions 1.1 and 1.5 at the same time. Otherwise, the "Old Projects Presets" folder will grow and load the system.

First of all, we intend to correct all existing errors. We will do our best to add all the proposed "improvements" after all corrections and bugfixes.

Thanks for the advice! I can confirm that after deleting workspace.db, preset location is now properly recorded with both SPF2 and SBF files. In a way, I was right that the "old code" creates the issue - however, it was workspace.db, not the DLL itself.

Just a warning - if you have Favorites, they will be lost after deleting workspace.db. Also, if you have saved projects with Spire 1.5, used patches will appear completely "SEPARATED" from the preset manager: no name in the manager, no way to copy or save the used preset. The name shows in the old upper filed, though. There is a simple solution: just touch the pitch bend wheel, and the preset will get "orange" color, and the option to "Save As" will be offered now (as if the patch was modified). "Copy" is possible only after saving.

ALWAYS BACKUP WORKSPACE.DB BEFORE DELETING. I did.

I suppose this is something to investigate. If workspace.db needs to be deleted for some reason, this means that all patches in used projects become "separated" from their original banks/folders. It's not a problem now, but if one has years of projects and has to delete workspace.db, it could be very annoying... Particularly if you use FAVORITES a lot!

HISTORY STOPPED WORKING. Is there a way to fix this? I thought it would be rebuilt with workspace.db, but it's not working at all. Nothing is recorded anymore. I don't use it often, but it's an interesting option. The Undo option works with Preset manager, but only for one step back! Also, I've noticed History recorded only one preset but when I clicked it, the entire host crashed. So, where is the preset History recorded? It seems it's not within workspace.db, so if one deletes .db the history becomes corrupted! I just hope it's not within the Windows registry.

[frag]

For all users who are having problems with 1.5.2:
We recommend refreshing the preset manager, to do that please delete the workspace.db file.
For Windows it is located in C: \ Users \ "Username" \ AppData \ Roaming \ RevealSound \ Banks
For Mac OS it is located in / Users / "Username" / Documents / RevealSound / Bank

If any problems still persist please contact our support@reveal-sound.com with detailed information. The most helpful will be a video with the steps and the issue itself.

Important note: It is not recommended to use versions 1.1 and 1.5 at the same time. Otherwise, the "Old Projects Presets" folder will grow and load the system.

First of all, we intend to correct all existing errors. We will do our best to add all the proposed "improvements" after all corrections and bugfixes.

Thanks for the advice! I can confirm that after deleting workspace.db, preset location is now properly recorded with both SPF2 and SBF files. In a way, I was right that the "old code" creates the issue - however, it was workspace.db, not the DLL itself.

Just a warning - if you have Favorites, they will be lost after deleting workspace.db. Also, if you have saved projects with Spire 1.5, used patches will appear completely "SEPARATED" from the preset manager: no name in the manager, no way to copy or save the used preset. The name shows in the old upper filed, though. There is a simple solution: just touch the pitch bend wheel, and the preset will get "orange" color, and the option to "Save As" will be offered now (as if the patch was modified). "Copy" is possible only after saving.

ALWAYS BACKUP WORKSPACE.DB BEFORE DELETING. I did.

I suppose this is something to investigate. If workspace.db needs to be deleted for some reason, this means that all patches in used projects become "separated" from their original banks/folders. It's not a problem now, but if one has years of projects and has to delete workspace.db, it could be very annoying... Particularly if you use FAVORITES a lot!

HISTORY STOPPED WORKING. Is there a way to fix this? I thought it would be rebuilt with workspace.db, but it's not working at all. Nothing is recorded anymore. I don't use it often, but it's an interesting option. The Undo option works with Preset manager, but only for one step back! Also, I've noticed History recorded only one preset but when I clicked it, the entire host crashed. So, where is the preset History recorded? It seems it's not within workspace.db, so if one deletes .db the history becomes corrupted! I just hope it's not within the Windows registry.

Seriously, what's with the History now?
I tried literally everything: repairing Spire, completely uninstalling and reinstalling, re-scaning the database, searching the registry for patch names, searching Users folder.
We're not going to get far if every fix creates a new issue
Where is the History data located??? The entire feature is dead.
I even restored the old workspace.db and the history until removal is visible, but new entries are not recorded at all.
It appears that History uses BOTH workspace.db and some external element, which is now completely corrupted.

So, it does seem that v1.5 is still Beta... No matter how I like the Preset manager, I am forced to go back to 1.1.17, 1.5 is just too unstable and unpredictable.

[dionenoid]

Good info. I'll keep from updating for now, wait 'til the issues are fixed

[chk071]

I experienced another weird bug where the init patch changes, when you click the init button again. I.e., the init patch is different when you add a instance of Spire, or click the "init" button.

I must admit that I'm a bit disappointed by all these bugs. Spire's new versions really need more testing.

[vega555]

Spire 1.5.3 with fixes for history function in Preset Manager has been added to www.reveal-sound.com

[maniacoli]

Spire Synthesizer update to v1.5.3 - build 5091 (2020.09.14)
==========================
* Fix preset history updating issue

[claudedefaren]

...

[v1o]

Spire 1.5.3 with fixes for history function in Preset Manager has been added to www.reveal-sound.com

Is the CPU back down to 1.17 levels?

You only need to go 3 pages back

The newest [Spire 1.5.1 5079] does solve the CPU usage a lot. It is as good as the version 1.17 Thanks Reveal-Sound team

[claudedefaren]

...