Shader Compile Time Mitigation

[i2iRobert]

We're writing a Windows Flutter app, the issue we've come across with dart_vlc appears to be shader compilation time.

The example app demonstrates the issue quite clearly, as it loads first time it takes around 10 seconds to "compile" the player for the first time.

Which can be seen in this screenshot of the performance dev tools when running the app we are working on:

I attempted to capture the "jank" on the example app but this happens as the app is loading and the performance tools aren't opened on load.

What would be the best way to mitigate this "compile" time on windows, as you don't appear to be able to pre cache shaders on Windows?

In the example app the video player is the first screen you see, so the delay appears to be "loading", however in the app we've made the video player is not the first thing you see, so when you click for the video player there will be a solid 10 seconds of loading/jank/pause before anything happens, making for a poor user experience. This only happens the first time on a fresh build/install, once its "compiled" once it loads as fast as I would expect.

Any pointers, or suggestions are welcome.

[alexmercerind]

Sorry, this has nothing to do with shader pre-compilation etc. etc. It has nothing to do with Flutter either.
I have explained everything in simpler terms here: Video: Hardware Acceleration.

---

Also, I as the author of package:dart_vlc don't feel satisfied for it's performance. I have started a new project package:media_kit which offers better, performant & stable media playback which is hardware accelerated. Please consider using it instead.

This project (package:dart_vlc) will also receive improvements in future, depending upon feasibility as discussed on the issue linked above.