Garth Dahlstrom wrote: > On Fri, May 15, 2009 at 4:03 PM, James Evans <[email protected] > <mailto:[email protected]>> wrote: > > Garth Dahlstrom wrote: > > I know about the VU LED problem, the output mappings are > correct, but I think the way the LEDs have been reimplemented, > they now have a 1-to-1 threshold value to output LED. I don't > know if that was a conscious decision or just a bug in the table > -> listener code (whatever the last output mapping for that > threshold key, is the only one that is activated). I haven't > had a chance to look into that. > > > Ok, no probs, I only mentioned it as it seemed to stop working at > the same time the jog wheel problem arose, but can't be certain of that. > > > The are only related in so much as the midi handling code (which does > both input and output) has been completely reimplemented for 1.7... >
Ok, ic. > > I didn't play with the jogs on the Mk2, but the ones on the RMX also > have this problem. This may be due to how HercJog option works (or > rather that its been depricated). I started writing a MIDI script > (javascript) for the RMX to "decelerate" the speed of the track over > time after a jog wheel movement, maybe this code would be useful for > the Mk2 as well. > > > Ok, sounds good. Does it make sense to you though that it *was* > working fine, in both 1.6.1+Herc and 1.8.0-beta1. Then, at the same > time, I seemed to loose any midi data into 1.6.1+Herc and got that > problem with the jog wheels in 1.7.0-beta1? > > > I don't know what 1.8.0-beta1 you speak of... current development > efforts are on 1.7.x anything else is likely an out of date branch of > trunk. It would have always done the behavior you described for 1.7.x. > Sorry Garth, that was a typo. I meant 1.7.0-beta1. I felt sure it was working. Guess I must have compiled 1.7.0-beta1 bu still been running the 1.6.1+Herc binary (thinking it was 1.7.0-beta1). > > > I'll just expand/clarify here exactly the symptoms in case it helps. > > Load track. Don't press play. Turn the wheel a tiny bit forwards. It > starts playing very fast normally - we would expect it not to > continue playing after the jog wheel stops moving. Turn it a wee bit > more forwards and it seems to double in speed. The same happens in > reverse turning the jog wheel the other way. When the jog wheel is > back in it's original position the track stops playing. > > As I say, the thing that puzzles me is that it was working ok. > > > It would only have worked in 1.6.1+Herc because the hercjog mapping flag > was moving the "wheel" offset value (which is inc/dec based on rotation) > towards 0. Hercjog in 1.6.x is acting as friction on the wheel, so if > you stop spinning the jog (i.e. Spinning CW = adding to the "wheel" > key), then the amount is incremented or decremented until it reaches 0 > (i.e. so stop spinning CW, friction reduces the "wheel" value by > dividing it by 2 every x ms until it reaches close to 0), "wheel" = 0 > being the standard forward playback speed. > Ok, that kind of makes sense. Guess it will make more so as I start playing. And the fact that I'm not getting any MIDI data at all into 1.6.1+Herc (when it was fine before) is just worth forgetting about in favour of concentrating on 1.7.x? > Absolutely. Would love to help. I know javascript fairly well. My > IRC nick is Ximmer, should you see me in #mixxx. > > > I will cook up the script sometime tomorrow morning and shoot it on to > the list (or if I see you in IRC). > Cool. I'm less likely to be in IRC on weekends, more likely weekdays 10.00-18.00 GMT+1 (UK). > Cheers, > > -G > > > > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
