Lines Matching defs:run
54 control data and each plugin is `run' for a `block' corresponding
59 single value at the start of a call to the `run()' or `run_adding()'
63 `connect_port()' function below) before it is asked to run.
113 management within its run() or run_adding() functions. All new
114 memory used in run() must be managed via the stack. These
115 restrictions only apply to the run() function.
125 (4) The plugin will take an amount of time to execute a run() or
184 to run without failure and, where possible, produce a sensible
370 buffers and workspaces and to run it. */
445 locations every time run() or run_adding() is called and the data
455 run() or run_adding() is called. When working with blocks of
457 size passed to the run function as the block allocated may only
480 When present, hosts must call this function once before run() (or
482 made as close to the run() call as possible and indicates to
484 on a prompt call to run() after activate(). activate() may not be
492 handle to the particular instance to be run and the second
494 instance may run.
497 before run() or run_adding(). If deactivate() is called for a
503 within the run() or run_adding() functions (see above). */
504 void (*run)(LADSPA_Handle Instance,
508 plugin for a block. This has identical behaviour to run() except
509 in the way data is output from the plugin. When run() is used,
540 run() (or run_adding()) for the last time. This call should be
541 made as close to the last run() call as possible and indicates to