auracaster/sw_pyalsaaudio
3
0
Fork 0
forked from auracaster/pyalsaaudio
Code Pull Requests Activity

Import from divmod. Added css. Original log message:

Browse Source 
r1585 | casper | 2005-07-09 23:26:15 +0200 (Sat, 09 Jul 2005) | 3 lines

Last checkin before version 0.2





git-svn-id: svn://svn.code.sf.net/p/pyalsaaudio/code/trunk@12 ec2f30ec-7544-0410-870e-f70ca00c83f0
This commit is contained in:
larsimmisch
2008-01-24 12:22:41 +00:00
parent 470d6140df
commit 8fa9d27a88
24 changed files with 1192 additions and 820 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/libalsaaudio.tex
View File

@@ -234,7 +234,7 @@ full. In this case, the data should be written at a later time.
The most common reason for problems with playback of PCM audio, is that the people don't properly understand
that writes to PCM devices must match \emph{exactly} the data rate of the device.
If too little data is written to the device will an underrun, and ugly clicking sounds will occur. Conversely,
If too little data is written to the device, it will underrun, and ugly clicking sounds will occur. Conversely,
of too much data is written to the device, the write function will either block (PCM_NORMAL mode) or return zero
(PCM_NONBLOCK mode).
@@ -394,4 +394,4 @@ and that which I do understand has come from a painful trial and error process.
\subsection{ALSA Examples \label{pcm-example}}
For now, the only examples available are the 'playbacktest.py' and the 'recordtest.py' programs included.
This will change in a future version.
This will change in a future version.