Data flow

V‑Spark is highly configurable for a wide variety of uses cases. The following generalized workflow does not cover every use case, but it illustrates how audio data moves through the system.

  1. Audio and metadata file preparation.
    • Ensure that audio is compatible with V‑Spark's built-in audio evaluation tool. V‑Spark supports one- or two-channel audio only; audio with more than two channels will be rejected.
    • Ensure metadata is correctly formatted and does not violate any system metadata restrictions.

  2. Audio and metadata upload.
    • Audio may be uploaded with the UI or with the API.

    • Custom metadata may be uploaded with audio data in a zip, or after the audio data in a separate upload.

  3. V‑Spark queues the audio for transcription.
  4. ASR transcription.
  5. Transcription output queued for analysis by V‑Spark.
  6. JSON transcript analytics processing.
    • Basic metrics provided for all transcripts.

    • Custom analysis performed by applications depending on configuration.

  7. Results available for download.
    1. If callbacks are enabled, V‑Spark sends results to the configured destination.

Other important workflows:

  1. Reprocessing audio
  2. Re-scoring transcripts
  3. Deleting audio, transcription, and analytics data
  4. Scheduled and ad-hoc report generation