9 ms·
Why don’t podcasts use VBR MP3s? Because iOS and macOS don’t accurately seek them
- kalleboo 10y agoThat's MP3s. AAC/MP4 has better efficiency, and I can't imagine any devices in 2016 don't support it...?
- colejohnson66 10y agoIf only OGG support was more common :(
- DarkLinkXXXX 10y agoOpus if the free software lossy codec of choice now, I think. It can be put in an ogg container though.
- TD-Linux 10y agoYup, .opus files are the Ogg container. While Opus is newer, both Opus and Vorbis are much better than MP3.
- dublinben 10y agoOGG Vorbis audio is supported by all Android devices, which is the vast majority of mobile devices in the world.
- wlesieutre 10y agoIs it a vast majority of podcast listeners?
- kalleboo 10y agoThat's MP3s. AAC/MP4 has better efficiency, and I can't imagine any devices in 2016 don't support it...?
- Analemma_ 10y agoIf you want more context to this, there's a lot more in the most recent ATP podcast (with timestamp link included in the article). Which kind of highlights a problem that I think is only going to grow over time - the general greatness of podcasts has one big black spot in that they're tough to share. I've seen so many discussions recently where there was awesome additional context or info in a recent podcast, but it was tough to share it with people in a format where they'd actually consume it. Whereas, if it had been in a blog, sharing would've been easy. Marco has the right idea with these timestamp links, but even that isn't perfect. A lot of people, especially technical people, won't even click on a non-text source, for better or worse. It's a shame that a lot of good information is becoming harder to share due to this. It's not even that podcasts are "locked down" or behind a paywall or anything, it's just that people often don't have the time or motivation to listen to them. I don't have a great solution to this; some kind of automatic transcription maybe?
- jsmthrowaway 10y agoThe solution is AAC, regarding which a number of prominent podcasters introduced FUD several years ago and now the podcasting industry is reluctant to give up MP3 -- unlike pretty much every other audio-related industry in the world. Seriously, MP3 was on its way out the year the Backstreet Boys released that song, and it surprises me that people still stick to it despite the VBR thing being a shitty problem in software that long. None of the solutions that Marco found are great, either. The solutions were dismissed decades ago in manners like this: http://www.foobar2000.org/FAQ#why_is_seeking_so_slow_while_playing_mp3_files http://www.foobar2000.org/FAQ#why_is_seeking_so_slow_while_p... Here's an example of podcasters talking each other out of AAC: http://podcastingguru.com/aac/ http://podcastingguru.com/aac/ His is not the first article I've read conflating "AAC" with some kind of "Enhanced Podcast" buzzword and then dismissing it based on the flaws of "Enhanced Podcasting." I left the radio industry in 2006 and we'd already transitioned all in-house production and delivery away from MP3 then. Probably 50% of the spots we received from external shops in 2006 were MP3. At some point you have to sit down with your listener and say that MP3 player you bought at Target in 2001 is holding us back, man. Marco is wrong on this one: it's AAC that would deliver all the good things that he wants, not VBR MP3. Fun fact: all AAC is VBR, in a manner of speaking, and it's way better than the hack that is VBR MP3s.
- zymhan 10y agoSo is this why I have weird problems fast-forwarding through some NPR podcasts? I'll find myself at the end of the podcast (as indicated by the time bar), but the podcast itself is still playing. Man, Apple really is neglecting podcasts. Reminds of an article I read recently - "Podcasts Surge, but Producers Fear Apple Isn’t Listening" http://www.nytimes.com/2016/05/08/business/media/podcasts-surge-apple.html http://www.nytimes.com/2016/05/08/business/media/podcasts-su...
- colejohnson66 10y agoIt's not Apple's fault; It's MP3 in general. Seeking in VBR MP3s is hard unless you decode the whole file and make note of the offsets for timing.
- derefr 10y agoAnd decoding the whole file, in turn, would be easy in any other use-case (iTunes does this for "gapless playback" calculation) but podcasts are quite often streamed, and only once. Probably the simplest "clever hack", if Apple wanted to fix this on their own, would be for all the podcast feeds registered through iTMS to get their files retrieved by the iTMS servers once, chewed through to calculate this information, and then all the calculated "keyframe" offsets injected as an opaque extra data field for each feed item of the iTMS-served podcast feed, where the Podcasts app can pick it up.
- mwfunk 10y agoThat article is a little misleading- it's actually about podcasters who want them to embrace/extend podcasting itself so that they (the podcasters, not the company) could better monetize podcasts. I can't imagine that the ways in which this might be done (DRM/subscriptions/user tracking/etc.) would appeal to HN readers, even if it would help the most popular podcasters make more money. IMO, benign neglect is the best possible situation for podcasting as a medium right now.
- MBCook 10y agoWhat are you talking about? Marco's been trying to avoid that, as opposed to what the Stitchers of the world are doing.
- Apreche 10y agoThat's not the only reason. We have been podcasting for over 10 years, and early on we tried to use VBR MP3s because we are teach people who know about that sort of thing. As it turns out, not everyone is listening using a modern device. When we tried VBR a significant number of people could not listen because their MP3 playing hardware/software of choice did not support VBR files properly. They didn't realize this was the problem. They just complained that the file was corrupted while it was working fine for everyone else. Also, lots of encoders, including Adobe Audition/Adobe Media Encoder, don't write the headers on VBR files properly. This also causes a lot of players to fail at playing them properly. https://forums.adobe.com/thread/1072786 https://forums.adobe.com/thread/1072786 When you make a podcast, maximum compatibility is the priority over audio quality and file size. So standard old MP3 it is.
- rincebrain 10y agoMy favorite bug about this was on an _ancient_ MP3 player I had (an EigerMan F20), which supported VBR MP3s...incompletely. It didn't support decoding regions with certain bitrates, so it would just silently skip them, leading to extreme confusion on my part.
- cmdrfred 10y agoI had a similar problem and never considered that...
- drzaiusapelord 10y agoVBR have been the red-headed step-child of MP3 since the beginning. I have no idea why, maybe it was difficult to write good encoders and decoders for it for back in the day. The few times I used them, I found trivial space savings compared to a CBR and to be honest I thought I could hear a difference (maybe its not humanly possible if the implementation of the encoder/decoder is good but what if the implementation is sub-par?). Storage and bandwidth are so cheap, why bother today?
- aianus 10y ago
- caiob 10y ago> VBR encoding is far more space-efficient and better-sounding than constant-bitrate (CBR) encoding While this may be true for podcasts, it's def false for music files.
- hyperbovine 10y agoHow so? Any VBR encoder could choose to produce CBR at the targeted average bitrate. The fact that it doesn't means that there is some better setting in terms of either space or quality.
- wolf550e 10y agoUsing a good encoder like LAME?
- astrange 10y agoVBR is a strict superset of CBR (= all CBR files are VBR), so this has to always be true. BTW, if you're going to claim any mp3 encoding is better sounding than another one, I hope you've done an ABX test.
- pierrec 10y agoThere are many degrees of VBR MP3 seeking support, and it's often surprisingly bad. In the case of Firefox's <audio> element, it was very poor (nearly unusable in my testing) until a few months ago: https://bugzilla.mozilla.org/show_bug.cgi?id=994561 https://bugzilla.mozilla.org/show_bug.cgi?id=994561 https://bugzilla.mozilla.org/show_bug.cgi?id=1163667 https://bugzilla.mozilla.org/show_bug.cgi?id=1163667 I had a fun time testing different js audio players, and going though their many confused bug reports, issues and threads all stemming from this. Even if Apple fixes their stuff, I still wouldn't use VBR MP3 for anything that's going to get streamed. There's always going to be some platforms that screw it up, and even a future browser introducing poor seeking seems very possible.
- eamsen 10y agoYou're correct about that there are different degrees of seeking support. Seeking VBR MP3 with perfect accuracy is trivial by forward-reading. However, this is obviously highly inefficient on long duration seeks. For instant seeking support, you need to (partly) depend on the optional VBR headers. This comes with its own set of issues, e.g., the most commonly used Xing header contains only 100 seek table entries, which may not provide enough resolution for large files. I'm still surprised about the complete lack of support for those headers in AVFoundation, since I would consider it a low-hanging fruit in terms of improving usability for the majority of use cases (excluding pod casts). Disclaimer: I've worked on MP3TrackDemuxer for Gecko/Firefox.
- Analemma_ 10y ago> However, this is obviously highly inefficient on long duration seeks. Is it that bad? On the podcast, Marco claimed that seeking forward through an MP3 to find the correct time is pretty efficient, and that the reason for all this trouble is that streaming (specifically, requesting the correct byte offset from the server, if you want to jump to a specific time on the stream) is the problem he's trying to tackle here. He said that if it weren't for the streaming use case, he'd be fine with forward-reading.
- 10y ago
- mikey_p 10y agoI assume this is the same problem I see in my car (VW) when streaming Spotify via Bluetooth? The progress bar in the car seems to go at double speed and runs out about halfway through each track.
- mattdonders 10y agoI thought so too but it's actually a bug in the radio itself (if you're driving a MK6). You can go to the dealer and reference Technical Service Bulletin (TSB) 91-13-03 and they'll do a software update to fix it. --- There's another bug in that radio but I won't tell you until after you see if you want to get it fixed because its really annoying.
- TazeTSchnitzel 10y agoOh, that explains why when I pause music on my iPhone and resume, it doesn't continue playing from the same place. Damnit, Apple.
- tombert 10y agoI actually didn't know that MP3s had a VBR option...I guess this shows how uncommon it is. I use VBR Ogg whenever I can, and I always thought it was weird that MP3 didn't have support for that feature. I guess I was (as always) a bit ignorant :D.
- CamperBob2 10y agoNot a fan of VBR MP3 files in general. They're more complicated to deal with when writing a codec, due in no small part to the seeking problem. And VBR is one of those optimizations that only works on things that didn't need optimizing in the first place (i.e., low-entropy frames.) There's just not much point to it. If you need VBR MP3 for some reason, chances are you really need a better format.
- anonova 10y agoHow does one actually see the bug report? What is `rdar://27848317` supposed to open?
- yoda_sl 10y agoThis in reference to Apple internal bug tracking system named "Radar", the number listed here is the bug ID and only Apple folks and probably the person that created that bug in the Radar system can see it
- deleted 10y ago[deleted]
- ksec 10y agoNot a fans of VBR MP3. VBR is great. But as some has shared maximum compatibility is much more important. Let's do some maths ( Correct me if I am wrong ) At 128Kbps that is 1MB per minutes, an hour would means 60MB. Since most podcast uses 64Kbps we are talking about 30Mb, a saving of 20% means 6MB per client, 10,000 listeners saves you 60GB per episode, assuming a Weekly episode, that is 240GB....... on an 2015 Est of ATP listeners around 80,000, that is ~ 2TB of Transfer. That is the transfer a $10 Linode would give you. So is it really worth the risk of VBR concern on a little saving worth $10 to $20? Since i didn't exactly listen to the podcast, I wonder what problem does he has with AAC. Because the argument about most having a newer devices with proper support for VBR MP3 also works for AAC. And AAC sounds A LOT better.
- et-al 10y agoYou raise a good point, but if you're ever in a place with a shoddy internet connection, you appreciate optimized filesizes.