Allow GetMediaInformation Function to fail with response

[JChappel]

Is your feature request related to a problem? Please describe.
When using FFprobeKit.getMediaInformation(url) it seems to only work if the url is valid. Which prevents subsequent code from being executed, by getting stuck.

Describe the solution you'd like
It would be useful if it provided a ReturnCode as the FFmpegKit provides. This way you know if the media information request failed and if so why. Or at a minimum, it could return nil if it fails.

Describe alternatives you've considered
I have added my own check before I execute GetMediaInformation. I check to see if I can hit the URL and get a response before trying the GetMediaInformation.

Platform
I'm currently experiencing the issue in Swift on tvOS but I would guess it would be a cross-platform issue.

Additional context

[tanersener]

getMediaInformation returns a MediaInformationSession. You should be able to see why it fails by checking.

1. State -> [session getState]
2. Return code -> [session getReturnCode]
3. Fail String -> [session getFailStackTrace]
4. Output -> [session getOutput]

There is also a getMediaInformationAsync method on FFprobeKit. It is an asynchronous method. So, it won't block your main thread. You can try using it if you want to unblock other threads.

[JChappel]

So what I was seeing is it was never getting past the getInformation command in Swift. Unless the URL was valid and then it would go on as normal and I could use MediaInformationSession.

[tanersener]

Well, there is not much we can do about it. When the URL is not valid ffmpeg waits HTTP/HTTPS stack to return an error. Depending the protocol and URI part that is not valid, this may take time.

My suggestion is to use the asynchronous getMediaInformationAsync method to unblock your application threads.

[JChappel]

Ok thanks, I just saw there is also GetMediaInformation withTimeout. Will setting a timeout say of 1 second cause it to fail if the URL does not respond?

[tanersener]

No, it won't. That timeout is for something else. You're free to try but it shouldn't change anything.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.