Tight encoding is implemented by almost all clients. What makes it better than ZRLE are the following facts:
It supports JPEG encoding which is bother faster and more compact than any loss-less encoding method.
JPEG encoding causes compression artifacts, but Tight also supports loss-less encoding, so it can switch between the two depending on the situation: e.g. based on the update frequency.
Tight has 4 zlib compression stream channels per client. This means that the load can be spread between CPU cores while encoding and decoding.
The compression artifacts can be eliminated when a pixel surface settles. I.e. some time after the image has stopped changing, the server can send a loss-less upgrade for the affected area.
Overall: Tight encoding should provide smoother animations and faster response times.
any1
commented
4 years ago
Tight encoding is implemented by almost all clients. What makes it better than ZRLE are the following facts:
Overall: Tight encoding should provide smoother animations and faster response times.