Occasional choppiness/underruns (aUaU) with FCDPP->GRC->Pulse


In most cases the problem comes from ALSA. If you’re able to change ALSA
something else, try to change it.

If you can’t change your default sound driver then you may try using
“-Dplug:default” option for aplay. If you need to use this option with a
Python script you may use it like " -c plug:default".

This was my only solution when I tried running rtl_fm on Raspberry
default audio driver of Raspberry is ALSA and not possible to change
(everything else like Jack, Pulseaudio etc. can’t be a solution because
of them run over ALSA, ALSA always remains at the bottom, so the problem
always remain).

I hope this helps.


Murat, TA1DB

From: Chuck R. [via GnuRadio]
[mailto:[email protected]]

Sent: Sunday, April 06, 2014 4:10 AM
To: Murat TA1DB
Subject: Occasional choppiness/underruns (aUaU) with FCDPP->GRC->Pulse

Hello list, I need some help.

When running GRC 3.6.1 I am getting a problem with occasional choppiness
my audio output. Details:

  • The choppiness sounds like only part of the buffer is filling, similar
    the sound you get when a filmstrip’s playback gets unstable and you get

  • The issue usually does not immediately occur however occurs a few
    into use.

  • Sometimes computer activity such as un-minimizing a window will
    the problem. Sometimes the same will fix it.

  • Input is Funcube Dongle Pro+ 192khz on alsa hw:3

  • Occurs regardless of using FCDPP+ Block or the Audio Input block.

  • Output is pulse, originally set to 192khz (pulse resamples it),
    brought it
    down to native 48khz and used Rational Resampler block to bring the 192

  1. Did not resolve, however the issue occurred less often. (still
  • Turned on Realtime Scheduling and then adapted the JACK instructions
    enabling system realtime scheduling permissions
    (http://jackaudio.org/linux_rt_config). Afterward confirmed the python
    process to have a nice of -30 which is realtime. Issue did not resolve
    again, it happened less often. (still intolerable)

  • Occurs regardless of graph complexity. Simple in->out arrangement will
    reproduce issue.

  • Sometimes you can hear it get worse as time goes by, and sometimes it
    just as randomly fix itself, only to occur again later.

  • I am using pulse as my audio output.

  • When the issue occurs, the console output in GRC fills rapidly with

  • When the issue occurs, looking into pavucontrol playback tab shows
    plug-in [python 2.7]” entry flickering rapidly, as if it is resetting
    connection over and over in an unreasonable manner.

  • When the issue occurs, the realtime python process on core 2 shows no
    change in core usage, however the non-realtime gnuradio-companion
    also on core 2, spikes from its usual 0.9% usage to 93%. The only way I
    see a high-priority process being pushed out by a low-priority process
    is if
    the high-priority process is waiting on the low-priority process for
    operation to complete (this is a DSP no-no).

  • When the issue occurs, pulseaudio’s verbose log fills rapidly.
    attached is
    a snippet of what repeatedly fills the log.

  • There is chatter about similar underrun issues with mozilla and pulse.
    However the fixes appear to be occurring in mozilla only so there wasn’t
    much help from that.
    (779392 - Improve the ALSA PulseAudio bug workaround used to fix bug 761274)

  • When attempting to specify ‘pulse’ as signal input in GRC and then
    FCDPP as its input in pavucontrol, GRC gives silence and a stream of

  • pulseaudio 4.0

  • Xubuntu 13.10 AMD64.

There was a similar issue posted earlier however it was different in
in the sense that the underruns occurred immediately instead of on
implying a consistent sample rate mismatch.

It is reasonable to rule out sample-rate mismatch in my case as the
occurs only on occasion and sometimes fixes on its own, a mismatch would
expected to immediately fail. It would be mathematically impossible for
mismatched sample rate to cause such cascading underruns after minutes
proper functioning except for clock drift, which would be expected to be
solved with a single buffer reset (a slight “blip”). This is not what is
happening. It is thousands of consecutive blips after a while of proper

Thanks for reading. Log dump attached.

Discuss-gnuradio mailing list
[hidden email]

grc-jitter-bug-pulse.log (15K) Download Attachment

If you reply to this email, your message will be added to the discussion


To start a new topic under GnuRadio, email [email protected]
To unsubscribe from GnuRadio, click here
by_code&node=2&code=bXRvbG9nbHVAaG90bWFpbC5jb218MnwtNTYyNDcwMzM2> .

s%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> NAML