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
I seem to have a similar issue when trying to connect to the PiKVM VNC server. It fails with the following message in the server logs:
[main]: ... has_tight [] -- False
[main]: ... tight_jpeg_quality [] -- 0
[main]: ... has_h264 [] -- False
[main]: Error: Tight JPEG encoding is not supported by client
Since you mentioned that Tight is not implemented as an encoding, and the PiKVM docs mention this as a requirement, I'd assume there is no way around this.
As someone with zero knowledge of how VNC encodings work: Is this something that could relatively easily be added to vncdotool, or would this be a greater effort or maybe even impact functionality like expect?
While refactoring vncdotool I already had some quick thoughts on adding support for other encoding as vncdotool currently only supports RAW.
You would have to extend vncdotool.rfb.RFBClient._handleRectangle() to handle other formats. For JPEG that should be easy as we already depend on Pillow, which supports many formats: get the right number of octets from the network stream, pass it to Pillow for decoding, paste the result into the screen buffer.
Add the new format to vncdotool.rfb.RFBClient.SUPPORTED_ENCODINGS.
No handler for TIGHT ?
vncdotool version
last master ersion
The text was updated successfully, but these errors were encountered: