-
-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Constant Failed to get runtime from the file, make sure ffprobe is available #218
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
Same error for me. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
I was running into this issue as well, it seems to be an issue with Radarr itself. For me, the problem was I remuxed a |
Also running into this issue |
Appears to be an issue specific to radarr - please work on this with them. |
Is there an existing issue for this?
Current Behavior
These errors are constant on my setup, multiple ffprobe unavailable and errors on VIDEO_TS folders
Failed to get runtime from the file, make sure ffprobe is available
Unable to parse media info from file: /PATH)/VIDEO_TS/VIDEO_TS.IFO: ffprobe exited with non-zero exit-code (1 - /PATH/VIDEO_TS/VIDEO_TS.IFO: Invalid data found when processing input)
FFMpegCore.Exceptions.FFMpegException: ffprobe exited with non-zero exit-code (1 - /PATH/VIDEO_TS/VIDEO_TS.IFO: Invalid data found when processing input)
at FFMpegCore.FFProbe.GetStreamJson(String filePath, Int32 outputCapacity, FFOptions ffOptions)
at NzbDrone.Core.MediaFiles.MediaInfo.VideoFileInfoReader.GetMediaInfo(String filename) in ./Radarr.Core/MediaFiles/MediaInfo/VideoFileInfoReader.cs:line 140
Expected Behavior
No error
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: