Pex SDK - Release Notes
Version 4.7.0
Search: Pex Registry Updates
Search by ISRC
In addition to performing a search with a fingerprint generated from a media file, you can now also initiate a search using an ISRC. If a corresponding asset can be located for the ISRC, the search will initiate and you will receive the same standard search response you would get from a fingerprint-based search
This allows you to search the Pex Registry when you don’t have a source media file but do have a known identifier.
Search: Custom Database Updates
Retrieve status of a particular custom database asset
A new "Get Entry" function lets you retrieve fingerprint information and status for a specific asset in your custom database. Returned data includes:
Fingerprint Types (Audio, Melody, Phonetic)
This will inform what fingerprint types you have ingested for the corresponding asset
Status (Active, Pending)
Active: Fingerprint is live and searchable
Pending: Fingerprint is processing and will be searchable soon
This provides better visibility into ingestion progress and fingerprint availability for a specific asset.
List Entries enhancement
The existing "List Entries" functionality has been updated so that in addition to a list of assets that are currently ingested in your custom database, it will return each asset's corresponding status (active, pending)
This provides better visibility into the status of your custom database as a whole.
Other Updates
CLI Helper Tool
A lightweight CLI tool is now provided for basic one-off searches against the Pex Registry and your Custom Database. It can also handle basic catalog management functions for Custom Database clients. It can be run via the
pexsearchcommand
In order to access these new features, you will need to:
Update your language bindings to the 4.7.0 release. Please see Language Bindings for more details.
Install the latest version of the SDK core library to ensure compatibility. Please see Core Library (SDK) for more details.
Version 4.6.1
Enhanced Cover Song Detection
Melody lookups can now include an additional phonetic fingerprint in the same request.
Detection can identify matches based on either melody or phonetic similarity to assets in the Pex registry.
More details can be found at Search Types & Use Cases
Content Classification
Analyze a query file to detect if it contains any music, speech, and/or silence segments.
Can be combined with an audio lookup to identify music content that contain no matches to any commercial tracks in the Pex registry
More details can be found at Content Classification
Melody Matching Improvements
Optimizations to the melody matching (approximately 35% higher true positive rate)
In order to access these new features, update your language bindings to the 4.6.1 release. Please see Language Bindingsfor more details.
Version 4.4.0
Archive Functionality (for Search: Custom Database clients) - allows client to remove a fingerprint from their custom database, so it will no longer be available for matching. For more details on using this functionality, please visit Basic Usage
Database List Functionality (for Search: Custom Database clients) - allows client to retrieve a list of what fingerprints (via provided_id) are currently in their custom database. For more details on using this functionality, please visit Basic Usage
Improvements made to the "Identify Music" search type for audio matching for DJ mixes, mashups, and long compilations.
Better Logging Information - Additional information added to the logs to assist with troubleshooting issues
Bug Fix: Fix for SDK occasionally erroring out after long period of connectivity with no activity
In order to access these new features, update your language bindings to the 4.4.0 release. Please see Language Bindingsfor more details.
Version 4.2.1
A
confidencevalue is now returned for every match segment in the search response. You can find it in thesegmentsobject in thematch_detailssection.For more details, visit the Search Response page for Search: Pex Registry or Search: Custom Database
Bug Fix: The SDK will no longer return an invalid input error when attempting to create an audio fingerprint from a file that contains no or low level audio
Version 4.1.2
When performing an audio or melody search against the Pex Registry, you can now also designate a specific search type to perform: an "identify music" search or a "find matches" search. A
identify musicsearch allows you to check any media file for copyrighted music. Afind matchessearch allows you to find commercially distributed versions of your own copyrighted asset. To designate a search type, you will pass an additional parameter when creating the search request. Note: if no search type is designated, the search will default to the "identify music" search type.For more details on how to prepare the search request and designate a search type, visit: Basic Usage
For more details on the two search types, visit: Search Types & Use Cases
In order to access these new features, update your language bindings to the 4.1.2 release. Please see Language Bindingsfor more details.
Version 4.0.10
When searching against the Pex Registry, DSP links (if available) are now returned for matched assets in the search response. You can find it in the
dspobject in theassetsection.For more details, visit the Search Response page for Search: Pex Registry
Version 4.0.3
When searching against the Pex Registry, the release date is now returned for the album associated with the matched asset. You can find it in the
release_dateobject in theassetsection.For more details, visit the Search Response page for Search: Pex Registry
Version 4.0.0
The search response has been expanded to include more asset metadata and match details for a matched asset.
Asset metadata now includes: ISRC, Title, Subtitle, Artist, Album/Release Name, Barcode, Label, Distributor
Match details now includes: Query Match Duration, Query Match %, Asset Match Duration, Asset Match %
Match segment details now includes: Query Start, Query End, Asset Start, Asset End, Pitch Modification, Speed Modification, Transposition information
For more details, visit the Search Response page for Search: Pex Registry or Search: Custom Database
Last updated