Such an easy question

[James Linder]

> It must be my own naivet. Building from src, debugging led to the simple answer that works. Thanks specially to Nirbheek.
> 
> gst-launch-1.0 $@ v4l2src device=/dev/video2 ! queue ! video/x-h264,width=1920,height=1080,framerate=30/1 ! h264parse ! queue max-size-buffers=0 max-size-bytes=0 max-size-time=1000000000 ! mux. pulsesrc device=0 ! audioconvert ! \
> 
> audioresample ! audio/x-raw, rate=16000 \
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> ! queue ! avenc_aac ! queue ! mux. mpegtsmux name=mux ! filesink location='output.mp4'

I have a a 1:25min file recorded from above! yet today I can record only 25 sec before ‘underflow’

I went spelunking

————————————— on gst-launch -e -m 
[busy recording]
time passes



Got message #189 from element "pulsesrc0" (warning): GstMessageWarning, gerror=(GError)NULL, debug=(string)"gstaudiobasesrc.c\(845\):\ gst_audio_base_src_create\ \(\):\ /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0:\012Dropped\ 3200\ samples.\ This\ is\ most\ likely\ because\ downstream\ can\'t\ keep\ up\ and\ is\ consuming\ samples\ too\ slowly.";
WARNING: from element /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0: Can't record audio fast enough
Additional debug info:
gstaudiobasesrc.c(845): gst_audio_base_src_create (): /GstPipeline:pipeline0/GstPulseSrc:pulsesrc0:
—————————————————


so why, with no messages in does pulsesrc suddenly decide ‘underflow’?
and why a working pipeline suddenly goes tilt?

James