![]() ![]() STAY in Helicon and change the method to C, set smoothing to 2 and render again. Once there, render the stack in Method B, using the default radius (8) and smoothing (4). Presumably they're shot in RAW, imported into Lightroom, then sent in RAW to Helicon Focus. Take one of your stacks - maybe a small one with 20 or 30 images. Take one of your stacks - I don't know what a GFX 100 is, but presuming you're doing focus stacks by changing focus. I think I'm starting to get punchy looking at this stupid thing. BTW: The two caches are on completely different drives.Īnyway, Bridge IS still showing them different. I purged cache in Lightroom and I had Bridge purge local cache. dngs that are sitting there, the ones that SHOULD be different are. I just went over and tried again, and realized I was looking at different versions of the same rendering. Include develop settings in metada… checked.Have had graphics process off, auto and custom, doesn’t make any difference.I presume there’s nothing in presets or external editing that can cause this? Replace embedded previews with standard checked.Ignore camera-generated folder names NOT checked. ![]() Is there any way a preference can be causing it… I figure it's going to be something stupid as soon as I know what it is. I have no idea what's different between the two computers I've tried this on here and what y'all are doing, but Lightroom here doesn't show the difference between the images. ALL with "previews" created this morning after deleting the previews. dng files, days apart, at least 4 that are perceptibly different, all with unique names. Completely different executions.īack to Lightroom, I now have 3 different images from 2 days ago, and 2 images created in separate executions of Helicon Focus this morning with unique names. Then took 8 of the 19 images exported back to Helicon and rendered those. I even ran Helicon Focus, rendered the images saved, exited back to Lightroom. I even opened Luminar and opened the three images. Opened Faststone viewer to make sure they WERE different. After that, viewing them a second time, all the same. Created 1:1 previews to see if that would matter. ![]() Restarted Lightroom, opened the three images in loupe view, still the same. It certainly wouldn't be a fix, and definitely not a reasonable thing to do, but in this case it was worth a try. I'm on Win10, Bridge 2020 (for a reason), Photoshop 2021, ACR 13.2.0.738, Helicon Focus 7.6.4 Pro.I thought for sure the nuclear option of deleting 36GB of previews would make these things unique. We'd appreciate if you could share your experience." Please let me know if you try this option. Maybe you can open the image in PS or Adobe DNG Converter and save it again, and maybe in this case only the enhanced image will remain. I was hoping that this can be adjusted in enhanced dng saving settings, but there doesn't seem to be an option. The problem is that the enhanced dng actually contains two dngs - the smaller and the larger one, and the smaller dng is the first one to be saved and the one to be uploaded to HF.Īt this point we don't have a good solution for this. They suggest trying to export or resave the enhanced DNG as DNG, hoping that only the large image will remain.ĭoes anyone know what is going on and how this can be fixed? I've tried exporting as DNG in Bridge and Adobe Camera Raw, with no succes. Helicon Focus uses the smaller one, and this is not easily changed. I contacted their support, and they suggest that the enhanced DNG files in fact contain two images: one with the original resolution, and one with the enhanced (double) resolution. But the DNG exported from Helicon Focus has the resolution of the original Canon CR2 RAW files that I started with. Exploring the possibilities of the new Super-Resolution option, I created a few DNG files, and I imported them into Helicon Focus to create a focus stack, as I often do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |