LED processing: Flickering if there is ANY movement

  • Hi,

    I have weird flickering problems with the image processing. As soon as there is ANY movement on the screen, ALL the LEDs start flickering for some reason. This happens especially in dark scenes.

    First I thought that this is a hardware problem with my LEDs or grabber, but it is also visible in the LED live view in the webinterface and is unrelated to the capturing method (happens with direct screen capture or HDMI grabber).

    The LED smoothing option has no affect.


    Forgive me if this has already been asked multiple times, but I wasn't able to find a flickering issue that is unrelated to the LED hardware.


    Here's a video of the issue:

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.


    Link if the embed is not working: https://www.youtube.com/watch?v=-ADdiAfPOP8




  • and is unrelated to the capturing method (happens with direct screen capture or HDMI grabber).

    did you run the Hyperion.NG on expertmode and alter the grabbersettings? eg pixelFormat and FPS settings.


    there's a few settings that you can do that will eliminate "flutter" in dark scenes for the most part. I will share them to you.

  • did you run the Hyperion.NG on expertmode and alter the grabbersettings?

    I'm not really sure, but I probably once was in expert mode on that instance.

    If I remember correctly I changed something in the USB capture settings, I think it was changing the encoding format.


    But what grabber settings and FPS do you mean exactly? I haven't found anything that is exclusive to the expert mode (by switching between modes and comparing).

  • I think it was changing the encoding format.

    thats the one.


    these are the settings i use.

    rood/rood/rood is a fault in the coding of Hyperion.NG, there should be R/G/B


    this setting is for disable leds bij dark scenes

    the signal threshold also.


    viel spass!


    FPS setting on my system is 25 frames per second with 720p

  • I have now changed the encoding format from YUYV to MJPEG and to 25 FPS but it makes no difference at all.

    After I finally found them, I set the settings from your screenshot but they also do not help.

    I expected that because as said, it happens no matter from what source, be it the USB HDMI grabber or a direct screen capture (depending on my input device I use a different method). The settings you've mentioned are only for the USB grabber.

  • troubleshooting is marking down al possibility flaws so that you hopefully can find the problem.


    we are here to trying to help people, especially the dev's. I get it that you are let down but be aware with free source software and applications there's no guarantees.


    the first time i invested time/effort in Hypercon (before Hyperion.NG) costed me almost 2 weeks to get it working!


    so relax and sit back.


    what about your problem, you can try to run another version of Hyperion.NG that you have now. So roll back or upgrade and see if that's OK

  • I'm sorry if my last reply was offensive, I'm not mad at all and I really appreciate that you are trying to help me.

    English is not my native language and there it's even harder for me to not sound offensive. I just want to make things clear because I had the feeling you didn't fully understand me.


    troubleshooting is marking down al possibility flaws

    Exactly, and I already confirmed that it's not the grabber. And even if any setting for the USB grabber would fix that problem, the problem would still persist for the screen grabbing, so it will not fix the actual problem.

    Because of that it just doesn't make sense for me further experimenting in that area and only a waste of time for both of us.


    I will try out a few things like switching versions and complete resetting my config.

    • Official Post

    Flickering problems visible in the LED live view may not be related to grabber settings.

    This suggests a hardware or OS issue.

    Please attach a Hyperion debug log file (Hyperion-log.txt) and check the system load.


    regards pclin

    Dreambox ONE / TWO

    dreamOS OE2.6

    Amlogic S922X - 53.000 DMIPS - 2 GB RAM - 16 GB Flash - Twin-DVB-S2X Tuner - HDR10 - HLG
    -
    AudioDSP: miniDSP 2x4HD - Amp: Pentagon - Lautsprecher ELAC / ARENDAL
    LG OLED65BX9LB (PicCap, hyperion.NG webOS)

    FireTV 4K max

    -
    hyperion (classic) & Plugin HyperionControl | hyperion-ng 2.0.16-beta.1 (dreamOS)
    Hyperion-ng (Debian bullseye)
    -
    6 x ESP32/Wemos D1 mini - WLED - SK6812 RGBW-NW 60 LEDs/m
    FeinTech VSP01201 - Grabber Macrosilicon

    LG TV Hyperion webOS & PicCap


    Ambilight for ever

  • I did some more testing now. First I tried it with a fresh config but it's the same result.

    My Hyperion runs on CoreELEC with the Addon that comes from the CoreELEC repo. Sadly there are no other versions than 2.0.16 for testing.

    But I can definitively confirm now that it's not the grabber, because I just remembered that we also effects in Hyperion ^^

    and with the Rainbow swirl (and probably all other effects) it's exactly the same and very noticeable.


    Next I tried it with another instance on my PC using the sirfragalot/hyperion.ng docker image, on version 2.0.16 and 2.1.1, and there it's exactly the same, so it should be easily reproduceable (no hardware needed, just the default effect as source and /dev/null as LED device). But there's one difference: it's not permanent. It's very noticeable after a restart of Hyperion and after about 30 seconds disappears and is completely smooth. Although sometimes there is still some flickering at random times.


    But testing it with the rainbow effect, I just realized that this flickering is actually not noticeable on the real hardware LEDs. But still, I often see flickering just like in the preview when watching something where movement is in the center but mostly still image at the edges of the screen. Maybe these are different kind of issues?


    Here's the debug log from my test instance:

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!