KVR Audio

bob swans · Post by **bob swans** » Sat May 02, 2020 5:45 pm

Are Wavesfactory having a sale this year or did I miss one? Finally got around to trying the demo of this and I'm very interested.

Edit: I missed the sale

enCiphered · Post by **enCiphered** » Mon May 04, 2020 12:35 pm

neverbeeninariot wrote: Sat May 02, 2020 2:56 pm Sorry to report that the Tube algo glitch is still there in 1.5.2 (Reaper 6.09, Bitwig 3.0.3)

Edit: VST3 version in both DAWS, I'm on a fresh Win10 install, 64 bits.

It does not happen if the gain is at zero when switching algos.

Starting playback causes the glitch in Reaper, but not in Bitwig.

Cheers
NBIAR

Tested in latest Wavelab, Cubase and Live 10.
Clicks are still there,

plexuss · Post by **plexuss** » Mon May 04, 2020 10:35 pm

enCiphered wrote: Mon May 04, 2020 12:35 pm Tested in latest Wavelab, Cubase and Live 10.
Clicks are still there,

Tested 1.5.2 in Reaper 6 under macOS - I get clicks when switching to/from Tube. Back to the drawing board. Is this really that hard to troubleshoot in the code?

monophonK · Post by **monophonK** » Tue May 12, 2020 9:03 am

Jesús any update about the problem with the "clicks"?

wavesfactory · Post by **wavesfactory** » Tue May 12, 2020 9:19 am

monophonK wrote: Tue May 12, 2020 9:03 am Jesús any update about the problem with the "clicks"?

Yes, fixed!

Spectre 1.5.3 is out now.
Fixes clicks with tube saturation in Reaper.

You can download here: www.wavesfactory.com/spectre
Or in the plug-in using the built-in auto-updater.

enCiphered · Post by **enCiphered** » Tue May 12, 2020 12:01 pm

You fixed it only for Reaper?

wavesfactory · Post by **wavesfactory** » Tue May 12, 2020 12:40 pm

enCiphered wrote: Tue May 12, 2020 12:01 pm You fixed it only for Reaper?

You shouldn't get any clicks in any DAW now.

enCiphered · Post by **enCiphered** » Tue May 12, 2020 12:48 pm

Well, I just installed and tested 1.5.3 in one of my mastering projects in Wavelab as well as in Cubase. Nothing changed for me, the clicks are still there.

I´m on Windows 10 if that helps

wavesfactory · Post by **wavesfactory** » Tue May 12, 2020 1:12 pm

enCiphered wrote: Tue May 12, 2020 12:48 pm Well, I just installed and tested 1.5.3 in one of my mastering projects in Wavelab as well as in Cubase. Nothing changed for me, the clicks are still there.

I´m on Windows 10 if that helps

I just tried in Cubase and I get no clicks.
Can you please click on the Wavesfactory logo in Spectre and confirm that you're using version 1.5.3?

enCiphered · Post by **enCiphered** » Tue May 12, 2020 1:28 pm

Weird. I installed 1.5.3 twice and it still shows 1.5.2 in my project.
I then removed it completely from my pc and re-installed the 1.5.3 but again, it shows 1.5.2 when I open it in WL or Cubase.
I´m using only the VST3 version but there was no option to choose the VST3 path in the installer. Might this be the problem?

wavesfactory · Post by **wavesfactory** » Tue May 12, 2020 3:12 pm

enCiphered wrote: Tue May 12, 2020 1:28 pm Weird. I installed 1.5.3 twice and it still shows 1.5.2 in my project.
I then removed it completely from my pc and re-installed the 1.5.3 but again, it shows 1.5.2 when I open it in WL or Cubase.
I´m using only the VST3 version but there was no option to choose the VST3 path in the installer. Might this be the problem?

You should reboot your computer and re-scan the plug-in. Then it will work

neverbeeninariot · Post by **neverbeeninariot** » Tue May 12, 2020 3:56 pm

wavesfactory wrote: Tue May 12, 2020 3:12 pm
enCiphered wrote: Tue May 12, 2020 1:28 pm Weird. I installed 1.5.3 twice and it still shows 1.5.2 in my project.
I then removed it completely from my pc and re-installed the 1.5.3 but again, it shows 1.5.2 when I open it in WL or Cubase.
I´m using only the VST3 version but there was no option to choose the VST3 path in the installer. Might this be the problem?
You should reboot your computer and re-scan the plug-in. Then it will work

Even more weird - I uninstalled the old version, made sure the VST3 was gone from the plugin folder, rebooted, installed the new version, rescanned, it is still showing v1.5.2 and prompting to upgrade. Windows 10, 64 bit, VST3 - Reaper.

I tried the version that the plugin downloaded, and a fresh download via the WF site.

neverbeeninariot · Post by **neverbeeninariot** » Tue May 12, 2020 6:05 pm

Just following on from my last post, I tried again.

I uninstalled using Uninstall Tool, cleared out the registry, rebooted, installed 1.5.3, rebooted. Rescanned in Reaper (well, it does this when it starts up anyway, but I did it twice). Program version is still showing as 1.5.2 and that there is an update to download.

The good news is that, despite the version number being reported incorrectly, the clicks are not happening in Reaper or Bitwig any more. Nice.

enCiphered · Post by **enCiphered** » Wed May 13, 2020 6:31 am

Rebooting and re-scanning didn´t change anything for me, unfortunately. I always see 1.5.2 in my projects and click are there too.

wavesfactory · Post by **wavesfactory** » Thu May 14, 2020 4:37 pm

Hi everyone and apologies for the version number confusion in Windows. We double checked and the version number wasn't correctly updated in the latest update.
A new installer has been uploaded and you can update right now: www.wavesfactory.com/spectre

Wavesfactory Spectre - Multi-band Enhancer