On Tue, 10 Jan 2006, Jaroslav Kysela wrote:
> On Fri, 6 Jan 2006, Hannu Savolainen wrote:
>
> > The fact is that there is nothing the audio subsystem can do to recover
> > the situation. For this very simple reason the OSS API lacks everything
> > that would be necessary to cope with this kind of problems.
>
> Applications should be notified that something is broken. If you have
> a professional environment, you really need to know, if the output
> survived all scheduling peaks and the audio data are delivered from/to
> I/O in time.
This is exactly how OSS API works. The application can check if there were
any errors so far. It can do it after finishing the playback or whenever
it likes. It can then show a dialog box saying that playback/recording
was not 100% error free. Alternatively it can show error counters on the
status line. Or most applications just don't care.
Best regards,
Hannu
-----
Hannu Savolainen ([email protected])
http://www.opensound.com (Open Sound System (OSS))
http://www.compusonic.fi (Finnish OSS pages)
OH2GLH QTH: Karkkila, Finland LOC: KP20CM
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
