It took me some time to figure out where this |RtmpSampleAccess packet came from. It turns out that this is an undocumented AMF packet that is used to transfer the state of the documented Client.audioSampleAccess and Client.videoSampleAccess state to the client.
This post gave me some clues: https://nicolas.brousse.info/blog/flash-how-to-fix-the-security-sandbox-violation-bitmapdata-draw/ These sampleAccess states are used to allow a (Flash) client to access the raw video and audio data. The states are pushed by the server as a IRtmpSampleAccess packet. Adobe FMS, Wowza, Red5, etc… all support this mechanism. I’m able to reproduce this issue with RTMP streams pulled from a Nginx-RTMP server (https://github.com/arut/nginx-rtmp-module). Client.audioSampleAccess and Client.videoSampleAccess are documented here: https://helpx.adobe.com/adobe-media-server/ssaslr/client-class.html#client_audiosampleaccess https://helpx.adobe.com/adobe-media-server/ssaslr/client-class.html#client_videosampleaccess Best, Peter On 18 Aug 2020, 14:46 +0200, Michael Niedermayer <mich...@niedermayer.cc>, wrote: > > Do you have a testcase? > Is this documented somewhere? > > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > In a rich man's house there is no place to spit but his face. > -- Diogenes of Sinope > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
