KVR Audio

dug dog · Post by **dug dog** » Sun Jul 02, 2023 10:00 am

I can't speak to the past, but I'm using the latest version of Reaper and SuperM. I'm seeing similar things reported with other Valhalla plugs.

(I did confirm that, in my case, the SuperM GUI shows the correct settings even when the actual settings are clearly "wrong".)

phankiejankie303 · Post by **phankiejankie303** » Sun Jul 02, 2023 4:20 pm

Same here everything seems to be “in order” albeit it isn't. The plugin might show the correct parameter values but that doesn’t translate into the correct sound, something is amiss.

I used to drop SM into everything, now not so much due to this bug.

Same reason I avoid using their other plug ins in fear the same would happen, which it seems it does, judging from dug dog's comment above.

Frankie.T · Post by **Frankie.T** » Sun Jul 02, 2023 7:57 pm

I have an older version, you can download in the following link, can you try if this works as intended or suffer that bug too?

https://we.tl/t-yfkO9Mb8eP

Funkybot's Evil Twin · Sun Jul 02, 2023 8:10 pm

Are folks experiencing this with the VST2, VST3 or both?

bagpipe200 · Post by **bagpipe200** » Sun Jul 02, 2023 11:20 pm

Funkybot's Evil Twin wrote: Sun Jul 02, 2023 8:10 pm Are folks experiencing this with the VST2, VST3 or both?

I originally created this thread. I experienced the issue with VST3. One of Valhalla's suggestion was to try and reproduce the issue in VST2. I didn't bother trying that.

dug dog · Post by **dug dog** » Sun Jul 02, 2023 11:55 pm

VST2 is problematic here. Haven't tried VST3.

surreal · Post by **surreal** » Mon Jul 03, 2023 4:37 am

I must check this.. it could a setting in the autosave and offline rendering that resets the SM vst engine

Frankie.T · Post by **Frankie.T** » Mon Jul 03, 2023 6:22 am

For people who wanna do some tests, please also try the version i linked, if you are concerned about downloading something from a stranger, use virustotal to check the file

robindrieghe · Post by **robindrieghe** » Mon Jul 03, 2023 11:47 am

i had similar in flstudio with vst 3. vst2 works ok here.

Andreya_Autumn · Post by **Andreya_Autumn** » Mon Jul 03, 2023 3:39 pm

I did have something similar happen with ValhallaDelay actually. Hmm... probably worth reporting to either dev.

Frankie.T · Post by **Frankie.T** » Tue Jul 04, 2023 6:30 am

People with this issue should really report to both devs

dug dog · Post by **dug dog** » Tue Jul 04, 2023 10:59 am

Reported to Valhalla. Will report to Reaper forum today.

"Supermassive VST2 settings are not properly saved with Reaper project. When a saved project is re-opened, the SuperM GUI settings look correct, but the plug is not out-putting those settings. I had saved my SuperM settings as a Reaper VST preset, and re-loading the Reaper preset makes everything work correctly. Other users are reporting similar issue with VST3 as well.
Thanks."

Frankie.T · Post by **Frankie.T** » Tue Jul 04, 2023 11:16 am

Thanks dug dog for the reports!
Please keep us updated.

For everyone else who suffer from this issue, make your own report too, cause the more infos devs can collect the sooner they can fix the issue

dug dog · Post by **dug dog** » Tue Jul 04, 2023 11:24 am

New Reaper thread here: https://forum.cockos.com/showthread.php ... ost2690090

phankiejankie303 · Post by **phankiejankie303** » Fri Jul 07, 2023 7:07 am

I have to add that in my laptop I have an older version (1.2) of Valhalla Supermassive that works faultlessly in REAPER but it's missing a lot of the new algorithms (many of which I've already used in many tracks so I can't back track).

Strange preset problem with Valhalla Supermassive and Reaper