feature request: layers about bschaffl HOT 2 CLOSED

Those are good points, unfortunately. ;)

1. You could make less parameters automate-able. I'm not sure I like that idea though...
2. I was hoping it would make it easier for you to get the visuals in time, at least compared to multiple instances.
3. I wouldn't say I fully understand it, but I think understanding the individual parameters and hearing the effects is enough to be able to use a plugin.

I hope one day someone will come up with solutions somehow! :)

from bschaffl.

Honestly, I experienced a lot of problems with B.Shapr's multiple shapes.

Problem 1:
Each shape almost needs the complete set of controllers. The easiest way to implement controllers are the LV2 control ports. But you have pre-define all ports you maybe will need. No creation of ports on the fly. And we have already > 60 control ports in B.Schaffl with one layer. Times the max. number of layers. The higher the number of controllers the trickier for the user to access to the controllers (e. g., via automation).

Problem 2:
Latency. It's now the job of the plugin to handle latency between the layers. And this can be tricky too. This is the main reason why progression of development for B.Shapr slowed down.

Problem 3:
Usability. Too many layers may make it complicated. And difficult to understand what's going on inside the plugin. Especially in combination with latency. Multiple instances of a plugin instead of multiple layers may communicate this in a clearer way. But anyway, do you fully understand your BSchafflSeries demo?

from bschaffl.