Currently some blocks that have realtime constraints (like audio sink) will drop extra data or add extra zero samples if the upstream pipeline cant keep up.
There is currently no mechanism for blocks to indicate how many samples they require to produce output or indicate that they need samples at a particular rate.
See: FutureSDR/FutureSDR#195
We might have to spearhead / upstream this since bastibl simply says
I usually debug this either by adding debug outputs to the work functions or the runtime
which wont work for our users
Currently some blocks that have realtime constraints (like audio sink) will drop extra data or add extra zero samples if the upstream pipeline cant keep up.
There is currently no mechanism for blocks to indicate how many samples they require to produce output or indicate that they need samples at a particular rate.
See: FutureSDR/FutureSDR#195
We might have to spearhead / upstream this since bastibl simply says