The Xponent (I used to have one but don't anymore, so this is from memory) works similar to the Total Control but the "zero point" is 63 or 65. Values less than 63 are anti-clockwise, more than 65 are clockwise.
I never read any meaning into the frequency at which the CCs were transmitted (mainly because I didn't see any easy way to do it in mixxx); the value itself seemed to adequately convey the speed of rotation. The full value range was never used in practice, you'd need to apply an electric drill to get anywhere near 127 or 0. So I added a sensitivity adjustment within mixxx to scale it in a user- configurable way (all of which has probably now disappeared from the code...). Ideally, one *would* also look at the frequency of the incoming CCs so that you'd be able to spot when rotation has stopped but the encoder has not transmitted 63 or 65, which did happen sometimes. In fact I think I broadened the zero range a bit to prevent the risk of drift. Even the slowest real turning of the wheel in normal use would produce values of 3-5 away from 64 so this was no problem. Ben ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
