[EMAIL PROTECTED] wrote: > I'm sure you are right about the gui taking the majority of the cycles, > but it's the real-time feedback that makes gnuradio so attractive. > Ideally one would beable to switch them on and off as needed during > operation of the program, which it is my understanding will be possible > with the implementation of mblocks. > > As things stand now, is there a "refresh rate" control that I can > modify, so that the scope sinks use less cycles? Yes, you can set the following parameters. sink param default less cycles Function oscope frame_decim 1 >1 keep one block in every "frame_decim" fft fft_rate 15.0 <15.0 refresh rate of fft_display
so for less GUI cycles set frame_decim to 10 or even 100 set fft_rate to 5.0 or even 1.0 I wished that fft_rate was set to 5.0 default because allmost allways 15.0 is too much a load on my machines. Greetings, Martin > thanks, > eric > > On Wed, 10 Oct 2007, Eric Blossom wrote: > >> On Wed, Oct 10, 2007 at 06:07:04PM -0400, [EMAIL PROTECTED] wrote: >>> Ok, that works in principle, but I'm finding that I cannot sustain the >>> same data rate as before on a fast dual core machine. >>> >>> I'm acquiring all 4 channels, and I'm doing both low-pass and high-pass >>> filtering on all of them. I am also displaying 5 sinks >>> simultaneously; 1 >>> fft and 4 scopes. >> >> You'll most likely find that the bulk of your cycles are spent in the >> gui. Try disabling it. >> >>> So, in the long term it would help to have this sorted out in the >>> fpga if >>> that's possible; is that impossible as things stand now, or is there >>> sufficient space in the 4rx no hb fpga? >> >> IIRC, the std_4rx_0tx.rbf configuration uses about 86% of the FPGA. >> >> Eric >> > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > _______________________________________________ Discuss-gnuradio mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
