Posts by Lord-Grey

It is exactly as the AI advised.
Best would be you install the latest version on the original platform. Then start hyperion and you can export.

Alternatively, you can install 2.2.1 on the new system, start and stop it.
Then you can replace the database file with the one from the old system.

As a courtesy, find attached your two exported 2.0.16 configs in a single 2.2.1config file.
Please remove the ".txt" suffix before importing.

You might need to change the instance names after import....

PS: I added a Breaking-Change note with release 2.1.1 to make it more explicit.

This is the Hyperion forum. If you are using HyperHDR please raise the question there.

Hi HansDampf & obelix05

Thanks for sharing your finding.

Looks I did not work diligently on ToDos I captured for myself after releasing 2.2.0

Can you please try again?

HansDampf Could you run the script in verbose mode and share the output, please?

 curl -sSL https://releases.hyperion-project.org/install | bash -s -- --verbose

BastianBee You are welcome.
While digging for through the code, I also learned more about the question at hand .

… and it triggered the question, if a default value of 100% makes sense…

BastianBee Can you try putting Brightness Compensation = 0?

Quote from BastianBee

To generate mainly only the white value, I am currently using the “Auto Accurate” or “Subtract Minimum – White LED” algorithm

With those two algorithms you should get a white = 255 for full white RGB (255,255,255) and not 85.

On SUBTRACT_MINIMUM you should get RGBW = 0,0,0,255

Is this not the case?

Edit: In case the color correction ends with RGB < 255, then RGB will be greater than zero… White get the smallest value of RGB and R,G and B will get white subtracted.

Quote

This avoids the situation where channels 511 and 512 are incomplete when using RGB LEDs (3 channels per pixel).

The current artnet code already considers this. One LED which is mapped to a defined fixture length, must be always within the same universe. If not, the next universe will start with it.

Quote

Do you plan to include the RGBW functionality in a future official release, so that users can enable or disable it in the settings?

Everything currently in the nightly release will be made available via an official release at one point in time; no ETA defined yet.

Quote from BastianBee

I downloaded the PR build again and tested it.
Art-Net is now working perfectly, and sACN is also working correctly.

It is great to hear that it is working now.

Quote from BastianBee

I also checked the image processing settings, but I could not find anything that would explain this behavior.

Just looking at the code, white values depend on the algorithm chosen.

RGBW will be calculated when updating the LEDs. Image processing was done already done before and provide RGB values into the calculation.

Just check out the way RGBW is calculated:

hyperion.ng/libsrc/utils/RgbToRgbw.cpp at master · hyperion-project/hyperion.ng

The successor to Hyperion aka Hyperion Next Generation - hyperion-project/hyperion.ng

github.com

Or share the way you configured and we have a joint look.

Quote from BastianBee

I also tried to install the official 2.2.0 version again, because I wanted to check something there.
However, Hyperion does not start anymore after the installation.

Do you maybe have an idea what could cause this?

It is likely that v2.0.0 complains that the database is already at a newer version.

You should see this reported as an error in the output or system log.

When testing PR normally a separate database is installed to avoid this. Not sure how you testen getting into the situation…

To fix this:

when a new version updates the configuration database, it stores an export in an backup folder next to the existing database. You should find a file with 2.2.0 in it.

If hyperion is stopped you can import the file via the commandline (filename is illustrative).

# Import a HyperionBackup JSON file

hyperiond -i --importConfig ./HyperionBackup_2025-05-28-151224-615_v2.2.0.json

Alternatively, wait for the next nightly build after I merged the PR and install that one.

BastianBee You might have missed the above given that we had some issues with Spam.

@BastianBee I did some corrections and using an ArtNet monitoring program it looked ok for me...
Would you mind testing the PR again?

Just download the PR build again as before.

Quote from BastianBee

Would it be possible to provide the changes as a ready-to-use version, for example as a .exe, so that I can use them directly? This would help me a lot to test the improvements without having to compile the code myself.

I am sorry, I missed to add the link how to test a PR which includes already a ready made version.
Here it is: https://docs.hyperion-project.org/user/advanced/Testing.html#linux

It will download the PR next to your current installation and you can remove it after successful testing...

BastianBee Can you test https://github.com/hyperion-project/hyperion.ng/pull/1983?
I fixed the channel issue and added RGBW support.

When using WLED with two segment and would would like to run this as a logical one, configure WLED without segments in Hyperion.

Then Hyperion sees the total sum of LED.

Via the layout you can define the positions for the LEDs. You might need to configure Strip 1 and Strip two independently and then merge the generated JSON output manually.

That depends on your layout.

BastianBee Thank you for sharing the detailed outline.

1. and 2. are related to a bug.

PR1983 will likely already address the issue.

3. If one universe is full, the next universe in sequence should be used…

This might currently not work correctly because of 1. and 2.

4. Please create a new feature request at

hyperion-project/hyperion.ng

The successor to Hyperion aka Hyperion Next Generation - hyperion-project/hyperion.ng

github.com

5. Currently, binding an UDP broadcast to a dedicated network adapter is not supported.

The current behaviour is as following:

Qt passes the destination address to the OS. The OS then:

1. Looks up the best route to destination IP
2. Selects the corresponding network interface (e.g., eth0, wlan0, enp3s0, etc.)
3. Sends the packet via that interface

So the chosen interface depends on:

• Destination IP
• Routing table
• Interface metrics
• Active connections

Edit: See https://docs.hyperion-project.org/user/advanced/Testing.html#linux on how to test PRs. so you can check, if the fix works.

Quote from Bogeyof

Gibt es keinen Weg, von 2.0.16 auf 2.2.0 upzudaten? Kann man mit "apt-get install hyperion" auf der alten SD-Karte updaten oder ist dann auch alles zerschossen?

Du kannst Dein aktuelles System aktualisieren

sudo apt update

sudo apt upgrade

Die Datenbank wird dann beim nächsten Start migriert, plus es wird ein Backup Deiner 2.0.16 Datenbank gemacht.

Es schadet sicherlich aber auch nicht, wenn Du Deine 2.0.16 Konfiguration vorher noch exportierst. Zur Sicherheit, falls Du auf die Version zurück willst.

Alternative, kannst Du auch das komplette Datenbankfile vom alten System auf das neue kopieren. Hyperion vorher stoppen.

Beim Neustart wird die Datenbank dann wieder migriert. Wo das Datenbankfile liegst sieht Du unter System/About

The latest version of Hyperion is now available! This release is a major milestone, featuring a massive architectural refactor to address memory consumption and significantly improve resource management.

🚀 Key Highlights

• Performance: Fixed significant memory leaks and optimized image handling to reduce CPU overhead.
• Windows DDA Grabber: Completely rewritten for improved stability and fixed orientation/sleep issues.
• Raspberry Pi: Introduced a new DRM/KMS screen grabber with plane-based capture.
• RGBW Support: Now natively supported for WLED, e1.31, UDP-DDP, and UDP-RAW devices.
• Security: Updated Hue Bridge integration to follow Philips’ latest security guidance (HTTPS/Certificates).

📥 How to Get It

Official Repositories: We provide executables for Debian, Ubuntu, and Fedora. You can also find the latest release files on our GitHub Releases page.

Installation & Update Guides:

• General Setup: See our Getting Started Overview for repository and manual installation instructions.
• HyperBian (Raspberry Pi): For a plug-and-play experience, we recommend HyperBian, our pre-configured image based on Raspberry Pi OS Lite. Follow the HyperBian guide here.

📝 Full Changelog

For a detailed list of all Added, Changed, Fixed, and Removed items —please see the full change log notes

Thank you to all the contributors and community members who helped test and refine this release!

soccer0204 Die Loglines mit der Pixelinformation beziehen ich auch die Flächen des Input Images, welche auf die jeweiligen LEDs gemappt werden sollen.

Bei den mir bekannten Hue LED Steifen können nicht alle LEDs einzeln angesprochen werden.
Philips teilt diese in Bereiche und rechten den Verlauf dazwischen.

Bei Deinem Strip erkennt Hyperioin, dass es drei Bereiche gibt.
Darum werden drei LEDs abgeleitet für die man Informationen and die Bridge schicken kann.

Ab besten Du definierst den Strip per Entertainmentbereich in der Hue App.
Mit dem Wizard bekommst die die Strip-Gruppe angezeigt und wählst Entertainment Bereich.
Über diese Einstellung erzeugt Hyperion das dazugehörige Layout selbständig, so wie es in der Hue App definiert ist.

PS: Ich habe Deinen Spoiler gelöscht, dass zu viele private Info enthalten war....

TPmodding Könntest du hier satdx62 helfen?

Quote

sickrandy The GRB option is not present in the dropdown.

Can you show me a screenshot of the Color Order of the LED-Device.
You need to switch to Expert setting.

I do see all six combinations....

Quote

Color test results (Color Calibration → Test Colors)

You should not use color calibration, but the RGB Byte Order wizard to get the Byte Order configured easily.