Ascentae Knowledge Base

Nureva HDL410 – Best Practice for Camera IntegrationDirect Integration Before installing a camera steering and switching solution to integrate with your Nureva audio solution, we recommend you refer to the below information and important links.You can find comprehensive instructions on installing and configuring a Nureva / camera solution on the Nureva Support site.This article gives guidance you may not find online, plus some Top Tips that we have picked up.Understand the customer requirementsNureva can support both camera steering (tracking/switching presets), and camera switching (changing to different cameras).It is important to have a view of the customers room, and understand which areas of the room need to be covered by a camera.  From this, you can determine the number of cameras required and the fields of view.If you have any queries about this, please contact Ascentae for advice.  We can even offer a full pre-installation consultancy service to help with this.Understand the limitations of the technology – HDL300 / HDL310         When integrating with a HDL300 or HDL310, you have a single sound bar – and so only one point of reference.  The information passed to the camera controller is based on the central point of the sound bar.  This makes it an ideal solution for azimuth presets, with a single camera mounted in line with the centre of the sound bar.Typically, up to 8 presets can be configured, each covering 22.5° of the room.The same is true if you have the legacy Dual HDL300 system.  The reference point for camera tracking will be the centre point of the primary sound bar (plugged into port 1 on the Connect Module).  The 2nd sound bar is not used for camera tracking).If using more than one camera, the best position for the cameras is either side of the sound bar, each covering half the room and using 4 presets.Understand the limitations of the technology – HDL300 / HDL310The HDL410 has 2 sound bars and when correctly positioned in the room, they can deliver accurate X,Y coordinate information to the camera controller.  Depending on the sophistication of the camera controller, it can interpret those coordinates in different ways.                Select appropriate camera and steer to coordinate location                Select appropriate camera and steer using presets                Select appropriate camera and switch to pre-defined zoneNote:  Not all camera controllers support all these modes.  Refer the camera vendor documentation for details.Camera zoning is covered in detail in a separate knowledge base article.Choosing the correct cameraNureva have created a suite of API calls which different camera providers have utilized to integrate with the Nureva devices.  Currently these are Aver and Lumens, plus drivers and sound tracking modules by Crestron and Extron.Typically, each camera vendor has created a software camera controller (in some instances it may be a hardware device).  Nureva confirm compatibility with the camera controller.  However, not all cameras from a specific vendor will be supported on the controller software.  It is the responsibility of the integrator to confirm compatibility of cameras and camera control solution.Make sure you check the focus length / zoom capabilities of the proposed camera.  If you are installing in a large room, the camera should be able to zoom and focus clearly on the furthest participant.Currently supported camera drivers are as follows.Note that camera switching is not supported by PTZApp 2 (single camera only)Note that camera switching is not supported by CamConnect Lite (single camera only)Cameras that support preset recall and have a Crestron module can support sound location data.Cameras that support preset recall and have an Extron driver can support sound location data.Positioning of the Nureva Sound BarsFor the HL300 / HDL310 remember that the camera reference point is the centre of the sound bar.The ideal position for the sound bar is above the screen – allowing sufficient clearance for the audio to be reflected off the wall into the microphones.It is important that there is no obstruction underneath the sound bar as this will degrade audio quality and cause inaccurate sound location data.To ensure best audio performance, measure how far your screen sits from the wall, and mount the sound bar so the bottom is 1.5 x this distance.E.g.  if you screen sits 10cm proud of the wall, the bottom of the sound bar should be 15cm from the top of the screen.Refer to the Microphone clearance requirements guide for more detailshttps://support.nureva.com/docs/installation-hdl300-microphone-clearance-requirements-and-recommendations-2We recommend that cameras are mounted underneath the screen where possible, but if underneath HDL sound bar, allow at least 6” (15cm) clearance from the top of the camera to the bottom of the sound bar.Available ResourcesSupported camera solution - https://support.nureva.com/docs/supported-integrations-for-camera-switching-and-tracking-1Aver Integration Instructions - https://support.nureva.com/docs/integrate-aver-cameras-with-camera-trackingLumens Integration Instructions - https://support.nureva.com/docs/how-to-integrate-with-lumens-ptz-camerasCrestron Module Instructions - https://support.nureva.com/docs/use-crestron-sound-tracking-moduleExtron Driver Instructions - https://support.nureva.com/docs/using-extron-sound-tracking-driverWatch out for reflectionsCameras are dumb and can easily be confused by reflections in windows.Be mindful of setting presets that can catch reflected images, or setting the camera to track in areas where windows will reflect if it’s dark outside.Ideally, curtains or blinds will not only avoid this issue, but have the additional benefit of reducing echo and reverberation in the room and so improve performance of the HDL device.If in doubt, ask AscentaeWe are here to help.  Please ask if you need any guidance, or would like to engage us to do a consultation on HDL and camera integration.

Nureva HDL410Best Practice for Camera Zoning Before installing a camera zoning solution to integrate with your Nureva audio solution, we recommend you refer to the below information and important links.You can find comprehensive instructions on installing and configuring a Nureva / camera solution on the Nureva Support site.This article gives guidance you may not find online, plus some Top Tips that we have picked up. Understand the customer requirementsWhen integrating the HDL410 for camera zoning, you can install up to 3 cameras covering different areas of the space.A typical use case may be a presenter / audience configuration, with a camera facing the front of the room for presentations and another 1 or 2 covering the audience.We also see this in use in larger meeting rooms where a single camera struggles to cover the entire room.If you have any queries about this, please contact Ascentae for advice.  We can even offer a full pre-installation consultancy service to help with this. Understand the limitations of the technologyThe HDL410 will deliver X,Y co-ordinates to an Inogeni Cam230 camera switcher, enabling it to switch to a camera relating to a specific zone in the room.It is then a function of the camera to Pan, Tilt and Zoom within that zone.  Additional camera software may be required to enable this.Zones cannot overlap – or be too close together – as this could result in the cameras switching incorrectly.Both the HDL410 and Inogeni CAM230 MUST be connected to a network and the HDL410 MUST have internet access and be enrolled in Console Cloud.Choosing the correct cameraThe Inogeni CAM230 allows up to 3 cameras to be integrated – 2 USB and 1 HDMI.  Alternatively, a 3rd USB camera can be supported using the Inogeni U-CAM convertor.This gives great flexibility and allows different types of camera to be used depending on the application.For example, a framing camera (such as Huddly L1) could be used to accurately frame a presenter as they move around the front of the room and a PTZ camera could be used for the audience.  A 3rd, static camera could be trained on a whiteboard to capture the content when someone is writing on the board.Positioning of the Nureva Sound BarsIt is strongly recommended that the 2 sound bars are mounted on opposite or adjacent walls to provide the most accurate sound location data. As with all installations of Nureva sound bars, ensure the sound bars are not mounted directly above a screen or other obstruction.We have found that any obstructions underneath the sound bar can cause problems with accurate sound location data, so ideally they should be mounted with nothing underneath them.  However, if this is not possible, refer to the Microphone clearance requirements guide for details on how to install.https://support.nureva.com/docs/installation-hdl300-microphone-clearance-requirements-and-recommendations-2   Creating camera zonesBe aware that unless your room is acoustically perfect, X, Y coordinates will always have a margin for error.Ideally, make your zones generous and leave at least 50cm gap between them.  If zones are too small, or too close together, in room echo can cause inaccuracies and cause the camera to switch unnecessarily.It is generally better to have the system revert to the default camera than to focus on the wrong person or continually switch cameras if someone is sat on the edge of 2 zones which are too close together.Watch out for reflectionsCameras are dumb and can easily be confused by reflections in windows.Be mindful of setting presets that can catch reflected images, or setting the camera to track in areas where windows will reflect if it’s dark outside.Ideally, curtains or blinds will not only avoid this issue, but have the additional benefit of reducing echo and reverberation in the room and so improve performance of the HDL device.If in doubt, Ask AscentaeWe are here to help.  Please ask if you need any guidance, or would like to engage us to do a consultation on HDL and camera integration.Available ResourcesInogeni Integration FAQ’s - https://support.nureva.com/docs/technical-faqs-hdl410-and-inogeni-cam230Inogeni Integration Guide - https://support.nureva.com/docs/integration-guide-hdl410-and-cam230

Supported DevicesIn order to get best performance from your Jupiter screen, it is important to use devices that are capable of supporting 21:9 resolutions.  The Jupiter screen natively supports 5120 x 2160 @ 60Hz (5K60).  Lower resolutions are supported and depending on the application can be displayed natively – with black borders – or stretched horizontally and vertically to fill the screen.  Refer to the Jupiter user manual for details.The following guidelines are based on testing by Jupiter.  They are not intended to provide a comprehensive list of supported devices.  Please check the specifications of the devices you intend to use.The Jupiter OPS module is designed to support Jupiter screens at full 5K60 resolution.PC’s with Graphical Processing Units (GPU)Older PC’s with onboard GPU’s over 3 years old will not support 5K resolution, but are likely to support a 4K variation of 21:9 aspect ratios – 3440 x 1440, 3840 x 1620, 2560 x 1080).Newer Intel models (less than 2 years old) support 4K60 and may support 5K30.Models with Nvidia GPU chipsets / software generally support software to create custom resolutions (including 5K60 21:9).Latest Intel models present no issues.Current Intel model computers with on-board GPU’s which support 5K+ monitors:i7 - 11th Generation Intel® Core™ i7 Processors, Processor Graphics, Intel Iris Xe Graphicsi5 - 11th Generation Intel® Core™ i5 Processors, Processor Graphics Intel UHD Graphics 750i3 - 12th Generation Intel® Core™ 13 Processors, Processor Graphics Intel UHD Graphics 730Separate GPU’sMost newer GPU’s cards should work.  Check the specification to ensure it supports 5KNVidea® software and hardware allows custom resolutions to be created should they not be supported by the OS.Apple® GPUsThe newer Apple M1 chip equipped machines have no issues driving 5K resolution monitorsCertain OS builds do not expose the 5120x2160 resolution, despite it being supported.  We recommend 3rd party software to set a custom resolution.Other AV Hardware (Extron, Crestron, TvOne, Brightsign etc)None of the AV hardware options we have tested currently support native 5K60 Support for MTR / Zoom Room systemsFront Row support on MTR’s is not dependent on support for 21:9 resolutions, and older generation MTR hardware will only support 16:9 resolutions.  If your MTR is older than 2 years, you may only be able to support 21:9 aspect at low resolutions (2560 x 1080).If you are attach a Jupiter screen to an existing MTR, please check the specification to ensure it will support 21:9 resolutions.Latest generation MTR systems should support 21:9.  We have tested the Lenovo ThinkSmart Core family which fully support 21:9 at 4K resolution.Zoom have recently added support for 21:9 to their latest software, but please check that your Zoom Room hardware is capable of supporting 21:9 resolutions.Supported CablesHDMI will not support 5K60.  Most systems connected via HDMI will support a maximum of 4K60.To get full 5K60 resolution, DisplayPort 1.4 or better is recommended.  Where possible, look for DP8K certification to ensure compatibility.USB Type C (Thunderbolt) is also supported for 5K60 and will also provide touch control without the need for a separate cable.  However, Thunderbolt cables can generally only be run a maximum of 5m without the requirement for signal boosting.  This is generally only recommended for very short cable runs.For longer cable runs, DisplayPort and separate USB-B cable for touch control is recommended.USB Device Pass ThroughThe Jupiter screen includes a USB hub, enabling you to attach USB-A peripherals and signal to pass via the screen to both the internal OPS and any attached PC (external PC connected via USB-C or USB-B).We have thoroughly tested this functionality with Lenovo ThinkSmart Core PC’s (MTR and OEM versions), Huddly cameras and Nureva audio products.

Huddly L1 – integration with Inogeni Cam230 We have identified an issue with integrating multiple Huddly L1 cameras with the Inogeni Cam230 camera switcher. SymptomsTypically, the Inogeni Cam230 keeps a USB signal active with all attached USB cameras.  However, the Huddly L1 camera uses 50% additional USB bandwidth.  The upshot is that when 2 Huddly L1 cameras are attached, the Inogeni Cam230 runs out of USB bandwidth and there is no USB signal to the non-active camera.Users may experience issues when switch sources between active / non-active cameras which include frozen image and very long delays between switches.ResolutionInogeni have issued a software patch which has been tested and shown to work in manual switch configurations and when switching is trigged via HDL410 zones.Currently, this software patch is available directly from Inogeni or through Ascentae support.Known limitationsThere is still a slight delay in the transition between active and non-active cameras, however, this is now below 1 second.How to Apply the FixSpeak to Ascentae support and we will guide you through the process.Future EnhancementThis fix will be included in the next version of Inogeni firmware update for the Cam230.  This is expected in April 2024.

By default NFC is not enabled on either the RoomPanel or RoomPanel Plus.Open a browser and load up https://IP_Address of the panel.User: adminPassword: 0000 Go to System > Device ManageEnter this code in the ‘Server URL’ field:M7:nfc.enable=1Select ‘Auto provision’Press ‘Confirm’ to save the changes.

The XDS-1588 and XDS-1588-A cannot exceed Android 7.1. The WRP-1000-A/H cannot  exceed Android 9. Please ensure camera capability before selecting your panel for visitor management if you will be taking a photo of the visitor or scanning QR codes.Last Updated:2nd of December 2025ModelGoBright App VersionAndroid OSCamera QR SupportAscentae approvedXDS-158812.24 to 14.157.1✔(2MP)✔✔XDS-1588-A12.24 to 14.157.1✔(2MP)✔✔WRP-1000-A/H13.28 to 14.159✔(8MP)✔✔WRP-1000-LN/A9❌❌❌WRP-1000-L V2N/AAndroid 12❌❌❌WRP-1000-A V2N/AAndroid 12✔ (8MP)✔✔WRP-1000-H V2N/AAndroid 12✔ (8MP)✔✔ RecommendationIf you are deploying new hardware, stick to the V2 (Android 12) to ensure security compliance (InfoSec). Android 9 is quite dated by modern enterprise standards.