Bias / ambient lighting with DMX fixtures

Hyperion NG might offer a fully open source ambient light with DMX fixtures in my opinion. For people interested I want to roughly point out how this COULD work:

1. Setup Hyperion NG and use the E1.31 (sACN) as device. (DMX over network - we'll stay on the same machine - no network hardware necessary, but possible)

2. Use OLA (Open Lighting Architecture) to receive the network traffic and feed it into a universe where a USB to DMX dongle (hardware) is patched as output.

I don't know if this works, but I'll try to find out.

Saw that Hyperion NG can directly write to USB devices.
OLA still helps in case you have multiple sources. (Using QLC+ in parallel to Hyperion NG for example)

I`ve tried to set up my DMX fixtures with Hyperion ng and realised that DMX needs more configurable channel mapping then the current configuration in the web interface allows.

How DMX fixtures can vary in DMX channel assignment was already discussed at https://hyperion-project.org/t…-lights-be-supported.392/ which was about DMX USB integration. This thread should be hardware independent. I think that DMX over USB hardware or E1.31 bring up the same addressing or channel mapping requirements.

Since the mentioned discussion above there is one configurable DMX fixture I can see in the code. The discussion also brought up the ideas for a fixture editor like in QLC+.
I would like to ask if it would be possible to avoid a complete fixture editor by

- just distinguishing fixtures by overall channel count (three for RGB or maybe ten with dimmer and other intelligent channels)
- using the fixture channel count to calculate channel gaps between LED (in this case fixtures)
- allowing the user to setup a mapping of the defined channels per fixture if the channel count is greater than three to RGB and dimmer channels
This could be done in the web interface by drag really dragging say connecting lines of Hyperion channels and the fixture channels. (Example for that : Claudia application : https://browse.startpage.com/d…53d9c6cdb461286&t=default)

This does not include the possibility that a user might have different fixture types within one setup. This might also be taken into account later.

I would like to hear the opinion of the dev team to my suggestions.

@penfold42 ? Can you assess my suggestion?

Found another pull request where DMX channel mapping took place.

https://github.com/hyperion-project/hyperion.ng/pull/256

The solution here was to add a fixture type into the serial DMX file.
Since channel mapping applies at least also to E1.31 and Artnet it might be a good idea to implemented it protocol independent.

Source code of DMX fixture config : https://github.com/hyperion-pr…rial/LedDeviceDMX.cpp#L27

Just a suggestion.

So my suggestions for the UI are accepted?

Maybe I can implement this. I'll take a look.
Can you tell me which web interface files I have to look at? I'm familiar with C++, but I worry about the web GUI part.

Okay. Ich werde mir das mal ansehen.