Community Forums Archive

Go Back

Subject:Regions Not Exported Correctly
Posted by: selavy
Date:3/5/2013 8:10:06 PM

I'm hoping someone from Sony is monitoring this forum. I really like the PC version, but am having problems with the Mac.

Happens very frequently but not always.

To reproduce:
1) Open an AIFF file.
2) Create a region.
3) Export it (also as AIFF).
4) Open exported region file.
5) Examine length (in samples or time whatever) of original region
and loaded region, They don't match.

The length of the exported region is often longer than the original by as many as 2000-3000 garbage samples (not silence). This is enough to throw off the timing and sound of a loop.

This bug is preventing me from buying the program. I can't see spending $$$ for a program that can't even cut loops properly.

Subject:RE: Regions Not Exported Correctly
Reply by: iain_m
Date:3/9/2013 1:33:47 PM

By the way - on the PC version, regions move if a list of regions is saved, then reopened. Sound Forge does not preserve their positions accurately!

Sony has known about this since November 2011.

Message last edited on3/9/2013 1:34:42 PM byiain_m.
Subject:RE: Regions Not Exported Correctly
Reply by: selavy
Date:3/13/2013 7:00:53 PM

Posting this so that others won't get burned by this defect.

I dug into this a little deeper by dissecting the AIFF output file.

What seems to be happening is that Sound Forge is padding out the audio to a 4096-byte multiple. Seems like a bug to me.

So I tried switching the output format to uncompressed WAV. That works.

So if you want sample-accurate region saves, don't use AIFF (or AIFC), use WAV.

After discovering this, I'll likely wind up buying the program. I really like the Sound Forge interface and workflow. Zooming and cutting are so much better than anything else I've used.

With the demise of Bias, Mac users really need a good audio editor. I hope Sony fixes the bugs and brings along more of the PC features (batch editing would be my request).

Subject:RE: Regions Not Exported Correctly
Reply by: SonySQAPete
Date:3/14/2013 11:25:27 AM

Selavy,

Thanks for taking the time to mention this issue here and even provide a workaround for other users.

This issue has already been fixed and tested and you'll see the fix roll out in our next update release.

Go Back