mirror of
https://github.com/RGBCube/serenity
synced 2025-07-26 03:17:34 +00:00
Base: Document /dev/audio devices
This properly documents the fact that /dev/audio contains a bunch of device's channels now, instead of being a single file.
This commit is contained in:
parent
3052c0578c
commit
01d056f794
2 changed files with 7 additions and 3 deletions
|
@ -10,7 +10,7 @@ SerenityOS structures audio into three groups of responsibilities: Audio drivers
|
|||
|
||||
### AudioServer
|
||||
|
||||
AudioServer is responsible for handling userland audio clients and talking to the hardware. For this reason, no userland application should ever need to write to `/dev/audio` directly, except for special cases in which AudioServer is not present.
|
||||
AudioServer is responsible for handling userland audio clients and talking to the hardware. For this reason, no userland application should ever need to write to a device in `/dev/audio` directly, except for special cases in which AudioServer is not present.
|
||||
|
||||
As with all system servers, AudioServer provides an IPC interface on `/tmp/portal/audio`. For specifics on how to talk to AudioServer, the IPC interface specifications are the best source of information. Audio clients send audio buffers with the standard audio format (see [audio](help://man/4/audio)) to the server. They can then query the state of these buffers, pause buffer playback or clear the playing buffers. For controlling mixer functionality, clients have the ability to obtain and change their own volume, or the main volume and mute state.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue