justin = { main feed , music , code , askjf , pubkey };
Ask Justin Frankel
No reasonable question unanswered since 2009!

Suggested topics: programming, music, sleep, coffee, etc.

Note: please do not ask questions about REAPER features, bugs or scheduling, use the forums instead.

Name: Ask: Human (enter yes):
[back to index] | [unreplied] | [replied] | [recent comments] | [all]
Question: Hello Justin. Is there a possibility for the instance effect oversampling in reaper to allow higher oversampling rates than 768k? I know It may seem excessive, but some plugins could really benefit from oversampling into the megahertz range, In fact this can be brute forced already, but is a bit cumbersome. Thanks for all you do.
Asked by Resonant Peak (201.138.38.x) on May 31 2022, 12:05pm
Reply on May 31 2022, 5:19pm (edited at May 31 2022, 10:29pm):
    We could, but so many plug-ins would fail disasterously it seems like a bad idea (768k is problematic enough)

Comments:
  • Posted by Resonant Peak (201.138.38.x) on May 31 2022, 7:45pm:
    Thanks for answering. I understand that most plugins fall apart easily, but the effect on some of them like amp sims Is nothig short of transformative (In a very good way that would otherwise be impossible in other DAWs) Maybe a "this could go horribly wrong" checkbox somewhere in the settings menu?

  • Posted by Justin on May 31 2022, 8:19pm:
    If you want to experiment, you can edit the .rpp, look for NEXT_FX_OVERSAMPLE. 0=no oversampling, 1=~96k, 2=~192k, etc. 15 is the max allowed. It might blow up.

  • Posted by Justin on May 31 2022, 8:21pm:
    You could also make a reascript to set those values

  • Posted by Resonant Peak (201.138.38.x) on May 31 2022, 11:50pm:
    Looks lI'll learn some scripting then.I ran a few tests with some JS plugins as well as native reaper plugs and they indeed reach higher OS multiplierss but only if the "chain oversampling" option is active, otherwise no matter what value you set them at in the .rpp file, they default to x16. I don't know If this is intended behaviour, but that sets the effective maximum OS value to "8" (or x256 ). I think I'll open a forum post on this.

  • Posted by Justin on June 1 2022, 1:48am:
    ah oops actually we limit it to *16

  • Posted by Justin on June 1 2022, 1:48am:
    ...will allow higher values via script in a build coming soon

  • Posted by Justin on June 1 2022, 1:57am:
    increasing the limit to 10 (1024x), or 45-49MHz...

Comment:
    Your Name:   -- Site Owner's Name:  (for human-verification)

    Comment:
[back to index] | [unreplied] | [replied] | [recent comments] | [all]
Copyright 2024 Justin Frankel. | RSS