What's New in this Release
Here's what's new in this release:
- New Custom Invocation Parameter: Disable Audio
- If you want to use Vidyo Neo’s video capabilities, but not its audio capabilities, you can invoke the new “Disable Audio” parameter to mute all audio (except notification sounds).
- For more information about the powerful Custom Invocation feature available with Vidyo Neo, see the Custom Invocation of Vidyo Neo Technical Note or the Using Custom Invocation article.
To determine which version of the VidyoPortal™ your Vidyo Neo release is compatible with, refer to the Vidyo compatibility matrix article.
Vidyo Neo for Desktop Compatibility
The following table defines the compatibility between Vidyo Neo for Desktop version 17.1.2 and OS platforms.
|Compatible Windows® Platforms||Compatible Mac® OS X Platforms|
|Windows 7 32-bit and 64-bit||Mac OS X 10.10.x|
|Windows 8.1 32-bit and 64-bit||Mac OS X 10.11.x|
|Windows 10 32-bit and 64-bit||Mac OS X 10.12.x|
Vidyo Neo for WebRTC Compatibility
The following table defines the compatibility between Vidyo Neo for WebRTC version 17.1.2, OS platforms, and browsers.
OS X Platforms
|Other Compatible Platforms||Compatible Browsers|
|Windows 7 32-bit and 64-bit||Mac OS X 10.10.x||Linux® (Ubuntu 14.04 and 16.04 LTS)||Chrome™ (two most recent stable channel released versions)|
|Windows 8.1 32-bit and 64-bit||Mac OS X 10.11.x||Chrome OS (two most recent stable channel released versions)||Firefox® (two most recent supported official releases)|
|Windows 10 32-bit and 64-bit||Mac OS X 10.12.x|
The tables above reflect Vidyo’s current test matrix. Other platforms and browsers may also work, although they are not officially supported.
Resolved and Known Issues
This section lists the resolved and known issues in Vidyo Neo for Desktop as well as the known issues in Vidyo Neo for WebRTC.
Resolved Issues in Vidyo Neo for Desktop
The following table lists the resolved issues in Vidyo Neo for Desktop version 17.1.2:
|Vidyo Neo for Desktop Version 17.1.2 - Resolved Issues|
|NEP-7911||The View Page Source option no longer appears in the pop-up when right-clicking on the Vidyo Neo window.|
|NEP-7889||In calls with more than eight to ten participants, audio clipping no longer occurs.|
|NEP-7780||The custom invocation parameter autoUpdate=false now correctly prevents automatic updates from occurring.|
|NEP-7779||The custom invocation parameter disableSearch=false now correctly prevents the Search field from being displayed.|
|NEP-7443||A Vidyo protocol registry application issue on Windows 7, 8.1, and 10 was fixed.|
|NEP-7171||The Vidyo Neo Calendar Integration feature for Google Calendar™ no longer displays meetings that users were not invited to.|
|NEP-7170||The Vidyo Neo Calendar Integration feature for Google Calendar no longer occasionally disconnects; therefore, users do not need to click Connect and re-authorize to see their meetings.|
|NEP-7131||An issue that prevented the Vidyo Neo Calendar Integration feature from connecting with Exchange has been fixed.|
|NEP-6774||If a user logs in via SAML on more than one machine, they will be able to successfully log in and will no longer receive the error message "Invalid username or password... Waiting for the successful login from your browser."|
|NEP-6626||Vidyo Neo now updates automatically, whereas prior to this release, in rare cases, Vidyo Neo was unable to do so.|
|NEP-6114||Joining a meeting now takes less time than it did in prior releases.|
Known Issues in Vidyo Neo for Desktop
The following table lists the known issues in Vidyo Neo for Desktop version 17.1.2:
|Vidyo Neo for Desktop Version 17.1.2 - Known Issues|
|NEP-7330||If a user joins a public room that they own, and they click the “Moderate Call” button, they are prompted to enter their credentials; however, if they click the “Moderate Call” button again, the Control Meeting page opens.|
|NEP-7244||If a user selects a ringing device other than the default on the Vidyo Neo Device Settings page, the selected ringing device is not remembered upon re-launch, and Vidyo Neo reverts to the default ringing device.|
|NEP-6836||When guest users or WebRTC users join a call with their cameras and microphones muted, they see audio-only tiles on the Vidyo Neo in-call screen.|
|NEP-6787||In some cases, if Outlook is the default email client and a user creates a meeting invitation with Vidyo Neo, when the Outlook meeting invite opens, the HTML meeting invitation does not appear.|
|NEP-6706||The “Joining the call” message continues to display for three to four seconds after all the video tiles appear.|
|NEP-6674||When Vidyo Neo is downloaded from the VidyoPortal and the installer is launched, the message “Vidyo Neo is an application downloaded from the Internet. Are you sure you want to open it?” appears twice.|
|NEP-6431||When a user has more than one display and shares a PowerPoint® slideshow when Presenter View is enabled, both the slideshow and Presenter View are shared.|
|NEP-6405||Occasionally, the ringing continues after a user cancels a direct call.|
When in Theater Mode, if all cameras are muted and then unmuted from the Control Meeting page, only one tile appears.Workaround: Switch to Gallery View to see all the tiles or disconnect and rejoin the call.
When a new meeting is created, Outlook crashes one time after each clean installation of Vidyo Neo on Windows 10 32-bit with Microsoft Outlook 2016.
If Vidyo Neo loses connection with the Microsoft Outlook calendar, the user will not receive a notification that the connection was lost.
If a user has the room details page open at the same time the admin sets a PIN for the room, when the user clicks the Join button, they will not be asked to enter the PIN nor will they be able to join the room.Workaround: Re-open the room details page. You will then be asked to enter the PIN.
|NEP-5988||The room status does not get refreshed every two minutes.|
|NEP-5956||If a monitor is shared from a Mac, the other participants in the conference see the shared monitor but they also see the highlighted borders and the Share icon.|
When a user clicks to select their own room, there is a few second delay before the room link and the send invitation links appear.
If a conference participant selects an application to share and then minimizes the application, that participant’s view will appear as if they are sharing the content, but the remote users will not see the shared content.
|NEP-5776||When the VidyoPortal is configured to not Allow Public Room creation by users, the + button (which enables the creation of new public rooms) appears for a few seconds after the Neo application starts|
When using Windows 8.1 64-bit or Windows 10, if a PowerPoint® is shared in edit mode and then switched to slide show mode, edit mode is still shown to the conference participants.
|NEP-4921||If a user’s camera is being used by an application other than Vidyo Neo, and then the user joins a call with Vidyo Neo, that user will not see a notification that their camera is in use by another application.|
|NEP-4802||Due to an Apple® limitation, when sharing the Mail application on a Mac, the minimized view of Vidyo Neo for Desktop is also shared.|
|NEP-4801||Due to an OS limitation, while a participant is sharing their screen, the green outline that appears around the shared content does not include the taskbar even though the other conference participants can actually see the taskbar.|
|NEP-4713||Due to an OS limitation, when a participant views the list of apps available to share, Safari® windows are shown as “Untitled” and Chrome™ windows are shown as “New Tab”.|
|NEP-4313||Due to a limitation in Outlook on a Mac, when a meeting is scheduled via Vidyo Neo on a Mac, the attendees’ availability information does not appear.|
In low bandwidth calls, lip sync issues might occur.
|NEP-4161||The tracer and share icon are not restored when the shared application is restored from minimized state.|
|NEP-4047||Echo can be heard for approximately one second after a headset is disconnected from a MacBook Pro® or a MacBook®.|
|NEP-3685||The incorrect CDR call completion code displays when the call is ended by the caller.|
|NEP-3684||Incorrect CDR entries display when an incoming call times out.|
|NEP-3467||If the network is slow and a user is the first participant to join a call, the user sees a “[username] has joined the conference” message instead of the “You’re the only person in the call” message.|
|NEP-3187||If a user has more than one display and shares the main display, the video window does not move to the non-shared display.|
|NEP-2129||If a Tenant admin changes the name of a room, Vidyo Neo users do not see the new room name in the UI until they log out and log back in.|
|NEP-1077||The order of the Available Shares list only updates when Vidyo Neo is restarted.|
Known Issues in Vidyo Neo for WebRTC
The following table lists the known issues in Vidyo Neo for WebRTC version 17.1.2:
|Vidyo Neo for WebRTC Version 17.1.2 - Known Issues|
|NEPWEB-1131||When a conference participant who is using a Microsoft Edge, Firefox, or Chrome browser disconnects from a call when their microphone is muted, the other participants in the call may briefly hear some audio.|
|NEPWEB-1118||Due to a limitation with the Firefox browser, if a user opens the application share list and then changes the name of an app, the app's name is not updated on the application share list.|
|NEPWEB-1090||If a user clicks a guest link, goes to the Device Settings screen, and then remains inactive for several minutes, Vidyo Neo for WebRTC times out.|
Due to a limitation with the Firefox browser, even if multiple audio output devices are connected, only the system default device appears as the speaker and ringing device on the Vidyo Neo Device Settings screen.
If there are no lines available on the VidyoPortal when a Vidyo Neo for WebRTC guest user tries to join a call, the guest user will receive the erroneous message “Unable to join the conference. Please contact your administrator” instead of the correct message “Unfortunately, all lines are in use. Please contact your administrator or try again”.
When using Firefox, if multiple windows of the same application are open, sometimes only one appears in the application share list.
|NEPWEB-916||If a Firefox user joins a call, shares content, and then edits the shared content, the other participants in the call will not see the edits.|
|NEPWEB-914||If a Firefox user joins a call as a guest and then gets disconnected, after refreshing the browser, that user will receive a message saying the server is full and asking them to “Try again”. If the user then clicks the “Try again” button, the Firefox browser icon will keep spinning and never load the page.|
When using Firefox on Ubuntu® 16.04 OS, when you start sharing an application, the application is not brought to the foreground.
When using Chrome on Windows 8.1, the device list may show an invalid speaker and microphone option with the label "Communications".