Why do Wav and Flac Files Sound Different?


This article is from 2016, so outfits like JRiver may have developed workarounds for the metadata/sound quality issues sussed out below. Inquiring minds want to know.

Why Do WAV And FLAC Files Sound Different?

"Based on these results, we attempted to pinpoint which section of the metadata might be responsible. Since the cover art file associated with the metadata is the largest contributor to the metadata header size, we began by examining the effect of deleting cover art prior to the WAV-to-FLAC-to-WAV conversion protocol. This proved fortuitous, as our first suspicion proved correct."

bolong

Wav vs Flac

Here is a somewhat more nuanced take on the issue. The author is responding to the article that started this thread.

I should stress here that I am not playing my files off of my computer - merely using the computer to store these files and then burn CD's to them which are then played on a Jay's Audio CDT3 Mk3. I am using a 2 year old Dell. What more interests me is the interaction of the computer buffer and perhaps more specifically the buffer involved in CD burning with the quality of the resulting burned CD.

By the way, whether an improvement or not, the "cover art" file is now deleted by me before copying the downloaded Quobuz .wav files to JRiver. I miss the visual tag of cover art in the JRiver front page, but the text caption is sufficient for locating files.

 

WAV files are so old that there was never a schema developed for them to hold metadata internally.  FLAC is merely a "container" for the WAV files having more robust places in the design (schema) to hold metadata, things like track name, number, and yes, cover art. Even lowly mp3 files have by design, places to put that data. If your streamer is working right, it will use the metadata but there should not be any sound artifacts from that metadata being present because they are not INSIDE the WAV file that is decoded. Free LOSSLESS Audio Codec is the nature of the beast.  The same can be said for Apple's ALAC. I've encoded wav files as level 8 FLAC (the best compression that can be done and still be lossless when decoded) and level 0 (no mathematical compression at all) and can hear no difference in my headphones. But then I'm 65. Still, by design, these things should have no sonic difference at all. Even whatever chips were in a lowly 1998 PC could handle the decoding without issue, let alone modern, much faster chips in phones, and well-designed streamers. 

A little while ago I downloaded a CD quality CD's worth of music (Sarah Janosz) from Quobuz. Once on my hard drive I deleted the "folder" (image of Janosz) from the list of tracks, uploaded the files to JRiver and was interested to see upon opening the file in JRiver that the "folder" image was still active and came up as the usual jpeg in JRiver where it acted as the visual header for the group of files. It would appear to a layman such as myself that this file is permanently embedded in the download even if "deleted." Any ideas on how to really and truly remove it before burning a CD of the tracks?

If FLAC levels 0-8 are all lossless, why are there so many FLAC choices, and why would anyone ever use anything but level 8?

Thanks,

aldnorab

@bolong You can have the image "embedded" in each track as FLAC allows it, in fact you can put a different image in each track of a "disc". If you try any tagger (I use Tag Editor) you will see that and you can also delete the image for each track if you want. When you use a program like JRiver, Audirvana, Roon, ..... to play the files they can work in two ways: choosing the "folder / disc" image over the track image or the contrary.

If one the images is missing, they will choose the one that exists. And if there is no one, no image will appear.

Regarding your question: if you burn your CD (physical disc) as a real CD the tracks are transcoded to WAV and the images are not included in the process.