CAMNET
Errata
Updates, fixes, and known problems
Current version
2015.10.17


Known problem: As of Windows 10 v10.0.17134 (update 1803) CAMNET SERVICE MANAGER no longer fast-forwards faster than the Trickplay speed (3x for h264; 2x for mpeg4pt2); instead play appears to freeze. No errors are reported, so no fix is possible in the near term (unless Microsoft fixes what was broken). Stay on 1709 or prior if you need to fast-fwd faster than 3x.


v1.0.5

Known problem: CAMNET server would override install settings when restarted manually

15-Oct-2015
Description

Manually stopping then restarting the CAMNET service would override the
install settings, such as -port, with default values since all settings
but -name are ignored (and should be) when not doing an install.
Work arounds: Instead of -service stop then -service start, do a -service remove (-name x) and -service install (required settings). -console mode was not affected.

Fix: Completed

Update: Download the current .MSI package to get the updated server. Also added a connection log. This works like the event log, where each month starts a new log. It is named yyyymm00_connectlog.txt, and is found in the service-name directory (e.g., c:\camnet\camnetserver\20151000_connectlog.txt).


Known problem: Transcoder sets GOP length to initial FPS indication

7-Oct-2015
Description

Transcoding would produce a stream with the GOP length (the number of video frames
between I-frames) set to the FPS as indicated when starting the stream.  The FPS
indication may have come from the camera's SDP, and that FPS may be incorrect;
some cameras will indicate 30 FPS when the actual rate is much lower, or one that
varies with conditions.  The transcoder now monitors the true FPS and updates the
GOP length of the transcoded stream to match the FPS.  Also, the software transcoder
would not resize when the resulting transcoded height was an odd value; the only
common stream size where this would happen is 1920 by 1080, when the transcode resize
was set to 1/8th (1080/8 is odd).
Work arounds: None.

Fix: Completed

Update: Download the current .MSI package to get the updated server.


Known problem: Recording could drop to a STOP RECORDING state (see System, Schedule panel) after a varying amout of computer uptime

3-Oct-2015
Description

An internal tracking value was not initialized and could result in recordings going to a
"Stop recording" state, which is the same as doing a Stop recording Now at the System, Schedule
panel.  This has not been reported in a release build but it was seen in test builds.
Work arounds: The simplest is to do a Stop recording (System, Schedule panel) manually: set to 1 minute and press Now. This sets the internal tracking value. This corrects the problem, but must be done again if you restart CAMNET server (server, not client).

Fix: Completed

Update: Download the current .MSI package to get the updated server.


Known problem: Camera auto-restart may not auto-restart the camera stream

28-Sep-2015
Description

A camera that was already streaming and then went offline, may not automatically
restart. This was due to a race between starting a new stream to the camera and the
closing of the old stream, where the new stream would win the race but then be closed.
Work arounds: Manually restart the camera from Camnet Service Manager: use Refresh camera at Cam setup, Test-Join panel, or if that does not restart the camera (it should), at Cam setup, ID, set Button text to REMOVE (then Accept/Save), after which, restore the camera by selecting it from the Name menu list (Accept/Save, then Test-Join).

Fix: Completed

Update: Download the current .MSI package to get the updated server.


Known problem: Selecting the T (inverse) DI filter causes other DI events to not be displayed

20-Sept-2015
Description

At the Recording panel, with Show events active, selecting DI filter 'T'
(to filter out is-only-trigger events) causes other DI events to not
be displayed unless that event record also had a motion detect (MD) hit, or if
it did have a 'T' hit.  For examle, with the T (inverse) filter active,
an 'x' event would be not be displayed if there were no MD hits and no 'T' hit.
Work arounds: Don't use a T filter when DI events need to always be seen.

Fix: Completed

Update: Download the current .MSI package to get the updated client.


Known problem: Mute not working in 5.1 speaker configuration mode with headphones connected

2-Sept-2015
Description

This is likely caused by the soundcard driver not switching speaker configuration mode
when headphones are in use.
Work arounds: Try an alternate speaker configuration

Fix: Use the system mixer panel to mute audio (this affects all streams instead of the single stream)

Update: None


Known problem: Pre-supplied Hik macros not acting

2-Sept-2015
Description

It is possible that Hikvision macros as supplied in the Hik campax DLL
are not doing any action.
Work arounds: None required

Fix: (Some) Hikvision cameras require digest authentication for all actions (except for streaming where basic authentication is all that is required). To get macros to work, change the Cam setup, Access panel, Camera authentication field, to digest. After making that change, refresh the camera configuration at the Test-Join panel. To test this, at Live video, press the Macros button. In the daytime, select "Ir cut night" and Send it. The camera switches to black-and-white. At night, select and send "Ir cut day". This turns off the LEDs. Send "Ir cut night" or "Ir cut [auto]" to turn the LEDs on.

Update: None required, however, the Super-Quick Start Guide was updated at Section II, subsection E, item 5: "Set the Camera authentication to digest" since the QSG uses Hikvision as the example camera make


Known problem: Onvif Probe panel may return no cameras (rc= 232)

21-July-2015
Description

The System, Onvif probe uses the first returned network adapter address
for the probe (in Win7 the same as used by INADRR_ANY for this system
call), but the first adapter may be a virtual internal network.  Additionally,
Onvif event notices would be sent to this virtual address and be lost.
Work arounds: The Camera setup, Onvif panel defaults to what is typically the correct Xaddr so the System, Onvif probe panel is more for interest than for need. Use the default Xaddr at Cam setup, Onvif. Using the optional -addr camnetserver cmd line switch lets you set the address for camera and event listeners, overriding the 169.254.* IP address, but this override was not being used for the Onvif probe.

Fix: Completed

Update: Download the current .MSI package to get the updated server.

v1.0.5


v1.0.4

Known problem: Directories created for recording files are not removed when empty

19-July-2015
Description

When the Purge task has removed all recordings from a directory, the containing
directory for that day is not removed.  Similarly, for the month directory containing
the daily directories, and the year directory containing the month directories, when
each of those becomes empty.
Work arounds: You can delete the empty directories, but since the disk space used is negligible - it cannot even be measured - it is better to get the update.

Fix: Completed

Update: Download the current .MSI package to get the updated server. Also fixed Early purge GB which was ignoring values > 50 (500GB is the correct max early purge GB value); the once-daily purge could start one second too early in which case it would reschedule immediately for another purge, which would cause the next once-daily purge to not be set up unless either of the early pct/GB values were non-zero (this caused the purge task to not run) - workaround was to use a non-zero early purge value, or do a NOW purge.

v1.0.4


v1.0.3

Known problem: Recording panel's specific Include types .f## and .e## are ignored

15-July-2015
Description

Selecting Include types of either .f## or .e## is ignored.
Work arounds: None

Fix: Completed

Update: Download the current .MSI package to get the updated server and client. Also changed how the server-camera connection time is displayed in the Live video stats panel: it was always shown as hours:min:sec and is now shown as days:hours:mins after 24 hours; Also changed in the stats panels is the Frame in MB value, which now switches to whole values after 10 MB; Also fixed transcoding MPEG-4/part2 straight to H.264 - it was being ignored if not also resized or rotated.

v1.0.3


v1.0.2

Known problem: Changing camera audio to not enabled does not start a new recording

13-July-2015
Description

Changing audio in Cam setup to no longer be enabled, once it had already been enabled and
recorded, does not start a new recording.
Work arounds:
Before disabling audio at Cam setup (Access panel), force a recognized-format-change at the camera (select a different video resolution) and Refresh at Test-Join panel. This starts a new recording file. Then disable audio (and Refresh). Also possible is to "remove" the camera, manually rename the current recording file (to *.f01, for example), then add the camera back. Even if nothing is done, the recording will play, though without the expected audio track.

Fix: None at this time.


Known problem: Snapstream may generate an invalid mp4 file

13-June-2015
Description

A camera that sends an SDP without an FPS indication (any non-zero FPS will
do) results in an unplayable snapstream .mp4 file.  An export of a recording
does generate a valid .mp4 file for these cameras.
Work arounds:
Create a snapstream (or export) of the period from the recording file

Fix: Completed

Update: Download the current .MSI package to get the updated server and client. Also fixes mjpeg stream segment time where known-and-handled-mjpeg cameras could return frames without a valid seconds-since-epoch value (after a power-cycle), which caused frame times to appear to be as many seconds in the future as it is from 1-Jan-1970 [play would start but immediately end]; Recording panel fields for Include-types (default is now "all") and From-last are now saved to scp_L.txt [when the client-side System settings are saved]; Clients streaming from a camera that had stopped sending before a disconnect are now recognized and removed by CAMNET server [such client connections would be zombied, and seen in the System, Connections, Clients list, until CAMNET server was restarted]; If the designated recording file could not be used (locked by another process, or marked read-only), a new recording file for the day is created, using the next available .e## name, such as 20150613.e01 [before, recording would not resume again for that camera until midnight]; Ignore audio for expanded slo-mo/fast-fwd, when set to yes with audio present, was not playing the recording.

v1.0.2


v1.0.1

Known problem: Frame rate jumps to 62.5 FPS

5-June-2015
Description

Some (all RTP) camera streams from CAMNET server (and their recordings) will
eventually have their indicated frame rate jump to 62.5 FPS (a limit-check
value internal to CAMNET server).  Playback is then performed at the indicated
62.5 FPS.
Work arounds:
Refresh the camera at Test-Join

Fix: Completed

Update: Download the current .MSI package to get the updated server and client Also fixes midnight crossing going to 24:00+ at the client; Camera restarts get into the event viewer; /trigger= can now include the query symbol: /?trigger=).


Known problem: Very slow playback rate at the client
5-June-2015
Description

Cameras with GOP/i-frame intervals far greater than 1 second can cause Media Foundation
(the presentation system used by Camnet Service Manager) to starve for audio/video; the
pre-roll time value for these cases is showing 0 frames in Q and 0.00 time in Q, or a 
much lower value than set.  This will affect all showing views (in peel off windows) until
those views with the affected streams are closed.
Work arounds:
Set the GOP/i-frame interval at the camera to be 1 second (ideally), or 2 seconds at the most. Alternatively, increase the pre-roll time as needed.

Fix: None. Working as designed. Set the i-frame interval to be 1 second, or at most no more than 2 seconds. If a camera slows its frame rate at night, be sure the GOP/i-frame interval matches the reduced frame rate. An FPS of 5 and a GOP interval of 60 is not good. This is 12 seconds per GOP.