HyperHDR, MSP2130, WLED, SK6812 -> out of sync between image and Ambi-LED

[toerther-379]

Dear forum members and Awawa,

I moved from Hyperion to HyperHDR since I was never able to calibrate my colors in the other program.

My setup: FeinTech VSP01202, MS2130 USB Grabber (recently bought, but sorry, I don't understand how to find out if it's a new or old version. It is connected to a RASPI3B and only gives me mjpeg as option), RaspBerry3B (I think it only has USB2) connected to a PanaSonic TV, SK6812 Leds connected to WLED installed on a 8266.

My problem is, that the LEDs, the control TV Display in the HyperHDR WebInterface and the real TV display often run out of sync. It works for minutes and then I realize, the LEDs show the light from a scene secomds ago. Also the Control Display in the HyperHDR Webinterface is too old and sometimes looks like slow motion, but the LEDs also don't show the scene displayed in the web interface (so the TV screen, the WebInterface Screen an the Leds al show different things). After a coble of minutes it comes back to sync, before it happens again.

I played with many parameters in HyperHDR, sometimes it seem to be ok to be out of sync again after a couple og minutes.

Any idea, what I could do wrong?

Thanks a lot, T

[awawa-dev]

Hi
Does this also happen if you don't have live preview turned on? The video preview puts a lot of strain on the network and HyperHDR, so if your bandwidth is limited (or CPU when high video resolution is selected), it will only make things worse. Set the grabber resolution to minimum and turn on quarter of frame mode. What is the RPI CPU load on the main panel? Are there any errors in the logs and what do the statistics generated every minute look like? Is it the same if you turn on the effect instead of the grabber?

[toerther-379]

I checked now for one hour, never switched on the live-preview and the Leds are still synced. Could this have happened because I opened the Live Preview (Btw, I'm on 21Beta1)

Another thing I observed:

Set the USB Recordings settings: Resolution: 640x480, 25fps, mjpeg, Quarter Frame Mode enabled
-> CPU 11%, Temperature 65°C
Switching the RASPI off/on (power off/on power supply), restart, and and don't change any settings -> CPU 30-35%, Temperature >75°C (increasing)
Going to Videorecording->Press Save Settings-> Nothing changes.
Going to Videorecording->Change Resolution to anything->Save Settings->Change Resolution back to 640x480->Save Settings-> CPU comes back to 11%..

Set all Video Recording settings to "Auto" brings the CPU to 13% and the temperature to 68°C.
Switching the RASPI off/on and don't change any settings (all automatic) -> CPU 50-60%, Temperature >82°CPU.

So maybe my sync problem is a temperature issue. Is there any reason, why the power consumption is different after a reboot? Is there a better way to power down the RASPI than a hard shut down?

Thanks for your feedback

[awawa-dev]

Hard to say, it depends on what you have installed, if the OS updates are enabled at startup and whether it's the GUI or server version. Even when you set resolution to 'auto' you can view selected resolution on the first page. If you have the RPi in a case, after a long time it will overheat, at over 80C for sure it will throttle and significantly reduce performance just like that.

[toerther-379]

Honestly speaking, I cannot answer all your questions.
The Overview Page always shows me : Video Modus 800x600x60 MJPEG, independend from what I set in video recording (edit: Just found out that I have to select the resolution/fps using the "Info" button rather than selection it in the pull down menues, then it also shows the correct info in the overview page, also after reboot. But the CPU-% still increases after reboot).

I installed Debian on my RASPI and then added the HyperHDR repository, (https://awawa-dev.github.io), Sorry for being so unprecise. Maybe I start with buying a metall housing for the RASPI for better cooling.

Best, T

[awawa-dev]

I don't have a clue. Use 'htop' to observe processes after you ssh to RPi and install it.

[awawa-dev]

Also compare in HyperHDR logs if the configuration has indeed changed after your action.

[toerther-379]

log.txt

Here are the htop screenshots when set to 5% (a), after reboot (b) when CPU is on 25% and (c) when video settings are changed and CPU is back to 5%.

The RASPI was startet at 5pm (17:00:00) or a few seconds before, CPU 25% and at 17:10 the video settings are changed and the CPU goes back to 5%. Sorry, the log file is over my head. I see a lot of WLED messages, but ...?!

[awawa-dev]

First of all you are a victim of this kernel bug that I mentioned in the v21 release note => #848 you must downgrade the kernel as other users described (quite easy, one command, in HyperHDR set brightness/contrast/hue/saturation controls to default 0 and restart). Not sure if it is a side affect of this kernel bug too, but your grabber switches itself to 1920x1080p despite it was configured to 640x480 (and it worked that way for about 1 sec)

2025-01-06T16:59:35.073Z [IMAGETOLED_MNG0] Total index number is: 5744 (memory: 5744). User sparse processing is: enabled, image size: 320 x 240, area number: 268
2025-01-06T16:59:36.816Z [IMAGETOLED_MNG0] Total index number is: 36506 (memory: 36506). User sparse processing is: enabled, image size: 960 x 540, area number: 268

One more thing: before downgrading kernel please also check dmesg after restart, maybe some errors will be there too

[awawa-dev]

Thanks to one of ours users maybe they will fix it in 6.12. Please give them a feedback if it works or not: https://forums.raspberrypi.com/viewtopic.php?p=2281694#p2281694

[toerther-379]

Colors in 6.1 are OK with HyperHDR brightness/contrast/hue/saturation controls set to 0
in 6.12 colors are the same (wrong) as in 6.6. This all doesn't affect the CPU usage, maybe it's time for a new unit (Intel N100 mini PC?) .

[awawa-dev]

So it still switches to 1920x1080 in HyperHDR logs and dmesg is clear? There may also be something wrong with the grabber firmware. Although from what you write that it only offers MJPEG, I suspect that you have an old and rather problem-free version and our F3 firmware probably won't change anything. I'll try to find my RPi3...

[toerther-379]

In 6.1 dmesg looks good. I'm not sure about the 1920x1080. Please don't waste too much time with this old device...

[awawa-dev]

This resolution switching is quite disturbing, and there are no other traces apart from specific entries in the logs and a general drop in performance...

[toerther-379]

Will send an updated log tomorrow. Thanks again for all your great support

[awawa-dev]

FYI I installed clean HyperHDR v21beta1 SD image and run it on RPi3. The kernel bug is present (wrong defaults):

2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:425) Device has 'brightness' control => min: 0, max: 100, default: -8193
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:431) Device has 'contrast' control => min: 0, max: 100, default: 57343
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:437) Device has 'saturation' control => min: 0, max: 100, default: 57343
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:443) Device has 'hue' control => min: 0, max: 100, default: -8193
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:232) Searching for USB3.0 UHD: USB2.0 HD (video0) 640 x 480 @ 20 fps, input: -1 (mjpeg)
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] *************************************************************************************************
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] Starting V4L2 grabber. Selected: USB3.0 UHD: USB2.0 HD (video0) [/dev/video0] 640 x 480 @ 20 fps mjpeg input -1
2025-01-06T23:31:09.313Z [V4L2:USB3.0 UHD: US] *************************************************************************************************
2025-01-06T23:31:09.314Z [V4L2:USB3.0 UHD: US] (V4L2Grabber.cpp:867) Hardware cropping is not supported: ignoring
2025-01-06T23:31:09.314Z [V4L2:USB3.0 UHD: US] Set device input to: Camera 1
2025-01-06T23:31:09.333Z [V4L2:USB3.0 UHD: US] Set resolution to: 640 x 480
2025-01-06T23:31:09.354Z [V4L2:USB3.0 UHD: US] Set framerate to 20 FPS
2025-01-06T23:31:09.358Z [SMOOTHING0] Using linear smoothing procedure (1)
2025-01-06T23:31:09.359Z [V4L2:USB3.0 UHD: US] Brightness set to: -8193 (default)
2025-01-06T23:31:09.363Z [V4L2:USB3.0 UHD: US] Contrast set to: 57343 (default)
2025-01-06T23:31:09.367Z [V4L2:USB3.0 UHD: US] Saturation set to: 57343 (default)
2025-01-06T23:31:09.371Z [V4L2:USB3.0 UHD: US] Hue set to: -8193 (default)

but I have only one such message after the grabber took control:

2025-01-06T23:31:12.312Z [IMAGETOLED_MNG0] Total index number is: 1600 (memory: 1600). User sparse processing is: disabled, image size: 320 x 240, area number: 1

and the CPU is low:

The HDMI cable was not connected to the ms2130. Maybe it's a grabber firmware issue afterall?

[toerther-379]

From what I can say I get decent colors in the live preview with kernel 6.1 if brightness/contrast/hue/saturation controls set to 0. However, changing e.g. the contrast from 0 to 1 already has a huge effect, going from decent colors to almost black. So there is no chance to adjust anything there.

in kernel 6.6 and 6.12 the colors with brightness/contrast/hue/saturation controls set to 0 are wrong (blue gras instead of green), but the values can be adjusted very well (somewhere in the range between 40..80).

The CPU problem ist still there with the different kernels. What 'more modern' unit would you recommend as a replacement for the rpi3b? Should I buy a MS2109 for testing?

[awawa-dev]

if brightness/contrast/hue/saturation controls set to 0. However, changing e.g. the contrast from 0 to 1

that's expected: 0 is a default value (=do not set) in HyperHDR for the grabber control (for example 50 in normal circumstances) and 1 is just 1.

The CPU problem ist still there with the different kernels.

Do you have an auto-start script somewhere that modifies grabber state for example using v4l2-ctl to set brightness/contrast/hue/saturation? Otherwise, nothing else comes to my mind except the firmware, because I can't repeat it on my RPi3

[awawa-dev]

I moved from Hyperion to HyperHDR since I was never able to calibrate my colors in the other program.

Also did you uninstall or disable Hyperion? Because something is changing capturing resolution and it's not HyperHDR.

[toerther-379]

No, no additional scripts, HyperHDR was installed on a new SD.
I think we'll stop here, you reminded me that the 3b is almost 10 years old. NO need to spend time here....

Anyway, if you want me to test something let me know. Thanks for your great effort

[awawa-dev]

Yes, for me the main problem of RPi3 is the lack of USB3.0. RPi4 or N100 could be an interesting upgrade, but if the MS2130 firmware is the problem then the issue may come back later.