WaveRazor 2.0.5 + Cubase 9.5.4 = hangs?

Question

Been having issues with WaveRazor 2.0.5 installing VST2 and VST3 and getting them to work in Cubase 9.5.4

Recently installed the trial on another machine (Win10 x64) using Reason 10 as my DAW. Reason explictily uses VST2 only and I found that an earlier version would work fine (V2.0.2). I've just offline unlocked v2.0.2 (older than 30 days demo) with no issues at all, sound working fine.

I'll redownload v2.0.2 but ideally would prefer VST3 on my main system with Cubase, as I'd prefer rescalable view (using a 48in 4KTV so a larger view would be beneficial)

v2.0.5 was installed twice on Cubase system, tried with VST3 only (synth and FX version), but only FX version shows up (under OTHER category when searching), synth cannot be found. Trying to put VST3 WRFX onto a channel results in Cubase hanging indefinitely (non responsive, had to force quit).

Will try v2.0.2 on Cubase 9.5.4 (after fully removing v2.0.5 which when uninstalling seems to clean up well, are all files removed ie user prefs / common files when uninstall is invoked? registry strings cleaned or not used?), if that works will up to v2.0.3 and test again to be sure.

Answer 1

@fresha : Following up on this, with v2.0.9, updates should be super fast and a clean install (with no db) should be faster than before.

Answer 2

Uninstall on Windows:   I haven't tested that in a while to be sure, but it should be removing everything.   The only registry entries are those put in by the Windows installation system, as we don't need the registry itself, and those should also be removed by the uninstall process.

On v2.0.5, did you try installing 'without' the FX version and see what happens?

Comments

Will try later today, I have v2.0.3 as well so I can do a stage by stage install and checklist what happens

---

That would be great, thank you!   Will stay tuned and look forward to hear how that goes.

---

ok something weird.... installing 2.0.5 Waverazor 64 bit VST3 actually installs 2.0.5 WR VST3 32BIT version - I just watched the installer drop the 32 bit VST3 WR into the (x86) Common files folder...even though I only had 64bit selected. Seems like the wrong config in the installer somehow.

v2.0.2 installed no problem at all, works in Cubase and Reason (VST2 Reason, VST3 in Cubase 64bit for both synth and fx)

v2.0.3 seems to install VST3 synth in the right place. Also installs VST2 2.0.3 in the 64 bit folder I choose. So that seems ok. However, VST2 2.0.3 versions hang Cubase when on splash loading screen (popup or blacklist the plugin.. no popup so...). 2.0.3 VST3 synth allowed to pass through, but 2.0.3 hangs Cubase when trying to initiate.

TL,DR; 2.0.3 and 2.0.5 not working well with Cubase 9.5.40. 2.0.2 works fine, but can't scale plugin

---

Egad...  doh!  You are correct, I made a mistake in the new installer.   The installation locations are correct, but the VST3 selections are reversed... fixing that now.

Regarding the hang, I have no idea.   I haven't tried Cubase on Windows yet, so will give that a go.

Answer 3

I got Cubase 9.5.4 setup on Windows...   I have been doing all kinds of things to see if I can create a problem (re-installing, rescanning, messing up the database, moving patches, and generally giving it tough startup conditions), and Waverazor just keeps working fine on my system.    Frustrating that I cannot reproduce this issue.

Another thing to try would be to just install the Waverazor plugins (without FX) and remove (or temporarily rename) the folder containing the patch database and settings and see if a rescan in Cubase will be happy with that. 

1. Uninstall Waverazor (C:\Program Files\MOK\Waverazor\uninst)

2. Rename C:\Users\<user-name>\AppData\Roaming\mok   to   C:\Users\<user-name>\AppData\Roaming\mok_temp

3. Install VST/VST3 of Waverazor

4. Run Cubase (and possibly rescan if needed)

Answer 4

Ok some more good progress....

Gutted out v2.0.2 and cleared the C:\Users\<user-name>\AppData\Roaming\mok folder (changed to mok_temp), and total uninstall (which did purge the system correctly, nothing anywhere)

Installed v2.0.3 as VST2 64bit, ensuring only the synth was installed. Opening Cubase and on the splash screen I had the 'error' message that Waverazor was 'processing or hanging' again.... but, and here's where I found that patience helped out.... I had the folder open where the WaveRazor_PatchdB files were being installed open (after the install the folder had the waverazor.log file and the patch folder empty as expected. When Cubase had the message I looked in the patch folder and could see that the patch dB was 'building' for a couple of minutes, then once finished Cubase continued on (without any blacklist message, Cubase closed it in response to the WR dB being built). Cubase - New Project - Added Waverazor VST2 synth, no problems, GUI opened straight away.

Uninstalled v2.0.3 VST2, and installed only v2.0.3 VST3, as there's no warning popup at the start of Cubase splash for VST3. Cubase opened no problem, and had WR VST3 listed. Added it to a new track and Cubase 'hanged' again... but.... I waited and with the patch dB folder again I could see the patches build into the dB file, so after that completed, Waverazor appeared. 

Seems that the hanging relates to the patch dB building, but a popup would be nice approach inidicating that 'first time use patch database building' progress bar or message would help the user realise what is happening. If the user quits out half way, the patch database become 'corrupt' as only half built, but WaveRazor may think it's complete but can't launch because it's not (causing my previous hanging issues).

Found something else too regarding rescaling but will post another bug report for that

 

Comments

I'll check with FX being installed after WR PatchDB first build now, to see if the FX loads up straight away. Will check v2.0.3 with Reason too since it has had first patch dB build already done. I did have issues with v2.0.3 but if Cubase half-patch-dB problem then likely that was what was causing Reason to hang as well as Cubase

---

v2.0.3 works fine in Reason, had the same initial 'lag' on first creation, think the database may have rebuilt and 'killed' v2.0.2 patchdB? not sure though just guessing here as didn't examine the folder while installing / initialisation of the plugin in Reason

Answer 5

Was rethinking on the installer side of things.... not prying but was wondering why the database would only build when the plugin is first 'created' within a DAW, and not have the patch-database be prebuilt and installed during the installer process? That should knock the lag out totally, unless there's some other reason for it I'm not aware of?

Sounds pretty slick though, diving right into the innards of this beastie too. Definitely a tasty way to create waveforms for wavetable synths that's for sure :D

Comments

I think the Patch DB could probably be installed, and you are correct that it would knock of that startup time for the first run.   Initially when I was building this, it wasn't clear if the static installed db would have the correct state for each platform/system/user...  and I also wanted to make sure we could recover if the user ever deleted everything, we would just recreate it... and if the db becomes corrupted I can recover and repopulate it with all existing patch files...

That being said, I could probably install a template db that would speed things up...