On Thu, Jun 14, 2012 at 9:40 PM, Phelps Williams
<address@hidden> wrote:
I found an old discussion
http://lists.gnu.org/archive/html/discuss-gnuradio/2012-01/msg00104.html
on this exact issue... Per Ed Criscuolo's suggestion modifying
GR_FIXED_BUFFER_SIZE in
gnuradio-core/src/lib/runtime/gr_flat_flowgraph.cc worked!
I'm a virtual noob here, but this issue is interesting.
When there is actual UDP source, there is essentially no latency issue, right?
Could the synthesized output with no input consumption be "confusing" the scheduler? When the scheduler calls forecast/work and there is no input, what happens?
Do you call produce or produce_each directly after synthesizing output?
If you set the environment variable GR_SCHEDULER to STS, do you see the same symptoms.
Thanks for your analysis.