Partners Blog Contact Us

VidyoRoom: About Version 3.3.24


The information in this article applies to the following products:

  • VidyoRoom™ HD-2
  • VidyoRoom HD-3
  • VidyoRoom HD-40 Revision A
  • VidyoRoom HD-40 Revision B
  • VidyoRoom HD-40 Revision C
  • VidyoRoom HD-100 Revision D
  • VidyoRoom HD-230 Revision A
  • VidyoRoom HD-230 Revision B
  • VidyoPanorama™ 600
  • VidyoRoom SE

What's New in This Release

Here's what's new in this release:

  • Support for Additional Peripherals
    • To make it more convenient for you to choose the peripheral device that best fits your needs, we’ve added support for these additional devices:
      • The Logitech® Meetup, an all-in-one device that includes an HD 1080p camera, microphone, and speaker.


      • The VDO360, a 90° field of view, USB, PTZ conferencing camera.


      • The Presonus AudioBox USB 96, a USB 2.0 audio interface for VidyoRoom HD-2 and HD-3 systems.


  • Resolved Issues
    • In this release, we’ve resolved a number of issues for enhanced system stability and usability.


Important Upgrade Information for On-Premises Customers

If you have an on-premises installation, refer to the information below to ensure that your on-premises upgrade goes smoothly. (If you are a VidyoCloud customer, you don’t need to take any action; Vidyo will upgrade your VidyoRoom to version 3.3.24 for you.)

  • If you are running VidyoRoom version 3.3.21 (0760), you can directly upgrade to version 3.3.24 by uploading it via the Admin UI.
  • If you are running VidyoRoom version 3.3.19 (0690), you must first upgrade to version 3.3.21 (0760). This will ensure that your Phoenix firmware is updated to the correct version. You can then upgrade your VidyoRoom to version 3.3.24 by uploading it via the Admin UI.
  • If you are already running VidyoRoom version 3.3.24 and you must reimage your system, your system will boot up with version 3.3.19 (0690) after the reimage. Because the Phoenix firmware will remain at the correct version, you can then directly upgrade to version 3.3.24 by uploading it via the Admin UI.



  • Version 3.3.24 (0872) of the VidyoRoom client is compatible with the following Vidyo images:


VidyoRoom Family Vidyo Image
HD-2 HD2-Win64-0_2_23_0_0584.vimage
HD-3 HD3-Win64-0_2_28_0_0841.vimage
HD-40 Revision A HD40-Win32-0_0_1_15_0084.vimage
HD-40 Revision B HD40B-Win64-0_0_2_9_0094.vimage
HD-40 Revision C HD40C-Win64-0_2_24_0_0510.vimage
HD-100 Revision D HD100D-Win64-0_0_2_8_0086.vimage
HD-230 Revision A


HD-230 Revision B HD230B-Win64-0_2_19_0_0295.vimage


Vidyo highly recommends that you apply the latest available image when upgrading your VidyoRoom system. However, before uploading a new image, please check which image version your VidyoRoom system is currently running. If it is already running a newer image, do not downgrade to an older image.


  • Compatibility for On-Premises Installations: To determine which version of the VidyoPortal™ your VidyoRoom is compatible with, refer to the Vidyo Compatibility Matrix article.

  • VidyoPanorama 600 Internet Browser Compatibility: When viewing the Admin UI pages, you must use Internet Explorer® version 9 or later, Google® Chrome™ version 35 or later, Mozilla® Firefox® version 30 or later, or Apple® Safari® version 7 or later.


Resolved and Known Issues

This article lists the resolved and known issues in VidyoRoom version 3.3.24 (0872). To make it easier to find the known issues, the Known Issues table is categorized into issues that pertain to VidyoRemote 3 only, issues that pertain to all models of the VidyoRoom, and issues that pertain to specific models of the VidyoRoom.

Prior to version 3.3.7, the VidyoRoom Resolved and Known Issues listed only the known issues that were introduced since the previous Generally Available (GA) version. Starting with version 3.3.7, the VidyoRoom Resolved and Known Issues has included a cumulative list of all known issues in the product.


Resolved Issues

The following table lists the resolved issues in VidyoRoom version 3.3.24 (0872):

VidyoRoom Version 3.3.24 (0872) - Resolved Issues
Key Summary

To prevent application errors, the Phoenix upgrader has been completely removed from the VidyoRoom installer. Therefore, Phoenix devices will no longer be upgraded during VidyoRoom reboots. If an upgrade is needed, you must manually disconnect the Phoenix device from your VidyoRoom system and run it on a separate machine equipped with a Phoenix upgrade utility.


Changes were made to the time server in order for the VidyoRoom systems to display the time more reliably.

Application crashes that occurred due to an open JSON port do not occur once the VidyoRemote interface is disabled.
GS-4308 If the VidyoRoom On Screen UI goes blank due to a Google Calendar API issue, the VidyoRoom application will restart so that the On Screen UI can be used again.
GS-4298 If a user enters an extension in the VidyoRoom Search bar, the VidyoRoom now sends the search request to the portal regardless of whether digits are added and removed from the extension and even if the digits entered indicate that the contact is an external contact.

The way in which VidyoRoom systems process the response from the portal about supported features has been changed, thereby resolving an issue where VidyoRoom systems inadvertently behaved as if the Presenter Mode feature was enabled.


If a user tries to make an IPC (Inter-Portal Communication) call but it fails for any reason, the endpoint will now retry with a direct call.

GS-4249 When using Chrome, a search for external (non-member) entries using the VidyoRemote 3 now works when the VidyoRoom is logged into a portal with a single Tenant and no scheduled rooms.
GS-4234 An Intel security vulnerability on some VidyoRoom models was addressed by a fix provided by Intel.
GS-4159 Automatic upgrade works correctly when a VidyoRoom system is paired with a VidyoRemote 3.
GS-4103 When the wrong DNS server is configured or the VidyoPortal FQDN cannot be resolved, VidyoRoom no longer displays the incorrect message "Unable to connect to VidyoPortal".
GS-3987 When using an Inogeni device with a Mac, the colors that display when sharing content are no longer muted.
GS-3867 When a VidyoRemote 3 is paired with a VidyoRoom system, the display name (rather than the username) is shown in the upper left corner of the VidyoRoom display.
GS-2293 The Windows Task Manager bar at the bottom of the On Screen UI home screen no longer flickers periodically.


Known Issues

The following table lists the known issues in VidyoRoom version 3.3.24 (0872).

If a VidyoRoom or VidyoPanorama 600 upgrade is interrupted by a system reboot or by cutting the power supply, the system may no longer boot properly, the device selection may be incorrect, and other issues may occur. If this happens, you may have to recover the system via the Recovery Console.


VidyoRoom Version 3.3.24 (0872) - Known Issues
Key Summary
VidyoRemote™ 3

In order for camera control to work when using a VDO360 camera, you must reboot your VidyoRoom system under the following circumstances:

  • Whenever the VidyoRoom system is returned to the default configuration, such as when the system is re-keyed or when the Recovery Console is used to restore both the default image and the settings.
  • When you change your camera selection from the VDO360 to another VISCA camera or from a VISCA camera to the VDO360.

Due to limitations with the VDO360 camera itself:

  • The camera cannot capture at 60 fps, even if it has been configured that way from the On Screen UI.
  • The camera cannot capture, encode, or send at 540p resolution, even if it has been configured that way from the On Screen UI.

On a VidyoRoom system with a single display, when the user displays local content, joins a call, and then disconnects from the call, the local content occasionally does not re-display.

If this occurs, disconnect and reconnect the local content-sharing device or click the pre-call local share preview (Projection) button using the VidyoRemote 3.

GS-3956 If the ScheduledRoomPrefix is 0, users cannot join a scheduled room from a VidyoRoom system using VidyoRemote 3.
GS-3955 There aren’t any indicators in place to inform users about whether the DTMF tones that they sent have actually dialed out successfully.
GS-3954 Users cannot cancel Inter-Portal Communication (IPC) calls with the “Hang Up” button.
GS-3901 If a remote user on the call is sharing content and then stops, Projection Mode becomes disabled until content is shared again.
GS-2510 When using the VidyoRemote 3, users cannot join a scheduled room by entering the full extension in the Search field.
GS-2397 If the background image is changed on the On-Screen UI Settings page, it does not get changed on the VidyoRemote 3 Settings page.
GS-2386 If a user is changed from the presenter to a viewer, the “Raise Hand” icon on that user’s VidyoRemote 3 disappears from the UI.
GS-2081 Once the VidyoRoom is controlled by the VidyoRemote 3 (that is, once the pair is established), the display name which is displayed on the top left corner of the On-Screen UI changes to user name.
GS-1843 When using the VidyoRemote 3, if a user removes their self-view, local projection gets disabled as well.
GS-1842 The VidyoRemote 3 does not have the DTMF function.

On a single display VidyoRoom using the VidyoRemote 3, the self-view preview and local projection get out of sync after disconnecting from the call. 

If this occurs, click the self-view preview and local projection icons two times to get them back in sync.
GS-1442 If a user is performing PTZ operations with the VidyoRemote 3 application and network connection problems occur between the VidyoRemote 3 and the VidyoRoom, the two may become out of sync. This results in the VidyoRemote 3 showing its home screen while the VidyoRoom screen shows the PTZ controls for the participant whose camera was being controlled when the network disconnection occurred.
GS-1409 It is not possible to PTZ cameras of guest participants from the VidyoRemote 3.
GS-1384 If the “Enable HTML Remote/VidyoRemote Interface” checkbox is not selected when the user attempts to access the VidyoRoom system from the VidyoRemote 3, the error message “Unable to communicate with the VidyoRoom. Please make sure all devices are connected to the network properly" appears. Because this message does not clearly state that the user should select the “Enable HTML Remote/VidyoRemote Interface” checkbox from the Admin UI, users might mistakenly think that the problem is related to their devices or network connection.
GS-1298 If a user with VidyoRemote 3 joins a call and is displaying local content, and then another participant in the call starts to share content and then stops, the VidyoRemote 3 user’s local content does not reappear automatically.
GS-1256 The Backlight On/Off option for the VidyoRemote 3 is not synced with the Admin UI Backlight On/Off option.
GS-960 If a user with VidyoRemote 3 clicks the Raise Hand button and their Raise Hand request is dismissed by the presenter, the button remains unchanged; therefore, the user doesn’t know that the request got dismissed, and additionally, that user must cancel the first request if they want to send a new Raise Hand request.
All VidyoRoom Models Unless Otherwise Specified

If the Screen Saver Timeout value on the Admin UI Settings page is changed from 0 to any value, a Vidyo call must be completed in order for the new value to take effect.


If a VidyoDesktop participant has a display name in a language other than English, the “Participant” field on the VidyoRoom Admin UI Statistics page does not display the correct name, but displays corrupted text instead.


In rare cases, after rebooting a VidyoRoom system, if the Exchange Server takes a long time to connect to the VidyoRoom system, the misleading message “Unable to connect to Microsoft Exchange Server. Please update user credentials” appears even when the user’s credentials are correct. Once the connection is established, the error message is removed and the calendar displays.


When a USB 2.0 camera, such as the Logitech® PTZ Pro 2, is connected to a VidyoRoom system via an extender, the video capturer does not reliably capture video frames which may result in a black screen.


Although pressing the Mute button on a Yamaha YVC 300 mutes the audio, the On Screen UI does not display the audio as muted.


After upgrading to a new VidyoRoom image, the user has to reenter their Gmail authorization code in order to see their meetings again.


When viewing Google Calendar meetings on a VidyoRoom system, the meetings should be displayed in order of occurrence. However, occasionally, the meetings do not display in order. In addition, sometimes the meetings get refreshed and meetings with a Vidyo link momentarily get displayed before meetings that don’t have a Vidyo link.


After a Phoenix device is upgraded, the Windows message “You must restart your computer to apply these changes” may appear.

  • If the message appears as part of an installer upgrade, the user needs to take no action since the VidyoRoom system will reboot as part of the upgrade.
  • If the message appears when a Phoenix device is upgraded as part of a system reboot, Vidyo recommends an extra system reboot.

When disconnecting and connecting cables on a Phoenix Power Hub MT340 or a Phoenix Quattro MT304, Phoenix Audio Technologies cautions that you must never unplug or disconnect the Cat5 Ethernet cable when the 48V power supply is plugged in.

Unplugging or disconnecting the Cat 5 Ethernet cable when the 48V power supply is plugged in may result in hardware failure, and the Phoenix device may require an RMA.


If the camera partially locks up due to the RS-232 serial port adapter (Prolific driver) failure, VidyoRoom systems are supposed to return the 90 68 03 ff code; however, occasionally they do not. 

GS-4117 When Write Protection is enabled, BSOD dump files cannot be saved or downloaded.
GS-4089 The splunkd.log is not forwarded to the server; therefore, the logs will be lost if the VidyoRoom system is rebooted before the admin downloads the log via the VidyoRoom Admin UI.
GS-4080 After the Splunk server is first configured, the event viewer logs are forwarded to the server first; therefore, it may take a few hours before the VidyoRoom logs are visible.
GS-4047 If a VISCA communication issue occurs with the camera, the VidyoRoom system will reboot once the conference is over in order to recover the camera. Note that when this issue occurs, the camera control may or may not work correctly, and there will be no indication of the cause of the reboot on the On Screen UI.
GS-4037 Occasionally, when the Phoenix Quattro or Smart Spider is connected via the Power Hub, the VidyoRoom application reads the firmware version as “unknown”.
GS-3944 VidyoRoom does not validate the client installer type after it is downloaded from the VidyoPortal.
GS-3847 If a username that contains angular brackets is entered in the Search field, an error message displays.
GS-3832 When upgrading from version 3.3.19 to version 3.3.21 while Write Protection Mode is enabled, the system may skip over a log and write to the next log. When this occurs, the log that is skipped over is displayed as 0.
GS-3827 If Presenter Mode is enabled in a conference where no participants then join or leave, the “Call in progress” indicator does not appear after a user is pinned and un-pinned. However, if a participant joins or leaves, the “Call in progress” indicator reappears.
GS-3808 When using the Remote Control API to shut down and power on the VidyoRoom, some of the log files may be created out of order.
GS-3797 After upgrading to a new installer when Write Protection Mode is enabled, all VidyoRoom.log files are not created. This issue will not occur for users upgrading from VidyoRoom version to the latest installer. 

Additionally, the Splunk® Forwarder will go into a bad state if enabled during the upgrade. Furthermore, if Write Protection Mode is only enabled during the upgrade and then disabled so that the user can make changes, when re-enabled, the remaining logs display in the Admin UI.
GS-3757 When the Mute button is pressed on a Konftel 55Wx device while the user is in a call, the audio does get muted, however the OnScreen UI does not correctly indicate that it is.

When the Splunk Forwarder is enabled, older log files are not deleted, which causes a delay in syncing new log files with the server. 

To prevent this issue, delete older log files prior to enabling the Splunk Forwarder.

GS-3752 The VidyoRoom system is unable to prioritize the order in which Splunk forwarder sourcetypes should be sent.
GS-3580 If the NTP Server checkbox is selected and the Apply button is clicked, it may occasionally take up to 15 seconds for the NTP service to be enabled, during which time the message “loading…” displays.
GS-3546 For proper calendar integration, the user should ensure that both the time zone and time on the system are correct; changing the time or time zone after calendar integration could cause the user to miss some meetings invitations.
GS-3501 If the network connection was lost while an image was being uploaded, the VidyoRoom system must be rebooted in order to upload the new image again; otherwise, the Admin UI will indicate that there is not enough space to upload the new image.
GS-3478 When two VidyoRoom systems log in to the VidyoPortal with the same credentials, the resulting behavior is not consistent (for example, one VidyoRoom may remain online while the other keeps trying to log in).
GS-3361 When a Sony EVI-H100V camera is set to D70 mode, the On-Screen UI and Admin UI About page display the camera model as D70.
GS-3360 When a camera has a long model name, such as the Sony EVI-HD7V and Sony SRG-120DH, the name wraps around to a second line on the Admin UI About page.
GS-3354 The format of the Minrray camera version that displays on the On-Screen UI and on the Admin UI About page is not the same format used by Minrray (for example, if the Minrray version is 2.2.3, the VidyoRoom could display 22.30).

When a content sharing device is connected and the user is on the Home screen of the On-Screen UI, if the user presses the Self-view key, the self-view tile will not toggle off.

If this occurs, press the Manage key from the Home screen or disconnect the content sharing device and then reconnect it.

If a user swaps displays by pressing the A button on the remote control and one of the displays is disconnected, the user may not be able to see the remote participants.

If this occurs, reboot the system to see the remote participants’ tiles. To prevent this issue, before removing a display, use the A button on the remote to swap the displays, and then either physically swap the display connections or use the Admin UI to swap the settings for each display.
GS-3330 Occasionally, when the Start Recording request is sent when the VidyoRoom system is not in a call, it causes the VidyoRoom system to crash.

If a VidyoRoom upgrade is interrupted by a system reboot or by cutting the power supply, the system may no longer boot properly, the device selection may be incorrect, and other issues may occur.

To prevent this issue, do not power off the system during an upgrade. However, if this inadvertently occurs, you may have to recover the system via the Recovery Console.
GS-3260 Log files cannot be downloaded successfully if the total size is bigger than 2GB.
GS-3256 Under high temperature conditions, VidyoRoom response time slows down and the systems take longer to get fully operational after being rebooted.

VidyoRoom does not limit the caption length; instead, as the caption gets longer, the point size of the font decreases.

To prevent this issue, the moderator client should limit the length of the caption to 80 characters for languages that use the English alphabet and 34 characters for Chinese and other Asian languages.
GS-3230 When in a call using a VidyoRoom with two displays, if the user changes which display is the Primary display via the Admin UI Display Layout page, the participant number and its corresponding green icon will appear on separate displays.
GS-3210 When using a VidyoRoom system with two displays, if the settings of the displays are different (for instance, one of them is for displaying content only or the number of tiles to be displayed are different), if the displays are swapped by pressing the A button on the remote control after joining a conference, the participants may no longer display correctly.
GS-3145 The “Call in progress” indication does not display if a user shares content after toggling their local projection.
GS-3102 The “Call in progress” indication does not display when a VidyoRoom with multiple screens has only the user’s self-view displayed.
GS-3097 The “Call in progress” indication does not display when Presenter mode is enabled but a presenter has not been selected or has left the conference.
GS-3089 The Splunk® forwarder is unable to pass VidyoRoom crash dumps and BSODs to the server.

When setting a Sony SRG-300H camera or a Sony SRG-120DH camera to VISCA, the camera resolution cannot be changed from the VidyoRoom’s configuration and remains set to 1080p60.

If this occurs, set the camera manually to the mode you want to use.

If a UniBrain USB 3.0 Active Optical Cable is unplugged from either the VidyoRoom system or from the host device linking the cable and USB 3.0 camera cable, after the UniBrain cable is plugged back in, the camera is not detected. 

In order for the camera you get detected, power cycle the UniBrain device.

GS-2852 In very rare cases, an ungraceful shutdown of a VidyoRoom connected to a power hub with a Phoenix Spider MT503 could cause the power hub to stop working.
GS-2815 If a VidyoRoom unit is connected to a power hub with a Phoenix Spider MT503, all HID-related functions (such as mute, volume, connect, etc.) do not work.
GS-2719 Some USB devices, such as the Phoenix Spider and the Logitech® GROUP, are not detected when connected with APC USB extenders.
GS-2709 The Mic buttons on the Phoenix Spider are not integrated with the VidyoRoom; therefore, pressing those buttons on the Spider has no effect on the VidyoRoom microphone volume.
GS-2705 The Admin UI does not notify the user that the “Enable/Disable Remote Control Interface” checkbox requires a reboot.

When a Revolabs FLX™ UC 1000 device is power cycled, by default it powers up with the USB set to “Off”; therefore, there is no audio from the device.

To prevent this issue, on the FLX UC 1000 dial pad, go to Menu > Settings > Admin Settings > Enter password (default is 7386) > USB Settings and select “Always Enabled”.
GS-2654 When a Revolabs FLX UC 1000 or FLX UC 1500 is connected to a VidyoRoom system, and a call participant tries to disconnect from the call from the Revolabs device, the USB device will power off, but the user will remain in the call.
GS-2653 Although pressing the Mute button on a Revolabs FLX UC 1000 or FLX UC 1500 mutes the audio, the On Screen UI does not display the audio as muted.
GS-2606 VidyoRoom cannot download the client from the VidyoPortal when web proxy and VidyoProxy are enabled, and the “File download request failed with result code 408” appears in the log.
GS-2548 If a Logitech GROUP or CC3000e is connected to a VidyoRoom after a call has been joined, and then the user presses the Mute button, the call gets disconnected.
GS-2403 If a user toggles their own local projection before any remote participant starts to share content, and then a remote participant shares content and the user toggles that content, the content reduces to a participant tile.
GS-2270 The Static IP configuration cannot be saved if the network cable is not connected.
GS-2252 When connected to the VidyoRoom via the Extron or Xtendez extenders, the Sony SRG-120DH camera resets to the default position after system reboot.

If a user makes configuration changes and also switches from normal mode to side-by-side mode, clicks Apply to apply the changes, and then clicks Cancel on the Reboot Required pop-up, some of the changes are canceled but some of them are applied.

If this occurs, reboot the system to apply all the changes.
GS-2157 When the Anti-Flicker Mode setting in the Video section of the Admin UI > Settings page is changed, the Save button must be pressed in order to save the change.

Changing resolution from 720p to 1080p via VISCA when using Sony cameras results in distorted video.

If this occurs, reboot the camera.

Occasionally, an INOGENI device does not recover during an installer upgrade.

If an INOGENI device fails to recover after an upgrade, power down the VidyoRoom system and wait at least 30 seconds before powering it back up. When the VidyoRoom powers back up, the INOGENI device will be upgraded.
GS-1923 If a new audio or video device is plugged into the VidyoRoom when the VidyoRoom is powered off, the device does not get automatically selected as a new device when the VidyoRoom is powered back on.
GS-1910 VidyoPanorama 600 and VidyoRoom appear as “VidyoPanoroom” in the CDR instead of “VidyoPanorama”.
GS-1882 If a USB device is selected as the sharing source and is then unplugged, the On-Screen UI does not show the device as disconnected, but continues to show the device as the selected sharing source. This occurs only when using a VidyoRoom with only one available sharing source.
GS-1855 When the PT Inquiry command to a Sony camera returns an error, the PT Reset command is not executed.
GS-1840 When a user in a Vidyo conference invites another user to join the conference, the inviting user receives no indication (visible, audible, or tactile) that the invitation was sent.
GS-1757 On some occasions, the recovery to the enhanced layer does not work immediately after some remote users leave the call. It may take up to ten minutes to recover the enhanced layer.

Occasionally on VidyoRoom systems with two different displays (one 720p and one 1080p), the On-Screen UI may use an incorrect resolution if one of the displays loses power and then re-gains it.

If this occurs, reboot the VidyoRoom system or press the A button on the radio frequency remote twice to swap the displays.
GS-1680 If the Use Status IPv6 checkbox is selected in the Admin UI, you cannot select or deselect the Enable IPv6 checkbox.
GS-1628 The Microsoft Office 365® calendar does not get configured when the Microsoft Exchange Server Web Service URL is set to “Auto Discover”.
GS-1507 If a call was joined using a calendar invitation, the username that the remote API replies with is not correct.
GS-1451 There is no On-Screen UI indication that lets users know if Fn lock has been activated.
GS-1427 When a Logitech ConferenceCam Connect is used, mute is not synchronized between the VidyoRoom and the Logitech.
GS-1363 When the frame rate on VidyoRoom systems with more than one display (such as the HD-230 and the VidyoPanorama 600) is set for 30 fps or 15 fps, the self-view occasionally displays at half the configured frame rate.
GS-1359 When mute is turned on or off on a Yamaha® YVC audio device, the mute indicator on the VidyoRoom On-Screen UI does not change accordingly.
GS-1259 When the VidyoRoom video transmit rate is set to 360p at 384 Kb/s, it impacts the receive bit rate of its clients in that the receive video remains at a low bit rate.

If a call is dropped or a user disconnects from a conference while the speakers are turned off, the next incoming calls appear as messages on the display but they do not ring.

If this occurs, answer one of the incoming calls and then disconnect while the speakers are on; subsequent incoming calls will then ring.
GS-1135 The VidyoRoom control interface is only available in the English language. If the On-Screen UI is set to another language, the control interface continues to display in English.
GS-1130 When creating a Google Calndar meeting, if the “Show Me As” status is set to “Available”, the Google Calendar meetings do not display on the screen.
GS-1042 When the DNS resolution fails because the user has the wrong DNS name, the user is not able to log in, but is not notified with a reason.
GS-835 The process of updating an INOGENI device takes several minutes, during which the screensaver typically displays. The screensaver is not an indication that the upgrade has paused or finished; therefore, users should not disturb the system and should allow the upgrade to complete.
GS-455 Remote users see a black, green, and gray window if a camera is not connected on VidyoInput1, VidyoInput2, or INOGENI video sources.
VidyoRoom HD-2 Only
GS-2913 When using a Minrray UV950A camera with an HD-2 at 1080p60@4M or 6M resolution, the Captured/Encoded framerate drops when a content share device is selected (whether or not content is actually shared).
VidyoRoom HD-3 Only

When a Revolabs FLX2 is used with a VidyoRoom HD-3 system, the audio does not work properly.

To prevent this issue, connect the FLX2 using a Revolabs FLX USB Audio Connector Kit (model 01-USBAUD35-KIT).
GS-3878 If an Epiphan device is connected to a VidyoRoom HD-3 after Write Protection Mode is enabled, the device will not be read properly and the Device Manager will display “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.”
GS-2935 The ambiguous message “Installer file is invalid” appears when an unsupported installer version is uploaded.
GS-2845 In some cases, if a Revolabs line-in/line-out audio device is disconnected and then reconnected to a VidyoRoom HD-3, it may cause the HD-3 to crash.
GS-2844 In two-display setups of the VidyoRoom HD-3 with both displays configured to decode in 4K resolution, no more than eight participants can be displayed per screen. Even if the user sets the Admin UI to display more, the system will limit the number of participants displayed on each screen to eight.

If a VidyoRoom HD-3 is shut down while an image upgrade is in progress, the HD-3 gets stuck in a BSOD loop.

If this occurs, reboot into the Recovery Console and perform a Factory Restore.
GS-2681 In two-display setups of the VidyoRoom HD-3 with both displays configured to 1080p60, if one display is unplugged, the remaining displays convert to 4K.

In four-display setups of the VidyoRoom HD-3, clicking the “Unlock EDIDs” button causes the displays to randomly disappear from the Admin UI display layout and causes their resolutions to change in the Admin UI. 

To prevent this issue, click the “Lock EDIDs” button after configuring the display layout—especially when using 4K monitors. If you need to unplug a display, you must click “Unlock EDIDs”, change the display setup, reboot, configure the displays, and then click “Lock EDIDs”. For more information, refer to the VidyoRoom and VidyoPanorama 600 Administrator Guide.

In two-display setups of the VidyoRoom HD-3 with both displays configured to 4k, the displays boot up with black screens after the VidyoRoom is keyed.

If this occurs, on the Display Layout tab in the Admin UI, change the resolution to the correct resolution for the display.
GS-2566 Extron extenders are unstable in two-display setups of the VidyoRoom HD-3 with both displays configured to 4k.
GS-2523 When 720p15 and 1080p15 are selected for the camera connected to an HD-3, the statistics display 30 fps.
GS-2495 In a setup of the VidyoRoom HD-3 with more than two displays, when a remote participant shares content and then stops sharing, the display layout may change.
VidyoRoom HD-40 Only

HD-40 Revision C systems negotiate 4K resolution when connected to a 4K display.

To prevent this issue, if you have a 4K display, you can select 1080p resolution on the Admin UI > Settings tab to ensure that the resolution remains at 1080p.
When performing a join and leave call test, the VidyoRoom HD-40 Revision A and C systems crash.
GS-3820 When performing a join and leave call test, the VidyoRoom HD-40 Revision 4A systems become unresponsive.
GS-3774 There’s an occurrence where the time zone in the VidyoRoom HD-40 Revision A changed to UTC on its own.

On rare occasions, new log files are not created when Write Protection Mode is enabled for VidyoRoom HD-40 Revision A systems that contain old CMOS batteries.

If this occurs, change the CMOS battery and correct the system time.


An exception error can occur if the VidyoRoom receives numerous IPv6 temporary addresses.

To prevent this issue, deselect the Enable IPv6 checkbox if your VidyoPortal does not support IPv6.
GS-2955 If a Sony SRG-300H camera is connected to a VidyoRoom HD-40 Revision A or Revision C via an extender, the camera does not go to its previous position after the VidyoRoom system is rebooted.

If a Sony SRG camera is connected to a VidyoRoom HD-40 Revision C with a UniBrain extender when a power outage occurs, the Sony camera freezes. 

In order for the camera to get detected, while still in the call, deselect and then re-select the camera from the Admin UI.
GS-2269 If a user has multiple audio devices plugged in and the selected audio device is unplugged after a system shutdown, then television speakers are automatically selected for the audio output.
GS-1922 If a VidyoRoom HD-40 Revision A system is ungracefully shutdown (such as during a power outage), in rare instances, the INOGENI device will not get detected by the VidyoRoom until the next time the VidyoRoom is rebooted.
GS-1795 A VidyoRoom HD-40 Revision A with a Sony EVI-H100V and an INOGENI device occasionally crashes if the television display is turned off while the VidyoRoom system is operational upon joining and leaving calls, and when camera control is in progress.
GS-1790 The Google calendar account is not a supported feature with VidyoRoom HD-40 Revision A. An invalid username/password error message displays when the correct credentials have been entered.
GS-1737 If a VidyoRoom HD-40 Revision A is connected to non-Vidyo branded INOGENI devices, the non-branded INOGENI firmware does not get updated when upgrading from VidyoRoom version 3.2.4 to version 3.3.5.
VidyoRoom HD-100 Revision 4A Only
GSI-138 VidyoRoom HD-100 Revision 4A systems go into sleep mode while the system is being configured after an image upgrade.

After disconnecting from a call, the VidyoRoom HD-100 Revision 4A system may freeze, which causes a black screen with a green lock to display. The VidyoRoom system may later recover on its own.


When testing the VidyoRoom HD-100 Revision 4A systems for long periods of time, the VidyoRoom system may get into a bad state and cause the GPU driver to crash.


There’s an occurrence where the VidyoRoom HD-100 Rev 4A system became unresponsive during an overnight call test.


In roughly one of 600 attempts, VidyoRoom HD-100 Revision 4A systems experienced a BSOD error upon rebooting and/or after an ungraceful shutdown.

If this occurs, press and hold the Power button to shut off the system, and then press the Power button again to power it back on.


eLert devices do not work when connected to the front USB ports on VidyoRoom HD-100 Revision 4A systems.

To prevent this issue, use the rear USB ports to connect eLert devices.

Under high temperature conditions, if a tvONE video scaler is connected to a VidyoRoom HD-100 Revision 4A system, the tvONE scaler may reset to factory defaults which would result in the remote site seeing green or black video.

If this occurs, manually reset the correct resolution on the tvONE scaler.
GS-2924 If a VidyoRoom HD-100 Revision 4A is re-imaged with a Gen 3 VidyoRoom image, the microphone and speaker volume settings are not maintained.

If there is an active 32-bit VidyoRoom installer on the VidyoPortal that is older than version and that installer is applied to any VidyoRoom HD-100 Revision 4A system running VidyoRoom version 3.3.x, the VidyoRoom HD-100 Revision 4A systems become inoperable.

To prevent this issue, ensure that there are no active 32-bit VidyoRoom installer versions older than on the VidyoPortal prior to upgrading to VidyoRoom version 3.3.8. If you inadvertently downgrade to an older version on a VidyoRoom HD-100 Revision 4A system, you will need to re-image it from the Recovery Console.

The Restore to Factory Image fails when users click the Restore Factory Image button on the Admin UI when all image files are deleted.

If this occurs, reboot locally and upload the image that needs to be applied in the Admin UI or upload the image from the USB drive via the recovery console.
GS-1972 The camera on VidyoRoom HD-100 Revision 4A systems cannot be powered off. If the camera is manually powered off, the VidyoRoom HD-100 Revision 4A resets the camera and powers it on again.
GS-1712 When a Sony D70 camera is connected to an HD-100 Revision 4A, the camera may not come back to its configured position after the VidyoRoom system is rebooted.
GS-1662 If a VidyoRoom HD-100 Revision 4A is re-imaged with a Gen 3 VidyoRoom image, the process takes longer than a standard reboot due to the drivers and older hardware in the HD-100 Revision 4A. In addition, during the reboot, a blank white screen may display for a minute or two.
GS-1574 If a VidyoRoom HD-100 Revision 4A is re-imaged with a Gen 3 VidyoRoom image, the microphone and speaker volume settings are not maintained.

Occasionally, a video capture device is not detected by the On-Screen UI when a VidyoRoom HD-100 Revision 4A is upgraded from a Flex Room image to a Panoroom image. 

If this occurs, reboot the VidyoRoom system in order for the On-Screen UI to detect the device again. You can then manually select the device.

Occasionally, in very long calls (such as a call that lasts overnight), participants in the conference see frozen video from an HD-100 Revision 4A. 

If this occurs, disconnect and then re-join the conference.

GS-1324 Unlike other VidyoRoom models, it may take up to ten minutes to upgrade an HD-100 Revision 4A.
GS-1316 If two monitors are connected to an HD-100 Revision 4A and the main display is configured for four tiles, the HD-100 restarts if it joins a conference with more than four participants.
VidyoRoom HD-230 Only
GS-2297 If a user of a VidyoRoom HD-230 changes the resolution of a Sony SRG USB camera, that user then has to manually re-select the Sony as the camera device.
GS-2283 The HD-230A and HD-230 images can be uploaded to the VidyoRoom HD-230 system via the Recovery Console.
GS-2231 The Sony SRG USB 3.0 camera does not display 1080p when connected to a VidyoRoom HD-230 system. When configuring 1080p from the On Screen UI, the self-view does not display and the screen is black.
GS-2228 If the VidyoRoom HD-230 system is unexpectedly shutdown (e.g., power outage), then the connected camera may not be detected by the room system until after rebooting.
VidyoRoom SE Only
GS-2504 When a Sony® SRG-120 camera is being used with a VidyoRoom SE, the resolution on the camera cannot be changed to 1080p15.
GS-2499 Occasionally, when using a VidyoRoom SE, the Sony SRG-120 camera stops appearing in the list of cameras after the resolution is changed.

In rare cases, after an ungraceful shutdown, VidyoRoom SE fails to launch. 

If this occurs, uninstall VidyoRoom SE and then re-install it.

GS-2354 In order for an INOGENI device to work with VidyoRoom SE, the latest chipset drivers, USB 3.0 drivers, and INOGENI drivers must be installed.

After switching from side-by-side mode back to regular mode and restarting the system, a Windows® 10 upgrade notification message appears on top of the self-view and local projection. 

T his occurs because the cursor is disabled in regular mode; therefore, you must exit the VidyoRoom SE application to close the notification.

Occasionally, when a user launches an app, the app can be opened on the monitor which is already being used by VidyoRoom SE. 

If this occurs, drag the app window to the other monitor to prevent it from blocking VidyoRoom SE.
GS-1962 The option to change the VidyoRoom SE IP address is available on the Admin UI even though the VidyoRoom SE always inherits the computer’s IP address. If a user attempts to change the IP address via the Admin UI, the VidyoRoom SE will not save the changes.
GS-1498 If VidyoRoom SE is running on a Windows computer where Windows UAC is not disabled, and the user starts an upgrade but takes an hour or longer to respond to the Windows UAC pop-up that asks “Do you want to allow the following program from an Unknown publisher to make changes…”, the VidyoRoom application stops running.


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



Please sign in to leave a comment.