-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add soft-takeover for MIDI controllers (XML and script) #5373
Comments
Commented by: rryan not gonna happen for 1.8.0 |
Commented by: Pegasus-RPG XML mapping support added in r2545 of trunk. Algorithm needs tuning though. |
Commented by: rryan Couple problems with the current implementation:
|
Commented by: Pegasus-RPG On Fri, Nov 12, 2010 at 4:35 PM, RJ Ryan wrote:
I have to figure out a better way to do this. I think taking time into
Indeed it does. Fixing that was outside of the scope of what I was |
Commented by: Pegasus-RPG r2558 of the features_softtakeover branch includes segfault fixes and adds soft-takeover to MIDI scripting. |
Commented by: Pegasus-RPG features_softtakeover merged in r2777 of trunk. |
Commented by: jenszo I cannot see any file in res/midi/*.js which already uses http://www.mixxx.org/wiki/doku.php/midi_scripting#soft-takeover
|
Commented by: Pegasus-RPG I didn't write the RMX script, but sure, we'll take a patch for that. Just make sure that any shifted functions still work correctly, with or without soft-takeover as appropriate. |
Issue closed with status Fix Released. |
Reported by: Pegasus-RPG
Date: 2010-04-05T06:38:52Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp555547
It would be useful in many cases for MIDI scripts to perform "soft-takeover" which prevents changing the MixxxControl value until the physical control matches (or comes within close range of) the MixxxControl value, avoiding sudden drastic control value changes. Adding this check as part of the MidiScriptEngine::setValue() function (using an extra boolean flag) is easy to do and can be used as needed for individual MixxxControls, but the downside is that it must be done on each setValue call as opposed to just setting a flag in the MixxxControl once and it being automatically handled. (Doing it in setValue() does allow for maximum flexibility however, and script writers need only do a search & replace to use it.)
The text was updated successfully, but these errors were encountered: