Hello Max,
Thanx for your answer. I forgot to write that the resolution of the movie is 480x360 pixels (there was a mistake in my previous mail where i wrote 640 480), 4 bytes per pixel. There is 7300 frames in this movie. So the size in RAM used should be : 480x360x4x7300=5045760000 bytes. It should be enough because there is 6.4 Go free on my Windows system (64 bits). Or I miss something ? On the same computer, but under Ubuntu 13.04 (64 bits) it works fine... So, is it a memory problem under Windows ? ++
Jack
Le 05/05/2013 16:51, Max a écrit :
AFAIK it isn't a windows problem but the problem is that you have not enough ram on the windows machine. I've reported this 2012-02-25
https://sourceforge.net/p/pd-gem/bugs/180/
Am 05.05.2013 um 16:24 schrieb Jack jack@rybn.org:
Hello,
[pix_buffer] seems to crash Pd with Windows when the number of image loaded by [pix_buffer_write] is > 2412.
I tested this with four configurations :
A MSI with 8 Go of RAM and Windows 8 (64 bits) Pd-extended 0.43.4
A MacPro with 3 Go of RAM and Windows 7 (32 bits) Pd-extended 0.43.4
A MSI with 8 Go of RAM and Ubuntu13.04 (64 bits) Pd 0.44.3 (with Gem ver: 0.93.git 374f713)
A MacBookPro MacOSX.6 Pd-extended 0.43.4
All works fine under MacBookPro with MacOSX and MSI with Ubuntu, but pd crash on Windows when the number of image loaded by [pix_buffer_write] is > 2412.
The patch contains a [pix_buffer test 10000].
If i create and send the message [allocate 640 480 4( to this [pix_buffer test 10000], on Windows i get in the console 'out of memory!', this is not the case under Ubuntu (not tested under MacOSX).
I just want to use the abstraction [pix_buffer_filmopen] which use [pix_buffer] under Windows but it is impossible with a (not so) long movie (around 7200 frames, .mov, codec photoJPEG)... This movie is read fine until the end with [pix_film] under Windows.
If someone can help me to solve this problem, it would be very nice. Thanx. ++
Jack
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev