Hello & good evening,
I'm just discovering this interesting project, want to say thank you for all the efforts so far, but just stumbled upon a problem.
While using no external USB-grabber und trying with the KODI-Addon as a software grabber, the protocol buffers server is disappearing frequently (one ore twice a second), which can be observed in the web configuration tool "remote control", causing the WLED to flicker extremly.
At the same time, these messages are appearing in the data logger in infinite repetitions:
"
2024-12-26T21:14:09.343Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:178:registerInput()) Register new input 'Proto@::ffff:127.0.0.1/PROTOSERVER' () with priority 100 as inactive
2024-12-26T21:14:09.343Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:422:updatePriorities()) Set visible priority to 100
2024-12-26T21:14:09.343Z [IMAGETOLED|First LED Hardware instance] (DEBUG) (ImageToLedsMap.cpp:112:ImageToLedsMap()) Total index number is: 810 (memory: 810). Reduced pixel set factor: 0, Accuracy level: 0, Image size: 64 x 36, LED areas: 270
2024-12-26T21:14:10.270Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:371:updatePriorities()) Timeout clear for priority 100
2024-12-26T21:14:10.270Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:422:updatePriorities()) Set visible priority to 250
2024-12-26T21:14:10.271Z [IMAGETOLED|First LED Hardware instance] (DEBUG) (ImageToLedsMap.cpp:112:ImageToLedsMap()) Total index number is: 23520 (memory: 23520). Reduced pixel set factor: 0, Accuracy level: 0, Image size: 480 x 270, LED areas: 270
"
Could it be, that my home server is overloaded and if, could I adjust manually the internal timeout trigger, that seems to cause this effect ?
I am grateful for every good advice. 
best regards & thank you
Jan