Difference between revisions of "Linux audio"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(→‎Reference: replacement for linux-sound.org)
(→‎Notes: sox)
 
(2 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
==Other Apps==
 
==Other Apps==
 
* [http://www.baudline.com/ baudline] advanced audio analyzer for Linux/BSD
 
* [http://www.baudline.com/ baudline] advanced audio analyzer for Linux/BSD
 +
* [http://wiki.hydrogenaudio.org/index.php?title=Rubyripper Rubyripper]: very exacting CD ripper
 +
==Notes==
 +
[[sox (audio utility)|sox]], aka [[Sound eXchange]]: command-line audio utility. Creates, converts, and manipulates audio data.
 +
 +
If sound won't work, here are some things to check.
 +
* Go into any of the mixer applications and make sure nothing important is muted
 +
* '''/dev/audio''' and '''/dev/dsp'''
 +
** permissions should be set up so you can read and write; typically, they will be owned by user "root" and group "audio", with read/write permission for user and group, and you must belong to the "audio" group.
 +
** {{linuxcmd|lsof}} each of these files (e.g. "lsof /dev/audio") to be sure neither is locked by another application (some audio applications can crash while leaving the audio device locked). Once unlocked after having been locked, you may need to restart the audio system for it to work again.

Latest revision as of 00:57, 13 January 2008

Navigation

computing: software: Linux: audio

This page is a seed article. You can help HTYP water it: make a request to expand a given page and/or donate to help give us more writing-hours!

Articles

Reference

Other Apps

Notes

sox, aka Sound eXchange: command-line audio utility. Creates, converts, and manipulates audio data.

If sound won't work, here are some things to check.

  • Go into any of the mixer applications and make sure nothing important is muted
  • /dev/audio and /dev/dsp
    • permissions should be set up so you can read and write; typically, they will be owned by user "root" and group "audio", with read/write permission for user and group, and you must belong to the "audio" group.
    • lsof each of these files (e.g. "lsof /dev/audio") to be sure neither is locked by another application (some audio applications can crash while leaving the audio device locked). Once unlocked after having been locked, you may need to restart the audio system for it to work again.