[X] One mp3 album is read unusually slowly by Mp3tag (~10 sec)

I have encountered one specific mp3 album
that is read unusually slowly by Mp3tag
(~10 sec while all other mp3 albums I have, are read instantly, in less than 1 sec)
I haven't noticed any unusual with these files tags .
(they are 11 320-kbps mp3's, of duration ~3 mins and without any embedded mp3 art cover)

Please PM me to send you links to download a track or the whole album.

Thank you.

PS. Using latest Mp3Tag v2.59a in win8.1 x64.

What happens if you create a copy of the folder of the album and then read the files?
If this is quicker then I would assume that the files are spread all over the disc.

PS: Where do you think the bug should be? (you posted in the bug section)

I've tried that before posting my OP
(copying it -several times- in an external hard disk or as duplicate in the laptop hd)
and it made no difference at all.

All other albums, that I have saved in recent time,
all are read quickly by Mp3tag.

I suppose that these files might have some characteristic
that causes Mp3tag to read them slowly.

You may now burn the whole firework of checking the files with mp3val and mp3diags, rewrite the headers with foobar2000.

:huh: I did't quote understand what you mean by

Anyway, I pressed "Remove Tags" (to a copy of the album folder) in Mp3tag,
and imported the tags via eg Tag Sources>discogs
and the files are read instantly now.

And, what I also noticed is this:
I copied just 1 of the initial mp3 (with no art cover, neither embedded nor separate)
to a separate -new- folder,
launched Mp3tag to read that folder,
and after I pressed "Remove tag"
THEN it showed that it had embedded art cover (image/png, 60 KB, with embed file as Other) !

I confirmed that the separate file was now containing an embedded cover art
by using Beyond Compare (MP3 compare) to compare it to the initial mp3

After "Remove tag"
the reading is quick again.

Mp3Diags showed:
(for the initial mp3)

(for the mp3 with the tag removed, revealing the hidden cover art file)

So, the initial mp3 had tag corruption,
and removing the tags now fixed this and revealed the cover art file.
Therefore, that was the cause of the slow reading, I believe.

A few days ago I observed a similar behaviour using Mp3tag v2.59a.

The procedure was to store a cover picture, for completion an already textually tagged media file.

  1. Original picture is a PNG file with properties ...
    1300 x 1300, 300 dpi, 725 kB.
  2. Using Irfanview I copied the PNG image to the clipboard.
  3. Using Mp3tag Dialog "Extended Tags..." I inserted the clipboard content into the media file, and saved the media file.
    It seems so that Mp3tag has converted the image from PNG to JPG with properties ...
    JPEG, quality: 100, subsampling ON (2x2), 100 dpi, 698 kB.
  4. I added one text data tag-field, and Mp3tag worked rather slow, about 20..30 percent as fast as before without the embedded cover image; the entire duration was about 8 minutes for 200 files.

After removing the image from the media file, the Mp3tag usual performance was restored, so that adding one text data tag-field was done in short time.

Then I tried the embedding process again.

  1. Now the picture is a JPG file with properties ...
    JPEG, quality: 80, subsampling ON (2x2), 159 kB.
  2. Using Irfanview I copied the JPG image to the clipboard.
  3. Using Mp3tag Dialog "Extended Tags..." I inserted the clipboard content into the media file, and saved the media file.
  4. I added one text data tag-field, and Mp3tag worked as it behaved in the usual performance; the entire duration was about 1,5 minutes for 200 files.

I suspect that the slowdown occurs while Mp3tag creates and saves the "undo data."
I do not remember having seen this behaviour of slowing down, even when tagging media files having more than one embedded image.


Sorry, that I did not express myself clearly.
I tried to point into the direction of trouble with the tags.
The tags could be checked with tools I mentioned.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.