After digging into this a bit more, it appears that the latency on the null
sink is all over the place when pavucontrol is NOT running. For example, here
is a case when it is not running:
index: 2
name:
driver:
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
After playing around with this for about 6 hours, I found some interesting
data. The latency on the g722 (since renamed to ip_mcast) null-sink hovers
around 20mS when I have pavucontrol running, and around 600mS when I don’t have
it running. Since G722 requires pretty consistent 20Ms packets,
