# Using WLED with QLC+ and LEDfx

**URL:** <https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313>\
**Category:** Integrations\
**Created:** [May 3, 2022, 4:42pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313 "2022-05-03T16:42:36Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![backache](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/backache/32/3387_2.png) [@backache](https://wled.discourse.group/u/backache)\
**Post date:** [July 28, 2022, 10:18am UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/21 "2022-07-28T10:18:05Z")

</div>

So have you found a way to have WLED quickly switch between data from the two sources or to have LEDFX act as a virtual light that QLC+ controls?

I can see in LEDFX’s API it has a specific function for QLC to use but I am not sure how you set it up in QLC

[https://ledfx.readthedocs.io/en/master/api.html?highlight=qlc#api-integrations](https://ledfx.readthedocs.io/en/master/api.html?highlight=qlc#api-integrations)

---

<div class="post-metadata">

**Author:** ![Kendaisy](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Kendaisy](https://wled.discourse.group/u/Kendaisy)\
**Post date:** [July 28, 2022, 2:52pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/22 "2022-07-28T14:52:31Z")

</div>

I prefer to modify the WLED source code because I want to control my LEDs simultaneously from QLC+ and LedFx while maintaining the 2 E1.31 (sACN) reception streams in WLED: DMX and RealTime. The changeover from one to the other is therefore instantaneous.

For this I created 2 additional DMX modes: QLC+ LEDfx RGB and QLC+ LEDfx RGBW.

 ![image](https://global.discourse-cdn.com/free1/uploads/wled/original/2X/8/879da57d34d534dc2f8f54725d2a17eac3e1b837.png)

These 2 modes differ in that the second manages RGBW LEDs (4 colors), the first only RGB (3 colors). They work on 2 different universe.

If one of these modes is selected, WLED responds to the RealTime LEDfx stream on its current universe (=1 in this example) and\or to DMX commands on a second universe = current universe + 2.

In LedFx configure Device like this

 ![image](https://global.discourse-cdn.com/free1/uploads/wled/original/2X/e/e6cdcc189a8e72bf97b861fd0e59754c1f9ec0c7.png)

In QLC+ Input\Output settings use a specific univers = current LEDfx univers + 2

 ![image](https://global.discourse-cdn.com/free1/uploads/wled/original/2X/4/41f1f3c54d3cf90646d6fa59f8f60dd7dab09c44.png)

To switch from DMX mode to LEDfx mode and vice versa, I added an new DMX channel: Select Mode

- value \<= WLED effects number: DMX mode (effects range : 0 - 117 in my WLED version)
- value \> WLED effects number: RealTime mode

 ![image](https://global.discourse-cdn.com/free1/uploads/wled/original/2X/7/77adaaafc6579f2ad8447823ecb9b30c7b85ffa6.png)

Now, with 2 PCs, I can simultaneously control my WLED devices from QLC+ and LEDfx also thanks to this architecture.

 ![image](https://global.discourse-cdn.com/free1/uploads/wled/original/2X/3/321cb91d4800da845a26a6b66b4fd8991f088631.png)

---

<div class="post-metadata">

**Author:** ![Jefta](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/jefta/32/6597_2.png) [@Jefta](https://wled.discourse.group/u/Jefta)\
**Post date:** [October 12, 2022, 3:43pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/23 "2022-10-12T15:43:19Z")

</div>

Hi,  
I am looking for a similar solution.  
Can you help me with that? I kinda want the same but running on 1 computer.

Im using MYDMX3.0 for controlling moving heads and other lights.

Thanks already

---

<div class="post-metadata">

**Author:** ![yestalgia](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/yestalgia/32/3755_2.png) [@yestalgia](https://wled.discourse.group/u/yestalgia)\
**Post date:** [October 27, 2022, 6:26pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/24 "2022-10-27T18:26:16Z")

</div>

Hey!

I’d suggest using QLC+ as a kind of “combiner” . It will make the integration much easier. You can feed MYDMX output into QLC+ and combine it.

Hope this helps.

---

<div class="post-metadata">

**Author:** ![mxklb](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/mxklb/32/4032_2.png) [@mxklb](https://wled.discourse.group/u/mxklb)\
**Post date:** [December 15, 2022, 2:46pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/25 "2022-12-15T14:46:09Z")

</div>

Why not make multiple configured universes in WLED UI, f.e. comma separated? Like: 1,3,5

Doing so, there is no need for extra static +2 universe modes QLC+. This would be a more general approach and every WLED DMX mode could benefit from it. Maybe this is some kind of DMX feature that others could potentially be interested as well? I think beeing able to control WLED by multiple external DMX software in parallel is cool, but … TBD

I don’t understand why multiple universe are needed to do so in general. IMO using a single start universe should not impact which external software is actually sending control data to it. Off cause external sofware like QLC or LEDfx must be silent and not interfer each others signals, but that crossfire case you have for mutiple universes as implemented in you QLC modes as well.

So maybe your change isn’t needed, or I don’t understand issues with parallel QLC & LEDfx usage?

Using different WLED DMX modes on different universe? Also a cool general feature request … TBD

---

<div class="post-metadata">

**Author:** ![mxklb](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/mxklb/32/4032_2.png) [@mxklb](https://wled.discourse.group/u/mxklb)\
**Post date:** [January 28, 2023, 1:53pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/26 "2023-01-28T13:53:05Z")

</div>

> [@pille](#):
>
> another solution could be E1.31 priority, which is currently not implemented on WLED (but QLC+ supports it)

I implemented some basic E1.31 priority handling, I think it may solve this issue, please test it:

> <https://github.com/Aircoookie/WLED/pull/3052>
>
> As of https://github.com/Aircoookie/WLED/issues/768 I implemented some kind of m…inimal E1.31 basic port priority handling some days ago.
> 
> Enables WLED devices to predictable handle E1.31 package priority for multiple E1.31 senders/controllers.
> 
> It's not implemented as the \[standard\](https://support.etcconnect.com/ETC/Networking/General/Difference\_between\_sACN\_per-address\_and\_per-port\_priority) says, but may be useful in situations where multiple senders can't be avoided:
> 
> When UI setting for E1.31 port priority is != 0 =\> Priority handling is active  
>         
> 1. Any packages with priority \< configured E1.31 port priority will be skipped.
> 2. Multiple senders: Highest priority packages win = will be used, others are skipped. 
> 3. E1.31 preview data & non-zero start code will be skipped.
>         
> Note: HTP for multiple senders with same priority is not implemented.
> 
> According to point 2: For package priority tracking a timeout of \`3s\` is predefined. When multiple senders send packages of different priorities, the highest priority gets tracked for this amount of time. After this timeout the next highest lower priority package sender will take over. This means take over of lower priority devices takes this timeout seconds - after higher priority device stopped sending packages. Nevertheless higher priority devices always take over in real time.
> 
> Note: Using multiple E1.31 senders is not recommended. Furthermore, multiple senders will reduce performance and it's advised to avoid it. Anyway if avoidance is not possible, this would handle crossfire more predictable.

Please use beta testing thread for direct feedback & discussion on this PR:

> [@E1.31 Port Priority - Beta testing](https://wled.discourse.group/t/e1-31-port-priority-beta-testing/7270):
>
> I implemented some basic E1.31 priority handling, looking for people to test it & write feedback: Please write any feedback to this PR here, in this discourse group chat, thank you …

---

<div class="post-metadata">

**Author:** ![RyFi](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/ryfi/32/4652_2.png) [@RyFi](https://wled.discourse.group/u/RyFi)\
**Post date:** [March 14, 2023, 9:55pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/27 "2023-03-14T21:55:39Z")

</div>

Hello Kendaisy! Would you be able to share your modification with me?  
I’m very interested in the ability to set different ArtNet modes (full RGB control, WLED effect mode) for different universes.

Alternately, if anyone knows of a way to directly export the effects from WLED into a format that I could import into a program like xlights or QLC+, I’d be interested in that, since the WLED effects are beautiful, and it would be cool to have the option to trigger them from a program while keeping the artnet mode as MultiRGB

---

<div class="post-metadata">

**Author:** ![RyFi](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/ryfi/32/4652_2.png) [@RyFi](https://wled.discourse.group/u/RyFi)\
**Post date:** [March 15, 2023, 12:54pm UTC](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313/28 "2023-03-15T12:54:07Z")

</div>

Also just wanted to note that I’d be very interested in both the port prioritization and an addition of Kendaisy’s code, since the former handles prioritization and the latter handles the actual WLED modes

[Previous page](https://wled.discourse.group/t/using-wled-with-qlc-and-ledfx/5313.md?page=1)
