# Colorwaves slow after update

**URL:** <https://wled.discourse.group/t/colorwaves-slow-after-update/14862>\
**Category:** Issues\
**Created:** [September 22, 2025, 1:40am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862 "2025-09-22T01:40:23Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 22, 2025, 1:40am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/1 "2025-09-22T01:40:23Z")

</div>

Hello! In my 24x128 matrix, the Colorwaves effect went from ~30 fps (a month ago) to ~9 fps.

My setup is two vertical 8x128 panels, separated by 8 pixels, so matrix size 24x128.

Was there a recent change that could have caused this?

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 22, 2025, 2:59am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/2 "2025-09-22T02:59:02Z")

</div>

That may be my bug. I’m investigating. Sometimes the .bin still doesn’t get updated and I got confused by that. I have to always remove .buildcache as per [Source code build issue](https://wled.discourse.group/t/source-code-build-issue/14770).

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 22, 2025, 3:20am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/3 "2025-09-22T03:20:14Z")

</div>

I found out something very strange. I have an effect, 2Dchillplasma, which is mostly a copy of 2Ddistortionwaves. My configuration boots automatically into 2Dchillplasma, so it is executed first.

If I comment out the following lines at the end of chillplasma (copied from distortionwaves):

```auto
  if(!SEGMENT.check1 && SEGMENT.palette)
    SEGMENT.blur(200, true);

```

Then I update the firmware and reboot, and then I select distortionwaves. The effect drops to 15 fps.

If I leave them uncommented, update, reboot, and select distortionwaves, the effect is at 36 fps.

This is very reproducible.

---

<div class="post-metadata">

**Author:** ![dedehai](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/dedehai/32/7265_2.png) [@dedehai](https://wled.discourse.group/u/dedehai)\
**Post date:** [September 22, 2025, 5:07am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/4 "2025-09-22T05:07:31Z")

</div>

need to provide a github link to your code, can’t work with guesses and and two lines of code.

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 22, 2025, 5:32am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/5 "2025-09-22T05:32:23Z")

</div>

I’m looking into reproducing it with just the wled code on github.

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 22, 2025, 6:15am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/6 "2025-09-22T06:15:53Z")

</div>

I wasn’t able to reproduce it at head of main in github.

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 26, 2025, 2:00am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/7 "2025-09-26T02:00:08Z")

</div>

A commit on the last few days must have fixed it:

I rebased my changes on top of HEAD as of today, and now I can comment out the SEGMENT.blur() lines and colorwaves is not slow anymore.

---

<div class="post-metadata">

**Author:** ![dedehai](https://yyz2.discourse-cdn.com/free1/user_avatar/wled.discourse.group/dedehai/32/7265_2.png) [@dedehai](https://wled.discourse.group/u/dedehai)\
**Post date:** [September 26, 2025, 8:47am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/8 "2025-09-26T08:47:25Z")

</div>

still cant comment without knowing what you did.

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 26, 2025, 9:14am UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/9 "2025-09-26T09:14:21Z")

</div>

Thank you for reading. Sorry, I can’t publish any code due to work contract (even though wled is not work-related).

I couldn’t reproduce it with pure wled without my changes, so all is good!

---

<div class="post-metadata">

**Author:** ![Jinx](https://avatars.discourse-cdn.com/v4/letter/j/c6cbf5/32.png) [@Jinx](https://wled.discourse.group/u/Jinx)\
**Post date:** [September 26, 2025, 8:53pm UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/10 "2025-09-26T20:53:02Z")

</div>

> [@epoyart](#):
>
> I can’t publish any code due to work contract

So you are taking free open source code, making modifications and then making it closed source, while asking for help from the Dev’s that are so kind as to provide the open source 🤨 mmmk..

---

<div class="post-metadata">

**Author:** ![epoyart](https://avatars.discourse-cdn.com/v4/letter/e/a587f6/32.png) [@epoyart](https://wled.discourse.group/u/epoyart)\
**Post date:** [September 26, 2025, 10:01pm UTC](https://wled.discourse.group/t/colorwaves-slow-after-update/14862/11 "2025-09-26T22:01:00Z")

</div>

I’m not making open-source project closed-source except for my own use. It’s an art project. I will not (and am not allowed to) distribute it in any way, open or closed. I wish I could make it open source.

I thought I found a problem and I wanted to help investigate it. I asked if anyone knew of a recent change that could have caused it.

I’m very thankful to the developers, and I wish people that try to help receive less of these attacks. If I’m not welcome to post here because I can’t make my code open source, I’ll stop.
