4.4.3

Added

• Dedicated helper to create Mapillary output folder
  New ensure_mapillary_output_dir(root_dir) utility (declared in the app class) to consistently create Mapillary_Output when Mapillary actions are executed.

Changed

• Mapillary output folder creation logic (Max workflow)
  Phase 3 now creates and uses TargetDir/Mapillary_Output only when Mapillary actions (sample/process/upload) are active, instead of falling back to TargetDir when the subfolder doesn’t exist. This ensures a predictable location and fixes rerun sampling issues. (Previously: used TargetDir if the subfolder was missing.)

• SVS‑only run behavior
  Starting the Max workflow with “SVS processing” (main workflow choice = 2) now explicitly sets RunUpload=False and RunSample=False, avoiding unintended Mapillary steps during SVS‑only runs.

• Hero workflow discovery & ordering
  When sampling from Hero source, MP4 files are now sorted alphabetically before processing. When running process/upload only from the Hero target, the script filters out system/hidden folders (e.g., Upload_Successful, System Volume Information, $RECYCLE.BIN, RECYCLER, dot‑folders) and sorts remaining folders. This improves determinism and avoids picking up unwanted directories.

• Consistent Mapillary username usage in batch upload
  Root‑level batch upload now consistently reads MapillaryUserName (previously, it tried MapillaryUser then fell back to MapillaryUserName).

Dependencies

• FFmpeg / FFprobe
  • Binaries updated from 2025‑12‑22 build to 2026‑01‑07 build.
• ExifTool
  • Updated from 13.43 to 13.45.

Fixed

• Sampling & rerun stability (Max)
  Creating—and then always using—Mapillary_Output under TargetDir when Mapillary actions run prevents sampling from writing to the wrong location during reruns or upload‑only cycles. (Addresses intermittent “missing frames directory” issues after re‑runs.)

Upgrade impact

• Safer SVS‑only runs: 4.4.3 better isolates SVS flow from Mapillary actions. Recommended if you switch between SVS‑only and Mapillary workflows on the same dataset.
• More reliable Mapillary reruns: Ensures the Mapillary_Output folder exists and is used consistently, reducing surprises when re‑processing or upload‑only reruns.
• Cleaner Hero target scanning: Avoids picking up system folders; alphabetical processing makes results repeatable.

---

TL;DR

v4.4.3 tightens folder management and flow control:

• Always uses a well‑defined Mapillary_Output when Mapillary actions are active.
• Prevents accidental Mapillary steps during SVS‑only runs.
• Makes Hero processing robust by sorting inputs and filtering system/hidden dirs.