Release Notes

DMSDK 3.7.4- 05/24

Changes:

• SDK
• There were updates on maintenance and stability improvements

DMSDK 3.7.3- 04/24

Changes:

• SDK
• There were updates on maintenance and stability improvements

DMSDK 3.7.2- 02/24

Changes:

• SDK
• There were fixes of several memory leaks

DMSDK 3.7.1- 10/23

Changes:

• SDK
• There were updates on maintenance and stability improvements

DMSDK 3.7 - 9/23

Changes:

• SDK
• There were updates on maintenance and stability improvements
• Set minimal Android API level to 24 (Android 7.0)

DMSDK 3.6 - 8/22

Changes:

• SDK
• The SDK library is now available as a Maven package. See the Getting Started guide for configuration details.
• Added payload representations for Print, Audio, and Recycling digital watermarks.
• Added getData() method to the Payload class. The method allows applications to more easily interpret and consume digital watermark data.
• Added support for showing barcode and watermark detection locations to DMSDetectorView.
• Barcode reader now reads at a fixed rate of every third frame.
• Fixed camera error on some devices caused by using an autofocus region near/equal to the size of the full camera preview FOV.
• Removed ACCESS_NETWORK_STATE permission from the SDK manifest.
• Camera
• Deprecated CameraHelper.setFocusRegion(). Metering regions near/equal to the size of the full preview FOV can cause unpredictable behavior on some handsets, depending on the OEM. Developers are encouraged to use CameraHelper.setFocusPoint instead.

DMSDK 3.5 - 4/22

Changes:

• SDK
• Now supports detection and resolving of Package ID data for recycling applications. This feature may be enabled with the existing EnablePlasticsReading reader option for applications that need to support recycling scenarios.
• Deprecated ImageReader.setImageDetectionRegion(RectF) and VideoCaptureReader.setImageDetectionRegion(RectF) methods. Those methods may not behave correctly if used with a display rotation beyond the device's natural orientation or if frames are being delivered from a source other than CameraHelper. Apps that need to restrict the detection area should use the new setImageDetectionRegion(DetectionRegion) method.
• DMSDetectorView changes for screen overlays.
• Added new API setOverlayType(). The options available are Crosshairs, Detect Region or None, with Crosshairs being the default.
• The setImageDetectionRegion() method now sets the camera focus region to match the detection region.
• Calling setImageDetectionRegion() will update the location of the screen overlay if one is enabled. The Crosshairs will be moved to the center of the detection region. The Detect Region will be sized to match the region bounds.
• Deprecated setShowAimingView() and showDetectRegion(). The new setOverlayType() API should be used instead.
• Deprecated setAimingView().
• The DMStockTake app now includes a demonstration of image detection regions. A button on the toolbar cycles through several region options and a new RegionView class in the app highlights the current region.
• Updated the AR Integration Guide based on latest version of ARCore (v1.30). The previous version of this guide was based on Google's Sceneform library, which is no longer maintained by Google. Note that the Sceneform-based sample app that accompanied this guide, DMSArDemo, was removed in DMSDK 3.3.
• Camera
• Improved support for device rotation.
• Added support for setting the focus to either a point on the screen or a region. Note that these APIs are only functional on devices that support Camera2 Limited or higher.
• Fixed a bug that could cause a reconfigure cycle when starting the camera. This fix improves camera startup time by 30-250 ms depending on the device.
• Fixed a bug that could cause camera disconnect errors when switching views.
• Improved support for multiple camera views.
• Added setCameraSurfaceView() method to CameraHelper.Builder. Apps that need multiple camera views should use this to direct camera data to the appropriate CameraHelper instance. No action is required for apps based on DMSDetectorView, as it uses this API internally.
• Deprecated CameraHelper.startPreview() and CameraHelper.stopPreview() methods.

DMSDK 3.4.2 - 9/21

Changes:

• SDK
• Added feature to distinguish between Code 128 and GS1-128 symbols. When reading a GS1-128 barcode the Code_128 representation value will begin with a FNC1 character. GS1-128 data is also accessible as GS1 AIs using the GS1_List and GS1_Formatted_List representations as well as the Payload class getGS1Data() method.
• Fixed a crash that could occur when reading a QR Code containing a malformed URL.

DMSDK 3.4.1 - 8/21

Changes:

• SDK
• Fixed a rare crash on audio shutdown.
• Camera
• Camera errors from DMSDetectorView now include the camera error description.
• Fixed several rare camera exceptions.

DMSDK 3.4 - 7/21

Changes:

• SDK
• Added EnablePlasticsReading to ReaderOptions. This option allows apps to read Digimarc Barcodes that are molded into plastic.
• Added detection support for advanced Digimarc binary pattern.
• Added detection support for new types of Digimarc user data.
• Updated methods for SDK licensing information.
• Fixed a crash in DMSDetectorView that would occur when calling setHelpPromptText() with an empty list of IDs.
• Fixed a bug that could change QRCode read performance when setting an image detection region.
• Added code to the DetectorViewDemo sample app for setting a read region. The code is commented out by default. Refer to the enableImageDetectionRegion() method in Views.kt for more information.

DMSDK 3.3 - 3/21

Changes:

• SDK
• Reduced size of SDK native binaries. Applications built with the SDK will be 2 MB smaller.
• Added the ability to set minimum ITF Variable code length. By default 10 digits is the minimum ITF Variable code read. The option allows a minimum code length down to 8 digits.
• Added getResolution() method to DMSDetectorView which returns the configured camera resolution for the current session.
• Fixed bug in DMSDetectorView that prevented detect region overlay from drawing properly after the detection region was changed.
• Fixed bug that could cause the wrong 1D barcode type to be reported when multiple barcodes of different types were detected in the same frame.
• Fixed a crash that could occur on the Samsung Tab A7.
• Fixed an issue that could cause a FileNotFoundException on first launch.

DMSDK 3.2.1 - 1/21

Changes:

• SDK
• Fixed an issue in DMSDetectorView where the aiming view would be visible when calling start() after setShowAimingView(false).
• Fixed excessive memory consumption caused by microphone animation in DMSDemo and DMSDetectorView.
• Added a release() method to DMSDetectorView. This method is intended for use in an application's onDestroy() method. This method and the CameraHelper release() method mentioned below are intended to clean up any lingering camera objects to avoid object leaks on shutdown.
• Camera
• Added a release() method to CameraHelper. This method is intended for use in an application's onDestroy() method to clean up any lingering camera objects.

DMSDK 3.2 - 12/20

Changes:

• SDK
• Major improvements for 1D barcode performance.
• New near and far modes allow for reading up to 40 simultaneous UPC-A/EAN-13 barcodes.
• Significant efficiency gains for better battery use.
• New DMStockTake sample app: This app demonstrates the use of the SDK's 1D barcode reading features for inventory restocking scenarios. Stock Take reads multiple UPC/EAN and ITF-14 barcodes from far distances. Settings in the app allow you to switch between near, far, and full-range distances. It also includes an implementation for results smoothing for maintaining a smooth stream of read results. Refer to the file ReaderResultCache.java for more information
• Minimum supported Android version is now 5.0 (API 21).
• Improved reading reliability for inverted QR codes.
• Added a method for setting the license key in DMSDetectorView.
• Added a metadata entry DistanceFromCenter to the DataDictionary. It is intended as a tool to help determine which results are most important.
• Added a method to get the image frame size to ReaderResult.
• Added a new DMSDetectorView attribute: showAimingView. This can be used to prevent the aiming view from being inflated and added to DMSDetectorView's layout.
• Fixed a bug where the aiming view could be shown when stopping DMSDetectorView with setShowAimingView(false).
• Fixed memory leaks in DMSDetectorView.
• Fixed problems with the SDK's Proguard configuration. The SDK rules will no longer interfere with application rules.
• Camera
• Added CameraHelper methods for registering a CameraNotifyListener, CameraConfigurationListener, and CameraRegionListener.
• Fixed a resource leak caused by CameraSurfaceView not releasing its Surface.

DMSDK 3.1.3 - 9/20

Changes:

• SDK
• Fixed a bug in DMSDetectorView that prevented PDF417 barcodes from reading.
• Camera
• Fixed a crash that could occur on the emulator.

DMSDK 3.1.2 - 8/20

Changes:

• SDK
• Fixed a bug in the Payload equals() method.
• Camera
• Fixed a crash on the Samsung A71 5G.
• Fixed a bug that could cause a black camera view after bringing an app to the foreground.

DMSDK 3.1.1 - 7/20

Changes:

• SDK
• Improved detection of PDF417 barcodes.
• Fixed a crash that could occur with PDF417 barcode scanning enabled.
• Camera
• Fixed a bug in the CameraSurfaceView where rapidly loading and unloading the view could cause the camera to stop capturing.

DMSDK 3.1 - 4/20

Changes:

• SDK
• NEW! Added support for PDF417 barcodes.
• Fixed a bug in the CameraSurfaceView where unloading and reloading the view rapidly could cause the camera to stop capturing. This could occur when quickly switching back and forth between tabs in an activity.
• Camera
• Added a new interface CameraRegionListener which notifies when the visible area of the camera view has changed. This is useful when displaying read locations on the camera view as it allows exact translation of locations within the camera frame to points on the visible camera surface.
• Added several utility methods for translating read location data into more easily usable formats. The method Utility.convertRegionPointsToPath() converts the location into an Android Path object, while the Utility.convertRegionPointsToRect() converts them into a simple Rect.
• Fixed a bug that prevented camera error dialogs from displaying in some instances.
• Fixed a crash that could occur when setting invalid camera parameters on a Camera1 device.

DMSDK 3.0.1 - 1/20

Changes:

• SDK
• Updated for the latest changes to the Resolver backend.
• Fixed a bug in the CameraSurfaceView where unloading and reloading the view rapidly could cause the camera to stop capturing. This could occur when quickly switching back and forth between tabs in an activity.

DMSDK 3.0 - 11/19

Changes:

• SDK
• DM SDK 3.0 is a major release and contains a number of breaking changes. Refer to the Porting Guide for more detail on how to migrate a project.
• An API key is required to use the SDK. A key can be obtained from the Digimarc Barcode Manager portal, for existing customers and on a trial basis for SDK evaluation.
• The minimum supported Android version is 4.1 (SDK 16). Android Studio 3.0+ is required.
• API changes
• Abstract methods in many SDK objects (readers, camera, resolver) have been replaced by listener interfaces. Some listeners are optional and may not be needed depending on the use case.
• SDK objects are now constructed and initialized using a Builder pattern.
• Multiple decode results per symbology can now be returned for a frame. The ReaderResult class wraps these and provides access to all read data as well as exposing which decodes were new for the most recent frame.
• The Resolver now gets its configuration information, including username, password and resolver URL from the API key.
• Payload
• Representations may now be returned in more relevant types than String. See the Representation documentation for information on the return type for each representation.
• GS1 AI data is now exposed through the Payload class method getGS1Data().
• Several Payload helper classes have been removed. The data exposed by them is all available through either representations or the GS1 data method.
• Camera
• The Camera library has been incorporated into DM SDK itself. Import paths within application code and layouts will need to be changed.
• The CameraHelperAdaptive and CameraHelperAdvance classes have been removed. CameraHelper now contains all support for both Camera1 and Camera2 image capture.
• Image frames are now wrapped in an ImageData object rather than being byte arrays.
• Access to camera metadata is now available through the Metadata class. The class is designed to allow standard metadata access no matter which camera API a device is using. Currently only a few metadata fields are exposed. Contact Digimarc if you require access to other fields.
• Audio
• The AudioHelper class is no longer needed in most use cases. The AudioCaptureReader class now handles audio capture itself.
• The Audio library has been incorporated into DM SDK.

DMSDK 2.12.2 - 8/19

Changes:

• SDK
  • Updated native modules to statically link with the C++ runtime.

DMSDK 2.12.1 - 7/19

Changes:

• SDK
  • In the Payload class the DataBar representation for Simple Product ID and SGTIN-96 Digimarc Barcodes now includes GS1 AIs for extra data fields.
  • Changed a Google search string so that all generated links use https.

DMSDK 2.12 - 7/19

Changes:

• SDK
  • Fixed audio capture distortion bug. Detection of Digimarc Barcode for Audio should be improved on most devices.
• Camera Support (CameraHelper library)
• Improved ability to read Digimarc Barcodes in ARCore sample app.
• Fixed a crash that could occur in Camera1 support code if the device did not have a camera.
• Fixed a native crash that could occur on camera startup in Camera1.

DMSDK 2.11.1 - 6/19

Changes:

• SDK
  • NEW! Added support for X86-64 architecture. If you don't need x86/x86-64 support in your application see the build.gradle file in the DMSDemo sample app for information on removing architectures from your build.

DMSDK 2.11 - 4/19

Changes:

• SDK
  • NEW! Notable detection improvement for objects enhanced with Digimarc Barcode through increased off center detection.
  • NEW BETA! Added an AR sample app. DMSArDemo uses ARCore on supported devices to read codes (Digimarc Barcode, 1D or QR codes) and display markers where they are detected. Give it a try and let us know what you think! Email your feedback to ashleigh.fortune@digimarc.com
  • Extended distance reader option is now deprecated. Extended distance reading is on by default and the option to turn it off will be removed in a future release.
• Camera Support (CameraHelper library)
• Fixed crash in native code that could occur when the camera was shutting down.
• Fixed a rare crash in Camera1 support that could occur when quickly starting and stopping the camera.
• Reduced memory usage while using Camera2.

DMSDK 2.10.1 - 1/19

Changes:

• SDK
  • Fixed error that would cause Resolver to silently fail all resolve() calls when the resolver object was restarted after calling release(). In this situation an error will now be sent to the onError callback when the app calls start(). When a Resolver object has been released() it is no longer valid and a new Resolver must be created in order to resolve again.
• Camera Support (CameraHelper library)
• Fixed a crash that could occur when running on a tablet emulator instance.
• Audio Support (AudioHelper library)
• Fixed a rare crash that could occur when stopping audio capture.

DMSDK 2.10 - 10/18

Changes:

• SDK
  • NEW! Image Digimarcs can now be read at a larger range of distances.
  • NEW! Image Digimarc read location is now reported in read result metadata. The Sdk2Demo application uses this data along with scale and rotation metadata to show an outline of the read region on the screen.
  • Improved performance of Image Digimarc reading
  • Sample app projects now use Gradle plugin version 3.0.1. If you are still using Android Studio 2.x or earlier you will need to edit the project files and change the plugin version to 2.3.3 or earlier.
  • Fixed a crash that could occur during DMSDetectorView initialization.
  • Fixed a crash that could occur when read region is being displayed and the application loses focus.
• Camera Support (CameraHelper library)
• NEW! Improved support for Camera2 devices. CameraHelperAdaptive will now use the Camera2 API for devices which support Camera2 Limited or Full. This includes most Android 6.0+ devices currently on the market. If you are using the CameraHelper class in your application we strongly suggest you move to CameraHelperAdaptive instead. On some devices like the Pixel 2 & Pixel 2 XL you will see improved performance reading Image Digimarcs when using CameraHelperAdaptive.
• Fixed a crash that could occur when quickly switching between applications which are using the camera.

DMSDK 2.9.4 - 9/18

Changes:

• Camera Support (CameraHelper library)
• Fixed a bug that prevented frame callbacks from stopping on Camera1 devices when the video surface is hidden.

DMSDK 2.9.3 - 9/18

Changes:

• Audio Support (AudioHelper library)
• Fixed possible crash when an audio session (Skype, Hangouts, etc.) is running in the background.

DMSDK 2.9.2 - 8/18

Changes:

• Camera Support (CameraHelper library)
• Fixed bug in the CameraHelper class which could prevent frame callbacks from occurring.

DMSDK 2.9.1 - 7/18

Changes:

• SDK
  • NEW! Location of traditional 1D barcodes now available in DataDictionary metadata returned by the reader. This can be used to highlight the location of a barcode in the camera view. Try running the Sdk2Demo app to see this is action, and look at the source of the app for an example of its use.
• Camera Support (CameraHelper library)
• Improved performance and fluidity on Camera2 devices.
• Fixed crash that could occur on Android 4.1.
• Fixed camera surface scaling issue on Samsung Galaxy S7 devices running Android 6.x.

DMSDK 2.9 - 6/18

Changes:

• SDK
  • NEW! Improved ability to detect Digimarc Barcode for product packaging and print media from an extended range of angles.
  • NEW! UPC E barcodes can now be represented as UPC A and GTIN 14 values.
  • NEW! UPC and EAN barcodes now have a DataBar AI representation.
  • Deprecated the Resolver.reportAction() and Payload.buildFastPathForServer() methods.
  • Readers can now have new ReaderOptions applied after creation.
  • Fixed a bug in the scheduler that resulted in a rare crash behavior.
  • Fixed a small bug in DetectorViewDemo that caused some history records to not have camera thumbnail images.
• CameraHelper
• Improved camera view scaling. When the camera view is limited or scaled within an application's UI the camera surface behind it will be scaled to fill the visible view fully while maintaining the capture aspect ratio. The surface will be centered within the visible area, meaning that camera's auto focus area matches the user's view.
• NEW! Added method CameraHelper.getRectForVisibleSurface() which returns a region for the visible area of the camera view within the overall camera image. The area retrieved from this method can be passed to the setImageDetectionRegion() method of the ImageReader and VideoCaptureReader classes so that 1D barcode detection does not occur outside of the visible camera area.

DMSDK 2.8 - 3/18

Changes:

• SDK
  • NEW! GS1 AI Weight Representations now support GS1 AIs 3x02.
  • Improved scheduling to reduce device power usage.
  • Sample apps now all support rotation.
• CameraHelper
• Fixed camera issue with HTC Desire 10 Pro.
• Fixed several rare crashes.

DMSDK 2.7.2 - 3/18

Changes:

• CameraHelper
• Fixed crash that occurred during camera startup on some Huawei devices.

DMSDK 2.7.1 - 2/18

Changes:

• CameraHelper
• Fixed camera preview distortion issue for both portrait and landscape orientations. Note: to enable landscape mode in the demo sample apps, you need to add android:screenOrientation="sensor" in your AndroidManifest.xml Activity section.

DMSDK 2.7 - 12/17

Changes:

• SDK
  • NEW! Added support for ITF-14 and Variable Length ITF 1D traditional barcodes.
  • Significant reduction in SDK binary size.
  • Improved sample code in DMSDemo which handles/launches links from QR Codes.
• CameraHelper
• Significant improvements to read performance with the HTC U Play handset.
• Improved read performance of Samsung S7 and S7 Edge.
• Camera focus improvements for newer LG handsets (Pixel 2 XL, V30, etc.).
• Fixed several bugs in Camera2 support.
• Modified overridable method onConfigureCamera2 in CameraHelperAdaptive. If you are using this method in your app Android Studio may not recognize the method change. If this occurs you will need to invalidate the build cache in Android Studio (File menu -> Invalidate Caches / Restart).

DMSDK 2.6.1 - 11/17

Changes:

• SDK
  • Fixed crash in DMSDetectorView camera help prompts.
• CameraHelper
• Fixed problem on camera startup with Camera1 devices.

DMSDK 2.6 - 10/17

Changes:

• SDK
  • NEW! Added representations for GIAI Company Prefix and GIAI Asset ID.
  • NEW! GIAI payloads are now resolved via the Digimarc Resolver.
  • NEW! On Camera2 devices frame processing is suspended as a power saving measure when the image gets too dark.
  • The DMSDemo app's UI has been simplified significantly.
• CameraHelper
• On Camera2 devices that support it Edge Mode (a smoothing algorithm) is now turned off.
• The default resolution used on most devices is now set to 1920x1080.
• Fixed a bug that would cause the camera to continue capturing when the screen was turned off.
• Fixed a bug that could cause a camera error when restarting the app and using Camera1.
• Fixed a bug that could caused the camera view to appear zoomed in on camera restart.
• Improved aspect ratio correction for the camera surface.
• Device rotation is now properly supported.

DMSDK 2.5 - 8/17

Changes:

• SDK
  • NEW! Reader option flag for detection of Digimarc Barcodes at extended distances. See ExtendedReadRange in ReaderOptions for more information.
  • NEW! Added new getting started guide for the SDK. You can find Overview of DM SDK in the Docs folder.
  • ContentItem class now contains payload & category fields.
  • Image recognition is no longer supported by DMSDK. The symbology and reader options for it are deprecated.
  • Performance improvements in Digimarc Barcode detection.
  • Fixed bug in Databar Formatted List representation with Expanded Fresh Digimarc Barcodes.
  • Fixed several bugs with GIAI representation.
  • Fixed several crash bugs in DMSDetectorView related to custom UI elements and help prompt text.
  • New sample app DetectorViewDemo has replaced the DISDemo app. It demonstrates simple usage of the DMSDetectorView drop-in component and contains a history of reads.
  • DMSDemo app is now much simpler & easy to understand.
  • Updated sample apps project files to use Google Gradle plugin version 2.3.3.
• CameraHelper
• The library now uses TextureView rather than a SurfaceView.
• For all Camera1 devices the denoise-filter is now turned off by default. This should lead to better Digimarc Barcode detection on a wide variety of devices.
• Fixed camera issue with some Camera2 devices that could prevent video from resuming when switching between multiple camera apps.
• The library is now fully self-contained, so it is possible to use it without needing to include the DMS library.

DMSDK 2.4 - 5/17

Changes:

• Traditional barcode detection can now be limited to a region of the screen using the setImageDetectionRegion method. This is supplied to support some use cases and/or UI implementations. Please see the documentation for more information.
• DMSDetectorView can display a barcode detection region set via setImageDetectionRegion as a screen overlay. This can be enabled via a layout flag or the showDetectRegion method.
• Performance optimizations in traditional barcode detection.
• Performance optimizations for image recognition.
• Performance and stability improvements in Camera2 support.
• Significantly reduced the SDK method count.

DMSDK 2.3.1 - 3/17

Changes:

• Improved SmartLabel detection

DMSDK 2.3 - 3/17

Changes:

• Scheduler changes to reduce power usage. Power draw is now comparable to DMSDK 1.16 if not better.
• Improvements in Camera2 support.
• Added documentation and beta sample code for handling multi-modal results. See the Multi-Modal Result Handling document in the Docs folder for more information.

DMSDK 2.2.1 - 1/17

Changes:

• Fixed a crash when displaying an error dialog in DMSDetectorView.
• Fixed a bug in the BitmapUtils.getScaledPreviewImage() method of CameraHelper.

DMSDK 2.2 - 1/17

Changes:

• New feature: Digimarc Image Recognition.
• Contact us for more information!
• New Representation support for GS1 Variable Measure Trade Items.
• New feature for apps to access the detected camera frame.
• Added ability to set custom help strings in DMSDetectorView.
• Android Camera2 now available as a beta feature.
• We welcome your feedback on this interface.
• Fix: correct handling in ImageReader when image size changes.
• Fix: potential crash on camera shutdown.
• Fix: extraneous exception throwing removed from QR code reader.
• Performance improvements and bug fixes.

DMSDK 2.1.1 - 12/16

Changes:

• Fixed a crash on reading a QR Code containing no data
• Improved performance for Digimarc Barcode detection at different angles and distances.
• Performance improvements and bug fixes.

DMSDK 2.1 - 10/16

Changes:

• Payload support added for Digimarc Barcodes using Simple Product ID and Expanded Fresh data encoding schemes.
• Performance improvements and bug fixes.

DMSDK 2.0 - 8/16

Digimarc Mobile SDK 2.0 is a major release and contains some significant changes and improvements over DMSDK 1.x. It should be noted that these changes are primarily found in the lower level components of the SDK rather than the UI components (DIS - previously referred to as the Drop-In SDK). Applications that use the UI component -- DMSDetectorView -- will need few changes to get up and running with the new SDK.

Porting guides can be found under the Docs folder for bringing your app from DMSDK 1.x to the new SDK. There are separate documents for applications using the DIS UI components and those using the lower level SDK components.

Note that use of this SDK to read traditional barcodes has a license cost associated with it. Please refer to https://www.digimarc.com/application/mobilesdk for more information.

Changes & New Features

• Image readers, audio readers and the Digimarc Resolver are now separate components. They can be created, initialized and used as needed and are not part of a larger session concept.
• Performance scaling is now standard behavior, and separate configuration files are no longer part of the SDK. The image and audio readers will monitor how much work the system is doing and automatically adapt their performance to keep from overstressing the device. This behavior can be disabled if needed, but in most cases we recommend leaving it on.
• The Payload class makes use of a new concept called Representations to provide easier access to the data that you need. With representations it is possible to easily get specific data types and ignore some/all others.
• Helper libraries CameraHelper and AudioHelper are included in the SDK to ease implementation of camera and audio capture & processing. The libraries are used in the sample applications as well as the SDK UI components.

Getting Started

The DIS UI components provide the easiest path to getting an application up, running and functional. Refer to the documentation for DMSDetectorView as well as the sample application DISDemo for more information.

Sample Applications

   DMSDemo - A full featured sample application with image and audio detection, as well as resolving or detected codes. It includes a history drawer and persists the entries across sessions.

   Sdk2Demo - A more simplistic application showing use of image and audio detection and resolving. This is a good sample to refer to for getting an application up and running quickly with image and/or audio capture using the SDK's helper libraries and lower level components.

   DISDemo - Demonstrates usage of the DMSDetectorView UI component for image and audio detection as well as resolving. The UI component is the easiest way to make use of this SDK, although it does lack some of the customization you can get from using the lower level components.