PATTERN CONTROL / TWEAK! Screen
Posted: Fri Dec 15, 2017 2:41 am
PATTERN CONTROLLER / TWEAK! Screen
While reading all the midi control stuff, and trying to stop my midi controller from constantly disconnecting, *this* occurred to me. I think this would be *immensely* cool, but obviously, there's quite a lot of work here, and I should probably be a lot less cheeky!
SCREEN LAYOUT
Top row - 8 pattern select buttons.
Right column – 8 Pattern group + Scene select buttons labelled ABCD ABCD.
The rest of the screen is a load of assignable sliders and buttons, like a wonderful in-built soft midi controller, with everything you might want to tweak at once right now, right there on one screen.
NAVIGATION
On the right are 8 smaller buttons, a column of 1x8 with 2 sets of A, B, C, D.
First ABCD set, press A to show A1-A8 pattern buttons, B to show B1-B8. If A1-A8, is already showing, pressing A changes the active pattern set to A9-A16, and back. Etc, etc, etc.
Bottom ABCD set. Same selection logic as above, but selecting 8 controller scenes.
I think this would be a good compromise between screen space, and getting where you want fast.
I know the MIDI options allocate an optional MIDI CC to a parameter, and this is set app-wide.
I think as a user interface, it would be nice to set parameter to a slider, by long clicking on a slider or button, and this opening a popup. Obviously there are A LOT of parameters available, but I think things work pretty fine, and go pretty deep, in the MIDI options.
If the controller scenes are loaded and saved with the song, that would be lovely.
Still great and workable if they're preset in options tho, like the MIDI mapping.
I guess the controller scenes could be loaded per pattern, but it might get silly!
Maybe a user option for size and number of sliders and buttons per scene, I don't know.
Obviously, it's a compromise between number of sliders and buttons on screen at once, vs size.
Having a lot of knobs and buttons would be cool.
But for adjusting several at once, bigger is probably better.
Buttons wouldn't necessarily have to mirror pictorial feedback on the actual app screens – eg, the Beast waveforms, filter types or OSC Mod Type, could be simple press for next with a number feedback (1, 2, 3, 1, 2, 3, 1…) type thingies.
You already have MIDI controllers able to adjust this stuff, so I *think* it's workable.
The complication might be automation feedback, but if there isn't any feedback, that would still be fine.
Some kind of short punchy label on the sliders and buttons might be nice. Not necessarily 100% accurate due to screen space, but readable. T12:LFO1 for the LFO 1 depth on T12. V2:WAV1 for a waveform button.
Some of sliders and buttons could be pre-set by default to volume, cutoff, mute, reverb send, etc, for each channel.
Others could default to random assigns, based on the module, to gently alert new users to the possibilities within.
I already know that I've written too much, and gone too far!
But I think others might like this just as much as me.
What do you think?
While reading all the midi control stuff, and trying to stop my midi controller from constantly disconnecting, *this* occurred to me. I think this would be *immensely* cool, but obviously, there's quite a lot of work here, and I should probably be a lot less cheeky!
SCREEN LAYOUT
Top row - 8 pattern select buttons.
Right column – 8 Pattern group + Scene select buttons labelled ABCD ABCD.
The rest of the screen is a load of assignable sliders and buttons, like a wonderful in-built soft midi controller, with everything you might want to tweak at once right now, right there on one screen.
NAVIGATION
On the right are 8 smaller buttons, a column of 1x8 with 2 sets of A, B, C, D.
First ABCD set, press A to show A1-A8 pattern buttons, B to show B1-B8. If A1-A8, is already showing, pressing A changes the active pattern set to A9-A16, and back. Etc, etc, etc.
Bottom ABCD set. Same selection logic as above, but selecting 8 controller scenes.
I think this would be a good compromise between screen space, and getting where you want fast.
I know the MIDI options allocate an optional MIDI CC to a parameter, and this is set app-wide.
I think as a user interface, it would be nice to set parameter to a slider, by long clicking on a slider or button, and this opening a popup. Obviously there are A LOT of parameters available, but I think things work pretty fine, and go pretty deep, in the MIDI options.
If the controller scenes are loaded and saved with the song, that would be lovely.
Still great and workable if they're preset in options tho, like the MIDI mapping.
I guess the controller scenes could be loaded per pattern, but it might get silly!
Maybe a user option for size and number of sliders and buttons per scene, I don't know.
Obviously, it's a compromise between number of sliders and buttons on screen at once, vs size.
Having a lot of knobs and buttons would be cool.
But for adjusting several at once, bigger is probably better.
Buttons wouldn't necessarily have to mirror pictorial feedback on the actual app screens – eg, the Beast waveforms, filter types or OSC Mod Type, could be simple press for next with a number feedback (1, 2, 3, 1, 2, 3, 1…) type thingies.
You already have MIDI controllers able to adjust this stuff, so I *think* it's workable.
The complication might be automation feedback, but if there isn't any feedback, that would still be fine.
Some kind of short punchy label on the sliders and buttons might be nice. Not necessarily 100% accurate due to screen space, but readable. T12:LFO1 for the LFO 1 depth on T12. V2:WAV1 for a waveform button.
Some of sliders and buttons could be pre-set by default to volume, cutoff, mute, reverb send, etc, for each channel.
Others could default to random assigns, based on the module, to gently alert new users to the possibilities within.
I already know that I've written too much, and gone too far!
But I think others might like this just as much as me.
What do you think?