24 Jun
2008
24 Jun
'08
11:25 a.m.
Hans-Christoph Steiner wrote:
My guess is because pix_buffer stores uncompressed frames, which are much bigger. But I could be wrong.
you could store the pixes in YUV-format, which will double the amount of images you can store in a given memory (the default is RGBA) (either send the [colorspace YUV( to the [pix_film] or use [pix_yuv] just before the [pix_buffer_write])
if you think that the bottleneck is the harddisk access, you could also try to read the film from a RAM-disk (if such a thing exists on w32)
fgmasdr IOhannes