# \[F\] Length misreads for long audiobooks

**URL:** https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [March 20, 2015, 2:44am UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718 "2015-03-20T02:44:38Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![vance003](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/9e8a1a/32.png) [@vance003](https://community.mp3tag.de/u/vance003)
#### Post date: [March 20, 2015, 2:44am UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718/1 "2015-03-20T02:44:38Z")

</div>

I have mp3tag 2.69 on Windows 7, 64 bit. I'm using it to check metadata on audiobooks converted from Audible's AAX format to more generic M4B format; all of these files were converted at a constant bit rate of 64kbps. In general, mp3tag can read the file metadata fine in the M4B files, but there seems to be an issue for audiobooks longer than a day in length. For files less than 24 hours long, the Length field is correct (or at least, it matches Windows Explorer). If, however, the file is a little longer than 24 hours, mp3tag will subtract 24 hours from the Length field --- so, for example, a file that Windows says has a length of 25:48:18, mp3tag gives the length as 1:48:18. For longer files still, say 30 hours or more, it simply gives the length as 00:00. Any workarounds?

---

<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: [March 23, 2015, 6:51pm UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718/2 "2015-03-23T18:51:55Z")

</div>

Thanks for reporting!

The issue should have been fixed now with the current Development Build (v2.69a) available from [http://developer.mp3tag.de](http://developer.mp3tag.de)

Kind regards  
Florian

---

<div class="post-metadata">

### Author: ![vance003](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/9e8a1a/32.png) [@vance003](https://community.mp3tag.de/u/vance003)
#### Post date: [March 23, 2015, 11:02pm UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718/3 "2015-03-23T23:02:41Z")

</div>

> [@Florian](#):
>
> The issue should have been fixed now with the current Development Build (v2.69a) available from [http://developer.mp3tag.de](http://developer.mp3tag.de)

Thanks, but the problem isn't fixed yet. I've attached a screenshot showing version 2.69a running on my computer (Win 7 64 bit). The entries are sorted by decreasing file size, with second column giving the file size and the third column giving the length. As you can (hopefully) see, around three quarters down the list is a file that is 732.96 MB in size and 26:23:59 in length. For all files above it in the list, ranging in size from 792.36 MB to 1.57 GB, the length is given as 00:00.

 ![](https://community.mp3tag.de/uploads/default/original/2X/4/440dcbfcf05b09ef5c40bd285056738c757af0c4.jpg)  

 ![](https://community.mp3tag.de/uploads/default/original/2X/4/440dcbfcf05b09ef5c40bd285056738c757af0c4.jpg)

---

<div class="post-metadata">

### Author: ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 24, 2015, 7:39am UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718/4 "2015-03-24T07:39:24Z")

</div>

> [@vance003](#):
>
> Thanks, but the problem isn't fixed yet. ... For all files above it in the list, ranging in size from 792.36 MB to 1.57 GB, the length is given as 00:00.

Check Mp3tag Column Definition for "Length".  
Value: %\_length%  
Sort by: %\_length\_seconds%  
Sort by: Numerical

Does it make any change in the list view?

 ![](https://community.mp3tag.de/uploads/default/original/2X/2/2740ac3732ea6dca60f8082a4ebce291e9424bb7.png)  

Or did I misunderstand the problem?

Here is another test result, which shows an error for filetype m4a.

 ![](https://community.mp3tag.de/uploads/default/original/2X/1/171cf77b9d1f0348257890fdbda10b5227dfa9f2.png)  

File properties ...  
[20150324.Properties.Track.1to7.txt](https://community.mp3tag.de/uploads/default/original/2X/0/0d4689b1f28e87faea589b1d6f934a4db7607c1c.txt) (3.16 KB)  
Download self extracting 7zip archive with test files ...  
[https://www.sendspace.com/file/1qwu0n](https://www.sendspace.com/file/1qwu0n)

DD.20150324.1214.CET, DD.20150324.2035.CET, DD.20150325.0917.CET

 ![](https://community.mp3tag.de/uploads/default/original/2X/2/2740ac3732ea6dca60f8082a4ebce291e9424bb7.png)  

[20150324.Properties.Track.1to7.txt](https://community.mp3tag.de/uploads/default/original/2X/0/0d4689b1f28e87faea589b1d6f934a4db7607c1c.txt) (3.16 KB)

 ![](https://community.mp3tag.de/uploads/default/original/2X/1/171cf77b9d1f0348257890fdbda10b5227dfa9f2.png)

---

<div class="post-metadata">

### Author: ![vance003](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/9e8a1a/32.png) [@vance003](https://community.mp3tag.de/u/vance003)
#### Post date: [March 25, 2015, 1:14am UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718/5 "2015-03-25T01:14:15Z")

</div>

> [@DetlevD](#):
>
> Check Mp3tag Column Definition for "Length".  
> Value: %\_length%  
> Sort by: %\_length\_seconds%  
> Sort by: Numerical
> 
> Does it make any change in the list view?

Those are exactly my settings for Length --- I haven't mucked around with the column definitions at all.

I'm glad to see the problem replicates on another system, although it's curious that it is not a consistent replication.

---

<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: [December 28, 2018, 2:08pm UTC](https://community.mp3tag.de/t/f-length-misreads-for-long-audiobooks/16718/6 "2018-12-28T14:08:21Z")

</div>

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