Release Notes

Client SDK for Linux 20.10

Important Notes and Requirements

  • Use of Anyware Client SDK requires a separate agreement with HP Anwyare.

  • The SDK is intended for use cases where client customizations are required and when Anyware Software Clients, PCoIP Zero Clients, and PCoIP Mobile Clients are not sufficient. 

  • The SDK is intended for customers with software development skills and knowledge, as well as a sound understanding of virtualization systems.

Release Overview

The PCoIP Client Software Development Kit (SDK) is a set of libraries and binaries provided to Teradici Cloud Access Software customers who require the ability to customize and build a PCoIP Client.

With control over how the PCoIP Client is built, you can:

  • Build clients that conform to your company style and branding guides.
  • Build clients that adapt to customized workflows (for example, embed a PCoIP session into a software solution).

PCoIP Client SDK 20.10 introduces new fixes and updates to the previous release. This article provides a summary of key additions, compatibility notes, resolved issues, and known issues for this release.

To build additional functionality, such as extended peripheral support, you can utilize the Teradici PCoIP Virtual Channel SDK.

What's New in This Release

This release introduces the following features and enhancements to the PCoIP Client SDK 20.10 for Linux:

SpeechMike Support

SpeechMike support has been added to the PCoIP Client SDK for Linux 20.10.

Enhanced A/V Sync Enabled by Default

The enhanced A/V sync feature is now enabled by default on the PCoIP Client SDK for Linux 20.10. User's just need to toggle on the option from the menu.

Support added for Cintiq 22 (DTK-2260) and Cintiq Pro 24 - Pen & Touch (DTH-2420) on High Latency Networks

The PCoIP Client SDK for Linux 20.10 now supports Wacom Tablets Cintiq 22 (DTK-2260) and Cintiq Pro 24 - Pen & Touch (DTH-2420) with local termination on high latency networks.

Touch support added for Cintiq Pro 32 Pen & Touch (DTH-2420)

The PCoIP Client SDK for Linux 20.10 now supports touch on the Cintiq Pro 32 Pen & Touch (DTH-2420) Wacom tablet on high latency networks.

Security and Stability Updates

Increased security and stability updates and enhancements around the PCoIP Client.

Important Notes and Requirements

  • The SDK is intended for Cloud Access Software who require some client customizations when PCoIP Software Client for Windows and Mac, PCoIP Zero Clients, and PCoIP Mobile Clients do not meet their needs. 

  • The SDK is intended for customers with software development skills and knowledge, as well as a sound understanding of virtualization systems.

Release Downloads

Related Documents and Software

Release History

Version/Build Date Description
3.5.0 April 2018 GA release
3.6.1 July 2018 GA release
3.7.0 October 2018 GA release
3.8.0 February 2019 GA release
19.05 May 2019 GA release
19.08 August 2019 GA release
19.11 November 2019 GA release
20.01 January 2020 GA release
20.04 April 2020 GA release
20.07 July 2020 GA release
20.10 September 2020 GA release

 


 
Supported Clients
PCoIP Client SDK for Linux PCoIP Client SDK for Linux is compatible with the following Linux distributions:
  • Ubuntu 18.04 (64-bit)

 

Supported Hosts
Teradici Cloud Access Software
Resolved Issues

Resolved an issue that delayed mouse event processing

109736

Eliminated delays in mouse event processing that caused a less responsive user experience. The effect was particularly noticeable when using Wacom tablets.

Fixed an issue where device remoting failed if pcoip_client_usb_is_available() was called after pcoip_client_usb_device_claim()

108791

Resolved an issue with the PCoIP Core API where calling the pcoipclientusbisavailable() SDK API after claiming the device with pcoipclientusbdeviceclaim() caused the device remoting to fail.

Shorthand method of command line parameters is obsolete

108293

The short hand method of specifying command line parameters as simply 2 characters has been obsoleted. For instance specifying debug log level could previously be specified simply as "l3", now that command must be specified as documented, either "log-level 3" or "-l 3".