[aljarry]

And some of those was my team and our CI. We were capable of replacing old hand-written video player based off DirectX.net in an enterprise app - mainly due to new requirements for supported codecs and video formats. No more list of codecs and installation order on target machines.

It was very easy to integrate - I've finished a POC with a lot of functionality rebuilt in just around 2 hours.

We had two issues that we spent quite some time on, though: 1. When jumping a lot from video part to video part, especially if reading movie files from NAS, we've seen the component hanging - the only way to automatically recognize it hanged was to parse warning logs and restart the component forcibly. 2. Lack of native per-frame backwards movement. It is video player, not video editing component, and there is only a way to move backwards a few frames at a time by slowly changing current position.

[vxNsr]

2 is a problem in their app as well. They explain that due to how they decode the file it’s not possible. I’m assuming it’s got to due with a decision that was made years ago in the architecture and would just be too costly to change today.