Patcher CPU, Native Nesting in Ctrl Surface

Post your ideas and suggestions here

Return to “To Do”

[You can only see part of this thread as you are not logged in to the forums]
Fortified Fibrous Friend
Tue Apr 13, 2021 5:40 pm

x

Patcher CPU, Native Nesting in Ctrl Surface

I think Patcher's the best so let's get to it:

- Ability to toggle plugins inside Patcher on/off to save CPU. For example, if one wants to make a multiband M/S saturation plugin in Patcher with multiple distortion types (esp. with oversampling), each type of distortion being emulated via Waveshaper would need a separate instance of Waveshaper and CPU will get taxed quickly (even if switching distortion types automatically stops oversampling Waveshapers not in use, every bit of CPU counts and the process of automating that will also eat up CPU). Alternatively, you could open the map to adjust the waveshaper manually, but that leads into the next request, which is likely less feasible:
- Ability to nest native plugins (EQ2/band splitter/waveshaper/etc) inside of the control surface. This would vastly improve Control Surface UIs and open the door to much more powerful options including metering, full control over PEQ2 interfaces from the control surface (if an EQ was feeding into other processing and had large effects from early on in an effects chain), multiband parameters, Waveshaping curves (for M/S, etc).
- Ability to change Z-axis order of knobs/sliders etc. Sometimes one layers knobs, and it is not convenient having to change over routing when creating a replacement knob for something because that knob is appearing behind one that was added later.
- Maybe we can reduce jittering when resizing/moving things in the control surface?
- Signal feedback inside patcher. I know. Limiter built-in or something and glhf with the maths. 8)
Last edited by Fortified Fibrous Friend on Sun Apr 25, 2021 8:21 am, edited 6 times in total.







Return to “To Do”