Hi,
looks like gnuradio is freezing due to the massive amount of underflows
ocurring. First try replacing the constant source with two separate analog
fast noise sources connected to the dma fifo - this might help if indeed
the problem is that the PC is being too slow to generate samples. Secondly
In general you should only call produce() and consume() from within
general_work(), and, really, you only need to consume() because
produce() can be called with the return value from the function call
(or, return WORK_CALLED_PRODUCE to indicate as much). The other block
types (e.g. sync), call both
On Sun, 19 Nov 2017 at 13:16:14 -0500, Michael Dickens wrote:
> You can safely call produce() and consume() multiple times in the same
> work() call: yes!
I assume this also applies to general_work()?
> Note that by doing so, if you're using the nitems_written() or
> nitems_read() [e.g., for find
You can safely call produce() and consume() multiple times in the same
work() call: yes!
Note that by doing so, if you're using the nitems_written() or
nitems_read() [e.g., for finding or writing tags], then those values
will be updated when you call produce() and consume() -BUT- inside the
work()
You're welcome, Anil; glad that was useful.
You can go either way with a block like the one you describe: general or
sync. The block is sync when the correct parameters are set
("set_output_multiple(512);") or the like; and, really, the scheduler
will handle the I/O correctly if you choose this bl
Hi Michael, Thank you very much for your response. This clears up things
for me.
One other question regarding this is: If the block takes in 4095 samples,
returns 3854 onto its output is this still considered a sync (1:1) block or
would it be a general block?
I am leaning towards thinking that an
On 19/11/17 17:22, rear1019 wrote:
> I have a question regarding the usage of produce() and consume(): Is it
> safe to call these functions multiple times? Or must the calls be
> merged into a single one?
consume() in the end calls buffer_reader::update_read_pointer(int
nitems) which again calls
Hello,
I have a question regarding the usage of produce() and consume(): Is it
safe to call these functions multiple times? Or must the calls be
merged into a single one?
Documentation of consume() [1] states that “this function should be
called at the end of work() or general_work(), after all p
