Scandit Data Capture SDK 6.5 Release Notes (October 1st 2020)#

See also the System Requirements of the Scandit Data Capture SDK across all platforms.

New Features#

Performance Improvements#

  • Improved the way frames are scheduled to be processsed by the data capture context. In some circumstances, this improves the frame rate by around 40%.

  • Significantly improved the recognition of 1D barcodes in single and low-resolution use-cases (especially of Code128 and EAN13).

  • Improved MatrixScan performance in selected use cases (Shelf Management, Inventory Audit, Receiving…), please use the new BarcodeTrackingSettings.Create() to get the latests advances. You can see this being done in our MatrixScan Bubbles Sample that is distributed with the Scandit Data Capture SDK.

Bug Fixes#

  • TextCapture now works with camera API 2.

  • Fixed the camera lag of the Algiz RT8.

  • Fixed a crash for barcodes that contain no data.

  • It is no longer possible to add a listener multiple times (and then have to remove it multiple times).

Deprecations#

Updates#

Scandit Data Capture SDK 6.5.1 Bug Fixes (October 21st 2020)#

  • Fixed decoding of MicroQR symbols with an abbreviated terminator.

  • Increased the maximum configurable Code39 symbol count from 40 to 50.

  • DLID parser: Some states can provide dates in two different formats: YYYYMMDD and MMDDYYYY. The parser handles both cases now.

  • DLID parser: Fixed parsing the expiration date for some Arizona codes.

  • DLID parser: Fixed parsing the issuer field for North Carolina and Arizona states as well as Newfounland and Labrador province.

  • HIBC parser: Fixed the issue that parsing secondary data with an additional lot field immidiately after 5-digit Julian date were treated as an error.

Scandit Data Capture SDK 6.5.2 Bug Fixes (October 22nd 2020)#

Contains no bug fixes for this platform.

Scandit Data Capture SDK 6.5.3 Bug Fixes (November 5th 2020)#

  • Fixed a PDF417 scanning performance regressions introduced in 6.5.0.

  • Fixed a bug in BarcodeTrackingSettings.Create() causing a sub-optimal performance in certain cases.