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
To connect to a live stream, the MISB UAS driver has two connection parameters that specify a TCP endpoint in its configuration class: serverIpAddress and serverIpPort.
It would be more flexible to change the configuration class to just have one String property called something like "connectionString". This would allow you to use the full flexibility of libavformat's available protocols. For example, it would allow you to stream from an HTTP(S) source using an https URL string.
The new configuration class might be modified something like this:
packageorg.sensorhub.misb.stanag4609.comm;
publicclassConnection {
// ... other stuff ...// Replacement for serverIpAddress and serverIpPort.// String that is passed to ffmpeg to tell it where to get streamed data.// https://www.ffmpeg.org/ffmpeg-protocols.html@DisplayInfo(label = "Connection String", desc = "Connection string that ffmpeg will use to connect to a MISB STANAG 4609 MPEG-TS stream")
publicStringconnectionString;
}
This would not be backwards compatible with existing configuration. But affected deployments would be trivially easy to update.
The text was updated successfully, but these errors were encountered:
To connect to a live stream, the MISB UAS driver has two connection parameters that specify a TCP endpoint in its configuration class:
serverIpAddress
andserverIpPort
.When the driver is started, the IP and port are just mashed together into one string with a ":" separator that ultimately gets passed directly to the ffmpeg libavformat library.
It would be more flexible to change the configuration class to just have one
String
property called something like "connectionString
". This would allow you to use the full flexibility of libavformat's available protocols. For example, it would allow you to stream from an HTTP(S) source using anhttps
URL string.The new configuration class might be modified something like this:
This would not be backwards compatible with existing configuration. But affected deployments would be trivially easy to update.
The text was updated successfully, but these errors were encountered: