|
|
20240124_22-21_ardour-dbg-8.2.85_master_warmy_dsp-load.png (19,357 bytes) 20240124_22-35_ardour-dbg-8.2.85_modded_warmy_dsp-load.png (19,072 bytes) audio_device_config.png (32,905 bytes) |
|
|
I will try to make a PR in Github with some code changes for a possible solution but any comments or guidelines that might be helpful for that are welcome. |
|
|
Can you check that when you use automation, rather than manual changes, this is not an issue? |
|
|
That is an interesting find. It'd be great to track down where those duplicate calls originate from. |
|
|
Hi x42, thanks for replying. I just did the test with the automation thing and yes, is an issue, it has the same behavior. Also, I forgot to mention that the issue is not present only when using plugin internal GUI but also when using Ardour inline controls for a plugin parameter, but in this case the methods called between host and plugin have not the exact same sequence. I did a dirty stack trace analysis for each plugin method call from ardour when a parameter is changed, maybe I could do it better so we can understand which core method or something like that is responsible of each plugin method call. First of all, there are plenty calls to "normalizedParamToPlain" for the same value, so maybe a possible solution could be a kind of mapping where to store the plain value if we already have it. If not, we do the call, but only one time. |
|
|
So the issue here is that various UI elements in Ardour request parameter conversion (interface_to_internal, internal_to_interface) ? normalizedParamToPlain is usually cheap, some basic math, at most a few CPU instructions. Except with yabridge, there is a context switch, which can introduce significant overheard. |
- Anonymous
