My drivers appear to install fine however I am not getting any sounds output
from the LINEOUT port...nor any other ports such as the surround_sound, etc.
The UniMixPM shows only 3 (line-in) interfaces and no outputs...not sure why.
I will spend some time looking at the unimix interface next...but I'm simply not
quite sure where to start with this one?
Tried to log a ticket through Netlabs but the user_id/pass combo in the readme
file does not appear to work...is it required that I create a new id?
Thanks!
Open a command window in \mmos2 and issue this command:-
unimix -list > unimix_controls.txt
Then open unimix_controls.txt with an editor and have a look at Control
IDs and their values.
Make sure that Playback switch(es) are Enabled (have a value of 1) and
that Volume(s) have values much greater than 1.
You may need to create a new id in order to submit a ticket/report on
netlabs.
Regards
Pete
OK, that worked.
Turns out that increasing the value of ID11: 'Headphone Playback Volume' from 39
to 42 all of a sudden turned ON the output jack....LOL...go figure.
OK, so the next question is: I have 34 controls listed, some names are
self-explanator, some are not. Is there a master list of explanations of what
these are and what the actual values represent? I suppose a decent start is the
ALSA homepage...
Regarding OS2 issues...the LBMix package does not see some of the
controls...neither does the UniMixPM application. Although, it does appear to be
a known bug of some sorts...at least that's what I gathered off of the Netlabs
page.
Thanks again Peter!
I guess the ALSA homepage is the only answer there.
> Regarding OS2 issues...the LBMix package does not see some of the
> controls...neither does the UniMixPM application. Although, it does appear to be
> a known bug of some sorts...at least that's what I gathered off of the Netlabs
> page.
>
> Thanks again Peter!
>
>
I think the only current mixer that more or less works OK is unimix.exe.
Regards
Pete
So here is a strange thing...I played some more with unimix...on a couple of
occasions it appears that just querrying up the status of the control turns it
on...so something appears to be amiss...but at least at this point in time I do
have sound...and worst case scenario I can simply activate it by querrying up
the control.