[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] buffer size 32k
From: |
Charles Swiger |
Subject: |
Re: [Discuss-gnuradio] buffer size 32k |
Date: |
Wed, 05 Jul 2006 13:32:51 -0400 |
On Wed, 2006-07-05 at 09:39 -0700, Eric Blossom wrote:
> On Wed, Jul 05, 2006 at 11:25:55AM -0400, Chuck Swiger wrote:
> >
> > Because: One of my simple test apps works 600% faster using 4k buffer
> > instead of 32k, since it doesn't have to wait for stale data to clear.
>
> Chuck, can you point me at the code for the application?
> I wouldn't expect the size of buffer to matter as long as each block
> returned all the data asked for on each call to work.
>
It's not an issue in continuous flow - the testing app had a problem
after changing DUC/DDC and restarting everything, it took about 750mSec
between samples to get a clean transition. I just tried it with a
buffer of 4k and was able to use 100mSec between samples.
Just curious if there could be easy way to specify the buffer size in
flow_graph.py - the comments seem to suggest there is a use for
'automatic optimization' but just another knob to tweak would be ok
with me. Other applications for minimal working buffer would be
shortning the delay between speaking into a mic and the transmitted
audio, or adjusting an antenna and seeing/hearing the results.
Script attached - the 'problem' shows up in the long 'else' clause
of the OnUpdate() function. Too small timer delay and the next few
data points are repeats of the one right before changing cordic freq.
--Chuck
f_sweep_2b.py
Description: Text Data