|Anonymous | Login | Signup for a new account||2018-03-22 08:25 PDT|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007443||ardour||bugs||public||2017-08-08 10:17||2017-08-16 10:54|
|Platform||Intel x64||OS||Ubuntu 16.04||OS Version||Ubuntu 16.04|
|Target Version||Fixed in Version|
|Summary||0007443: MIDI Automation (CC) not being read by Ardour 5.10|
|Description||Clear on MIDI automation does not allow new automation to play.|
|Steps To Reproduce||Start a new session, new MIDI track (zynAddsubFX), create a MIDI region, add some notes, on the track select [A]->Controllers->64-79->select 72/Channel 1 - add some automation points, play - all goes well. Then right click on the automation track and select Clear - then put some new points on the automation track - play will not pick up the new points. When I press stop then the automation picks up the last point, ie where it should be, and indeed, if i move the playhead the automation is right at the point at which i let go the mouse, if that makes any sense.|
|Additional Information||Logs - default log level:|
[ERROR]: LADSPA: cannot load module "/usr/lib/ladspa/sifter_1210.so" (/usr/lib/ladspa/sifter_1210.so: undefined symbol: q_sort)
[ERROR]: LADSPA: cannot load module "/usr/lib/ladspa/ladspa_guitarix.so" (/usr/lib/ladspa/ladspa_guitarix.so: undefined symbol: _ZN4sigc9slot_baseC1EOS0_)
[WARNING]: Ignoring LV2 plugin "LV2 Convolution Mono" because its buffer-size requirements cannot be satisfied.
[WARNING]: Ignoring LV2 plugin "LV2 Convolution Mono=>Stereo" because its buffer-size requirements cannot be satisfied.
[WARNING]: Ignoring LV2 plugin "LV2 Convolution Stereo" because its buffer-size requirements cannot be satisfied.
[WARNING]: Ignoring invalid LV2 plugin http://gareus.org/oss/lv2/onsettrigger#bassdrum_stereo [^]
[WARNING]: Ignoring LV2 plugin "Big Meter" because its buffer-size requirements cannot be satisfied.
[INFO]: Loading bindings from /opt/Ardour-5.10.0/etc/ardour.keys
harvid version: 802
[INFO]: Loading menus from /opt/Ardour-5.10.0/etc/ardour.menus
[INFO]: Loaded custom session defaults.
[INFO]: Loading 88 MIDI patches from /opt/Ardour-5.10.0/share/patchfiles
[INFO]: Loading history from /home/path/to/Ardour5_Projects/DeeBug/DeeBug.history
[INFO]: DeeBug: no history file "/home/path/to/Ardour5_Projects/DeeBug/DeeBug.history" for this session.
|Tags||No tags attached.|
|Fixed in git (nightly builds)|
Hi, I built from git last night - seems that the midi automation is being followed now (after a clear), which is great (and I like the new play/off feature) - but the slider doesn't follow the automation, which I like to see (rather than just hear) it moving about - is this your experience with the latest builds?
Version is Ardour 5.10.525
"Atmospheres and Soundtracks"
Intel 64-bit - debug
Ardour5.10.525 (built using 5.10-525-ga1143a0 and GCC version 5.4.0 20160609)
That's my experience too. Still not 100% sure of the correct approach for the fader. If we just go back to have it follow the CC data, it's just a reversion of a commit from several weeks ago.
The issue is that the fader actually sends realtime CC messages when adjusted. This doesn't work well during automation playback so something needs to change, at least a bit.
Thanks for the reply, not sure about the etiquette of discussing it here, but perhaps the fader could be greyed-out (and moving) while there are CC messages playing? I wouldn't expect to be able to move the slider about manually when there is automation going on, so perhaps that could be a compromise?
|2017-08-08 10:17||Caesura||New Issue|
|2017-08-11 10:14||paul||Assigned To||=> paul|
|2017-08-11 10:14||paul||Status||new => confirmed|
|2017-08-13 16:06||paul||Note Added: 0019973|
|2017-08-16 10:35||Caesura||Note Added: 0019980|
|2017-08-16 10:38||paul||Note Added: 0019981|
|2017-08-16 10:54||Caesura||Note Added: 0019983|
|Copyright © 2000 - 2018 MantisBT Team|