Strange preset problem with Valhalla Supermassive and Reaper

[bleen]

Thanks for that update, @phankiejankie300! This gives us a good direction to start with and see if we can reproduce it and then track down/catch the bug if it's ours.

[Chris-S]

I'm using an older version (2.0.0) and was not able to reproduce on Win 10.

[phankiejankie303]

That's the thing... I believe it's something introduced on the latest 2.5 version which is why I asked for access to older versions of Valhalla Supermassive from Don in order to verify (or not) this.

Let's hope we will get to the bottom of this. It's a pretty annoying bug (for those of us that get to be affected by it) to an otherwise really great plugin.

[bagpipe200]

The bugs occurs during rendering only if the Valhalla Supermassive delay parameter is synced to the DAW.

So to sum it up. The bad actor is the synced (to DAW tempo) delay parameter (normal, triplets or dotted). It works fine during playback but it bugs out during rendering for some weird reason in REAPER. Using SM in manual delay mode is safe and there is no render bug.

This makes sense as I only ever use the synced delay option. Strangely I now haven't seen the problem for a while and I use Supermassive on pretty much every project. I still think there is another "factor" at play here or else we'd all be able to reproduce the problem 100% of the time.

I guess the workaround for me is to setup Sppermassive with synced delay and get the sound I want. Then switch to manual delay before any rendering of the project in Reaper.

[urosh]

To chime in: this has happened to me on at least one occasion with Supermassive. But it has happened on more occasions with Eventide Ultratap. So, I would guess it is not some specific Supermassive/Valhalla issue, but Reaper issue with exporting tracks with certain plugins. I also had trouble with repro'ing this. And it is not related in my case with selection of preset, both for Supermassive and Ultratap I would tweak from default preset.
In Supermassive case there were several instances in the track, and all were screwed up on render. I think that some settings we're applied correctly (mode and msec/bpm selector). So, just maybe Reaper gets confused with something related continuous vs dropdown/selector controls. In Ultratap case, it would typically ignore/screwup sync to host vs manual tempo IIRC.

[bleen]

The issue, as we have found it: when rendering audio using Supermassive in one of the sync delay modes, the msec value of Supermassive is set to 2000 msec. This happens on Sean’s M1 MacBook Air (running Big Sur), so it isn’t a Windows specific issue.

We have been able to reproduce this issue when rendering with Supermassive, going back to Supermassive 1.0.0. So this suggests that it is due to a recent Reaper change, as we would have heard about this issue over 3 years ago when Supermassive 1.0.0 was released. We have been able to consistently fix the issue when rendering by selecting the “Save Settings” button at the lower right of the Reaper Render window before rendering the file:

IMG_1524.png

We will continue to look into a code solution for this issue, but it won’t be a quick fix, as the sync modes will have to be tested in all the major DAWs, and right now Reaper is the only one with this issue (and it seems like this this might be an issue that has only come up with more recent Reaper builds). Plus, Sean is on sabbatical until mid-August, and doesn’t have a Windows build machine with him. In the meantime, clicking “Save Settings” before rendering should provide a solution.

[Funkybot's Evil Twin]

Hi Don, glad you guys made headway on this. This is probably stating the obvious, but you may want to reach out to Justin+Schwa on the Reaper side with how to reproduce it. If it's indeed a Reaper bug, 1) they will likely be quick to fix it, and 2) that would possibly save Sean from having to make any changes at all. If it's a Valhalla thing, they may be able to help pinpoint why.

Reaper has done a lot of work around the render window recently, so possible that something there broke.

[phankiejankie303]

In the meantime, clicking “Save Settings” before rendering should provide a solution.

Splendid, now we have two solutions for the problem, which is also now officially verified from the Valhalla devs.

The most crucial step is done so we now wait patiently for the fix either by Valhalla or REAPER devs.

Good work all!

PS: Considering the nature of this bug and REAPER's and Supermassive's popularity it really surprises me how few people participated/responded in this thread...

[enCiphered]

PS: Considering the nature of this bug and REAPER's and Supermassive's popularity it really surprises me how few people participated/responded in this thread...

This is due to the fact that this forum is a grain of sand or a drop of water in the ocean of music and music making, even though some people still think that KVR is the center of the Earth. But if you look closely, you will quickly realize that the same people are always actively participating in discussions. A truly insignificant minority,

[egbert101]

Well it's useful (for developers at least) to know such a problem so it doesn't appear with other plugins or DAWs. All bugs are essentially costing money for both devs and customers, so there is always a common interest despite how small it seems.

[surreal]

PS: Considering the nature of this bug and REAPER's and Supermassive's popularity it really surprises me how few people participated/responded in this thread...

This is due to the fact that this forum is a grain of sand or a drop of water in the ocean of music and music making, even though some people still think that KVR is the center of the Earth. But if you look closely, you will quickly realize that the same people are always actively participating in discussions. A truly insignificant minority,

Please advise us on the ultimate forum where we can get all the answers and detailed info as well as where the developers actively participate.. a forum that is infinetly bigger than kvr and is trully representative of the music industry please... I would loove to join it!!

[Frankie.T]

Just to sums things up. If i load SM and i tweak in sync mode, then i switch it to ms, i shoudn't have any issue anymore or do i misunderstood something?

[phankiejankie303]

Yeah one solution is that the other (as suggested by Don from Valhalla) is to hit "save settings" [edit (29/07/23): this doesn't work for me the problem remains only reverting to ms mode fixes it] in the REAPER render window and then proceed to render the track as usual.

[Frankie.T]

Yeah one solution is that the other (as suggested by Don from Valhalla) is to hit "save settings" [edit (29/07/23): this doesn't work for me the problem remains only reverting to ms mode fixes it] in the REAPER render window and then proceed to render the track as usual.

Thanks for the update.

Any news from Reaper devs?

[Frankie.T]

Thanks for that update, @phankiejankie300! This gives us a good direction to start with and see if we can reproduce it and then track down/catch the bug if it's ours.

Hi Don,

Do you have any news about this issue?

Thanks