Replies: 2 comments 18 replies
-
|
Hi |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Wow, so fast! Someone is using the TV now, so will test as soon as it's possible. |
Beta Was this translation helpful? Give feedback.
-
|
I already had this ready in my backlog... however, the old PWM hardware solutions for the older Raspberry Pi were of terrible quality, so I hesitated. Here we have PIO taken from rp2040 so maybe it will be better...we will see. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Some progress already 👍 I have setup the I get a new device YAY! The light strip lights up! However, it's not changing colors. This is very likely a user error as I'm new to HyperHDR. Important as it could influence: I have four strips and only one lights up. (37 of the 207) - as I can properly test/see the installation, I realized something might be wrong. I need to check the wiring during daytime, will report back. Observation: When I change settings such as changing RGB to GBR, I see the LEDs change (color 'hops' to the next LED). I do not trust my capturing yet, however, I expected when I select an effect (remote control > colors/effects > 'Rainbow swirl fast', I should see something move. The LEDs stay the same. Logs: More info on the Raspberry pi 5: 
|
Beta Was this translation helpful? Give feedback.
-
|
Who knows? this RP1 driver expects just raw RGB/RGBW and you must configure it properly (rgb/rgbww, led number both in HyperHDR and in overlay). Make sure you have valid video/effect input. |
Beta Was this translation helpful? Give feedback.
-
|
No you dont have it correctly. Verify ALL settings in HyperHDR again: |
Beta Was this translation helpful? Give feedback.
-
|
I gave you poor advice on how to define the RGBW strip in config.txt (the instructions have been updated) and corrected the writing to the LED device. Unfortunately, I don't have good information: the author of this driver customized it for himself and used a hardcoded gamma that can't be disabled in the settings. New installers: More info (updated): |
Beta Was this translation helpful? Give feedback.
13 replies
-
|
It's 21 not 22 beta 0. You should set correct PKG_VERSION in the HyperHDR package configuration to match specific commit and because it's not on master yet also: PKG_GIT_CLONE_BRANCH. Source https://github.com/LibreELEC/LibreELEC.tv/blob/libreelec-12.0/scripts/get_git |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your guidance! Will try on Tuesday. |
Beta Was this translation helpful? Give feedback.
-
|
Good news: the fix for the kernel driver module is available raspberrypi/linux#7108 |
Beta Was this translation helpful? Give feedback.
-
|
and corresponding installers that can utilize it: https://github.com/awawa-dev/HyperHDR/actions/runs/18822837600 |
Beta Was this translation helpful? Give feedback.
-
|
Seems it has been merged with the mainstream firmware so rpi_update should work now with this commit to switch kernel module to proper version: |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Dear HyperHDR,
I have connected a SK66812 LED via Justin's level shifter directly to IRQ18/ground on my raspberry pi 5. I was expecting to run WS281x directly, but then found the RP5 has some major changes.
has come by a few times here on the discussion already.
I then stumbled on this wiki which gave some hope, after building 'insmod' and 'dtoverlay' and running ./test I saw my LEDs twinkle! However, I coudn't get HyperHDR to recognize it. I suppose it's build not to expect this newer module (alterative name? rp1_ws281x_pwm)
After reading more, I decided to buy a 2040 raspberry from itsybitsy. But wanted to leave my expience here for any insights or pointers as I felt I was quite close! Thanks.
Beta Was this translation helpful? Give feedback.
All reactions