You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The array of connection-map object provides a description of the media workflow DAG, i.e. the connection information between different tasks in the graph. (Subclause 8.4.1)
The input-ports and output-ports are described as follows:
The input-ports and output-ports objects specify the endpoints where the data is communicated from NBMP sources to tasks; and between tasks; and from tasks to NBMP sinks. (Subclause 8.2.1)
It's unclear to me what will ultimately define the DAG. My current understanding is that connection-map defines the DAG between tasks and input-ports and output-ports are only used to connect input and output streams to tasks and otherwise only describe available in-/output ports.
Assume the following workflow:
input -> normalize -> transcode720p -> output
Would the following WDD be a proper description (omitting some of the required fields)?
As a side question: Why is the function ID specified as part of the connection-map instead of in the function-restrictions. If one task has multiple connections, the function ID is repeated multiple times with possible inconsistencies.
The
connection-map
is described as follows:The
input-ports
andoutput-ports
are described as follows:It's unclear to me what will ultimately define the DAG. My current understanding is that
connection-map
defines the DAG between tasks andinput-ports
andoutput-ports
are only used to connect input and output streams to tasks and otherwise only describe available in-/output ports.Assume the following workflow:
Would the following WDD be a proper description (omitting some of the required fields)?
As a side question: Why is the function ID specified as part of the
connection-map
instead of in thefunction-restrictions
. If one task has multiple connections, the function ID is repeated multiple times with possible inconsistencies.The text was updated successfully, but these errors were encountered: