Feature Request: Enable Server-Side Transcription Retrieval via ID after Real-Time Audio Feed via Browser Microphone #57
Description
Is your feature request related to a problem? Please describe.
Currently, the only way to receive a real-time transcription stream is through the same WebSocket connection that sends the audio stream. This process introduces an additional step where the received transcription must be sent to the server for further processing. This extra step increases the potential for points of failure and latency, which can impact the overall user experience and system reliability.
Describe the solution you'd like
I would like to request the ability to retrieve the transcription stream on the server using a unique real-time audio feed ID, without needing to send the audio stream over the same WebSocket connection. By enabling this feature, we could directly access the transcription stream via the audio feed ID on the server, thereby simplifying the workflow, reducing potential points of failure, and enhancing the efficiency and reliability of the system.
Describe alternatives you've considered
One alternative considered is continuing with the current setup, where the transcription stream is received and then manually sent to the server for further processing. However, this approach is less efficient and more prone to errors.
Thank you for your continuous improvements and dedication to providing a powerful transcription service!