Error when using Sound Forge as Vegas Audio editor

chap wrote on 12/13/2012, 7:32 PM

One of my favorite features of Vegas has been that you can right click an audio event and open it right in Sound Forge, then apply any effect, save it, and it saves as a take in Vegas.

but since upgrading to Vegas 11 (and 12), when I open a copy of an audio event in Sound Forge, often (not always, but around 60% of the time), it opens and I can edit it, but when I click save it says:

An error occurred while saving one of more files.
The file could not be created.

I have tried changing the temp file directory, I have tried many things, but it doesn't have a consistent fix.

Does anyone else have this problem?

Comments

Woodenmike wrote on 12/14/2012, 10:12 AM

Yeah, I use that all the time and often get the same eerror message...for some reason, when you import into sound forge, it doesn't seem to like a marker at both ends of the file, so I usually delete the one at the end and then it behaves. if there is still an issue, I just "save as" and then pop that version into the Vegas project. I have better luck overall when I "open a copy" of the file rather than the file itself...the only down side of doing this, is if you have trimmed the file in Vegas, and then try to expand it after editing in sound forge it cannot expand beyond what was edited in SF.

VanLazarus wrote on 2/3/2013, 1:06 AM

This is related to issues with file ownership. The solution I've found is, that after making your edit to the audio in Sound Forge, switch back to Vegas, wait a second, switch back to Sound Forge, and now you can save the file.

Unfortunately, there now seems to be a new error with Vegas 12 b486, where one can't even open the audio file in Sound Forge. Investigating...

Mindmatter wrote on 2/3/2013, 4:22 AM

I recently had a similar issue, when saving the file in SF, I got a " no template was specifified " error. In my case, the solution was to use " open as copy in soundforge" to make it work as it used to.

Woodenmike wrote on 2/5/2013, 4:04 PM

I have rolled back to V12 b394 because of this, and other issues using the project media tab in b486...b394 has been working for me quite well except for needing to keep the GPU off while editing and turning it on for rendering. I'm thinking that some of my issues have been with material on different drives with different data streams coming into Vegas at different speeds...the freezeups occur while attempting to use clips from slower drives (perhaps they spin down while just sitting there?). going back and forth to Sound Forge from Vegas is a large part of my work flow, so the issues with b486 caused me to roll back.

gripp wrote on 2/15/2013, 10:21 AM

I too have now rolled back to b394 from b486 because of the Sound Forge problem.

I' m not sure what, if any, benefits b486 brought me, but the SF problem was a stopper.

Hope they get this sorted out in the next release

Laurence wrote on 2/15/2013, 1:30 PM

I have that problem, plus another one where I can't use Sony NR because of some sort of registration issue unless I run Sound Forge as an administrator. Unfortunately I can't call SF from Vegas when SF has the "run as an administrator" tab checked. I haven't been able to go back and forth properly since V10.

R0cky wrote on 2/15/2013, 2:32 PM

+1
rocky

dxdy wrote on 2/15/2013, 2:51 PM

Is everyone having these issues using the same version of SF Pro? While I have not yet upgraded to v486 (waiting to finish an big project), I have not had these issues.

wwaag wrote on 2/15/2013, 11:50 PM

Me too! Rolled back to 394 because of the same SF issues.

wwaag

Grazie wrote on 2/16/2013, 2:58 AM

Nope . . . No repro here in B486 . . .

1/- Right Click on Audio and select Open Copy in SF

2/- SF fires-up and the Audio is there to "edit"

3/- Save and close, returns back to B486

4/- New Take appears in B486.

These "non-repros" are a true barrel of eels to sought out . . . .

Grazie