I've compiled WLED 0.11 (latest source code) with MAX_LEDS 2400 in my_config.h (also removed the # and space)
It still was having a limit of 1500 in the Config web-interface.
Then I re-compiled and also changed the const.h to #define MAX_LEDS 2400
Still when in the CONFIG web-interface the max is 1500 and when I press the up button it won't go higher.
When I manually type 2400 and click SAVE it says: "Value has to be lower or equal than 1500".
Is there a hard limit (accidentally) in the front-end?
Board: [ESP32 dev with multistrip mod]
Hardware: LilyGO TTGO T7 Mini32 V1.4
Version [0.11]
Format [self-compiled]
PS. I found (after some research) the issue might be in html_settings.h (do a search for 1500 there).
You will need to change the web page source here https://github.com/Aircoookie/WLED/blob/7684fb83d6b6c9dc0afd0131bdc5374333e03bad/wled00/data/settings_leds.htm#L97
Once you change the htm page, you need to run the tools/cdata.js script to update the header file that gets the htm pages embedded.
FYI, At 2400 pixels, you will be limited to about max 13.8 frames/second updates. Some effects may not look good. WLED tries to do 42 frames/sec.
Sorry to interrupt, can we change fps or is it fixed?
Little off topic, but there are two things you can change to have FPS change:
https://github.com/Aircoookie/WLED/blob/b5232886d992090bafd719cc74643afa505c1018/wled00/FX.h#L56
and
https://github.com/Aircoookie/WLED/blob/b5232886d992090bafd719cc74643afa505c1018/wled00/FX.h#L75
MIN_SHOW_DELAY defines the minimum time between calculation of segment updates and displaying them
WLED_FPS and computed FRAMETIME define the next time the segment should be updated
MIN_SHOW_DELAY = 15 means you will never get more than 67 fps (1000/15) - you can think of this as a short cut to avoid work if we updated fairly recently.
FRAMETIME or the returned effect delay is added to the current time to compute the time that segment should be updated.
Thank you and sorry again for jumping into someones issues.