Multimedia

Adaptive audio

With Adaptive audio, you don’t need to configure the audio quality policies on the VDA. Adaptive audio optimizes settings for your environment. It replaces legacy audio compression formats to provide an excellent user experience.

For more information, see Adaptive Audio.

Feature attributes

There are two feature attributes:

• EnableAdaptiveAudio: Set the value to true to enable the adaptive audio feature. Set the value to false to disable the feature.

• EnableStereoRecording: Stereo recording is an optional feature. By default, this feature is disabled. Set the value to true to enable stereo recording for the Google Chrome browser or set the value to false to disable the feature. This feature can be supported only when the adaptive audio feature is enabled. When the EnableStereoRecording attribute is set to true, the stereo recording is supported with the Google Chrome browser with echo cancellation disabled. The Apple Safari and Mozilla Firefox browsers can’t support stereo recording.

How to Configure

You can configure the adaptive audio feature as follows:

Configuration.js

In Citrix Workspace app for HTML5, the configuration.js file is located under the C:\Program Files\Citrix\Receiver StoreFront\HTML5Client folder. Edit this file to configure adaptive audio.

Notes:

• Citrix recommends that you back up the configuration.js file before modifying it.
• Administrator-level credentials are required to edit the configuration.js file.

To configure adaptive audio:

1. Navigate to the configuration.js file in the HTML5Client folder.
2. Add the EnableAdaptiveAudio attribute and set the attribute to true. Add the EnableStereoRecording and set the attribute to false. For example,

  'features' : {
    'audio' : {
      'EnableAdaptiveAudio': true
              }
             }
<!--NeedCopy-->

  'features' : {
    'audio' : {
      'EnableStereoRecording': false
            }
           }
<!--NeedCopy-->

1. Click Save.

Note:

• To disable the feature, set the EnableAdaptiveAudio attribute to false.

Known Limitations

• The Mozilla Firefox browser doesn’t support resampling for recording. In some abnormal cases, recording on Mozilla Firefox might fail.

  The adaptive audio support for recording is disabled when the Mozilla Firefox browser is used.

• The Apple Safari and Mozilla Firefox browsers don’t support stereo recording because of a limitation in the browser.

Plug and Play audio device support

Previously, only a single audio playback and recording device was supported and displayed as Citrix HDX Audio regardless of the real device name.

We support many audio devices and redirect them to VDA. Now, when you redirect audio devices, you can view the real name of the audio device under the Sound settings > Playback and Sound settings > Recording on the VDA. The list of devices on the VDA is dynamically updated whenever an audio device is plugged in or removed.

Note:

• By default, this feature is enabled.

Configuration

You can use configuration.js to configure this feature as follows:

Notes:

• Citrix recommends that you back up the configuration.js file before making changes.
• Administrator-level credentials are required to edit the configuration.js file.

To disable the feature:

1. Navigate to the configuration.js file.

   Note:

   The configuration.js file is located under the C:\Program Files\Citrix\HTMLClient folder.

2. Edit the file and locate the AudioRedirectionV4 attribute. Set the attribute to false.

   For example,

       'features' : {
           'audio' : {
               'AudioRedirectionV4': false
                   }
           }
   <!--NeedCopy-->
   

3. Save the changes.

Known Limitations

• On the VDA, the name of the built-in audio device is in English only. The issue occurs when you use ChromeOS-based devices. [RFHTMCRM-8667]
• This feature is supported on Microsoft Chromium Edge and Google Chrome browsers only.

Webcam

Citrix Workspace app supports webcam optimizations for both 32-bit and 64-bit applications with built-in webcams.

Webcam redirection

To configure webcam redirection:

1. Open the configuration.js file.

2. Navigate to HTML5_CONFIG > features > video > config > codecType.

   Note:

   • The Google Chrome and Microsoft Edge Chromium browsers use both hardware and software codecs. The Mozilla Firefox and Apple Safari browsers use only software codec.

3. Select the codecType value:

• 1 - HARDWARE_CODEC with SOFTWARE_CODEC fallback (default)
• 2 - Only SOFTWARE_CODEC
• 3 - Only HARDWARE_CODEC

Enhanced support for webcam redirection

Webcam redirection support is available not just for Google Chrome and Microsoft Edge (Chromium) browsers, but it also available on Mozilla Firefox and Apple Safari browsers.

Microsoft Teams optimization

Microsoft Teams optimization supports audio call, video call, and screen sharing functionalities on the Google Chrome browser only. The minimum Google Chrome version required is m97 and later.

Note:

• The Microsoft Teams optimization applies to the Microsoft Teams desktop version and not the web version on the VDA.
• The screen sharing functionality is enabled by default.

Feature limitation:

• When you use Microsoft Teams optimization and share the screen, a red border that indicates the screen sharing is unavailable. [RFHTMCRM-6360]
• When you use Microsoft Teams optimization, the screen sharing functionality is disabled by default. After you enable it, you can share the local device contents. [RFHTMCRM-6156]

Known issues in the feature:

• Microsoft Teams optimization is supported on the Google Chrome browser only. [RFHTMCRM-6194] [RFHTMCRM-4724]

For troubleshooting on the shim library version, see the Microsoft Teams optimization logs section.

Screen sharing

Starting with version 2209, by default, the screen sharing is enabled. The end users can now share apps and tabs that are opened through Citrix Workspace app. During screen sharing, the blue border appears around the shared window.

To share the entire screen, administrators can edit the configuration.js file located under the C:\Program Files\Citrix\Receiver StoreFront\HTML5Client folder and change the shareAllContent attribute to true. When this feature is on, the end users can share the entire screen including the resources that aren’t opened from Citrix Workspace app.

For example,

    'msTeamsOptimization':{
                       'screenSharing' : true,
                       'shareAllContent' : true
                       'seamlessApps' : true,
                       'webcamSupportInMM' : true,
                       'originTrialToken' : {
                               'chrome': "",
                       },
                       }
<!--NeedCopy-->

Support for dynamic e911

Citrix Workspace app supports dynamic emergency calling. When used in Microsoft Calling Plans, Operator Connect, and Direct Routing, it provides the capability to:

• configure and route emergency calls
• notify security personnel

The notification is provided based on the current location of the Citrix Workspace app that runs on the endpoint, instead of the Microsoft Teams client that runs on the VDA.

Ray Baum’s law requires the 911 caller’s dispatchable location to be transmitted to the appropriate Public Safety Answering Point (PSAP). Starting from Citrix Workspace app 2202 for HTML5, Microsoft Teams Optimization with HDX is compliant with Ray Baum’s law.

For Microsoft Teams optimization e911 calling, enable Location access as shown:

Background blurring and effects in Microsoft Teams optimization

Starting with the 2303 release, Citrix Workspace app for HTML5 supports background blurring and effects in Microsoft Teams optimization for video calls. You can either blur or replace the background effects provided by Microsoft Teams to avoid unexpected distractions by helping the conversation stay focused on the silhouette (body and face). This feature can be used with P2P and conference calls.

Notes:

• By default, this feature is disabled.
• This feature is now integrated with the Microsoft Teams UI. Multi-window support is a prerequisite that requires a VDA update to 2112 or higher. For more information, see Multi-window meetings and chat.

Limitations

• Administrator and user-defined background replacement aren’t supported.
• When you enable this feature, you might observe performance issues.
• After the ICA session is reconnected, the effect is off. However, the Microsoft Teams UI shows that the previous effect is still On by a tick mark. Citrix and Microsoft are working together to resolve this issue.

How to configure

You can configure the background effect feature as follows:

Configuration.js

In Citrix Workspace app for HTML5, the configuration.js file is located under the C:\Program Files\Citrix\Receiver StoreFront\HTML5Client folder. Edit this file to configure the background effect feature.

NOTES:

• Citrix recommends that you back up the configuration.js file before modifying it.
• Administrator-level credentials are required to edit the configuration.js file.

To enable background effect:

1. Navigate to the configuration.js file in the HTML5Client folder.

2. Add the backgroundEffects attribute and set the attribute to true. For example,

   'features' : {
           'msTeamsOptimization' :
           {
               'backgroundEffects' : true
           }
       }
   <!--NeedCopy-->
   

3. Save the changes.

Multi‑window chat and meetings for Microsoft Teams

Starting with the 2301 version, you can use multiple windows for chat and meetings in Microsoft Teams. You can pop out the conversations or meetings in various ways.

For details about the pop‑out window feature, see Pop out a chat in Microsoft Teams. For troubleshooting see, CTX253754.

Microsoft will deprecate the single‑window support in the future. If you’re running an older version of Citrix Workspace app or Virtual Delivery Agent (VDA), you can upgrade to:

• Citrix Workspace app 2301 or later and
• VDA - 2203 or later

Live Captions in Microsoft Teams

Microsoft Teams optimization supports real‑time transcription of what the speaker is saying when Live Captions is enabled in Microsoft Teams.

Support for secondary ringer

You can use the secondary ringer feature to select a secondary device on which you want to get the incoming call notification when Microsoft Teams is optimized.

For example, consider that you have set a speaker as the Secondary ringer, and your endpoint is connected to the headphones. In this case, Microsoft Teams sends the incoming call ringer to both the headphones and the speaker. You can’t set a secondary ringer in the following cases:

• When you aren’t connected to more than one audio device
• When the peripheral isn’t available (for example, a Bluetooth headset)

Note:

By default, this feature is disabled.

Configuration

You can enable the secondary ringer feature in the following way:

Configuration.js

Notes:

• Citrix recommends that you back up the configuration.js file before making changes.
• Administrator-level credentials are required to edit the configuration.js file.

To enable the feature using the configuration.js file, do the following:

1. Navigate to the configuration.js file.

   Note:

   The configuration.js file is located under the C:\Program Files\Citrix\HTMLClient folder.

2. Edit the file and set the value of secondaryRingtone to true.

   The following is an example of JSON data:

   {
       'features':{
           'msTeamsOptimization':{
               'secondaryRingtone' : true 
               }
           }
   
   }
   <!--NeedCopy-->
   

3. Save the changes.

Simulcast implementation for optimized Microsoft Teams video conference calls

Starting with the 2312 release, by default, simulcast support is enabled for optimized Microsoft Teams video conference calls. With this support, the quality and experience of video conference calls across different endpoints are improved. We’re adapting to the proper resolution for the best call experience for all callers.

With this improved experience, each user might deliver multiple video streams in different resolutions (for example, 720p, 360p, and so on). It depends on several factors including endpoint capability, network conditions, and so on. The receiving endpoint then requests the maximum quality resolution that it can handle by that giving all users the best video experience.