On Sat, Sep 4, 2010 at 8:47 PM, Eric Blossom e...@comsec.com wrote:
On Sat, Sep 04, 2010 at 08:22:38PM -0400, Marcus D. Leech wrote:
On 09/04/2010 08:08 PM, Tom Rondeau wrote:
On Sat, Sep 4, 2010 at 12:19 AM, Marcus D. Leech mle...@ripnet.com wrote
Like Eric said, remove the throttle or at
On 09/06/2010 05:03 PM, Tom Rondeau wrote:
On Sat, Sep 4, 2010 at 8:47 PM, Eric Blossom e...@comsec.com wrote:
Marcus,
Indeed, this could be something we want to talk more about. Kind of on
the periphery of my vision, I can see a handful of applications where
the large chunking issue could be
On Sat, Sep 4, 2010 at 12:19 AM, Marcus D. Leech mle...@ripnet.com wrote:
On 09/03/2010 11:52 PM, Eric Blossom wrote:
Thought about that, as well. So replaced the graphical FFT sink with a
file sink, and set the
unbuffered flag. That file fills up in fits and starts'--that is,
it spends
On 09/04/2010 08:08 PM, Tom Rondeau wrote:
On Sat, Sep 4, 2010 at 12:19 AM, Marcus D. Leech mle...@ripnet.com wrote
Like Eric said, remove the throttle or at least change the rate and
that should clean things up.
Tom
I also noted in the reply to Eric that I observe the same behaviour
On Sat, Sep 04, 2010 at 08:22:38PM -0400, Marcus D. Leech wrote:
On 09/04/2010 08:08 PM, Tom Rondeau wrote:
On Sat, Sep 4, 2010 at 12:19 AM, Marcus D. Leech mle...@ripnet.com wrote
Like Eric said, remove the throttle or at least change the rate and
that should clean things up.
Tom
I've got a flow-graph with a throttled random byte source, which is a
test input for a modulator:
http://www.sbrac.org/files/fm4_test_modulator.grc
http://www.sbrac.org/files/fm4_test_modulator.py
The source is throttled to the byte rate required to produce the correct
number of symbols/second
On Fri, Sep 03, 2010 at 10:09:01PM -0400, Marcus D. Leech wrote:
I've got a flow-graph with a throttled random byte source, which is a
test input for a modulator:
http://www.sbrac.org/files/fm4_test_modulator.grc
http://www.sbrac.org/files/fm4_test_modulator.py
The source is throttled
On 09/03/2010 11:52 PM, Eric Blossom wrote:
The throttle block was written so that the GUI elements could be
tested without an inherently rate limiting source being in the graph.
It is not designed to precisely rate limit anything. For any use
other than that, you're asking for trouble.
