"Image compression" definition mismatch

[ilouzl]

My actions before raising this issue

• Read/searched the docs
• Searched past issues

Mismatch between the definition of "Image quality" parameter in the Task creation page, and it's definition in the User's Guide.

Expected Behaviour

High "Image quality" parameter should yield low compression level - and vice versa.
Also, need to maintain consistency between the documentation and the actual parameter meaning.

Current Behaviour

In the User guide It's defined in the opposite way - Image Quality. Use this option to specify quality of uploaded images. The option helps to load high resolution datasets faster. Use the value from 1 (completely compressed images) to 95 (almost not compressed images)
In the Task page, the Image quality parameter tooltip displays Defines image compression level which may sound inverse to Image quality. - and in fact low value in this field yields high compression level <-> lower image quality.

Possible Solution

Either change the name of the parameter to

Context

Confusion when trying to lower image quality in order to achieve better streaming experience when dealing with high resolution videos.

Your Environment

• Git hash commit (git log -1): 07de714
• Docker version docker version (e.g. Docker 17.0.05): 19.03.12
• Are you using Docker Swarm or Kubernetes? No
• Operating System and version (e.g. Linux, Windows, MacOS): Ubuntu 18
• Code example or link to GitHub repo or gist to reproduce problem:
• Other diagnostic information / logs:
  Logs from `cvat` container

Next steps

You may join our Gitter channel for community support.

[azhavoro]

@ilouzl thanks for the report!

[nmanovic]

@ilouzl , thanks for the issue. Do you think you can help us to prepare the PR?

[ilouzl]

Sure