I can confirm that this new verison works with H264 4K non-HDR movies as well, thanks for that!
The other file I was trying to test with was a hevc 4k HDR file, there the leds either remained blank or showed some random static color, so it seems that it is not (yet ) working.
I uploaded two more slow-mo vids of smoothing testing whilst a video grabbing (“video_” prefix). As i can see, smoothing doesn’t work for it either Dear @Portisch, i express my deepest gratitude to your work, and i will use it “as is” with my pleasure for sure (coz it’s awesome)! But if you have an interest yet - please, look into this problem too
@benoe, it was discussed many many times before For example, here is described a simple solution for HEVC, but keep in mind, that it heavily loads the RAM’s I/O, so you can face some trouble (artifacts or even system hanging) on cheap boxes.
Just instant (literally, per-frame) color change from blue to black. I use this video for testing, smoothing was set to 50Hz. My eyes pretty sensitive (above overage), especially as for strobing effects, and i can see the difference with an unarmed eye. That’s why i recorded slow-mo videos for you
This is not clear for me.
First: You know the framerate of this video? Remember the frame grabbing speed == frame rate. So do not use video’s with a low frame rate like 24Hz.
Second: You talked about OSD (user interface) and not video!?
Hyperion has built-in smoothing mechanism, which interpolate color changing. It calculates missing intermediate colors if the LED output FPS set higher than grabbed FPS. So for your latest implementation, it should be like that: video frame rate (f.e. 24Hz) == grabbing speed (same 24Hz) != LED output frame rate (50Hz thanks to smoothing). And resulting LED output should be stepless and fluent no matters how low original grabbed FPS is.
Firstly i noticed and reported the problem with UI, and promised to check the video grabbing either. Later (today) i checked it and confirmed that video grabbing doesn’t use smoothing either.
I’m using non modified Hyperion.ng and CE stable image and for me echo 3 (instead of 1) in my autostart.sh is working great for all content including 4K HDR. I haven’t noticed any performance issues yet.
echo 3 | tee /sys/module/amvdec_h265/parameters/double_write_mode
All these other problems are off-topic. Here we talk only about the slow-downs.
So for other features/bugs make a new thread or if hyperion.ng related go to the hyperion support forum.
what i can say: it IS smoothing GUI and Video. i can not say if it is as smooth as before Portisch´s modifications - but i cant see any difference.
vevs: maybe you have to play with smoothing settings because they change with capture frequency as Portisch said…?