Spire Synthesizer

[Elektronisch]

Greetings!

We are happy to inform you about new version of Spire - 1.1.1
Major objective - a lot of bug fixes were added. Now you can experience higher stability. Some presets, built in previous versions, will now sound correct in upcoming version.

Recommended settings for FL Studio users: http://reveal-sound.com/knowledge.php?27-30

Do not forget to visit our site: Christmas sale is on!

Merry Christmas and a Happy New Year!!!

http://reveal-sound.com

Thank you for this update

I have a question - why new versions install as separate DLLs ?

Merry christmas and happy holiday!

This is a reply to a similar question someone asked on their FB page:

Reveal Sound Spire The fact is that new version was completely developed from scratch(global update)
However, there are some bugs in Spire 1.1, that need to be fixed. It would be very risky to make older release been instantly replaced by new one. Because a lot of our clients have unfinished projects with Spire 1.
Therefore, we decided to go in a safe way: Old projects will continue to be produced on proven, stable and fixed plug-in.

Hence, all new projects can be produced with new Spire. One way or another, old plugin will be replaced by the new one.

So when bugs are fixed and it's more compatible with old presets will it go back to being compatible with the old version so people can actually open their old projects with a current version instead of being stuck with an abandoned one?

No idea, but i don't see how this is any different to a version 2 of a soft synth coming out, and it isn't compatible with v1 sounds. After all, you're not "stuck with an abandoned one", but only need it for project compatible reasons, and use the new version for your future projects anyway. The way i see it, it's a workaround so that you don't lose your old projects.

My personal guess is that version 1.1 and upwards never will be 100% compatible with sounds from the versions before. Too much has changed under the hood for that to happen as far as i can see.

I see the logic here from Reveal Sound, but with my question initialy i ment that there is 1.1 and now there is 1.1.1 1.1.1 is an update of 1.1 but its installed as separate DLL.

Tho i have an idea:

Why not to make an installer where it says "overwrite the original spire 1.0" and "install new dll 1.1" also it says "warning overwriting might give incompatibility issues". Well you have the idea right?

Btw Spire 1.1.1 64bit works fine here on FL Studio 12.2 64bit, Macbook Air 11, Windows 10. Gonna try also on my work desktop pc in the studio.

[Dúnedain]

To me it is not clear how many layers / amps it has?

[Elektronisch]

To me it is not clear how many layers / amps it has?

1

[chk071]

Greetings!

We are happy to inform you about new version of Spire - 1.1.1
Major objective - a lot of bug fixes were added. Now you can experience higher stability. Some presets, built in previous versions, will now sound correct in upcoming version.

Recommended settings for FL Studio users: http://reveal-sound.com/knowledge.php?27-30

Do not forget to visit our site: Christmas sale is on!

Merry Christmas and a Happy New Year!!!

http://reveal-sound.com

Thank you for this update

I have a question - why new versions install as separate DLLs ?

Merry christmas and happy holiday!

This is a reply to a similar question someone asked on their FB page:

Reveal Sound Spire The fact is that new version was completely developed from scratch(global update)
However, there are some bugs in Spire 1.1, that need to be fixed. It would be very risky to make older release been instantly replaced by new one. Because a lot of our clients have unfinished projects with Spire 1.
Therefore, we decided to go in a safe way: Old projects will continue to be produced on proven, stable and fixed plug-in.

Hence, all new projects can be produced with new Spire. One way or another, old plugin will be replaced by the new one.

So when bugs are fixed and it's more compatible with old presets will it go back to being compatible with the old version so people can actually open their old projects with a current version instead of being stuck with an abandoned one?

No idea, but i don't see how this is any different to a version 2 of a soft synth coming out, and it isn't compatible with v1 sounds. After all, you're not "stuck with an abandoned one", but only need it for project compatible reasons, and use the new version for your future projects anyway. The way i see it, it's a workaround so that you don't lose your old projects.

My personal guess is that version 1.1 and upwards never will be 100% compatible with sounds from the versions before. Too much has changed under the hood for that to happen as far as i can see.

I see the logic here from Reveal Sound, but with my question initialy i ment that there is 1.1 and now there is 1.1.1 1.1.1 is an update of 1.1 but its installed as separate DLL.

No, it isn't. What gave you that idea?

1.1 plus and 1.0.20 and lower=separate plugins. 1.1.1 and upwards replace 1.1 therefor.

[fisherKing]

1.1.1 is an update for 1.1, (which is a separate install from the earlier spire). there are some changes in the sound, in cpu use, in options, the GUI... but the new plugin plays any and all presets from the earlier version (or 3rd party soundbanks).

[Elektronisch]

No, it isn't. What gave you that idea?

1.1 plus and 1.0.20 and lower=separate plugins. 1.1.1 and upwards replace 1.1 therefor.

Sorry, indeed!

[mutantdog]

I see they've fixed the problem of presets not being able to load or save as .spf. Still can't copy/paste presets between 1.0 and 1.1 though.

I haven't had time to test it for stability yet though, not sure if i can be bothered just yet. I expect it may take a couple more updates before everything's running nice and smooth, I'll probably stick to the old one a little bit longer.

[chk071]

No, it isn't. What gave you that idea?

1.1 plus and 1.0.20 and lower=separate plugins. 1.1.1 and upwards replace 1.1 therefor.

Sorry, indeed!

No problem. It's really a bit confusing one must say. Maybe they should have just named it version 2 hehe. But who knows, maybe they save up that version number for a paid update, which would be fair enough considering what they have in the bag still.

[chk071]

I see they've fixed the problem of presets not being able to load or save as .spf. Still can't copy/paste presets between 1.0 and 1.1 though.

I haven't had time to test it for stability yet though, not sure if i can be bothered just yet. I expect it may take a couple more updates before everything's running nice and smooth, I'll probably stick to the old one a little bit longer.

One thing i noticed is that the pops/clicks when activating fx, or when adding a filter (i think) still haven't been removed.

[core]

I see they've fixed the problem of presets not being able to load or save as .spf. Still can't copy/paste presets between 1.0 and 1.1 though.

I haven't had time to test it for stability yet though, not sure if i can be bothered just yet. I expect it may take a couple more updates before everything's running nice and smooth, I'll probably stick to the old one a little bit longer.

One thing i noticed is that the pops/clicks when activating fx, or when adding a filter (i think) still haven't been removed.

I don't have any pops or clicks with the fx or adding a filter in v1.1.1 in FL Studio (64-bit).

[chk071]

I will test a bit more, tbh, i'm not sure what situation exactly caused the pops, maybe it was using the wet/dry control of the fx too, or adding some X-Comp.

[fischkopf]

Still buggy in FL Studio, the OSC phases sound messed up when you reload a project.

[Dasheesh]

yosemite/AU/macbook pro 2012.

Downloaded the newest version yesterday. It's more unstable than the previous ones. Crashes one daw consistently and the gui just freezes in another. Pretty ridiculous actually. It's unusable right now and I'm going back to 1.2 until I get word it works. it sounds great though. Really like the sound. The shadowing is too heavy if you ask me. Looks nice otherwise. It's a little annoying but maybe that's what the kids like. I think the quick load of banks is completely redundant as it's no faster than going to the menu. Hope it all gets sorted soon.

[Dasheesh]

SO I ripped all of 1.1.1. whatever and reinstalled 1.0.2.whatever and now it will no longer read my license that I threw down the full 200$ for... I'm completely without spire now. What a cluster software is.

[aMUSEd]

This has got to be one of the most poorly managed updates ever. They should have waited till it was working properly and not forced this change of plugin ID on everyone just because it's not yet stable.