Camera setup
To record the camera set Enable recording to yes. Set Days to keep to however old you want a recording from this camera to be before it is deleted.

Encrypt depth applies to what is written to the (generally) local drive. This does not apply to network encryption between the CAMNET server and its client. Recording encryption lets you encrypt some or all of the recorded frames (or none). The recording's meta-data is not encrypted. The meta-data includes the index to frames, the event records, end-frame markers, and information about the format of the recording[1].

What can be encrypted is the frame data. The default (which is the same as entering 1) encrypts the first 256 bytes of each frame. This is enough to make most frames unreadable. Values of none, maximum, and from 1 to 254 can be used. Each unit encrypts an additional 256 bytes of each frame. Maximum encrypts the entire frame. The frame encryption is done on a per-frame basis: you can change the encrypt depth while recording, and the change will apply to all frames recorded after that.

As with nearly all Cam setup changes, the change is not enacted by CAMNET server until you press the Refresh camera button in the Test-Join panel. Doing that reloads the cam.cfg, the file that stores this camera's configuration data. Doing this also disconnects then reconnects the server-camera connection. The same recording file is used, taking up right where it left off. As mentioned in the Cam setup, ID panel of this guide, if the video or audio format changed, a new recording is automatically started.

If you don't care to encrypt the recording file, use none.

[ camnet camsetup, record ]
The Recording base file path by default locates this camera's recordings to CAMNET server's base directory, for instance:
and then the server's service (-name) directory, and camera's directory, year, month, and day:
and the recording file is, for this example, 20150501.CNS. See the Cam setup, ID panel in this guide for more on the recording file name and how the extension can change on detected A/V format changes.

The Recording base file path lets you specify where the first part of the path is to be, the c:\camnet part. For example, if you want to record to a network share[2] you could specify something like:

where now, this camera's recording would be at, for this particular day:

When recording by event notification (see the Schedule panel), where recording is performed only when the camera has generated an event, or a trigger was otherwise handled, a way to describe how much should be recorded is needed. That is done by the Pre-event seconds and Expire event seconds fields. Pre-event seconds describes for how many seconds before the event was received that the recording is to include, and Expire event seconds for how long to continue recording after the event was received. These values apply only if the Cam setup, Schedule, b) how to record value is 3 (write event only) or 4 (write event plus min).

 Pre-event seconds can be from 0.0 to 10.0 seconds (at least 2x the I-frame interval).
 Expire event seconds must be 14.0 seconds or greater.

The pre-event staging buffer requires at least one I-frame to start the staging, and must throw away an entire GOP if the I-frame has to be discarded for new space. For best results all-around when using CAMNET server, set all cameras' GOP/I-frame interval to be 1 second. If a camera does not specify this interval in seconds, set it to the value that results in 1 second between I-frames (longer intervals are not desired; shorter than 1 second will do but results in streams that are less compact). As an example, if the camera runs 30 FPS, set the I-frame interval to every 30 frames (one I-frame followed by 29 delta frames). This applies to MPEG4/2 and H.264 streams, where ideally the Pre-event seconds is set to at least 5.0 seconds. JPEG streams are effectively all I-frames, so the pre-event staging buffer is always well-filled.

The Trigger group by default is the same as the service name (camnetserver, unless the service was started using -name with another service name). All cameras, therefore, share the same trigger group and so all cameras automatically get a T(rigger)event notification when any other camera gets a real event notification. To have a camera not receive the T event notification automatically, set the Trigger group to a unique value (e.g., noTforCam_m1031). Using an external, HTTP /trigger=all event will trigger even those uniquely-named trigger group cameras.

[1] The included cnsdump.exe file inspector can show what is in a recording file (encryption reduces this information)
[2] The account under which the CAMNET server is running must have R/W permission for the share