mp3HD: New lossless MP3 format explained
By Nate Lanxon on 27 March 2009

(Credit: Thomson)
French media behemoth Thomson has announced mp3HD, a new lossless "hybrid" MP3 format, which not only offers the sound detail lost in a normal MP3, but remains compatible with your existing MP3 player or iPod.
It's called mp3HD and still uses the traditional .mp3 file extension. Simply put, it works by storing a conventional lossy MP3 track that standard players can play, alongside a "lossless" version — both audio streams are contained in one single MP3 file. It's similar to how hybrid SACDs work.
Ideally this would appeal to users who want to enjoy lossless audio at home and universally compatible MP3s on the commute, without having to rip two versions of the same song.
Real-world testing
We've tested the format, ripping our own CDs using Exact Audio Copy and Thomson's mp3HD command line encoder. A six-minute 22-second mp3HD file (Pink Floyd's Money), using default settings, gave us a 48MB file — just 5MB larger than a file ripped in FLAC, level 8.
On a PC with Thomson's mp3HD decoder plug-in installed, Winamp played the 800Kbps (on average) lossless audio track, but when dragged into iTunes the same file played as a normal old 320Kbps MP3 file. It transferred without issue to an iPhone 3G and to a Cowon iAudio D2 MP3 player and played without any problems.
This is it: a lossless audio file, theoretically backwards compatible with all existing MP3 players! Why wouldn't everyone adopt this? Well, for a whole bunch of reasons, frankly.
The problems
At face value it's remarkably convenient, like a car that doubles up as a plane. But like your aeromobile, there are problems for the average consumer. Firstly, file size. A normal 320Kbps MP3 of the same Pink Floyd song was just 14.6MB, and 320Kbps is all you'll hear if you listen to an mp3HD track on your iPod.
But the lossless audio stored in the file will be stored on your iPod nevertheless, taking up precious storage space. (Although we should point out to audiophiles that the hybrid files are smaller than the combined size of a FLAC and 320Kbps MP3, and are less efficient to encode than FLAC.)
The second problem concerns compatibility. The joy of MP3 files, and the reason for their ubiquity in the marketplace, is their small size and compatibility with almost anything you throw at them. With mp3HD, not only are file sizes massive (making them impractical for small flash players), but you need to install plug-ins on your computer. True backwards compatibility would mean no additional software or updates were required.
Ideally you'd be able to transfer only the small, lossy part of the mp3HD to a portable player, leaving the lossless part (stored as what's known as "correction data") behind. But this would require additional software, and that means Average Joe won't want to know about it.
The last word
Undoubtedly, mp3HD will appeal to archivists with hard drives in their portable music players (such as the iPod Classic or Archos 5). But for the chap on the street it'll be small, convenient, decent-enough-sounding MP3s all the way and smaller Apple Lossless files for the iTunes audiophiles.
You can get started using the format at Thomson's website.
Topics: lossless, mp3, file, player, small
Related Articles
Cowon O2 (32GB)
Know your digital audio formats
Advanced iTunes: Get more from the software
Cowon iAudio A3 (60GB)
Comments (1)
-
Eka-X commented on 30/03/2009 15:53
infomation from hydrogenaudio by Peter Pawlowski, foobar2000 maker.
---
Useless format:
* The lossless part is stored in ID3v2 tags.
* Size of ID3v2 tags is limited to 256MB by specifications; as a result, lossless part of an mp3hd file can't be larger than 256MB.
I wonder what those people will think of next. Maybe resurrect VQF or something.
Addendum:
Current tagging software isn't prepared to deal with this kind of situation, so you're going to see various disturbing behaviors such as:
* Very slow tag updates (near-full-file-rewrite with each edit).
* Heavy memory usage of tag editors.
* Retagging stripping correction data.
* Tag editing or even reading failures when approaching the 256MB limit because software will try to put each ID3v2 frame in a single memory block and allocating a single block of such size is likely to fail in 32-bit address space because of fragmentation issues.
Post your own comment
Enter your personal information to the left, or sign in with your Facebook account by clicking the button below.
ConnectThe Explain Series
-
Get (laptop) smart before you buy
Win the numbers game and get the laptop that's perfect your needs as well as your budget!
-
Microsoft Windows® 7. Your PC, simplified.
Windows® 7 has been designed to be more reliable, more responsive, and to make the things you do every day easier.
-
Whereis® maps
If you’d like to get to know more of Australia, and do it safely, then check out Whereis® maps.
Must read
-
Will former Google exec help save the music industry?
The new chief of EMI's digital unit is a Googler down to his soul, which...
-
A bittersweet look at ten years of MP3s
In the '90s, when the MP3 was new, it was difficult to predict the...
-
Amazon's MP3s not affecting iTunes
Amazon.com's MP3 service is growing but not at the expense of Apple's...
-
Top free MP3 apps: alternatives to iTunes and WMP
Sick of Windows Media Player? Over iTunes? Here are three free...
-
Apple to boost music content for iPhone
Apple is in talks with the largest record companies as it attempts to...








1%
3%



