Help - Search - Members - Calendar
Full Version: Adobe audition 1.5 help
Hydrogenaudio Forums > Hydrogenaudio Forum > General Audio
The Bob
Okay, so i'm still somewhat new to music making, etc... So, when going to save my music, every once in awhile there will be a music file that doesnt' save correctly, and it sounds awful. Like, it's all crackly and bubbly sounding and...yeah. Is there any way to fix this kind of problem?
AndyH-ha
What is the source of these music files? How do you get them into Audition?

Exactly what do you do to save them? Before saving them?
DVDdoug
This is a guess... It might be clipping (distorted flat-topped waves, caused by trying to go over the digital maximum).

Most audio editors use floating-point storage, which gives you unlimited headroom. But, most file formats use integers. So, you can end-up introducing clipping when you save. Once the file is clipped, it cannot be properly restored.

I don't use Audition, but I believe there is a way to check the peak and average levels*. If your peak is above 0dBFS (zero decibels full scale), it will be clipped when you save. You can prevent that by normalizing before saving, which will set your peaks to exactly 0dB.

* Of course, you need to check those levels before you save... before the file is distorted... If you open and check a file (i.e. a "standard" 16-bit integer WAV file) and it has 0dB peaks, it's either clipped or its already been normalized. Most commercial recordings are normalized (after compression & peak limiting).
pawelq
QUOTE (DVDdoug @ Mar 31 2009, 14:26) *
Most audio editors use floating-point storage, which gives you unlimited headroom. But, most file formats use integers. So, you can end-up introducing clipping when you save. Once the file is clipped, it cannot be properly restored.


A loating-point file exceeding 0 dBfs would sound terrible when played from Audition as well - the peaks would get truncated on their way to the sound card. And Audition may save files to 32-bit floating-point wave that would preserve that information.

We definitely need more data: which area of the program are you saving from (Edit View vs. Multitrack View)? To what format? And checking levels with Amplitude Statistics wouldn't harm.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.