View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003948 | ardour | bugs | public | 2011-04-06 20:38 | 2020-04-19 20:15 |
| Reporter | pablomme | Assigned To | paul | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0-alpha4 | ||||
| Target Version | 3.0-beta2 | ||||
| Summary | 0003948: "latency" plugin parameter resets to 16 every time | ||||
| Description | I've been trying to build a template session on ardour 3 alpha 4, imitating my previous 2.8.x template, but replacing all ladspa plugins with lv2 equivalents. What I'm seeing is that SWH's multiband EQ plugin (and possibly others) has a configurable "latency" parameter, with a default value of 16ms, which: - resets itself to 16ms if I try to set it to 0 - if I set it to >0 (e.g., 1ms), the change appears to stick, but then it resets itself again when I reload the session I hear a fairly noticeable latency in the output with respect to the input, and I suspect that this "latency" parameter being ignored could be the reason. I can't be sure, but I think that the 'latency' parameter is not (entirely) external to ardour; sorry for the bug report if it is! | ||||
| Tags | No tags attached. | ||||
|
|
there is a bug here, but you're misunderstanding the meaning/purpose of this dialog. the bug is that the dialog does not correctly redisplay newly set values. but the dialog doesn't allow you to get rid of actual latency. its there for two purposes: (1) a way to see what plugins are actually reporting as their internal latency (2) for plugins that are latent but that report zero (there are quite a few), it allows you to set a non-zero value so that Ardour knows to compensate for it. the plugin you're using is latent, and reports the right value more or less. you can't do anything to get rid of that latency. the dialog needs some work to make all this clear. |
|
|
I was indeed misled by the dialogue - I could change the value, so I assumed I was changing the behaviour of the plug-in (I thought the equalizer might have some algorithm to approximately deal with low freqs to reduce latency). From your explanation I don't know if there is a way to distinguish non-latent plugins from latent plugins which do not report a latency; probably not. In any case, the modal dialogue just needs some explanatory text like "This plugin reports a latency of %s. Change it here only if you know that this is wrong:", possibly with a different wording for zero and non-zero reported latencies (and for non-latent plugins if they can be identified). About the bug in question, is it just a display issue, or is it perhaps also not saving/restoring the value to/from the session file? I noticed that after changing the latency ardour did not acknowledge the session as modified (with a '*' in the titlebar), so I suspect it might not be. Many thanks for your help! |
|
|
The latency value should be saved in the session file now, at least. |
|
|
please confirm if possible. |
|
|
Yup, the latency value is correctly saved and loaded with the session. Thanks! |
|
|
see notes |
|
|
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. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2011-04-06 20:38 | pablomme | New Issue | |
| 2011-04-06 22:44 | cth103 | cost | => 0.00 |
| 2011-04-06 22:44 | cth103 | Target Version | => 3.0-beta1 |
| 2011-04-08 17:04 | paul | Note Added: 0010518 | |
| 2011-04-09 00:07 | pablomme | Note Added: 0010523 | |
| 2011-07-15 00:18 | cth103 | Note Added: 0011131 | |
| 2011-07-18 18:05 | paul | Note Added: 0011157 | |
| 2011-07-18 18:05 | paul | Status | new => feedback |
| 2011-07-19 19:46 | pablomme | Note Added: 0011167 | |
| 2011-11-15 15:59 | cth103 | Target Version | 3.0-beta1 => 3.0-beta2 |
| 2011-12-05 19:46 | paul | Note Added: 0012306 | |
| 2011-12-05 19:46 | paul | Status | feedback => resolved |
| 2011-12-05 19:46 | paul | Resolution | open => fixed |
| 2011-12-05 19:46 | paul | Assigned To | => paul |
| 2020-04-19 20:15 | system | Note Added: 0022520 | |
| 2020-04-19 20:15 | system | Status | resolved => closed |
