I noticed this bit in the kickstarter FAQ:
Is it worth putting a two-digit LED display and a knob for selecting programs or does that make it a lot more complex?
It is possible to program either effect-chains, or a program that contains several patches which you can switch between using one of the assignable pots.
I exactly understand the logic behind it: if you have multiple patches you want to e.g. switch between, you can use one of the spare knobs or even the (all new) push-button and writing the code that does the switch is the easiest thing there is.
The thing I'm concerned about is how it will work out when you want to use other people's patches, since there's a number of difficulties here (please correct me if I'm wrong):
- The artists that can't code won't have the freedom the coders will
- If you download a compiled patch (as opposed to the source code) from somebody else, you don't have the ability to plug it into your switching code anymore. I think many people will prefer to release their patches compiled, wanting to keep their code to themselves or being ashamed of the quality of the code
- Anytime you want to change a set of patches you'll be using for a performance for instance you'll have to rewrite some of the code and make sure there are no conflicts - it's not a breeze anymore
Do I see it the way it is? Do you have some ways to mitigate the problems on mind?
While writing this I figured that if there's a simple CLI interface (like a script ready) for loading patches (in addition to drag-n-dropping), one could just have a computer plugged to the OWL and load the patches with one hand, with a single keystroke. I think it should be good enough for anybody
BTW: thanks for doing this project, I'll be donating as soon as I'm sure the rest of my money will keep my belly full