On Mon, Dec 03, 2007 at 05:34:32PM -0500, Garth Dahlstrom wrote:
> I don't by any means want to discouraging anyone from picking up the banner
> and creating a midi learning interface for Mixxx, it could be quite cool to
> have...  just tryin' to shed some light as to why no one is probably doing
> it yet...  :D

Indeed it would be cool, please do it if you want Brian!

But there's another reason -- it's not an easy problem. I mean,
it's reasonably trivial to identify a key number or controller number
(you have to take several samples and filter out bogus messages
from other controls which might have moved slightly, but easy enough).
What's harder is working out the precise nuance of the values that
different controllers send, especially for the dreaded jogwheels
but also for other kinds of rotary encoder, buttons that send 
strange combinations of CC instead of noteon/off, and so on.

It's something that would have been pointless to attempt before because
we didn't have experience of a sufficiently wide range of hardware. 
The last thing you want is a Learn function that gets it all horribly
wrong. That would give people the impression that mixxx as a whole was 
somehow broken/buggy. 
I think now we're getting towards the point where we'll have
(collectively) experience of a large enough range of hardware 
that we can see patterns emerging of the most common kinds of 
control message, so a useful Learn function might be feasible. 
Still, it's a bit of a project.

Ben


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to