I processed a raw file and saved it as a jpg to another folder. Both images are on a USB attached SSD. Now the jpg is nowhere to be found. I’m on a laptop using Linux (Pop! OS). I can see the file in my OS folders so I know it’s still around but it’s not showing in Lighttable. It’s probably a setting or something simple but I’m at a loss here. I’m not even sure of the question to ask.
Is that specific folder to be seen in
lighttable | collections?
There’s an icon in Lighttable that reads “expand grouped images”, it’s represented by an image that looks like a stack of documents one on top of the others. Click that. Maybe.
Yes, the folder is there with all the other jpgs I’ve saved to it. Funny thing, though, if I right click the folder and search the film roll the image is there but it doesn’t seem to have an xmp file.
That doesn’t have any effect. It was already to collapse grouped images.
Sorry for the noise, probably I should have read your message twice (anyway you should ‘expand’ not ‘collapse’, and sometimes for me it didn’t worked as I expected and had to click it more than once).
If you save a .jpg into “another” folder — why would you find an .xmp there? Have you looked in the “originating” folder?
Have you imported the jpg into darktable? It’s not done automatically. It’d also explain why you don’t find an xmp for it.
?? How do you save a jpg in darktable? Explain your steps.
All the other jpgs have xmp folders.
After processing the raw file I saved it as a jpg to another folder like I have done many times before. All those have xmp files.
Yes, this was a raw arw file which I processed in Darkroom. When I was done I exported it to my “Complete” folder as a jpg all within Darktable. I’ve done this before a bunch of times. This time, though, it doesn’t appear.
No, this was a raw ARW file I processed and saved as a JPG all within Darktable.
What you describe is not how dt works when you export the images. When you export a jpg, it does not create an xmp with the jpg. Second, the exported images are not automatically imported back into dt. Therefore, the jpg is not going to show up in the lighttable unless you import the jpg after exporting. Importing the jpg will create an xmp for the jpg (using default dt settings).
Could you be using a lua script?
With a program like LR the export dialog has an option to select for the image to be added to the catalogue (library) which I find a nice option. I feel if this option could be implement in DT it would be good to have. I wonder if I am the only person who feels this way?
I don’t see the value of importing the jpg I just exported. When I export, it is a finished product, so what value there is to import it?
In other words, what’s the use case?
I guess this is why I ask if I am the only person who feels this way. But probably the cases I envision its usefulness for me is processing a RAW file to a 16 bit Tiff and having it added to the library. This would then help me manage my images better. I might then also want to open that tiff file to convert it to a JPG file to share. I previously used to do this with images when I was a LR user. However, I appreciate others may not see value in my suggestion and just see it as a waste of time to code or bloat to the DT software. Thanks for your reply.
It is not about wasting time or bloat or feelings, it’s about having a good use case that would make it a feature that most could use. Going from Raw processing to export Tiff and then from Tiff to jpg seems more complex than just exporting from Raw straight to jpg.
I’m not using a lua script on purpose.
Not importing the jpg back into dt is probably why I’m not seeing it. I’m away for a little bit so will check that later.
It seems to me that importing the jpg is one step I shouldn’t have to take. If I do all the work in dt I would think dt would see it. I guess I don’t understand why that extra step of importing again is needed.
Many thanks for the help.
I think I agree with you. Why wouldn’t you want dt to recognize the new TIF or JPG? Having to import again, for me, is just an additional unneeded step in the workflow.
Because the exported image is the result of your work, not basis for more. If you want to add more modifications, you could add them to the original image.