Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
(haven't built any fluidsynth plugins yet)
|
|
and a VST plugin's own GUI
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
processor:to_insert():plugin(0):get_info().type
|
|
|
|
|
|
|
|
...now that bindings alone need approx 700K and some more complex DSP
scripts are showing up 2MB is not much :(
|
|
fixes OOM with extreme automation in HP/LP.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This [hopefully] fixes jack1 zombification on session-load with large
plugin-states. Previously it was possible to block
Route::process_output_buffers().
|
|
|
|
reset synth in offline thread, queue panic on deactivate to be
called in run() after first re-activate.
Initial activation does not warrant a panic.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- fixes jittery tempo movement when snapping within large gradients.
|
|
|
|
|
|
and also allow immediate work during use latency-compute runs.
At session load, Ardour calls a plugins "set default" state (GUI thread).
Some plugins may schedule work during state-restore. Ardour immediately
proceeded to restore the actual session plugin state without processing
the already scheduled work and without calling run() for a plugin
to apply state synchronously.
|
|
|
|
|