Appearance
Troubleshooting cards, imports and ejection
My CFexpress card appears under Other External Volumes
Some generic PCI/NVMe readers do not identify themselves as CFexpress hardware. Easy Eject may need to inspect a DCIM or other camera folder to classify the volume. In the App Store edition, authorize the whole card for that inspection. You can choose Eject under Other External Volumes without this permission. In the website edition, use Refresh List after connecting a card or allowing macOS drive access.
I see Untitled 2, or the wrong import device
The Finder name can change when another card with the same name is connected. A saved import profile matches a filesystem volume ID rather than the displayed name. During setup, connect only the device you intend to enroll and give its profile a recognizable name. After formatting, the ID can change; set up a new profile. If you have two block-level clones with the same volume ID, keep only one connected for automatic importing until the app can distinguish them.
The card is busy or won't eject
Finish Lightroom, Finder, and any other copy or write operation. Close apps with files open on the card, then retry. Easy Eject does not force an unmount. If cleanup failed, fix the access or file issue and retry; cleanup does not silently fall back to plain eject. If a disk has several partitions, check all of them before ejecting the physical disk. An active Easy Eject import also protects its source and destination from normal eject commands.
An import says Needs attention
Open Device Media Imports… (called Air Unit & Camera Imports… in earlier versions) and read the full issue. Dismiss only clears the menu-bar warning; it does not retry or change a saved profile. Then check:
- Is the original device still connected and mounted in Finder?
- Is the chosen destination connected, writable, and on another physical disk with enough free space?
- Did the card get reformatted, changing its volume ID? Enroll it again.
- In the App Store edition, did the media-folder or destination permission expire? Use Change media folder… (called Authorize media folder again… in earlier Store builds) or Change destination…. Whole-card authorization is separate and needed for cleaning or device Trash recovery.
- Did the Mac sleep or another app add recordings during the import? Keep it awake and rerun Import now after checking partial destination copies.
The app checks copies before declaring completion. An interrupted import may leave finished copies at the destination and originals on the device. Avoid manually clearing the card until you have inspected the destination.
Eject prompt did not appear
In website 1.7.0, enable Ask to eject after import for the profile. Successful imports and scans use a native dialog, including when no media matches the options or all selected media already has verified copies. Keep Connected is the default. Notification permissions and Focus do not control this dialog.
Eject remains available in the menu, and the import window has an Eject Now button for completed, still-connected devices. A camera exposing multiple storage sources gets a grouped confirmation listing them. A no-media result on Internal does not mean its SD Card is empty; set up and import that source separately if needed.
Disconnecting/reconnecting, importing again, or restarting the app expires its old completion action. A busy or changed disk prevents ejection. Failed or unreadable imports remain errors. Website 1.6.2 used notification actions; upgrade to 1.7.0 for the current dialog flow.
I need help from Ryan
Use Contact Ryan or report an issue on GitHub. Include the app edition and version, macOS version, reader/card model, what you clicked, and the exact error. Do not publicly post private footage, credentials, or unredacted logs containing private paths. See Privacy, logs and support.
I still see Camera01, unfamiliar files or extra folders
In website version 1.6.0 or later, enable Clean folder layout in the profile to bring ordinary media into the main dated folder. Existing profiles keep their earlier layout until you choose this option. It affects future imports; Easy Eject does not reorganize past destination folders.
Additional media keeps conflicting names separate without breaking related filenames. Camera originals preserves unfamiliar files and folder-dependent recordings. The recognized Insta360 fileinfo_list.list index is backed up under hidden .easy-eject-metadata and retained on the device. These are deliberate safeguards, not a failed flattening step. See camera compatibility.
Videos-only asks me to use the whole card
Some recordings need their directory tree, project data, proxies or several related files. The importer copies the complete support tree for recognized packages. It stops before copying if the source is too narrow or the package is ambiguous. Choose the complete recording folder or whole card; for ambiguous or multi-camera structures, use All media and sidecars. Keep deletion off while verifying a new recording workflow. Follow the camera's documented import method if its required files span multiple cards or devices.
Lightroom still shows videos after an import
Copy-only import leaves videos on the device. Only the separate, confirmed Permanently delete imported videos option removes eligible imported videos after verification. Videos outside the selected source or supported selection, interrupted imports, and retained motion-photo components may still appear. Review Lightroom's selection and see Videos first, then Lightroom.
Previews are missing from the import, or left on the device
Check Include camera previews in the profile. When off, it skips recognized optional LRV, LRF, THM and preview-folder files. It still copies files required within a complete structured recording package. The choice is separate from Videos only.
Skipped previews stay on the device and in its Trash, including when permanent original deletion is on; Easy Eject has not made a verified saved copy of them. If the originals were removed, use the camera's supported cleanup after backup. Turn preview inclusion on for future imports if Studio, your editor or camera-preview workflow needs those files. See camera compatibility.
