Drone My Roof Part 3

As I wrote about in Drone My Roof and Drone My Roof Part 2, I was getting my roof redone at great expense, and I was determined to get a good time lapse of the whole process. As I said in Part 2, I made a circular waypoint track. At semi-regular intervals I went out and flew it twice. My intention was that for each time I flew, I’d use some non-integer number of circles. I wasn’t sure if I’d use 7/8ths of a circle or 9/8ths of a circle, but I thought it would be more interesting that doing one full circle each time. Which is why I did two circles, and also why I had the circles start at the back of the house instead of the front. (Actually, I forget why I chose starting at the back, but because I was going to do a non-integer number of circles I didn’t think it would matter).

For about a day and a half I didn’t think to put starting and stopping the camera into the waypoint file, so there was a bit of a bobble around the back of the house as the drone decided that it needed to turn 45 degrees and possibly move a bit while moving from the end waypoint to the beginning of the next, even though they had the exact same latitude and longitude. I had to edit those bobbles out, to greater or lesser success each time. The last 3 or 4 missions didn’t have the bobble, which was a great relief.

I sped up each clip by 4x, so that it was obvious it was a time lapse. I also added the start time of each clip as a caption.

The other thing I discovered is that even though the drone is tracking 20-odd GPS satellites at once, there were significant differences between different circles. Usually not much between the two circles in one go, but between one mission and the next, sometimes 5 or more meters difference. Which I find a bit odd, because my first gps, a Garmin GPSMAP 195 which only tracked 12 satellites at once, could quite consistently show you which lane you were in when you used it in the car (in spite of it being an aviation GPS). And my Garmin Forerunner 920XT fitness watch could show which side of the river you were on.

As well as the problem with the circles being offset, the center point also meandered around – I had to save a new one several times. Unfortunately the KMZ file only saves center points that are in-use, so you can’t go back to an old one if you save a new one. It’s confusing, because during the session, you can have multiple center points saved, but after you come back to the waypoint file, all the ones that aren’t actually in use are gone.

I did some messing around in Final Cut Pro trying to get something usable out of this. A while ago I used a weird trick I’d found on Reddit’s r/finalcutpro sub-reddit to center a tracked object on the screen, involving inverting the clip, tracking the object, and then applying that to the non-inverted clip. Unfortunately there wasn’t a trackable object in the middle of the roof, so I was wondering if there was a way I could track the four corners of the house and do some sort of geometric mean on that. r/finalcutpro was not much help with that, but suggested I ask in r/vfx but they used a lot of terminology that I didn’t understand. Something about a gaussian splat or something like that.

So I decided on two things. First is that I’d do a single circle each time, starting from the more logical front of the house. Second is that I’d try to hide how badly the waypoint moved around from time to time by using a transition that had a lot of movement in it.

First attempt at editing

Then as a second attempt, I zoomed in 25 percent, and tried to use the slop to center the images a bit better. I did that by using some guide lines on the screen and setting a keyframe at each cardinal point and moving it as close to centered at each point. But there wasn’t enough leeway in the video – many of the positions I couldn’t get the roof centered without having black bars on the outside.

Second attempt at editing

Not perfect, but I think it’s better than the first attempt.

So lessons learned:

  • Make the waypoint file go full circle or maybe two circles without stopping, starting at the front of the house.
  • Make the circle further out or use a wide angle lens so there’s more slop on the edges for cutting in.
  • I think I’d fly slower and speed it up more – I like the frenetic movements. I know I said in Part 2 that I didn’t like it that way, but I’m having second thoughts.
  • Be more careful about launching the drone at exactly the same place each time – some of the worst offsets were the times I had to launch at somewhere other than the exact spot on the sidewalk I’d chosen for most of them. In one extreme case I had to take off the screen window and fly it out the door.
Flying from my doorway

Drone My Roof Part 2

So in the last blog post I left off with wanting to do some manual editing of the waypoint file. The first thing I had to do was grab the KMZ file from the controller. The controller is an Android device, and I have two programs that are supposed to allow you to connect to Android devices on your Mac. I’ve had inconsistent results getting these connections to work. One of the programs, OpenMTP, warns you to close the background tasks from Google Drive and Dropbox and Android File Manager before it will be able to connect. And by trying various combinations of doing that, rebooting the computer, rebooting the controller, I was able to connect a few times.

The waypoint file is a KMZ file, which is actually a zip file containing two files, template.kml and waylines.kml. They’re both relatively straight forward XML files. You can figure out most of the syntax just by looking at one of the files you’ve downloaded from the controller. So after I got a connection to my controller, I grabbed one of the KMZ files, extracted the waylines.kml file to copy the first “<Placemark>” to the end of the “<Folder>” and change the “<wpml:index>” tag from 0 to 17. I refreshed the file in the KMZ file and uploaded it to the controller.

This gave me a full circle that returned to the start, which made it much closer to what I wanted. I still get a little bobble when I restart – even though it’s moving from point A to point A, it still has to turn the drone about 45 degrees and then back, for some reason. Also I decided that since I’d decided to change from shooting a hyperlapse to a sped-up video, the drone was moving too slowly. Also it looked like the gimbal angle was down too far, so the roof was not the center of the video. I made the changes to the waylines.kml file to support that – I changed all the “<wpml:waypointSpeed>" from 0.213… to 0.852 (meters/second). and I changed all the “<wpml:waypointPoiPoint>” so the third argument (the height) changed from 3.0 to 5.0 (meters above ground). But then I had a multi-hour long struggle to try to get the damn controller connected to my Mac. Eventually I gave up, and tried my ancient Windows laptop. I don’t know why, but I thought Windows had native support for Android. But before I could even try, I discovered that since the last time I used it, it’s decided that it no longer has any drivers for the WiFi or Ethernet controllers. I presume that’s something to do with the fact that it’s Windows 10, and it’s ineligible for upgrade to Windows 11. Not that I could, without a network connection. So I guess it’s going off to electronic recycling. Pity.

But as I was coming to terms with the fact that the laptop I “borrowed” from a former employer is no longer working, I glimpsed a USB A to USB C port handing off one of the front USB ports on my Linux box. I use the Linux box from the command line all the time, but I figured for this I’d probably need to be in the GUI. So I logged into KDE, and plugged the controller in. And it immediately popped up a Dolphin file manager window showing all the files in the controller. So I was able to do those changes. What a change to find something that’s easier in Linux than on the Mac.

I did a couple of test flights this morning. At first, the one bit of XML I wasn’t sure about, the command for what to do at the end of the waypoint flight, wasn’t set right. Fortunately you can do that easily on the controller. After those first two flights, I wasn’t happy with where the drone was pointing. I decided to edit the POI on the controller, and did two more circles and I think it came out just about perfect. I suppose I could make another edit and duplicate “<Placemark>“s 2-16 at the end so it can do two circles without having to restart, but I’m kind of running out of time. And what I’ve got now is pretty good, especially after I speed it up in Final Cut Pro X.

Drone My Roof

So we signed a contract last week to get a new roof done on our house. It’s going to be ridiculously expensive, and both Vicki and I have had moments of self-doubt about committing to this. But one thing I wanted to get out of this, as well as “not having water leaking inside the walls that we don’t discover until the plaster starts failing”, is a great drone video.

One thing I’ve seen before, and what I want to emulate, is a video where the drone flies circles around the house being worked on, but with it doing it as a sort of time lapse, maybe taking a flight every hour or so while the work goes on. In my mind, I see it as doing about a turn and a quarter to a turn and a half, and then fading into the next flight, and so on.

My first problem is getting it to do consistent circles. The problem is that the DJI Air 3 can do waypoint flights, but there isn’t a “do a circle at this distance from this POI” waypoint option. I found a site that would generate a bunch of points to define a flight around a point, but it ends the flight at the 16th point, rather than completing the flight back to the start. When you edit the waypoint flight on the controller, you have options for what to do at the end of the flight, and one of the options is to fly to the start point. Jackpot, you might think. But no, when it does, the drone points toward the final point, and flies towards it, instead of sidestepping to it. I got a smoother and more complete circle using the QuickShots circle, but since you have to highlight an object to circle around with your finger on the screen, I have worries about how repeatable it will be.

My second problem is that originally I was thinking in terms of doing a hyperlapse. The waypoint editor in the Hyperlapse is simpler than the main waypoint editor for some stupid reason – you can’t define a POI to point the camera at, for instance. The instructions for the site that generates the waypoint file involve you connecting the controller to your computer and copying the KML file on top of another waypoint file. But I haven’t seen any instructions on how to do that with the waypoint editor in Hyperlapse. So I’ve been experimenting with the timed exposure mode where it just takes a photo every two seconds and then I combine them into a video in Final Cut Pro X. For my first several tests, I was trying to use manual exposure so I could use a really slow shutter speed to get a tiny bit of motion blur. But yesterday when I was doing these experiments it was partially cloudy, and every time the sun peaked out from behind a cloud the exposure blew out. I even tried pre-processing all the frames through Adobe Photoshop Elements and that helped, but that didn’t fix the blow out. In retrospect I probably should have set the exposure when the sun was out.

Today I tried again, but this time I used automatic exposure. I think the results were better. But again, today was sunny with a few clouds, so it was probably a simpler exposure problem. When clouds came over, it did get a bit darker.

The third problem was that when you create a hyperlapse in Final Cut Pro, the video isn’t stabilized. Weirdly, in Final Cut Pro X you can’t stabilize a compound clip, you have to export it as a video, re-import it, and then stabilize the newly imported video. And it’s been pretty windy while I’ve been doing these tests, so even with the stabilization, the resulting video was not very stable. I was starting to get less in love with the idea of a hyperlapse. I’m starting to think that what I want to do is shoot a video, and then speed it up. I tried that out (with a QuickShots circle) and I really like the result – the video is very smooth, and it had much more consistent exposure.

So all I have to do is solve the problem of making a waypoint file with a double circle, and make it repeatable. I’m hoping I might be able to edit the XML of the KML file manually. I guess that’s tomorrow’s testing.

More Linux techie bullcrap

My Linux box has a M2 NVME drive with standard stuff, but bigger files go on two hard drives in a RAID1 (mirrored). A few months ago, one of the drives fell off the RAID, which usually means it failed. Luckily when one drive fails in a RAID1, the content continues to be available.

At that time, I just bought a new drive, swapped it in for the old one, and then added it to the RAID and then it automatically resynchronized. No muss, no fuss, no bother.

But a few days ago, I noticed that the SMART monitor on the other hard drive was showing some errors. I guess it makes sense that if one drive fails after 6 years, it’s not too surprising that the other one does as well. It hadn’t failed off the RAID yet, but I figured I’d be proactive. I ordered a new hard drive, figuring it would be as simple as last time.

And of course, this time it wasn’t that simple. After swapping the drive, the box wouldn’t boot, because the BIOS didn’t recognize the M2 NVME drive as a bootable drive. It showed up in the NVME configuration menu of the BIOS, but I couldn’t add it to the boot menu. I tried the “update the BIOS over the network using a PXE boot, but it just hung up and didn’t work. But that option had put the PXE boot options in the boot priority menu, and wouldn’t let me add anything else until I disabled all boot options. So I fiddled a few BIOS configurations (I think I turned off support for some AMI special NVME mode and turned on some boot thing that I had no idea about), and rebooted, and this time it booted. But now the command I used last time, mdadm /dev/md0 --add /dev/sdb failed because the RAID was inactive. So after a bit of googling and a bit of experimenting, I found the combination that worked:

mdadm -A --run /dev/md0 /dev/sda
mdadm /dev/md0 --add /dev/sdb

The first command re-assembled the RAID with just the first drive in it, and the run option to make it make it active even though it doesn’t have both drives. The second command then adds the second drive. I couldn’t put both drives in the first command because when I tried it said that the new drive wasn’t formatted or whatever for RAID.

So now the RAID is happily resynchronizing and I’ve got no SMART errors showing up in my munin console. So all is right in the world. Now if only I could convert the RAID box I have on my Mac Studio from a RAID0 (interleaved for maximum speed) to a RAID5 (safer for long term storage) without paying $150 for a new license for SoftRAID.

Linux Upgrades

Both my home server, and my VPS (Virtual Private Server) need updates. My home server uses Kubuntu 22.04 LTS, and the current version is 25.04 (or 24.04 if I want to stick to LTS, which I probably should). My VPS is on Debian 10.13 (buster), and the current stable version is 12 (bookworm). Both are nagging me that the version they’re running is no longer supported and I should upgrade ASAP.

Ok, for the Kubuntu machine, there’s an update program. But when I run it

sudo do-release-upgrade

I get a message that says

The package 'postgresql-14-postgis-3' is marked for removal but it is in the removal denial list.

I think that means I need to remove PostGIS and try again, and then hopefully reinstall PostGIS after the update. But I’m reluctant to do so, in case it breaks something. I guess I need to bite the bullet and do it.

My VPS was originally Debian 5, and over the years I’ve upgraded it many times just by editing the /etc/apt/sources.list to the new release name, and running

sudo apt update
sudo apt upgrade

But when I contacted Linode technical support about something else, they were horrified that I appeared to them to be using Debian 5. When I told them what I’d done, they were even more horrified. Evidently the proper way update is to spin up a new VPS instance with their Debian 12 image, and then migrate applications and files over. I’d worry about missing something. On the other hand, it might be a chance to leave behind the cruft of things I no longer need.

I guess I’ll start with the local server by removing PostGIS and proceeding from there. For the VPS, I might try just cloning the VPS and doing the old fashioned way.