Define external recording workflow for MVP
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
# ADR 0009: Use External Audio Recording for the MVP
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Context
|
||||
|
||||
Reliable simultaneous capture of system audio and microphone audio is highly
|
||||
platform-specific.
|
||||
|
||||
OBS Studio already provides stable, configurable and cross-platform audio
|
||||
capture. Reimplementing audio capture during the initial project phase would
|
||||
add substantial complexity without directly improving transcription quality.
|
||||
|
||||
The primary value of the Meeting Assistant lies in transcription, speaker
|
||||
diarization, analysis, structured knowledge extraction and export.
|
||||
|
||||
## Decision
|
||||
|
||||
The MVP shall not require an integrated audio recorder.
|
||||
|
||||
OBS Studio is the recommended reference recorder for online meetings.
|
||||
|
||||
The Meeting Assistant shall initially import existing audio recordings.
|
||||
|
||||
Initially supported input formats shall include:
|
||||
|
||||
- WAV as the preferred processing input
|
||||
- FLAC as a lossless import and archive format
|
||||
|
||||
Support for additional formats such as MP3, M4A and Opus may be added later.
|
||||
|
||||
The existing `recorder` module shall remain in the project architecture so that
|
||||
integrated recording can be implemented in a later phase without restructuring
|
||||
the application.
|
||||
|
||||
## Consequences
|
||||
|
||||
- Development can focus on transcription and downstream processing.
|
||||
- Platform-specific audio capture complexity is deferred.
|
||||
- OBS configuration remains outside the Meeting Assistant.
|
||||
- Users must start and stop the initial recording separately.
|
||||
- Imported recordings require validation before processing.
|
||||
- A future integrated recorder remains possible.
|
||||
Reference in New Issue
Block a user