
RC-E User Manual
Management Client (RC-E Manager)
The Presets tab (see "PTZ Tab (Hardware Properties)" on page 102) for managing the selected camera's preset
positions (only available if the selected camera is a PTZ camera).
The Patrolling tab (see "PTZ Patrolling Tab (Camera Properties)" on page 80) for managing the selected
camera's patrolling profiles (only available if the selected camera is a PTZ camera).
The Events tab (see "Events Tab Overview" on page 99) for managing hardware configurable events.
The Client tab (see "Client Tab (Camera Properties)" on page 76) lets you specify information which will affect
client's use of the selected camera.
The Privacy Mask tab (see "Privacy Mask Tab (Camera Properties)" on page 79) lets you enable and configure
privacy masking for the selected camera.
The Motion tab (see "Motion Tab (Camera Properties)" on page 77) for managing the selected camera's motion
detection settings.
Client Tab (Camera Properties)
The
Client
tab lets you specify information which will affect clients' use of the selected camera. To access the
Client
tab, select the required camera in the overview pane (see "Panes Overview" on page 36), then select the
Client
tab in
the properties pane (see "Panes Overview" on page 36).
Client Settings
Live multicast:
RC-E supports multicasting (see "Manage Multicasting" on page 70) (sending of single data
packets to multiple recipients within a group, thereby saving bandwidth and system resources) of live streams
from recording servers to Ocularis Client s. To enable multicasting of live streams from the selected camera,
select the check box.
Remember that for the feature to work, multicasting must also be configured for the recording server; see
Manage Multicasting (on page 70). If multicasting is not possible, for example due to restrictions on the
network or on individual clients, RC-E will revert to unicasting (sending of separate data packets to separates
recipients).
Default microphone:
By defining a default microphone, you can determine from which microphone Ocularis
Client users should by default hear recordings when they select the camera in question in their Ocularis Client s.
The users can subsequently select another microphone if they require so
.
Bear in mind that although you have defined a default microphone for a camera, it cannot be guaranteed that
all Ocularis Client users will hear audio from the microphone in question: Some users may not have speakers
attached, some users may not have the rights required to listen to audio, etc.
Default Speaker:
By defining a default speaker, you can determine through which microphone Ocularis Client
users should by default be able to speak when they select the camera in question in their Ocularis Client s. The
users can subsequently select another speaker if they require so.
Bear in mind that although you have defined a default speaker for a camera, it cannot be guaranteed that all
Ocularis Client users will be able to talk through the speaker in question: Some users may not have a
microphone attached, some users may not have the rights required to talk through speakers, etc.
Shortcut
: Users of the Ocularis Client can take advantage of a range of keyboard shortcuts, some of which let
the users toggle between viewing different cameras. Such shortcuts include numbers, which are used to identify
each camera. In the Management Client, each camera's shortcut number is specified in the
Shortcut
field.
A camera shortcut number must not contain any letters or special characters, and cannot be longer than four
digits. Examples of correct camera shortcut numbers:
3
,
1234
. Examples of incorrect camera shortcut
numbers:
A*3
,
12345
. Always use a unique camera shortcut number for each camera.
On-Net Surveillance Systems, Inc.
76