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!

[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.

[fisherKing]

1.1.1 still buggy. Downloaded the demo, almost purchased a license but then crashed FL Studio 12.2, so..I uninstalled the demo inmediately.

Why you come to tell people here instead of contacting Reveal-Sound, or ask people here, and try to fix the problem is beyond me. It's working here in 3 different hosts without crashing btw, go figure.

You can even ask on FB btw, they usually answer there even.

personally...first thing i did was email support. but while i wait that out (and they do get back, but it may take some time), am sharing my experience here, one useful aspect of such a forum: information.

[chk071]

It's cool. It's just that it sounded like (well actually, it's exactly what has been posted) "Tried the demo, crashed FL Studio, so i immediately uninstalled it." Well, what exactly is the use of such info? I mean, the fact that he uninstalled it immediately is not exactly very relevant or interesting to me (or anyone else), while on the other hand, feedback like "It crashes my host", or "It still crashes my host" after the next update is indeed helpful, of course accompanied with infos on the used OS and DAW. But, the best case would of course be to conduct these infos straight to the developers, so they can figure why Spire crashes under FL Studio, or Logic (or MuLab, i just saw). That's something which they can work with, and ultimately the user will benefit from it too, when they manage to get Spire to work on those DAW's.

[fisherKing]

It's cool. It's just that it sounded like (well actually, it's exactly what has been posted) "Tried the demo, crashed FL Studio, so i immediately uninstalled it." Well, what exactly is the use of such info? I mean, the fact that he uninstalled it immediately is not exactly very relevant or interesting to me (or anyone else), while on the other hand, feedback like "It crashes my host", or "It still crashes my host" after the next update is indeed helpful, of course accompanied with infos on the used OS and DAW. But, the best case would of course be to conduct these infos straight to the developers, so they can figure why Spire crashes under FL Studio, or Logic (or MuLab, i just saw). That's something which they can work with, and ultimately the user will benefit from it too, when they manage to get Spire to work on those DAW's.

agreed. easy to walk away from a problem, but much more rewarding to solving it. and sometimes we need help with that...

[Yorrrrrr]

Seems some devs don't even bother testing these plugins, just for the sake of getting them online to sell, as the plugins crash inmediately in some cases (FL Studio, Logic and MuLab, to name a few). There is not much info I can give beyond the fact the plugin crashed in FL Studio 12.2 almost instantly, even after doing some workarounds (which no other VST that adheres to the VST plugin standard even needs..), so it can at least work, initially. But, no worries. I still will send a support message and hopefully they take the time to reply and try to solve possible issues (maybe it's my system?), because I really like Spire and hope to buy it again when it works properly. Sorry if my comment was innappropriate. Thanks.

[Orbit-50]

Sorry if my comment was innappropriate. Thanks.

It wasn't inappropriate. What chk071 was saying basically is that coming here stomping your feet up and down in this forum might not be as fruitful as sending a support request to Reveal Sound stating the problems that you are experiencing. Do you have any other hosts to try, such as Live or Cubase? Surely you have to have a cornucopia of hosts lying around on your hard drive. No?

[Yorrrrrr]

No, just FL Studio. And this system, if it matters at all:

- Motherboard: MSI Z170A Gaming M7
- CPU: 6th Gen Intel Core i7 6700K @ 4.5 GHz
- RAM: 16GB (2x8GB) G.Skill Ripjaws V DDR4 3000 CL15
- CPU Cooler: Noctua NH-U12S
- Power Supply: Corsair AX750
- OS Drive: Samsung SM951 M.2 PCIe 3.0 x4 AHCI 256 GB SSD
- Data drives: Samsung 850 Pro 256 GB SSD, external Toshiba USB 3.0 drive
- Audio: RME Babyface @ 256 samples ASIO buffer
- Video: MSI GTX 980 Ti Gaming 6G
- OS: Windows 10 64-bit
- Audio Monitors: JBL LSR305, Audio-Technica ATH-M50
- Video Monitor: ASUS VG248QE 144 Hz
- Mouse: Logitech G402
- MIDI controller: Novation Launchkey 25 MK2

As I said. I will send a support request on the website. Thank you.

[Orbit-50]

You know what? I'm going to try this on my system. I'll be back.

[aMUSEd]

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?

[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.

[Orbit-50]

1.1.1 still buggy. Downloaded the demo, almost purchased a license but then crashed FL Studio 12.2, so..I uninstalled the demo inmediately.

I'm not having any issues at all with Spire v1.1.1 in FL Studio 12 on Windows 8* 64 bit.





*I've not let my computer update to Windows 10.

[aMUSEd]

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.

Considering this is a plugin renowned for the large amount of banks made for it that's a pretty insane thing for a developer to do, it basically means all those banks will need redoing, something many sound designers would balk at. I know when XILS 3.2 broke patch compatibility I basically lost the motivation to make more patches for it as I had a hundred patches that stopped sounding as I made them (some just don't work at all and can't be fixed) - I know other SDs who feel the same way, same with Iris 2, they completely sabotaged their user base by pissing off the people who had invested in buying all their soundbanks for version 1. u-he got it right by making Zebra 2.5 compatible with older versions with a version switch, that's what should have been done here too.

[fisherKing]

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.

Considering this is a plugin renowned for the large amount of banks made for it that's a pretty insane thing for a developer to do, it basically means all those banks will need redoing, something many sound designers would balk at. I know when XILS 3.2 broke patch compatibility I basically lost the motivation to make more patches for it as I had a hundred patches that stopped sounding as I made them (some just don't work at all and can't be fixed) - I know other SDs who feel the same way, same with Iris 2, they completely sabotaged their user base by pissing off the people who had invested in buying all their soundbanks for version 1. u-he got it right by making Zebra 2.5 compatible with older versions with a version switch, that's what should have been done here too.

it's nothing like that. 1.1 plays all the eariler soundbanks fine, there are just some slight sonic changes (among other things). whether 1.1 ultimately replaces the earlier version, it's an update, not a new plugin.

[ATS]

was coming here to see how it goes with others. For me it crashes Studio 1 every time. Unusable now. Worked before.