[Team B] AWS Transcribe Streaming implementation#272
[Team B] AWS Transcribe Streaming implementation#272FlyingWaffleDev merged 7 commits intodeveloperfrom
Conversation
6831881 to
08cc27e
Compare
|
New commit should integrate AWS configuration into the settings menu. |
|
All functional now. I would point out, though, that the quality between AWS and Sherpa is very nearly identical. Using this Youtube clip from House, I produced the following two transcripts in parallel: SHERPA:
AWS:
As you can see, Sherpa has better sentence chunking, AWS has better recognition of weird words, but overall both mess up the speaker count, both mess up the speaker differentiation, etc. |
7e31b08 to
594943d
Compare
I found this library early on in trying to implement AWS: https://github.com/javer/aws_transcribe_streaming
Unfortunately, it hasn't been updated in two years, so it can't be used because of dependency issues. So, I went down three rabbit holes trying to manually implement the bare basics I needed using Amazon's API docs, but that just went nowhere in the time I have.
What I ended up doing was to just copy all the code from that library I linked into our codebase. It still works fine (just hasn't had the dependencies updated) so I was able to make a horrible garbage implementation of AWS side-by-side with our local stuff.
It works, but is just as flaky as our stuff, in new and interesting ways.
This also introduces the need for AWS keys, which I will move to the settings page in my next commit.
I want to add some kind of option to ignore AWS and just use Sherpa if the keys are missing, but that might take a while to get right.