DNG file keeps crashing

[AndyV]

I'm trying for the first time the pixel shift feature on a Fuji X-T5. It creates 20 raw files, and then with a combining software creates a DNG file. Everything I'm reading says that Affinity can open DNG files, but every time I try it crashes. I tried raising the memory used (from around 10gb to 30gb - I have 64) but that didn't help.

I tried downloading Adobe's DNG convertor but my o/s level is too low for it to be installed. I can change that of course, but for now I just want to get the DNG file open in Affinity. As I write I'm trying to open the 20 files as a stack, but I may have to wait a week or so until it opens.  😆

Any suggestions?

 

TEN MINUTES LATER: Importing the 20 images as a stack does in fact work. But at this point I have nothing to compare it to other than a test of a single raw file that I made of the same image/same position. Its much better than the single RAW file, almost scarily so. Makes me want to use the pixel shift as much as possible; the RAW file looks out of focus in comparison.  But I don't know how it compares to a DNG file generated by the combiner software. It does give me some tools to manipulate how the stack is combined, but I can't see much difference in them.

[AndyV]

I am replying to myself only to push it back up to a new thread status in hopes that someone might respond this time.

I can't seem to get DNG files to open in Affinity.

[Ldina]

@AndyV I don't have an answer for you, Andy, but I have come across a few other discussions where some DNG files do not open, or open incorrectly. It could be that the file format written by Fujifilm Pixel Shift Combiner (and some other cameras/software) doesn't fully conform to Adobe's DNG spec. I'm not sure if Affinity supports the latest DNG spec, which added support for JPEG-XL compression, in addition to JPEG Lossless compression (DNG v1.7). Some cameras and software write to a High Efficiency Compression formats, which can also cause problems. The Nikon Z-9 was an example where standard compression RAW files opened fine, but High Efficiency RAW files did not (which I think has been fixed now, but I'm not sure if that has yet been released). 

If importing 20 individual RAW files in a stack works, but the combined DNG file created by Pixel Shift Combiner software does not, it suggests a possible file format issue that is not compatible with Affinity. Were those 20 images you opened in a stack DNG files, or Fuji native RAW file format? 

Have you tried opening individual DNG files that were converted from Fuji RAW format? I've had no problem opening DNG files converted from Canon CR2 format, or Apple iPhone 16 Pro DNG images. Just throwing out some ideas to consider. If you have NOT opened a Fuji RAW file converted to DNG, why not upload a single file (and also one of the Pixel Shift Combiner files, so others can try. I do have DNG converter and could try converting your Fuji RAW to DNG if you haven't done so. 

[AndyV]

Sigh. This is giving me flashbacks to the 1990s when there were all sorts of incompatibilities I always had to deal with.

Those 20 images that I stacked were RAW files. Those open just fine in Affinity.

Fuji has a proprietary program called "Pixel Shift Combiner" that does what the name suggests. Pixel shifting creates 20 RAW files. The "Combiner" creates the DNG file out of those 20 files (or however many you choose from). Which is over 620mg. That's what i can't open in Affinity. (And why I can't upload it here. If you really want to try playing with it, I could put it on Google drive.)

But there is now new information that I learned tonight: I can open that DNG file in Raw Therapee. I've tried it now three times. So that is a definite workaround. I'd rather just do that than beat my head against the wall in trying to figure out how to make a DNG file that Affinity likes. I'm too old for this!!!

The new glitch is that the DNG file that is created has so many artifacts in it that it is making this project of using pixel shifting pretty useless. (camera is on a tripod) This is just a cropped close-up. (Those are colored pencil shavings.)

So as usual, I solve one problem and go right into a new one. 🤣 But i think the answer might be to choose less than the 20 files it creates. I need to learn more on that aspect.

[Ldina]

@AndyV If I understand you correctly, (which I may not), Fuji Pixel Shift software is combining and writing DNG files that aren't fully compatible with Affinity. It sounds like Raw Therapee opens those Fuji files, but they are full of ugly artifacts.

If that's the case, you can try to find software that works with the Fuji generated file, or use the Stacking feature in Affinity with separate RAW files. I've always had pretty good success with stacking (focus stacking, regular stacks or HDR Merge), but I prefer to stack pre-processed JPG or TIFF file formats. I find I get better results using pre-processed images than I do with RAW files. FWIW.

[AndyV]

Yeah, you understand me correctly. But maybe I should be contacting Fuji about this. It really is a problem that they are creating. (I think they recommend Capture One, but I"m loathe to start buying into a whole new software. I already did that with Affinity!

Also, reading between the lines of what you say, I guess maybe I"m jumping to conclusions that the artifacts I'm seeing in Raw Therape are from the pixel shifting. So maybe Raw Therapee is doing that?

When I have stacked the 20 raw files from the pixel shift, in Affinity, I don't see any such artifacts, but then stacking in general is still rather new to me, and I"m not sure what I'm doing. All the differnt blending choices are still new to me. But more importantly, I'm not sure that's doing the same thing as the Pixel Combiner is doing.

[Ldina]

23 minutes ago, AndyV said:

But maybe I should be contacting Fuji about this. It really is a problem that they are creating. (I think they recommend Capture One, but I"m loathe to start buying into a whole new software. I already did that with Affinity!

I saw that Fuji recommended Capture One. It may some special algorithm that only a few other software packages can open and process properly. I don't know. If those Fuji merged files are choking on everything but Capture One, it's most likely something they are doing, or a feature that is not supported in other software.

If you are doing this primarily to extend Depth of Field (e.g., sharper macro photos, front to back), try File > New Focus Merge in Affinity. I've had success doing that. It takes the sharpest details from each individual exposure and merges them into a single image. I guess that is what the Fuji software is attempting to do. Again, I prefer to work with pre-processed JPGs or Tiffs, but try it with RAW...it may work fine. The other stacking options (New Stack, New HDR Merge, New Astrophotography Stack) are useful, depending on what it is you are trying to accomplish. 

You can run a New Batch Job to convert all your RAW images you plan on merging in a Focus Stack (or other stack). I created a macro that will Develop multiple RAW files, using the same WB for each, and exports to whatever format I choose. That way, I can speed up the process of "preprocessing" a bunch of RAW files. It doesn't optimize each RAW file, but it does save them all with the same WB (to avoid weird color issues when combining) and saves them to the same pixel dimensions and file format). You add the macro to a New Batch Job and it is applied to each RAW image you have added to your Batch Job. This macro opens the file in the Develop Persona, applies a basic Daylight WB to all images, then exports to your chosen file format. Not sure if that is anything you want to try, but the Macro is attached (very simple macro). After stacking the images in one of the Stacking options, you can always adjust WB afterwards if it's not what you want.

The 'New Stack' option in Affinity simply aligns and stacks the images, then loads them into a Group. You can apply an operator to that Group of stacked images, then do manual operations on one or all those stacked layers (images). So, it does provide some flexibility, but if you are focus merging or HDR merging, I'd generally choose one of the dedicated stacking options mentioned above. 

Hope this is somewhat helpful. 

Develop Macro with Daylight WB.afmacro

[AndyV]

Thanks for all this. I've actually been playing around with focus stacks too. But I'm trying the pixel shift for another idea I have. Yes, it is about getting a sharp image, but  in my case more for a relatively flat image (e.g. rust on some sheet metal) in which focus stacking would be largely useless.

From what "clean" areas I could manage to get from a pixel shift, they are remarkably sharper/distinct than just a single one of the raw files in the group. Which in some ways is rather dismaying how "unsharp" a single raw file can be in comparison. If in the end, I get more serious about this specific project, I might just have to bite the bullet and buy Capture One. I need to first hear from Fuji what they are actually saying about their DNG files.

But I'm certainly going to save your instructions for another day. I'm still trying to learn focus stacking too. I've done a few experiments of some close-ups (just using an extension tube) with mixed results.

I think my biggest problem is that between the X-T5 and Affinity, there are waaaaaaaay too many things to learn (and to go wrong!).

Thanks much for your very helpful  responses. 

[Ldina]

@AndyV Sounds like a plan. 

You might try experimenting with a Live Displace filter, Live Lighting Filter (primarily Directional Light), etc. They can do some very interesting things to amplify detail, edges, texture, etc. Good luck.