Hi all, apologies for the delay in getting back to you! The end of last week was quite busy and I was away from my computer during the weekend.
2012/11/1 Ryan May <rma...@gmail.com>: > You might have more luck using a temp-file based writer. By default, > movies are created by piping in the data to the command; this is much > faster, but, at least as I've done it now, requires a fixed number of > bytes per frame. Try passing writer='ffmpeg_file' or > writer='mencoder_file' to the command to save the animation. Yes, this works indeed. Thanks for pointing it out! I had feared that getting the 'bbox_inches' argument to work at all would be much more involved. > If I get a chance (or someone else if you want to help), I'll see if > there's any way to make the pipe-based writers work with > variable-sized frames. That would be awesome of course. :) > Failing that, we could just ignore the tight > bbox option when using pipes for saving movies. I like this idea. I have now updated my branch so that the save() method checks which writer is being used. If it is not a temp file-based one a warning is issued and the 'bbox_inches' argument is dropped if it is present (see [1]). Please review and comment. :) Best regards, Max [1] https://github.com/maxalbert/matplotlib/commit/fe44357d04fd708c616e88e386bb06100c12aaca ------------------------------------------------------------------------------ LogMeIn Central: Instant, anywhere, Remote PC access and management. Stay in control, update software, and manage PCs from one command center Diagnose problems and improve visibility into emerging IT issues Automate, monitor and manage. Do more in less time with Central http://p.sf.net/sfu/logmein12331_d2d _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
