Mid-March 2017 Release of APSync

@peterbarker wrote:

I've just changed the links on the firmware server to reference new images for APSync.

I've also pushed up the relevant changes to the build instructions and scripts to the github master repo.

So that's what a release for APSync looks like!

Here are the release notes:

Release 201703

 - RPi is based on 2017-03-02-raspbian-jessie-lite.zip
 - "niceties" like strace, tcpdump installed by default
 - cmavnode now does the 14550 broadcast
 - MAVProxy is no longer started by default
 - video streaming is automatically started to first connector to :14550
 - release files:
  - apsync-rpi-20170314110804.img.xz
  - apsync-tx1-201703141027.img.xz
  - apsync-edison-20170316114410.tar.xz

I believe the change in there which is going to be of most interest to people is the "starts streaming video automatically" change. I've had several reports of out-of-the-box success already, which is awesome! There is a major caveat with this functionality, however: the script which starts the video stream is extremely limited in functionality. On RPi3 it streams the board camera (v2) only. On TX1 it encodes the first video device it finds using hardware acceleration. Edison uses software encoding for the first video device found, and is a slide-show.

If your camera does not work out of the box, you will need to modify the "start_udp_stream" script on the input and encoding sides. Notably, I have had great success on Edison using h.264-encoding cameras; both the LogiTech C920 (not the C930!), and a random camera I picked up off Ali-Express (https://www.aliexpress.com/item/USB2-0-1080P-full-HD-usb-Camera-Module-with-H264-Output-audio-mic-microphone-UVC-for/32424848584.html?spm=2114.13010608.0.0.Df1A69).

Second caveat: we don't change the video stream once it is in motion. If you change GCS you will need to CC.

Enjoy, and please report on both successes and failures!

Posts: 2

Participants: 1

Read full topic