Why does XLIghts not use ZLIB for the ED Extended Data ?

[Florida-Rob]

Why does XLIghts not use ZLIB for the ED Data !!!

I have found that the facebook ZSTD need > 150KB to run, no matter how to try and contain the workspace for the algorithm, either Block, Raw or Stream. So for small micros, its 'impossible' to use ZHSD.
So ZLIB works, typically 32KB, and works great.
BUT, BUT....
The ED section is ALWAYS encoded in ZSTD !

// XS - xLight xsq (zstd compressed binary)
// XN - xLight xlights_network.xml (zstd compressed binary)
// XR - xLight xlights_rgbeffects.xml (zstd compressed binary)

so...
How are we supposed to decode universes from the file? as the blocks with Frames of Channels are in ZLIB, but the ED data is in ZSTD !

am I missing something ?
Of course we can seperate the Sender from Receiver, and program the Receiver (with the FSEQ file) with mapped Universe(s) to strip(s), but how is that mapped ?


you can see from the data below how a simpel 2 universe, 200 LED, 600 Pixel, FSEQ as ZLIB is output, and also the memory usage during Zlib:

Directory contents of /sdcard:
DIR: System Volume Information
FILE: seq-200LED.fseq
Inside process_fseq
-->MEM FREE 151552
======================
== Xlights FSEQ V2.0 Header
======================
Channel Data offset : 216
variable Data offset : 128
FSEQ Version: 2.2
Channel Count: 1020
Frame Count: 600
Step Time (ms): 50
Compression : ZLIB
Compression Blocks : 12
channel Range Count : 0
======================
-->MEM FREE 151552
== Variable Headers
ID: sp, Size: 34 Data: xLights Windows 2026.01 64bit
ID: ED, Size: 18, Code: XR, Offset: 47126, Ln: 1805xLights_rgbeffects.xml (zstd), Data[0-9]:28 B5 2F FD 60 CB 1E 1D 38 00
ID: ED, Size: 18, Code: XN, Offset: 48931, Ln: 460xLights_network.xml (zstd) , Data[0-9]:28 B5 2F FD 60 25 02 15 0E 00
ID: ED, Size: 18, Code: XS, Offset: 49391, Ln: 1415xLights xsq (zstd) , Data[0-9]:28 B5 2F FD 60 9F 18 ED 2B 00
======================
-->MEM FREE 151552
== Compression Blocks
Block 0: First Frame 0, Comp. Size 2594 bytes
Block 1: First Frame 10, Comp. Size 17946 bytes
Block 2: First Frame 76, Comp. Size 8241 bytes
Block 3: First Frame 142, Comp. Size 1934 bytes
Block 4: First Frame 208, Comp. Size 1375 bytes
Block 5: First Frame 274, Comp. Size 1834 bytes
Block 6: First Frame 340, Comp. Size 2672 bytes
Block 7: First Frame 406, Comp. Size 4011 bytes
Block 8: First Frame 472, Comp. Size 3420 bytes
Block 9: First Frame 538, Comp. Size 2883 bytes
Block 10: First Frame 0, Comp. Size 0 bytes
Block 11: First Frame 0, Comp. Size 0 bytes
======================
Block 0: MEM FREE 129024 SUCCESS 10200 bytes
Block 0: Decompressed 10200 bytes. Starting timed output...
Block 1: MEM FREE 56320 SUCCESS 67320 bytes
Block 1: Decompressed 67320 bytes. Starting timed output...
Block 2: MEM FREE 65536 SUCCESS 67320 bytes
Block 2: Decompressed 67320 bytes. Starting timed output...
Block 3: MEM FREE 71680 SUCCESS 67320 bytes
Block 3: Decompressed 67320 bytes. Starting timed output...
Block 4: MEM FREE 71680 SUCCESS 67320 bytes
Block 4: Decompressed 67320 bytes. Starting timed output...
Block 5: MEM FREE 71680 SUCCESS 67320 bytes
Block 5: Decompressed 67320 bytes. Starting timed output...
Block 6: MEM FREE 71680 SUCCESS 67320 bytes
Block 6: Decompressed 67320 bytes. Starting timed output...
Block 7: MEM FREE 69632 SUCCESS 67320 bytes
Block 7: Decompressed 67320 bytes. Starting timed output...
Block 8: MEM FREE 69632 SUCCESS 67320 bytes
Block 8: Decompressed 67320 bytes. Starting timed output...
-->MEM FREE 151552
======================