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
Hi Anil - In the case where your block gets 4095 items, it can't process
all of those items. Your block performs seven 512-length FFTs, consumes
7x512 == 3584 items, and generates 3584 items, leaving 511 unprocessed.
The code that calls your block's "::work" method will handle making sure
that the
Hi Anil,
You can fix the buffer size using the Min Output Buffer parameter (under
the Advanced tab in your block, assuming you're using GRC).
[image: Inline image 1]
Regards,
Ernest
On Thu, Nov 16, 2017 at 1:56 PM, Anil Kumar Yerrapragada <
yanilkumar2...@gmail.com> wrote:
> Hi all
>
>
> I am
