I am wondering if the "optimizations" you have are actually slowing you
down. I have never found myself needing to flush_events() or call update()
like that. Or to draw the artists like you are doing. Without seeing more
of the code, it is hard to judge. Have you tried using "runsnakerun" to
profil
Thanks for the help (and sorry for the super-late reply).
I just tried blitting, but it doesn't really help. I cannot exceed 20 fps.
The problem is that I'm plotting data from a video file, so that for each
frame I need to draw a new array (not just a foreground). I think its just
to much data.
T
To push much past 20Hz you will want to look into blitting. See
http://matplotlib.org/devdocs/api/animation_api.html for a rough
introduction on how to use blitting (and see the animation code for an
example of handling all of the corner cases).
Tom
On Fri, Oct 14, 2016 at 5:29 PM Hjalmar Turess
That works fine. And it explains why update() only worked with the Qt
backends (I tried all). The speed is still not super impressive though (~20
fps), but I think I will just start skipping frames when playing at above
20 fps.
Thanks,
Hjalmar
On Fri, Oct 14, 2016 at 10:37 AM, Thomas Caswell wro
Instead of `canvas.update` call `self.im.figure.canvas.draw_idle()`.
IIRC `update` is part of the API inherited from Qt, not part of the API we
ensure that all of the canvas objects have.
Tom
On Fri, Oct 7, 2016 at 4:48 PM Hjalmar Turesson wrote:
> Hi all,
>
>
> I made a little video player us
Hi all,
I made a little video player using matplotlib. I need it to allow very good
control over the playback speed (e.g. direction, frame-by-frame stepping
and fast and slow).
However, it's not very fast. Max frame rate I can achieve is 10-20 fps.
I followed Basti's advice on speeding up plotti
Michael Droettboom wrote:
> Ok -- well, I'm genuinely sorry for wasting your time.
No waste. As I said, I'm investigating Graphics Context for other things
anyway.
> Paul Kienzle made a change back in February that changed where
> wx.Yield() gets called, that by side-effect seems to have fixed
Michael Droettboom wrote:
so are you working on an example? Or should I?
I'm happy to do it, but may not get to it for a few days. My own test
was to run "simple_plot_fps.py" with "handle_clip_rectangle" (in
backend_wx.py) turned on and off. But obviously the wxPython folks will
want a mor
On Tue, Jun 17, 2008 at 7:16 AM, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Christopher Barker wrote:
>> If we really think that would help, and we would use it for MPL, we
>> could try to get it done -- but I doubt that it's worth it -- we have
>> enough trouble keeping the wx back-ends main
Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> Creates a wx.GraphicsContext from a native context. This native
>> context must be eg a CGContextRef for Core Graphics, a Graphics
>> pointer for GDIPlus or a cairo_t pointer for Cairo. NOTE: For
>> wxPython we still need a way to make t
Michael Droettboom wrote:
> Thanks. I had seen these threads already -- I was hoping you had some
> more.
sorry :-(
> It also is different from what I was talking about in the sense of
> clipping. The effect I see is that when an explicit clipping rectangle
> is applied (e.g. the axes), spee
Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> Christopher Barker wrote:
>>
> A number of threads on the wxPython list. Here's a couple:
>
> http://aspn.activestate.com/ASPN/Mail/Message/wxpython-users/3519845
>
Thanks. I had seen these threads already -- I was hoping you ha
Michael Droettboom wrote:
> Christopher Barker wrote:
>> For what it's worth, apparently you can speed up GraphicsContext code
>> substantially if you use it right --
> Can you be more specific about this
no. I haven't done much with it myself.
> or provide a reference?
A number of threads
Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> If you're using 0.98.x with the wx backend, things are *very* slow. The
>> performance of wx.GraphicsContext (that is uses under the hood) is
>> terrible.
>>
>
> For what it's worth, apparently you can speed up GraphicsContext c
Michael Droettboom wrote:
> If you're using 0.98.x with the wx backend, things are *very* slow. The
> performance of wx.GraphicsContext (that is uses under the hood) is
> terrible.
For what it's worth, apparently you can speed up GraphicsContext code
substantially if you use it right -- i.e.
Are you using the wxAgg backend or just wx? Which version of matplotlib?
If you're using 0.98.x with the wx backend, things are *very* slow. The
performance of wx.GraphicsContext (that is uses under the hood) is
terrible. You may want to try switching to the WxAgg backend, which,
among other
I have developed a wxPython GUI that uses matplotlib to plot line traces
(using plot()). If I were to plot about 250,000 data points, it takes
nearly 1 minute to load the plot (using a intel dual core), although once
this plot is loaded, it is easy to interact with it - changing the x/y scale
& sc
17 matches
Mail list logo
