{"push_id":2549327638,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e39855fb0e0798a706443174431f7c0499f3463f","before":"f4791ac1399d997bfbcc61211137731f00fa5e39","commits":[{"sha":"e39855fb0e0798a706443174431f7c0499f3463f","author":{"name":"lane-s","email":"119e815277160dcde075c27ca4bcf9b1b71fe580@virginia.edu"},"message":"Add module selection system\n\nRenamed Player to ModuleSelector, since the component only servers to\nlisten to events that result in a new module being selected and then\npass the selection on to the SoundModuleMenu.\n\nThe selection system brings up the issue of the various module types.\nThere will eventually be an AudioEffectModule, a MIDIEffectModule, and\nan InstrumentModule. Currently the only module defined is SoundModule.\n\nAll of these modules will need to allow the user to browse for devices, load presets, select the module, and map module parameters to controls.\n\nTherefore, there should be abstract base classes which define much of\nthe functionality currently laid out in SoundModuleController and\nSoundModuleObject. These could just be called 'ModuleObject' and\n'ModuleController'.\n\nThis means that a Module is a physical object that has a 1:1 correspondence with\na Bitwig track.\n\nNoteOrbs and similar objects will no longer be considered Interface\nModules. Instead, they will called MIDI Instruments. There will also be\nMIDI Control objects which do not output notes, but correspond to MIDI\nCC messages that control instrument and effect parameters.","distinct":true,"url":"https://api.github.com/repos/lane-s/ComposeVR/commits/e39855fb0e0798a706443174431f7c0499f3463f"}]}
{"actor":{"display_login":"lane-s"}}