Giters

audioscience / avdecc-lib

Simple C++ library for implementing IEEE1722.1 (AVB Device Enumeration, Discovery and Control)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

AVDECC fast connect

radhika-sfo opened this issue · comments

commented

Hi,
I have done a few modifications to the AVDECC code to make it communicate with another vendor's AVB stack. The setup is like: OpenAVB stack is a listener and third party stack is the talker. The talker expects the listener to initiate a fast connect (or a mocked fast connect) to initiate data transfer. I could make the OpenAVB stack to send a fast connect, but it is sending only for the audio source from talker (talker_unique_id and listener_unique_id are 0, which is the audio source). How can I make the listener send TX_COMMAND_RESPONSE for both audio and video?
Note: I have added support for VIDEO_UNIT and VIDEO_CLUSTER in the AVDECC library.

commented

Assuming the audio and video are different streams, you would just send a CONNECT_RX_COMMAND to the listener side for the video stream and the listener will send a CONNECT_TX_COMMAND to the talker stream. You do have to set the correct unique IDs for both the listener and talker side in the CONNECT_RX_COMMAND.

commented

Thanks for the information, Andrew.
The audio and video streams are to be sent by a single talker, from a video file. I assume they are considered as two different streams, since the talker_stream_sources from the talker is shown as 2 (as per wireshark data).
I tried sending the CONNECT_RX_COMMAND with different unique ids, but the talker responded (with CONNECT_TX_RESPONSE) to the last one only and it sent the video stream.

commented

Does the talker advertise 2 talker streams?

commented

The talker is advertising three streams - including media clock. (value of talker_stream_sources) and listener advertises two streams (in listener_stream_sinks and capabilitiy includes audio and video).

One of my doubt is that if the listener has to support audio and video at the same time, do we have to specify two different ini files while running avdecc application? If this is the case, do I have to run two different openavb_harness / openavb_host client applications with these ini files?

Currently I am using the same ini files (h264_gst_listener.ini) to run avdecc and the client application. Is this ok?

commented

Hi Andrew,
This issue is resolved, hence I am closing this thread.
The AVDECC fast connect logic was modified so that the listener sends TX_COMMAND for both audio and video sources.