-
The size of the file is to blame here. The ARSE uses double precision floats, which means that simply loading a regular WAVE file will result in occupying 4 times as much memory as the file uses disk space. With your example file, it results in 200 MB of RAM occupied by the file alone.
Also, the ARSE 0.1 wasn't designed to process efficiently such large files, and even if memory usage wasn't...
2007-12-06 04:11:42 UTC by michelrouzic
-
Here's a decode of the MP3 I tried to analyse. It's quite long (and quite big):
http://data.vectec.net/arse.wav
Default settings, saved to a file called foo (no extension). Had to cancel partway through due to memory consumption.
2007-12-05 17:42:17 UTC by codyhs
-
The ARSE may take a lot of memory depending on the length of the wave file and the settings used, but there's also a chance that the ARSE's wave file parser didn't read your file correctly and that it lead to the leak you've noticed.
In order to help determine which of the two happened to you I would need to know how long your wave file was (preferably in number of samples, but...
2007-11-28 19:02:48 UTC by michelrouzic
-
I have "ARSE" a test today, and tried it on a wave file, it started processing, but chewed up all of my memory. I'm not sure if this is a real bug, but perhaps maybe less memory could be used?.
2007-11-28 17:20:33 UTC by codyhs
-
michelrouzic committed revision 1 to the Analysis & Reconstruction Sound SVN repository, changing 14 files.
2007-11-22 16:48:12 UTC by michelrouzic
-
Anonymous committed patchset 1 of module CVSROOT to the Analysis & Reconstruction Sound CVS repository, changing 11 files.
2007-04-20 20:10:13 UTC by nobody
-
michelrouzic registered the Analysis & Reconstruction Sound project.
2007-04-20 20:05:05 UTC by michelrouzic
