Anwida is back with a free 64 bit reverb, both pc and mac

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
RELATED
PRODUCTS
DX Reverb Light

Post

Hello! Yes, we are back. I am sorry for the problems you might have encountered. This is a brand new plug-in, therefore we apologize if some problems might still be present, that uses the original DX Reverb Light algorithm (actually with some little improvements). By the way...no DX to VST wrapper was used (it would have no sense).
I tested personally (and I repeated the test today) the 64 bit plug-in in windows 10 and 7 with both Reaper (latest version) and FL 12. From our side everything is working fine. Did you add the right VST folder to your host?
The plug-in is installed by default in the C:\Program Files\Steinberg\vstplugins folder. This path must be set in the host preferences (in Reaper choose option -> preferences -> plug-ins -> VST then Add button).
For the ones that were asking, yes, all our plugins will be updated (Spazio included).

Best Regards
Massimiliano Tonelli

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.
By the way.. I was forgetting. For the Windows version, since it was mentioned in the discussion, any other installation folder (this can be specified during the setup) different from "C:\Program Files\Steinberg\vstplugins" should work (i.e. I tested c:\vst and c:\vstplugins).
Reaper should be restarted after the preferences have been saved. We will be very happy to help anyone interested, please send us feedback at http://www.anwida.com/contact.asp?ct=2 (http://www.anwida.com/contact.asp?ct=2)

Thank you again
Massimiliano

Post

[DELETED]

Post

ANWIDA wrote: Did you add the right VST folder to your host?
Yes of course. As I said:
Teksonik wrote: I just let it install in it's default location and let it create the Steinberg/VstPlugins folder. I then pointed both Reaper and FL Studio to that location and did a re-scan.
But the point is that I originally installed it in my VST 64 folder which Reaper was already pointed to and all the other plugins in that folder do show in Reaper but it still can't see the Anwida Reverb. For the record I have hundreds of plugins installed across four different computers and four different Hosts. I am familiar with the process of installing new plugins. :wink:
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

Teksonik wrote:
ANWIDA wrote: Did you add the right VST folder to your host?
Yes of course. As I said:
Teksonik wrote: I just let it install in it's default location and let it create the Steinberg/VstPlugins folder. I then pointed both Reaper and FL Studio to that location and did a re-scan.
But the point is that I originally installed it in my VST 64 folder which Reaper was already pointed to and all the other plugins in that folder do show in Reaper but it still can't see the Anwida Reverb. For the record I have hundreds of plugins installed across four different computers and four different Hosts. I am familiar with the process of installing new plugins. :wink:
As I said before; life is just too short. I think you are wasting your time here Teksonik.

@ANWIDA Rule number one of root cause analysis: fully understand the problem, before trying to find the root cause :dog:
Why won't you delete this account as I have requested Ben ?

Post

Sounds like it's just typical tech support protocol. Is your computer plugged in Sir ? Is the Power On ? etc..... :)

Let's give Anwida another chance. Seems like he's at least trying to catch up with current technology. Time will tell I suppose...... :shrug:
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

Did you try to delete it from Reaper's (64bit). VST .ini and then rescanI woulg guess that this would do the trick...

Post

jens wrote:Did you try to delete it from Reaper's (64bit). VST .ini and then rescanI woulg guess that this would do the trick...
I did a "Clear Cache/Re-Scan" twice. The point is that I shouldn't have to do any such acrobatics. I don't remember Reaper ever failing to see a plugin before. That includes hundreds of plugins on my Studio computer most installed in the same custom folder although it is running Win 7 not Win 10 as this system does. I'm using Reaper 4.78 and the developer is testing in what I assume is the latest version 5 so perhaps that is a clue.

Speaking of clues I'm not the only one who has reported the issue........
RockinMillie wrote:The 64 bit version is neither showing up in Studio One 3.2.3 x64 nor in Sonar X2 x64 here.
Removed from my hard drive.
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post

I used to have a few Anwida plugins back in the stone age and they were OK at that time...

But after checking out the "new" reverb,all I can say is that Anwida have a lot of catching up to do,because there has been a considerable amount of development since they coded their plugins...

I uninstalled the "new" reverb after a few short moments because I have many other better options...

Sorry...but no cigar this time around :party:
No auto tune...

Post

I still have an account there. Yippie. Downloaded my GEQ Plug-in and DX Reverb Light.
Anyone who can make you believe absurdities can make you commit atrocities.

Post

Teksonik wrote:
jens wrote:Did you try to delete it from Reaper's (64bit). VST .ini and then rescanI woulg guess that this would do the trick...
I did a "Clear Cache/Re-Scan" twice. The point is that I shouldn't have to do any such acrobatics. I don't remember Reaper ever failing to see a plugin before.

*ouch* - a full rescan? Not the right method at all in this case...

It happens regularly to me... Reaper might fail to successfully load a new plugin during the scan for this or that reason and then Reaper immediately blacklists it i.e. it gets an entry in the .ini that says to ignore it - which is why I suggested to delete this entry.
If you then manually rescan (or close and re-start Reaper) Reaper will again recognize it as a new plugin and re-try to load it

You find the .ini-files by chosing "Show action list..." from the "Actions"-menu, typing "path" in the "Filter"-field, selecting "Show REAPER resource path in Explorer" and then hitting "Run" - this opens the folder in which all the .ini-files are stored. YFor 64bit VSTs you need to open reaper-vstplugins64.ini and either search the file for the plugin in question or look for it towards the bottom of the list. If it is the latest plugin which Reaper has scanned, it will beright at the bottom. Simply delete the whole line and close and save the .ini.

To rescan open any FX-window, choose "Add FX..." from the "FX"-menu and then hit F5 (or select "Scan for new plugins" in the "FX"-menu of the plugin-window.

Post

WIN 7 x64. Installed without a hitch in MY plugins folder and loads fine in Reaper.

Haven't tried it out yet but I remember it was a pretty good reverb back in the day so I'm sure I'll find some uses for it.

Thanks Anwida :)

Post

TheoM wrote:I really don't see anyone paying 200 bucks for a single reverb plugin anymore, for example.
Depends on the market. Audio Ease Indoor just came out and it’s near $800. Adaptiverb from Zynaptiq is brand new and $150 right now — its price will increase to $250 at the end of September.
Sam Trenholme — Software developer, electronic musician — Listen to my music: http://caulixtla.com/music

Post

[DELETED]

Post

jens wrote:*ouch* - a full rescan? Not the right method at all in this case...
Oh stop. I've been using Reaper for years. You're not paying attention to what I've been saying. I know you're just trying to "help" but seriously I don't need your help. So please just stop. :wink:

Anyway Anwida just sent me a new .dll and I'll test it right now.......
None are so hopelessly enslaved as those who falsely believe they are free. Johann Wolfgang von Goethe

Post Reply

Return to “Effects”