Lines Matching defs:run
55 control data and each plugin is `run' for a `block' corresponding
60 single value at the start of a call to the `run()' or `run_adding()'
64 `connect_port()' function below) before it is asked to run.
114 management within its run() or run_adding() functions. All new
115 memory used in run() must be managed via the stack. These
116 restrictions only apply to the run() function.
126 (4) The plugin will take an amount of time to execute a run() or
185 to run without failure and, where possible, produce a sensible
371 buffers and workspaces and to run it. */
446 locations every time run() or run_adding() is called and the data
456 run() or run_adding() is called. When working with blocks of
458 size passed to the run function as the block allocated may only
481 When present, hosts must call this function once before run() (or
483 made as close to the run() call as possible and indicates to
485 on a prompt call to run() after activate(). activate() may not be
493 handle to the particular instance to be run and the second
495 instance may run.
498 before run() or run_adding(). If deactivate() is called for a
504 within the run() or run_adding() functions (see above). */
505 void (*run)(LADSPA_Handle Instance,
509 plugin for a block. This has identical behaviour to run() except
510 in the way data is output from the plugin. When run() is used,
541 run() (or run_adding()) for the last time. This call should be
542 made as close to the last run() call as possible and indicates to