I’ll try to outline some of my biggest likes and dislikes for each app in this article. Let’s begin with…
I think one of the most valuable features Litchi has going for it is the ability to design waypoint missions on the web using The Litchi Hub. I’ve included a screenshot of the Eastern portion of the example mission I’ll talk about below:
Each inverted purple teardrop is a waypoint. Each blue one is a Point of Interest. You can place and drag both kinds (waypoints and POIs) on the map with the computer’s mouse pointer (or your finger if you’re doing this on a touch screen). The white box on the right shows the settings for Waypoint #2. You can set the altitude, speed, curve size (if curved turns are enabled in global options), aircraft heading, reference point of interest, and gimbal pitch. Heading only matters if you have a camera that swivels independently (like the DJI Inspire). Otherwise, if you have a DJI Phantom series with a non-swiveling camera and you have any point of interest aiming going on, the aircraft heading (the direction the “nose” of the aircraft is pointing) will adjust to keep the camera aimed properly. This is true for both Litchi and Autopilot’s aircraft heading settings. Camera aiming changes heading constantly when the drone is in motion and maintaining a POI in the center of the camera’s view.
Being able to use my computer’s large monitor and precise mouse pointer to design missions is fast, easy, and very convenient. With Autopilot, all this mission design and more) must be done in the app on your Apple IOS device’s touch screen – using your fingers. This one feature is, for me, the largest advantage Litchi has over Autopilot… and I think it’s a biggie.
Another advantage Litchi has over Autopilot is its support for both IOS (Apple) and Android mobile devices. My tablet is an iPad, but my phone is a Samsung, so it’s nice to have the flexibility to use either one and still be able to use Litchi. I don’t know if I could have talked Litchi into giving me their app for one platform after I’d bought it on the other. I didn’t try. I bought the app twice. I’d love to hear if anyone successfully talked them into a “twofer!”
Litchi has other modes besides “waypoint” but I don’t use them enough to comment on them fairly. I’m after smooth cinematic shots that I can think about and plan in advance. That makes Litchi’s waypoint mode the one I’m almost exclusively interested in.
Autopilot is viewed as having a steeper learning curve than Litchi. That’s true if you want to know what every setting does and how to use it. But the largest difference that I see is one of conceptual design. With Litchi, all things happen at waypoints. Autopilot takes a different approach. It also has waypoints, but they’re almost completely concerned with aircraft position, altitude, and speed over the ground… and not much else. Autopilot adds two other kinds of markers you can add to your flight map: Focus Triggers and Camera Triggers. Think of them as “action at a location” markers… Another way to think of them might be “points along the course (defined by the waypoints) where other stuff happens.” Waypoints and Triggers can be located at the same spot – making Autopilot work more like Litchi.
Camera triggers are the least complicated and easiest to understand. With a camera trigger, you’re telling the camera to do something as the aircraft passes the camera trigger’s location… Start recording video. Stop recording video. Take a photograph. Things like that. Camera Triggers don’t have that many options and aren’t even necessary if you are going to start recording video when the mission starts and stop when the mission ends.
The next “action at a location” marker you can place along your route are called Focus Triggers. While Camera Triggers instruct the camera to do something, Focus Triggers instruct the camera to point somewhere. Here’s where a lot of the charges that Autopilot is complex are spawned. There’s a zillion ways (not really) you can instruct the gimbal and/or aircraft to aim the camera. Mastering Focus Triggers is essential for creating sequences containing complex moves. But there’s also a way to look at Focus Triggers the same way you commonly control camera aiming with Litchi. You can have a Focus Trigger that includes a Point of Interest (POI) marker that you can place on the map. POI’s work pretty much the same.
The really useful and powerful technique you can pull off with Focus Triggers involves interpolating the camera’s aiming as the aircraft flies between Focus Triggers. You can make transitions as rapidly or slowly as you like depending on how far apart you place two Focus Triggers that use interpolation between them. The first Focus Trigger (with the Interpolate setting on “Next”) tells the camera to “start the move to your new aiming point” while the second Focus Trigger (with the Interpolate setting on “Previous”) says “by the time you get here, the camera will have it’s new aiming point in the center of the field of view.” The further apart you place these two Focus Triggers, the more slowly the “move” takes place.
Remember that Focus Triggers have only to do with the camera’s aim. You can have all kinds of other stuff happening with the aircraft using Waypoints – changes in speed, altitude, course, or all of the above – and the camera will continue to maintain or adjust its aim based only on what the Focus Triggers tell it. This decoupling of aircraft movements and camera aiming is at the heart of what makes Autopilot so flexible and powerful.
Here’s a screenshot of my iPad with the Eastern portion of the Autopilot Waypoint mission in view:
The blue teardrops are Waypoints… locations where the aircraft’s course over the ground, altitude, or speed change.
The green circles are Focus Triggers… places where the camera’s aim point changes (no interpolation)… or begins to change (interpolation “next”)… or completes changing (interpolation “previous”) or for that matter changes the way the aim point is changing (interpolation “previous and next”). The green Focus Point circles have plus signs on the right to indicate “Interpolate Next” and minus signs on the left to indicate “Interpolate Previous.”
The blue circles are used to split a segment of the course line and insert a new waypoint. You’ll also notice that the curved path in Autopilot looks different than the curved paths in Litchi. That’s because I selected a special kind of curved path that Autopilot offers called “Bezier Curves” (pronounced “Bez-yay”). They make the curved path less like a radius of a circle and more natural looking (I think).
To give you a quick glance at waypoint settings, here’s a screen shot of “Waypoint 2” on the map:
You see there aren’t that many settings – even when displaying the “advanced” level of detail. One thing to keep in mind… Waypoint settings are Interpolative all the time… meaning that if waypoint 8 says 10 MPH at 100 feet altitude and the next waypoint (9) says 20 MPH at 200 feet altitude – the aircraft will cross waypoint 8 at 100 feed and 10 MPH. Then it will immediately start climbing and speeding up after passing waypoint 8 so that when it crosses waypoint 9, it will be at 200 feet and going 20 miles an hour. Not knowing this can lead to unexpected behavior (and even obstacle troubles!)
If you make big changes in altitude between waypoints that are close together, the aircraft can easily be asked to perform more radical maneuvers than it’s capable of (or that is consistent with safety). In this case, the aircraft will simply stop at a waypoint and complete a safe vertical ascent or descent to the desired altitude… and then continue its horizontal movements.
Although I seldom use them, Waypoint Actions are always available in Autopilot when in “cool features enabled” mode. They include commands to “Hover for x seconds,” “Ascend or Descend vertically to a specified altitude,” and “Take a Panorama of photos”… or combinations of these.
Now let’s take a look at some Focus Trigger settings:
You have lots of options here. Especially with the “advanced” settings displayed. However, if you keep thinking logically and do some reading and experimenting, it will all make sense.
Let’s go through the example above:
The first setting is the Focus Strategy and it’s set to “Subject.” We’ll say what the subject is in the next setting. In this case the subject is a “Waypoint” which can be a little confusing. The options amount to: “Use a previous POI marker”, “Focus on the ‘operator’ ” or “Create a new POI marker for me to place somewhere.”
The Altitude slider sets the estimated altitude of your point of interest. The top of a water tower rather than the base for example.
Interpolation we’ve talked about already.
Reference Focus Trigger let’s you “borrow” another Focus Trigger’s point of interest marker and use it – instead of creating another one in the same spot.
An aside: I don’t want to open a whole new can of worms here, but the “operator” option has a cousin that’s not displayed called “Airspace“. Autopilot has a free “Airspace” app you can use with tablets and phones. Multiple aircraft can also join the same Airspace. So long as all the airspace objects have a network connection, they can become the aiming point for the camera. So one drone can automatically maintain its camera aim at another drone or can focus on a person or vehicle carrying a GPS equipped mobile device running the Airspace app. You can hand out Airspace-running mobile devices to multiple people and use focus triggers to switch between the one the camera is tracking. Airspace can also be used in Autopilot’s “real time” (i.e. not pre-planned waypoint) modes. Autopilot has the same visual tracking capabilities that Litchi (and DJI Go for some aircraft) have. But Airspace is FAR more reliable and immune to things like trees getting in the way… causing visual tracking to get lost.
See for Yourself
The videos below show Litchi and Autopilot flying missions that are nearly identical in design. I flew the Autopilot mission in “cool features enabled” mode and had a signal loss right as the aircraft was starting for home near the end of the mission. So what you see at the end of the Autopilot video is me flying home by hand. Both videos are 30 FPS and 4K. Both were post-processed in Adobe Premiere and have color grading adjustment layers applied prior to the final render. The music is legit to use on YouTube and elsewhere in public. The right to use comes from my subscription to Audoblocks.com.
Here’s the Litchi-controlled mission:
Here’s the Autopilot-controlled one:
The idea to compare the two with similar missions didn’t occur to me till after I’d flown the Autopilot mission so you’ll see some minor tweaks between the two based on what I saw in the video after the Autopilot run was over and I looked at the video on a big screen.
I’ll admit up front that I didn’t design this mission to draw a huge contrast between Litchi and Autopilot by employing big, complex moves that Litchi can’t do – or only does with some difficulty. It’s intended to be a representation of a common mission with a common goal. In that environment, I think both apps performed quite well!
Feel free to share with friends using share buttons above and below the article. Share your thoughts with other readers using the Comments section below. I’d be interested to hear your thoughts!