✨ add a way to specify the connectionSpec in the bundle configuration
Summary
In order to configure the Executor
quiddity, as this one is very generic and could expose arbitrary connectionSpec we must provide an interface that will configure these connectionSpec for the quiddity Executor
in priority but it seems a general feature for all other bendles.
How would you like the feature to work ?
We add an entry connectionSpec
in the bundle configuration that will replace the default connectionSpec
when the quiddity is instanciated.
So, the bundles should be like this:
{
"bundle": {
"ndiInput": {
"pipeline": "executor name=Executor <add_to_start _whitelist_caps _autostart=false _periodic=false _restart_on_change & watcher name=Watcher <add_to_start <shmw _create_directory=true",
"connectionSpec": {
"writer": [{
"label": "audio",
"description": "Audio stream",
"can_do": ["audio/x-raw"]
}, {
"label": "video",
"description": "Video stream",
"can_do": ["video/x-raw"]
}]
},
"doc": {
"long_name": "NDI® input",
"category": "network",
"tags": "writer",
"description": "NewTek NDI® stream from local network"
}
},
"ndiOutput": {
"pipeline": "executor name=NDI <top_level <shmr _whitelist_caps=audio/x-raw,video/x-raw _autostart=false _periodic=false _restart_on_change=true",
"connectionSpec": {
"follower": [{
"label": "audio",
"description": "Audio stream",
"can_do": ["audio/x-raw"]
}, {
"label": "video",
"description": "Video stream",
"can_do": ["video/x-raw"]
}]
},
"doc": {
"long_name": "NDI® output",
"category": "network",
"tags": "reader",
"description": "NewTek NDI® send to local network"
}
}
}
Why is this feature important to you ?
It is a requirement for the use of the ndiInput
and ndiOutput
quiddities.
Impact of non completion
We can't use NDI in Scenic 4.1.
Edited by Valentin Laurent