• launch/sample_application.launch
  • This is an example launch file for how a ROS application could use a kinesis_video_streamer
  • • node_config_file [default: $(find kinesis_video_streamer)/config/node_sample_configuration.yaml]
    • stream_config_file [default: $(find kinesis_video_streamer)/config/stream_sample_configuration.yaml]
• launch/kinesis_video_streamer.launch
  • This is an example launch file to use when you want to launch a Kinesis Video Streamer node. By default it starts up with a single stream, but the stream_count parameter can be adjusted and additional stream configuration files can be loaded. When loading additional configuration files, make sure to load them into an appropriate namespaces (monotonically increasing kinesis_video/stream). @param stream_config Configuration for the (first) stream. If provided, rosparam will attempt to load the file into the private namespace of the node. Otherwise, the example configuration file 'sample_configuration.yaml' will be loaded. @param aws_client_configuration/region Defaults to us-west-2. @param kinesis_video/stream_count Number of streams to load & transmit. Stream definition should be provided for each stream. @param kinesis_video/log4cplus_config Optional path for a log4cplus config which will be used by the Kinesis Video Producer SDK. @param kinesis_video/stream/ as described in https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/how-data.html#how-data-header-streamdefinition
  • • node_name [default: kinesis_video_streamer]
    • node_config_file [default: ]
    • stream_config_file [default: ]

No questions yet, you can ask one here.