AP - Simon Blandford wrote:
> OK, after compiling and installing the latest Alsa lib and drivers I
> set about creating a .asoundrc file. Here is what I put in it from the
> example shown below...
>
> pcm.dsnoopy {
> type dsnoop
> ipc_key 5978293
> ipc_key_add_uid yes
> slave {
> pcm "hw:0,0"
> }
> bindings {
> 0 0
> 1 1
> }
> }
Looks right.
> Now I don't feel easy about this because I have no idea what ipc_key
> means or where the magic number came from.
The ALSA library uses a mechanism called IPC to communicate between
multiple processes. The key is required to identify cooperating
applications, and must be a unique number. Usually, it's some random
number.
> When I get Helix Producer to query what sound/capture cards are
> availble it still only reports one sound card...
>
> $producer -pd
> Helix(TM) DNA Producer 9.1 Copyright (c) RealNetworks, Inc. 1995-2003. All rights
> reserved.
> ...
> AUDIO
>
> Device 00: TriTech TR A5 /dev/dsp
You need to tell the application to use the ALSA PCM device named
"dsnoopy". "/dev/dsp" is an OSS device which doesn't support PCM plugins.
(I don't know if Helix Producer does support ALSA devices at all.)
HTH
Clemens
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
