* J. Paul Bissonnette <jpaulb...@gmail.com> [09-16-15 20:50]: > I have been using 1,6,8 since about when it came out in the PPA. > tonight and a week ago I completely removed DT 1.6.8 including the > Database and reinstalled. I then started to import photos by folders. > The skulls started to appear again. I assume that that happens when a > photo is not where the database claims it is. With a new BD > should there be an existing reference to a photo.
Your original post indicated you had used 1.4 and 1.6 and intermingled them. > I located the offending photos and tried to open them with UFRaw and > RawTherapee , they would not open. I delete them from the HDD and > replace them with the originals from the SD card, re imported the folder > and the skull are gone and UFRaw and RawTherapee can open them. These > same photos have been edited before in DT. Darktable *only* writes to xmp files or new output generated by export, never to your raw originals. > I am far, far from an expert, more like a beginner. I always thought > that metadata was stored in the photo and DT wrote a sidecar with > changes it did. And that is what it does. If something is wrong with your raw files, something else is doing it. > I thought that lens type and white balance would be an integral part of > the photo. When DT complains that it can not find the lens data and I > replace that photo with the original and DT can now find the lens data. > what does than mean? It means that you have two different files or you are trying to access with different versions of dt, one which does not support the particular lense or camera. > To me, either DT of something else is writing to the photo file, am I in > the right direction? Only you can know about something writing to the raw/origianl, but it is not dt. The right direction would be away from dt. I suggest you detail the handling of your originals up to the time that you notice problems with them in dt. Then you will know what the problem is. I have used dt for several years now and have only one time had a problem anywhere similar to your report and then I had a corrupted database and I probably caused it. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
