I doubt it has to do with the SLEEP, but with the code itself. So, I grab the smallest picture possible which is 96x54px (to keep everything small and fast). I than subtract from each side (top, bottom, left, right) 9px (since some movies have black-borders which are within this range). I'm now left with a pixel range of 78x36 ... and here's the error... 36 is not enough to fit into your 38.. so therefore it crashes... Looks like you're using the more dense LED-strip which has more LEDS/meter, which at that time, I didn't know existed.aimaim wrote: ↑Sat Aug 08, 2020 1:19 pmMy physical Setup is 70 horizontal LEDs and 38 vertical ones (on each side). I used to use
H_LEDS=36;
V_LEDS=18;
(half number and one off) and then double the leds in the app.ino because this worked without crashing. With your new version
H_LEDS=35;
V_LEDS=19;
does not crash anymore, yet it does not properly work either. It results in 4 (due to doubling, usually 2) LEDs being just white.
Using the actual number of LEDs
H_LEDS=70;
V_LEDS=38;
still crashes. That might be solved by increasing the "SLEEP" value. I have not tried that, since I prefer the lower "resolution" over slower performance.
What happens if you try the following:
H_LEDS=35
V_LEDS=19
which is 108 pixels in total
and then in app.ino
NUM_LEDS 216 (double the total pixels)
int p = 0;
for (i = 0; i < NUM_LEDS; i+=2) {
r = incomingPacket[(p*3)];
g = incomingPacket[(p*3)+1];
b = incomingPacket[(p*3)+2];
new_leds.r = r;
new_leds.g = g;
new_leds.b = b;
new_leds[i+1].r = r;
new_leds[i+1].g = g;
new_leds[i+1].b = b;
p+=3;
}
fadeLeds();
this should theoretically work in the way, that two LEDS show the same color.