# Wrong time lenght

**URL:** https://community.mp3tag.de/t/wrong-time-lenght/69894
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [September 28, 2025, 5:22pm UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894 "2025-09-28T17:22:32Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![Jaff](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jaff/32/6590_2.png) [@Jaff](https://community.mp3tag.de/u/Jaff)
#### Post date: [September 28, 2025, 5:22pm UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/1 "2025-09-28T17:22:32Z")

</div>

MP3Tag timing (1h00m00s) (probably ID3v2 tag, and ID3v1 are calculated as audio data on CBR MP3 files)

 ![MP3Tag](https://community.mp3tag.de/uploads/default/original/3X/7/3/7340306c0b8b6d0513c8c6ab650078fd4eb54b5c.png)

MPC-HC timing (59m51s - the right one)

 ![MPC](https://community.mp3tag.de/uploads/default/original/3X/5/7/57c9857fdd981499dea9b55e5c2aaa3e458e2093.png)

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [September 28, 2025, 5:35pm UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/2 "2025-09-28T17:35:28Z")

</div>

have you checked the file with the a tool to rule out that the file has a problem?  
And then it would be nice, if you could supply such a file.

---

<div class="post-metadata">

### Author: ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)
#### Post date: [September 29, 2025, 1:42am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/3 "2025-09-29T01:42:51Z")

</div>

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

---

<div class="post-metadata">

### Author: ![Jaff](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jaff/32/6590_2.png) [@Jaff](https://community.mp3tag.de/u/Jaff)
#### Post date: [September 29, 2025, 6:31am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/4 "2025-09-29T06:31:17Z")

</div>

Checked with MP3Diags / MP3val / fobar2000. All good, no errors on MP3. The timing problem is not happening on a singular file. Good timing on Winamp/Foobar2000/MPC-HC/VLC/Media Player/WMP/IrfanView/Aegisub etc, but not on MP3tag. Tested with different files (with and without tags). Same results, MP3tag (v3.31a) gives wrong time of file. The only fix is to write a Xing/Info header (with MP3packer) to help MP3Tag see real time of file

---

<div class="post-metadata">

### Author: ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)
#### Post date: [September 29, 2025, 6:46am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/5 "2025-09-29T06:46:35Z")

</div>

Can you try with the latest development version ? 3.31d

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [September 29, 2025, 6:50am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/6 "2025-09-29T06:50:47Z")

</div>

> [@Jaff](#):
>
> fobar2000

I compared the data of the following files in Foobar and MP3tag:

| Track | MP3tag | Foobar |
| --- | --- | --- |
| Moon Sequence | 06:19 | 6:18.868 |
| Heavy air | 07:00 | 6:59.802 |
| In search of | 03:33 | 3:33.487 |
| Walk into space | 06:55 | 6:54.943 |

TBH I do not see a significant difference.

---

<div class="post-metadata">

### Author: ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)
#### Post date: [September 29, 2025, 7:04am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/7 "2025-09-29T07:04:03Z")

</div>

I compared the longest Mp3 I have with Mp3tag and Foobar and the results are the same

Foobar2000

 ![Screenshot 2025-09-29 at 14.02.21](https://community.mp3tag.de/uploads/default/original/3X/4/7/47629f5c6311da7b51a956681f96648ca3fbb746.jpeg)

Mp3tag

 ![Screenshot 2025-09-29 at 14.03.08](https://community.mp3tag.de/uploads/default/original/3X/9/e/9e2021bb38f464492d0181eff42ead20f70827ec.jpeg)

Edit: Maybe send a link to your test file to Florian via PM so he can have a look (refer to this thread if you do so)

---

<div class="post-metadata">

### Author: ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)
#### Post date: [September 29, 2025, 7:31am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/8 "2025-09-29T07:31:21Z")

</div>

One more comparison this time 3 songs approx 1 hr in length

Foobar

 ![Screenshot 2025-09-29 at 14.29.39](https://community.mp3tag.de/uploads/default/original/3X/5/7/5783339d97a1babfab92f6062c84723cf69ae49b.jpeg)

Mp3tag

 ![Screenshot 2025-09-29 at 14.29.56](https://community.mp3tag.de/uploads/default/original/3X/7/5/75d955048d0f89d532600dd4ed26fc623074483d.jpeg)

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [September 29, 2025, 8:17am UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/9 "2025-09-29T08:17:55Z")

</div>

I sent a link with instructions to upload the file via PM.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [September 30, 2025, 3:36pm UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/10 "2025-09-30T15:36:22Z")

</div>

Thank you for the example file. It seems like the file uses no frame padding for the first frame (frame size = 417) and padding for subsequent frames (frame size = 418), so that calculation using the initial frame size is off by the margin you've observed.

I'll probably need to come up with a different way to calculate this in those cases (maybe simple `file_size * 8 / bps`). Looking at each frame would be too time-consuming.

I'll keep you posted.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [October 22, 2025, 4:08pm UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/11 "2025-10-22T16:08:39Z")

</div>

This is now fixed with [Mp3tag v3.31e](https://community.mp3tag.de/t/455). Thank you for reporting!

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [November 21, 2025, 4:09pm UTC](https://community.mp3tag.de/t/wrong-time-lenght/69894/12 "2025-11-21T16:09:09Z")

</div>

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