- Lightroom Version Number
- 10.4 CLassic
- Operating System
- Windows 10
I used Helicon to stack a set of 7 images (3888 by 5184 px) using the export to Helicon as DNG plugin from lightroom and exported the three rendered outputs (different rendering parameters) back to LR. However, I found the resulting DNG - reported in LR as 3876 by 5172 pixels - had "cropped" key areas off the bottom and RHS. This was a surprise (and extremely annoying) as the cropped areas were visible in Helicon rendered images and the cropped bits were important elements of the composition
After much messing about, I opened the Helicon output dng's in DXO photolab and obtained an image that showed the full original area visible in the Helicon output screen BUT ALSO REPORTING AS 3876 BY 5172 PIXELS. I saved that as a tiff, loaded it into PS and saved it to LR as a psd and the image is now complete in LR and still reporting as 3876 by 5172.
Using the PS ruler very roughly, it appears that the "opening helicon dng directly in LR version" removed approximately 130- 140 pixels from each edge while still reporting the image as having identical numbers of pixels as the psd version which shows a lot more of the original field of view.
I hope soemoen can tell me what I am missing here and how the LR dng import algorithm can "crop" a dng file differently from the DXO tool but still report the same pixel numbers - I must be missing something very simple here. I have attached jpg exports showing a) one of the oiriginal stack of 7 images to show the original field of view b) the result of importing the dng into LR directly and c) the result of opening the dng in DXO PL and passing back throguh PS to LR as a PSD
I must be doing something very stupid or forgetting something basic about importign in LR - any ideas??
After much messing about, I opened the Helicon output dng's in DXO photolab and obtained an image that showed the full original area visible in the Helicon output screen BUT ALSO REPORTING AS 3876 BY 5172 PIXELS. I saved that as a tiff, loaded it into PS and saved it to LR as a psd and the image is now complete in LR and still reporting as 3876 by 5172.
Using the PS ruler very roughly, it appears that the "opening helicon dng directly in LR version" removed approximately 130- 140 pixels from each edge while still reporting the image as having identical numbers of pixels as the psd version which shows a lot more of the original field of view.
I hope soemoen can tell me what I am missing here and how the LR dng import algorithm can "crop" a dng file differently from the DXO tool but still report the same pixel numbers - I must be missing something very simple here. I have attached jpg exports showing a) one of the oiriginal stack of 7 images to show the original field of view b) the result of importing the dng into LR directly and c) the result of opening the dng in DXO PL and passing back throguh PS to LR as a PSD
I must be doing something very stupid or forgetting something basic about importign in LR - any ideas??