AES67LiteHostInterface.h header file related issues

[Shurehon]

Hello, I would like to ask if the contents of the header file \ OCAMicro \ src \ common \ HostInterface Lite \ OCA \ AES67 \
AES67LiteHostInterface.h are all related to the aes67 protocol. Did I not find the relevant code implementation or do I need to find the source code implementation of aes67 myself.

[tljdebrouwer]

Hi @Shurehon we don't supply the AES67 implementation, only the control of it.

The AES67 hostinterface provides the hooks between OCA and AES67 and should be forwarded to your AES67 implementation.

Hope that helps.

[Shurehon]

Okay, I understand. Thanks for your reply.

[Shurehon]

Hello, I would like to ask if there are regulations in the standard that allow the use of multiple control terminals to control (one or more) OCA devices. Will there be conflicts between the control terminals, or is there an exclusive logic between them

[tljdebrouwer]

@Shurehon there is the possibility for a controller to lock an object (or a whole device). This does give the controller exclusive control over that object.

However generally you would like to use the change subscription mechanism, so that 1 controller is informed about changes of another controller and a such can update its status

[Shurehon]

Thanks a lot for your reply！
When I implement the hook functions related to the aes67hostinterface, it involves obtaining the number of channels, obtaining the ID of the stream, or obtaining the number of slots in the stream. Are these interfaces related to hardware drivers? For example, when obtaining the number of channels, do I need to obtain it from the SDP information, or do I need to obtain it from the driver or configuration file, or neither? Can you give me some guidance？