! - Please don't use this script before reading the last "warning" paragraph, or you risk a small chance of having your video messed up. - !

Avata 2 Merge Flights

Python script that processes segmented DJI Avata 2 drone videos to determine which files belong to the same flight, merges them, and manages file organization based on user-defined parameters.

Features

• Automatic Flight Detection: Groups video files into flights based on timestamps within filenames and the video duration.
• Video Merging: Uses an external tool to merge videos that are detected as part of the same flight.
• Customizable Output: Prompts the user for an output directory name and constructs directories based on the earliest date found in file names.
• Size Validation and Cleanup: Checks merged file sizes against the sum of the input files. Deletes source files if the size difference is within a 0.1% threshold. This is to avoid deleting input files if due to full hard disc mp4-merge silently fails and outputs a half finished output video.
• Error Handling: Provides detailed error messages and skips deletion if file sizes do not match closely enough.
• SRT Merging: If .SRT files are detected next to videos, they will be merged and copied over as well (timestamps and frame counts within will be adjusted appropritely).

Set Up

1. Make sure you have Python 3.x installed.
2. Download mp4-merge tool from here: https://github.com/gyroflow/mp4-merge
3. Install MoviePy by opening command prompt and typing: pip install moviepy
4. Modify the OUTPUT_BASE_PATH and MP4_MERGE_PATH in the script to point to your desired output directory and the location of mp4-merge tool, respectively.

Usage

Select all your video files straight from the SD card and drag and drop them onto the script.

Warning!

As of August 4 2024, Avata 2 still has the date time bug, where it will tag files with wrong date time in both filestamp and file metadata. This usually just means that output folder will have the wrong date in its name, and sometimes flights will be in wrong order, but on rare occasions it's possible for Avata to fuck up so badly that it manages to trip up the script flight detection feature. While this feature could be made more robust to doublecheck against index numbers at the end of filenames, I'm hoping DJI will actually fix this bug as it's a pretty huge bug experienced by many, if not most users, so I'm not going to invest time into implementing workarounds until I'm conviced they've dropped the ball. Here is an example of script being tripped up by an especially faulty timestamp, so please doublecheck the output of the auto flight detection before starting the merge to avoid having your flights messed up!

In this example files with index _21 and _22 should on their own make up the 5th flight.

The only way to workaround this DJI bug on your own seems to be to connect headset to your phone's DJI Fly app before every single flight.