From: Philippe C. <la-...@or...> - 2012-09-30 12:45:23
|
Le mardi 18 septembre 2012 à 19:39 +0930, Jonathan Woithe a écrit : > 1) Standard control methods are used at the hardware level. In this case > we would need someone to construct a device-specific mixer along the > lines of what's been done for the Saffire interfaces. Such a mixer can > label the controls and arrange them physically in a way which correlates > well with the physical device. > > ... > > Since someone's said that the generic DICE mixer works with this TC > interface I suspect option 1 is applicable. Note that "generic mixer" > here refers to a mixer module which uses information supplied by the device > to construct a mixer window. Because this is fully automatic and relies > solely on the control enumerations provided by the device, the result is > sometimes not entirely intuitive to use (eg: control names may be confusing, > the GUI layout may not be logical, and so on). Having said that, there are > some devices where the generic mixer does a fine job - it all comes down to > the information supplied by the interface. > > Having said all that, if someone were to implement a device-specific mixer > for the TC interfaces we would welcome it with open arms. > > Regards > jonathan Hi Ludovic, Have you a particular device in mind (your own one, I presume) ? If so, as a first evaluation, you may send me the output of the following command $ test-dice-eap -c 1 --port=fw1 If things work, possibly I could implement something, provided you are ready to send me more complete outputs (and probably to set up one times your device on an other OS - mean Windows or Mac OS). Regards, Phil -- Philippe Carriere <la-...@or...> |