lintoai/linto-diarization-pybk Docker 镜像 - 轩辕镜像

LinTO-diarization

LinTO-diarization is the LinTO service for speaker diarization.

LinTO-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-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:

bash
git clone [***]
cd linto-diarization
docker build . -t linto-diarization-pybk:latest -f pybk/Dockerfile 

HTTP

1- Fill the .env

An example of .env file is provided in pybk/.envdefault.

Parameters:

2- Run the container

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

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

Parameters:

*diarization uses all CPU available, adding workers will share the available CPU thus decreasing processing speed for concurrent requests

Using celery

LinTO-diarization can be deployed as a micro-service using celery. Used this way, the container spawn celery worker waiting for diarization task on a message broker.

You need a message broker up and running at SERVICES_BROKER.

1- Fill the .env

An example of .env file is provided in pybk/.envdefault.

Parameters:

2- Fill the docker-compose.yml

#docker-compose.yml

yaml
version: '3.7'

services:
  punctuation-service:
    image: linto-diarization-pybk: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

bash
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:

json
{
  "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": $MODEL_INFO,
  "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
• speaker_count: (integer - optional) Number of speakers. If empty, diarization will clusterize automatically.
• max_speaker: (integer - optional) Max number of speakers if speaker_count is unknown.

Return a json object when using structured as followed:

json
{
  "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

Diarization worker accepts requests with the following arguments:

• 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:

json
{
  "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:

bash
curl -X POST "[***]" -H  "accept: application/json" -H  "Content-Type: multipart/form-data" -F "file=@YOUR_FILE.wav;type=audio/x-wav" -F "speaker_count=NUMBER_OF_SPEAKERS"

License

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

Acknowlegment.

• PyBK diarization framework (License MIT).