View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002898 | ardour | features | public | 2009-11-03 12:05 | 2009-11-03 12:05 |
| Reporter | nettings | Assigned To | |||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | SVN/2.0-ongoing | ||||
| Summary | 0002898: binding a midi controller loses current setting | ||||
| Description | this is somehow related from a user's POV to the recently fixed http://tracker.ardour.org/view.php?id=879: if i want to assign a midi controller, the current setting of that parameter is lost. at least when midi feedback is enabled, that need not happen. how about this?: fader is set to some value, say -6dB. ctrl-middle click, popup "operate controller now" midi controller is operated, we now know the controller, but discard the value and do not enable the controller right away. instead, we send midi feedback once. the controller jumps to the current value previously set in the GUI. then we wait a while for the controller to settle, say .1 sec (think slow motorfader). now the controller can be enabled. the question is how to handle this in the absence of midi feedback. all i could think of would be a locking feature like many midi controllers have, when the controller only becomes active after it has moved past the current value, to avoid discontinuities (to some degree). don't know how feasible this is with ardour. what do you think? | ||||
| Tags | No tags attached. | ||||
