On Sat, Aug 16, 2008 at 4:03 AM, Rakesh Peter <[EMAIL PROTECTED]> wrote:

> Just tested the opengl implementation... Rocks hard ! Update times are
> really up on my C2D 2.4G E4600 / 2GB / Intel 82G33/G31 / Ubuntu Hardy.
>
> Had to do a "make clean" also, since it was reporting some top_block4dump
> error while running any GR code. Probably a lone case. In Ubuntu, you can
> get python-opengl bindings with "sudo apt-get install python-opengl".
>
> Some bugs (ticket #260):
>
> In Waterfall, I can go down the time scale till milliseconds updating, when
> the whole window freezes and I can't update the parameters anymore.
> Terminating the application seems to be the only way.
>

With a smaller time scale, the waterfall must process FFT frames even
faster. Most likely, the UI cannot respond because too much % CPU is taken
for other processing. Can you report how much CPU usage when this freeze
happens?


>
> Happened to notice some occasional frequent flickering with the windows in
> the background. The screenshot is attached. Also the FFT window (only the
> graph portion) becomes overlaid over other windows (right now, I can see it
> inside Firefox ;)) if it is not minimized.
>

What kind of graphics card/driver version?


>
> http://imagebin.ca/view/6zuODeL6.html
> http://imagebin.ca/view/HIMraDE.html
>
> Indeed, thanks to Josh and team for the release...
>
> Regards,
>
> rakesh
>
>
> On Fri, Aug 15, 2008 at 12:51 AM, Johnathan Corgan <
> [EMAIL PROTECTED]> wrote:
>
>> Josh Blum has implemented OpenGL-based versions of the FFT, waterfall,
>> and scope sinks in gr-wxgui. These have been merged into the trunk as of
>> revision 9291, and will be part of the 3.2 release.
>>
>> This feature available to those who have installed GNU Radio via a
>> source code build from the GNU Radio trunk repository.  You will not be
>> able to use it if you are using the release tarballs, the release
>> repository, or binary package installations.
>>
>> You will need to have OpenGL available for your graphics card, and have
>> installed the python-opengl bindings.  This is the default for many
>> systems, but please see your distribution documentation for details.
>>
>> Currently, the new displays must be explicitly enabled in your GNU Radio
>> preferences, though in release 3.2 they will become the default with
>> fall back to the non-GL versions if GL is not available.  Please see:
>>
>> http://gnuradio.org/trac/browser/gnuradio/trunk/gr-wxgui/README.gl
>>
>> ...for details on how to enable.  If you have written your own GNU Radio
>> applications that use wxgui sinks, you will not have to make any changes
>> to your source code for these.
>>
>> The existing Python scripts in gr-utils and gnuradio-examples will
>> automatically take advantage of the new functionality if enabled.
>>
>> To obtain this new code, you will need to update your GNU Radio trunk
>> distribution, and re-run the build:
>>
>> (From the top-level source code directory)
>>
>> $ svn update
>> $ ./bootstrap
>> $ ./configure (...whatever you might currently use...)
>> $ make
>> $ make check
>> $ sudo make install
>>
>> We are looking for testers, to measure the difference in performance
>> between the non-GL and GL versions, and in particular, the performance
>> of the GL versions when using a non-accelerated host-based GL
>> implementation like Mesa (without DRI).
>>
>> In particular, the waterfall implementation is a vast improvement over
>> the existing one.  Try usrp_fft.py -W to view.
>>
>> Thanks, Josh!
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to