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
The Local API is useful for integrations such as Raycast, but its current file-path transcription endpoint has a hard five-minute limit:
Audio file exceeds the 300 second API limit.
Could we clarify the intended purpose of this limit and consider making the API better aligned with FluidVoice’s existing in-app file transcription workflow?
The in-app uploader already supports longer recordings through native file transcription or chunked processing. By contrast, the Local API’s /v1/transcribe file-path route currently rejects files above five minutes before transcription starts.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The Local API is useful for integrations such as Raycast, but its current file-path transcription endpoint has a hard five-minute limit:
Audio file exceeds the 300 second API limit.Could we clarify the intended purpose of this limit and consider making the API better aligned with FluidVoice’s existing in-app file transcription workflow?
The in-app uploader already supports longer recordings through native file transcription or chunked processing. By contrast, the Local API’s /v1/transcribe file-path route currently rejects files above five minutes before transcription starts.
Beta Was this translation helpful? Give feedback.
All reactions