Spencer Russell

What version of portaudio and your ALSA packages are you using? Are the messages coming out once in a while, or spitting continuously?

Hmm, I don't see this on my machine so I'm trying to nail down what the difference is. @shashi - you mentioned you see it on 0.4, does that mean...

@staticfloat, @shashi, @flpf, @maackle, @dpsanders It would be super helpful if I could get the following info: 1. output of `AudioIO.Pa_GetVersion()` 2. output of `versioninfo()` 3. whether you see the...

OK, feel free to open an issue anyways if you'd like some help figuring things out. If you're running into an issue it's likely others will as well, so it's...

The drop-outs while Julia is JIT compiling or garbage collecting are pretty much unavoidable at the moment. There is some work on Julia core to allow multithreading and incremental garbage...

If you checkout master the error messages are disabled by default. I should probably tag a release with that change, as there are also some others who get the error...

The ALSA messages are trickier, because they're actually printed to STDOUT by the portaudio library itself. From what I can tell from the portaudio SVN history that behavior was removed...

Ah, it looks like that error isn't printed where I thought it was. In the PortAudio file `pa_linux_alsa.c`, in the `PaAlsaStream_HandleXrun` function, it calls `alsa_snd_pcm_recover` with the third argument 0....

I just heard back from the main PortAudio dev and he supports enabling the `silent` flag. If none of the other core devs disagree then the change will probably happen....

I don't think there's anything in particular that makes it difficult. I just need to add some logic that looks at the filename and uses Wav.jl if it's a "*.wav"...