Is it time for remove (crap) ALSA from kernel tree ?
Quoted 3 lines
Quoted 2 lines
I don't like random applications blocking my sound card.
So don't use random applications.
I have ICE1724, a very good sound card to my taste, works like a charm. But with ALSA I had a really hard time to configure it properly, wanna see my .asoundrc? And I am not sure I have done it right (== the best possible way). I have read everything on http://www.alsa-project.org/documentation.php
about .asoundrc. When I am using Skype I have to rename .asoundrc to something else in order to get it working. When I am doing some changes to .asoundrc I have to restart the app. Is there a tool which can be used to configure .asoundrc? I want to be able to hear sound from flashplayer on my reciever or in my headphones -- how? It's not quite clear to me how to get full duplex working with my .asoundrc.
Signature · 1 line
Anton Petrusevich
On 06/28/2007 02:42 PM, Anton Petrusevich wrote:
Please always use Reply-to-All on this list -- subscribers here like to also get personal copies.
Quoted 3 lines
I have ICE1724, a very good sound card to my taste, works like a charm. But with ALSA I had a really hard time to configure it properly, wanna see my .asoundrc?
Not particularly. I don't count as a great fan of the config file syntax and don't use any configuration myself. I moreover don't own an ICE1724 card, so I'm not familiar with it's possibilities and quirks and generally, if this thread turns into guiding every user on the list through his/her respective problems with ALSA I have to respectfully decline...
Quoted 4 lines
And I am not sure I have done it right (== the best possible way). I have read everything on http://www.alsa-project.org/documentation.php about .asoundrc. When I am using Skype I have to rename .asoundrc to something else in order to get it working.
The first thing I don't know is why you need an .asoundrc at all. I've CCed the alsa-user list -- some subscribers to it probably have experience with ice1724 and might be able to get you specific advice if you want.
Renaming .asoundrc seems wrong in any case. If you need anything special for
Skype, it seems you could always define it in a seperate "skype" PCM and
use that only from skype.
Quoted 1 line
When I am doing some changes to .asoundrc I have to restart the app.
Yes, as far as I'm aware you do.
Quoted 1 line
Is there a tool which can be used to configure .asoundrc?
vi.
Quoted 1 line
I want to be able to hear sound from flashplayer on my reciever or in my headphones -- how?
Not sure? Is your receiver on an analog output and are your headphones connected directly to a card output as well? In that case, "or" would seem to be just a mixer issue, and "and" would be dependent on hardware abilities and needs someone who knows your specific card and setup.
Quoted 2 lines
It's not quite clear to me how to get full duplex working with my .asoundrc.
It's not working without an .asoundrc?
But -- I'll personally not continue this very specific subthread simply due to not having the hardware, nor great generic experience with an .asounrc due to not needing it myself. When I do use one, I alway start by googling up a few examples and take it from there. Perhaps someone from alsa-user will step in.
Rene.
Quoted 2 lines · On Thursday 28 June 2007 17:02:55 you wrote:
Please always use Reply-to-All on this list -- subscribers here like to also get personal copies.
I am not subscribed to linux-kernel, I am reading it on the web.
Quoted 5 lines
Quoted 3 lines
I have ICE1724, a very good sound card to my taste, works like a charm. But with ALSA I had a really hard time to configure it properly, wanna see my .asoundrc?
Not particularly. I don't count as a great fan of the config file syntax and don't use any configuration myself.
Do you have an SPDIF out? If you don't then you don't need .asoundrc of course.
Quoted 1 line
The first thing I don't know is why you need an .asoundrc at all.
Because I want to route it differently, sometimes to spdif, sometimes to headphones, sometimes to mix sounds from different apps. Well, my config may be a bit ancient as it was written when dmix was not default.
Quoted 3 lines
I've CCed
the alsa-user list -- some subscribers to it probably have experience with ice1724 and might be able to get you specific advice if you want.
I have read some advices for ice1724 already. The main reason I wrote to lkml -- I hate .asounrc and reading docs about it. I hate "flexebility" that requires restarting apps after changing sound routes.
Quoted 2 lines
Quoted 1 line
Is there a tool which can be used to configure .asoundrc?
vi.
I perfectly know this one. I would like to use some really user-friendly tool.
Quoted 5 lines
Quoted 3 lines
I want to be able to hear sound from flashplayer on my reciever or in my headphones -- how?
Not sure? Is your receiver on an analog output and are your headphones
My receiver is on spdif out.
Quoted 8 lines
connected directly to a card output as well? In that case, "or" would seem to be just a mixer issue, and "and" would be dependent on hardware abilities and needs someone who knows your specific card and setup.
Quoted 2 lines
It's not quite clear to me how to get full duplex working with my .asoundrc.
It's not working without an .asoundrc?
Looks like it's not working with. As skype is not so informative.
Quoted 5 lines
But -- I'll personally not continue this very specific subthread simply due to not having the hardware, nor great generic experience with an .asounrc due to not needing it myself. When I do use one, I alway start by googling up a few examples and take it from there. Perhaps someone from alsa-user will step in.
I am not about ice1724 or .asounrc here. I am trying to talk about user-friendliness of ALSA. It's very unfriendly.
Signature · 1 line
Anton Petrusevich
Quoted 4 lines · Anton Petrusevich
Quoted 2 lines
Please always use Reply-to-All on this list -- subscribers here like to also get personal copies.
I am not subscribed to linux-kernel, I am reading it on the web.
Then please subscribe just for the time you want to participate to the discussion.
Xav
Quoted 1 line · Anton Petrusevich
Do you have an SPDIF out? If you don't then you don't need .asoundrc of course.
I do on a number of cards, although being without sensible equipment (other than other soundcards) with an S/PDIF _in_ I don't actually use it for more than testing purposes.
Why do I need or want an .asoundrc? What's wrong with just using the iec958 PCM device? Yes, I checked, and ICE1724 has it defined.
Quoted 3 lines
Quoted 1 line
The first thing I don't know is why you need an .asoundrc at all.
Because I want to route it differently, sometimes to spdif, sometimes to headphones,
These two consist of specifying different devices (iec958 and <see below>)
Quoted 2 lines
sometimes to mix sounds from different apps. Well, my config may be a bit ancient as it was written when dmix was not default.
Right, it now is. The "default" device on your card uses both the dmix and the dsnoop (for the capture direction) plugins and if you want direct access without going through those plugins, you can select the direct "hw" devices simply by specifying them.
Quoted 3 lines
I have read some advices for ice1724 already. The main reason I wrote to lkml -- I hate .asounrc and reading docs about it. I hate "flexebility" that requires restarting apps after changing sound routes.
How would you _like_ things to work? asoundrc is a configuration file for alsa-lib. Would you perhaps suggest that alsa-lib expand its API with a snd_all_your_base_are_changed_out_from_under_you() application callback and sets notifies on its configuration file(s)? The application may have done things like enumerate the available PCM devices when it started up. Heck, maybe it's _busy_ playing through some "route" that you just changed...
Quoted 5 lines
Quoted 2 lines
Quoted 1 line
Is there a tool which can be used to configure .asoundrc?
vi.
I perfectly know this one. I would like to use some really user-friendly tool.
Some would say "emacs" now, but I'll not be as childish as that. I'm not like that. At all.
Quoted 1 line
I am not about ice1724 or .asounrc here. I am trying to talk about user-friendliness of ALSA. It's very unfriendly.
In another recent post in this thread, I linked to:
http://forum.skype.com/lofiversion/index.php/t85880.html
Note how it starts with:
"Now that Skype uses ALSA for its sound I/O, I can set it up to work properly with my multi-channel audio interface (an Echo Gina24 with an 8-channel ADAT interface chained onto it)."
That, as far as I'm concerned, says quite a bit. It says the flexibility is welcomed and used. Sure, simple things should be simple and with myself being a non-beginner-level user (user, not an audio professional) still not using or needing any configuration indicates to me that things have been partitioned correctly.
Yes, I can lose my way in the configuration as well when I play with it but I expect I could actually fairly easily remedy this by learning more about it before I start. And I expect for example that you hadn't heard of the iec958 PCM device before this message so that you only _think_ stuff is complex.
Generally, I tend to have some opinions on this blind insistance people seem to have they have an inalienable right to operate complex technology without turning their bloody brain on. I've been ranting just about enough now though so I'll not drag general "user friendliness" into it and just say that if I would have, it would've probably included the line "go buy a copy of windows and be gone" at some point.
Rene.
Quoted 5 lines · Rene Herman
Quoted 1 line · Anton Petrusevich
Do you have an SPDIF out? If you don't then you don't need .asoundrc of course.
I do on a number of cards, although being without sensible equipment (other than other soundcards) with an S/PDIF _in_ I don't actually use it for more than testing purposes.
Sorry please keep all "I don't need" or "I don't count" words for themeselve. We are taking not about you but about *ALSA*.
kloczek
Signature · 4 lines
----------------------------------------------------------- *Ludzie nie mają problemów, tylko sobie sami je stwarzają* ----------------------------------------------------------- Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*
Quoted 7 lines · Tomasz Kłoczko
Quoted 5 lines · Anton Petrusevich
Quoted 2 lines
Do you have an SPDIF out? If you don't then you don't need .asoundrc of course.
I do on a number of cards, although being without sensible equipment (other than other soundcards) with an S/PDIF _in_ I don't actually use it for more than testing purposes.
Sorry please keep all "I don't need" or "I don't count" words for themeselve. We are taking not about you but about *ALSA*.
Read the next lines. And then piss off, retard troll.
Rene.
Quoted 9 lines · Anton Petrusevich
Quoted 6 lines
Quoted 3 lines
I have ICE1724, a very good sound card to my taste, works like a charm. But with ALSA I had a really hard time to configure it properly, wanna see my .asoundrc?
Not particularly. I don't count as a great fan of the config file syntax and don't use any configuration myself.
Do you have an SPDIF out? If you don't then you don't need .asoundrc of course.
With a properly coded ALSA app, one doesn't need a .asoundrc. You would enter "plug:spdif" [or something similar] into the pcm device name entry text field.
Or if you want to point all apps to that device you actually could add this to your .asoundrc:
pcm.!default {
type plug
slace.pcm "spdif"
}
[or something similar. Too lazy to look up the exact syntax now]. And then every app using the ALSA API _correctly_ should use that device [if configured to use the default device, which should be the _default_ ;)]
Sadly it seems pretty much everyone, especially closed source apps get this wrong (but to be fair: loads of open source software gets it wrong, too, ekiga for example).
What they do wrong is that they try to present a list of devices to the user from which he can choose [which isn't bad in itself] and also do _not_ offer any way to specify an arbitrary PCM device name.
Sadly, the ALSA api docs do not stress this point often enough, so it gets missed pretty often.
I once posted an [not original, i suppose people before me got that idea, too] idea to the alsa-dev list a while back, proposing a way to be able to "register" pcm devices defined in .asoundrc/asound.conf, so that apps that want to present a list to the user can simply ask ALSA for a list of devices nd hav the user defined ones included. Sadly i don't think it ever went anywhere..
Quoted 3 lines
Because I want to route it differently, sometimes to spdif, sometimes to headphones, sometimes to mix sounds from different apps. Well, my config may be a bit ancient as it was written when dmix was not default.
Well, like i said, the application in question should allow you to enter any pcm name you want. If it doesn't it's broken.
Quoted 3 lines
I have read some advices for ice1724 already. The main reason I wrote to lkml -- I hate .asounrc and reading docs about it. I hate "flexebility" that requires restarting apps after changing sound routes.
I own a ice1712, too, but i only use it for JACK and it works brilliantly there. But i know it can be a bitch to configure since it sports a 10/12 channel device which can be too complicated for some ALSA apps making assumptions about the device they get ;)
Quoted 2 lines
I perfectly know this one. I would like to use some really user-friendly tool.
I don't know of any. But any text editor will do.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
I want to be able to hear sound from flashplayer on my reciever or in my headphones -- how?
Not sure? Is your receiver on an analog output and are your headphones
My receiver is on spdif out.
The flashplayer has been another one of these badly coded apps ;) Maybe that has changed in recent releases.
Quoted 3 lines
Quoted 1 line
It's not working without an .asoundrc?
Looks like it's not working with. As skype is not so informative.
But skype is a piece of crap anyways. It also doesn't get any sounds out of my other [non ice1712] card. Neither in OSS nor in ALSA mode. Not a beep. And yeah, the device is available [and even has hardware multiplexing]..
Quoted 2 lines
I am not about ice1724 or .asounrc here. I am trying to talk about user-friendliness of ALSA. It's very unfriendly.
I agree. ALSA is not very userfriendly. Especially the missing proper device enumeration support is a problem.
But 99.9% of problems people have with ALSA are due to badly coded apps..
Regards,
Flo
Signature · 2 lines
Palimm Palimm! http://tapas.affenbande.org
Quoted 3 lines · On Friday 29 June 2007 12:30:54 Florian Schmidt wrote:
Sadly it seems pretty much everyone, especially closed source apps get this wrong (but to be fair: loads of open source software gets it wrong, too, ekiga for example).
Isn't that because there's a perferct documentation for programming ALSA but authors of those apps can't read?
Quoted 2 lines
Well, like i said, the application in question should allow you to enter any pcm name you want. If it doesn't it's broken.
But in real life I have to use flashplayer, for example.
Quoted 1 line
I don't know of any. But any text editor will do.
I am with Linux since 1997, I know bunch of them. I used to use XEmacs, but now I prefer VIM. But I am not a .asoundrc programmer, I want to be just a user.
Quoted 2 lines
The flashplayer has been another one of these badly coded apps ;) Maybe that has changed in recent releases.
[...]
Quoted 5 lines
But skype is a piece of crap anyways. It also doesn't get any sounds out of my other [non ice1712] card. Neither in OSS nor in ALSA mode. Not a beep. And yeah, the device is available [and even has hardware multiplexing]..
But 99.9% of problems people have with ALSA are due to badly coded apps..
"Those apps are crap and ALSA is perfect". I hoped some ALSA-developers would think of improving usability of ALSA, or I would not talk here.
Quoted 2 lines
I agree. ALSA is not very userfriendly. Especially the missing proper device enumeration support is a problem.
It's good that people are not thinking that ALSA is already perfect, it leaves us (me) a hope it will be improved.
Signature · 1 line
Anton Petrusevich
Quoted 7 lines · Anton Petrusevich
Quoted 3 lines · On Friday 29 June 2007 12:30:54 Florian Schmidt wrote:
Sadly it seems pretty much everyone, especially closed source apps get this wrong (but to be fair: loads of open source software gets it wrong, too, ekiga for example).
Isn't that because there's a perferct documentation for programming ALSA but authors of those apps can't read?
No, like i said, the docs are unclear on these issues :) That's why so many people get it wrong.
Quoted 1 line
But in real life I have to use flashplayer, for example.
Yes, in these cases flashplayer should use either the default pcm device [which the user can then tweak to his liking] or provide some means to configure it. for example via a dotfile in the user's homedir. This is not ALSA's fault.
Quoted 3 lines
I am with Linux since 1997, I know bunch of them. I used to use XEmacs, but now I prefer VIM. But I am not a .asoundrc programmer, I want to be just a user.
I agree that it would be nice to have a tool to select the default device in ALSA.
Quoted 9 lines
Quoted 6 lines
But skype is a piece of crap anyways. It also doesn't get any sounds out of my other [non ice1712] card. Neither in OSS nor in ALSA mode. Not a beep. And yeah, the device is available [and even has hardware multiplexing]..
But 99.9% of problems people have with ALSA are due to badly coded apps..
"Those apps are crap and ALSA is perfect". I hoped some ALSA-developers would think of improving usability of ALSA, or I would not talk here.
ALSA must be improved, too. But that doesn't change a thing about these apps misusing the ALSA API and people blaming ALSA lateron. Which is wrong.
Quoted 2 lines
It's good that people are not thinking that ALSA is already perfect, it leaves us (me) a hope it will be improved.
I don't think any serious person believes that ALSA is perfect :)
Regards,
Flo
Signature · 2 lines
Palimm Palimm! http://tapas.affenbande.org
Quoted 3 lines · Anton Petrusevich
Is there a tool which can be used to configure .asoundrc?
There is an QT4 based one [1] and a somewhat old KDE based tool [2].
Regards,
Gabriel C
[1] http://sourceforge.net/projects/aplugedit/
[2] http://sourceforge.net/projects/kasound/