lintoai/linto-platform-diarization repository overview

⁠LINTO-PLATFORM-DIARIZATION

LinTO-platform-diarization is the LinTO⁠ service for speaker diarization.

LinTO-platform-diarization can either be used as a standalone diarization service or deployed as a micro-services.

• Prerequisites⁠

• Deploy⁠

  • HTTP⁠
  • MicroService⁠

• Usage⁠

  • HTTP API⁠
    • /healthcheck⁠
    • /diarization⁠
    • /docs⁠
  • Using celery⁠

• License⁠

⁠Pre-requisites

⁠Docker

The transcription service requires docker up and running.

⁠(micro-service) Service broker and shared folder

The diarization only entry point in job mode are tasks posted on a Redis message broker. Futhermore, to prevent large audio from transiting through the message broker, diarization uses a shared storage folder mounted on /opt/audio.

⁠Deploy

linto-platform-diarization can be deployed:

• As a standalone diarization service through an HTTP API.
• As a micro-service connected to a message broker.

1- First step is to build the image:

git clone https://github.com/linto-ai/linto-platform-diarization.git
cd linto-platform-diarization
docker build . -t linto-platform-diarization:latest

⁠HTTP

1- Fill the .env

cp .env_default_http .env

Fill the .env with your values.

Parameters:

2- Run the container

docker run --rm \
-v SHARED_FOLDER:/opt/audio \
-p HOST_SERVING_PORT:80 \
--env-file .env \
linto-platform-diarization:latest

This will run a container providing an http API binded on the host HOST_SERVING_PORT port.

Parameters:

⁠Using celery

You need a message broker up and running at SERVICES_BROKER.

1- Fill the .env

cp .env_default_task .env

Fill the .env with your values.

Parameters:

2- Fill the docker-compose.yml

#docker-compose.yml

version: '3.7'

services:
  punctuation-service:
    image: linto-platform-diarization:latest
    volumes:
      - /path/to/shared/folder:/opt/audio
    env_file: .env
    deploy:
      replicas: 1
    networks:
      - your-net

networks:
  your-net:
    external: true

3- Run with docker compose

docker stack deploy --resolve-image always --compose-file docker-compose.yml your_stack

Queue name:

By default the service queue name is generated using SERVICE_NAME and LANGUAGE: diarization_{LANGUAGE}_{SERVICE_NAME}.

The queue name can be overided using the QUEUE_NAME env variable.

Service discovery:

As a micro-service, the instance will register itself in the service registry for discovery. The service information are stored as a JSON object in redis's db0 under the id service:{HOST_NAME}.

The following information are registered:

{
  "service_name": $SERVICE_NAME,
  "host_name": $HOST_NAME,
  "service_type": "diarization",
  "service_language": $LANGUAGE,
  "queue_name": $QUEUE_NAME,
  "version": "1.2.0", # This repository's version
  "info": "Multilingual diarization model",
  "last_alive": 65478213,
  "concurrency": 1
}

⁠Usages

⁠HTTP API

⁠/healthcheck

Returns the state of the API

Method: GET

Returns "1" if healthcheck passes.

⁠/diarization

Diarization API

• Method: POST
• Response content: application/json
• File: A Wave file
• spk_number: (integer - optional) Number of speakers. If empty, diarization will clusterize automatically.
• max_speaker: (integer - optional) Max number of speakers if spk_number is unknown.

Return a json object when using structured as followed:

{
  "speakers": [
      {"spk_id": "spk5", "duration": 2.0, "nbr_seg": 1},
      ...
  ],
  "segments": [
      {"seg_id": 1, "spk_id": "spk5", "seg_begin": 0.0, "seg_end": 2.0},
      ...
  ]
}

⁠/docs

The /docs route offers a OpenAPI/swagger interface.

⁠Through the message broker

STT-Worker accepts requests with the following arguments: file_path: str, speaker_count: int (None), max_speaker: int (None)

• file_path: (str) Is the location of the file within the shared_folder. /.../SHARED_FOLDER/{file_path}
• speaker_count: (int default None) Fixed number of speakers.
• max_speaker: (int default None) Max number of speaker if speaker_count=None.

⁠Return format

On a successfull transcription the returned object is a json object structured as follow:

{
  "speakers": [
      {"spk_id": "spk5", "duration": 2.0, "nbr_seg": 1},
      ...
  ],
  "segments": [
      {"seg_id": 1, "spk_id": "spk5", "seg_begin": 0.0, "seg_end": 2.0},
      ...
  ]
}

• The speakers field contains an arraw of speaker with overall duration and number of segments.
• The segments field contains each audio segment with the associated speaker id start time and end time.

⁠Test

⁠Curl

You can test you http API using curl:

curl -X POST "http://YOUR_SERVICE:PORT/diarization" -H  "accept: application/json" -H  "Content-Type: multipart/form-data" -F "file=@YOUR_FILE.wav;type=audio/x-wav" -F "spk_number=NUMBER_OF_SPEAKERS"

⁠License

This project is developped under the AGPLv3 License (see LICENSE).

⁠Acknowlegment.

• PyBK⁠ diarization framework (License MIT).