- Más nuevo
- Más votos
- Más comentarios
In order to create media concatenation pipeline we use Media capture pipelines capture the contents of a meeting by chunking the media streams and storing those artifacts in your S3 bucket and Media concatenation pipelines allow you to concatenate each type of artifact into a single file, and then store those larger files in your S3 bucket. You can create a media concatenation pipeline without waiting for the media capture event to end, but the concatenation pipeline only starts concatenating when the capture pipeline stops.
Please refer the architecture of the Concatenation pipeline: https://docs.aws.amazon.com/chime-sdk/latest/dg/concat-architecture.html
Please refer the documentation to create an Amazon Chime SDK media concatenation pipeline: https://docs.aws.amazon.com/chime-sdk/latest/dg/create-concat-pipe-steps.html
The Amazon S3 buckets for media concatenation pipelines use this folder structure.
S3 bucket path/
audio
video
data-channel
meeting-events
transcription-messages
Please refer the GitHub page chimeSDKMediaPipelines.createMediaConcatenationPipeline
https://github.com/aws/amazon-chime-sdk-js/issues/2531 which helps in the creation of the media concatenation pipeline.
Here is the Update from AWS Service Team,
I've received an update from the service team that the service team is working on fixing the issue. They will be fixing it soon and releasing it.
The issue seems to occur in files which are lesser in size. The service team is actively working on fixing it. Please note I've received an update that service team has already fixed the issue but it is still in the testing phase. I can assure you that they will be releasing the fix within a few days.
I would not be able to provide a specific ETA for the resolution of the issue by our internal team but be rest assured that I understand the severity of use case which is captured in my escalation. The service fixing it soon.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
@Govind: I have read all these documents and followed all the steps. As I clearly mentioned concat API works for recordings which are started and stopped once and twice per meeting but fails when the recording is started and stopped multiple times in the same meeting.
For example: Recording 1: Started at 00:10 and ends at 00:50 Recording 2: Started at 01:00 and end at 1:30 Recording 3: Started at 1:40 and end at 2:00
This produces 3 sets of chunks in the same folder in S3. However concat fails in this scenario. However, if the recording was started and stopped only once and twice then there is no issue.