|This is the talk page for discussing improvements to the FLAC article.|
|This article is of interest to the following WikiProjects:|
|Threads older than 120 days may be archived by.|
The line "The Android operating system has supported native FLAC playback since version 3.1." Seems to imply that 3.1 was the first Android version to support FLAC. However, my current phone is running gingerbread (version 2.3x) which I assume is earlier than 3.1 and it supports native flac perfectly fine. Am I missing something here? — Preceding unsigned comment added by 126.96.36.199 (talk) 22:10, 19 August 2012 (UTC)
More detail, continued
In my experience, FLAC files convert to cda files when ripped to a CD-R, but then 'bounce back into shape' and become FLAC files again (and thus lossless the whole time, I assume) when copied back to disc. If someone could explain that process a bit, that would be great. See the Compact Disc Audio track article, which should have similar info added to it. Thanks in advance. Anarchangel (talk) 23:39, 28 February 2012 (UTC)
The article says: "FLAC allows for a Rice parameter between 0 and 16." I don't know what this means -- and it will be very obscure and unhelpful to the average reader.
It is important to offer readers a practical understanding of the quality parameter in common usage:
- "The quality parameter for FLAC refers to the quality of compression, not audio. The audio will stay lossless but you get a better compression with higher quality. Higher quality will take more time to compress however.
- Free Lossless Audio Codec (FLAC): FLAC is a popular lossless, freely available open source encoder.  Quality Settings: 0 - 8. Sets the quality of compression (and not sound, which is lossless), 8 meaning most compressed/time/effort."
These resources are relevant and helpful:
- What differences among CUETools outputs? libFlake/libFLAC/flake/FLACCL, Moderation—derailed into a verbose discussion about compression levels
- " Compression levels
- libFLAC has compression levels 0..8, where 0 is the fastest and 8 provides the best compression ratio. libFlake and FlaCuda are tuned differently, so libFlake -5 might in fact compress better than libFLAC -8. They also support additional compression levels 9-11, however their use is not recommended, because those levels produce so called non-subset files, which might not be supported by certain e.g. hardware implementations.
- FLAC specifies a subset of itself as the Subset format. The purpose of this is to ensure that any streams encoded according to the Subset are truly "streamable", meaning that a decoder that cannot seek within the stream can still pick up in the middle of the stream and start decoding. It also makes hardware decoder implementations more practical by limiting the encoding parameters such that decoder buffer sizes and other resource requirements can be easily determined. flac generates Subset streams by default unless the "--lax" command-line option is used."
In sum, readers need to understand that the quality setting will affect how long the compression takes, will generally lead to a relatively small difference in compressed file size, have very little impact on decoding time, and not impact the "lossless" aspect at all -- unless taken to such an extreme that incompatibilities might arise. -188.8.131.52 (talk) 15:16, 12 February 2013 (UTC)
Inconsistency in compression rate
- Do you mean it has to say 40-50% to be correct? C'mon +-10%. --Kays (talk) 22:28, 15 October 2013 (UTC)
Reference to Wavpack removed, since it uses only public domain technologies
From the Wavpack website:
WavPack employs only well known, public domain techniques (i.e., linear prediction with LMS adaptation, Elias and Golomb codes) in its implementation. Methods and algorithms that have ever been patented (e.g., arithmetic coding, LZW compression) are specifically avoided. This ensures that WavPack encoders and decoders will remain open and royalty-free.
Additionally, I have confirmed with one of the developers that this status is current.