Replies: 3 comments
-
Beta Was this translation helpful? Give feedback.
-
|
@krakenled not sure what you actually want to achieve, could you create some screenshots and add annotations to show what you want to add? Unfortunately, the AI suggestion is hot garbage, its mixing design of WLED-SR, WLED upstream and WLED-MM in a chaotic way. That suggestion will lead nowhere. Just for clarity, there are different ways to "sync" several WLED-MM instances, and you can even combine them:
In case of DDP output, you can already limit the receiving device to receive LEDs on the "main segment" only (Sync settings). If you want finer control, I'd suggest you make a feature proposal in upstream WLED. |
Beta Was this translation helpful? Give feedback.
-
|
I have a master athom esp32wroom32e compiled with my own wled firmware to
8mb as athom only supply its compiled to 4mb. I run 0 leds off the master
and have 8 esp32 pico d2 have running 96 leds each. I run ddp with segments
for each controller. I want to run ddp for my 8 segments for non sound
active so i can use the segment controls to change up the direction and
mirror on each segment and on the AR effects i want them all the run local
sound processing more like udp synch would do do withoit the segment
control. Im looking how to run the AR in udp synch while having ddp set
…On Tue, 31 Mar 2026, 11:27 pm Frank Möhle, ***@***.***> wrote:
@krakenled <https://github.com/krakenled> not sure what you actually want
to achieve, could you create some screenshots and add some annotations to
show what you want to add?
Unfortunately, the AI suggestion is hot garbage, its mixing design of
WLED-SR, WLED upstream and WLED-MM in a chaotic way. That suggestion will
lead nowhere.
Just for clarity, there are different ways to "sync" several instances
- AR udp sound sync - shares preprocessed audio data with several WLED
instances over multicast (sometimes not working, depends on WiFi router)
- DDP output: sends LEDs output over network to another WLED.
- WLED sync: this just synchronizes the effect "name" (=selected
effect) and effect settings, it does not synchronize any additional data
like audio.
In case of DDP output, you can already limit the receiving device to
receive LEDs on the "main segment" (Sync settings). If you want finer
control, I'd suggest you make a feature proposal in upstream WLED.
—
Reply to this email directly, view it on GitHub
<#352?email_source=notifications&email_token=CAVNGVO3OSMML3GZWCOBAQD4TO2SVA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRTHE2DKMBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16394503>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CAVNGVPUYZULKBWB2MKNQ7T4TO2SVAVCNFSM6AAAAACXHSOU3OVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMZZGQ2TAMY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all
I have a problem with ddp vs synch and its pros and cons. My latest build i run 8 controllers each running 96 leds in 1d of 1 master running 0 led. I run DDP and segment each controller so i get 8 led bars i can program doing their own thing like 2 in reverse, two mirror, 2 mirror reverse. this works great on the non AR effects. When i used the udp sych on non AR effects it was pretty boring have multiple bars doing the same effect. When it came to AR effect the individual controllers did their own thing and would all react different to each other but running multiple AR in DDP its just slave all doing to same old thing. My idea is to override the ddp with a override checkbox on the segement box or on the preset box. Im not a programmer but asked my friend, google ai and they suggested it be done this way.
To integrate these custom features into the WLED MoonModules (or standard WLED) source code, you will need to modify specific files within the /wled00 and /wled00/data directories.
To add a new UI element like a checkbox to the segment control area, you must modify the frontend files and then rebuild the compressed header files.
WLED
WLED
+1
Primary File: wled00/data/index.htm
Locate the segment template or the segment container in the HTML and add your element.
Javascript Logic: wled00/data/index.js
Update the getV() or segment rendering functions to handle the state of your new checkbox and include it in JSON API calls.
Required Action: After modifying files in /data, you must run npm install and npm run build in the repository root to regenerate html_ui.h.
GitHub
GitHub
+4
Adding a dedicated settings page involves modifying the core server and configuration navigation.
WLED MoonModules
WLED MoonModules
HTML Template: Create a new file (e.g., wled00/data/settings_um.htm) or modify wled00/data/settings.htm to include a link to your usermod settings.
Web Server: wled00/wled_server.cpp
Register the new URL path so the ESP knows which file to serve when the "Usermod" config button is clicked.
JSON Handling: wled00/set.cpp and wled00/xml.cpp
Update these to parse incoming settings from your new page and save them to the device's flash memory.
Usermod Code: wled00/usermod.h (or your specific usermod file)
Use the addToConfig() and readFromConfig() methods within your usermod class to define what fields appear in the "Usermods" section of the standard config.
GitHub
GitHub
+4
To modify how Distributed Display Protocol (DDP) or node-to-node communication is handled, you need to look at the networking and sync modules.
WLED
WLED
Node Management: wled00/nodes.cpp
This file handles the discovery and listing of other WLED nodes. Override logic here if you want to change how nodes are displayed or prioritized.
DDP Reception/Handling: wled00/udp.cpp
This is where incoming DDP packets are processed. If you want to "override" DDP (e.g., ignore certain packets or change their priority), modify the handleNotifications() or specific DDP parsing functions here.
Configuration UI: wled00/data/settings_nodes.htm (or settings_sync.htm in newer versions)
Modify this if you want to add manual DDP override toggles to the "Nodes" or "Sync" settings page.
GitHub
GitHub
+2
Would you like the specific C++ code snippets for the addToConfig function or the npm build commands for the UI?
undefined
undefined
undefined
13 sites
customization for usermod configuration, short of a ... - GitHub
6 Dec 2024 — I can see two ways to implement this but there may be other good options. One is a new function (addA, for attributes?) that large...
GitHub
Custom Features - WLED Project
In order to conserve space, the Web UI interface is represented as a series of wled00/html_*. h files which contain C/C++ strings ...
WLED
Adding a new Settings Page - WLED MoonModules Project
WLED MoonModules
Show all
there are no pages with nodes in the title
In WLED MoonModules, the "Node" functionality is actually integrated into the Sync Settings page. There is no standalone file named "nodes.htm".
To achieve your modifications, you will need to work with the following files:
File: wled00/data/index.htm
This is the main UI. You need to add the HTML for your checkbox inside the segment template section.
File: wled00/data/index.js
Modify the JavaScript to handle the checkbox state and include it in the JSON object sent to the ESP.
Required Task: After editing these, you must run npm run build in the root folder to update the compressed html_ui.h header file.
WLED MoonModules
WLED MoonModules
+1
File: wled00/data/settings.htm
Add a new button or link here to navigate to your custom usermod page.
File: wled00/wled_server.cpp
You must register the route for your new page (e.g., server.on("/settings/myusermod", ...)).
Alternative (Standard Usermod UI): If you just want fields to appear in the existing "Usermods" config section, use the addToConfig() and readFromConfig() methods inside your usermod's .h file (e.g., wled00/usermods_list.cpp).
WLED-MM
WLED-MM
+1
Since there is no "node" page, these settings are located in the Sync section:
UI File: wled00/data/settings_sync.htm
This page contains the "Network Nodes" and "Instance List" settings. This is where you would add UI toggles to override DDP behavior.
Core Logic File: wled00/udp.cpp
This file handles the actual DDP packet processing. If you want to change how WLED reacts to DDP (e.g., ignoring specific nodes or changing priority), you must modify the handleNotifications() function or the DDP-specific parsing logic here.
Node Discovery: wled00/nodes.cpp
This file manages the list of other WLED instances on the network. Modify this if you want to change how nodes are discovered or listed in the UI.
WLED MoonModules
WLED MoonModules
+1
Would you like the exact line numbers for the DDP handling in udp.cpp?
I couldto someone more try and follow google ai's instuctions that are usually wrong or be a sponsor to saysomeone more capable.
if anyone else is willing to sponsor please let me know.
Beta Was this translation helpful? Give feedback.
All reactions