Currently setting up a Voxl 2 for DFS with Ardupilot and can read the proximity for the most part but think I have a lot of false positives... https://docs.modalai.com/dfs-qrb5165/ this page is a WiP so I was wondering if anyone found ideal tuning parameters for the config file to do obstacle avoidance with the QRB5165???

I noticed in the wifi setup that there's a note that says

Note: It’s not currently possible to assign a static IP, only DHCP is supported. If you need a static IP on your own wifi network it’s best to configure that in your router’s software.

I was wondering if this is still true today or if this was addressed in the new 1.0 SDK?

@Alex-Kushleyev Sounds good thanks for clarifying. Also, it looks like you can use a hybrid CQP and CBR mode per the documentation, but when I use "cbr+cqp" in the camera server conf file, it does not seem to like it. Is this feature not available yet?

I'm looking at the camera server documentation and this is saying that H265 essentially requires twice the bandwidth that H264 does. Isn't that backwards? Isn't H265 more efficient at the cost of latency? @Alex-Kushleyev

@bendraper said in streamer default h265:

@Eric-Katzfey Yea I think that functionality may be broken though. If I try to do the inverse aspect ratio, it just kinda shrinks the stream as opposed to stretching it back out

It's also seemingly fixed in the daily builds of QGC... Oh well

@Eric-Katzfey Yea I think that functionality may be broken though. If I try to do the inverse aspect ratio, it just kinda shrinks the stream as opposed to stretching it back out

@Alex-Kushleyev This is great, much appreciated! Also regarding that squished stream in QGC, seems to only be a linux thing so probably not much to do about it right now.

@Alex-Kushleyev Awesome. On a different note, do you know why ffmpeg has no issue with the aspect ratio of the stream but in QGroundControl, the stream seems to be vertically squished? I would guess ffmpeg correctly makes some assumptions about the aspect ratio that voxl-streamer doesn't outwardly declare and maybe QGC doesn't make these assumptions?

@Alex-Kushleyev Incredible, it works! Thanks Alex

@Alex-Kushleyev it's probably just my gstreamer ignorance and it not being as simple to set up an h265 stream as swapping our h264 with h265

@Alex-Kushleyev Thanks for getting back. Here's our fork of voxl-streamer and the specific commit

As you can see, not much going on here. I just noticed how the 265 omx encoder object would be created but just unused when encoding a raw stream (using hires_small_grey in my tests which is RAW8).

When I try to connect to the stream, streamer gives the following

voxl2-mini:~$ voxl-streamer -i hires_small_grey -s -b 2000000 -p 554
Waiting for pipe hires_small_grey to appear
Found Pipe
detected following stats from pipe:
w: 1024 h: 768 fps: 30 format: RAW8
Stream available at rtsp://127.0.0.1:554/live
A new client rtsp://169.254.4.2:40732(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally

and using ffmpeg to connect gives the following

ffplay version 4.4.2-0ubuntu0.22.04.1 Copyright (c) 2003-2021 the FFmpeg developers
  built with gcc 11 (Ubuntu 11.2.0-19ubuntu1)
  configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 70.100 / 56. 70.100
  libavcodec     58.134.100 / 58.134.100
  libavformat    58. 76.100 / 58. 76.100
  libavdevice    58. 13.100 / 58. 13.100
  libavfilter     7.110.100 /  7.110.100
  libswscale      5.  9.100 /  5.  9.100
  libswresample   3.  9.100 /  3.  9.100
  libpostproc    55.  9.100 / 55.  9.100
[rtsp @ 0x74e358000cc0] method DESCRIBE failed: 503 Service Unavailable
rtsp://169.254.4.1:554/live: Server returned 5XX Server Error reply

It looks like if you are to use voxl-streamer to encode a RAW8 pipe, it will default to encoding it in h264. Is there a way to change this to 265? I tried recompiling the service and editing the pipeline.c file to use the 265 encoder where applicable (and changed other mentions of 264 to 265) but the stream fails when I try to start it. Is there a simpler way to achieve what I'm trying to do that I'm missing?