From: Takashi Iwai <tiwai@suse.de>
To: Zinx Verituse <zinx@epicsol.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: patch, and other via82xx (VT8235) capture problems
Date: Mon, 27 Oct 2003 11:41:37 +0100 [thread overview]
Message-ID: <s5hllr76jz2.wl@alsa2.suse.de> (raw)
In-Reply-To: <20031025143159.GA1176@bliss>
At Sat, 25 Oct 2003 09:31:59 -0500,
Zinx Verituse wrote:
>
> On Fri, Oct 24, 2003 at 03:59:18PM -0500, Zinx Verituse wrote:
> > On Fri, Oct 24, 2003 at 03:14:44PM +0200, Takashi Iwai wrote:
> > > At Thu, 23 Oct 2003 20:05:02 -0500,
> > > Zinx Verituse wrote:
> > > >
> > > > Any ideas on the problem with me not being able to record
> > > > if the Input Source is set to Mic?
> > > >
> > > > arecord records when it's set to Line (as it was forced, before),
> > > > and does playback as well..
> > > >
> > > > When it's set to Mic, I get no playback from a Mic (and I'm not
> > > > wanting to hook up powered output in to the jack when it's set
> > > > to Mic), but I suspect it's still Line-in, and the register
> > > > being twiddled isn't right, or needs some more setup.
> > > >
> > > > arecord waits a bit, then gives the error I mentioned:
> > > > arecord: pcm_read:1110: read error: Input/output error
> > > >
> > > > dmesg says nothing :/
> > > >
> > > > If nothing else, the settings do have to do with the actual
> > > > capture sources (idx 0 vs. idx 1), because when I set idx 0
> > > > to mic, it can't record, but idx 1 can, and when I set idx 1
> > > > to mic, it can't record, but idx 0 can. When both are set
> > > > to mic, neither can record.
> > >
> > > sorry, could you elaborate this? i'm confused.
> > > did you try hw:0,0 and hw:0,1, right?
> > >
> >
> > Yeah, hw:0,0 fails when Input Source idx 0 is set to Mic,
> > and hw:0,1 fails when Input Source idx 1 is set to Mic.
> >
> > >
> > > Takashi
> > >
> >
>
> I have more to report on this issue:
> When I was recording with 'Line' selected as the 'Input Source',
> 'Mic' was the selected recording device, and 'Line' was completely
> silent. Also, I have noticed that if I'm playing something on
> hw:0,0, then hw:0,1 fails like recording does. However, if I try
> to play two things to hw:0,0, it works. And if I try to play
> something to hw:0,1 while hw:0,0 is closed, it also works.
well, playing hw:0,0 and hw:0,1 is different from capture.
hw:0,0 is the multi-play device (DXS channels) while hw:0,1 is the
multi-channel play device for 5.1 outputs. and you cannot access to
both devices at the same time, anyway.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-27 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 4:48 patch, and other via82xx (VT8235) capture problems Zinx Verituse
2003-10-23 16:47 ` Takashi Iwai
2003-10-24 1:05 ` Zinx Verituse
2003-10-24 13:14 ` Takashi Iwai
2003-10-24 20:59 ` Zinx Verituse
2003-10-25 14:31 ` Zinx Verituse
2003-10-27 10:41 ` Takashi Iwai [this message]
2003-10-27 21:35 ` Zinx Verituse
2003-10-28 18:32 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hllr76jz2.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=zinx@epicsol.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox