View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005296 | ardour | bugs | public | 2013-01-22 11:57 | 2020-04-19 20:16 |
Reporter | nettings | Assigned To | x42 | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0005296: "motorized" flag for MIDI controllers is not stored in session or user preferences | ||||
Description | The "motorized" flag in Preferences->User Interface->Generic MIDI is very important for users of BCF2000 and similar devices, because otherwise Ardour3 easily loses track of its faders and then goes into "latch" mode, where updates are suppressed unless the fader has passed over Ardour's current value, to avoid jumps. This latch feature is pretty undesirable on motor faders, "motorized" switches it off. Unfortunately, this flag is not stored in the session prefs, which from a UX point of view leaves you with a broken MIDI controller on session reload. | ||||
Steps To Reproduce | Check "Preferences->User Interface->Generic MIDI->motorized". Save the current session. Quit Ardour. Restart, reload session. Observe how the motorized flag is now unset. | ||||
Tags | No tags attached. | ||||
Users sponsoring this issue | ||
Sponsors List |
Total Sponsorship = US$ 10 2013-09-17 15:44: jamiejessup (US$ 10) |
---|
|
I am also experiencing this behaviour as well. In addition, The controller map that is being used is also not saved. Therefore, every time I open a saved session I have to re-initialize the midi controller settings. This is with RC2 (rev 14024). |
|
still a problem with 3.2 |
|
Creating a .map file solves this problem, at least with my workflow. Still a bug however, but this workaround keeps me presumably "grooving". |
|
Still an issue with 3.4 |
|
bumping this, as it is still not fixed in 4.2. it's a major hassle for me when i use ardour4 for live shows, _especially_ when something goes wrong and you have to start a session in a hurry. it's hard to remember to always apply that setting manually after loading, and kind of tedious... |
|
fixed in Ardour 4.2-47-gb8b6f61 |
|
to clarify, the setting (as well as the bindings) are per session (and not in preferences) |
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-01-22 11:57 | nettings | New Issue | |
2013-01-22 11:57 | nettings | cost | => 0.00 |
2013-01-22 22:00 | nettings | Relationship added | related to 0004704 |
2013-03-08 20:47 | jamiejessup | Note Added: 0014687 | |
2013-06-15 20:26 | otherone23 | Note Added: 0015001 | |
2013-06-29 09:45 | otherone23 | Note Added: 0015066 | |
2013-06-29 09:45 | otherone23 | Note Edited: 0015066 | |
2013-09-17 15:23 | jamiejessup | Note Added: 0015331 | |
2013-09-17 15:44 | jamiejessup | Sponsorship Added | jamiejessup: US$ 10 |
2013-09-17 15:44 | jamiejessup | Sponsorship Total | 0 => 10 |
2015-08-19 20:11 | nettings | Note Added: 0017063 | |
2015-08-19 22:20 | x42 | Note Added: 0017069 | |
2015-08-19 22:20 | x42 | Status | new => resolved |
2015-08-19 22:20 | x42 | Resolution | open => fixed |
2015-08-19 22:20 | x42 | Assigned To | => x42 |
2015-08-19 22:24 | x42 | Note Added: 0017070 | |
2020-04-19 20:16 | system | Note Added: 0023185 | |
2020-04-19 20:16 | system | Status | resolved => closed |