File type changed when using SAVE -Sound Forge - PC

Subject:File type changed when using SAVE Posted by: DJ BrianBASS Date:9/19/2012 12:21:05 PM Hello. I recently upgraded from Sound Forge Audio Studio 9 to version 10. Since then, whenever I use the SAVE feature for work I have done on a track, it changed the file bit-rate(say an mp3 from 320 to 256). Is there some setting I need to change? I thought SAVE simply kept the previous file type, or it did with version 9? SAVE AS is for changing file name or format.
Subject:RE: File type changed when using SAVE Reply by: musicvid10 Date:9/19/2012 6:33:13 PM Sound Forge will render your .mp3 each time you save it. Proper workflow is to save as WAV each time, until you are ready to render your final .mp3. That way, there are no losses and no changes except the ones you make.
Subject:RE: File type changed when using SAVE Reply by: Chienworks Date:9/19/2012 8:34:43 PM You had probably set up a 320Kbps template under version 9 and left this as the default MP3 template. Sound Forge does not, and never has, used the source bitrate as a guide for the bitrate while saving. As musicvid says though, you should only save as MP3 the last time you are editing a file, and only after you've already saved a WAV copy as well.
Subject:RE: File type changed when using SAVE Reply by: Relayerman Date:8/4/2013 12:05:49 PM I have the same problem. The problem is that if you open an MP3 to edit and use SAVE instead of SAVE AS it will save the MP3 back at 256 Kbps because that is Sound Forge's Default Template for MP3. You can us SAVE AS and then create a CUSTOM template with the bit rate you want, but it will only use the custom template with SAVE AS and not with SAVE. It sucks that the Default Template cannot be changed. This is a design flaw in my opinion. Users should be able to either specify the parameters for the Default Templates or be given the option to always use a user-designed template, at least for non-WAV files. The SAVE AS function is very slow at saving the file back compared to the SAVE function and does require a few more clicks. BTW, this is still flawed in Sound Forge Pro 11 as well.

Subject:File type changed when using SAVE

Posted by: DJ BrianBASS

Date:9/19/2012 12:21:05 PM

Hello. I recently upgraded from Sound Forge Audio Studio 9 to version 10. Since then, whenever I use the SAVE feature for work I have done on a track, it changed the file bit-rate(say an mp3 from 320 to 256). Is there some setting I need to change? I thought SAVE simply kept the previous file type, or it did with version 9? SAVE AS is for changing file name or format.

Subject:RE: File type changed when using SAVE

Reply by: musicvid10

Date:9/19/2012 6:33:13 PM

Sound Forge will render your .mp3 each time you save it.
Proper workflow is to save as WAV each time, until you are ready to render your final .mp3. That way, there are no losses and no changes except the ones you make.

Subject:RE: File type changed when using SAVE

Reply by: Chienworks

Date:9/19/2012 8:34:43 PM

You had probably set up a 320Kbps template under version 9 and left this as the default MP3 template. Sound Forge does not, and never has, used the source bitrate as a guide for the bitrate while saving.

As musicvid says though, you should only save as MP3 the last time you are editing a file, and only after you've already saved a WAV copy as well.

Subject:RE: File type changed when using SAVE

Reply by: Relayerman

Date:8/4/2013 12:05:49 PM

I have the same problem. The problem is that if you open an MP3 to edit and use SAVE instead of SAVE AS it will save the MP3 back at 256 Kbps because that is Sound Forge's Default Template for MP3. You can us SAVE AS and then create a CUSTOM template with the bit rate you want, but it will only use the custom template with SAVE AS and not with SAVE. It sucks that the Default Template cannot be changed. This is a design flaw in my opinion. Users should be able to either specify the parameters for the Default Templates or be given the option to always use a user-designed template, at least for non-WAV files.

The SAVE AS function is very slow at saving the file back compared to the SAVE function and does require a few more clicks. BTW, this is still flawed in Sound Forge Pro 11 as well.