5 * even though it is long try to stick to the prefix "dparam" for the whole library
6 * e.g. avoid namespace clashes with "dataprotocol" which is using "dp" as well :-(
7 * use a new namespace "ctrl" for control
8 * resolve g_return_if_fail() into GST_WARNING and return()
9 in cases where the caller has to handle the problem
11 GST_TYPE_DPSMOOTH to GST_TYPE_DPARAM_SMOOTH
12 GST_TYPE_DP_LININT to GST_TYPE_DPARAM_LININT
13 there seems to be nobody using them, as they still look unfinished
14 * move modes into extra modules
15 dparam_mode_synchronous
16 dparam_mode_asynchronous
18 * split dparam manager api (like e.g. GConf does it)
19 * plugin api : GstCtrlManagerServer
20 * application api : GstCtrlManagerClient
21 * remove "value-changed" signal from DParam?
22 * one can connect to e.g. "notify::value-double" as well
23 * dparam update callback needs to pass more info
24 * GstElement as the first arg
25 * GstDPram as the second arg
28 * state of unitconvert
29 * state of sychronous params
31 if element_sampling_rate is 44100 and dpman_rate is 22050, dparams are updated twice a second
34 * concept for global, voice params
35 one plugin instance can repeate the processing for the same input, but with
36 different parameter sets (sound synthesizers, effects)
37 * based on gobject params, so that e.g. the GUI can connect to "notify:param"
38 events and update the GUI
39 * implement timelined dparams via queues
40 * the queue contains dparams and timestamps
41 * GST_DPARAM_DO_UPDATE() checks the head of the queue for events that are due now