Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Viewer: Improve compression level controls #70

Open
dcommander opened this issue Nov 5, 2016 · 2 comments
Open

Viewer: Improve compression level controls #70

dcommander opened this issue Nov 5, 2016 · 2 comments

Comments

@dcommander
Copy link
Member

I think it would be a good idea to borrow from some of the experimental enhancements I made to the noVNC GUI (https://github.com/dcommander/noVNC) and change the TurboVNC Viewer options dialog such that it behaves similarly vis-a-vis setting the compression level. Specifically, I would propose to make the Compression Level widget into a combo box rather than a slider, and change the "Interframe" check box into a boolean option that allows one to enable the equivalent of the "CompatGUI" command-line parameter. If CompatGUI is true, then the compression level combo box would show all 10 options:

  • 0 (none)
  • 1 (minimal)
  • ...
  • 9 (extreme)

If CompatGUI is false and JPEG is enabled, then the compression level combo box would show the following options:

  • 0 (no Zlib) [not selectable]
  • 1 (minimal)
  • 2 (medium)
  • 3 [not selectable]
  • 4 [not selectable]
  • 5 [not selectable]
  • 6 (CL 1 + interframe comparison)
  • 7 (CL 2 + interframe comparison)
  • 8 [not selectable]
  • 9 (extreme)

If CompatGUI is false and JPEG is disabled, then the compression level combo box would show the following options:

  • 0 (no Zlib)
  • 1 (minimal)
  • 2 [not selectable]
  • 3 [not selectable]
  • 4 [not selectable]
  • 5 (CL 0 + interframe comparison)
  • 6 (CL 1 + interframe comparison)
  • 7 [not selectable]
  • 8 [not selectable]
  • 9 (extreme)
@dcommander dcommander added this to the TurboVNC 2.2 milestone Nov 5, 2016
@dcommander dcommander modified the milestones: TurboVNC 2.2, TurboVNC 2.3 May 22, 2018
@dcommander
Copy link
Member Author

Unfortunately have to push this to TurboVNC 2.3.

@al3x609
Copy link

al3x609 commented Dec 1, 2018

image

specs: nvidia grid k2, centOS,
network latency 50ms
bandwidth network 10Mbps
wifi

Hi, I want to show you this preview test, from my project.

A remote visualization HPC CaaS , containers as a service, on a cluster.

turbovnc/virtualgl
noVNC
ssh tunel ( only for test, not in production= nginx reverse proxy)
slurm WM.
singularity containers.
the perfomance is good, pero maybe will be better.
maybe:

  • level controls for low latency and hight bandwidth
  • nginx or apache image compression.
  • cache on client side.
  • H.264 hardware codification
  • UDP over websockets/tcp
  • decoding approach webGL/vnc, :S

what do you think about that?
your advice will be well received

@dcommander dcommander modified the milestones: TurboVNC 3.0, TurboVNC 3.1 Dec 21, 2021
dcommander added a commit that referenced this issue Aug 1, 2023
I was leaving room to describe #70, but unfortunately that feature is
going to have to slip yet again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants