Update audio and video service with camera manager

[Williangalvani]

I just tested this starting from the 0.0.21 image.

steps:

• flash image
• boot
• git fetch origin pull/339/head:pr339 && git checkout pr339

• nano update.sh:

  sudo apt install -y python3-pip
  sudo python3 $HOME/companion/services/network/setup.py install
  
  # camera-manager
  ## Install gst-rtsp-server
  cd /tmp
  [ ! -d gst-rtsp-server ] && git clone git://anongit.freedesktop.org/git/gstreamer/gst-rtsp-server
  cd gst-rtsp-server
  git checkout -t origin/1.8
  git pull
  ./autogen.sh --disable-gtk-doc
  make -j4 && sudo make -j4 install
  cd $HOME/companion
  
  # Add LD_LIBRARY_PATH for screen
  echo "setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH" >> $HOME/.screenrc
  
  echo "Kill running gst-launch..."
  sudo pkill -9 -f gst-launch
  echo "Converting old video settings file."
  python3 $HOME/companion/tools/convert-old-video-settings-file.py
  
  # Enable bcm module for camera on boot
  ## Make sure that there is only a line with this module
  sudo sed -i "/bcm2835-v4l/d" /etc/modules
  echo "bcm2835-v4l2" | sudo tee -a /etc/modules

• sh update.sh
• cd br-webui
• npm update
• reboot

I have video but the camera page is not populated (all selects are empty)

[patrickelectric]

@Williangalvani what you mean by camera page ? QGC or companion ? Can you send a picture ?

[Williangalvani]

@Williangalvani what you mean by camera page ? QGC or companion ? Can you send a picture ?

I also didn't see any calls to the backend, did you accidentally drop something?

[Williangalvani]

Tried again, same steps. Started with qgc stable. After reboot I had video for a few seconds and then lost it. /camera shows rtsp selected, changing to udp did nothing. changed back to rtsp: rtsp had weird aspect ratio again (image centralized using 50% of the available space) changed to udp in browser: had to change in qgc aswell, but now qgc shows video artifacts which lead me to believe it is received two of the same streams at the same port.

with qgc master: Alternating between stream types sometimes fails in qgc. changing to udp causes the same weird artifacts I mentioned before (stream is in slowmotion and full of artifacts)

rtsp streams are also showing these artifacts at the lower right:

also relevant log from qgc:

VideoReceiverLog: Starting decoding "rtsp://192.168.2.2:8554/video1"
VideoReceiverLog: GStreamer error: Could not open resource for reading and writing.
VideoReceiverLog: Stopping because of error
VideoReceiverLog: Stopping "rtsp://192.168.2.2:8554/video1"
Camera "name" stopped transmitting. Removing from list.
VideoManagerLog: Restart video streaming 0
VideoManagerLog: Restart video streaming 1
VideoReceiverLog: Streaming did not start "rtsp://192.168.2.2:8554/video1"
VideoReceiverLog: Stopped "rtsp://192.168.2.2:8554/video1"
VideoReceiverLog: Stopping "rtsp://192.168.2.2:8554/video1"
VideoReceiverLog: Stopped "rtsp://192.168.2.2:8554/video1"
CameraManagerLog: Hearbeat from  100
CameraManagerLog: _requestCameraInfo( 100 )
CameraManagerLog: _requestCameraInfo( 100 )
CameraManagerLog: _requestCameraInfo( 100 )
CameraManagerLog: _requestCameraInfo( 100 )
CameraManagerLog: _requestCameraInfo( 100 )
Giving up requesting camera info from 1 100

[patrickelectric]

@Williangalvani Try to use gst source directly from the terminal or a stable version of QGC, I'm using the last table appimage available I have seen such problems here

[patrickelectric]

I was able to replicate both problems: The UDP problem was a missing sync in the udp multudpsink pipeline The RTSP rectangle is a result of the RTSP streaming as faster as it can, I have added a h264parse to avoid such problem.

[patrickelectric]

@Williangalvani I did the same steps without the update.sh (that's not necessary) and with npm install in place of npm update. Everything appears to be working without issues here.

I'll flash your sdcard and see if the problem was during your manual installation or a fault of the sdcard

[jaxxzer]

@Williangalvani @patrickelectric The way I recommend to test something like this:

git fetch origin pull/339/head:pr339
git tag 0.0.22 pr339

• go to /git page
• choose local/tags/0.0.22
• click update

This will make sure an update is done in the same manner as when it's performed from the /system page after we push a new stable tag

alternatively, push the tag to your github fork, then add your fork as a remote from the github page, and you can skip the command line fetch/tag

[jaxxzer]

I updated with the steps described above, this is the output in the console on the /system page: https://pastebin.com/JTK6vf0F

Make failed, see line 459