Now back to the and we need a plan to evaluate this and other incidents being reported because it is doing no good to to the reputation of DxPL and shaking user’s confidence.Īll the tests I ran late last night and early into the morning showed that PL5.2.0 on my Main machine was behaving perfectly until I ran into a test where the data seemed to be changing under its own steam!!Įither I was hallucinating (tiredness from age/to much DIY) or more likely I had switched between directories with similar titles because of tiredness and trying to re-purpose existing tests instead of copying to new Test directories plus I was using LR across my LAN (LR on Test machine and PL5.2.0 on Main machine)! I just changed a keyword on PL5.1.4 (on my test machine) and LR showed the ‘Metadata has change externally icon’, Just using ‘J’ toggles the display options and ‘Ctrl-J’ on Win 10 opens the screen you included. It is too late to continue tonight so will try again Thank you. but I seem to remember LR flagging when the image metadata had changed and when I started to investigate I discovered that PIE had changed and was no longer showing the data that had been added by PL5!? Needed to be read in LR but new PL5 keyword present.Open the new directory in PL5 and add a new keyword.Use Adobe DNG convertor to create DNG files.Copy only the original RAW files to a new directory. I then tried to reproduce the original workflow so:. So we are back to not being able to reproduce the problem on Windows 10 and …!? Sorry it could have been shorter but If I don’t write it down as I go then …? So I copied the DNG file back to the original directory and checked with LR and it also found the added key successfully in spite of the sidecar belonging to the original RAW! So I moved the DNG files to a separate directory and PIE found the new keyword successfully! all in the same directory an xmp sidecar file should not be used with a DNG or TIFF and, if present’ should be ignored. PIE and FastRawViewer seem to get into trouble when there are sidecar files (in this case for the RAW) and TIFF or DNG files with the same name as the sidecar file and the RAW file etc. I added a new keyword in PL5 with AS(ON) and nothing new appeared according to PIE! However, the DNG and the RAW and its sidecar were all in the same directory! So I used Adobe DNG convertor on the original files and they were added to the same directory that PL5 has the RAWs. I opened LR on my Test machine and accessed the directory across the LAN and it also found the keywords, including the new one, intact! Is there something I am missing? Any option in PL5’s settings that allows such a DNG based workflow? That is nice, but im my case DNG files are preferred over NEF files. And thereby exchanging metadata between the two apps becomes possible. In contrast, If I do not convert my images to DNG, PL5 reads and writes metadata in xmp sidecars. In the end, all metadata edits are wasted as Lightroom can’t see any of them. All edits are just stored in PL5’s database. Also, no xmp sidecar file is created by PL5. But if I alter the metadata in PL5, nothing gets written to the metadata section in the DNG file (despite having “always sync” switched on). PL5 does see all metdata I previously entered in Lightroom. When I edit these DNG files in PL5 everything works according to plan. The advantage of that (at least for me): All metadata is stored inside the DNG file instead of having an xmp sidecar file, too. While doing that I convert all images to DNG files. I usually use an outdates Lightroom 6.14 to cull images and to set metadata. I’m new to Photolab 5 (running 5.2 on Windows 10) and often get in troble with metadata.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |