Daniel Wenger

valhalla-vintage-verb-problems

You could try to remove the plugin name from the vst~ object, and

send message plug ValhallaVintageVerb_x64.vst at some point

You could try to remove the plugin name from the vst~ object, and
send message plug ValhallaVintageVerb_x64.vst at some point
with loadbang/delay .


I remember having similar issues with a Lexicon.vst plugin some time ago, cut and paste always fixed it. I think I loadbanged it in the end and although there was a "not found" error message it still loaded the plugin.

I remember trying to fix the problem but in the end I just accepted it.

I remember having similar issues with a Lexicon.vst plugin some time ago, cut and paste always fixed it. I think I loadbanged it in the end and although there was a "not found" error message it still loaded the plugin.
I remember trying to fix the problem but in the end I just accepted it.


Indeed, Source Audio's solution works. If I remove the plugin name from the vst~ and loadbang a message plug ValhallaVintageVerb_x64.vst, the vst~ works when the patch is loaded.

Also, as Dominikk predicts, the patch loads with an error message: ValhallaVintageVerb.vst:no format VST exists. But also as Dominikk predicts, the vst~ works despite the error message.

I am not thrilled with any vst~ that produces errors on load, but the patch works, and I appreciate the accurate insights.

I wanted a CPU-friendly reverb. The choice was between one of the Valhalla and 2C's Breeze. I have chosen the Breeze because it has a broader scope. It sounds really great and it functions quite well inside Max 7 on my old 2007 MBP. I have one regret only: you cannot switch between presets using MIDI messages. But that's really a tiny drawback...

--