Replies: 6 comments 22 replies
-
|
Thanks for the update. 👍🏼 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I consider it. Unfortunately beta/alpha are hardcoded in several strange places like web interface and custom code in installers. And few external projects already adjusted to HyperHDR release versioning so it would be a breaking change for them. Today I also made a mistake removing old v21.0.0beta1 tag (my typo when hot-fixing bugged softprops/action-gh-release#562), so I had to restore it first before publishing v21.0.0beta2. That could have caused some unnecessary messages from Github for users following HyperHDR. I hope it won't happen again. |
Beta Was this translation helpful? Give feedback.
-
|
What is correct way to update? On the update page it says "On top you could update or downgrade your version of HyperHDR whenever you want. Sorted from newest to oldest" but where is "On top"? Nothing is clickable on that page for me. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I've updated via apt was just wondering if there's GUI method for package management. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I tried to install the HyperHDR-21.0.0.0beta2-Linux-aarch64.deb package but getting several errors: E: Invalid archive member header Got no issues with installing the older version HyperHDR-21.0.0.0beta1-Linux-aarch64.deb |
Beta Was this translation helpful? Give feedback.
-
|
Got this as checksum: Is there a reference checksum, for this file, where I can verify this? |
Beta Was this translation helpful? Give feedback.
-
|
seems ok, why dont you upgrade using apt if you have a HyperHDR repo connected?
|
Beta Was this translation helpful? Give feedback.
-
|
Tried that first but it seems that the architecture is not supported: N: Skipping acquire of configured file 'main/binary-arm64/Packages' as repository 'https://awawa-dev.github.io noble InRelease' doesn't support architecture 'arm64' Weird though that the older version is installing without issues |
Beta Was this translation helpful? Give feedback.
-
|
ubuntu arm64 is not officially supported so the repo is missing this package. you can compare these two installers details using eg. |
Beta Was this translation helpful? Give feedback.
-
|
ok thanks for your quick replies! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, there is no |
Beta Was this translation helpful? Give feedback.
-
|
Where? |
Beta Was this translation helpful? Give feedback.
-
|
When i do |
Beta Was this translation helpful? Give feedback.
-
|
yes something is wrong, seems aarch64 packages where built as a armhf |
Beta Was this translation helpful? Give feedback.
-
|
in fact armhf overwritten aarch64/arm64 packages having wrong package name |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic work btw! |
Beta Was this translation helpful? Give feedback.
-
|
@kenshin-17 @JayJay-SmartHome @EddyBurnett |
Beta Was this translation helpful? Give feedback.
-
|
and if you uninstall HyperHDR first? |
Beta Was this translation helpful? Give feedback.
-
|
I went ahead and just recreated the LXC again, and now it's working fine. I think the issue was that the script didn't migrate over to the new repo from tteck's config correctly. Thanks for your help nonetheless. |
Beta Was this translation helpful? Give feedback.
-
|
BTW which Debian and architecture? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
strange, it was not affected by the descibed issue with arm runners. but apt list on the server was recreated. |
Beta Was this translation helpful? Give feedback.
-
New test release HyperHDR 21.0.0.0beta2 brings few more features and fixes:
Older HyperHDR 21.0.0.0beta1 changes:
The architecture has been rebuilt once again, this time focusing on further eliminating heavy dependencies from the past. In addition to lower resource consumption, you will definitely notice how much the installers have been slimmed down (they still contain all the necessary dependent components) and the HyperHDR application itself.
The DirectX grabber has been expanded with a multi-monitor option. You no longer have to use external applications to capture a second or third monitor. Do you still use them? So please make sure they provide full acceleration support by the graphics card as HyperHDR does including using pixel & vertex shaders to scale the textures before sending them from the graphics card memory to the computer so as not to block communication resources which can cause for example: performance drops in games. It is also the cheapest and most effective alternative to HDMI grabbers and splitters on Windows x64 platforms such as multimedia miniPCs with N100. All you need for such setups is USB LED driver like Pico with HyperSerialPico.
More about DirectX 11 grabber can be found here: https://github.com/awawa-dev/HyperHDR/wiki/DirectX-11-software-grabber
Another new feature that I think will be useful for many people is automatic tone mapping. In case you can't control it from outside via the application's API this is the solution for you. Once enabled HyperHDR will analyze the video image and enable it automatically for dark and faded raw HDR signal and disable it when it detects bright SDR image with normal colors.
More about automatic tone mapping can be found here: https://github.com/awawa-dev/HyperHDR/wiki/Automatic-tone-mapping
In the past, the process of calibrating the grabber's LUT to obtain the best possible colors was quite problematic: to do it, it usually required a PC set. HyperHDR v21 introduces a small revolution here because now all you have to do is play the calibration MP4 file in your favorite player and HyperHDR will take care of the rest. Thanks to this, we calibrate not only the grabber and TV, but also your default video player. HyperHDR was also the first to introduce support for the NV12 codec for flatbuffers, which opened completely new perspectives for the calibration of external systems because standard RGB flatbuffer stream was usually already processed at the source.
⚠️ ⇒ Elgato dirty tricks with the HD60X model ⚠️ #1010
You can find more about the new LUT calibration using MP4 files here: https://github.com/awawa-dev/HyperHDR/wiki/lut-calibration
If you own Elgato HD60X make sure you read it
I am also pleased to announce for the first time support for the 10-bit P010 codec, which is already appearing in increasingly cheaper grabbers such as the UGreen 25173 (which can only gain in attractiveness after what happened with ELgato HD60X, more: Elgato dirty tricks with the HD60X model ⚠️ #1010). While it does not contribute much to SDR signals, it changes the situation a lot when it comes to HDR by expanding the default narrow bandwidth range above the standard 8-bits, minimizing the quantization effect. Another advantage is that it is usually a raw signal not damaged by the grabber trying to process the HDR signal as SDR. The format is supported by default by Windows, and when it comes to Linux, I created a patch for the UVC module so that it also works on this system.
The HyperHDR SD image already has a patch for P010. Note that it is based on the newer Bookworm so configuring wifi via wpa_supplicant will no longer work: for this you need to use the Raspberry PI imager installer (wpa_supplicant autoconfigure removed in bookworm but not replaced with other mechanism raspberrypi/bookworm-feedback#72). For Raspberry Pi 3b and Zero 2W users, I would like to remind you about a bug in the Raspberry Pi kernel that can cause incorrect display of colors on Bookworm (RPi 3b & zero 2 kernel bug: swapped colors ⚠️ #848).
More about support for the P010 format can be found here: https://github.com/awawa-dev/HyperHDR/wiki/p010-video-format
Full changelog:
This discussion was created from the release HyperHDR 21.0.0.0beta2.
Beta Was this translation helpful? Give feedback.
All reactions