-
Notifications
You must be signed in to change notification settings - Fork 164
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
Support to Google Speech To Text transcription format #152
Comments
Hi @eyal13579 , If you are interested in creating a Google STT one, and need any help to setup a PR let me know. |
Hi @pietrop , I'm familiar with Google STT and would love to contribute to this development. I have gone through the helper docs. I have a small clarification regarding which approach to take. Google STT provides speaker diarization as a beta feature, so is it okay if I use the beta results for creating the sample json ? |
Hi @sshniro, that's awesome, thanks! re-speaker info, sounds good to use the beta feature for Google STT speaker diarization. We have been using a flexible approach in the current module, because a lot of these STT have those optional attributes, so didn't want to impose them as defaults. You can see in the other modules, that we check if the attribute is available, if it is we break the paragraph down based on the speaker diarization, if it isn't we break the paragraphs down based on punctuation, and add place holder names to the speaker labels. The user can then change the size of the paragraphs and speaker labels in the UI. for example you can see in the I think it be good to add support for both, creating paragraph based on speaker label as well as on punctuation, as a fallback if speaker labels are not provided. However if you want to priorities the speaker labels, and leave the punctuation one for a separate PR that's also fine. Let me know if you have any questions. |
Hi @pietrop I have created a PR for GCP to Draft JS conversion , The PR does not cover speaker diarization. I will send another PR with the segmentation soon. |
any plans to support Google?
The text was updated successfully, but these errors were encountered: