Strange preset problem with Valhalla Supermassive and Reaper

[bagpipe200]

Just curious if anyone else has seen this issue. This is on a Windows 10 PC and the latest version of Reaper. And the latest version of Supermassive.

I have a Reaper project with a number of tracks. On one track I have Valhalla Supermassive. After a while, the Supermassive preset I have chosen still shows up as that preset, but the actual parameters have changed ie number of echos, feedback amount etc have changed. I verified that the parameters shown still looks correct, but the sound is not. If I select another preset, then go back to the original preset everything is good.

I haven't been able to reliably reproduce the issue but it has now happened on several occasions. I usually notice it when I render the project ie I then notice that the sound isn't what it originally was on that track with Supermassive.

[Frankie.T]

I'd open a ticket to Valhalla and/or Cockos, so if there is a bug they can fix it

[Funkybot's Evil Twin]

Just curious if anyone else has seen this issue. This is on a Windows 10 PC and the latest version of Reaper. And the latest version of Supermassive.

I have a Reaper project with a number of tracks. On one track I have Valhalla Supermassive. After a while, the Supermassive preset I have chosen still shows up as that preset, but the actual parameters have changed ie number of echos, feedback amount etc have changed. I verified that the parameters shown still looks correct, but the sound is not. If I select another preset, then go back to the original preset everything is good.

I haven't been able to reliably reproduce the issue but it has now happened on several occasions. I usually notice it when I render the project ie I then notice that the sound isn't what it originally was on that track with Supermassive.

Which version? VST2, VST3, AU? Mac or Win?

Definitely include that when reporting the info. And if you have a project and/or steps to reproduce, have those ready to go when reporting to Valhalla/Reaper.

[Dirk Diggler]

Win10 and Reaper with Super Massive here on an old machine, I do not have the issue.
Also no issues in Gig Performer either, everything stores as it was last left at save.
I tend to only use the VST3 version.

You might check your Reaper preferences, maybe something got unchecked? Sounds like it's just not saving the last state of the plugin.

[phankiejankie303]

I have the exact same problem and it's more apparent when rendering the tracks, then Supermassive sounds totally different than the one I've set up before rendering.

To rectify this I reload the project add a new instance of Supermassive dial in the exact same settings and render the track or just recall the preset if I have saved one.

Strange bug indeed because on project load the effect sounds correctly. It's when rendered offline that sounds different.

Do you have Novation's Automap software installed btw?

PS: If you found a solution on this please do share.

[Funkybot's Evil Twin]

Over the weekend, I left Reaper on overnight and a preset changed settings at some point. Using the VST3 in Reaper. So there's definitely something happening. Going to report to Valhalla. Others should as well because I don't know how to reproduce this and those are always the trickiest bugs to diagnose.

[bagpipe200]

Glad to hear its not just me. I created a problem report with Valhalla. I was going to post the problem report number but they don't provide a number. The title of my Valhalla report was "Strange preset problem with Valhalla Supermassive and Reaper".

Valhalla asked me if my track had tempo changes (it didn't) and what the Sync mode was set to - it was Note. They then asked if I could reproduce it on the VST2 version of Supermassive. I haven't tried that yet as the issue is not 100% reproducible.

[Frankie.T]

Please keep to write updates on this issue when you have

[Funkybot's Evil Twin]

Glad to hear its not just me. I created a problem report with Valhalla. I was going to post the problem report number but they don't provide a number. The title of my Valhalla report was "Strange preset problem with Valhalla Supermassive and Reaper".

Valhalla asked me if my track had tempo changes (it didn't) and what the Sync mode was set to - it was Note. They then asked if I could reproduce it on the VST2 version of Supermassive. I haven't tried that yet as the issue is not 100% reproducible.

In my case, it was ValhallaVintageVerb, VST3. Going to try to reproduce after work.

I had changed a bunch of settings and created a Dirty Hall-based preset with a 2 second decay time and both early+late diffusion dialed in somehere in the 60% range. Walked away from the PC and forgot about it. Woke up the next morning to find the PC still on, and the preset had reverted back to the default settings (4 second Concert Hall with Diffusion at 100% for both Early/Late), but it was still showing my preset name. At first I couldn't figure out why this patch that was sounding great yesterday was just meh today, then I noticed the decay time. I reloaded the preset and everything was fine.

it was like it had decided to reset itself to the default preset at some point.

[phankiejankie303]

The first thing I did after experiencing the bug was to install the VST3 version over VST2. It didn't make any difference at all so I guess it has something to do with REAPER and the latest update of Supermassive. I never encountered this bug with version 2.4 of Supermassive but now I can’t go back because I’ve used the two new modes introduced in 2.5 in various tracks .

[Frankie.T]

Any news on this issue?

[Funkybot's Evil Twin]

Any news on this issue?

I've had zero luck reproducing it with the VintageVerb VST3 so I didn't report it because now I'm questioning if what I think happened in the first place actually happened. But I'm making a point of keeping an eye out for it.

[dug dog]

This weirdness is still happening with Super Massive VST2 with Reaper 6.80 on Windows 7. Open a previously saved project and Super Massive may, or may not, "operate" at the proper settings. Close the project, re-open, and Super Massive behaves as expected. (I haven't yet verified whether or not the Super M's GUI shows the "correct" settings when it doesn't behave properly.)

[phankiejankie303]

I've just learned to live with this. Every time I am about to render a track with Supermassives I just redial all the parameters again or reload the preset before hiting the render button. Problem gone but unfortunately this need to be done every time I render a track otherwise the feedback just goes crazy on the rendered track as if it's cranked all the way up.

[diroxe7660]

Oof, just happened to me too. Does this only happen with specific Reaper and/or S-Massive versions? I don't remember this happening before.