Partners Blog Contact Us

VidyoWeb: About Version 1.3.24

Follow

What's New in This Release

Here's what's new in this release:

  • Changes to the Permission Pop-ups
    • VidyoWeb now displays a pop-up that asks the user for permission to access their microphone in addition to their camera. In previous releases, the pop-up only asked about the camera.
    • The VidyoClientForWeb application now indicates to Chrome™ that it’s using both the camera and microphone. In previous releases, VidyoClientForWeb indicated that only the camera was being used.
    • We have modified our permission mechanism on Chrome to leverage the native mechanism only; therefore, all the issues that were related to the “Save” checkbox are no longer applicable.
    • When the pop-up that requests permission from the user to join a conference appears (when using the NPAPI plugins), the application receives the following:
      • PrivateOutEventGetJoinApproval events with the “joinStatus: true” value when the user selects “Allow”.
      • PrivateOutEventGetJoinApproval events with the “joinStatus: false” value when the user selects “Deny”.

  • New and Updated Features
    • New APIs allow you to modify the number of log files and the size of each one. Here are some usage examples:

      var msg = messages.requestSetMaxLogFiles({maxLogFiles:10});
      proxyWrapper.sendRequest(msg, function(response){console.log(response);});
      var msg = messages.requestSetMaxLogSize({maxLogSize:5000}); // maxLogSize in byte
      proxyWrapper.sendRequest(msg, function(response){console.log(response);});
      
    • We now have a JavaScript equivalent API call for the native function VidyoClientConsoleLogConfigure(). You can use it as shown here:

      vidyoClient.setConsoleLogConfiguration({consoleLogConfiguration:'All'}); // (for NPAPI)
      var msg = messages.requestSetConsoleLogConfiguration({consoleLogConfiguration:'All'});
      proxyWrapper.sendRequest(msg, function(response){console.log(response);}); // (for NON-NPAPI)
      
    • A new out event, OutEventInitialVideoFrameSent, enables a window to appear as soon as the camera starts sending frames.
    • Vidyo now delivers the requireJS and non-requireJS files that work with the sample application.
    • We’ve updated the certificate bundle stored within the NPAPI plugins. This update applies mainly to Internet Explorer® users who have selected the “Enable Protected Mode” checkbox.

  • Resolved Issue
    • If a domain name is long, the “Allow <domain name> to use your camera and microphone?” pop-up message now scales to fit all of the text within the pop-up box.

 

Compatibility

If you need to determine which version of the VidyoPortal™ your VidyoWeb version is compatible with, refer to the Vidyo Compatibility Matrix.

The following table lists which OS platforms and browsers this version of VidyoWeb is compatible with. 

 

Compatible Platforms Compatible Browsers
Windows® 7 32-bit and 64-bit Chrome version 48 and later
Windows 8 32-bit and 64-bit Firefox® version 38.7.0 ESR,
and earlier than version 52
Windows 8.1 32-bit and 64-bit Internet Explorer version 11
Windows 10 32-bit and 64-bit Safari® version 9.0.3 and later
Mac® OS X 10.8 – 10.11.6  
macOS Sierra 10.12  

 

In order for VidyoWeb to work properly with Chrome:

    • The VidyoWebConnector Chrome Extension must be enabled.
    • The minimum requirement is OpenGL 2.0, and the latest GPU/Graphics driver should be installed (with OpenGL 2.0 support).

 

VidyoWeb may run successfully in environments other than those listed in the table above; however, only these environments have been tested and are supported by Vidyo.

Vidyo has tested VidyoWeb using the out-of-box settings. Issues may occur when using different browsers and security settings.

 

 

Resolved and Known Issues

Resolved Issues

The following table lists the resolved issues in VidyoWeb version 1.3.24 (0001):

VidyoWeb Version 1.3.24 - Resolved Issues
Key Summary
VWEB-3516 We’ve updated the certificate bundle stored within the NPAPI plugins. This update applies mainly to Internet Explorer users who have selected the “Enable Protected Mode” checkbox.
VWEB-3511 When the pop-up that requests permission from the user to join a conference appears (when using the NPAPI plugins), the application receives the following:
  • PrivateOutEventGetJoinApproval events with the “joinStatus: true” value when the user selects “Allow”.
  • PrivateOutEventGetJoinApproval events with the “joinStatus: false” value when the user selects “Deny”.
VWEB-3510 VidyoWeb now displays a pop-up that asks the user for permission to access their microphone in addition to their camera. In previous releases, the pop-up only asked about the camera.
VWEB-3508 The VidyoClientForWeb application now indicates to Chrome that it’s using both the camera and microphone. In previous releases, VidyoClientForWeb indicated that only the camera was being used.
VWEB-3504 If a domain name is long, the “Allow <domain name> to use your camera and microphone?” pop-up message now scales to fit all of the text within the pop-up box.
VWEB-3498 We have modified our permission mechanism on Chrome to leverage the native mechanism only; therefore, all the issues that were related to the “Save” checkbox are no longer applicable.


Known Issue

The following table lists the known issues in VidyoWeb version 1.3.24 (0001):

VidyoWeb Version 1.3.24 - Known Issue
Key Summary
VWEB-3329 When users access VidyoWeb via Chrome version 56 from their Windows 10 device and share content, the content being shared becomes misaligned on the device.

 

Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.