Sound Forge v14 vs v11 Performance

MCC wrote on 4/7/2020, 6:46 PM

I generally edit 40 minute long lecture style MP3 files. I have an i7-8700k processor with EVO-960 NVME drive. I just upgraded from Sound Forge v11 to v14, but the save times for the 40 minute MP3 file continue to be about 40 seconds, as are the times for processing (normalize, compression, audio restoration, etc.). Processor and drive usage never exceed 25% and are generally 10% during processing.

Another quirk is that the longer I edit the file, the slower the mouse response becomes. I usually proceed through the file to remove dead space, coughs, and other artifacts. I often use CNTR-X with left hand as it is easier than pressing delete. It is difficult to quantify precisely, but seems as though the time from mouse operation to action increases from ~10-30ms to 100-300ms. If I save, or exit the file, this interactive lag build-up goes away.

I have noticed this problem in both v11 and in v14, which I purchased in an attempt to resolve this problem. Hoping there is an obvious solution I am missing rather than converting MP3 source file to another format and back again.

Comments

rraud wrote on 4/8/2020, 11:34 AM

Hi @MCC and welcome to the Sound Forge forum.

Try "Options> Preferences> General" and check- mark "Always proxy compressed formats"

The available RAM in your PC can affect response time as well ..as can plug-ins. . Using the SF project file workflow can slow things down as well. I usually use the destructive editing mode, 'Saving as' after each topic or speaker. Naturally you want to copy the original file before starting in case something goes horribly wrong in editing.

Other than that, MP3 should avoided especially for acquisition and editing. Always use PCM files <.wav> A PCM single channel (mono) 44.1k Hz, 16 or 24 bit format is more than adequate for spoken word material. When editing is complete, an MP3 can be encoded from the PCM master if that is the preferred end-delivery format.

MCC wrote on 4/11/2020, 8:02 AM

Thank you. My source is MP3, but I will see if the proxy file workflow improves the response.