Hi all,
I tried to use the dmix plugin, as mentioned :
pcm.dmix_analog {
type dmix
ipc_key 5678293
ipc_key_add_uid yes
slave {
pcm hw:0,0
}
bindings {
0 0
1 1
}
}
When I do
aplay
Hello again,
Quoting Jaroslav Kysela [EMAIL PROTECTED]:
The 32-bit mixing code is not debugged. Please, could you try to change
one line in pcm_dmix.c (alsa-lib/src/pcm/pcm_dmix.c) from
'#ifdef __i386__' to '#ifdef __i386XX__' and recompile library?
We'll see then if it's a problem with the
On Fri, 21 Mar 2003, Patrick Shirkey wrote:
Fernando Pablo Lopez-Lezcano wrote:
It would be nice that the user not need to type magic numbers into a
configuration file, unique or not. I don't know what it involves, but it
would make using the configuration file much easier.
Even
At Fri, 21 Mar 2003 13:56:50 +0100 (CET),
Jaroslav wrote:
On Fri, 21 Mar 2003, Patrick Shirkey wrote:
Fernando Pablo Lopez-Lezcano wrote:
It would be nice that the user not need to type magic numbers into a
configuration file, unique or not. I don't know what it involves, but it
At Thu, 20 Mar 2003 10:02:06 +0100,
Kristof Pelckmans wrote:
I wonder how you know that the number you assign is not in use...
well, there is no guarantee for that.
i think it would be more understandable to have the string type ipc
key, such as
pcm.dmix {
type dmix
On Thu, 20 Mar 2003, Takashi Iwai wrote:
At Thu, 20 Mar 2003 10:02:06 +0100,
Kristof Pelckmans wrote:
I wonder how you know that the number you assign is not in use...
well, there is no guarantee for that.
i think it would be more understandable to have the string type ipc
key, such
just to clarify: all 3 plugins will not enable several processes to use the same
soundcard's channels, i.e. software mixing?
Thanks,
Florian
Hi all,
the dmix plugin was extended to support channel bindings and
mixing code for 32-bit samples (24-bit resolution).
I'd like to
On Thu, Mar 20, 2003 at 02:13:18PM -0800, Florian Bomers wrote:
just to clarify: all 3 plugins will not enable several processes to use the same
soundcard's channels, i.e. software mixing?
dmix does just that. Works fine here, ipc_key stuff and all :)
--
Ville Syrjälä
[EMAIL PROTECTED]
On Thu, Mar 20, 2003 at 02:13:18PM -0800, Florian Bomers wrote:
just to clarify: all 3 plugins will not enable several processes to use the same
soundcard's channels, i.e. software mixing?
dmix does just that. Works fine here. ipc_key stuff and all :)
--
Ville Syrjälä
[EMAIL PROTECTED]
I wonder how you know that the number you assign is not in use...
well, there is no guarantee for that.
i think it would be more understandable to have the string type ipc
key, such as
pcm.dmix {
type dmix
ipc_key_str /usr/alsa/foo
...
}
which generates
Fernando Pablo Lopez-Lezcano wrote:
It would be nice that the user not need to type magic numbers into a
configuration file, unique or not. I don't know what it involves, but it
would make using the configuration file much easier.
Even nicer is if this could be embedded like the dmix was
At Wed, 19 Mar 2003 17:49:51 +0100 (CET),
Jaroslav wrote:
Hi all,
the dmix plugin was extended to support channel bindings and
mixing code for 32-bit samples (24-bit resolution).
I'd like to introduce new two plugins (seems also most wanted by
ALSA users): dsnoop and dshare.
On Wed, 19 Mar 2003, Takashi Iwai wrote:
At Wed, 19 Mar 2003 17:49:51 +0100 (CET),
Jaroslav wrote:
Hi all,
the dmix plugin was extended to support channel bindings and
mixing code for 32-bit samples (24-bit resolution).
I'd like to introduce new two plugins (seems also
Sure. First example is for the dmix plugin and ice1712 (10 playback
channels - last two are S/PDIF, so this configuration allows sharing of
the S/PDIF jack):
pcm.dmix_spdif {
type dmix
ipc_key 5678293
Hmm, sorry for my ignorance, but what does this number mean and where
14 matches
Mail list logo
