- Newest
- Most votes
- Most comments
Hello! Over the past few years, we have made improvements on how the text is rendered using the WSP protocol. At this time of writing, the latest WSP agent version is 2.0.0.829. The major change to improve text rendering was released with version 2.0.0.312. Previous releases (such as all 1.x versions, like 1.0.1.1855) could experience the issue described above.
To check the current installed version, you can open the file ".applications" (there's a period) which is located in the C:\Program Files\Amazon\SkyLight\ (double click and choose to open with Notepad) in your WorkSpace and then look for the following:
{
"appName": "WspInstallStatus",
"version": "2.0.0.829"
},
If you still notice the issue with current versions, please check your latency by clicking the "honeycomb" icon in the top right of the WorkSpaces client. For optimal results, your latency should be less than 250 ms [1]. If you are not experiencing high latency, please open a new support case and we will be here to assist you.
[1] Amazon WorkSpaces client network requirements - https://docs.aws.amazon.com/workspaces/latest/adminguide/workspaces-network-requirements.html
WSP updates to improve frame rates are regularly being released, however I would like to revisit the audio issues at 60 ms with PCoIP. Typically, customers start to notice audio issues above 100 ms, so I think there is more to the story.
I'd love to provide more context about our setup. Feel free to reach out or provide a way for me to reach you please.
Relevant content
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
My organization is experiencing the exact same issue. We have several users experiencing compression artifacts and pixelation after migrating their WorkSpaces from PCoIP to WSP. These users are connecting from their home ISPs, WorkSpaces network check all green, ping < 100 ms. Have you found a fix to this issue? So far all we can do is migrate these users back to PCoIP.
No, I have not found a solution and I did exactly what you did which was migrate them all back to PCoIP.