View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006633 | ardour | bugs | public | 2015-10-09 14:24 | 2015-10-19 10:35 |
| Reporter | z33ky | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 4.X git (version in description) | ||||
| Summary | 0006633: LV2 (de)activate always called when stopping playback after scrolling once | ||||
| Description | When you scroll once during playback, Session::pending_locate_flush is set to true, by the call start_locate (ev->target_frame, true, true, false); in Session::process_event, but this flag is never cleared, causing Ardour to call LV2 deactivate() and activate() on each subsequent stop. When opening a new session and just toggling play/stop and scrolling while stopped this does not happen. This seems like unintentional behaviour in Ardour, although I'm not sure what behaviour is expected. | ||||
| Additional Information | Ardour commit 268d53f5028c222d1f3b5d91b186eba52c5db6c8 | ||||
| Tags | No tags attached. | ||||
|
|
While the way this is achieved seems odd. The overall behavior sounds correct to me. On activate() a plugin must reset the its internal state[1]. When locating to a different position on the timeline it is usually good to not keep information or sound of the previous location. So the bug is rather that this de/re-activate calls is not done consistently. [1] http://lv2plug.in/doc/html/group__lv2core.html#ad34d59efaed8faaf8a05a4c375f62415 |
