I use supervision as one of my main analyzer tool both in Cubase and Wavelab.
I now recoginzed since the installation of Wavelab 13.0.20 (used the Wavelab Sale) that supervision used in Wavelab does not load any setup - not my defined setups nor the factory-setups. In Cubase 15 pro everything is working fine.
Computer is Windows 11 25H2 64GB Ram
Any idea what am I doing wrong?
Thanks in advance for your assistance and hints
PG1 if he has any previously saved setup they will show below the Factory Presets as it does here.
This is correct
What Cubase version are you using?
Steinberg has tested it successfully with Cubase 15.0.30.
I am using Cubase 15.0.30 pro and here SuperVision is working correctly and loads all presets correctly.
I have Wavelab Pro 12 still installed on the same computer and here SuperVision is loading the presets correctly
Only Wavelab 13 has this issue (btw. I have two computers Win11 just with some different Ram and Disks and Wavelab 13 does on both not loading the SuperVision presets)
What Steinberg has tested is this:
If this doesn’t work for you, try to re-save the preset from Cubase.
Hello PG thanks for your assistance.
Unfortunately it didn’t solve the problem.
I setup a new set of preferences in Cubase 15.0.30 and copied them from
c:Users\…\Documents\VST3 Presets\Steinberg Media Technologies\SuperVision (this is the folder where Cubase (SuperVision) stores the user presets
to
c:\ProgramData\VST3 Presets\Steinberg Media Technologies\SuperVision (this is the folder where Wavelab stores the SuperVision presets.
When I now open SuperVision in Wavelab I can see on the dropdownlist of the presets for SuperVision all the created presets but when I load them nothing changes in the SuperVision Display. BTW this is also true for all the factory presets that are provided.
So it seems that Wavelab is accessing the correct preset-files but SuperVision is not changing the setting.
Hello PG
some more information.
I have now removed the following folder
C:\Users\…\AppData\Roaming\Steinberg\Wavelab Pro 13
assuming that a full new intialization for Wavelab takes place.
I also renamed the WaveLab Pro 12 folder to be sure that no setting from Wavelab 12 are loaded during the init-phase of Wavelab 13.
The inti-phase of Wavelab 13 took some time, because all the VST-Plugins are scanned.
Then when Wavelab13 opened I loaded SuperVision. I came up with the default Window. I selected one of the presets and it loaded and changed the window but any further loading of a differen preset failed.
Just to let you know
I think I see the problem now.
Once a preset has been loaded, another one cannot be loaded.
I have yet to identify if the problem is on the supervision side or on the WaveLab side.
The problem I described in my previous post has been fixed for 13.0.30.
The current workaround is to unload Supervision and reload it before loading a preset.
Hello PG
thanks for your reply and for providing a workaround. I’ll use that until the underlying problem is fixed
Removing Supervision, then loading Supervision, (in this case I inserted it in Playback Processing) then loading a preset that was configured for Wavelab in Cubase does not do anything other than the preset title on the top bar changes to the correct name.
Am I misunderstanding your workaround?
Normally this is the right procedure. but you must not have a default preset assigned to supervision else when you load it, this preset is first loaded and the problems happens with the preset you load.
