Suppoprt for MPV video player

[BuyMyMojo]

MPV supports GLSL shaders and this shader could work great for watching older media but needs some modifications to work with MPV.

MPV Shader docs can be found here: https://mpv.io/manual/master/#options-glsl-shader

[mdrejhon]

Fantastic suggestion, but can you help this UFO call home a signal to the MPV planet? 🌎

(BTW, I'm still glad you posted it, because it helps produce a bat signal for that team.)

Since we're not the MPV team, we can tell you up front, some minor modifications to MPV will be needed to create a refresh cycle shader system within it. So, may you try the MPV suggestions page (maybe this one?), and link to www.github.com/blurbusters/crt-beam-simulator as well as this github issue item?

I prefer to to just only invent open source algorithms, and let other software developers implement them (or hire me to help them implement the algorithm into their app -- I do it sometimes -- just contact me via services.blurbusters.com)

Instructions for Developers of Shaders For Other Apps

Mandatory Requirement: CRT simulator shader must run every refresh cycle.

Even if you supply only 24fps, the mandatory "must have a shader reprocessed version of the same old frame" feature is true for my upcoming shaders:

• CRT simulator shader (today)
• LCD simulator shader for OLEDs (a true adjustable GtG to reduce stutters)
• Plasma simulator shader (2025-2026)
• 35mm projector simulator shader
• VRR-CRT shader (native display doesn't even need to be VRR!)

Obviously, you need large native:simulated Hz & framerate ratios, to successfully do all of this in an unrestricted way, but it begins to look very good at a ratio of 4 (e.g. 240Hz OLED), and quite fantastic at a ratio of 8 (e.g. 480Hz), and you know Hz is always going up.

The nice thing is that you have flexibility earlier in the chain:

(Begin)
(You can do any content frame rate) ->
(you can simulate any virtual refresh rate) ->
(My display simulation shader must process Hz times/sec)
(End)

As long as the CRT shader has uniforms relayed to it once every refresh cycle about current content frame rate and the desired simulated refresh rate (e.g. "I want to Play 24fps Content on a Simulated 72Hz CRT", then my shader can do the rest. My CRT simulator does not even need integer native:emulated Hz -- it is a float! The fact remains, however, my shader needs to run every native refresh cycle.

The nice thing however, is there's no restriction on content frame rate, and no restriction on refresh rate simulated. I just have to run my shader every native Hz, that's all. Rearchitecture your software accordingly, and it will work.

To help prepare for this, you need to rearchitecture your shader workflow to have a shader the processes every single native-display VSYNC event. So I need to run shader 240 times for 240Hz, or 360 times for 360Hz, even if your movie is playing back Charlie Chaplin at 18fps, or you're playing Lord of Rings at 48fps, or your regular Hollywood Filmmaker Mode content at 24p.

The dawn of open source display algorithms, with the starting pistol of the CRT simulator algorithm, requires a new workflow whereupon you have a refresh cycle shader independent of the underlying framerate (even though you can adjust variables, like change the simulated CRT Hz, you can simulate 72Hz CRT with 24p content, and 60Hz CRT with 60p content, and automatically switch the simulated CRT refresh rate without touching the output refresh rate). It's just a single shader variable.

Any video player authors need to rearchitecture their shader processor workflow to have a refresh cycle shader system in a separate CPU thread from the playback system, so that once the player delivers a frame, the refresh cycle shader can process it as many times as it washes (e.g. 240 times at 240Hz, regardless of 24p or 30p or 60p or 60i).

BTW, If the video player developers don't believe me, make sure you inform them of my credentials: I'm the author of the world's first 3:2 pulldown deinterlacing algorithm BTW (see December 15th, 2000 on Internet Archive Wayback Machine). Years of experience with (display+temporal) brillance, and I am now cited in over 30 research papers related to elements in the (display+temporal) universe.