Stone Voices - DReverb 2.0 (Free)

[El°HYM]

Great developer.

[dmcsweeney]

Thanks for the update Vasyan.
Sadly the latest .vst3 from your website isn't scanning in Reaper on Windows 11.
I've got it in the same folder as v1, which is still scanning successfully. (commonfiles>vst3).

* It does scan correctly if I remove the old v1, but I would have thought that your latest update was a workaround for that.... correct me if I'm wrong.

The name of the plugin has been changed to DReverb2, both the file name and the internal name used by the DAW.

* I recommend double checking the internal plugin ID has been correctly changed, this will ensure that v1 and v2 can live side by side successfully.

[vasyan]

Thanks for the update Vasyan.
Sadly the latest .vst3 from your website isn't scanning in Reaper on Windows 11.
I've got it in the same folder as v1, which is still scanning successfully. (commonfiles>vst3).

* It does scan correctly if I remove the old v1, but I would have thought that your latest update was a workaround for that.... correct me if I'm wrong.

The name of the plugin has been changed to DReverb2, both the file name and the internal name used by the DAW.

* I recommend double checking the internal plugin ID has been correctly changed, this will ensure that v1 and v2 can live side by side successfully.

The internal name is defined as

Code: Select all

 PLUG_NAME "DReverb2"

And I did not change the identifier, because then it will be more difficult to recognize presets and banks of the old version in the new version. After all, one of the advantages of the new version is backward compatibility with the old one in terms of loading .fxp and .fxb files.

I want to ask why do you need the old version when there is a new one?

[plexuss]

Update: DReverb2 AU is working fine. I made an error in my post shown below thinking it was DReverb2 that was not working. DReverb2 works fine.

DReverb 2.0 AU did not initially scan when I booted Reaper 7 under macos 12. I rebooted and DReverb 2.0 showed up but under StoneVoices not Stone Voices like the previous version. Now there is Stone Voices and StoneVoices in the manufacturers list which is annoying. DReverb 2.0 did open but without a GUI, showing the default parameter sliders. Sounds good though but not the easist to use with sliders.

[vasyan]

Many people write to me in private messages that when trying to load DReverb2 builds for AU, the message is: “DReverb2.component” cannot be opened because the developer cannot be verified.
I can't imagine what this might be related to, however, in older versions of macOS, for example, in version 10.11.6 El Capitan, AU the plugin version loads without problems. This is probably due to the fact that Apple's policy towards unidentified developers has been tightened in more recent versions. Unfortunately, I can't get an Apple certificate, as Russian developers have been sanctioned. And getting a certificate costs money, which is economically unprofitable for free distribution of the plugin.
I do not know if there are workarounds to solve this problem, so if anyone can help, write in private messages.

[kidslow]

It's due to lack of signing certificate. There is a codesign command that can be used to workaround this issue. I don't have the plugin to verify exact syntax, but would be something like:

Code: Select all

 sudo codesign -fs - "/Library/Audio/Plug-Ins/Components/DReverb2.component" --deep

[dmcsweeney]

Thanks for the explanation Vasyan. I must have gotten the wrong idea from your latest update notes.

Personal preference: I don't mind too much, but on loading the newest version the default preset isn't the same - and - the older GUI is easier on the eyes for me, so I may just stick with the old version instead of the new version, especially if it's more or less the same.

All the best.
Dom

[vasyan]

However, I would like to remind you that the first and second versions of DReverb are incompatible, so you must decide which version you want to use, since in some DAWs you will not be able to use both versions at the same time.
This also means that if you used the old version of DReverb in your projects, then installing the new version, it incorrectly counts the saved preset parameters, which will spoil the sound. Therefore, be careful when updating the DReverb version.

[dmcsweeney]

- first / second versions are incompatible
but you said that it was backwards compatible?

- daws won't be able to use both versions at the same time -
yes, that's the reason I wrote here and in the old v1 thread, but we've gone over that already

anyway.. like I said before, I'm happy with the old version, but I'm happy you are enjoying updating things as you see fit and I'm sure the new version will suite others

[Agreed]

Doesn't scan for me in the most recent version of Reaper 64-bit on Windows 11. I end up with two folders in my plugin listing, one for Stone Voices and one for StoneVoices, but only dReverb 1.0 actually shows (and it shows only in the "Stone Voices" labeling, not "StoneVoices"). So this is a bit of a phantom for me at this time. That does mean that I can imagine it to sound impossibly good, though. Like angels singing, in my imagination, I can't wait to actually try it some day when it can load

[dexrow]

However, I would like to remind you that the first and second versions of DReverb are incompatible, so you must decide which version you want to use, since in some DAWs you will not be able to use both versions at the same time.
This also means that if you used the old version of DReverb in your projects, then installing the new version, it incorrectly counts the saved preset parameters, which will spoil the sound. Therefore, be careful when updating the DReverb version.

If it is not compatable it should have a new name. I jeskola Buzz though you would be able to use both versions if everything is working the same and you had them seperate (at least that is the impression I am under). The thing about making up rules is that people game them to make it exclusive or whatever.

[plexuss]

I previous posted that the AU for DReverb2 opens without a custom GUI in Reaper. I was mistaken: That was DReverb (version 1) that opened without the custom GUI. DReverb2 works fine and it works with DReverb also installed.

[kontakt]

I installed version 2.0.9 windows vst3 but modulation doesn't seem to work. (It seems to work while dragging the knob)

[vasyan]

- first / second versions are incompatible
but you said that it was backwards compatible?

Yes, I wrote this, and if you read it carefully, then you can load the banks and presets from the first version.

However, it is backward compatible with the first version - you can load presets and banks into it that were made in the first version.

It doesn't say anything about loading projects from the first version.

However, at this point in time, I believe that there is a need to load projects from the old version, so in the next update I will add this function to the plugin.

[vasyan]

Doesn't scan for me in the most recent version of Reaper 64-bit on Windows 11. I end up with two folders in my plugin listing, one for Stone Voices and one for StoneVoices, but only dReverb 1.0 actually shows (and it shows only in the "Stone Voices" labeling, not "StoneVoices"). So this is a bit of a phantom for me at this time. That does mean that I can imagine it to sound impossibly good, though. Like angels singing, in my imagination, I can't wait to actually try it some day when it can load

Yes, I made a little mistake here - the reason for that was a very stressful job, where I accidentally confused the PLUG_MFR parameters with BUNDLE_MFR. This mistake will be fixed in the next update.