Huffmann data overrun

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Vittorio
Posts: 9
Joined: Wed Jan 07, 2015 1:41 pm
Operating System: Windows 7

Re: Huffman data overrun

Post by Vittorio » Thu Sep 03, 2020 7:59 pm

Hi there,

I have had the same issue today, but only on certain mp3 files.

What I have done:
- opened a 60-minute mp3 file in mp3DirectCut
- split the audio into separate tracks
- saved split tracks into individual files
- drag & drop the tracks into Audacity

What has happened:
- first track imported just fine
- second and following tracks threw an error telling me that "Huffman blah blah blah ..."

I used mp3DirectCut, because it allows lossless editing (without re-encoding the audio, unlike Audacity).

I assume that the saving procedure in mp3DirectCut messed up the mp3s. But what can I do?

Actually, opening the mp3s in Audacity wasn't neccessary, because I didn't plan to do any further editing.
I just wanted to check the audio and then this issue occured.

Does that mean that my mp3 files are damaged?

steve
Site Admin
Posts: 81866
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Huffmann data overrun

Post by steve » Thu Sep 03, 2020 8:26 pm

Vittorio wrote:
Thu Sep 03, 2020 7:59 pm
Does that mean that my mp3 files are damaged?
Yes, but not necessarily badly damaged, and there may be no audible damage when played in other apps.
Audacity 2.4.2 is very fussy and requires MP3 to exactly meet the MP3 specification. In particular it does not accept "ape" tags. The next Audacity version will be a bit more forgiving.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

DVDdoug
Forum Crew
Posts: 9461
Joined: Fri Sep 10, 2010 11:30 pm
Operating System: Windows 10

Re: Huffmann data overrun

Post by DVDdoug » Thu Sep 03, 2020 8:46 pm

Does that mean that my mp3 files are damaged?
Yes. :( But it may play fine in other applications and maybe you can live with it. Until now, I thought MP3directCut was pretty good...

I wonder... Maybe the original file was non-compliant and MP3directCut somehow compounded the problem???

MP3 Diags can diagnose & repair lots of different MP3 problems.

Any changes made by MP3 Diags are permanent so make a backup before you start playing with it. It's "highly technical" so I don't always understand what it's doing but applying some or all of the repair tools often does "repair" the file. You'll probably have to read some of the documentation on the website but the "All Notes" tab tells you what's potentially wrong with the file (often several different things) and the icons at the top that look like hammers are the repair tools (AKA "transformations").

MP3 Diags seems to find lots of issues with my "perfectly good" MP3s. (I don't check all of my files with it.)

ricklowen
Posts: 1
Joined: Mon Oct 12, 2020 9:31 pm
Operating System: Windows 10

Re: Huffmann data overrun

Post by ricklowen » Mon Oct 12, 2020 9:43 pm

I'm using Windows 10 and Audacity 2.4.2

Quoting and earlier message in this thread "The message "huffman data overrun" is an error message from the MP3 importer "libmad", which indicates there is an encoding error in that MP3 file".

Is the error returned from libmad in such a way that the error dialog indicating a Huffman data overrun could indicate the name of the damaged file? I frequently drag and drop 30+ mp3 files into Audacity, and it is almost impossible to detect which file is damaged if it is more than a couple into the group being imported. It would be very helpful if the error dialog included the name of the damaged file.

srib
Posts: 1
Joined: Thu May 13, 2021 1:48 am
Operating System: Windows 10

Re: Huffmann data overrun

Post by srib » Thu May 13, 2021 1:54 am

Ran into this "Huffmann data overrun" on an mp3 file today. I worked around the issue by renaming the file to .mp4 and am able to open in Audacity.. Once opened, I am then able to save as .mp3 for further processing.

Hope this helps someone.

-Sri

DVDdoug
Forum Crew
Posts: 9461
Joined: Fri Sep 10, 2010 11:30 pm
Operating System: Windows 10

Re: Huffmann data overrun

Post by DVDdoug » Thu May 13, 2021 3:10 am

I am then able to save as .mp3 for further processing.
Any "further processing" should be done before you export to MP3. If you want to save a temporary/intermediate file, save as WAV.

As you may know, MP3 is lossy compression. Audacity (and all "regular" audio editors) decompress the file so when you re-export as MP3 you are going through another generation of lossy compression, and "damage" accumulates with each generation of re-compression. MP3 is one of the worst formats for re-compression and MP4 immune to accumulated damage.
I worked around the issue by renaming the file to .mp4
Maybe it was actually an MP4, or maybe you just "fooled" Audacity into using FFmpeg (which is normally used for MP4) and then FFmpeg detected it as MP3 and was able to open it. (FFmpeg is more tolerant of "bad" MP3s.)

waxcylinder
Forum Staff
Posts: 14718
Joined: Tue Jul 31, 2007 11:03 am
Operating System: Windows 10

Re: Huffmann data overrun

Post by waxcylinder » Thu May 13, 2021 9:11 am

There is an open bug logged for this:
https://bugzilla.audacityteam.org/show_bug.cgi?id=2749
LIB-MAD: Huffman Data Overrun

Peter.
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * FAQ * * * * * Tutorials * * * * * Audacity Manual * * * * *

Post Reply