- Newest
- Most votes
- Most comments
Please note that the default limits are per-region and us-east-1 allows 100 (not 10) concurrent media pipelines by default. The other regions are 10 each. https://docs.aws.amazon.com/chime-sdk/latest/dg/media-pipelines-limits.html
Also please note that these are just the default SOFT limits. These quotas can be adjusted to accommodate your business requirements. Please make a request through the Service Quotas page in the AWS Console.
For sending meeting audio to KVS, media capture pipelines are the appropriate solution and you should not let the default limit prevent you from proceeding with your application.
However, if you are only processing the audio for transcription, you will get better results using the native integration with Amazon Transcribe. The Amazon Chime SDK live transcription feature will manage this for you. (https://docs.aws.amazon.com/chime-sdk/latest/dg/meeting-transcription.html)
Yes, there is a recommended architectural pattern for your use case that doesn't rely on Chime Media Capture Pipelines. You can use the Amazon Chime SDK's audio analysis feature to stream audio directly from your WebRTC sessions to Amazon Kinesis Video Streams for real-time processing and transcription.
Here's a high-level overview of the recommended approach:
-
Host video meetings using the Amazon Chime SDK in your web application.
-
Utilize the SDK's audio analysis feature to send the WebRTC session audio to Amazon Kinesis Video Streams.
-
You have two options for streaming the audio: a. Send each attendee's audio stream to a separate Kinesis Video Stream for individual analysis. b. Send a single mixed-audio stream with the meeting's audio.
-
Once the audio is in Kinesis Video Streams, you can perform live analysis using AWS machine learning services, including real-time transcription.
This approach allows you to bypass the limitations of Media Capture Pipelines and support more than 10 concurrent meetings. It leverages managed AWS services as requested, utilizing the Amazon Chime SDK for video meetings and Kinesis Video Streams for audio processing.
For transcription, you can integrate Amazon Transcribe with your Kinesis Video Streams. The Amazon Chime SDK supports real-time meeting transcriptions through integration with Amazon Transcribe or Amazon Transcribe Medical. While this is typically done within the SDK, you can achieve a similar result by processing the audio streams from Kinesis Video Streams.
Keep in mind that audio sent to Kinesis typically uses a sampling rate of 8 kHz, which is suitable for transcription purposes.
To implement this solution, you'll need to:
- Set up your Amazon Chime SDK meetings in your web application.
- Implement the audio streaming to Kinesis Video Streams using the SDK's audio analysis feature.
- Configure your Kinesis Video Streams to receive the audio data.
- Set up Amazon Transcribe to process the audio streams from Kinesis Video Streams.
- Implement any additional downstream processing or storage of the transcription results.
This architecture should allow you to scale beyond the 10-meeting limit of Media Capture Pipelines while still leveraging managed AWS services for your real-time audio capture and transcription needs.
Sources
Video Chat SDK - Amazon Chime SDK Features -AWS
Using Amazon Chime SDK live transcription - Amazon Chime SDK
Plan for live media streaming from Amazon Connect to Kinesis Video Streams - Amazon Connect
Relevant content
- asked 2 years ago
- asked 2 months ago
If this is true, then how to do it without Chime Media Capture Pipelines? (as the requirement initially was) Every sample seems to rely on Chime Media Capture Pipelines.