| 1 |
On Sunday 15 November 2009 00:40:48 Dale wrote: |
| 2 |
> > The only reason arts ever existed at all was to do sound mixing in |
| 3 |
> > software in the days when hardware generally did not do that. |
| 4 |
> > |
| 5 |
> > These days alsa takes care of all of that. OSS-4 does a better job I |
| 6 |
> > hear, but in any case you do not need arts. If you did, how would it be |
| 7 |
> > possible to hear sound in a flash video in a browser on a non-KDE system? |
| 8 |
> > |
| 9 |
> > |
| 10 |
> |
| 11 |
> And I think that was my problem. It would only play one sound at a time |
| 12 |
> and some things hogged up the sound system. Mine makes a sound when I |
| 13 |
> change desktops for instance and it would hold onto the sound system for |
| 14 |
> a minute or so before other sounds could use it. |
| 15 |
> |
| 16 |
|
| 17 |
|
| 18 |
Typical arts behaviour :-) |
| 19 |
|
| 20 |
arts would grab the sound device, and any KDE app could then use arts to play |
| 21 |
sound. arts used software mixing to make this all work. However, non-KDE apps |
| 22 |
(or any app actually without arts support) could not get to the sound device |
| 23 |
as arts had locked it. It would give up the lock after 1 minute of no sound. |
| 24 |
|
| 25 |
This led to obvious problems. There were some "solutions" such as a wrapper |
| 26 |
script you'd use to start gnome apps with, the wrapper would grab the gnome |
| 27 |
app sound and sent it onto arts. But none of this was synchronized so although |
| 28 |
the app sound played, you were never sure exactly *when* is would play .... |
| 29 |
|
| 30 |
Yuck. I mean, alsa is a bit of a mess but arts makes also look pristine and |
| 31 |
wonderful in comparison |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
alan dot mckinnon at gmail dot com |
Archives