Replies: 5 comments 8 replies
-
Here is my current setup: PXL_20221224_073007713.TS.mp4 |
Beta Was this translation helpful? Give feedback.
-
additional suggestions: instead of wood, using aluminum angle is stronger and acts like a heat sink for the LEDs. if you use the alum angle that is 1"x2" it creates an angle off the back of the TV less than 45 degrees which is IMHO a better light projection on the wall. something that I really liked about Prismatik were the color adjustments. adjusting the LED strip based on Kelvin scale color temp is much more intuitive than adjusting color 0-255 scale individually. the ability to change modes from color backlight to dark scenes with a single click was great too. It took me a while to dial this in with HyperHDR and because i had to mess with so many parameters to do it, some color reproduction has suffered. |
Beta Was this translation helpful? Give feedback.
-
Good afternoon. Could you take a picture of the back of your TV. I'm interested to see what the aluminum profile looks like. There is matte plastic and transparent. But I still don’t understand how to attach it on TV, it still has its own weight along with the tape. |
Beta Was this translation helpful? Give feedback.
-
Hi
That's why I always recommend a dedicated USB power supply for the Raspberry Pi. I'm not surprised that a voltage spike with such a large configuration can cause voltage instability during sudden scene/LED brightness changes. You also bypass the protection of the Rpi by powering it through the pinout instead of using the USB port. What is even more dangerous is that the power supply is using an unstable LED power supply, whose characteristics change under a sudden load because it also powers the LEDs.
99% of such users setups don't use a mandatory level shifter. Neopixel protocol requires strict timings, emulation (it is not native SPI protocol like for APA102, it needs a special data buffer to be prepared first to simulate it), Rpi solution usually starts to malfunction around ~250LEDs (occasional blinking) sometimes it starts around 200LEDs especially if RGBW LED strip is used. With larger setups it simply doesn't work (usually last segment doesn't work at all or is constantly blinking).
Agree, I use it mainly for cost-effectiveness, and also wood is easier to work with. I still have no problems with heating (96 diodes / meter, diodes and its surroundings on the strip have the ambient temperature to the touch). My guess is that the temperature problem may arise with a very large setup, but it's not the LEDs themselves under normal conditions/use, only with the internal copper LED tracks if only one power injection is used, causing high current flow using only one path. However, it is still a problem of bad design, which such cooling would only mask. A 45 angle was also used because my frame is very close to the wall, about 3 cm. But for a greater distance, the angle should be smaller (the angle of incidence/reflection, but also the angle/intensity distribution of light scattering on the material/wall towards the observer)
I could not find a HD107s specification that could confirm that. Always the high logic level voltage specification is missing. If it works for you then OK, but for 5V LEDs strip I stick to the 3.3V to 5V level shifter recommendation. For example for Neopixel LED strip like WS2812b high logic level is defined usually as 0.7 * Vdd. I know there are WS2812b versions that can handle logic voltage as low as ~2.8V, only problem is to recognize such versions. Since we are not so sure, we also have to assume the use of a level shifter.
The high density ws2812b can also produce very bright white. But so what if the white produced from the RGB components has a much worse purity than the white produced by RGBW ... in addition, it changes depending on the white scale and is impossible to calibrate.
This is HD108 protocol? https://www.rose-lighting.com/wp-content/uploads/sites/53/2019/11/HD108-led.pdf It does not require much work to be able to control such a LED strip. I can implement it even blindly in HyperHDR without sample of this LED, but then you would have to test it yourself. But we will not use it to its full potential for now (LED is 16bits, all inputs/grabbers work at 8bits).
I used RGB ws2801 for years, ws2812b temporarily and still have ws2813 as one of my test setup. Yes, RGBW is much better and I can't imagine going back to RGB LEDs, even if they offered 16 bits of resolution. sk6812 is not perfect due to the slow neopixel data protocol, but only with the HD108 RGBW version I would consider an upgrade ... they have been announcing them for years, but nothing has come of it, and as you noticed, there is a problem even with buying such a 16-bit RGB version, so probably they focus on solutions for companies, not consumers.
Solution for color temperature is only available for RGBW in HyperHDR for some LED drivers. This is done outside, not in HyperHDR, and is used to correct the characteristics of a given type of LED: they already have a factory-defined temperature, e.g. in the case of "neutral" sk6812 RGBW, we must cut off a large share of red and green so that the white color is actually white and not yellowish . I do not anticipate similar solutions for RGB for the reasons I wrote about: we are not able to provide software workaround for similar quality as with RGBW diodes. |
Beta Was this translation helpful? Give feedback.
-
i found where i read about these strips being 3.3v tolerant. it is on the Newstar site. the rose site (including the data sheet) is a mess of copy and pasted information. this data sheet may be better to use: i was also reading that CMOS chips, which are what these strips use, are traditionally 3.3v logic. |
Beta Was this translation helpful? Give feedback.
-
For many years I used @dmadison set-up with Prismatik fork. This obviously had its limitations and after switching to Windows 11 and HDR I decided to use your system. I had many issues at first but have worked through [most] of them. I appreciate the immense amount of time you have devoted to this and share openly with us; therefore, my suggestions are only to be of help.
Current set-up:
Rpi 2b v1.1, SD card version of HyperHDR
HD107s 60/m strip, 284 total LED
Flatbuffers protocol @30fps, switch between Rpi and Nvidia card
I was running 144/m strip for a total of 510 LED with no lag but my 1000w PSU was not enough and on full white scenes the Rpi would crash and reboot (I am powering the Rpi off the strip via GPIO pins back through the same cable that I am sending SPI over and while not recommended, with 60/m strip i have had no issues).
I first used a grabber via zone2 HDMI out of my AVR but the lag was high (lacking usb3 on the Pi) and the AVR did not like configuration and would consistently kick out HDR in Windows. I did not want to use a splitter because even a good one will process the signal. My goal is passthrough of 2160p HDR10 Dolby Atmos 7.1.
I then used HyperHDR as the master in Windows to an Arduino Nano Every using SPI and adalight. Then I tried HyperHDR forwarder to Rpi to Nano Every. Both worked but had frequent connection and communication issues with Windows10 and 11 made that all worse. I also had too much cabling between my HTPC and TV. I will say, the Nano Every is very capable if the user wants to still use Arduino.
Then I found @sabaatworld HyperionScreenCap. This was it. I could use the same Ethernet cable already used to communicate with HyperHDR on Rpi and using shielded cat8 cable I had strong data transfer over longer distances. I have no latency issues, the colors that are sent to the Rpi are exactly what the Windows screen is displaying so no having to mess with calibrations, and the connection is automatic when turning on my HTPC.
So my question is, why are you using a ESP32 connected to the Rpi instead of communicating with the LED strip directly from the Rpi GPIO? Can the Rpi not do parallel pwm output as well?
Some issues that the HD107s strip has eliminated for me:
I have never used an RGB/W strip. is the white color reproduction that much better than the HD107 to justify all the other devices, wiring, programming, etc that must be done for the R/W strip?
My next goal is to use the 16-bit color HD108 strip but I am not skilled enough like you are to make it work. So I have an offer:
I had to have a big order manufactured in order to get these strips. I have been re-selling them but if I gave you HD108 60/m strips to keep for free... would you be able to make them work with your HyperHDR for Rpi?
Beta Was this translation helpful? Give feedback.
All reactions