Sound Forge 7b Messes up HDV???

mjroddy wrote on 4/19/2006, 4:42 PM
I am building a :30 spot shot in HDV. Had it pretty well built and then was going to clean up my audio. I "Opened In Sound Forge" (7.0b) and Normalized, Wave Hammered and Saved. I did that to about 10 clips. When I went back to watch the rough cut, those clips I "fixed" in SF were mind-bogglingly jumpy and unusable. They were taking randome frames from within the clip and re-arranging them in a - shall I say, "unique" order.
I restarted Vegas (6.0c Build 153) to no avail. A reboot also had no effect.
The few clips I DIDN'T take into SF play fine.
Whu hoppened?

Thanks!

Edit: Forgot to mention that I'm using the Prospect HD Cineform codec.

Comments

farss wrote on 4/19/2006, 9:56 PM
Me thinks SF might be having an issue with the way the audio is encoded. Might have been an idea to render the audio out as 16/48K .wav first. Two advantages there. Firstly if something does snafu the audio you've always got the original and secondly you're working with something that SF can handle without any drama.
mjroddy wrote on 4/19/2006, 10:40 PM
Definitely.
I've always read that you work on a COPY of the original. That's the pleasure of non-destructive editing.
Well, I've learned my lesson. I was just wondering if anyone else had had that issue and if I made a mistake when I should have known better.
So if there's anyone else out there thinking that you might just as well work on the original HDV file in SF, I'm here to tell ya... reconsider.
farss wrote on 4/19/2006, 10:45 PM
Yes SF makes a temp copy of the file, that is UNTIL you hit Save. SF is a destructive editor.
Bob.
mjroddy wrote on 4/20/2006, 9:38 AM
"SF is a destructive editor."

Understood. This much, I knew.
I just didn't know it destroyed the video.
I'm pretty comfortable with what I do in SF, so I don't mind the destructiveness. But when it jounced the video files, that's what surprised me.
Thanks very much for the help.
busterkeaton wrote on 4/20/2006, 9:54 AM
When you edited in Sound Forge, did you "open a copy in Sound Forge" or did you "open in Sound Forge."


Also when the problem occurred, you were no longer working in mpeg, but Cineform avi? I can see the mpeg possibly causing issues since it is long GOP, but avi causing problems is wierd.

Did you have quantitize to frames turned on? Is it possible you made some cuts at the sample level and not the frame level?
mjroddy wrote on 4/20/2006, 7:42 PM
When you edited in Sound Forge, did you "open a copy in Sound Forge" or did you "open in Sound Forge."

Was NOT working on a copy :-(

you were no longer working in mpeg, but Cineform avi?

Correct. I digitize straight from Prospect HD.

Did you have quantitize to frames turned on?

Heck no! ;-)

Is it possible you made some cuts at the sample level and not the frame level?

No... SF just made a mess of my files. As stated above, the only files that got corrupt were the ones I took into SF. The files became a mess with random frames here and there and all over. The files were completely unsuable. 7 clips in total. It wasn't a tragedy, but it did set me back a day. But I did learn a lesson, as stated above.
Thanks for the thoughts.
farss wrote on 4/20/2006, 7:59 PM
Sorry I hadn't thought through what could happen opening a video file in SF, that's sure one big trap. I've only opened an avi once in SF7 and I've never saved one.
My advice to just render the audio out as a separate .wav sounds good except then you've got to pray you can keep that separate file in sync with the original vision, no real bullet proof solution and doing the 'Open Copy' thing is fine for audio BUT if it's a big avi that'd take some time and eat a lot of HDD.

Guess Madison should take a look at this issue however it might be a big ask, getting SF to cope with every video codec correctly.

Bob.