Failures to render or stop seeking when stress system with multiple ffmediaelement instances in an WPF application

[rstelling]

I use ffmediaelement with a configured up to 20 instances on one window and also up to 20 instances added and removed dynamically in another window. Use with displaying UDP streams and playing back video files. Currently having trouble where PTS increments when play/single step but display is all black (though that is my background color). If if save RenderingVideo callback parameter e.Bitmap to a file the video is fine, but display is not. Can often detect by calling CaptureBitmapAsync, which returns null in this condition (though apparently sometimes gets an exception). I see static RC.Current property for frame reference counting would be shared among all ffmediaelement instances, not clear if this is a problem.

Also have trouble where the player continues to have a status of IsSeeking. In my application I recover from this after few single steps where this doesn't change by reopening the file.

I searched for ffmediaelement multiple instances and found this page with a simple application that creates 9 instances. This works fine when all it does it play the video.

#185

I have extended the sample application to stress the system more, with Pause, Play and Seek (via button and slider). I have been able to reproduce the player stuck in IsSeeking and have the video frame display all white. If I stress it enough using the slider it will crash.

I have checked in my version of Mario's sample to the following repo. The checked in version has Mario's hard-coded video files but I actually tested with my own set of files that I'd rather not make public. They are 10 to 20 seconds long.

https://github.com/rstelling/FFME_multiple