Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dark table creates XMP files during import #17709

Open
DziadekGrabowski opened this issue Oct 22, 2024 · 3 comments
Open

Dark table creates XMP files during import #17709

DziadekGrabowski opened this issue Oct 22, 2024 · 3 comments

Comments

@DziadekGrabowski
Copy link

Describe the bug

Darktable creates XMP files during import, although I disabled XMP file creation during import

Steps to reproduce

I select Preferences _> Storage -> Create XMP files -> after edit
I use Import -> add to library
Darktable creates XMP files in direcroty during import

Expected behavior

Dont create XMP files

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.8.1

What OS are you using?

Windows

What is the version of your OS?

Windows 10

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

@ptilopteri
Copy link

ptilopteri commented Oct 22, 2024 via email

@DziadekGrabowski
Copy link
Author

I see XMP files after import before opening the file in DT.
I import JPG files.

But if I use import in DT 4.4.2 (Legacy windows 7), DT don't create XMP files :-) !!!

@DziadekGrabowski
Copy link
Author

The described problem occurs when the photos are on a network drive mapped to Windows. Today I restarted DT and imported the files into the library from the network drive. I don't know why, but XMP files are not created for all files during import. XMP always appears for some files, never for others. I can't find the correctness. I'll test it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@DziadekGrabowski @ptilopteri and others