Skip to main content

Troubleshooting o/PARASHOOT

Find your symptom and jump to the right fix for o/PARASHOOT.

Most issues fall into one of the categories below. Find the symptom that matches what you're seeing and follow the link.

Before anything else: update to the latest version. Click the o/PARASHOOT icon in the menu bar and open More, then either choose Check for updates or open Settings and click the refresh button next to the version number. You can also download the latest build from ottomatic.io/o/parashoot/download. Many issues are already fixed in the newest release. Please do this before troubleshooting further.

Check Full Disk Access (macOS)

A lot of "card not detected", "won't erase", and "can't restore" problems come down to a missing permission: on macOS, o/PARASHOOT needs Full Disk Access to manage disks.

Open o/PARASHOOT Settings (menu bar icon → More → Settings) and look at the Full Disk Access row. If it doesn't say Granted, click Grant Full Disk Access; it opens the right page in System Settings. Enable o/PARASHOOT there, using the + button to add it if it isn't listed, then relaunch the app if prompted.

I can't find the app: there's no window

o/PARASHOOT runs in the background with an icon in the macOS menu bar. See Where's the app?

My card isn't detected

o/PARASHOOT only treats certain media as cards. See Card detection for how detection works and what to send us if your card is missing.

A normal drive is being detected as a card

Usually an ExFAT backup or shuttle drive. The "Ignoring a disk" section of Card detection explains how to exclude it. If it's actually one of your backup drives, see Backup destinations.

The card won't erase

This is by design: o/PARASHOOT only erases a card once it has confirmed your footage is safely backed up. It verifies by scanning your configured backup destinations for files matching the card by name and size. It doesn't matter which app made the copy. If a card won't erase, it's protecting you and will tell you the reason. The common ones:

  • Files reported missing on the destination. o/PARASHOOT lists exactly which files it couldn't match. The usual cause is not a copy still running but a mismatch: the destination configured in o/PARASHOOT isn't the one you actually backed up to, or your backup app renamed files so the names no longer match the card. OffShoot 24.4+ communicates renamed files to o/PARASHOOT. See OffShoot integration.

  • No backup destination set, or the destination can't be read. Check that a destination is configured and that the backup drive is connected, mounted, and readable. See Backup destinations. If you've set Erase requires backup on to N or more destinations, an offline or incomplete destination that isn't marked Required is skipped by design and does not block the erase. That is expected behavior, not a fault.

  • The card is write-protected. See Card is write protected.

  • ARRI HDE: backup doesn't match the card. If HDE is enabled in Codex Device Manager, o/PARASHOOT expects the HDE filenames _h and .arx on the destination; if your backup is standard ARRIRAW with _a and .ari names they won't match and verification fails. The reverse applies too. Make sure the backup was made with the same HDE setting o/PARASHOOT sees. See Understanding Virtual _hde Volumes.

I erased a card by mistake / I need the data back

If the card was fake-formatted by o/PARASHOOT and not reformatted in camera, it's fully recoverable. See Restoring a card.

Sony cards

Still stuck?

The fastest way to get helped, whether you're chatting with our assistant or a person, is to give us enough to work with up front: your o/PARASHOOT and macOS versions, the card and reader model, the exact text of any message the app showed, your log file, and a screenshot or short screen recording of the problem. The more context we have, the less back-and-forth it takes to fix it. See Contacting support and getting your log file for how to grab the log.

Did this answer your question?