help with audio render out compatibility

megabit wrote on 9/25/2008, 3:29 AM

I cut an audio track, ripped from CD, to create a background for narration. After syncing everything, I also had to cut off the very end of the track so that a valid "musical phrase" is created; now it lacks release and ends abruptly. Since most of the audio part is done by our sound engineer, I rendered a fragment into Microsoft Wave, and e-mailed it to him.

Unfortunately he cannot open it in ANY of his several audio editors, including WaveLab and Soundforge (I can open this file in Soundforge here without problem). I tried re-sending with
different settings (like changing from 16bit to 24bit, changing the fragment length, using other formats like AIFF, etc) - to no avail: he says his editors don't even "see" my file, and cannot display its format etc !

Would a header be missing, or not encoded properly by the new Vegas (of course I tried both the 8.0c and the 8.1)?

What's interesting, we already exchanged sound files successfully, with the only difference being that those were from my EX1 sound (not a ripped CD), and I was rendering in Vegas 8.0b.

I'd think it's Vegas 8.0c / 8.1 bug, but I also tried saving the fragment in SoundForge - didn't help.

Any suggestions?

Comments

farss wrote on 9/25/2008, 3:34 AM

Did you get my email, sent two several hours ago with a read reply request.

Bob.

megabit wrote on 9/25/2008, 3:55 AM

No I didn't Bob. But basing on previous experience with our servers (which apparently don't like each other), it's a question of time....It will arrive, sooner or later.

Thanks, anyway!

blink3times wrote on 9/25/2008, 5:03 AM

It can't be a bug. I export M$ wav files regularly from Vegas into Adobe Audition.

The problem I run into sometimes is the 5.1 sound setting. For me vegas defaults on 5.1 sound so when I bring up my wav template to render, it's also set to export as 5.1 and I forget to switch it over to stereo.

Of course my wav files are from video and not from ripped cd but I fail to see how that would make a difference

blink3times wrote on 9/25/2008, 5:09 AM

Well.... I was thinking maybe some kind of DRM thing.... but I just ripped a selection from a cd, chopped it up, exported as M$ wav 16bit, 48000 stereo.... it opens fine in AA, and plays fine in all three of my players.

I would be more inclined to believe that some thing is going on with some ones' email program or server..... may be junk mail filters or some kind of virus protection kicking in?? Try changing the extension to JPG then email it and have your guy change the extension back when he gets it.

Former user wrote on 9/25/2008, 6:32 AM

Are you sure you saved it as a MS WAV file. There are other wav file types that are not compatible.

But otherwise, I would say the file was chewed up by email. Is it bigger than most files you send?

Dave T2

megabit wrote on 9/25/2008, 7:23 AM

Thanks guys for your replies. The reason proved to be trivial: my sound engineer's software doesn't like Polish national characters in file names!

Of course, it goes without saying that the person who first suggested it to me (not to mention - edited the piece for me, and sent it back ready to use) was...

...yes, you guessed right: Bob!

Bob, you're the Best.

Robert W wrote on 9/25/2008, 12:26 PM

Maybe worth me adding another filename issue here. Quicktimes .movs don't like fairly long file names. I think you need to keep them under 20 characters to be safe, otherwise you get failed renders, lock ups and crashes.