Glaceverb gone?

[pheeleep]

Is Glaceverb by DaSample gone? The web site seems dead. The download link on KVR doesn't work... Dang, wish I had made a backup..

[halcyon68]

Yep. The DaSample website apparently went down a while ago, but you can still find Glaceverb on some other websites.

[pheeleep]

Found it here:

http://www.vstplanet.com/Effects/Effects.htm

Thank you!

[redshift factor]

I would suggest replacing all instances of GlaceVerb with a suitable alternative.
It's not a good idea to be reliant on abandonware, particularly when they were made with old versions of SynthEdit, as this one was.

You may one day discover your old projects are broken after updating your host.

[antto]

eh.. i don't get it, old SynthEdit versions?
a lot of VSTs are made with an old version of the VST SDK in fact, and they run on _old_ versions of VST-Hosts as well as on newer ones
newer VST Hosts must support plugins made with the older SDKs..

btw, i like GlaceVerb a lot

[redshift factor]

SynthEdit has well documented issues with multiple instances, multi-processors, GUI, and with initiating when reopening saved projects. I don't know if they have been fixed in newer versions, but they would certainly be present in a plugin of GlaceVerb's age.

SynthEdit is not the same thing as the VST SDK. You cannot compare them.
It is a VST plugin compiler, and implements the SDK poorly.

And yes, every time the VST spec is updated, there are some old plugins that cease working in updated VST hosts. Those that are no longer supported with updates can wreck your project and permanently render it unable to load.

[Klemperer]

And yes, every time the VST spec is updated, there are some old plugins that cease working in updated VST hosts. Those that are no longer supported with updates can wreck your project and permanently render it unable to load.

For people with multicore machines, of course the vast majority by now, the old SE bug is simply fixed as far as I know - if you got 2 or more instances of glaceverb running, simply rename 2, 3 and so on...
The newest Synthedit (I bought it ages ago but don't use it today, so am not sure if it is out by now or just spoken about here at KVR ) fixes this, which of course does not help old plugins which are not updated.

Most hosts load projects with missing or unuseable plugins anyway. Reaper keeps their configuration and loads without a problem, as does Podium, energyXT, and I guess many many others.

I understand what redshift thinks, but just want to say - it's not a huge problem using plugins you love as long as they work - replace them as soon as they would not work in the future. I use a lot of plugins that are not longer updated, and it just works most of the time, quite well

[A.M. Gold]

Those that are no longer supported with updates can wreck your project and permanently render it unable to load.

Not sure about your host but with mine, Tracktion 2, all I would do is delete the bad plug-in from the VST folder and reload the project.

[redshift factor]

What both of you are saying will work of course, but as abandoned plugins age and the hosts continue to march on, the list of necessary workarounds grows longer.

Is it really worth the hassle for some old free SynthEdit plugin?
If an abandoned plugin no longer works with a host update, the only options are either downgrade, or remove the offending .dll from Vstplugins to get the project to load again. But then you've lost the effect and will have to rebuild a similar setting in a new plugin from memory.

That can prove to be difficult if not impossible. Which is why I suggest just clearing out the cobwebs now at your leisure, while you can still use them as a reference at least, before you find yourself in an emergency situation.

[Cordelia]

What both of you are saying will work of course, but as abandoned plugins age and the hosts continue to march on, the list of necessary workarounds grows longer.

Is it really worth the hassle for some old free SynthEdit plugin?
If an abandoned plugin no longer works with a host update, the only options are either downgrade, or remove the offending .dll from Vstplugins to get the project to load again. But then you've lost the effect and will have to rebuild a similar setting in a new plugin from memory.

That can prove to be difficult if not impossible. Which is why I suggest just clearing out the cobwebs now at your leisure, while you can still use them as a reference at least, before you find yourself in an emergency situation.

Well, sure. It's a good idea to render tracks before doing any major update. No one should allow themselves to get into an emergent situation. But a host update rendering a plugin unusable? Has this happened to you? I'm still using ReFX Trasher which I used on my PII with nTrack. Neon works on my quad core with Reaper.

Someday all of our 32bit plugins might not work, someday the VST standard may be gone, firewire looks as though its days are numbered, I have nothing to play back my 16 track tapes on...

The possible future demise of support for some older SE plugins is so low on my list of worries, it is the lowest worry in the last category in the lowliest subset of worries- "worries about my plugins".

[eduardo_b]

I would think the only issue for staying with this reverb is if it meant re-doing a lot of projects with another reverb and it was going to take hours upon hours of effort. Otherwise, I think it's time to move on. There are any number of other reverbs that can easily replace this one.

[metamorphosis]

SynthEdit has well documented issues with multiple instances, multi-processors, GUI, and with initiating when reopening saved projects. I don't know if they have been fixed in newer versions, but they would certainly be present in a plugin of GlaceVerb's age.

SynthEdit is not the same thing as the VST SDK. You cannot compare them.
It is a VST plugin compiler, and implements the SDK poorly.

And yes, every time the VST spec is updated, there are some old plugins that cease working in updated VST hosts. Those that are no longer supported with updates can wreck your project and permanently render it unable to load.

I've never had a single problem with Glaceverb, running on three different machines and Tracktion versions, one multicore, the others not.
It's my favourite reverb, regardless of age. VST DLL's aren't like programs. They don't get made 'incompatible' by newer OS's...

[xybre]

Those that are no longer supported with updates can wreck your project and permanently render it unable to load.

Wow, I'd hate to have your host

[robenestobenz]

There are any number of other reverbs that can easily replace this one.

Is there? I found it unique for unnatural reverb effects (check out the FX - * presets for example).

//Edit: As for the obsolesence scenario... unless the VST standard goes away altogether, I find it hard to imagine such a large swathe of plugins would ever become unusable without one of the developer community's many industrious souls writing a wrapper.

[redshift factor]

I have yet to come across a plugin that is truly irreplacable.
Lord knows a free SynthEdit reverb isn't going to be the first.

If you believe this plugin is indespensable to you, then by all means, continue using it.
But if it's just another of many free reverbs to you then I think that under the circumstances, it's best to dump it.

This is just my personal philosophy, because I don't want to find myself flatfooted one day.
I used to have Glaceverb on a few tracks myself, but swapped it out after it went MIA.
I also deSynthEditted my Vstplugins folder once and for all. Too many of the above problems for a class of plugins that tend to be inferior more often than not.