Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Problem with mp3 cbr duration (Read 3019 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Problem with mp3 cbr duration

This is only for files with no VBR Header.
It seems especially on longer mp3 tracks with a constant bitrate, the duration is displayed too long.

To test this encode a long audio track (20min+) with recent lame.exe with  -b and -t parameters.

Problem with mp3 cbr duration

Reply #1 –
I've experienced another issue - duration is displayed less than it really is. Accordingly, file is played only partially (example). The issue is still present in beta.
Magically yours
Raistlin

Problem with mp3 cbr duration

Reply #2 –
1.1.12b2 - no changes relating my issue. Still plays just 19 minutes of 41 minutes mp3 file  . I'm forced to use Winamp to play it...
Magically yours
Raistlin

Problem with mp3 cbr duration

Reply #3 –
Have you tried either verify integrity [foo_verifier] or rebuild stream from the context menu?

Problem with mp3 cbr duration

Reply #4 –
Quote from: dano on
This is only for files with no VBR Header.
It seems especially on longer mp3 tracks with a constant bitrate, the duration is displayed too long.

To test this encode a long audio track (20min+) with recent lame.exe with  -b and -t parameters.


The example you posted was encoded with LAME 3.91, -m j -V 4 -q 2 -lowpass 15.5 -b 128

-V 4 means VBR, at LAME's quality level 4. So the -b 128 is merely constraining the minimum bitrate, not forcing CBR.
Correction: Actually the -b 128 seems to override the -V4; the file has all 128 kbps frames, so it is CBR.
I see what you mean about the duration... actual duration is 41:34 but fb2k is reporting 19:53 for me, unless I add a VBR info header.

Problem with mp3 cbr duration

Reply #5 –
Example was posted by me, not by topic starter. It may have nothing to do with the problem he/she reported. But it surely concerns recognition of an mp3 file's length, so I wrote here instead of starting new topic.
Magically yours
Raistlin

Problem with mp3 cbr duration

Reply #6 –
Quote from: tpijag on
Have you tried either verify integrity [foo_verifier] or rebuild stream from the context menu?

No, I didn't. The fact is that this mp3 file is from torrent tracker. I don't want to change it 'cause I want to stay seeding. Anyway, Winamp recognizes its length correctly, so I believe foobar can do the same.
Magically yours
Raistlin

Problem with mp3 cbr duration

Reply #7 –
GCRaistlin, the header in yours has a LAME tag with a bad MusicLength value (19100315, nowhere near the size of the file). I wouldn't say it's a problem with foobar2000; it's just using what it's given.

Problem with mp3 cbr duration

Reply #8 –
Quote from: GCRaistlin on
I don't want to change it 'cause I want to stay seeding.

Most operating systems offer the possibility to copy files. You will gain no sympathy or more helpful advice from me to fix your broken pirated downloads.
It's only audiophile if it's inconvenient.
 

Problem with mp3 cbr duration

Reply #9 –
Kohlrabi
Maybe I was looking lazy - I didn't want to 'cause I'm really not. Let me explain. It surely is easy to copy the file and fix its header, now actually I did it, and thanks to tpijag for the advice. But it isn't a common solution for the issue. I agree that the file has broken header, but how an user should know about it? I knew that the file's duration is longer than foobar shows just from comments on the tracker page.
IMHO it would be better if foobar made some additional checks to recognize such bad situations.
Magically yours
Raistlin