At the risk of being flamed for not investigating enuf I'd like to say I've spent the better part of 2 days trying to resolve this issue, mostly on Puppy Linux forums. No luck!

I have Skype 2.0.0.72 static download on Puppy 4.2.1, frugal install on a usb stick. That OS does not use PulseAudio and has no built in sound recorder to test with. I have set the AlsaMixer settings as recommended and tried every Skype option for Sound In but get only some hums and clicks after a test call in the Default setting. The Ringing and Sound Out work fine.

I am hoping someone out there has the same setup and can lead me to the key to this frustrating problem.

Thanks.

Maybe try this? If succeeds please post a brief report to renew its currency. You're certainly not the first report of confounded mic with ol' 2.0.

Best wishes

chriswozzie;

Thanks for the reply. Being a Linux newbie tho I need to ask a few questions re: the script. Here is are 2 segments of it:

#a ctl device to keep xmms happy
ctl.pasymed {
type hw
card 0
}

In above I assume I type as root user "ctl.pasymed" > Enter > "hw" > it asks me something about a card so I > "0"?

#for aoss:
pcm.dsp0 {
type plug
slave.pcm "asymed"
}

And in this example I type "plug" > then I'll be responding to something about "slave.pcm" so I'll type "asymed"?

And finally will my sound card parameters be different than the examples given? If so where would I find mine to use instead?

Sorry to have to ask something so basic but that is where I am.
Fred

Hi again Fred!

Sorry no-one else's jumped in to help with your follow-up Q.
That CODE is actually the ALSA config language text needed to change/ create the ~/.asoundrc file in order to make the mic work. Each named and bracketed stanza is an element definition. You'd be right in thinking, like in shell-script, lines beginning with # are comments.
So, as regular user, use an textfile editor to open ~/.asoundrc (which will create it if it doesn't exist), and paste that at the end. (If not blank, best check if - & probably comment out - earlier stuff that does dmix-ing.)
(Btw, as explained later there, ~ is a shell-symbol for your home directory.)

I've not mucked with ALSA enough to be the one to ask whether its "hw:0,0" is a virtual or real card, but dmix etc is software-mixing (as one'd expect with HDA). (Could compare with .asoundrc in typical (d)mix-ing Skype with other audio (mixed by PA) config if you like.) Jinn explicitly offered this for others, so I suspect that's universal, and no-one's voiced problems, plus no harm to 'give it whirl'.
Deloptes or maybe Dâniel Fraga/someone could likely sort things if there's a problem and you come back with some hw details.
(Failing that, upgrade to 2.1 beta and ask in ALSA f/b thread if problem?)

Fingers crossed!

Chris

PS I should also said if successful, please also mark this thread as [solved], to delineate open issues / useful readings, plus encourage others to get into the habit of doing likewise.

Chris;

I really appreciate your help but unfortunately the hack did not solve my problem. It did create an "asymed" option in Skype sounds but using it in Sound In did not make the recording function.

I suspect the answer may be in the actual parameters of the script relative to my computer. I just copied and pasted the thing verbatim to an .asoundrc file I created but I don't have the Linux knowledge to be able to modify it, if that is the problem.

Drats ;(

My suggestions of things to try would be
a) turn off "auto adjust mixer level" in Options.. : Audio

b) replace .asoundrc with the basic dmix-ing (as used with PA above)

c) try 2.1 - the ALSA implementation is not buggy AFAIK

else people are going to need stuff like from "lsmod | grep snd", "lspci -vvk", "uname -a" and alsa version# etc to make suggestions.

HTH