'Twas brillig, and pl bossart at 20/08/09 20:37 did gyre and gimble: >> Just wanted to say that I'm working on a module for unrelated reasons that >> would probably come in handy here. >> >> While some other modules (bluetooth?) may load this module internally >> as/when they need it, I'm working on a system that would let you define >> modules to load via a GUI and associate them with sinks/sources etc. that >> are not currently plugged in (it maintains a history of the sinks/sources >> it's seen in the past). >> >> This GUI would allow you to e.g. define a loopback module definition that >> works with Source A and Sink B. The loader module will automatically try and >> load any defined and active module which are not currently loaded every time >> a new sink/source is detected. >> >> This structure shoudl be ideal for people wanting to define custom "pass >> throughs". > > Yes this would be nice. In my tests I load the module from a file, and > this is a hard-coded configuration. Having the ability to recall which > sinks and sources need to be connected would be quite useful indeed. > Didn't think my week-end hack would be associated with a GUI anytime > soon.... Yeah. "soon". For various values of "soon" :p Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mandriva Linux Contributor [http://www.mandriva.com/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
