Specifications

140

from the camera, which may not be desirable if either CPU cycles or video display

capability is nearing physical limits. Note that all frames continue to be internally

processed and recorded as configured.

• Serial port Pelco-D and Pelco-P protocols are now supported from the camera PTZ (See

7.9) page.

• New DDE commands: "schedule=1 or 0" to enable/disable the schedule for a camera,

and "profile=x" to override the active Motion Sensor

(See 7.3) profile for a camera. If

x=0, the camera is inactive (no recording or alerts at all). Use x=1 for the default Motion

Sensor profile. The schedule is automatically disabled if you send the profile=x

command.

• If you specify the Motion Sensor option to "Restore window when triggered," Blue Iris

will also "wake" your monitor if it's in power-saving mode.

2.44

• Specify the camera number 0-3 in the Parameters box when adding multiple Aviosys

9100/a/b cameras and set the device for round-robin. Images will be automatically

routed to the correct Blue Iris camera.

• It is now possible to use the Sound alert (See 7.5) while running as a service.

• When using remote desktop the camera image is updated once each 10 seconds instead

of displaying the message "Remote terminal session detected." You may still use a

checkbox on the Options/Startup page to override this and display video as quickly as

possible.

2.43.02

• Fix for PTZ double-clicking on all remote pages and the ActiveX control. It was possible

to get the camera to continue moving to its pan/tilt limits by double or triple-clicking the

PTZ buttons on the remote pages. For cameras which have separate motor start/stop

commands, you may now hold down the PTZ buttons to move longer distances.

2.43

• The install now includes an XCastInstall.exe which should be used to install and update

the ActiveX control. Too many systems are blocking the automatic download and

installation of the Blue Iris ActiveX control. A link has been placed on the default.htm

page.

• PTZ cameras with separate button-down and button-up events (for variable duration

movement) are now better supported in the main UI, the ActiveX component, as well as

the Java and JPEG web pages.