On Mon, Jan 5, 2009 at 6:51 PM, Albert Santoni <[email protected]> wrote:
> the deal: > - Feature freeze now (other than the stuff below) > - Disable the LADSPA tab, since we're up to our neck in MIDI. I'm of the mood that we should do two releases... 1) the polished feature frozen version described here... (MIDI Learn + Script + MIDI Script) 2) the second a mad scientist/house clearing (MixxxX?) release that basically turns on the experimental stuff + LADSPA, ipod, m4a and tonal support... so normal users can have a chance to play with that stuff until we can produce the first Mixxx 2 builds. - We'll keep the old crappy MidiObject-based code. > - Sean just wrote sysex output support for Windows (MidiObjectWin) > - I will write the CoreMidi output support for OS X > (MidiObjectCoreMidi). > > - The prefs dialog still needs work, but we think we've thought of a > quick and easy way to fix it: > - Remove the separate device selection dialog. > - Add a new "Device" tab in the bindings dialog before the "MIDI > Input Bindings" tab. > - Inside the "Device" tab, have a single drop-down to select the > MIDI device. > - *** Auto-load a binding on device selection, if it's a device we > have a mapping for. *** > > The biggest problem with the MIDI bindings dialog is that it's a bit > difficult to use for new people, so auto-loading the right binding > will mean that most people won't have to tinker with the bindings > interface. This makes things easier for novices, and still gives > advanced users the option to MIDI bind with Tom's interface to their > heart's content. > Essentially, if we have decided that we are sticking with the old midi-object code, and not exploring multiple MIDI device support until Mixxx 2, then this dialog will largely be throw away (which is fine with me). Probably be one drop down for device, one to load mapping (both in and out), something similar to the old sytle controller mapping... autobinding might be okay if there are no other mappings present in the table, but I would probably not have it run if there were already bindings present. Also likely merge MIDI Learn and MIDI Group Learn into one button that does each behaviour based on whether 1 or multiple rows are selected as the distinction to me is a little bit silly. I'll do some playing on paper to see what I can come up with interface wise... Cheers, -G
------------------------------------------------------------------------------
_______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
