invalid runtime for movie when viewing mediainfo details #8659

New issue

Closed

opened 2026-02-20 00:06:11 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 00:06:11 -05:00

Owner

Originally created by @thezoggy on GitHub (Aug 12, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

mediainfo

File size                                : 21.8 GiB
Duration                                 : 2 h 2 min

ffprobe ffprobe -loglevel error -print_format json -show_format -sexagesimal -show_streams -probesize 50000000 /path/file.mkv
https://hastebin.com/share/jorapizeqe.json

but the important bit

            "duration": "2:02:21.793000",

possible fallout of: github.com/Radarr/Radarr@5533528b56

Expected Behavior

show correct runtime

Steps To Reproduce

Look at any movie runtime in radarr that has 1+ hour runtime...

Environment

- OS: Unraid 7b2
- Radarr: 5.9.0.9010
- Docker Install: yes
- Using Reverse Proxy: yes
- Browser: Firefox 129
- Database: sqlite3

What branch are you running?

Nightly

Trace Logs? Not Optional

i do not have trace logs enabled at the moment, but this issue is easily seen without logs (see above ffprobe info)

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @thezoggy on GitHub (Aug 12, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior ![image](https://github.com/user-attachments/assets/16f6f699-370d-4fda-85b5-f92a5ae6de97) mediainfo ``` File size : 21.8 GiB Duration : 2 h 2 min ``` ffprobe `ffprobe -loglevel error -print_format json -show_format -sexagesimal -show_streams -probesize 50000000 /path/file.mkv` https://hastebin.com/share/jorapizeqe.json but the important bit ``` "duration": "2:02:21.793000", ``` possible fallout of: https://github.com/Radarr/Radarr/commit/5533528b56cbdeaf08192f208faecac8c3ce3cc9 ### Expected Behavior show correct runtime ### Steps To Reproduce Look at any movie runtime in radarr that has 1+ hour runtime... ### Environment ```markdown - OS: Unraid 7b2 - Radarr: 5.9.0.9010 - Docker Install: yes - Using Reverse Proxy: yes - Browser: Firefox 129 - Database: sqlite3 ``` ### What branch are you running? Nightly ### Trace Logs? **Not Optional** i do not have trace logs enabled at the moment, but this issue is easily seen without logs (see above ffprobe info) ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 00:06:11 -05:00

closed this issue
added the
Type: Bug

Area: UI

Type: Regression
labels

deekerman commented

2026-02-20 00:06:12 -05:00

Author

Owner

@thezoggy commented on GitHub (Aug 12, 2024):

to note, sonarr still displays things as you'd expect, hh:mm:ss
so i assume not an upstream bug, but specific to radarr

@thezoggy commented on GitHub (Aug 12, 2024): to note, sonarr still displays things as you'd expect, `hh:mm:ss` so i assume not an upstream bug, but specific to radarr

deekerman commented

2026-02-20 00:06:12 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Aug 12, 2024):

Regression from 5533528b56

@mynameisbogdan commented on GitHub (Aug 12, 2024): Regression from 5533528b56cbdeaf08192f208faecac8c3ce3cc9