Known defects

Known defects

The following is the list of known defect in the version 2.5.x releases. [1]

202602051611 Frame rate text overlay does not work in pro mode

To reproduce the error, go into settings , click on pro. Enable overlay notes. In the notes section, enter &f. Then set 3 different capture frame rates with durations set to non-zero values. Capture a video. Notice the frame rate text is XXXXXX.XX.

The problem exists because when we extended the camera with pro setting to capture at different frame rates, the overlay code logic was not updated. If this defect is causing you problems, let us know and we will bump up its priority.

202508221549 WebUI settings switch from pro to easy will resets to factory defaults

When the webUI settings modal is in pro mode a check is done before allowing the webUI settings modal to be switched to easy mode. During the check all features that are only available in pro mode has the selected value compared to the default value. A list of all settings that are set to a non-default value are shown in a confirmation dialog box with a message indicate only those settings will be changed. However, if the user confirms going to easy mode in this case, all settings are changed to the factory default values.

20231223103452 Overlaying text and graphics causes crash for very small image heights

If you set the vertical resolution to 96 and enable all overlays, the camera software crashes and requires a factory reset to recover.

20231005074253 Spurious Genlock Error reported when camera is properly genlocked

Occasionally a Genlock Error is incorrectly reported by the camera properly configured as a genlock receiver. The captured video is correct.

20220415111422 Setting the DNS server IP address via CAMAPI net_set_configuration() is broken

requested_dns_server and dns_server keys not handled properly in dictionary passed to net_set_configuration().

20190302135422 SC2 SC2+ SC2X pretrigger frame count inaccurate on when the pretrigger buffer is not full and a trigger occurs

If you trigger a SC2, SC2+, or SC2X camera before the pretrigger buffer fills, the metadata file will have an inaccurate number for the frames captured before the trigger event. This also effects review mode.

201604040552 Too many files in the DCIM directory cause huge delays

The VFAT file system used on the SD card is not well designed. The implementation in the Linux 2.6 kernel supporting VFAT is not optimized. Together, these two issues result in huge delays, more than 60 seconds in some cases, for the camera to be able to create a new file when saving a video. The camera can continue to operate, but other software, like the internal webserver, times out waiting for a response.

Work around: do not design your system to shave more than 200 movie files plus metadata files in any single VFAT dirctory.

This is defect #461 in Sanstreak's internal tracker.

201412161349 Multishot Genlock buffering can get out of sync due to power cycle or selective save

No fix defect -- there are no plans to fix this defect.

If you are in the middle of a Genlocked Multishot sequence and power cycle one of the cameras, the buffering will be out of sync once the camera is powered back on. Until the cameras configured for genlock talk to each other over the network cable, there is no way to resynchronize which multishot buffer is being used.

Work around: Power cycle all cameras that are configured and cabled for multishot and genlock.

Similarly, if you are in the middle of a Genlocked Multishot sequence and decide to save your video set, you cannot just press the save button on the genlock source camera's GUI since only the videos on the genlock source will be saved.

Work around: you must press the save button on the genlock source and all the receiver camera GUIs.

201409120935 Updating camera fails if there is a space ' ' character in the update tarball filename

If you download the update tarball more than once, some operating systems put a space in the file name (e.g. " (1)" so the file being downloaded will have a unique filename. If you use the file with the space in the filename, the update will fail. To work around the defect, remove the big SD card, delete the file with a space in the filename and store the original file on the big SD card. The camera will then update correctly.

201409091802 Cancel trigger at the end of capture misbehaves

No fix defect -- This is really not a defect.

On occasion, if you cancel the trigger just as the post trigger capture buffer is being filled, the camera will calibrate then save the video data instead of properly handling the cancel.

Work around: This is a race condition. The user thinks the camera is still capturing data when they press cancel, but in fact the camera has already switched to saving the captured video. Simply trim the video to get back to filling the pre-trigger buffer.

201408271324 Genlock false triggers

No fix defect -- there are no plans to fix this defect; the hardware design doesn't support any means to fix the issue.

This defect only occurs when using the Genlock feature with multiple cameras and a genlock cable.

Plugging in genlock cable may trigger both genlock source and receiver cameras. Unplugging genlock cable may trigger both genlock source and receiver cameras. Powering off a genlocked camera may trigger any other connected cameras.

Work around: connect all genlock cables before powering on the cameras.

201407242317 Save fails when save view is enabled

In heavy use cases when save view is enabled, the camera can stop saving views and needs to be power cycled or reset to recover. The cause of the documented defect is a library provided by the SoC vendor that can occur when both the JPEG and H.264 hardware encoders are used at the same time. We added the Save View On / Off setting as a way to work around this defect.

Work around: disable save view in the options menu

When the defect occcurs, it is common to see something similar to the following three lines in the log file.

CMEMK Error: get_phys: Unable to find phys addr for 0x43175004
CMEMK Error: get_phys: get_user_pages() failed: -14
CMEMK Error: GETPHYS: Failed to convert virtual 0x43175004 to physical.

This is defect #480 in Sanstreak's internal tracker.

201312111624 File timestamp is in GMT

No fix defect -- there are no plans to fix this defect.

The camera was intentionally designed to use GMT for the timezone when saving video files. Some might consider this a defect (issue #182).

As of 2.4.1 you can create your own filename pattern and not use seconds since 1970 in GMT timezone.

201312021613 Browser forward and back buttons may change camera settings

No fix defect -- there are no plans to fix this defect.

If you browse to another site and then use the browser back button to return to viewing the camera, your camera settings may have changed.

Work around: either don't browse to another web site or don't use the back button when you do; simply browse to the IP address of the camera.

201311041114 Playing last recorded video can fail in rare cases

No fix defect -- there are no plans to fix this defect.

The camera will automatically switch which storage device is used when the current storage device fills up and another, non-full, storage device is available. You can not play the video recorded right before the switch occurs since the active storage device has changed.

Work around: You can remove the storage device and properly play the video by retrieving the video file from the non-active storage device.

201311101454 CAMAPI does not detect new space on mounted storage device

No fix defect -- there are no plans to fix this defect.

CAMPI handles changes in storage status using an interrupt scheme (mdev). If your SD card is full and you telnet into the camera and delete some files, no event occurs, so CAMAPI doesn't detect there is now room and the memory full message is displayed.

Workaround: after deleting the files, remove and reinsert the storage device to create a change in storage status event.

[1] Naming convention for the 'Defect numbers' are in the format YYYYMMDDHHMMSS