Saving edited backing tracks

The subject of bit-rates for backing tracks seems to have got a few of you asking some other related questions about this…

Hi Kenny,
Having read your blog entry about mp3 encoding (not that i know anything about it) I happened to look at my own tracks, only to find that all mine were at 256kbp. I use soundforge 8 for editing and saving my tracks. When I download a track it is saved in “My received files” I then load it into soundforge to edit, ie to cut silences at start and end and to adjust volume, once that is done I save it to “Backing tracks” folder and then when required to a SD card if playing in my SD player or into Onstage Performer if transfering to my laptop. Thanks to your article, I am now in the middle of changing all my tracks to 128kbp as the files will be half the size they were. I do seem to have one problem though with soundforge and I don’t know if you can help me? I’m having a problem saving any editing. If I change the volume so as not to “peak” the edit process does it’s thing. Then if I play the track the volume change has taken effect, so I click on “Save” when the “Save” process has finished the track re-appears in the frame but the “Save” hasn’t worked, as the peak lights up on the volume again. Any idea’s?

Hi Gordon
Yes, re-encoding your backing tracks from 192Kb/s to 128 Kb/s will allow you to double the number of tracks you can store on your SD card.
If you are having trouble saving your edited file in Soundforge, then try using “save as…” instead of “save” and give it a new filename.
Sometimes programs have issues over-writing files that they still have opened within the program, so saving it as a new file with a different name usually does the trick. As an aside, this generally applies to any file in any program that you’re trying to over-write and I suggest you always use “save as…” instead of “save” – if nothing else, it lets you go back to the original file if for any reason the over-write doesn’t work or you make a mistake and need to redo something.
If using the “save as…” command doesn’t solve the problem, then you’ll have to delve a bit deeper I’m afraid. Like most software problems, there’s usually 3 common problem areas to look at:
#1. The “problem program” installation has become unstable. Re-installing it usually fixes the problem.
#2. Windows itself or any other programs running on your computer that use the same components as the “problem program” have become unstable. Re-installing Windows, the “problem program”, or any other programs which share components with the “problem program” usually fixes the problem.
#3. The “problem program” doesn’t function well with your particular operating system. Compatibility problems with Windows running third party software are commonplace because Microsoft do not let anyone know their source code so only Microsoft products can be absolutely guaranteed to work well on Windows computers (although many critics claim even Microsofts own products often have issues running on Windows)!
So, in a nutshell, if the “problem program” worked fine before, but has now mysteriously stopped working, then it’s most probably #1 or #2 above.
If the “problem program” has never worked properly, then it’s most probably #3 above.
Troubleshooting software problems is often like looking for a needle in a haystack.
Generally the makers of your software and Microsoft don’t help – the software makers blame Windows for problems and Microsoft blame the software makers.
The poor users usually find themselves in a catch-22 situation where they’ve got problems with a program that doesn’t work but no-one wants to help them or accept responsibility for it.
Welcome to the world of Windows (and by the way, Apple Mac are not much better despite what Mac afficianados would try to have you believe)…