Modality-toolkit icon indicating copy to clipboard operation
Modality-toolkit copied to clipboard

A SuperCollider toolkit to simplify the creation of personal (electronic) instruments utilising hardware and software controllers of any kind.

Results 31 Modality-toolkit issues
Sort by recently updated
recently updated
newest added

ATM groupTypes like noteOnOff, noteOnOffTouch expand properly into MKtlElements, but not yet into proper responders and midi lookup dict entries within MIDI devices. -> Do extensive tests of all types...

Currently, most desc files of MIDI keyboard device create guis where all reachable keys are shown, e.g. for a nanokey, keys 0-120. this is useful to get to all keys,...

question
design goals
MKtlGUI

groupType expansion should allow for different midiNums of its components, and for adding more elements to the group: ``` // different number for polytouch : (midiNum: [21, 21, 61], groupType:...

Explicitly allocate time to prepare a Modality Concert (ie. playing _with_ Modality instruments). Should be e.g. August/September.

documentation
design goals
use case

E.g. by saving the state of an `MKtlElementGroup` and recalling it later.

enhancement
question
design goals

Currently, Tutorials/How_to_create_a_description_file_for_MIDI is behind the implementation: It says \noteOnOff types has turned out problematic, it is better to make the on/off pairs by hand, or use MKtlDesc.notePair. The current implementation...

if the same fader has different cc-numbers for in and out but physically the same thing, we should deal with it in the spec.

desc files
MKtlElement

as we are assembling the release for #200, I stumbled over `MKtlElementCollective` which still needs a basic Help file. I am willing to write it, though need some two sentences...

Most desc files now have complete gui style info and look quite good; in some the elements are not aligned as on the physical device, but they are usable. The...

desc files
MKtlDesc