Strange preset problem with Valhalla Supermassive and Reaper

[Frankie.T]

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).

Please report it to Valhalla so they can have a better understanding about the issue

[phankiejankie303]

There is a lot of talk about how and when this bugs occurs. I can reproduce it quite easily so I made a comparison playlist in Soundcloud for anyone to hear (and use).

The "clean" version is when I recall the preset and the rendered audio file is correct.

The "bug" version is the one that occurs if when loading the project I don’t recall the preset. You can here that timing is way off.

https://soundcloud.com/user-38230094/se ... al_sharing

[Funkybot's Evil Twin]

There is a lot of talk about how and when this bugs occurs. I can reproduce it quite easily so I made a comparison playlist in Soundcloud for anyone to hear (and use).

The "clean" version is when I recall the preset and the rendered audio file is correct.

The "bug" version is the one that occurs if when loading the project I don’t recall the preset. You can here that timing is way off.

https://soundcloud.com/user-38230094/se ... al_sharing

Great!

Non how do you reproduce it easily? What are the steps? Did you report to Valhalla? Have a project to share?

[phankiejankie303]

I have zero problems reproducing this because it happens to me every time I render a track with Supermassive(s) in it.

Playback is always fine (as far as I remember) on my side, the bug pops up only when rendering.

Yeah I plan to make a Valhalla report, hopefully later in the day.

[dug dog]

In my case, I've used it in only one project. I made a stripped-down project in an attempt to isolate the issue and make it reproducible by others, but the dang thing works perfectly in that project. So, I don't know.....
I guess I'll just stop using it.

[Frankie.T]

In my case, I've used it in only one project. I made a stripped-down project in an attempt to isolate the issue and make it reproducible by others, but the dang thing works perfectly in that project. So, I don't know.....
I guess I'll just stop using it.

Didn't you got any reply from Valhalla?

[dug dog]

No reply from Valhalla yet, but it was a big holiday week in North America (if that's where they're at.)

[dug dog]

Got a response from Valhalla tonight:

"I’m having difficulty reproducing this in Reaper 6.81 with Supermassive 2.5.0 VST2 and VST3; the saved settings always come back when reopening Reaper just as they were saved. This is under Win11, but I can’t imagine that’s a factor. Do you have a stripped down Reaper project you could send us where this is always reproducible?"

I replied with the same info that I reported up-thread: I tried to create a stripped down Reaper project that reproduces the "bug" but was unable to do so.

[Frankie.T]

There is a lot of talk about how and when this bugs occurs. I can reproduce it quite easily so I made a comparison playlist in Soundcloud for anyone to hear (and use).

The "clean" version is when I recall the preset and the rendered audio file is correct.

The "bug" version is the one that occurs if when loading the project I don’t recall the preset. You can here that timing is way off.

https://soundcloud.com/user-38230094/se ... al_sharing

Reading the last post of dug dog seems Valhalla cannot reproduce it. Since you are able to, could you please contact them sending also your project?

[Funkybot's Evil Twin]

It sounds like the issue occurs after render. Please let them know. Likely a critical piece of information.

[bleen]

I'm happy (ish...) to keep trying to reproduce any of these bugs in Reaper, but please write to us at support (https://valhalladsp.com/support-request/) and don't just say "this is happening on my system" - please give me a step-by-step process of how you are able to reproduce the issue.

So far, I haven't been able to recreate the bugs folks have written in with; this makes it really difficult to track down where the problem is and if it's a Valhalla issue or a Reaper one.

Thanks!

[Funkybot's Evil Twin]

Yes, please listen to Bleen (Don from Valhalla's support). If you have a way to reproduce this reliably, please share steps and/or a project with Valhalla support. If that doesn't work, maybe even report to Reaper support and include the link to the project but also your reaper.ini. Could be a weird setting causing this particular condition to appear.

I think I may have run into this once or twice, but I can't be 100% that it wasn't user error and definitely can't reproduce it consistently. Tried a few test renders and they were fine. Wish I could be of more help.

This is currently the best lead. Hoping phankiejankie303 can reply with details.

I have zero problems reproducing this because it happens to me every time I render a track with Supermassive(s) in it.

Playback is always fine (as far as I remember) on my side, the bug pops up only when rendering.

Yeah I plan to make a Valhalla report, hopefully later in the day.

[phankiejankie303]

So far, I haven't been able to recreate the bugs folks have written in with; this makes it really difficult to track down where the problem is and if it's a Valhalla issue or a Reaper one.

I guess it all falls down on me... the pressure

OK I gave this a bit of a thought and I need to try some stuff today after work before I bring this to Valhalla and REAPER. There is this thing I thought was weird when trying to Automap Supermassive and it has to do with the fact that SM reports two delay parameters to the DAW independently regarding time. It reports both the synced values but also the non synced ms values regardless of the mode you choose on the plugin.

So I need to do some tests.

1) I am going to make a non synced to tempo preset (manual delay ms mode) and see if the bug occurs during rendering if it doesn't I think we are narrowing down on the problem.

2) I am going to load a project with SMs on it and instead of recalling the whole preset I will just redial in the delay values if the render is fine then I think we have our bad actor right there. Meaning for some weird reason REAPER doesn't pick up the correct delay values during rendering despite the values being correctly displayed on the plugin.

PS: Dear Don is it possible to give us access or maybe make a WeTransfer .zip with the previous versions of SM? I think it could help with all of this. Maybe this strange bug only happens with the last version 2.5.

[phankiejankie303]

OK I've done my testing and it seems I was spot on...

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

Valhalla Supermassive in manual ms mode for the delay has no render problems.

I loaded my project (the one I posted on Soundcloud above), changed the preset from synced to manual ms, saved the project, reloaded and worked fine. Switched back to synced delay, boom, again problematic rendering.

Also I found out that you don't need to recall the preset to get a proper render, opening the GUI and moving a bit the delay knob when in synced mode, means you get a bug free render as the parameter picks up its value properly again.

Another trick to avoid the render bug is to set up the delay in synced mode and once you are happy with the result then switch to manual mode for the delay. The value matches your synced selection and it will always render properly.

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.

[phankiejankie303]

So far, I haven't been able to recreate the bugs folks have written in with; this makes it really difficult to track down where the problem is and if it's a Valhalla issue or a Reaper one.

Thanks!

Dear Don please check my post above.