Hello everyone.

I've been busy working on and polishing multiple MIDI device support in
the Features_PortMIDI branch over the last few weeks after Albert busted
tail writing the bulk of the PortMIDI back-end code.

It works correctly in Linux and Windows now (tested with two SCS.3ds,)
and the biggest user-facing changes are 1) MixxxMIDIBindings.xml and the
--loadXMLfile command line option are gone because we can no longer
assume just one device is connected, and 2) the MIDI presets/mappings
are written to a "midi" sub-folder under the preferences directory
(where mixxx.cfg is.) Currently the mapping loading & saving is
hard-coded to work with up to nine devices so we might want to address
that soon. (Just a matter of adding a place when using device numbers
10-99.)

The remaining issues at this point are all GUI-related (MIDI device
preferences pane) and are summed up under "PortMIDI branch" on the 1.8
to-do list here: http://mixxx.org/wiki/doku.php/1.8.0_to_do_list
I'm quite confused as to how much of the GUI stuff works, so could any
of you with experience take some shots at the stuff on that list? After
those tasks are complete, the branch will be ready for merging into
trunk (though I think it's still currently based on 1.7.)

Thank you very much for your time and attention. Looking forward to
multiple MIDI device support in 1.8!

Next up for me: an SCS.3m mapping & script and another video showing it
all in action!

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to