Currently tensors is handled by GstMeta. However it is only works within MAXIMUM number of Meta (currently which is 16) and due to this reason there is limitation to use. It could be better to use multiple push to srcs (header -> data -> footer) and could be parsed at the Tensors Demuxer using GstAdapter Class. It is more stable and Looks like more standardized way in gstreamer area.
Expected Result
Muxer with header -> data -> footer.
(header example:
--boundary
Content-Type: other/tensors
Content-Length: tensors buffer size
Content-DataType: unit8,uint8,uint8
Content-Dimentions: 3:200:200:1,3:200:200:1,3:200:200:1
Demuxer
. Using GstAdapter
. parsing header
. parsing data -> push src (sometimes pad)
Issue Description
Currently tensors is handled by GstMeta. However it is only works within MAXIMUM number of Meta (currently which is 16) and due to this reason there is limitation to use. It could be better to use multiple push to srcs (header -> data -> footer) and could be parsed at the Tensors Demuxer using GstAdapter Class. It is more stable and Looks like more standardized way in gstreamer area.
Expected Result
Muxer with header -> data -> footer. (header example: --boundary Content-Type: other/tensors Content-Length: tensors buffer size Content-DataType: unit8,uint8,uint8 Content-Dimentions: 3:200:200:1,3:200:200:1,3:200:200:1
Demuxer . Using GstAdapter . parsing header . parsing data -> push src (sometimes pad)