From: Paul Davis <pbd@op.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: asoundrc parse error (bug)
Date: Thu, 09 May 2002 09:05:11 -0400 [thread overview]
Message-ID: <200205091304.PAA26398@alsa.alsa-project.org> (raw)
In-Reply-To: Your message of "Thu, 09 May 2002 09:26:57 +0200." <Pine.LNX.4.33.0205090856280.544-100000@pnote.perex-int.cz>
>> pcm.st {
>> type plug
>> slave.pcm 9652
>> ttable.0.24 1
>> ttable.1.25 1
>> }
>>
>> this will fail unless you put the "9652" for the slave.pcm definition
>> in quotes. the error is:
>>
>> ALSA lib pcm.c:1621:(snd_pcm_open_conf) Invalid type for PCM definition (id:
> pcm, value: 9652)
>> arecord: main:447: audio open error: Invalid argument
>
>It's ok, slave.pcm should be a string (as defined in asoundrc.txt or
>alsa-lib reference guide).
well, my original claim was that the parsing code wouldn't allow the
use of numerics as device names. abramo claimed that there was no
problem with this. this example shows that there is.
there is nothing ambiguous about the example above. the problem arises
only because a formal grammar is not being used to parse it. whatever.
>Anyway, it would be better to add support for RME cards to standard
>configuration files. I've created initial ones, could you verify them?
>They are placed in /usr/share/alsa/cards/ directory - RME9636.conf and
>RME9652.conf files (sources are in alsa-lib/src/conf). The S/PDIF output
>should work as 'plug:spdif' or simply 'spdif' when no conversion is
>necessary.
they look fine, to the extent that i actually understand them :)
--p
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
prev parent reply other threads:[~2002-05-09 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 1:19 asoundrc parse error (bug) Paul Davis
2002-05-09 7:26 ` Jaroslav Kysela
2002-05-09 13:05 ` Paul Davis [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=200205091304.PAA26398@alsa.alsa-project.org \
--to=pbd@op.net \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
/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.