Robin Sheat wrote: > But, some internal > documentation would be nicer. For example, something defining the behaviours > of 'jog' vs. 'wheel', what the various 'Rot*' things are, and so forth.
That would be great, and all someone would have to do is add that information to http://www.mixxx.org/wiki/doku.php/midi_controller_mapping_file_format#definitions_of_the_elements Ideally the writers of the original options should, since it's not entirely clear what they were trying to do, but carefully tracing the code in midimapping.cpp starting at line 713 ( MidiMapping::ComputeValue() ) and populating the wiki with your findings would be very helpful. > doesn't necessarily reflect reality. I'm pretty sure there is a command that > can be sent to the device to make it provide the current state of all the > controls. Do we have the facility to do this at some point during startup? This is what the <devicename>.init script functions were designed for. http://mixxx.org/wiki/doku.php/midi_scripting#init_and_shutdown_functions (The SCS.1m script does exactly this.) Sean <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
