No exception/feedback when using more recent FFMPEG builds.

[sirdoombox]

No exception thrown when using more recent FFMPEG builds.

I apologise in advance if this issue is erroneous, and I have tested the same version of ffplay with the offending files directly and it opens/plays the video correctly.

I'm currently grabbing the most recent FFMPEG build from Zeranoe's Window builds, it works for almost every video file i try to open, but there are a couple that cause my app to instantly close on opening the file, with no error in the logs or exception thrown. I know that Ffmpeg 4.2.1 is the only officially supported version (with 4.2.2 working perfectly fine on my end) however the lack of any feedback on errors or runtime limitations on ffmpeg versions makes for a difficult time figuring out what is the most recent build that will function correctly.

Logs:

Direct Command 'Close' not accepted. Open media before closing or changing media.
Direct Command 'Open' accepted. Perparing execution.
Direct Command 'Open' entered
VIDEO - Start Time:      0.017; Duration:        N/A
Timing Offsets - Main Component: Video; Start Time:      0.017; Duration:     23.583; 
EVENT START: MediaStateChanged
Direct Command 'Open' completed. Result: True
EVENT DONE : MediaStateChanged
EVENT START: MediaOpened
EVENT DONE : MediaOpened
EVENT START: MediaStateChanged
EVENT DONE : MediaStateChanged
EVENT START: MediaReady
EVENT DONE : MediaReady
[At this point the app immediately closes with exit code 0.]

Issue Categories

• [ ] Bug
• [ ] Feature Request
• [X] Question
• [X] Not sure

Version Information

• [X] NuGet Package 4.2.330
• [ ] Build From Master branch
• [ ] Build from Branch Name

Steps to Reproduce

1. Grab the most recent shared build from Zeranoe - 64 bit | 32 bit for convenience.
2. Attempt to open one of these files - Video file that causes the problem | Video file that opens correctly (Apologies for the random video files, just happens to be two random small files that I had that I knew caused the issue)

Expected Results

• Any exception or feedback in the logs on what caused it to fail.

[stale[bot]]

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.