Hi,
the /video option allows the server to offload decoding to the client.
For that you need the following:
1. A server with support (obviously)
2. Software with support
3. A use case (e.g. viewing a youtube video in h264)
If all requirements are met, then the server MAY decide to use it.
(currently only h264 is supported)
It is best used in combination with /gfx:avc444 as that is the most
recent codec (low bandwidth with high image quality) supported (which
uses h264 and you need it for /video anyway)
So, usually the sequence is the following:
1. You play some video
2. The server decides that this task does not require decoding and
re-encoding server side and sends the video directly to the client using
the video channel
Step 2 is delayed for some seconds up to a minute.
So, to sum up:
1. /video is for reducing CPU/GPU encoding load on the server side
2. You will not see any difference on the client
regards
Armin
On 26.02.20 16:49, Rodney Barnett via FreeRDP-devel wrote:
I'm not clear on the requirements for using the /video command line
option and wondering if anyone can provide some information or point me
to some documentation.
Are other command line options required (e.g., /gfx)? Are there
particular external codecs or libraries required?
When I tried it, I didn't see any errors, but couldn't see any
difference with or without the /video option. Is there a good way to
confirm that it's actually working?
Thanks for any help.
Rodney
_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
_______________________________________________
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
