You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients expect zlib streams to be preserved when switching encodings.
This is what causes the the RealVNC client to fail to connect sometimes. The screen flickers a bit and it shows some Zlib error. It happens because it switches between ZRLE and raw while starting up, possibly for trying to figure out which is faster.
This is also a problem for ZRLE, but H264 should be fine because it will always send a key-frame after a new encoder has been allocated.
The text was updated successfully, but these errors were encountered:
Both RealVNC and TigerVNC clients expect zlib streams to remain when
switching encodings, so when they switch back, inflate fails if the
encoder is discared.
fixes#109
Clients expect zlib streams to be preserved when switching encodings.
This is what causes the the RealVNC client to fail to connect sometimes. The screen flickers a bit and it shows some Zlib error. It happens because it switches between ZRLE and raw while starting up, possibly for trying to figure out which is faster.
This is also a problem for ZRLE, but H264 should be fine because it will always send a key-frame after a new encoder has been allocated.
The text was updated successfully, but these errors were encountered: