I get, vaguely, how MIDI mapping works, and is done (ugh,
XML in vi, but I've done worse things).
But I'm missing how the "primitives" that mixxx supports are
specified.
So a (example) jog wheel generates ROTATE-CLOCKWISE (CW) and
ROTATE-COUNTERCLOCKWISE (CCW) events issued as MIDI command
strings. But where and/or how is the mixxx-function-mapped-to
that performs the "increase playback rate in forward direction"
(map to CW) or "increase playback rate in reverse direction"?
There's two things hidden in that question: one of mapping
mechanism (syntax, etc) and the other is the more-occult
paradigm, eg. how does jogging actually work at the interface
level?
I mean, playing normal speed is a function of mp3 bitrate and
all; let's call that speed 1X. Given nothing else, mixxx clearly
plays tracks at that rate.
In a "vinyl" model, I'd twist the EP clockwise/faster (positive
sign) or drag finger-slow it (negative factor). Twisting the
vinyl EP creates an accelleration rate (in my head and fingers
and ear) that translates to a bunch of instantaneous playback
speeds (1X ... 1X, 1.5X, 2X, 3X, ... 2.2X, 1.2X, 1X times
normal rate). (Finger-drag-slowdown is the same, only the sign
changes -- I think.)
Does the controller need to maintain accelleration profile
("now play at 1X" ... "now play at 3X") or does mixxx build one,
given a series of CW or CCW events from the MIDI jog dial?
Is there a list of the mapped-to available mixxx playback-rate
functions?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
