Is there a way to set initial values for the controls of patch displayed on the website?
I noticed that after the last updates the initial control values have been changed from 50 to 35, but i wonder if there is a user preference, which we can set upon upload or editing the patch?
On a wider angle it could be useful to supply presets already on the patch page, so one can try different suggestions without using the owl. Would that be wished for or possible?
Currently not, though we can set the default back to 50% if that’s better.
There will (soon!) be a way to define more parameters and to give them default values, which will take care of the initial state.
Having user defined presets is a good feature, could you add it as a feature request on github please?
We’ve discussed presets here in the past. It’s nice because they could work over web midi as well, giving you a recall method.
Of course, once you start doing this sort of thing, you’re only a bit of Javascript away from preset morphing and parameter automation…!
Been trying to work out some ideas around this.
Here’s a super basic example of a custom control page for a patch that makes heavy use of extended parameters:
https://rawgit.com/pingdynasty/OwlWebControl/master/quadfm.html
The four presets selects values and sends them out to the device.
Here’s another raw example of extended controls, this time with a virtual keyboard (but no presets):
https://rawgit.com/pingdynasty/OwlWebControl/master/extended.html
An interface along these lines, with the addition of patch store and device configuration, could replace OwlControl completely.
We’d like to somehow work in presets, but beyond having default parameter values (ie a single default ‘preset’ per patch) it could potentially get quite complicated.