Closed tomlson2 closed 7 months ago
Can you clarify a bit more? Are you trying to use CreateMediaCapturePipeline or CreateMediaConcatenationPipeline API?
Can you clarify a bit more? Are you trying to use CreateMediaCapturePipeline or CreateMediaConcatenationPipeline API?
I am using both, but my problem seems to be with the CreateMediaConcatenationPipeline API.
In eventBridge.ts the startConcat function triggered by Amazon EventBridge (when the media capture pipeline ends) invokes the CreateMediaConcatenationPipeline. From my understanding, this should be storing the files in the concat bucket with the directory/file names in the same convention of the capture bucket, however it seems to be creating and storing these files under a new UID.
The clarification I need is where does the UID/Name come from for the items in the concat bucket?
Hopefully this illustrates my issue and the expected behavior a little better:
https://docs.aws.amazon.com/chime-sdk/latest/dg/concat-folder-structure.html
It's based on the media pipeline id.
https://docs.aws.amazon.com/chime-sdk/latest/dg/concat-folder-structure.html
It's based on the media pipeline id.
This is what I had originally understood, but following the trail of original media pipeline creation through the creation of the media concat pipeline, the concatenated files do not exist under the given media pipeline id.
Log showing the media pipeline id after creating a meeting / media pipeline:
createConcatPipelineParams log from the startConcat function (eventBridge.ts/post-call lambda):
No match in the concat bucket. The concatenated data does exist, but under a different unique id.
Can you check it against the concat pipeline id? That looks like the capture pipeline id.
The concat bucket directory/file names do not match neither the MeetingId (this is convention for the capture bucket) nor the initial MediaPipelineId returned from invoking the Media Pipeline. Is this an issue with the way that the CreateMediaCapturePipelineCommand works?