Open starburst997 opened 11 years ago
Hey thanks for this hint! I've started using Standingwave for my air app, and also finding bugs.
You actually show have noticed that it's function public function writeWavBytes(destBytes:ByteArray, offset:Number=0, numFrames:Number=-1):void {...} . For me it was on line 865
E.g., in WaveFile.as I had to comment out line 57: //fileLen += wav.position;
as it breaks the cycle below. It's very strange why would length of wav be increased after just reading a byte from it...
Also, your suggestion doesn't work when original wav files is 1 channel mono.
Memory usage is steadily increasing over time
Am I doing something wrong here? It is also leaking even if you play it one time, the "New" at each frame is to better show the increase.The only way I was able to fix it was to use Flash built-in "writeBytes" instead of "awave.writeBytes"
If I look at the Profiler, the ByteArrays stay in memory. A workaround:
On line 850 in "Sample.as" replace
with
Now when I look at the profiler, it isn't leaking anymore.
I tried to play with "awave.c" using an old Alchemy toolchain since it doesn't seem to be compatible with Flascc but couldn't find a proper fix.