Skip to content

Improve Audio Storage Handling and Speaker Diarization Playback Debugging

srilatha bandari requested to merge feat/models into feat/develop-pro

MR Description

Summary

Enhanced the frontend audio handling and debugging workflow for the Speaker Diarization and transcription modules. This update improves visibility into how audio files are temporarily managed in browser memory, how playback sources are generated, and how session history is stored locally using IndexedDB.

Changes Implemented

  • Improved analysis and handling of temporary Blob-based audio playback.
  • Added support for inspecting dynamically generated audio playback URLs.
  • Enhanced debugging workflow for browser-side audio storage and playback.
  • Investigated and validated IndexedDB-based session history storage behavior.
  • Improved understanding of frontend-only audio lifecycle without backend modifications.
  • Verified speaker diarization playback flow using existing frontend resources.
  • Added inspection methods for identifying active audio sources and temporary blob URLs.
  • Documented cleanup behavior for temporary object URLs and memory management.
  • Verified handling of uploaded audio files and microphone recordings in browser memory.
  • Analyzed how transcription history metadata is persisted locally.

Technical Improvements

  • Explored usage of:

    • URL.createObjectURL
    • URL.revokeObjectURL
    • performance.getEntriesByType("resource")
    • browser media playback APIs

  • Investigated temporary in-memory Blob handling for uploaded and recorded audio.

  • Validated browser cleanup behavior after transcript clear, toggle off, and page refresh actions.

  • Verified that history records persist locally through IndexedDB storage.

  • Improved debugging methods for React/custom audio playback implementations where <audio> elements are not directly rendered.

Screenshot

image

Outcome

  • Better debugging and tracing for audio playback issues.
  • Improved visibility into temporary and persistent audio storage mechanisms.
  • Easier inspection of browser-managed audio resources during diarization workflows.
  • Clear understanding of frontend-only audio handling architecture.
  • Enhanced maintainability and troubleshooting support for transcription and speaker diarization features.

Impact

  • No backend changes required.
  • No impact on existing transcription functionality.
  • Fully compatible with current diarization and history modules.

closes #40 (closed)

Edited by srilatha bandari

Merge request reports