On Thu, Sep 04, 2008 at 05:29:08AM +0000, Jacob Meuser wrote:
>
> curious, what makes you think it's line3?
came to the conclusion because if i set, like, mix3 to have a volume
of something high, and mix4 to something lower, and then change
the source for line3 between them, i can hear that volume change.
also if i outputs.line3.mute=on, sound stops; if i 'off' it, comes back.
couple other things i don't remember right now; didn't really have the
liberty of burning wallclock on sound on the worklaptop these past days :(
> if you do:
>
> $ mixerctl outputs.mix2=200
> $ mixerctl outputs.headphones.source=mix2
> $ mixerctl outputs.line.source=mix2
>
> then can you hear audio on the line-out or headphones jack?
unfortunately not
> I suggest this because your mixerctl is showing outputs.line3.source=mix2,
> and you say line3 is giving you output. this says to me that mix2 is
> giving output. sorta corresponds to my realtek 882 as well.
i wouldn't be super surprised if i didn't understand all the widget
interconnect stuff; i was thinking it went something like:
dac* -> mix* -> line*
inputs.mix2.dac.mute=off
inputs.mix3.dac2.mute=off
inputs.mix4.dac3.mute=off
inputs.mix5.dac4.mute=off
inputs.mix9.dac6.mute=off
if i tell line3 to have a source of mix3 and i mute dac3 in the above, sound
stops; if i tell line3 to have a source of mix5 and i mute dac4, it stops, etc
so i it seemed to me that the mix[2-59] wasn't really the end output device
but rather a stream that wants to be pointed at one; essentially anything
i use as a source for line3, if i look at the connection relationship for
that source on back to the dac, any mute or volume changes in that chain
has effect on what i hear.
when i do the same for any other output device (speaker,speaker2,headphones,
any of the other lines ("", 2, 4), or mic (all set to direction output)),
i get nothing anywhere for any combination of the one pair of headphones
plugged in -- at least assuming i've muted line3 is when i get nothing.
i have not tried two pairs of headphones yet to see if that would do
anything...
> > the codec itself supports sample rates only "down to" (*cough cough
> > cough*)
> > 44100 (that's bullshit; thanks realtek or apple or whoever).
>
> aucat(1) can resample. check the manual on -current.
hooray
> > it would still be nice to know if the reason i can't get sound in any case
> > other than headphones in the linein jack is because i suck at mixerctl, or
> > because of something a bit more extenuating than that.
>
> azalia devices such as yours are more complex than what you may be
> used to. in particular, it supports i/o routing and jack sensing.
way more
i'm used to GUS, PAS and AWE.
> I suppose there could also be a bug or quirk somewhere. maybe also try
> twiddling outputs.[line|headphones].[boost|mute] in mixerctl???
at this point i've got the impression that i've exhausted everything i
can; but i'm not asserting that i FOR SURE have done so; like you mention,
they're complicated -- part of my problem was i was never able to really
believe i defined for sure for myself what the actual function and heirarchy
and relationship of these widgets is.
for example, i don't know if 'mix4' is a seperate instance of a 'mix'
object/bus
from 'mix5', or rather, if there's only one single mix object and the various
numbered entities are simply something like an individual unique "cable" with
a
volume knob on it (what gave me that impression is how the 'mixN.dacN' stuff
seems to show up, and it doesn't seem like 'dac3' is any different than 'dac4'
so long as i'm using the correct 'mixN' that corresponds to whichever dacN...
--
jared
