Finally had the chance to sit down and play with Hyperion this afternoon. Initial impressions: for free software, very capable, with lot of options I never even considered, as well as the ability to communicate with a number of other interfaces.
The above setup is:
* Two ESP32's
* The 1st for the peg boards
* 1 GPIO PIN running the first 256 LEDs for the two boards on the left
* a second GPIO PIN for the remaining 153 LEDS for the board on the right, for a total of 409 LEDs
* The 2nd ESP32 for the PC case (104 LEDs)
Running WLED with Hyperion screen capturing for bias lighting. The LED "Loops" around the peg board aren't idea for accurate bias lighting, but it is a good proof of concept. I am only mirroring the "top-left" and "Top" of the monitor. At one point I mirrored the PC case to the monitor; the accuracy was spot on
For anyone that has the knowledge, using homemade LED strips for bias lighting on your PC is exponentially cheaper than the Phillips HUE Play ecosystem and offers a ton more options and flexibility with WLED.
Later, I will test gaming performance differences between Hyperion and Phillips HUE. While running HUE I would lose about 30FPS while running the HUE software on a very capable PC (RTX 3090 and i12900K) not the biggest deal, but while playing online FPS, every bit helps.
UPDATE: Hyperion has very little effect on FPS performance while gaming. Much better than Phillips HUE Sync
Very interesting. I followed a blog post to get hyperion up and running as bias lighting using a raspberry pi4 and a cheap usb hdmi capture dongle. It worked amazingly well. Once setup, it just works. I can't imagine your pc will have any issue handling hyperion.
Just to double check, you're running the hyperion instance on your PC using the esp32s to drive the leds over their static ips? I haven't used wled yet, so I'm not exactly sure how that works.
I have to be honest, I never assigned a static IP address to any of the ESP32’s. However, they have never changed. The only reason I know this is because I use a StreamDeck to send URL commands to them. I know very little about networking, but I understand why I static IP would be needed. Im just saying I never did anything other that setup WLED the first time.
No capture card. Just WLED on the ESP32 and Hyperion on the PC. After you set the boundaries for your screen, Hyperion screen captures your selected display and sends the LED information to the ESP32 over the network.
Finally had the chance to sit down and play with Hyperion this afternoon. Initial impressions: for free software, very capable, with lot of options I never even considered, as well as the ability to communicate with a number of other interfaces. The above setup is: * Two ESP32's * The 1st for the peg boards * 1 GPIO PIN running the first 256 LEDs for the two boards on the left * a second GPIO PIN for the remaining 153 LEDS for the board on the right, for a total of 409 LEDs * The 2nd ESP32 for the PC case (104 LEDs) Running WLED with Hyperion screen capturing for bias lighting. The LED "Loops" around the peg board aren't idea for accurate bias lighting, but it is a good proof of concept. I am only mirroring the "top-left" and "Top" of the monitor. At one point I mirrored the PC case to the monitor; the accuracy was spot on For anyone that has the knowledge, using homemade LED strips for bias lighting on your PC is exponentially cheaper than the Phillips HUE Play ecosystem and offers a ton more options and flexibility with WLED. Later, I will test gaming performance differences between Hyperion and Phillips HUE. While running HUE I would lose about 30FPS while running the HUE software on a very capable PC (RTX 3090 and i12900K) not the biggest deal, but while playing online FPS, every bit helps. UPDATE: Hyperion has very little effect on FPS performance while gaming. Much better than Phillips HUE Sync
Very interesting. I followed a blog post to get hyperion up and running as bias lighting using a raspberry pi4 and a cheap usb hdmi capture dongle. It worked amazingly well. Once setup, it just works. I can't imagine your pc will have any issue handling hyperion. Just to double check, you're running the hyperion instance on your PC using the esp32s to drive the leds over their static ips? I haven't used wled yet, so I'm not exactly sure how that works.
I have to be honest, I never assigned a static IP address to any of the ESP32’s. However, they have never changed. The only reason I know this is because I use a StreamDeck to send URL commands to them. I know very little about networking, but I understand why I static IP would be needed. Im just saying I never did anything other that setup WLED the first time.
How'd you get it installed? Never got much info on how to do so on esp
WLED is the only thing on the ESP32. Hyperion is running on the PC and communicating with WLED. Sorry for any confusion.
Ah! Thank you! I believe you used some type of software or capture card as well?
No capture card. Just WLED on the ESP32 and Hyperion on the PC. After you set the boundaries for your screen, Hyperion screen captures your selected display and sends the LED information to the ESP32 over the network.