View Issue Details
|ID||Category||Date Submitted||Last Update|
|0007765||bugs||2019-06-12 21:15||2019-06-12 22:28|
|Platform||Windows 10||OS||Windows||OS Version||10|
|Fixed in Version|
|Summary||0007765: Modulation wheel affects playback of previously recorded tracks|
|Description||The position of modulation wheel on your MIDI keyboard before pressing play should not affect playback (unless you are recording), but it does.|
|Steps To Reproduce||1. Create a MIDI track with the built-in General MIDI Synth instrument|
2. Set the modulation wheel on your MIDI keyboard to zero (all the way down)
3. Record some MIDI on the new track
4. Stop recording and unarm the track
5. Set the modulation wheel on your MIDI keyboard to 127 (all the way up)
6. Play back the previously recorded MIDI
|Additional Information||Expected behavior: Track should play back with no vibrato (as recorded)|
Actual behavior: Track plays back with heavy vibrato (to match the current position of the modulation wheel).
This unexpected behavior is especially apparent when working with multiple tracks, some that use no modulation wheel (like piano) and others that make use of the modulation wheel (like brass). Heavy vibrato on piano sounds very strange.
|Tags||No tags attached.|
It's not only the modulation wheel, but all event messages. Ardour does not re-play MIDI when the transport locates. That is a known long-standing issue.
It's a non-trivial issue. In theory every "locate & play" would have to reset the synth and replay all events prior to the transport target position. In practice it **might** suffice to remember the most recent program-change and every control-change. Then there's also the issue with active notes, e.g. drone-sounds. Should the note-on be replayed if you start rolling in the middle of the note? etc