Hi James,
What readanysf~ version are you using?
If you aren't using the latest version, please download from here http://aug.ment.org/readanysf/download.php
or use the handy ppa's from puredyne: https://launchpad.net/~puredyne-team/+archive/ppa
If you are using the latest info, can you narrow the problem down to a particular file? Does it only happen with that one wav file?
I've build a stress patch that opens, plays and then reopens your Gunfire.wav file over and over again...and can't seem to reproduce your buzzing.
-august.
Hi list,
I've been using readanysf~ for a while and had no problems. However recently I've been experiencing random buzzing when playing soundfiles. I'm running Ubuntu 10.04 on a 1.6ghz machine with Pdextended 0.42-5. It doesn't happen on every file or even every time I play a particular file, just randomly about once every 20 plays and seems to be an error with how the file is opened, as once it's opened, it always buzzes until a new file is loaded in.
any ideas as to what could be wrong?
Here's the file with the buzz: http://www.4thharmonic.com/audio/ readanysf~test.wav (Notice it's only in the right channel) and here's how it should sound: http://www.4thharmonic.com/audio/Gunfire.wav
thanks
James
Hi August,
I'm using this version - https://launchpad.net/~reduzierer/+archive/ rdz-pd-extra+deps
that is the latest.
which is dated 2010-10-06 so should be current? I'm also using Pdextended 0.42-5 from http://puredata.info/downloads (Lucid i386). I just tried again to recreate the error and it took much more than 20 times to happen, but eventually the file opened with the buzz. I've attached the patch I'm using - basically I'm loading various files in a playlist with the "left" and "right" keys on the keyboard and then starting the file with "enter". 95% of the time the files play fine, but inevitably one time (like the show last night!)
ouch. sorry. that shouldn't happen.
the
buzz happens.
the first thing I notice about your patch (besides all of the externals that don't load for me) is that you are looping the files based on the bang at the end of file. You should really use the "loop" message to readanysf~ to turn looping on and off.
Attached is the stress test patch I made with your gunfire.wav. It's been running for minutes now without that problem.
Can you test it on your setup? If it doesn't make the buzz, please simplify your patch so that it works in vanilla pd without any extras but still makes the buzz.
-august.
I ran your patch several times and it takes a while to happen, but it still buzzes eventually (although once it happened on the third or fourth load). I recorded the results here: http://www.4thharmonic.com/audio/readanysf~test2.mp3 - (the buzz happens around 2:28 and happens 3 times)
ok, this smells like a memory leak to me. Not going to be easy to find.
Do you have other externals loaded at the same time? If so, try re-running my stress patch with no other libs or externals loaded.
thanks -august.
ok I downloaded Pd-vanilla 0.42-6 from puredata.info and ran the patch. It took about 10 mins, but eventually there were a couple of buzzes. No libs or other externals, just pd-vanilla 0.42-6 with readanysf~ running your stress patch.
yeah, I heard it once too.....not sure yet what is causing it.
ok I downloaded Pd-vanilla 0.42-6 from puredata.info and ran the patch. It took about 10 mins, but eventually there were a couple of buzzes. No libs or other externals, just pd-vanilla 0.42-6 with readanysf~ running your stress patch.
James,
Can you download and try this:
http://aug.ment.org/software/readanysf~testing.tar.gz
does that help any?
-august.
Hi August,
Thanks for looking into this. I ran the stress patch again on pd-vanilla-0.42-6 and heard a buzz after a minute or so. I also got the following error in the console (although not at the same time as the buzz)
readanysf~: error on m_decode_block inside perform()
James
Okay, try this one now:
http://aug.ment.org/software/readanysf~testing2.tar.gz
I don't think it is a memory leak error. memory usage should be real
tight.
I'm guessing the buzzing comes from when the dsp is stuck. It can't
happen in the readanysf~ function that sends out the audio. ..but
could happen right when you open a file and the open callback spits
out file inof. I've moved some things around. I hope this helps.
please test and let me know.
-august.
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.
Hi James,
Sorry this is so late. I haven't had time to investigate the buzzing
problem you reported. I suspected it was an issue with the gmerlin
libs. I'm trying now to test it again and can't reproduce the error.
I hope it was a bug with gmerlin that has now been fixed.
can you download, compile and run the test patch again?:
http://aug.ment.org/software/readanysf~testing.tar.gz
I've run the stress test patch now for a few minutes and don't get
the buzzing like before.
If you are using the latest ubuntu, I believe the gmerlin libs are
all included in the multimedia section.
-august.
-
august -
James Dunn