You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Added attachment to CVPixelBuffer disappearing on receiver side.
To Reproduce
Steps to reproduce the behavior:
Create a custom video processor to access CVPixelBuffer
Create a custom video renderer view to be able to receive CVPixelBuffer
Edit sending buffer by adding personal metadata to attachments property or via CVBufferSetAttachment function
On receiver side try to get this attachment
Expected behavior CVPixelBuffer attachments should not be removed or AWS Chime SDK should have a possibility to add metadata to VideoFrame
Test environment Info (please complete the following information):
Version AmazonChimeSDK: 0.19.2
Version AmazonChimeSDKMedia: 0.15.2
Can you reproduce this in the demo app? yes
Additional context
In general looks like pixel buffer is completely transformed by chime on server side, cause even some system attachments is not stored as well.
The text was updated successfully, but these errors were encountered:
Hi Thank you for opening the issue. We don't transmit all additional meta data from video to remote. I will add feature request label to transmit metadata for video frame.
Describe the bug
Added attachment to
CVPixelBuffer
disappearing on receiver side.To Reproduce
Steps to reproduce the behavior:
CVPixelBuffer
CVPixelBuffer
attachments
property or viaCVBufferSetAttachment
functionExpected behavior
CVPixelBuffer
attachments should not be removed or AWS Chime SDK should have a possibility to add metadata toVideoFrame
Test environment Info (please complete the following information):
Additional context
In general looks like pixel buffer is completely transformed by chime on server side, cause even some system attachments is not stored as well.
The text was updated successfully, but these errors were encountered: