ALSA userspace API complexity
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Jaroslav Kysela ha scritto:
Quoted 25 lines · Pete Zaitcev
Quoted 11 lines · Alistair John Strachan
Quoted 7 lines
Quoted 4 lines
2) ALSA API is to complicated: most applications opens single sound stream.
FUD and nonsense. []
http://devzero.co.uk/~alistair/alsa/Quoted 6 lines
That's the kicker, isn't it? Once you get used to it, it's a workable API, if kinky and verbose. I have a real life example, too:
http://people.redhat.com/zaitcev/linux/mpg123-0.59r-p3.diff
But arriving on the solution costed a lot of torn hair. Look at this bald head here! And who is going to pay my medical bills when ALSA causes me ulcers, Jaroslav?Well, the ALSA primary goal is to be the complete HAL not hidding the extra hardware capabilities to applications. So API might look a bit complicated for the first glance, but the ALSA interface code for simple applications is not so big, isn't?
Quoted 9 lines
Also, note that app developers are not forced to use ALSA directly - there is a lot of "portable" sound API libraries having an ALSA backend doing this job quite effectively. We can add a simple (like OSS) API layer into alsa-lib, but I'm not sure, if it's worth to do it. Perhaps, adding some support functions for the easy PCM device initialization might be a good idea.
Jaroslav
considering that alsa API and drivers is pretty stable i see no problem in OSS removal.
When writing a program adding oss compatibility seems faster, but, creates lots of problems.
check the skype example (yes i know it's closed-source). 99% of sound problems users have is due to OSS driver usage.
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
A good idea could be an OSS API layer over Alsa-lib...but i personally don't know how much can that costs, considering you should link against alsa-lib too.
This discussion seems a no-sense.
Kernel API continues to change every -rc and noone cares that. OSS has been deprecated for a lot, and it's as old as moon.
Patrizio
--
Patrizio Bassi
www.patriziobassi.it
Quoted 2 lines · On Wed, 04 Jan 2006 12:56:12 +0100 Patrizio Bassi <[email protected]>…
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
aoss works _much_ less often than the OSS emulation kernel modules. I'd rather see (if not just for ease of setup), sw mixing in the OSS emulation kernel modules. aoss should still continue to exist as it has some advanced functionality like being able to use any alsa defined pcm device, but for the vast majority of cases it would be the best if the OSS emulation kernel module simply finally provided sw mixing.
It might also be worth taking a look at FUSE and stuff like oss2jack instead, as it would be (imho) the cleaner approach for getting OSS emulation to userspace as opposed to aoss (device file interface vs. ugly LD_PRELOAD hack (which has its share of problems. Especially with apps/libs that resolved the linux system call symbols at compile time - this is where aoss/LD_PRELOAD won't work, but a FUSE based approach would)).
Actually i suppose a FUSE based oss2alsa would probably make the old OSS emulation modules unnecessary if implemented right :) As the relevant code then lives in userspace it can make trivial use of stuff like ALSA sw mixing and all other ALSA userspace goodies (which aoss can, too, but at the cost of being an ugly LD_PRELOAD hack).
Have fun,
Flo
Signature · 2 lines
Palimm Palimm! http://tapas.affenbande.org
Quoted 21 lines · Florian Schmidt
On Wed, 04 Jan 2006 12:56:12 +0100
Quoted 2 lines · Patrizio Bassi
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
aoss works _much_ less often than the OSS emulation kernel modules. I'd rather see (if not just for ease of setup), sw mixing in the OSS emulation kernel modules. aoss should still continue to exist as it has some advanced functionality like being able to use any alsa defined pcm device, but for the vast majority of cases it would be the best if the OSS emulation kernel module simply finally provided sw mixing.
It might also be worth taking a look at FUSE and stuff like oss2jack instead, as it would be (imho) the cleaner approach for getting OSS emulation to userspace as opposed to aoss (device file interface vs. ugly
LD_PRELOADhack (which has its share of problems. Especially with apps/libs that resolved the linux system call symbols at compile time - this is where aoss/LD_PRELOAD won't work, but a FUSE based approach would)).
Quoted 5 lines
Actually i suppose a FUSE based oss2alsa would probably make the old OSS emulation modules unnecessary if implemented right :) As the relevant code then lives in userspace it can make trivial use of stuff like ALSA sw mixing and all other ALSA userspace goodies (which aoss can, too, but at the cost of being an ugly
LD_PRELOADhack).
Not to disrespect Miklos's work, but relying on FUSE for such a fundamental problem is probably not a good idea. Most people probably do not compile FUSE into their kernel.
I do agree with other posters here that OSS compatibility a) needs to be improved and b) should not be limited to the features of the soundcard (i.e. it must software mix). As Andi has pointed out, wholly removing OSS is not in the spirit of Linux and will not happen for many years.
Signature · 6 lines
Cheers, Alistair. 'No sense being pessimistic, it probably wouldn't work anyway.' Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.
Quoted 4 lines · Patrizio Bassi
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
Please rephrase your statement in the form of a USEFUL BUG REPORT.
Lee
Lee Revell ha scritto:
Quoted 10 lines · Patrizio Bassi
Quoted 8 lines
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
Quoted 7 lines
Please rephrase your statement in the form of a USEFUL BUG REPORT.
Lee
i opened an aoss/skype bug, that got closed without a complete fix.. because other problems were found...but actually that's not a complete solution
Quoted 19 lines · Patrizio Bassi
Lee Revell ha scritto:
Quoted 10 lines · Patrizio Bassi
Quoted 8 lines
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
Quoted 7 lines
Please rephrase your statement in the form of a USEFUL BUG REPORT.
Lee
Quoted 7 lines
i opened an aoss/skype bug, that got closed without a complete fix.. because other problems were found...but actually that's not a complete solution
Please see bug #1228. I closed #1224 as it had diverged wildly from the original bug report (which was someone asking "why ALSA doesn't do software mixing like artsd", which it does of course).
The status is we need more information on this bug. Some people report that Skype works perfectly with aoss. It seems to be hardware, ALSA version, or Skype version dependent.
Since Skype is closed source I'm afraid you'll have to do most of the debugging work yourself, we can't waste time debugging closed source apps.
I have heard that kiax (open source VOIP client) has some of the same problems with aoss as Skype so that's likely to be the most productive approach.
Lee
Lee Revell ha scritto:
Quoted 13 lines · Patrizio Bassi
Quoted 8 lines
that's a big problem. Needs a radical solution. Considering aoss works in 50% of cases i suggest aoss improvement and not OSS keeping in kernel.
yes i am the one (testing lots of voip solutions) in the bug report.
i told you that kiax has a similar problem :)
i think this sort of mail flood in kml is not productive. As Lee asked, let's use their mantis system and leave kml free.
this is going OT...from OSS removal, to Alsa bad design, to Alsa bugs...what else?
Patrizio