Yair K. wrote: > On Wednesday 23 July 2008 16:22:58 you wrote: > >> Hi, >> >> The attached patch changes the way ossxmix polls for new vmix engines a >> bit, so that it uses update_counter: >> A. Make vmix use the MIXF_DYNAMIC flag when vmix engine group is created. >> B. Have ossxmix poll update_counter of groups with MIXF_DYNAMIC flag. If >> it's different from the previous, reload. >> I already applied your previous patch so could you review the hg version and to send me the new changes. > Another option I've been thinking of, instead of reusing MIXF_DYNAMIC, is to > add a separate MIXF_VMIX flag to mark controls made by vmix. This is probably > better from the previous idea, since it can also be used by mixer program who > wish to avoid the vmix stream controls (so far, all of them except ossxmix), > and I can't think of other uses which adds controls dynamically. > Better way might be using a MIXF_HOTPLUG flag. For groups it means that new controls/groups might be added (or removed) to the group any time. The root group (MIXT_DEVROOT) is an example of such group. New controls/groups may appear under it for examole when vmix is attached to the device.
For controls this flag means that the control might get removed on fly. In addition we would need a MIXF_UNAVAILABLE flag to mark controls that are (temporarily) removed from the system (the mixer might show such controls as grayed out). Later the control might return back and the MIXF_UNAVAILABLE flag gets cleared. Maybe this is overkill and just makes the mixer programs too complicated. Best regards, Hannu _______________________________________________ oss-devel mailing list oss-devel@mailman.opensound.com http://mailman.opensound.com/mailman/listinfo/oss-devel
