Trinitou

document latency handling for events

1

on Dischord someone had questions concerning latency handling for automation. At least I and @defiantnerd think we should document this better: - put the full explanation in latency.h. Some thoughts:...

proposal after some discussion on Dischord. 1. Someone reported that Bitwig and Reaper immediately call `plugin_latency->get` after `host_latency->changed` gets called from the plugin during activation - solution: allow `plugin_latency->get` to...

Remove unnecessary includes from clap.h

4

let's see if this passes the pull-request workflows... 😉 I think this removes some clutter. here is my theory: - `plugin.h` is included via `factory/plugin-factory.h` and plugin extensions (makes sense...

undo/redo extension

4

already discussed in #161 and #223 Now I found time to do a first draft. I tried to (hopefully) integrate suggestions the came from different people in those threads. Some...

PluginEntry

2

first version for a + clap::helpers::PluginEntry` - works for local plugin project (single-plugin clap, multi-plugin clap) - has the thread safety checks built-in - some basic test - some points...

Plugin factory

4

I tried to find a good solution for this common pattern and looked at various repositories how they do it. It worked well for a local repo. But not tested...

just a nitpick: the `.hh` headers are already included via the `.hxx` headers

Reopening #427

param-resolutions extension

4

see in-code documentation. If something is not specified enough, please ask/propose changes of course 👍

I wanted to derive from `HostProxy` to try out some custom host extensions. And it would be good to be able to derive from `HostProxy` myself and then pass a...