Bug - Oversampling Render Control Doesn't Work

[vectorwarrior]

Had a hunch it wasn't working, so just did a test in Reaper and sure enough, setting the 'For Rendering' oversampling didn't change the render. Only changing the 'Normal' (playback) oversampling actually changed it in the render.

Here was my test case:

-Create new session, one track
-add MXXX, keep oversampling to 1x for both normal and rendering
-in MXXX add an oscillator
-after the oscillator add a saturator
-boost the saturator up to max gain (48dB), switch harmonics to 0 (this keeps the saturation clean and easier to read)
-render out ten seconds
-set MXXX oversampling on rendering ONLY to 16x
-render out ten seconds to a second file
-set MXXX oversampling on both rendering AND 'normal' to 16X
-render out ten seconds to a third file
-compare files

Here is the spectral analysis of the above. Red is 1x1x. Orange is 1x16x. Yellow is 16x16x. With the first number being 'normal', the second 'for rendering'.

Oversampling.jpg

You cant see Red because it's identical to Orange (trust me on this). This means that changing the 'for rendering' setting on oversampling didn't change anything. Sure enough, when i rendered out the 16x16 version is took longer too, so it's clearly not working correctly.

Possibly this is Reaper only.

[vectorwarrior]

Looks like there's a similar, but not identical issue with the smart interpolation settings too. Here's what I've found with smart interpolation:

Setting 'Normal' to High (Default) and changing the 'For Rendering' between High and then Extreme, I do see a difference in render time, so it's obviously doing something different, although it's maybe a 1% increase in render time when set to Extreme. But, changing 'Normal' to Extreme, DRASTICALLY changes the render time (800% increase). So, while there is a slight difference when changing the For Rendering setting, it's obviously not the same as changing it in Normal. Something is definitely screwy.

For this test I just looked at render time rather than output though, so that may be a bad test case.

[MeldaProduction]

Damn, I checked and it really doesn't seem to work in Reaper. I'll check what's wrong!

[MeldaProduction]

Ok so it appears to be a problem in Reaper. It doesn't return correct Offline flag. In fact, it works on one computer and doesn't work on another one here . I notified Cockos.

[pone]

I can confirm that it works on all my computers with the latest reaper.

[MeldaProduction]

Got reply from Cockos and it is NOT a bug, but there is a setting - search for "offline" in the preferences, one is something like "inform plugins about offline state" or something. You need to enable it . Otherwise the plugin cannot know you are rendering.

[vectorwarrior]

Ah, nice. Thank you, I'll give it a go when I'm back in the studio.

[vectorwarrior]

Couldn't waited, so i tested at home. The setting is indeed called 'inform plug-ins of offline rendering state'. It was disabled, i set it to enabled. It works correctly for VST2. It does NOT work for VST3.

You may want to inform Cockos that VST3 offline rendering states aren't being sent correctly, or check that your VST3 plugins are handling that data properly in Reaper.

Thanks!

[MeldaProduction]

Ok, I looked into it, and it seems it's a bug in Reaper, I asked them, so we'll see, maybe that's yet another option somewhere .

[Svama]

It´s already been fixed with Reaper pre release 5.22v10

[vectorwarrior]

Reaper was updated to version 5.22 today, fix works!