Template:Software release version 2.3.1

From edgertronic high speed video camera
Jump to: navigation, search

Version 2.3.1

Update file

Copy the v2.3.1g1 update tarball file to the big SD card, power on the camera, and wait around 7 minutes for the camera to finish updating.

Version details

Build host: contra-lx
Built by: tfischer
Build date: 20190104111207
Build tag: ssc1
Build hash: 8a7b030
Build version: v2.3.1-g1

Release Notes

Improvements since software release version 2.2.2:

  • Gamma correction can be set to sRGB or OFF (linear).
  • Some of the video configuration parameters can be modified during review. Parameters that can be changed include ISO, force monochrome, gamma correction, video encode quality, overlay notes and information, and the file name.
  • Added saved video counter so user supplied filenames can have an incrementing number. Video saved count is included in metadata file and can be included in the notes field.
  • Added shortened form of camera model string so user supplied filenames can include camera information and in the notes field.
  • Allow user to specify the subdirectory to use when saving videos by including directories in the user supplied filename.
  • Avoid overwriting files by appending a number to video and metadata filenames if the current filename would cause a file to be overwritten.

Resolved defects

  • 20180410101223 Return default values do not include the default frame rate

Added the default frame rate to dictionary returned by CAMAPI configure_camera(None).

SDK API changes

  • User specified filename with pattern substitution added to CAMAPI configure_camera(), run(), and selective_save() methods.
  • Added CAMAPI configure_save() to allow some of the video parameters to be modified before selective_save() is invoked.
  • Added requested_gamma_correction support to dictionary passed to CAMAPI configure_camera() and run() methods.

Developer changes

  • New CamApi Windows .NET library available to make it easy to integrate the camera into Windows based solutions.
  • Cleaned up how the multicast trigger daemon is started to improve reliability.
  • Added calibration temperature information to metadata file to help diagnose image quality issues if too much time elapses between last calibration and current camera conditions.
  • Algorithm used to calculate the get_camstatus() config_changes value should now be unique across multiple cameras and across power cycles.
  • Better parameter validation for the dictionaries passed to CAMAPI configure_camera() and run() methods.
  • Support for user added camera code to control a USB-serial connected device such as a battery pack.

Known defects

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

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.

201607011045 Power on camera with USB storage may cause camera to not properly detect available storage

If you have a USB flash thumb drive or USB hard disk connected directly to the camera and turn the camera on, depending on the USB device, the available storage will not be detected.

Work around: There are several work arounds -

  • Use a powered USB hub between the storage device and the camera
  • Remove the USB storage device before powering on the camera
  • Remove and reinsert the USB storage device after the camera has powered on

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 Master camera's GUI since only the videos on the master will be saved.

Work around: you must press the save button on the master and all the slave camera GUIs.

201409120935 Updating camera fails if there is a space 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 master and slave cameras. Unplugging genlock cable may trigger both master and slave cameras. Powering off a genlocked camera may trigger any other connected cameras.

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

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