Hi, I did some more tracing and I could narrow down the problem to the call when writing data synchronously to the sound card.
When the sound card does not receive the data in time, it will cause an "Underflow". I read that the underlying, platform specific sound card drivers handle Underflows differently. Alsa on Linux apparently closes the audio stream and reinitializes it - and this of course takes some time and blocks in the meanwhile my go-routine. Apparently what I should do is to write empty audio buffer samples to the sound card when no data is received from the network to avoid underflows. Let's see if this fixes the problem :-) Tobias On Sat, Jan 21, 2017 at 8:31 AM, Sokolov Yura <funny.fal...@gmail.com> wrote: > Did you try GOMAXPROC=1 ? > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
