When you hear audio engineers talk about coded audio...
Inevitably you’ll hear conversations centering around “coding artifacts” in one way or another.
Before going any further...If you are landing directly here from somewhere else, I suggest you check out the first article on this topic before continuing!
What are “coding artifacts”, and what exactly is it that we are hearing? Listening for artifacts involves knowing where to listen. In this case, one must listen in the background. It is also easier to hear artifacts if you have a non-coded version of the audio to compare with.
Why is this an issue? It helps to know what happens to audio when it is converted to a (permanently) "lossy" data compression format. What is a "lossy" compression format?
When, for an example, a 128 kilobit mp3 file is created, over 90% of the original audio data is PERMANENTLY thrown away (permanently lost) to make the audio file smaller. This is useful (and vital) for shipping audio across the internet (such as for a podcast), but should NEVER be used as high quality source material if you can help it. Always save your files as .WAV, or .AIFF files when producing your content. Convert to MP3, MP4, or AAC ONLY when producing the FINAL package to be sent to your audience.
HINT: Saving a .MP3 file as a .wav does not restore the original quality. The audio is permanently altered once it becomes a lossy audio file.
Let’s turn to our audio examples to demonstrate what happens when a file is converted to a "lossy" format..
This file has no coding (Linear). It is the audio as produced in our studio.