| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021272 | MMW 5 | Codecs | public | 2024-10-11 22:21 | 2026-09-16 14:00 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Target Version | 2027.0 | Fixed in Version | 2027.0 | ||
| Summary | 0021272: Some tracks Length are incorrectly read | ||||
| Description | Some tracks Length are incorrectly read Actual Track length is 04:36 (44.1 / 140 kbps) but MM reads it as 20:06 (44.1 / 32 kbps) As a result of that, Seek Bar appears not working correctly even Wave Bar shows track is really 04:36. Sample Track is on FTP | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3522 | ||||
|
|
Win 10 Media Player also reads wrong length image-3.png (9,354 bytes) |
|
|
It is not MM issue. The file is VBR MP3 but seriously corrupted - VBR (Xing) header is missing, so MM even does not know, it is VBR. Without this header it is not easily possible to compute file length correctly. Players only guess, I tried several players and each shows different file length and all wrong. Even some specialized tools for fixing MP3 do not work, tried mp3val and no luck. I have found one, which worked - specialized Vbrfix tool. As our soft is not designed to fix seriously corrupted files, I am closing this. |
|
|
Fixed in build 3522. I chose compromise - parser for tracks without Xing header now checks data in more places in the file to be sure, they are really CBR (the example file looks like CBR, but later changes bitrate). This way it should be as fast as before for most of the files and only possible problematic files are parsed more carefully and in case VBR is detected, parsed whole. |
