-
Notifications
You must be signed in to change notification settings - Fork 160
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(deprecated-api-removal): removed deprecated media-translations ap…
…i for google transcriptions
- Loading branch information
1 parent
e49ee78
commit 662bbf7
Showing
1 changed file
with
5 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,7 +4,7 @@ sidebar_position: 4 | |
sidebar_slug: transcriptions-google | ||
--- | ||
|
||
To add the realtime audio transcriptions in a Dyte meeting you can use Google Cloud Speech-to-Text | ||
To add the realtime audio transcriptions in a Dyte meeting you can use Google Cloud Speech-to-Text and Cloud translation APIs. | ||
|
||
These Google services are paid, a Google Cloud account is required to proceed. | ||
|
||
|
@@ -18,17 +18,17 @@ This integration is Web only at the moment | |
|
||
## 1. Setup Google Cloud Credentials | ||
|
||
You must have a service account with GCP (Google Cloud Platform) to use Google transcriptions. Please create a project in that account that allows Google Media Translations and Google Translations API. | ||
You must have a project & a service account with GCP (Google Cloud Platform) to use Google transcriptions. Make sure that service account allows Google Speech-to-Text and Google Translations API. | ||
|
||
Once done, download the keys for the service account. | ||
|
||
## 2. Setup a Server | ||
|
||
Setup a server to forward the Audio Data from client to Google Cloud. You don't want to put your GCP credentials on client side and therefore need a server which forwards audio data to Google Cloud | ||
|
||
For this, we have provided a sample in NodeJS for you to checkout (dyte-io/google-transcription)[https://github.com/dyte-io/google-transcription/tree/main/server]. Please find it here. Currently, we only have NodeJS samples; if you're working on a different backend, feel free to port this code or connect with us to help you port it. | ||
For this, we have provided a sample in NodeJS for you to checkout (dyte-io/google-transcription)[https://github.com/dyte-io/google-transcription/tree/main/server]. Please find it here. Currently, we only have NodeJS samples; if you're working on a different backend, feel free to port this code. | ||
|
||
To use this sample, please clone this using the following command. | ||
To use this sample, please clone the repository using the following command. | ||
|
||
``` | ||
git clone [email protected]:dyte-io/google-transcription.git | ||
|
@@ -50,7 +50,7 @@ Note: PRIVATE_KEY should be in a single line. Try picking the value from the ser | |
npm install | ||
``` | ||
|
||
This would automatically install @google-cloud/media-translation, @google-cloud/speech, and @google-cloud/translate. | ||
This would automatically install @google-cloud/speech, and @google-cloud/translate. | ||
|
||
``` | ||
npm run dev | ||
|