[EMAIL PROTECTED] wrote:
> Hi again,
>
> the biggest problem with kmix is that it doesn't even has the possibility to 
> form a tree layout. If it could, the dicussion here wouldn't go so long :P
>
> The problem I see is, that even not so experienced users want to for example 
> choose the recording source (or activate spdif, micboost and similar), which 
> is supported by the kmix API with that red button below the sliders. If I 
> really drop every other control but those with with the MIXF_MAINVOL etc. 
> flags set, the whole point about writing this backend is.. well useless. The 
> goal of the backend was to write something so that average users can very 
> well live without having to work with ossxmix (and its tons of controls) at 
> all. Maybe the OSS devs should go a step further and add more to the (I call 
> it this way now) MIXF_MAINVOL etc. (simplified) layer of the mixer API, by 
> adding a flag like "MIXF_COMMONCTL" or similar.
>   
The point is that all the controls an ordinary user will ever need to 
use will (sooner or later) be marked by MIXF_MAINVOL/etc. These 
important controls will be all that is needed to select recording 
sources/etc.

The method to be used for (say) recording source control just may be 
different depending on the device. It may be something like line.rec or 
a MIXT_ENUM control like rec1.src={"line" | "mic1" | "mic2" | "cd" | ... 
| "digital"}. There may even be multiple recording source controls 
(rec1.src, ..., recN.src).

It may not be possibe or easy to convert existing mixer applications to 
use this approach. In such case it might be better to create a 
replacement from scratch.

Btw, The line.rec model comes from the controls that have been 
automatically generated based on the "legacy" (OSS3) mixer API. The 
conversion logic will
create a group called "line". Then it will create a mono/stereo slider 
with empty name and a ONOFF control with name "REC" under that group. 
After all legacy controls there will be a MIXT_MARKER entry which 
indicates that this rule is no longer valid for subsequent controls.

Best regards,

Hannu
_______________________________________________
oss-devel mailing list
oss-devel@mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

Reply via email to