darktable-org / darktable-org/darktable

Movie (MOV) files imported everytime as new

Open
#20,021 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity scope: DAM
Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

When copy & importing with the mounted camera feature movie files (*.MOV) are always imported with each import run.

I also wonder, why Darktable copies files other than images, because it cannot open them in general.
It would be nice to be able to exclude serveral filetypes from importing. Sometimes I don't want to import RAW, but there is no option, just the other way around.

Steps to reproduce
  1. Connect camera via usb connection
  2. Choose 'mount camera' in DT
  3. After mounting choose 'copy & import from camera'
  4. Select 'select only new images'
  5. Verify only new JPG & RAW (RAF) files have been selected, but notice also MOV files are selected
  6. Click 'copy & import'
  7. DT will start also copying MOV files
  8. Repeat steps and see for Step 5.) that same mov files appears again as new.
Expected behavior

Darktable should not interact with MOV files at all.

Logfile | Screenshot | Screencast
Image
Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

5.2.1

What OS are you using?

Linux

What is the version of your OS?

Manjaro Linux 25.1.0

Describe your system

No response

Are you using OpenCL GPU in darktable?

None

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue through “mount camera” and “copy & import from camera,” selecting only new images and repeating the import. Trace how MOV files are selected and copied during that flow. Done means MOV files are excluded from camera import and repeated runs no longer treat them as new.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.