Wavesfactory Spectre - Multi-band Enhancer

[enCiphered]

Confirming that everything is working fine now over here. Thanks for the fix, really appreciate it.

[Hez]

Anybody else having intermittent issues with NaN errors when trying to change gain, frequency or bandwidth by dragging the text below the EQ graph? It never happens when I drag the nodes on the graph itself, only the text parameters underneath the graph. It also seems more likely to occur if I've closed and reopened the plugin GUI - I don't think I've ever seen it happen when opening a fresh instance.

Tested with the latest version of Spectre (1.5.3) and the latest version of Bitwig (3.2 beta 5), though this issue has been present in Bitwig for a while.

To reproduce, load Spectre on any track, dial in some settings on the high shelf, close the GUI, reopen the GUI, tweak the high shelf gain/resonance/frequency (using the text parameters, not the graph). If the error doesn't occur, repeat the closing/reopening/tweaking steps until it does occur. Seems to happen more often if the changes are made during playback and with audio going through the plugin, but not sure if that's critical.

Sometimes when the NaN glitch happens Spectre will also stop passing audio (often with a bit of a click/blowup as it happens), but sometimes it won't.

[wavesfactory]

Anybody else having intermittent issues with NaN errors when trying to change gain, frequency or bandwidth by dragging the text below the EQ graph? It never happens when I drag the nodes on the graph itself, only the text parameters underneath the graph. It also seems more likely to occur if I've closed and reopened the plugin GUI - I don't think I've ever seen it happen when opening a fresh instance.

Tested with the latest version of Spectre (1.5.3) and the latest version of Bitwig (3.2 beta 5), though this issue has been present in Bitwig for a while.

To reproduce, load Spectre on any track, dial in some settings on the high shelf, close the GUI, reopen the GUI, tweak the high shelf gain/resonance/frequency (using the text parameters, not the graph). If the error doesn't occur, repeat the closing/reopening/tweaking steps until it does occur. Seems to happen more often if the changes are made during playback and with audio going through the plugin, but not sure if that's critical.

Sometimes when the NaN glitch happens Spectre will also stop passing audio (often with a bit of a click/blowup as it happens), but sometimes it won't.

We've been chasing this bug for some time now. We haven't been able to reproduce it though.

[wavesfactory]

Hi guys,

Spectre has been updated to version 1.5.4:

- Fixed: crash when reloading a project in Ableton Live.
- Fixed: saturation and processing modes correctly recalled in FL Studio / VST3.
- Improved: general optimisation.

As always, the update is free.
You can download the installers in the website or in the plug-in itself with the auto-updater functionality.

[Ploki]

Anybody else having intermittent issues with NaN errors when trying to change gain, frequency or bandwidth by dragging the text below the EQ graph? It never happens when I drag the nodes on the graph itself, only the text parameters underneath the graph. It also seems more likely to occur if I've closed and reopened the plugin GUI - I don't think I've ever seen it happen when opening a fresh instance.

Tested with the latest version of Spectre (1.5.3) and the latest version of Bitwig (3.2 beta 5), though this issue has been present in Bitwig for a while.

To reproduce, load Spectre on any track, dial in some settings on the high shelf, close the GUI, reopen the GUI, tweak the high shelf gain/resonance/frequency (using the text parameters, not the graph). If the error doesn't occur, repeat the closing/reopening/tweaking steps until it does occur. Seems to happen more often if the changes are made during playback and with audio going through the plugin, but not sure if that's critical.

Sometimes when the NaN glitch happens Spectre will also stop passing audio (often with a bit of a click/blowup as it happens), but sometimes it won't.

which DAW is that

[foosnark]

I've seen the NaN thing in Bitwig a couple of times, but I couldn't tell you what I was doing with it at the time.

[dermage]

I've had this NaN error once too in Ableton Live 10.1 on Win10, good to know it wasn't just me.

[EnderWillSaveUs]

I noticed you now have an effects bundle, is there any upgrades to it from owning other plugins from you? I own trackspacer and cassette...

[audiot]

Hi guys,

Spectre has been updated to version 1.5.4:

- Fixed: crash when reloading a project in Ableton Live.
- Fixed: saturation and processing modes correctly recalled in FL Studio / VST3.
- Improved: general optimisation.

As always, the update is free.
You can download the installers in the website or in the plug-in itself with the auto-updater functionality.

Spectre is working fine in my environment, but thanks for the update! It's my go-to enhancer ... this thing is magic and the price is more than fair! Thank you

[Jet Set]

Using this in a project again this week - it remains awesome.

[wavesfactory]

Anybody else having intermittent issues with NaN errors when trying to change gain, frequency or bandwidth by dragging the text below the EQ graph? It never happens when I drag the nodes on the graph itself, only the text parameters underneath the graph. It also seems more likely to occur if I've closed and reopened the plugin GUI - I don't think I've ever seen it happen when opening a fresh instance.

Tested with the latest version of Spectre (1.5.3) and the latest version of Bitwig (3.2 beta 5), though this issue has been present in Bitwig for a while.

To reproduce, load Spectre on any track, dial in some settings on the high shelf, close the GUI, reopen the GUI, tweak the high shelf gain/resonance/frequency (using the text parameters, not the graph). If the error doesn't occur, repeat the closing/reopening/tweaking steps until it does occur. Seems to happen more often if the changes are made during playback and with audio going through the plugin, but not sure if that's critical.

Sometimes when the NaN glitch happens Spectre will also stop passing audio (often with a bit of a click/blowup as it happens), but sometimes it won't.

Bug fixed. Please, email me so I can send you the beta.

[Hez]

Bug fixed. Please, email me so I can send you the beta.

Just had a little test and it looks good to me so far. Thanks so much for tracking this one down - seems like it was a real tough bug to solve.

I really appreciate the level of communication & support in general from you guys - definitely one of the most open and responsive devs I've had the pleasure of dealing with

[wavesfactory]

Hi guys,

Spectre has been updated to version 1.5.5:

- Fixed: NaN bug.
- Added: dark mode. A user in another thread pointed out that the UI made his migraine worse specially during night sessions, so this new mode gets rid of the white bars and it's easier on the eyes.



As always, the update is free.
You can download the installers in the website or in the plug-in itself with the auto-updater functionality.

[dermage]

Looks GREAT.
thanks for fixing the NaN bug, will be installing promptly

[Ploki]

Hi guys,

Spectre has been updated to version 1.5.5:

- Fixed: NaN bug.
- Added: dark mode. A user in another thread pointed out that the UI made his migraine worse specially during night sessions, so this new mode gets rid of the white bars and it's easier on the eyes.



As always, the update is free.
You can download the installers in the website or in the plug-in itself with the auto-updater functionality.

could you elaborate on the NaN bug?
i think this is exactly what i've been getting with Cassette, Pulsar Mu and Unisum in Logic.

also, absolute love on the dark mode.