Mathieu Duponchelle

> There is a [stream_identifer](https://github.com/aws/aws-cdi-sdk/blob/57ce52b0dfd68a6d2bea3a9e397886c801c28b08/include/cdi_avm_api.h#L140) that is associated with each payload and is set by the transmitter. This value can then be used by the receiver to re-associate the video...

I see OK. Well my suggestion would be to transmit ancillary data tightly coupled with the video data it is associated with, and to preserve that coupling for the receiver...

@mhhen to be clear, is order of delivery of payload data guaranteed?

> Correct. The order of delivery for payloads matches the order the calls to send payloads were made for an endpoint. The payloads are placed into a [queue](https://github.com/aws/aws-cdi-sdk/blob/2627db1fa8bee2e7ccb3de1742b19954d58cfa36/src/cdi/internal_tx.c#L799) and are...

> A proposal concerning the coupling of the video and ancillary data API would be great! Or even better, submit in the form of a pull-request. That's a bit above...

OK, I suppose this guarantee will have to do. Note that another one of my suggestions still stands @ https://github.com/aws/aws-cdi-sdk/issues/95 , the ability to instantiate any number of adapters would...

@jacobgkau I don't have more information than what's in the mail thread I linked, but I assume this is on third-party hardware.