Community Forums Archive

Go Back

Subject:SUGGESTION to improve 'Edit in Sound Forge'
Posted by: Snappy
Date:11/5/2003 8:23:59 PM

Right now the most common way i use this feature is: 'Edit in Sound Forge', do some edits, then 'save as' from Sound Forge, then import back into Acid via the track's Replace command. I do this because often i want to make non-destructive edits to my sample library - a 'chop' that works for one song may not work for another... So i 'save as' in order to maintain the original file's original state.

i want Acid to always* assume i'm going to want to save a _copy_ of the original file, and to automatically re-load that new file in place of the original file.

(*some people might not like it, so it would be nice to have a global option to turn it on/off)

example: i want to use 'Edit in Sound Forge' on a track based on the file 'kick.wav'. Acid immediately makes a copy of the file, called 'kick_edit.wav'**, and automatically changes the track to now point to the file 'kick_edit.wav' instead of 'kick.wav'. (at this point, if the track was using the default track name, it should be updated to reflect the new filename; but if the user put in a custom name, leave it alone***) then 'kick_edit.wav' would be opened in Sound Forge for editing, edited, 'saved' (not 'saved as'!), and when the Acid window regained the focus, the track would automatically refresh to the edited file, ready to rock! the original file is 'dropped out of the loop', preserved in its original state.

(**a time/date stamp added to the filename would be nice)
(***or replace with the new filename - leave it up to user's Preference)

THANKS! =)

cc: Product Suggestions

Go Back