View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0009533||ardour||bugs||public||2023-11-11 20:34||2023-11-18 22:56|
|Platform||Apple Macintosh||OS||MacOS||OS Version||10.12 or later|
|Summary||0009533: Automation Inconsistency|
|Description||In the attached file, the pitchbend is set at neutral for bars 1-2, and then set to maximum for bars 3-4. When played from the beginning, it sounds as expected. However, if after playing past measure 3, playback is resumed at measure 2, then measure 2 will sound with the pitchbend at maximum (the last value that was played), rather than at neutral (the last value that was set in the timeline).|
Whenever resuming playback, automatable parameters ought to be set either to the last value that was set in the timeline, or to neutral if there was no previous setting in the timeline.
automation-inconsistency.zip (11,887 bytes)
||does this still happen if you set the automation style for pitchbend as "interpolated" ?|
||It happens in both "Discrete" and "Linear" modes.|
||This is a manifestation of a more general phenomenon (which could justifiably be seen as a problem): Ardour plays MIDI sequentially and doesn't in general try to restore the track state to what it would have been if it had played from the start. If there are patch changes in a track, for example, this can lead to the wrong "instrument" being played. (I haven't checked if the same problem arises with all CC messages, but if it doesn't, that would be a (welcome) inconsistency.)|
we actually have the internal "technology" to do the "catch up with current total MIDI state" now.
the actual problem is deciding when to emit any MIDI messages. for example, in the specific case of this bug, doing it on completion of a locate is potentially wasteful, because the user may just locate again. they may also edit the information that is earlier than the current playhead position, which will make the MIDI sent be inaccurate. that would suggest doing it just before we start rolling (playing), but it can be tricky to ensure the ordering of messages is 100% accurate.
|2023-11-11 20:34||erdavis7||New Issue|
|2023-11-11 20:34||erdavis7||File Added: automation-inconsistency.zip|
|2023-11-11 20:34||erdavis7||Tag Attached: automation|
|2023-11-14 19:39||paul||Assigned To||=> paul|
|2023-11-14 19:39||paul||Status||new => feedback|
|2023-11-14 19:39||paul||Note Added: 0028331|
|2023-11-15 02:40||erdavis7||Note Added: 0028332|
|2023-11-15 02:40||erdavis7||Status||feedback => assigned|
|2023-11-18 22:06||DonJaime||Note Added: 0028338|
|2023-11-18 22:56||paul||Note Added: 0028340|