Hi,
> 52 int pdu_to_tagged_stream_impl::calculate_output_stream_length(const
> gr_vector_int &)
> 53 {
> 54 if (d_curr_len == 0) {
> 55 /* FIXME: This blocking call is far from ideal but is the best
> we
> 56*can do at the moment
> 57
That was great information Marcus, appreciate it!
Thanks,
Lakshay.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Alright. Thanks for your help Martin.
-Lakshay.
On Fri, Jul 22, 2016 at 8:51 PM, Martin Braun
wrote:
> On 07/22/2016 04:38 PM, Lakshay Narula wrote:
> > Thanks Martin, that was exactly what I was looking for.
> >
> > Would the following statement be correct: the GNU Radio flowgraph always
> >
Hi Piotr,
I let gdb loose on your minimal example [1], and found this:
52 int pdu_to_tagged_stream_impl::calculate_output_stream_length(const
gr_vector_int &)
53 {
54 if (d_curr_len == 0) {
55 /* FIXME: This blocking call is far from ideal but is the best we
56
Hi Marcus,
>Debugging your flowgraphs on a C++ and threat level when they ought to
>be exiting would be pretty interesting!
An example of my flowgraph where I used PDU to tagged stream convertion
is this:
https://github.com/ptrkrysik/examples/blob/master/voice_decoding_in_grc/tch_f_reception.grc
Stressing "average rate"! In GNU Radio, samples are processed in as much
space there's output buffer and/or how many samples a block wants to
consume or produce at once.
In the case of throttle, a single call to its work() method takes all
the input there is (let's say it's 8000 samples in this ro
Hi Piotr,
> Maybe it can be some "exit" tag that would be propagated to all blocks
> in a flowgraph.
In fact, GR does have something like that: It's a built-in message
handler for a message port called "system"; see block.cc:60:
60 message_port_register_in(pmt::mp("system"));
61 set_msg
