Marcus, You're correct, I probably want to set the minimum. I'm writing a GRPC source block to accept a data stream over the network. Each read over GRPC is about 64k bytes or 32k shorts (noutput_items), so I'd like to increase this number so I don't have to worry about queueing. I see a set_min_output_buffer() function, but no set_min_noutput_items. I imagine I'll have memory issues if I return a vector larger than noutput_items?
Jason On Tue, Mar 27, 2018 at 11:14 AM, Müller, Marcus (CEL) <[email protected]> wrote: > You set a maximum, and what you got is a value below. Did you plan to > set a minimum instead? What is it that you want to achieve? > > Also, noutput_items is not _necessarily_ the full buffer. Typically, on > the first call, you'd get offered half the buffer "to keep the spice > flowing", if I remember correctly. > > Best regards > Marcus > On Tue, 2018-03-27 at 11:05 -0400, Jason Hein wrote: >> I'm having issues increasing the global noutput_items value on my >> flowgraph. I'm setting the value in the python flowgraph to be global >> for all blocks. The code is below. However, when I print the value >> of noutput_items in my general_work() function within one of my >> blocks, it's still the default value of 16384. Any suggestions? >> >> tb = top_block_cls(fft_size=options.fft_size, freq=options.freq, >> port=options.port, samp_rate=options.samp_rate, >> update_rate=options.update_rate) >> tb.set_max_noutput_items(72000) >> tb.set_max_output_buffer(72000) >> tb.start() >> tb.show() >> >> Jason >> >> _______________________________________________ >> Discuss-gnuradio mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
