Add container diarization configuration
This commit is contained in:
@@ -106,6 +106,23 @@ Optional machine-specific settings include:
|
||||
- `MKA_DIARIZATION_MODE` (`auto`, `cpu`, or `gpu`; default: `auto`)
|
||||
- `MKA_DIARIZATION_RUNTIME` (`native` or `container`; default: `native`)
|
||||
- `MKA_DIARIZATION_CONTAINER_IMAGE` (required for container diarization)
|
||||
- `MKA_DIARIZATION_CONTAINER_ARGS` (default: no extra arguments), encoded as a
|
||||
JSON array of strings so ordering and leading dashes are preserved exactly
|
||||
|
||||
For example, a compatible AMD ROCm workstation can configure validated
|
||||
container access without adding controls to the Streamlit UI:
|
||||
|
||||
```bash
|
||||
export MKA_DIARIZATION_MODE=gpu
|
||||
export MKA_DIARIZATION_RUNTIME=container
|
||||
export MKA_DIARIZATION_CONTAINER_IMAGE=rocm/pytorch:rocm7.2.1_ubuntu24.04_py3.12_pytorch_release_2.9.1
|
||||
export MKA_DIARIZATION_CONTAINER_ARGS='["--device=/dev/kfd","--device=/dev/dri","--group-add","video"]'
|
||||
```
|
||||
|
||||
The JSON elements are forwarded as four separate, ordered Meeting Lab
|
||||
container arguments. Runtime and hardware details remain machine-specific
|
||||
environment configuration; the UI continues to expose only the diarization
|
||||
on/off choice.
|
||||
|
||||
From the Meeting Assistant repository, start the UI with:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user