You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in Batch v1 it is possible to send raw audio bytes for transcription, which is preferable for my use case. However, I noticed that in Batch v2, it appears that URI's are used, which based on my understanding, means that sending raw audio bytes is not supported in Batch v2. Is being able to send raw audio bytes via Batch v2 planned in the future? Or is it currently possible and I am missing something? I was hoping just to get some clarification regarding this as I want to use the newest API version, but not if it means a critical use case for me is missing.
The text was updated successfully, but these errors were encountered:
Hi! Thanks for asking. You are correct, the v1 API does support raw bytes input, and that feature is missing from v2. The immediate reason is that we wanted the v2.ProcessAudioSource to be more specific and thus understandable, whereas the v1.ProcessAudio handled all use cases in the same method.
We do have the raw byte stream input support on the backlog for the v2 also, but the release schedule for that is not clear at the moment. We will keep v1 alive until the streaming support exists in v2 also, so you can continue using the v1 raw byte input for now.
Hi there!
I noticed that in Batch v1 it is possible to send raw audio bytes for transcription, which is preferable for my use case. However, I noticed that in Batch v2, it appears that URI's are used, which based on my understanding, means that sending raw audio bytes is not supported in Batch v2. Is being able to send raw audio bytes via Batch v2 planned in the future? Or is it currently possible and I am missing something? I was hoping just to get some clarification regarding this as I want to use the newest API version, but not if it means a critical use case for me is missing.
The text was updated successfully, but these errors were encountered: