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):
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 😉
These are all valid concerns, and we’ve been thinking and talking quite a bit about how to do this.
It would be easy enough to reserve one control, say a button, for switching patches, and then letting users upload a number of them to switch between. However that takes one (or more, say if you want to move up/down) of the assignable controls away from use within the patches themselves. Also whatever solution we come up with might work well for some people but not for all. So currently we’re planning to keep it open.
Saying that, it’s fairly easy to write a kind of supervisor-patch which lets you switch between other patches, regardless of what they are, as long as the controls are assigned in a sensible way.
You must be logged in to reply to this topic.