View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008932 | ardour | bugs | public | 2022-06-29 16:49 | 2022-06-29 16:58 |
Reporter | afranke | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | GNU | OS | Linux | OS Version | (any) |
Product Version | 6.9 | ||||
Summary | 0008932: midnam Values not taken into account for automation ranges | ||||
Description | On a MIDI track, I set it to Novation A Station and add an automation on controller 3 (Arp Pattern). I then get a slider that goes from 0 to 127. Looking at the matching MIDNAM file (shipped with Ardour), I see that the values are supposed to be between 0 and 5. Ardour ignores that range. The 6 values also have names in a ValueNameList, but those aren’t displayed anywhere, as far I can see. Is this also ignored? | ||||
Tags | No tags attached. | ||||
|
Ardour only uses Midnam for annotation, not to constrain parameter-ranges. Looking at the source-code, the value-names should be displayed in the verbose cursor (when hovering over an automation point). I agree that the value-names should ideally also be displayed on the Fader-Control itself. I am unsure about constraining the range (and showing it as dropdown). One can change the name-document on the fly and CCs range is not really constrained. |