I just purchased H-Reverb from Waves. Gig found and listed the plugin(s) in the plugin manager. However when I attempted to add the plugin to a rack, Gig crashed. This occurred regardless of which variation I used (there are several). I did start out attempting to open the Stereo VST and VST3…crash, and so on. I was able to recreate this behaviour several times. I then opened and hooked up Waves F6 EQ without any problem.
Just wondering if anyone else has experienced this and if they were able to find a workaround.
I am using the latest version of Gig Performer in Windows 10 version 1809, build 17763.529. Audio interface is Focusrite Scarlet 18i8 v2 with latest drivers.
Am using V10 plugins. Installed the plugin outside of Gig Performer. Opened H-Reverb in an existing Gig. Created a new Gig. Opened H-Reverb and it crashed Gig Performer.
Hi there and welcome to our forums. Your Waves plugin seems to be crashing.
I can see that you sent us a report - THANKS so we could figure out that this is what was happening.
Here is the message:
> Unhandled exception at 0x00007FF95EC29EF0 (WavesLib1_10.0_Win64.dll) in crashdump.dmp: 0xC0000005: Access violation reading location 0x0000000000000018.
Maybe this could help them if you contact Waves and give them this message, explain what happened.
Yes, same result here with any of the H-Reverb plugins. My workaround is to put the plugin inside Blue Cat PatchWork, which I use a lot of anyway.
For some reason, wrapping H-Reverb inside another plugin allow it to work, but it crashes by itself.
Thanks @gfd although - we do have Canadians on the team as well
It seems that there’s something wrong with the plugin.
If you are on windows - try VST2 and VST3 versions if they provide those. On a mac - try AU version as well. Sometimes a different edition of the plugin works slightly differently.
Maybe I’m losing my mind, but I was able to open the VST3 versions without a crash today. Opened quickly, all good. I could have sworn Gig crashed when I opened a VST3 yesterday. But neither Gig, Windows, nor H-Reverb have changed; so it has to be my error.
Gig Performer is once again crashing, even when I open an H-Reverb VST3. Perhaps I could get the latest crash info so that I can contact Waves. Thanks again,
Waves should have a Gig Performer license and with detailed instructions from @gfd they should be able to reproduce the problem you’re having. Once they reproduce it - they should be able to fix it.
We have a good relationship with them and should they need any help they can contact us any time.
Please note that Gig Performer 3 is not officially supported with Waves latest software version. This does not necessarily mean that it won’t work, just that our software was not designed for it nor tested and qualified to run with it.
Due to this fact, we do not have a knowledge-base of possible issues. It might work fine, but if it doesn’t we will not be able to assist.
I got a little lazy and it fell on you. Thank you. Perhaps you could let us know of the result of your second session with Waves.
Should I contact Waves support now or wait until you get a second response?
I find the first response from Waves to be rather curious. Why would Waves not want to ensure their plugins work on as many platforms as possible. Furthermore, they have the information required to do the fix. Perhaps a fix would involve digging too deep into the software. Or maybe they’ll just fix it quietly
There are wrappers. Blue Cat’s has Patchwork and I see that MetaPlugin by DDMF is an alternative. Don’t know how well or if they work, but I read that Blue Cat’s is well regarded. But that begs the question "why am I buying plugins, plugin hosts; and wrappers to make plugins work in the host?
While we wait … @pianopaul managed to capture the crash report clearly indicating how and where it crashed within the Waves H-Reverb plugin. Here’s part of that report
