Le 2011-10-24 à 12:57:00, João Pais a écrit :
what I also do is to send the file name to iemlib/soundfile_info, which gives
out the file size (for wav files). then I send that value as an argument to
-maxsize, and I don't have to worry about how big the sound file is. (except
for Mathieu's error, which I hadn't heard about before)
AFAIK (by reading source, not by trying) :
-maxsize between 2GB and 4GB will cause pd to take the size as a negative
value, which it will replace by 0, and thus won't load the file.
-maxsize between 4GB and 6GB will pretend that the size is 4GB less than
what you specified.
-maxsize between 6GB and 8GB will give a negative value again.
-maxsize between 4GB and 6GB will pretend that the size is 8GB less than
what you specified.
and so on.
This problem also would happen in 64-bit mode.
Someone with a bigger RAM and bigger soundfile could confirm it.
Just like most other bugs about overflow, the changes happen at binary GB
boundaries : multiples of 1024*1024*1024 bytes, and not multiples of
1000*1000*1000.
______________________________________________________________________
| Mathieu BOUCHARD ----- téléphone : +1.514.383.3801 ----- Montréal, QC
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
