I could fully understand that the UI/UX challenge is a reason why this has not be implemented yet.
I can see two spots where this could be implemented. I assume that two new of these sound shaping tools would be available.
1. As an add-on of each algorithm
On the last parameter page where in/out gain is located would be two new parameters:
- Shaping Tool: Would select the type of tool to be applied like 4 band EQ, Pan, Compressor, Gate.
- Position: Determines if the tool is applied before or after the effect.
Depending on the tool there would be a few more pages for the parameters. I see certain pros and cons:
+ Seamlessly blends into the existing menu structure.
+ Easily discoverable and accessible when doing sound design.
– It should be part of an algorithm preset to keep UX simple and predictable but might not make always sense as such because it’s dependent of the whole effect chain.
– Re-position of the tool (eg. use it after algo two instead of before algo one in the chain) is cumbersome.
– The final amount of parameters can be big. There are algos which have 12 parameters and if a 4 band EQ with filters is selected as tool the total amount of parameters would be 30 spread over 10 pages.
– Adding more than one tool would make the menu a mess.
2. As dedicated blocks in the routing chain
The routing menu would get two new pages before or after the insert configuration. Each page would consist of two static parameters which are similar to the one above:
- Type: Would select the type of tool to be applied like 4 band EQ, Pan, Compressor, Gate
- Position: Determines the position in the effect chain
Depending on which type would have been selected, additional parameters would be visible.
Pros and cons I see in this solution:
+ The blocks are independent from the effects which allows easier positioning and persistent state between preset/algorithm changes.
+ It’s a bit more logical
+ More sound shaping possibilities because more flexible placement (ie. affect inserts or one algo with two tools)
– The menu structure and visual representation within the routing menu needs more rework compared to the solution above.
– Accessibility is not ideal because it’s a different menu not directly associated with sound design.
– Preset saving would only possible on the program level unless new paradigms for that would be introduced.
What do you think? I’m very open to additions or different approaches.
