FileBot

Posted: **04 Jan 2026, 03:26**

FileBot 5.1.7 (r10514) on Docker (jlesage/filebot:latest)

AcoustID matching fails with duration parsing error:

Console Output: Select all

Bad duration value: 249.0 => java.lang.NumberFormatException: For input string: "249.0"
Bad duration value: 295.0 => java.lang.NumberFormatException: For input string: "295.0"
AcoustID: Failed to identify music file: /media/music/4 Non Blondes/4 Non Blondes - Whats Up.mp3
Failed to identify or process any files

fpcalc works correctly and returns valid fingerprint from command line.

Looks like the AcoustID API is returning duration as a float (249.0)
but FileBot is parsing it as an integer, causing NumberFormatException.

sysinfo output:

Console Output: Select all

FileBot 5.1.7 (r10514)
JNA Native: 7.0.2
MediaInfo: 25.10
Tools: fpcalc/1.5.1

Posted: **04 Jan 2026, 06:21**

Thanks for the bug report. Looks like the API response has changed. Fixed with FileBot r10884.

Posted: **04 Jan 2026, 19:16**

Thanks for the quick fix!
I'm running FileBot via Docker (jlesage/filebot) and the image still has r10514. Is there a direct download link for the updated JAR (r10884) so I can manually update the container while waiting for the Docker image to be rebuilt?

Posted: **04 Jan 2026, 23:26**

mediastack913 wrote: ↑04 Jan 2026, 19:16 Is there a direct download link for the updated JAR (r10884) so I can manually update the container while waiting for the Docker image to be rebuilt?

Latest Beta Revisions and Release Candidates

FileBot

AcoustID - Bad duration value NumberFormatException (float parsing)

AcoustID - Bad duration value NumberFormatException (float parsing)

Re: AcoustID - Bad duration value NumberFormatException (float parsing)

Re: AcoustID - Bad duration value NumberFormatException (float parsing)

Re: AcoustID - Bad duration value NumberFormatException (float parsing)