View Issue Details

IDProjectCategoryView StatusLast Update
0005210ardourbugspublic2020-04-19 20:16
Reportertweed Assigned Topaul  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0005210: A3 doesn't retain Generic Midi Control Surface Settings after reopening a session
DescriptionA3 doesn't retain Generic Midi Control Surface Settings after reopening a session. This is what happens:
Open Ardour3 Session > Preferences > User Interaction > Control Surfaces > Generic Midi (Enabled) > Set to 'KorgNanoKontrol2' >
Verify Control surface works > Save/close Session > Reopen same session > Generic Midi Setting reverts to 'Reset All' > Control Surface does not work.

Additional InformationVerified Control Surface is routed to Midi Control in Midi Connection Manager.
TagsNo tags attached.

Relationships

duplicate of 0005396 closedjamiejessup MIDI bindings are not saved. 

Activities

nefthy

2013-04-06 11:42

reporter   ~0014818

I can confirm this.

Midi controls assigned via midi learning, are also not saved with the session and have to be reassigned every time.

paul

2013-04-06 13:13

administrator   ~0014819

nefthy: i don't have a problem with MIDI learn bindings being reloaded.

paul

2013-04-06 13:14

administrator   ~0014820

actual reported bug (binding map state not restored) fixed in git 6e485c0fc1425de78e21ea1aeec6233b136681dd and will be in the next release due out this weekend.

nefthy

2013-04-06 16:33

reporter   ~0014833

paul: I tried this several times. Here is what I did:

- Ctrl+midle click on a control
- move a fader on my BFC 2000 (also tried a BOSS GT-100)
- confirm that it works
- save the session
- restart ardour3
- load the session
- move fader and nothing happens

I suppose the bindings should be saved in the session xml file. What should they look like?

paul

2013-04-06 17:25

administrator   ~0014834

attach the session file (*.ardour) and i'll take a look

nefthy

2013-04-22 17:12

reporter   ~0014876

The Issue is fixed in the git version.

paul

2013-04-22 17:23

administrator   ~0014877

see notes. this is actually fixed in 3.1, not just git

system

2020-04-19 20:16

developer   ~0023169

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.

Issue History

Date Modified Username Field Change
2012-12-06 01:49 tweed New Issue
2013-04-06 11:42 nefthy Note Added: 0014818
2013-04-06 13:13 paul Note Added: 0014819
2013-04-06 13:14 paul Note Added: 0014820
2013-04-06 13:24 paul Relationship added duplicate of 0005396
2013-04-06 16:33 nefthy Note Added: 0014833
2013-04-06 17:25 paul Note Added: 0014834
2013-04-22 17:12 nefthy Note Added: 0014876
2013-04-22 17:23 paul Note Added: 0014877
2013-04-22 17:23 paul Status new => resolved
2013-04-22 17:23 paul Resolution open => fixed
2013-04-22 17:23 paul Assigned To => paul
2020-04-19 20:16 system Note Added: 0023169
2020-04-19 20:16 system Status resolved => closed