Re: [pygame] pygame.image.save(...)

[David Muffley <sunami.2600@xxxxxxxxx>]

My first instinct is that the first several frames' data is sent to
your hard drive, where it's cached to be written, which fills up
faster than it's depleted since the file size per second is higher
than your disk can handle writing it.  I had this issue myself trying
to do something similar.  If this is the case, saving as a smaller
file size obviously helps, but could become a CPU issue, where I can
say that pygame.image.save appears to be asyncronous (maybe only on
some file types?)

If it's growing in time it takes to save each time though, instead of
just spiking up, I don't know.

On Tue, Apr 27, 2010 at 10:56 PM, Ian Mallett <geometrian@xxxxxxxxx> wrote:
> Hi,
>
> In a related email thread here, I've been trying (now successfully) to
> render a movie from a series of frames captured from a program I wrote.
>
> The screen capturing is done via pygame.image.save(...).  In my case, the
> surfaces that are being saved are derived from OpenGL framebuffer readbacks.
>
> I've noticed that the first few dozen or so frames save in a fraction of a
> second, while subsequent frames take increasingly longer.  This, obviously,
> gets annoying.  I do not know why this is.  Can someone please explain?
>
> I am using PyGame 1.9.1.
>
> Thanks,
> Ian
>