Possible SF8 Bug in Batch Converter -Sound Forge - PC

Subject:Possible SF8 Bug in Batch Converter Posted by: mpd Date:4/5/2005 6:45:27 PM I am having a weird problem in Batch Converter, and was wondering if anyone else is. Batch Converter works great for me, expect for Auto Trim. If I add Auto Trim to the process list, then it hangs up at that point. Auto Trim by itself works, but if there are any plugins after it, then the batch process freezes after the Auto Trim step. Other processes that change the file length, such as Insert Silence, seem to work OK. I am going to play with this some more, but can anyone else confirm this? Thanks.
Subject:RE: Possible SF8 Bug in Batch Converter Reply by: mpd Date:4/6/2005 6:47:25 AM I did some more experimenting, and Auto Trim is definetly wonky when running in Batch Converter. Not only does it not appear to work when processes follow it, it doesn't look like it works properly. Here are steps to demonstrate the problem. 1. Create a new data window. I created as 44.1 / 16 / mono 2. Genrate a five second sine wave at 440 Hz 3. Open Batch Converter 4. Add process: Insert 1 sec silence at beginning of file 5. Add process: Insert 1 sec silence at end of file 6. Add process: Auto Trim/Crop, trim silence from ends, bump up fade in and out to 500 ms 7. Start the batch job Now look at the data window. The silence was trimmed at the beginning to the proper length. The silence at the end of the file was not touched, and the waveform was corrupted towards the end. Now reproduce the steps above manually, and everything is OK. Batch Converter seems to work OK for everything else, but not being able to use Auto Trim/Crop puts a serious cramp in my workflow.
Subject:RE: Possible SF8 Bug in Batch Converter Reply by: Sonic Date:4/6/2005 8:36:50 AM Good repro. I believe BC is getting confused by length-changing processes. I see worse problems like hangs when you shorten the data instead of lengthening it, say, first Auto-Trim/Crop, then try to do a Fade In. I"ll investigate further. J.
Subject:RE: Possible SF8 Bug in Batch Converter Reply by: mpd Date:4/6/2005 9:01:57 AM Here are the steps to reproduce BC hanging: 1. Create a new data window. I created as 44.1 / 16 / mono 2. Genrate a five second sine wave at 440 Hz 3. Insert 1 sec silence at beginning of file 4. Insert 1 sec silence at end of file 5. Open Batch Converter 6. Add process: Auto Trim/Crop, trim silence from ends, bump up fade in and out to 500 ms 7. Add process: Volume, leave at 0 dB 8. Start the batch job I contacted tech support on both of these as they are reproducable and serious.
Subject:RE: Possible SF8 Bug in Batch Converter Reply by: mpd Date:4/15/2005 6:05:18 AM I heard back from Tech Support last night about this: "Unfortunately there isn't a workaround at this point. The issue actually involves any plug-in that changes the length of the file, not just the Auto Trim/Crop. This one is very high priority, so it will be one of the first issues to get fixed."

Subject:Possible SF8 Bug in Batch Converter

Posted by: mpd

Date:4/5/2005 6:45:27 PM

I am having a weird problem in Batch Converter, and was wondering if anyone else is.

Batch Converter works great for me, expect for Auto Trim. If I add Auto Trim to the process list, then it hangs up at that point. Auto Trim by itself works, but if there are any plugins after it, then the batch process freezes after the Auto Trim step. Other processes that change the file length, such as Insert Silence, seem to work OK.

I am going to play with this some more, but can anyone else confirm this?

Thanks.

Subject:RE: Possible SF8 Bug in Batch Converter

Reply by: mpd

Date:4/6/2005 6:47:25 AM

I did some more experimenting, and Auto Trim is definetly wonky when running in Batch Converter. Not only does it not appear to work when processes follow it, it doesn't look like it works properly.

Here are steps to demonstrate the problem.

1. Create a new data window. I created as 44.1 / 16 / mono
2. Genrate a five second sine wave at 440 Hz
3. Open Batch Converter
4. Add process: Insert 1 sec silence at beginning of file
5. Add process: Insert 1 sec silence at end of file
6. Add process: Auto Trim/Crop, trim silence from ends, bump up fade in and out to 500 ms
7. Start the batch job

Now look at the data window. The silence was trimmed at the beginning to the proper length. The silence at the end of the file was not touched, and the waveform was corrupted towards the end.

Now reproduce the steps above manually, and everything is OK.

Batch Converter seems to work OK for everything else, but not being able to use Auto Trim/Crop puts a serious cramp in my workflow.

Subject:RE: Possible SF8 Bug in Batch Converter

Reply by: Sonic

Date:4/6/2005 8:36:50 AM

Good repro. I believe BC is getting confused by length-changing processes. I see worse problems like hangs when you shorten the data instead of lengthening it, say, first Auto-Trim/Crop, then try to do a Fade In.

I"ll investigate further.

J.

Subject:RE: Possible SF8 Bug in Batch Converter

Reply by: mpd

Date:4/6/2005 9:01:57 AM

Here are the steps to reproduce BC hanging:

1. Create a new data window. I created as 44.1 / 16 / mono
2. Genrate a five second sine wave at 440 Hz
3. Insert 1 sec silence at beginning of file
4. Insert 1 sec silence at end of file
5. Open Batch Converter
6. Add process: Auto Trim/Crop, trim silence from ends, bump up fade in and out to 500 ms
7. Add process: Volume, leave at 0 dB
8. Start the batch job

I contacted tech support on both of these as they are reproducable and serious.

Subject:RE: Possible SF8 Bug in Batch Converter

Reply by: mpd

Date:4/15/2005 6:05:18 AM

I heard back from Tech Support last night about this:

"Unfortunately there isn't a workaround at this point. The issue actually involves any plug-in that changes the length of the file, not just the Auto Trim/Crop. This one is very high priority, so it will be one of the first issues to get fixed."