[Alsa-devel] Bug in sis7012 driver - or probably I'm doing something wrong ?
Hi,
I have Asus pundit with sis7012 sound device and alsa 1.0.4 under Suse 9.0.
I've got advice how to use this 6 channel device as 3 stereo channels but
there seems something not to be right (it could be my mistake).
Now I do:
- alsaplayer with mp3 file on device plug:a
- aplay -D plug:ch12 (funny is that plug:a doesn't work)
- everything is ok and mixed properly
- but if I start another alsaplayer on plug:b (probably also plug:c would be
the same), then aplay produces sound that is interleaved in short chunks
and also sound from alsaplayer on plug:b is also heard in addition to
original mp3 and aplay sound.
Am I doing something worng or is this somkind of bug or limitation of alsa
driver ?
Thanks in advance,
Robert.
I have /etc/asound.conf :
pcm_slave.sis {
pcm hw:0
channels 6
rate 48000
buffer_size 4096 # make these sizes smaller for lower latency
period_size 2048
periods 0
period_time 0
}
pcm.ch12 {
type dmix
ipc_key 47110815
slave sis
bindings.0 0
bindings.1 1
}
pcm.ch34 {
type dmix
ipc_key 47110815
slave sis
bindings.0 2
bindings.1 3
}
pcm.ch56 {
type dmix
ipc_key 47110815
slave sis
bindings.0 4
bindings.1 5
}
pcm.a {
type plug
slave.pcm ch12
}
pcm.b {
type plug
slave.pcm ch34
}
pcm.c {
type plug
slave.pcm ch56
}
pcm.dmixerALL {
type dmix
ipc_key 47110815
slave sis
bindings.0 0
bindings.1 1
bindings.2 2
bindings.3 3
bindings.4 4
bindings.5 5
}
pcm.channelALL {
type plug
slave.pcm dmixerALL
ttable.0.0 1
ttable.1.1 1
ttable.0.2 1
ttable.1.3 1
ttable.0.4 1
ttable.1.5 1
}
-
---
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] migrating from old to new alsa-api
[EMAIL PROTECTED] wrote: Hi, i need some clarifying about how the defines ALSA_PCM_OLD_HW_PARAMS_API etc. behaves. for alsa-1.x its clear that if the app uses the new api i have to define ALSA_PCM_NEW_HW_PARAMS_API, but what is for the case if i have an app with the new api and the user uses only alsa9? is alsa1.x then backwards compatible? regards Zsolt Barat ALSA_PCM_NEW_HW_PARAMS_API etc. is for use with alsa0.9.x That define is assumed to be the default for alsa1.x.x ALSA_PCM_OLD_HW_PARAMS_API is for use with alsa1.x.x to make it behave like alsa0.9.x without the ALSA_PCM_NEW_HW_PARAMS_API. Summary: - To make your code work with bother alsa 0.9.x and 1.x.x, use ALSA_PCM_NEW_HW_PARAMS_API etc. and then write your code to the 1.x.x api. --- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] dxs_support and via82xx (yet once more) -- some new findings
yes, the module name still consists of snd- prefix. the snd_ prefix was dropped from the module OPTIONS. (e.g. dxs_support would have been named as snd_dxs_support in the old versions.) Oh, I see now. Thank you very much for explaining that. Now, when I do put in an option into the modules.conf specifying a different dxs mode, am I still supposed to get the same message in my syslog about picking trying dxs=1 or 4 or does that message show up only when no options have been successfully parsed? I am asking this since even when I am 100% sure that my syntax is/was ok I would still get the message no matter what option was specified in modules.conf. I tried hacking via82xx.c file where I would hardwire my vendor/card ID into the list of known cards and changing it that way and the card worked the same no matter which options I chose, so I decided to leave it at DXS_ENABLE (or 1 if I am not mistaken). This is the only way how I would disable that message from appearing in syslog. What kind of difference am I supposed to notice by changing dxs in order to figure out the best option anyhow? As it is right now I can play 4 simultaneous streams and they all sound ok (no apparent glitches etc.). But this is the case no matter which option I pick. BTW, i assume that are you using 2.4 kernel. is it right? No, I am working with 2.6.3 and 2.6.5 (both patched). Finally, I've observed one extremely interesting phenomenon. I did notice that when compiling preemptive versions of these kernels that I get tons of xruns even when using aplay talking directly to hw:0. I literally need at least buffer of 512 for aplay to play ok. I also noticed that certain applications (i.e. frozen-bubble) would play stuff a bit faster than they ought to be played (although I am not sure whether this is linked to a particular alsa driver version or the preempt stuff). With preemptive flag disabled, everything seems to be ok. Best wishes, Ico --- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
