Posts by Issuing3795

Ok, ive found a solution. You can change the gamma settings to control how the led brightness scales https://docs.hyperion-project.…Advanced.html#gamma-curve. Ive set it to 2.5, so the leds dont even turn on on dark scenes

Only thing I found is the "backlight threshold" setting in the image processing tab. But at least with wled, thats even worse because it turns the lights bright white on dark scenes. Not sure if thats for all output hardware tho

As someone with a usb capture device, who just stumbled upon this thread, id still like to know where those settings are. Searching for some of the key words in that screenshot brought me to this page of the documentation https://docs.hyperion-project.…hue.html#signal-detection . So does this feature only exist for philips hue leds? Its the only page that comes up when searching for "threshold" in the docs

Update:

turns out using the live video in the LED visualization tab eats up your ram like crazy. Im not 100% sure, but i think using the live video of the Hyperion integration for Home Assistant does the same.

So the good news is that i probably fixed that problem.

The bad news is that I still have undervoltage. Ive also read that the 4.something volts I read about are outdated. My Pi requires 5.1V source. So I guess Ill have to get a separate power supply for Pi and LEDs?

Hello dear forum goers,

I am running Hyperion Nightly on a Raspberry Pi 3B+ with 100 WS2812B LEDs and a MiraBox Capture Card. Unfortunately Im having two issues and I dont know if they are related, so Ill post them both in here just in case.

So, my Hyperion instance keeps crashing every so often. Looking at dmesg reveals two issues:

1. Hyperion gets killed for taking up too much memory Out of memory: Killed process 758 (hyperiond) total-vm:1227096kB, anon-rss:872592kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:1082kB oom_score_adj:0
2. There are **many** warnings about the Pi being undervolted hwmon hwmon1: Undervoltage detected!

The oom error only occurs once every few hours or so, so ive never looked at the memory usage in that exact moment. But when im looking at htop, the Pi usually sits at about 90 MB of around 900. Is this a software bug or could this be caused by the Pi dropping too far in voltage to function properly?

Regarding the undervoltage warning Im using a 5V 10A power supply to power both my strip and Pi. Despite it's rating, when measuring with my multimeter, the psu actually puts out 5.4V and 13A. Im not well versed in this kinda stuff, but I assume that's what it **could** supply and not what its actually pushing through my LEDs? But regardless, it shouldnt drop below the 4.75V required for that undervoltage warning.

Does anyone know what could be wrong with my setup? Ill gladly provide more info if theres something important that i didnt mention.

Oops, didnt mean to delete my previous thank you post
So thanks for the info, the nightly build works great

Hello people,

Here is the background info:

I am running the latest version of Hyperion (2.0.15) on my revision a020d4 Pi 3B+ with a WS2812B strip and I get the error Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: Hardware revision is not supported'

As far as I understand Hyperion is using the rpi_ws281x library for ws281x strips. This library supports revision a020d4 Pi 3B+s since this commit in april. Ive compiled the rpi_ws281x master myself and it seems to work fine using the test program that thing spits out upon compilation.

Now the actual question:

Can I just overwrite the version Hyperion is using with the version I compiled myself? If yes, how would I go about doing that?

Regards,
someone who doesnt really know how libs work