Stone Voices - DReverb 2.0 (Free)

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
RELATED
PRODUCTS
DReverb DReverb Lite

Post

The latest DReverb2 update is available
version 2.1.0



What has been done:
  1. Added compatibility with the old version in terms of projects. Now you can upload projects to the DAW, where the old version of DReverb was used.
  2. Fixed the plugin category from "StoneVoices" to "Stone Voices".
Download on the official plugin page

Post

Thank You! :)

Post

My projects (old and new) no longer correctly recall DReverb's parameters. I've tried removing all references to DReverb from all of Reaper's INI files, I've tried replacing existing instances with completely new instances, but no luck. Every time I reload a project, I get some combination of parameters I didn't dial in. This is with DReverb 2.1.0.

Post

This is not working for me - the operation completes but the plug-in still fails due to unverified developer. I understand this may not be the exact syntax needed, does anyone have a suggestion for a different form that might work? Thanks.
kidslow wrote: Sun Jul 28, 2024 2:11 am 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

Post

tonycore wrote: Tue Jul 30, 2024 7:01 pm This is not working for me - the operation completes but the plug-in still fails due to unverified developer. I understand this may not be the exact syntax needed, does anyone have a suggestion for a different form that might work? Thanks.
kidslow wrote: Sun Jul 28, 2024 2:11 am 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
Guess I'm obligated follow this to the end ... The syntax seems to be ok but yeah that doesn't do it.

System Settings: Privacy & Security ... scroll to the bottom under Security, you can explicitly approve it "'DReverb2.component' was blocked from use because it is not from an identified developer" [Open Anyway] and authorize. You might be asked to authorize again by your DAW.

That's what it took to install the AU for me on an M1 Sonoma 14.4.1 ... it is Intel 64 not compiled for ARM. AU crashes Kv Element but does open in Reaper with a generic UI. The VST3 couldn't authorize at all but the VST opens and has a proper UI. VST2 thus appears to be the most stable.

There are a lot of minor inconsistencies similar to ones pointed out previously. "Stone Voices" vs "StoneVoices" and publisher strings in Pluginfo are ru.StoneVoices.audiounit.DReverb2 and ru.stone-voices.vst.DReverb2 ... those should be the same string.

But that's all surface level. Now that I have it installed, guess I'll have to listen to it. :D

Post

diroxe7660 wrote: Tue Jul 30, 2024 2:22 pm My projects (old and new) no longer correctly recall DReverb's parameters. I've tried removing all references to DReverb from all of Reaper's INI files, I've tried replacing existing instances with completely new instances, but no luck. Every time I reload a project, I get some combination of parameters I didn't dial in. This is with DReverb 2.1.0.
Some REAPER users wrote about inaccuracies in the work, namely, resetting the input filter parameters when resuming playback after a pause. However, this does not happen in many other DAWs. As it turned out, REAPER sends a reset command to the plugin when starting playback after a pause (does the VST protocol imply this?). No other inaccuracies were found in working with REAPER of the latest version 7.19. If you notice an inaccuracy in the work, then please describe it in as much detail as possible, under what circumstances it occurs, what other minor details may be, screenshots and videos attached to the bug report will be highly desirable.

Post

kidslow wrote: Wed Jul 31, 2024 2:59 am
Guess I'm obligated follow this to the end ... The syntax seems to be ok but yeah that doesn't do it.

System Settings: Privacy & Security ... scroll to the bottom under Security, you can explicitly approve it "'DReverb2.component' was blocked from use because it is not from an identified developer" [Open Anyway] and authorize. You might be asked to authorize again by your DAW.

That's what it took to install the AU for me on an M1 Sonoma 14.4.1 ... it is Intel 64 not compiled for ARM. AU crashes Kv Element but does open in Reaper with a generic UI. The VST3 couldn't authorize at all but the VST opens and has a proper UI. VST2 thus appears to be the most stable.

There are a lot of minor inconsistencies similar to ones pointed out previously. "Stone Voices" vs "StoneVoices" and publisher strings in Pluginfo are ru.StoneVoices.audiounit.DReverb2 and ru.stone-voices.vst.DReverb2 ... those should be the same string.

But that's all surface level. Now that I have it installed, guess I'll have to listen to it. :D
All these formalities and other bureaucracy initiated by Apple's policy does not give the green light to developers who are creative people.
Instead of being creative, you have to do the devil knows what, wasting precious time at the same time.
I'm not happy anymore that I started building plugins for macOS. I have a fairly old macintosh computer with Mac OS X El Capitan 10.11.16, which does not have the above problems.

Post

The latest DReverb2 update is available
version 2.1.1

Image

What has been done:
  1. Fixed an inaccuracy in the operation that resets the filter parameters when playing after a pause in some DAWs.
  2. Redesigned DReverb 2.1 logo.
Download on the official plugin page
Last edited by vasyan on Wed Jul 31, 2024 1:19 pm, edited 2 times in total.

Post

kidslow wrote: Wed Jul 31, 2024 2:59 am Guess I'm obligated follow this to the end ... The syntax seems to be ok but yeah that doesn't do it.

System Settings: Privacy & Security ... scroll to the bottom under Security, you can explicitly approve it "'DReverb2.component' was blocked from use because it is not from an identified developer" [Open Anyway] and authorize. You might be asked to authorize again by your DAW.
Ah of course, should have thought of that - do it all the time...thanks.

It worked in terms of DP seeing and validating, and wonderfully, the newest version (2.1) does not crash DP and I can now play with this new reverb. Thank you all.

EDIT: I wrote too soon. It crashes DP when I try to change sequences, so apparently there's an issue when it unloads or something.

Post

My AU version works fine and does not crash the DAW. MacOS X El Capitan 10.11.16, Logic Pro X 10.2.4

Image

Post

Thanks, I believe the latest update fixed my problem! Great reverb!

Post

kidslow wrote: Wed Jul 31, 2024 2:59 am
tonycore wrote: Tue Jul 30, 2024 7:01 pm This is not working for me - the operation completes but the plug-in still fails due to unverified developer. I understand this may not be the exact syntax needed, does anyone have a suggestion for a different form that might work? Thanks.
kidslow wrote: Sun Jul 28, 2024 2:11 am 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
Guess I'm obligated follow this to the end ... The syntax seems to be ok but yeah that doesn't do it.

System Settings: Privacy & Security ... scroll to the bottom under Security, you can explicitly approve it "'DReverb2.component' was blocked from use because it is not from an identified developer" [Open Anyway] and authorize. You might be asked to authorize again by your DAW.

That's what it took to install the AU for me on an M1 Sonoma 14.4.1 ... it is Intel 64 not compiled for ARM. AU crashes Kv Element but does open in Reaper with a generic UI. The VST3 couldn't authorize at all but the VST opens and has a proper UI. VST2 thus appears to be the most stable.

There are a lot of minor inconsistencies similar to ones pointed out previously. "Stone Voices" vs "StoneVoices" and publisher strings in Pluginfo are ru.StoneVoices.audiounit.DReverb2 and ru.stone-voices.vst.DReverb2 ... those should be the same string.

But that's all surface level. Now that I have it installed, guess I'll have to listen to it. :D
Try

Code: Select all

sudo xattr -rds com.apple.quarantine /Library/Audio/Plug-Ins/Components/DReverb2.component

Post

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.
vasyan wrote: Wed Jul 31, 2024 4:57 am The latest DReverb2 update is available
version 2.1.1

Image

What has been done:
  1. Fixed an inaccuracy in the operation that resets the filter parameters when playing after a pause in some DAWs.
  2. Redesigned DReverb 2.1 logo.
Download on the official plugin page (https://stone-voices.ru/vst/dreverb?lang=en)
Thank you very much Mr Vasyan!!
What a great service for a free plugin!
Great smooth sounding at all...

Post

onerob wrote: Wed Jul 31, 2024 2:18 pm Try

Code: Select all

sudo xattr -rds com.apple.quarantine /Library/Audio/Plug-Ins/Components/DReverb2.component
Not sure why I skipped that. It's my goto, but Yes, that works.

My recommendation would be to put them in ~/Library/Audio/Plug-Ins (user library) and then you can skip the sudo and privileged de-quarantine.

The VST3 of DReverb2 v2.1.1 does now show up in Reaper with a UI :tu: . I think I will stick with the VST2 is likely still most stable.

Thank you vasyan for making the effort and sharing your work freely. We all know that Apple doesn't make it easy for independent developers. You suffer doubly for your geography. I'm looking forward to taking some time and playing with it.

Post

kidslow wrote: Thu Aug 01, 2024 3:02 am Thank you vasyan for making the effort and sharing your work freely. We all know that Apple doesn't make it easy for independent developers. You suffer doubly for your geography. I'm looking forward to taking some time and playing with it.
This filth from Apple not only spoils the life of developers, but also of users. Although it didn't really hurt me personally, since I use an outdated version of macOS that doesn't have this hemorrhoid. :D

P.S. As for geography, I live far from megacities, in a remote village in Siberia, surrounded by taiga and Sayan mountains. I develop plug-ins and write music in the genre of ambient, noise and electropunk. :wink:

Image

Post Reply

Return to “Effects”