HyperHDR 22.0.0beta1

[awawa-dev]

This is a v22.0.0beta1 test release intended for community evaluation and feedback before the stable version. The highlight of this update is the revolutionary Infinite Color Engine, which breaks the 24-bit barrier using high-precision floating-point arithmetic. By shifting transformations to linear sRGB space, we provide physically accurate light reproduction and native deep-color support for devices like Philips Hue and LIFX. This update also marks our transition to the C++20 standard, leveraging modern language features to improve code performance, robustness, and long-term maintainability.

Performance has been significantly optimized, with video decoding for YUV, NV12, and P010 codecs seeing speed improvements of up to 46%. Linux users will benefit from an enhanced Pipewire implementation featuring GPU scaling to drastically reduce CPU load. Additionally, we have added native PWM support for Raspberry Pi 5 and transitioned all installers to the modern Qt 6.8+ framework to reduce installer size and ensure version consistency across all supported distributions. We encourage you to test these new features and report any issues to help us finalize this major release.

Warning

Known issues and fix pack: #1410

The Linux Debian/Ubuntu repository already contains the patched v22beta1.
Included until 2026‑01‑29 — Fix: Initial smoothing surge after a period of static video input (c1d67d7).

To refresh the package on Debian/Ubuntu:
sudo apt install --reinstall hyperhdr

For other systems, please use the installers available in the GitHub Actions tab.

---

Changelog

• Infinite Color Engine - Breaking 24-bit Limits (Infinite Color Engine #1261)
  • Floating-Point Precision: All color computations use high-precision floating-point arithmetic, eliminating cumulative rounding errors for more accurate results
  • Linear sRGB Accuracy: Core color transformations are processed in linear sRGB space, ensuring physically correct and consistent light reproduction
  • Deep-Color Support: Compatible devices, including Philips Hue lamps, LIFX and HD108 LEDs, can take advantage of rendering beyond standard 24-bit RGB color depth.
  • Advanced color smoothing algorithms: inertia-based physics, exponential, and perceptually-uniform YUV/RGB interpolators for more fluid and natural color transitions
  • Start migrating to modern C++20
  • Add Hybrid RGB Smoothing Interpolator (Add Hybrid RGB Smoothing Interpolator #1379)
  • Add Infinite Color Engine support to file LED driver (Add Infinite Color resolution to file LED driver #1311)
  • Infinite Color Engine: add LIFX support for beyond 24-bit rendering (Infinite Color Engine: add Lifx support for beyond 24-bit rendering #1299)
  • Infinite Color Engine: fix for YUV & hybrid interpolators (Infinite Color Engine: fix for YUV & hybrid interpolators #1302)
  • Fix RGBCMYK calibration (Fix RGBCMYK calibration #1369)
• Significant speedup for YUV/NV12/P010 and related codecs (Significant speedup for YUV/NV12/P010 and related codecs #1374)
  • Performance increased up to 46%
  • Compared performance of RPi 5 vs N100 in HyperHDR video decoding benchmark
  • Switched to modern C++20 format style logging
• Improved, faster Pipewire + option to disable EGL (Improved, faster Pipewire + option to disable EGL #1397)
  • GPU Scaling (EGL/DMA mode) - scales the desktop on the GPU; only the small final texture is sent to the CPU
  • Optional HW acceleration - option to disable EGL in the Pipewire configuration
  • Auto-resume - automatically restarts the grabber if dimensions change or the stream fails
  • EGL texture caching - improves performance by reusing textures
  • MemFD caching - reuses file descriptor memory mappings
• Add PWM support for Raspberry Pi 5 GPIO/PIO (Add PWM support for Raspberry Pi 5 (RP1/PIO) #1317)
  • Reported necessary kernel LED module changes to the RPi team
• Full FTDI and libFTDI dynamic runtime support. Thanks @nurikk-sa for help (Full ftdi and libftdi dynamic runtime support #1155)
  • libFTDI support on Linux/macOS
  • support of manufacturer "ftd2xx.dll" driver on Windows
• Migrate ALL installers to Qt 6.8+. Breaking: docker build subsystem (Migrate ALL installers to QT6.8.3 and up! Breaking changes: docker repo improvements #1203)
  • reduced size of HyperHDR's installers
• Philips Hue driver: add option for linear or nonlinear RGB color output (Preparation for v22beta1 release #1401)
  • for recommended nonlinear you may increase gamma to 2.2 in the processing tab
• Windows DX grabber: multi-monitor capturing status check & restart
• DirectX grabber: support for portrait mode (DX grabber: portrait mode support #1200)
• Update language files. Thanks @AstaRom (Update language file's #1396, Update language file's #1300, Update language file's #1288, Update language file's #1131, Update language file's #1402, Update language file's #1403)
• Smoothing: restore continuous output control + stricter end detection (Smoothing: restore continuous output control + stricter end detection #1337)
  • Fix rendering w/o continuous output (Fix rendering w/o continuous output #1377)
• Hide HyperHDR from the macOS Dock (Hide HyperHDR from the macOS Dock #1345)
• Add replacement for libglib2.0-0 (armhf, Y2038 bug) (Add replacement for libglib2.0-0 (armhf, Y2038 bug) #1341)
• Add QElapsedTimer include to DriverNetLifx.cpp Thanks @arfoll (Add QElapsedTimer include to DriverNetLifx.cpp #1330)
• Add just released Ubuntu 25.10 & incoming Fedora 43 (Add just released Ubuntu 25.10 & incoming Fedora43 #1304)
• Add Windows-2025, macOS-15-intel, Debian Trixie and migrate others (Add Windows-2025, macos-15-intel, Debian Trixie and migrate others #1296)
• Fix for OpenSSL on macOS (needed by HTTPS/TLS) (Fix for OpenSSL on macOS (needed by https/tls) #1290)
• Updated Home Assistant module to enable SSL support. Thanks @josh-blake (Updated Home Assistant module to enable SSL. #1249)
• Don't rely on plutovg CMake script to detect C++11 threads support (Dont rely on plutovg cmake script to detect C++11 threads support #1253)
• Remove min/max limits to allow using only a very small part of the screen capture as input area. Thanks @markusressel (remove min/max limits to allow using only a very small part of the sc… #1175)
• Update CMake configuration to add support for additional system libraries. Thanks @hatch01 (Update CMake configuration to add support for additional system libra… #1158)
• Add USE_SYSTEM_SDBUS_CPP_LIBS option (Add USE_SYSTEM_SDBUS_CPP_LIBS option #1140)
• Update LunaSVG to v3.1.0 (Update LunaSVG to v3.1.0 #1139)
• Fix ENABLE_PIPEWIRE_EGL=OFF build (Fix ENABLE_PIPEWIRE_EGL=OFF build #1138)
• Amlogic grabber restore & refactor. Thanks @santievil (Amlogic grabber refactor #1119)
• Fix Dutch translations. Thanks @dijkstrar (Fix Dutch translations #1122)

---

This discussion was created from the release HyperHDR 22.0.0beta1.

[Duese123]

Nice! I had the issue that after update the colors were wrong. I had set up BGR. I had to go to different color and then back to BGR and the order was fine then... I guess the update overtook RGB as default (cause green was working)

[awawa-dev]

For grabbers and selected codecs there is an automatic tone mapping feature in the processing tab since v21.

[Duese123]

By the way after a time leds began to flicker heavily. It was because of Filtering Downgrade to oder Version solved it. I could not get it to solve otherwise. Is there a bug known? It came after some time...

[awawa-dev]

Use latest build from github action (or apt reinstall from repo. instruction in the first post) and restart settings to default to exclude some configuration isues. It's hard to figure out much more from this general description without more details. I dont such issue on my setup even after few hours.

[inferno1231]

thanks for the reply. True i was changing it via remote page.. since my denon is not supporting anymore https://192.168.0.35:10443/ajax/general/get_config?type=12 after newest update and giving html error 500, my auto HDR recognizion is not working anymore... but this is of course another topic and not hyperhdr relevant.

Try /ajax/info/get_config?type=3

[Duese123]

you are my man!!! Thanks a lot!

[ocaydin]

Hello. I started using this application for my Skydimo LEDs. First of all, thank you. Much better than the original app. I have a question, is there a setting to turn off the LEDs when the screen is black? When there is a black screen, the LEDs glow slightly white and this is something that undermines the experience.

[schwatter]

I have the same problem. Also after update to latest actions build https://github.com/awawa-dev/HyperHDR/actions/runs/21886255111
I tried COLORED true and false without luck. The log actually says, that i have not set so zero. But in the webinterface it is zero @Remote and also @image processing with saving and fully restart...mhhh
log.txt

[schwatter]

Ah and i forgot to write, when i adjust higher plus the led got brighter (yeah normal) and then with minus lower i get the max minimal
value of 0,0025.

[awawa-dev]

If your video input is not producing absolute zero (pure black), HyperHDR will process those values accordingly.

Even with 'Minimum Backlight' at 0, any noise or gray-ish tint from your grabber and even with Gamma settings cannot bring it to zero, resulting in a glow. This is not a bug; it's how image processing works. If you want me to look at why you see '0.0025' in your specific case, provide the logs. Without logs, I assume it's just hardware noise from your setup. No full logs = it lands in the trash.

[schwatter]

I provided a log. It is direct above the picture. If it is not enough i will dig deeper.

[schwatter]

Ok, i found it. First i thought gamma was the problem. 2 or above 2,5 fixed it on some way, but yeah sometimes some led's get a bit
green. I tested all of my cheap grabbers, no luck. But all the years i wasn't infected, ummhh. From Hyperion to HyperHdr21 and then HyperHdr22...all fine.
The solution was simple, switching from videoformat mjpeg back to yuyv. I forget that...now all black and minimum backlight level stays at 0.

[el-bakkali]

thank you @awawa-dev for all your hard work and efforts.
I'd like to request precompiled Docker images that allow users to run HyperHDR directly without needing to build from source.
The HyperDockerBuilder repository provides build environments for compiling HyperHDR, which is helpful for developers.
However, for end users who just want to run HyperHDR, the build process is still a barrier , even with Docker, it requires understanding compilation, build scripts, and dependency management.

Providing ready-to-run Docker images (e.g., on GitHub Container Registry or Docker Hub) where HyperHDR is already compiled and configured would be a nice add for the future hopefully.

Many people have moved away from Raspberry Pis due to price/availability, opting for more affordable options like N100/N150 mini PCs or x86 thin clients such as the Dell Wyse 5040.

Additionally, since devices like the UGREEN 25173 capture card are becoming popular, we could even include the modified kernel for P010 codec support for amd64/arm64, which would be much easier to maintain in a single image(but i understand this is more work and may need volunteers)

I see the following advantages for community:

• Lower barrier to entry for new users
• Easier deployment on NAS devices, servers, and headless systems(promox etc)
• Simplified updates (just pull new image)
• Consistent with how most self-hosted applications are distributed (Home Assistant, Jellyfin, etc.)

[awawa-dev]

Hi,

Yes, I’m planning to do it (#1126); maybe it’ll make it in before the v22 release. Regarding the RPi vs. PC situation, it looks like a migration in the opposite direction is brewing: even the budget N100s have nearly doubled in price due to SSD/DDR4/DDR5 costs. RPis have gone up too, but not quite as astronomically. Unfortunately, the outlook is grim—AI might eventually sink projects like HyperHDR because there won't be anything left to install it on... though we did survive the post-COVID availability crisis. Just in case, I’ve still got those TV boxes ;-)

[ender]

Thank you for your hard work! Love this project and can’t wait to see it in action when I rebuild my setup 😄

P.S. Have you considered making a Discord server for the project? You seem to be the sole respondent to most of the posts here and lots are fairly simple issues. Just wanted to put it out there that maybe us users can help each other out. Thanks again for your dedication to this wonderful software!

[awawa-dev]

No, I’m not planning to. I don’t have the resources to run a server and fight off Discord bots. Besides, Discord isolates content from search engines, which is a major drawback. It’s mostly good for ad-hoc support, but AI has already taken over that role anyway. I’d rather focus on creating tutorials and documentation; even if AI ends up using them, they’ll still reach the right people when they actually need them.

[outsyde617]

Hey, sorry if this not the right place for this, but I had things working great on my Mac mini, but then tried changing a crop setting and now the web interface won't load and nothing works. I have tried deleting and reinstalling the app but I am still not getting output.
After a reboot, the app will load, I can click settings, and it gives me the login page, but nothing happens after entering my password.
Are there other locations I need to delete items from to start over? Or can I just move the app to the trash?

[awawa-dev]

Hi, take a look in your home folder. To start from scratch, make sure HyperHDR is not running. There’s a .hyperhdr folder (may be hidden ⚠️ ) - rename it and restart HyperHDR. If it’s not a problem, send me the hyperhdr.db file from the db folder inside that old .hyperhdr directory (my email is on my GitHub profile), or upload it here if you’re comfortable sharing it.

[awawa-dev]

Also check your old db folder for backups.