GoldWave Inc.

I Batch process daily with commands like: "C:\Program Files\GoldWave\GoldWave.exe" -proclog:C:\Temp\ProcessBatch.log "-process:My loudness, silence, bandstop, 2019-03-26" *.mp3 *.m4a But with this latest GW version, the Batch processing dialog no longer shows in Window's taskbar....

I apologize for the delay. My main computer crashed for the holidays. Does the file play in Windows Media Player on your computer? Are you downloading the file first, or are you trying to play it using the "Open URL" feature in GoldWave (or from the iCloud)? Yes, I download them first and,...

The program is freezing (and Windows reports "Not Responding") merely when trying to open certain m4a files.
Goldwave never recovers. Windows 7 SP1, Professional, 64 bit.

Sample file that kills Goldwave is Episode 7 (¿and most early episodes?) of the Ben Shapiro Show.

I wondered that he (it) had echoed my words so precisely -- and so selectively. That's better than any bot I've yet encountered.

Sure it wasn't some disgruntled user (or competitor) with some scripting "skillz"?

jerry050321111, it's not a RAM bug. It's that GoldWave is not a true 64-bit application. Did you see my workaround? I've had excellent results by using a RAM-drive when processing audio. It actually even seems faster than using straight memory (but I have not definitively measured). You can get free...

Thanks for the knowledgeable response, Chris. I had suspected that GoldWave was not true 64-bit and resorted to a trick I used with Audacity (which crashes on both my Win 7 systems, alas). I create a temporary RAM drive, and the processing proceeds without the slowness of "flying rust"-dri...

Because you are using the hard drive, you won't see this error. BUT, your batches are much, much slower. Using RAM, a 30M file takes about 10 minutes for my batch to process. Using Disk it takes about between 30 minutes to an hour (I haven't yet timed it accurately -- I will stop using GoldWave if t...

No, the batch is 1 chain and two processes, that's it.

I do not run one file at a time except when trying to troubleshoot this bug. If there is more than one file, GoldWave aborts on the first one that is more than about 33M.

What are your "storage options" set to?

Whenever I try to batch process a file greater than about 33M, GoldWave aborts the job after a few minutes -- saying, "Not enough memory is available for processing". Thing is, I've got 4G of RAM, and GoldWave never even uses 2G of it. I watched the process with Performance Monitor open, a...