![]() ![]() The main important factor is making sure the different pipelines can’t get confused with each other. To set up your own pipeline, you can either piggy-back off the existing scripts with modifications to handle your extra camera(s), or copy the relevant/desired components of them and make that run through. start a gstreamer stream with the specified camera and parameters.if not, try to find a valid h264-encoded camera.check if those parameters are for a valid h264-encoded camera.To actually start the video stream, streamer.py runs a bash script start_video.sh, using either parameters that are passed in as command-line arguments, or by reading them in from a file vidformat.param. Note that stream failures are rare, so most of the time this is just chilling and making sure the stream is still available. Line 18 starts a ‘screen session’ (basically opens a new terminal and gives it a name so you can access it again later), and runs a script called streamer.py, which starts the video stream and monitors it - restarting the stream at most 5 seconds after it fails. Video is started on line 18 (if relevant, audio is started on line 22). It’s relevant here to look at how the bluerobotics companion computer sets up the existing pipeline. ![]() Setting up the pipeline Existing pipeline ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |