Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support calculating approximate duration
See original GitHub issueGiving the duration: true option makes all media files be fully scanned to calculate their accurate duration, but when a large number of files should be handled, it is enough to get approximate duration of songs; most clients to play them do not trust what the server gives anyway.
How about adding an option like approximate: true to duration: true for approximate duration? As I recall, an old version of musicmetadata did that by assuming CBR when the first three frames have the same bit-rate; I ported that to mp3-duration (https://github.com/mycoboco/mp3-duration/commit/abdb1bca7d9739dbff1b99479b84c811d2bc6f12).
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That could very well be the reason.
On a good quality (using a recent Lame encoder) MP3 encoded file, it will do the duration calculation on the VBR/Xing/Info header. That header specifies the number of frames.
I just removed a silly rounding from that calculation. It is pretty accurate only thing what is missing is subtracting the “empty” space in the very last frame.
@mycoboco, thanks for your reply and promising the benchmark.
Feel free to open an issue for the remaining 6 files or re-open this one.