Hybrid Reverb (standard) crashes Cubase and Nuendo

[dterry]

I recently demoed, and purchase Vienna Suite (standard), and found that any latency setting other than whatever Hybrid Reverb sets as its default (512 when I demoed it), would crash Cubase 9.5 when opening the project. 

A.  I purchased Vienna Suite thinking the solution/workaround was to simply leave the latency set to 512.  However, the day after purchasing, every project where I had used Hybrid Reverb the day before, with the latency set to 512, would crash.  When I load Hybrid Reverb in a new project, the latency now defaults to 128, and that is the only latency that will work without crashing Cubase 9.5

B.  I then tried Hybrid Reverb in a new Nuendo 7 project, and it would instantiate and save without a problem.  However, when trying to reopen that project it would crash, regardless of the latency setting it was saved with. 

The crashes always happen when Cubase/Nuendo begin loading the first channel on which Hybrid Reverb was inserted.  Cubase/Nuendo will issue a Windows' "not responding" error, and immediatly quit.  I can remove Hybrid Reverb from the VST3 folder, and the same projects open fine.

C.  I also have the demo for Vienna Suite Pro (about to run out), and Hybrid Reverb Pro works fine at any latency setting. Unfortunately I can't upgrade to Pro just to solve this problem.  

I have reported this to Support and they had no answers at first - I am waiting for a respone on a couple of updates to the problem (outlined here already).   It is clearly a problem only with latency settings in the standard version of Hybrid Reverb.  Other suite plugins seem fine, but I bought the suite for Hybrid Reverb specifically.

Any other Cubase/Nuendo users run into this?  Any ideas?

[Dietz]

Hi Dterry,

what kind of audio hardware are you using? What's the ASIO system latency set to? And what are your ASIO Guard settings in Cubase/Nuendo? 

... I can't test in Nuendo 7 or Cubase 9.5 myself, but I'm sure VSL support staff will get back to you ASAP. Thanks for your patience!

[dterry]

Hi Dietz,

Audio interface:  MOTU 2408 Mk2 (two I/O 2408s connected to the PCIe card)
ASIO buffer is set to 256.  

ASIO Guard is on for everything except VEPro (known issue - lag caused when selecting tracks when AG is enabled for VEPro instances).  

Hmm - I will test now with ASIO Guard off for Hybrid Reverb, and off for the project and post back later.

[Dietz]

Seeing that you're using MOTU hardware makes me assume that you're running your DAW under OS-X, don't you?

[dterry]

Windows 8.1.  This is an i7 PC, 64G Ram, SSDs, etc.  

Hybrid Reverb will crash even a basic blank project with nothing but one FX bus with one instance of Hybrid Reverb.  Once Cubase is closed, that project will crash as long as Hybrid Reverb is availble to load (I have to remove it from the VST3 folder to open those projects). 

Yesterday only a latency of 128 seemed to work, but today it is back to 512, or so it seems. There may be some sequence of "default" vs. saved presets vs. saving a project with unsaved Hybrid Rev settings that contributes to when 512 works or doesn't.  But regardless, it will crash at any other setting, and often with 512 as well. 

Pro works fine, so something was changed in the Pro version vs. the standard version that fixes this.

I have a crash dump from one of my tests just now with Cubase 9.5 that I will send to Steinberg, but it will likely be a couple of weeks before they are back from the holidays to check it.  

[Dietz]

I can confirm your findings to some extent. A quick test under Windows 7 and Nuendo 6.5 makes me run into similar (and severe) issues as you do.

This is quite obviously a bug of Hybrid Reverb. Sorry for the inconvenience - I'll try to make sure that this gets fixed ASAP.

Kind regards,

[dterry]

Thank you Dietz!  I appreciate the help and quick confirmation.  I will check back in from time to time to see if a fix is posted to updates. 

[Dietz]

PS: VST2 version seems to be unaffected - this could be a temporary workaround.

[dterry]

You are right - thank you. 

The first times I tried the VST2 version a couple of days ago, I got an eLicenser error (not licensed to run), though the license was clearly active.  I thought it was the demo license running out of starts and after going through some hassles with elc trying to refresh the license, I never tried the VST2 version again. 

I had the same elc error when I first loaded the vst2 version just now, but after saving the project, closing Cubase and reopening, it is loading without crashing (and without the elc error, for now at least). 

I will test the VST2 version a bit more, but it does seem to be unaffected here as well. 

[Dietz]

Please make sure that all the software (including the so-called "license database") and drivers for the eLicenser(s) are up-to-date. This is crucial, really.

Kind regards,

[dterry]

Absolutely.  I had been getting frequent timeouts ("operation failed") errors when trying to refresh the number of starts for the Vienna Suite/Pro demo license and as a part of troubleshooting that, updated eLicenser and ran maintenance, etc (VEPro must be closed when using eLicenser, which takes time to reload with large templates). 

[TFIS]

Same problem here

Is there a fix now?

[TFIS]

@TFIS said:

Same problem here

Is there a fix now?

 

Self quoting sucks, but:

It seems that issue depends on odd soundcard latency settings.

I ran mine on 196 samples when the crash occurs, set it to 256 worked.

[MS]

@TFIS said:

It seems that issue depends on odd soundcard latency settings.

I ran mine on 196 samples when the crash occurs, set it to 256 worked.

 

Thanks,

I have found and fixed the issue, and an update will be released soon. I can recommend you not to use oddly sized (non powers-of-two) buffers though - it will impact performance of most plugins negatively.