I am not sure if I had the same problem as snicholshms, but I lined up a bunch of wav files today and got a clipping noise at the end of each clip which did NOT occur if the clip was a standalone or the last in the series.

Bottom line was I CXL'd the project because I could not figure out the problem.

There's a BIG difference in quality between .wav files and MP3 files. Why would a professional want to down grade the audio? That doesn't make sense.

There is NOT a BIG diff between quality in a WAV and an MP3 if a Professional knows what he or she is doing.

I have been producing Professional audio cd's, video snippets, interative CD's including both music and video for years......

If your MP3 file is converted correctly and using (at least) one of the higher bit rate settings - the resulting file is indistinguishable from a WAV file.

But I think you are missing the point.

There are different formats (audio and video) that a person can use as tools to get to the final product. The final product is what really matters....not just the tools you use to get to that final product.

Okay...so stick with WAV files. No biggie. Just don't put so many on one event line.

Last I looked - you can have ... uh....I think something like....unlimited event lines....so use them. Or....here is a though -

...mix down your audio from multiple event lines....since you are doing audio lay out...into one rendered event. You can do this is Vegas Video....or Vegas Audio....or tweak it in SoundForge and reinsert into your project. The combination is endless...and dare I say again - a no brainer.

IMHO people get too stuck on the mind numbing small points and never allow for growth.

That is the quality difference between a rank amateur and a professional.

"I am not sure if I had the same problem as snicholshms, but I lined up a bunch of wav files today and got a clipping noise at the end of each clip which did NOT occur if the clip was a standalone or the last in the series.

Bottom line was I CXL'd the project because I could not figure out the problem."

From a technical support/trouble shooting point of view.....I think you may have missed something here - or haven't supplied enough information.

That is....you are trying to describe two different states of your project - but you don't continue to allow for the difference between the two. That is to say...

State #1: ...lined up a bunch of wav files today and got clipping

State #2: ...did not occur if the clip was a standalone or the last in the series

What is the difference between state #1 and state #2? Are the clips over lapping? Are they "butt up" against each other?

If the answer is the latter....have you zoomed in to the clip to see if there is any other difference that may have occured at the end of the clips that don't occur at the end of the last clip in the series?

See....what is happening is you are wrapping your brain around a result (wav files lined up) without looking for a cause or difference.

If there was no difference from when the clips are lined up or separate - then it must be the WAV file (or how the software uses WAV files). Very fuzzy logic.

Does it do the same thing with MP3 files, or other audio type file?
Does it have something to do with the files being lined up on the event vs stand alone?
Do you get the same result if you use multiple event lines for audio editing?

"That is the quality difference between a rank amateur and a professional. "

That's exactly what I would say about someone mixing audio using MP3. Oh well, as long as we're all happy...

Hi Kameronj-

Clips are butted, problem does not occur with mp3, too lazy to convert it and shouldn't have to IMHO.

At any rate we were just fooling around with a promo. Maybe I will reload VV3 and try it that way...

The problem I am aware of happens with certain systems when you have two AVI or WAV files next to each other without overlap, and without trimming. In this case, the audio glitches for the first 1-3 seconds at the beginning of each event. This only happens during playback from the timeline; it is fine once rendered and played to the camera. If the audio is on a different timeline, the problem doesn't occur, so one workaround is to place audio from each event on alternating audio audio tracks (e.g., first event on track one, second event on track two, third event back on track one, etc.).

I think SOFO is aware of this and hopefully will provide a fix for it in a future release.

Everybody RELAX! Here's some good news from SonicMatt:

"The answer is:

*** SOON ***

We are working on an update which will address a number of concerns brought up by our customers. When we feel the update is stable and ready to ship, we will ship it.

Our policy is to not announce product release dates or features in advance of actually having the product ready to go. I realize this leaves our customers without answers to questions like this, but it also allows us the flexibility to provide the best update possible."

Enough said! Thanks for the update Matt!

Glad there is a fix in the works. I use Vegas (now back to 3 since 4 is broken) for multi-track post production for CDs. Typical selection has a minimum of five tracks, each on a separate track in Vegas. Allows for sonic placement, appropriate track filters, etc.

Projects that were fine in V3 and broken bad in V4. V3 will play 15 track projects properly even if I have a fair number of track effects and bus effects. When I get to 22, and have track and bus effects I am pushing the wall.

Had to revert back to Vegas 3 to get work done.

Oh, conversion to an MP3 is not an acceptable solution in this case :-)

Cool.

You posted a valid question. I can certainly understand SoFo not wanting to announce a rev before its time. Much of the other comments were not particularly helpful.

Thanks for sharing the encouraging news.

-Rex

1. Can someone tell me why .wav is better than .mp3 ?

2. I have a PC and want to get a Mac soon. Wouldn't it be better for me to transfer .mp3's to the Mac instead of .wavs?

Wave table files represent instantaneous values of the audio signal, MP3 involves compressing the data to reduce the file size. I guess the closest comparison would be bitmap images versus jpeg. At high sampling rates and with good encoders I'm told MP3s can be of excellent quality, they get a lot of bad press because that's not how they are normally used.

I guess it comes down to how good you want your audio, I was horrified to find a Mac user working with aiff files, 12bit 44.1Khz. Thats fine for delivery (same as whats on CDs) but if you try doing anything with it the quality goes down very quickly.

Without boring you with science pretty much every time you do arithmetic on binary numbers there is a single bit error involved. So if you reduce the level of a track thats only 12 bits by 1 dB a bit gets lost. Render it out like that and bring it in again and bring the level back up 1 dB, that bit doesn't come back!

Now you can see why WAVs are 16 bit resolution, the pros will disagree with me on this, but at least you can afford to loose 4 bits of resolution before you even get to CD quality. With 24bit/ 96K you're really in front.

I'm certain I've missed a few crucial points but hopefuly I've captured the gist of the story for you.

How do you get 24 bit 96k?