Open someghuser opened 1 year ago
Please post more specific info about this problem.
It takes a while to process long audio so sometimes I would get a "network error" message and I don't know if it finished the job or it was some other error. So having a default output directory would help recover finished transcripts. Maybe write a logfile there instead if it was an error.
I encountered this both locally and using google compute.
It's been a while since I used whisper so I don't have the error messages anymore.
Maybe it's a timeout from your HTTP client? If the transcript is finished but errors out for a different reason, I think we should fix that bug rather than add a "temp" directory feature.
Logs could definitely be improved: #100, #155
Other apps don't treat that as temp directory but output directory because they support queues like comfyui and automatic 1111, which are stable diffusion and not transcription but still. Being able to download later and not have to deal with an expiring download page seems like an improvement is user experience.
I just use a browser and the default html interface so I don't have any design input in the clients.
Sometimes it throws network error. Output files and intermediates in
/data/output
to save time./data/output/<jobid>-<timestamp>-transcription-gb-<notes>.srt
/data/output/<jobid>-<timestamp>-translation-en-<notes>.srt