Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fixes AU-plugin transfer function display.
(LADSPA & LV2 do not need this, connect&run pushes the
parameters)
|
|
|
|
Scan-only: “Iterate over all plugins. skip the ones where there's no
io-cache entry
Discover: cache new plugins info, update cache if needed.
|
|
in case $HOME/Library/Caches/Ardour4/au_crashlog.txt
is not writeable, just log to stderr.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Don’t include non-automatable params.
|
|
Ardour only queries AU writable (or read+writable)
parameters, hence announce them as such.
|
|
|
|
Ardour calls input_streams(), output_streams() to determine
if the plugin is about to be re-configured (old stream I/O count
!= new I/O count) and emit PluginIoReConfigure() if that’s true.
If the plugin has not been initialized (no format set), we can
safely assume that it will need to be reconfigured.
Forcing Audio=Midi=0 will do so.
The only time where the format is not yet set and hence the actual
channel count is still unknown) is during the first call to
PluginInsert::configure_io().
At the time of writing, this all is a NOOP anyway! The only user
of the PluginIoReConfigure() signal is the GUI to update connection
lines… and since the first PluginInsert::configure_io() happens
during insertion before the plugin is painted and subscribed to
PluginIoReConfigure(), this function could return any value.
Still 0,0 is just more appropriate than assuming mono audio in/out
and no midi.
|
|
|
|
|
|
operation is undefined. C works on all platforms
|
|
|
|
|
|
|
|
stopgap solution to allow a user to detect which plugin caused a crash during discovery.
|
|
This limit was not used or documented. The same functionality can be
performed when iterating through the results.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* forward midi-data around plugins that have no MIDI-out
* allow to insert plugins with no MIDI-input at a point with one MIDI-channel
This works because excess ports (both plugin and route) remain
unconnected and use scratch-buffers.
Tested with LV2, LXVST and LADSPA.
(AU plugins with variable in/out retain the old behavior, no bypass)
fixes http://tracker.ardour.org/view.php?id=5630
|
|
|
|
|
|
|
|
be useful
|
|
several files
|
|
Replace AU_STATE_SUPPORT compile-time define with NO_PLUGIN_STATE and make it prevent plugin state setting, preset loading, preset saving and plugin state saving. Blocks on these actions exist partially in the backend and partially in the GUI (this latter class are not absolute, and should OSC or MIDI be able to drive Plugin::save_preset() the block could be circumvented). Set NO_PLUGIN_STATE if --freebie is used at waf-configure time
|
|
|
|
git-svn-id: svn://localhost/ardour2/branches/3.0@13084 d708f5d6-7413-0410-9779-e7cbd77b26cf
|
|
git-svn-id: svn://localhost/ardour2/branches/3.0@13040 d708f5d6-7413-0410-9779-e7cbd77b26cf
|
|
Plugin::parameter_changed()->Plugin::ParameterChanged()->Plugin::parameter_changed() ...
git-svn-id: svn://localhost/ardour2/branches/3.0@13037 d708f5d6-7413-0410-9779-e7cbd77b26cf
|
|
handle these signals and mark the start end of touch/gestures for a given AutomationControl; net result is that touch automation now works for AudioUnit plugins, at least those whose GUIs send kAudioUnitEvent_{Begin,End}ParameterGesture events
git-svn-id: svn://localhost/ardour2/branches/3.0@13028 d708f5d6-7413-0410-9779-e7cbd77b26cf
|
|
automation will record parameter changes performed in a plugin GUI (#4976)
git-svn-id: svn://localhost/ardour2/branches/3.0@13026 d708f5d6-7413-0410-9779-e7cbd77b26cf
|