Some will be aware of several recent posts I've made relating to debugging a problem I've had on a legacy application whereby randomly one or more videos in a sequence of up to 12 videos throws an error, even though at other times the same videos play faultlessly.
For reference here's a couple of those posts Can I do more than MediaView.dispose to make MediaView ready again? and Handling _Finished event in jVLC library.
But while spending countless hours on this problem, my mind kept coming back to what had changed since successfully using the application for several years which may have caused this problem with MediaView given I'd only made minor changes to the application code which related to other functionality over that time. And the thing which stood out, but I discounted, was an upgrade from Win10 to Win11. I'd resisted upgrading because the machine used for this application was stable and performing well, but with end of support approaching for Win10, I updated to Win11 a few months ago and have only had this problem since that upgrade.
Given I’ve spent so much time trying to debug the problem, I was heartened by finding these two references: Video sometimes does not start when reinitializing in Windows 11 and Flaky JavaFX ERROR_MEDIA_INVALID MediaException.
These reinforce/confirm my view that the problem has occurred since updating from Win10 to Win11, particularly as the last comment in the first reference says “Checked with attached testcase in Windows 11, Issue is reproducible . . . . . whereas Issue is not reproducible in Windows 10.” And in the second reference which shows the OS as Win11 it says “As you can see, in player.setOnError() the code allows to re-try opening the file, which does work. So a typical run starts the first movie without problem. For movie 2 it needs 1 re-try, movie 3 needed 7 re-trys, and movie 4 needed 3 re-trys. But I also have runs where the application needed to re-try the first movie and all others were fine. So technically each movie is "showable".” is exactly the behavior I see.
So is the only solution to find an old Win10 laptop just to run this application?
EDIT: I should say that the "flaky" issue with MediaView only relates to the playing of videos. The same application can use images in lieu of videos in the sequencer and that continues to work flawlessly, even after the Win 10 to Win11 update.
For reference here's a couple of those posts Can I do more than MediaView.dispose to make MediaView ready again? and Handling _Finished event in jVLC library.
But while spending countless hours on this problem, my mind kept coming back to what had changed since successfully using the application for several years which may have caused this problem with MediaView given I'd only made minor changes to the application code which related to other functionality over that time. And the thing which stood out, but I discounted, was an upgrade from Win10 to Win11. I'd resisted upgrading because the machine used for this application was stable and performing well, but with end of support approaching for Win10, I updated to Win11 a few months ago and have only had this problem since that upgrade.
Given I’ve spent so much time trying to debug the problem, I was heartened by finding these two references: Video sometimes does not start when reinitializing in Windows 11 and Flaky JavaFX ERROR_MEDIA_INVALID MediaException.
These reinforce/confirm my view that the problem has occurred since updating from Win10 to Win11, particularly as the last comment in the first reference says “Checked with attached testcase in Windows 11, Issue is reproducible . . . . . whereas Issue is not reproducible in Windows 10.” And in the second reference which shows the OS as Win11 it says “As you can see, in player.setOnError() the code allows to re-try opening the file, which does work. So a typical run starts the first movie without problem. For movie 2 it needs 1 re-try, movie 3 needed 7 re-trys, and movie 4 needed 3 re-trys. But I also have runs where the application needed to re-try the first movie and all others were fine. So technically each movie is "showable".” is exactly the behavior I see.
So is the only solution to find an old Win10 laptop just to run this application?
EDIT: I should say that the "flaky" issue with MediaView only relates to the playing of videos. The same application can use images in lieu of videos in the sequencer and that continues to work flawlessly, even after the Win 10 to Win11 update.
Last edited: