You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just spent 30 minutes trying to figure out why my lights weren't animating from the sACN data I'm sending from LedFx. If I changed any parameters of the lights within the led-control panel, it would update the pixels with the latest "snapshot" from LedFx, but they wouldn't animate on their own.
I accidentally fixed it while playing around with the local patterns in led-control...it seems like if a "static" pattern is chosen (like "Static Color", "Static White", etc), the data from sACN is not processed. An animated pattern needs to be selected (it doesn't seem to matter which one...I used "Hue Scan 1D") in order for the sACN data to properly animate the lights.
It doesn't seem like the local pattern should matter at all if sACN is in use...it was not even remotely clear why they randomly stopped working and then randomly started working again until I stumbled upon this discovery.
The text was updated successfully, but these errors were encountered:
I just spent 30 minutes trying to figure out why my lights weren't animating from the sACN data I'm sending from LedFx. If I changed any parameters of the lights within the led-control panel, it would update the pixels with the latest "snapshot" from LedFx, but they wouldn't animate on their own.
I accidentally fixed it while playing around with the local patterns in led-control...it seems like if a "static" pattern is chosen (like "Static Color", "Static White", etc), the data from sACN is not processed. An animated pattern needs to be selected (it doesn't seem to matter which one...I used "Hue Scan 1D") in order for the sACN data to properly animate the lights.
It doesn't seem like the local pattern should matter at all if sACN is in use...it was not even remotely clear why they randomly stopped working and then randomly started working again until I stumbled upon this discovery.
The text was updated successfully, but these errors were encountered: