IIRC, Apple also sold AAC as requiring lower bandwidth for the same quality, but I don't recall when that was.
(Not sure if the video clarifies this point since I cannot watch it right now.)
But let's say Amazon decides to go with VBR to save space and download speed, now there's an easy way for Apple to attack Amazon. "We never dip below a certain quality. Amazon does. We care. Amazon doesn't"
Maybe that ad/slogan works, or maybe it doesn't. But if you're Amazon would you be willing to risk some weird consumer backlash over it? And if you're Apple it is an easy point to attack, and if it doesn't work, no harm no foul (and then secretly also switch to VBR and announce it at the next Apple conference!)
I have noticed that older pre-2.0 versions of Mixxx would sometimes get glitchy (warbly) when using the pitch-correction feature (key lock, I think is the name in the UI), but, I don't think it's related to VBR vs CBR, but I never thought to check.
The only time I've noticed an audible sound quality problem when DJing was with low bit rate (usually 128kbps) files.
The warbling definitely sounds like our pre-2.0 time stretching algorithm to me. The new one in 2.0 is much better.
Anyway, I really appreciate your work on Mixxx. I don't get to do audio or music work much these days, but I do occasional DJ gigs (mostly for free for non-profit orgs and such, but sometimes they're paying gigs), and it's been a whole lot of fun.
And, to be clear, the article is making a guess that Amazon or Apple are imposing a minimum bit rate to insure some lower bound on file size. I don't think there is really any solid evidence that Amazon or Apple are making decisions based on trying to make file sizes bigger to convince consumers they're getting "more value". I took exception to the premise, which is why I commented above. I don't believe Apple and Amazon are making decisions based on trying to increase file sizes, and I find it weird that the article suggest they are. I believe they are trying to maximize audio quality at smaller file sizes. Evidence seems to indicate that is what is happening.
And, we've come full circle to the point of my initial comment. I don't think the argument he's making about maintaining large file sizes is backed by evidence or a particularly good understanding of consumer behavior/preference. I do think his guesses about the Netflix algorithm are interesting, but his digression into consumer behavior is less so, IMHO.
That has led to a consumer revolt of sorts, for people who care about audio. That's not a large enough group to make a difference to the big record companies, but it is large enough that catering to them is a good business model in itself.
128kbps mp3 files do sound pretty bad, especially on the high end and during very dynamic parts. It is audible to me, regardless of the quality of the original recording and its mastering.
And, while we're talking, I'll point out that the loudness wars began roughly 20 years ago, so you may need to go back to an even earlier mastering to get the really good stuff. Certainly it was more pronounced through the late 90s and 00s, but I remember the first few records I bought that suffered badly from over-compression, and they were released around 1994-1996. The multi-band compression that has killed many great recordings began to see usage around that time as well, though it peaked much later (it was expensive to start with).
I'm not sure if it has ever happened with bitrates in audio files, but the megapixel war comes to mind. 36 MP in a point-n-shoot? Must be better than the 12 MP in a Canon 5D DSLR since 36 is way more than 12.
You can tell if you play them next to each other, on an expensive club sound system. Other than that, you probably can't.
That said, a 128kbps mp3 through a really loud system tends to sound harsh. It is definitely audible, even to untrained ears. But, anything above 192kbps, or so, is fine and any flaws that might be audible in an ideal listening environment are lost in the general noise of the club environment.