Quoth august, on 11/12/10 20:01:
Also, I'm running pd-0-42.6 from a terminal and noticed this in the terminal
console at the same time as a buzz:

opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
Couldn't get an audio frame, audiofifo is 0.000000 full.
error getting frame...must be seeking
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format
opened /home/james/2012/Chisenhale/sounds/Gunfire.wav
[demuxer] Info: Detected WAV format

is that where the buzzing is occurring?

it really shouldn't happen there.


It just means your disk is slow and the internal buffers haven't been
filled yet.   There should be no buzzing there as readanysf~'s buffers
are set to zero when that happens.

Sorry perhaps that was a false alarm. I ran it again and got a buzz after 115 loads but no message in the terminal.