-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Code 413 #38
Comments
get this too and my guess is the audio file is too large. for some reason the default recording format is .mp4 which makes really large audio files so anything over a few minutes cannot get sent to whisper because of file size limits |
I don't think the audio file being too large is the case, unless, the uploading file size limit has been capped recently. Earlier this month, I was able to upload an hour's worth of an WEBM file with a file size above 20MB and it worked successfully. |
I believe the upload limit for whisper is 25mb. webm file sizes much smaller than mp4. unfortunately mp4 seems to be the only format that my phone records via this plugin - need to record elsewhere then upload to whisper. Hope this gets fixed and we can record mp3 natively. |
I was experiencing the same issue and converted 43mb .mp4 file down to 1.2mb .mp3 file (using Audacity) and the upload worked perfectly. |
413s can be quite frustrating. I've updated the settings to use |
Same here. A compression would be solving this issue. Or a split of the stream. |
I get this issue when I try to upload a recording of even a 30 minute meeting. Just checked the file size of a 45 minute WEBM recording that just failed and it was a little over 50 MB. Whisper's limit is 25 MB, so I have to assume that's the problem. Short recordings work great. I agree w/@g1ronn1mo - we probably need this plugin to either compress before uploading, and/or chunk the recording and make multiple calls. |
After attempting to upload an audio file, I get error code 413. "error sending audio data: request failed with status code 413"
The text was updated successfully, but these errors were encountered: