From: Takashi Iwai <tiwai@suse.de>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: alsa-devel@alsa-project.org,
Giovanni Maruzzelli <gmaruzz.lists@gmail.com>
Subject: Re: dsnoop do not works on snd-hda-intel
Date: Mon, 17 Sep 2007 14:55:58 +0200 [thread overview]
Message-ID: <s5hd4whe9i9.wl%tiwai@suse.de> (raw)
In-Reply-To: <200709170732.46430.maximlevitsky@gmail.com>
At Mon, 17 Sep 2007 07:32:46 +0200,
Maxim Levitsky wrote:
>
> On Monday 17 September 2007 07:21:03 Giovanni Maruzzelli wrote:
> > Hi all,
> >
> > I hope someone can give me an hint on this problem, that is stopping me.
> >
> > On my new laptop (asus f5v) dsnoop do not works, neither I can record
> > at the same moment with more than one application. The second
> > application that want to use the dsnoop, fail to open it.
> >
> > I'm using Ubuntu 7.04 fully updated.
> >
> > lspci gives:
> > 00:0f.0 Audio device: Silicon Integrated Systems [SiS] Azalia Audio Controller
> >
> > cat /proc/asound/card0/codec#* | grep Codec gives:
> > Codec: Realtek ALC660-VD
> > Codec: Motorola Si3054
> >
> > I've upgraded driver, lib, and utils to 1.0.14 but it do not helped.
> >
> > I've put at the end of /etc/modprobe.d/alsa-base
> > options snd-hda-intel model=3stack-660
> >
> > I can always reproduce the behavior, for eg:
> >
> > root@ubuntu-lap:~# arecord -Ddefault ciao.wav &
> > [1] 6923
> > root@ubuntu-lap:~# Recording WAVE 'ciao.wav' : Unsigned 8 bit, Rate
> > 8000 Hz, Mono
> >
> > root@ubuntu-lap:~# arecord -Ddefault ciao2.wav &
> > [2] 6926
> > root@ubuntu-lap:~# ALSA lib pcm_dsnoop.c:606:(snd_pcm_dsnoop_open)
> > unable to open slave
> > arecord: main:545: audio open error: Invalid argument
> >
> > [2]+ Exit 1 arecord -Ddefault ciao2.wav
> >
> > I can give any additional info is needed.
> >
> > Thank you all in advance,
> >
> > Giovanni Maruzzelli
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
>
> Hi,
>
> I was also hit by this problem
>
> To fix this you need to open /usr/share/alsa/pcm/dsnoop.conf
> and change
>
> @args.SUBDEV {
> type string
> default -1
>
> to
>
> @args.SUBDEV {
> type string
> default 0
>
> I was told that this is a feature of alsa, not bug, I don't know.
>
> the above will make dsnoop to record from hw:0,0
>
> Also, I bet that your hardware can record more that one stream a time.
> So you can also try recording from hw:0,1 or hw:0,2
>
> you can check how many streams can be recording at same time in /proc/asound/Intel/pcm0c/info
> look at subdevices_count
>
> Each stream can have its own input source, so check your mixer to make sure that
> each stream records what you want, eg: records from same source, or not,
> is enabled or not, and has enough gain.
Ah, actually it should be counted as a bug.
The -1 works well for the devices with a single substream but not for
the devices with multiple substreams. Should be 0 for dmix/dsnoop.
I'll fix alsa-lib HG tree now.
thanks,
Takashi
prev parent reply other threads:[~2007-09-17 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 5:21 dsnoop do not works on snd-hda-intel Giovanni Maruzzelli
2007-09-17 5:32 ` Maxim Levitsky
2007-09-17 5:53 ` Giovanni Maruzzelli
2007-09-17 12:55 ` Takashi Iwai [this message]
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=s5hd4whe9i9.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=gmaruzz.lists@gmail.com \
--cc=maximlevitsky@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.