Skip to main content

Analyze Library Tracks

The analysis of a library track with all the available classifiers will automatically be started upon creation.

However, in case the analysis limit for a time period has already been reached, the analysis will not be enqueued and must be manually enqueued at a later point (when the limit got reset/increased) using the Mutation.libraryTrackEnqueue field.

Additionally, it is recommended to re enqueue the analysis of a library track when our classifiers have been updated.

The current available analysis types are AudioAnalysisV6, FastMusicalAnalysis, FullScaleMusicalAnalysis and InDepthAnalysis. Depending on the account type the eligible analysis for that account will be enqueued upon invoking the Mutation.libraryTrackEnqueue mutation.

The Mutation.libraryTrackEnqueue returns the LibraryTrackEnqueueResult GraphQL union type which can either be LibraryTrackEnqueueSuccess or LibraryTrackEnqueueError.

Enqueue succeeded#

In case the Mutation.libraryTrackEnqueue result is LibraryTrackEnqueueSuccess, the library track got successfully enqueued.

Enqueue failure#

In case the Mutation.libraryTrackEnqueue result is LibraryTrackEnqueueError, the library track could not be enqueued. The error and message field on the LibraryTrackEnqueueError contain a detailed description on why the library track could not be enqueued.

Error code overview#

Error codeMeaning
limitExceededThe analysis limit was exceeded.
libraryTrackNotFoundThe LibraryTrack with the provided id does not exist.

Next steps#

A detailed overview can be found on the GraphQL schema documentation: