NoldusViso – Test your setup
Last updated: Nov 09, 2026
Testing your setup before recording prevents lost recordings. A quick test lets you confirm: cameras are available, PTZ (pan-tilt-zoom) settings are correct, the right audio sources are selected, the needed annotation presets (subjects, tasks, events) are available, you have access to the scenario and its devices, and the physical room is available.
- Skipping this step risks discovering a problem — a missing feed, wrong preset, no audio — only after a real session has already started.
Prerequisites
- Devices must already be configured — see Manage devices.
- At least one scenario must already be created — see Create and configure scenarios or How to Use Templates.
- Your role must allow starting recordings: Administrator or Researcher/Trainer — see User Accounts and Roles.
1. Open or create a scenario
Open the Scenarios page and click the scenario you want to test, or create a new one — see Create and configure scenarios.

2. Check the camera feeds
Confirm the camera feeds you expect are available and visible in the scenario.

3. Check PTZ settings and audio equipment
Check the PTZ settings for each camera: hover over a camera tile, and on a camera that supports PTZ a PTZ controls button appears. Then confirm the required audio equipment is selected: the microphone tile shows a level meter that moves while the microphone picks up sound.


4. Check availability in the scheduler
Check in the scheduler whether the scenario and its devices are available at the time you need them. The Sessions view lists the sessions planned on a day, and the Devices view shows which devices are already booked, hour by hour.


If necessary, schedule a session for your test to prevent others from claiming the same resources — see Schedule sessions.
5. Make a short test recording
Record a short test session. Check the audio/video quality, and whether the defined subjects, tasks, and events fit what you'll actually be observing.

6. Adjust and save the scenario
Make any necessary changes to the scenario, then save it as a new scenario or save it under your own name.

Note: Once a setup has proven to work reliably for your research needs, you don't need to repeat every check before each recording. A fixed testing interval is a good baseline; re-test whenever any part of the scenario or setup changes.