Hello,
Please note that PRIME is not supported with Xtrans sensors. So as mentioned in "Processing Failed for an Unknown Reason" - error message - #18 by Lucas , unless you can switch back to macOS 11 or have a usable GPU, and until Apple or DxO provide a fix, you’re stuck with HQ only. The bug lies in macOS 12 so hopefully it should only be a matter of time.
Best regards,
Lucas
I haven’t tried my Fuji since updating my computer to Monterey, which means I may have the same issue now that @Lost_Manc has. I’ll try this later today. Monterey was released with several functions turned off for now - hopefully it won’t be a very long wait. In the meantime, I am thrilled that PhotoLab can now process my Fuji X-Trans images. I appreciate all the work you guys did to make this possible. I don’t remember being bothered much by noise in my Fuji images anyway, and now I can use all the other tools in PhotoLab 5.
~ PL5 DEEP PRIME ALSO FAILING EXPORT WITH WINDOWS 10 ~
I’ve only tried on a couple photos, but so far, Deep Prime fails every time on export with:
If you have my OS and graphics card and PL5, does Deep Prime work for you?
Deep Prime works with PL5 if I use CPU Only, and it works with PL4 with graphics processor.
I submitted a ticket and log files to DxO.
Heard back the log files don’t reveal the cause, and that I should try a fresh download and reinstall with antivirus turned off.
Still failed.
DxO would like me to install an app that’ll check my registry for hijacking and send that report.
Not going to install that.
I’m guessing DxO will fix this soon using other feedback.
No problems here with Win 10 Pro 64 bit version 1909 with Core i7-4810MQ @2.80Ghz and an older NVIDIA Quadro K2100M Graphics card.
And if that’s the case why is that not stated anywhere around the talk of Fujifilm X-Trans support on the product page?
If it’s there I cant find it or missed it.
Beta or not if its was a known ‘issue’ then it should have been made clear that PRIME would not be supported especially as it seems you were aware that things were about to get worse once MacOS 12 was released. Again would it have hurt to send a warning out to Mac users that it was highly likely the update would reduce functionality in DxO PL5?
Yes PL5 is more than just PRIME & DeepPRIME but its still frustrating to buy something and find in a week it has become less than it was.
Regardless of this being Apples fault or DxO’s a warning wouldn’t have gone amiss. It cant be hard to identify the users who run the software on a Mac.
They aren’t. Or at least mine don’t seem bad but its still annoying (to me) that the software now functions less than it did when I tried it (PRIME notwithstanding as I didn’t check that and didn’t notice at the time it was greyed out and just tried DeepPRIME instead) and then subsequently purchased it.
I guess I’m too excited by the major improvements, that it now works with Fuji, and that I’ve got this new Control Line tool to help my edits.
If you don’t want to, that’s OK, but I’d like you to take a photo with your Fuji, and then send it to me to test.
I just tried this with my X100f. I took a photo from my balcony, transferred it to my Mac mini, opened the image in PL5. As you noted, PRIME was turned off/grayed-out, so I used DeepPRIME which is my goal anyway. It processed with no issues.
_DSF4572 | 2021-11-06.raf (48.1 MB)
_DSF4572 | 2021-11-06.raf.dop (11.6 KB)
I suppose I should take it again, being more careful about the settings, which gave me an underexposed image, ISO 400, f/10, and 1/1000th shutter, in bright sunlight and shadows, but all I wanted to know is whether it worked.
Please download this image, and edit in PL5 on your computer, doing no additional editing, and see if it works or not. I would like to do the same thing, with your image, if you let me.
Same image, again with DeepPRIME, but also using Smart Lighting:
…and the new .dop file:
_DSF4572 | 2021-11-06.raf.dop (12.8 KB)
I took the second DOP.
The Smart Lighting zone for highlight is better placed over the brighter building towards the left. This achieves a better balance.
I also raised the intensity to Medium and added a gentle tone curve.
I also played with the colour wheel, to lower the saturation on the red roof tops, and in the sky, which oversaturated when I applied the tone curve.
DOP file…
_DSF4572 | 2021-11-06.raf.dop (26,8 Ko)
Aha! So all it has to do is include the brightest spots, they don’t need to fill most of the selection? Obviously it works - will remember for future.
I need to take an entire day, and learn the color wheel as well as I understand the other tools you’ve helped me learn.
The purpose of this photo was just to quickly take “a photo” to see what PL5 did with it, for @Lost_Manc to try - to see if his Mac computer would accept DeepPRIME which it doesn’t for images he takes with his Fuji. Hopefully when he reads this, he can try both of our .dop files, mine with a minimal amount of processing, and yours with additional processing. I think that the more processing there is, the more likely DeepPRIME will fail, but that’s just speculation. When images do fail, and I remove most of my processing, sometimes DeepPRIME then works again. Not very scientific I guess…
How come, that a camera with roughly 24 MPix produces a raw-file of 48 MB?
Does it include a huge jpg?
Interestingly, the pic shows very little blown out highlights – or to state it differently, the cam did a good job.
So I haven’t had time to take a picture. its pitch black here so ill grab something tomorrow however we can probably get to the bottom of something here without the need for me to take one and post.
I downloaded your originals and both @Joanna and your edited .dop files and I can confirm I can export all 3 without any issues at all.
For reference I just exported to the ‘Standard JPEG’ profile exactly as it was set up by DxO.
This got me wondering if your X100f wasn’t an X-Trans sensor and maybe that was the issue but a quick search confirmed that not to be the case and both your X100f and my X-T4 use an X-Trans sensor.
From there I backed up one of my .dop files to a picture I know fails with DeepPrime and started from scratch with it.
The tests I did were as follows…
From here I went back to your files and also applied a simple 1x1 crop. Export immediately fails.
So if you or @Joanna if she feels like joining in with this can apply a 1x1 or indeed any other crop to your file and see what happens then we maybe able to point the finger at ‘cropping’ being the culprit in the failed exports. As to why I don’t know and I’m not saying other edits might not result in a failed export but as it stands that’s the first thing that caused the export to fail and I currently don’t have the time to keep trying individual things.
I am definitely interested in whether the crop makes the export fail for others.
The X-T4 produces roughly 58MB from a 26MP sensor.
I am running a 2019 MacBook Pro with Catalina and have never had any problem exporting.
If I remember correctly, I selected non-compressed. It shouldn’t include a huge jpg, as I only selected raw images. Maybe this is because of something to do with the x-trans sensor? I noticed this last time, but just accepted it. Here’s what I just found, after doing a search:
From the internet:
the files are larger on your Fuji because they don’t compress their RAW files like Nikon or any other camera manufacturer does . Whish Fuji will implement this in a future update otherwise you’ll have to learn to live with it
Also:
https://www.imaging-resource.com/news/2020/04/20/fujifilm-x-trans-is-it-really-all-that-different
Just for the heck of it, I will try for a good Fuji photo of the next nice sunset. With sunsets now being an hour later than they did while I was on Daylight Savings Time, it will be easier for me to so. I’ve always loved my Fuji, but felt limited by the fixed lens - but that made it great for a walkabout camera, much nicer than my other cameras. X100f = small, light, skinny, and very capable. It also has an electronic shutter, something I’ve never yet used:
https://fujifilm-x.com/en-us/stories/advanced-month-3-motion-9-electronic-shutter/
Nikon has taken this to a new level in their Z9 cameras - I guess I ought to check what Fuji has done, but I doubt I will ever give up my X100f because it doesn’t make me use a touch-screen, and I can use normal camera controls.
Right. the issue is isolated to macOS Monterey I believe so that will I guess be why.
I have just created a virtual copy of a picture I know has quite a few edits applied but removed the crop and turned on DeepPrime and the file exports just fine.
Back to the cropped master and it wont export with DeepPrime turned on so for me and my bit of testing its the ‘crop’ that’s ‘breaking’ DeepPrime exports.
Again if @mikemyers can apply a crop to the files he uploaded for me to check and see if he gets a failed export that should point to the issue being both crop and Monterey related as iirc Mike is also running the latest MacOS.
If he also gets failures then that’s great in so much as it rules out the issue being isolated to me and my machine but also strange as to why something as simple as cropping the image would cause the failure when much more complex edits don’t.
For reference and because I don’t think I’ve mentioned im using:
2019 MacBook Pro now running Monterey 12.01
1.4 GHz Quad-Core Intel Core i5
8 GB 2133 MHz LPDDR3 Ram
Intel Iris Plus Graphics 645 1536 MB
So certainly no power house editing rig but it was never meant to be used for this and circumstances have just dictated that this is what I’m using at present. Its does however still meet the minimum requirements to run PL5.
Easy enough to try - I took the same image, and cropped it quite a bit so just the middle part was still showing, then made sure DeepPRIME was back on, and exported with no problem. Here’s the .dop file and the resulting image.
The only thing unusual is that I’ve been noticing I no longer get notifications when the export has finished, as I used to.
Assuming you can download my file, you can try the same thing yourself.
_DSF4571 | 2021-11-06.raf (48.2 MB)
_DSF4571 | 2021-11-06.raf.dop (11.8 KB)
It’s still an ugly image, and I haven’t yet tried Joanna’s improvements, as the only purpose of this image is for you to download it and see if you get the same results. For me, doing the crop made no difference.
Well for me it fails when cropped, either using your provided .dop or a crop I add, so I’m at a loss really.
To rule out anything I removed the crop you added and sure enough back to the export working.
So for some unknown reason cropping essentially breaks DeepPrime exports for me. Can @Lucas offer any insight here?
I will try and get a suitable shot tomorrow in the daylight and post it for for @mikemyers to try on his machine. I guess if he has no problems then something my end is a miss and if he does then still my end but maybe the X-T4 files are the issue, although actually its obviously something else also as your X100f files fail for me.
So sorry to keep this going. Can @mikemyers try one more thing.
I’m getting some success in cropping so long as its constrained to the original ratio. Not always but more often I get a successful export but as soon as I try 1x1 or 4x5 say it fails.
Anyway. I found a suitable file which was in my rejected folder that I have not yet deleted. Poor composition and forgot my filters. it was a disappointing day!
Hopefully I upload everything correctly but here we go…
(DELETED UNTIL I CAN FIGURE OUT HOW TO UPLOAD!)
Hopefully I’ve done that right!
I suspect you will have no issues at all cropping either your own or mine anyway you see fit and its starting to look like an issue with my machine/setup but curious to know how you get on.
Edit: so that failed. how do you attach the raw file without it converting to the jpeg image?
I was told to open Apple’s “Finder” app, locate the file, and “drag” it into the place where you want it to go, as in right below your response, before you save it. I suspect that’s because it is a huge file, at least for me. Depending on your internet speed, it will likely take a long time, but it hasn’t failed yet.
Once you upload, I will try.
So simple! I was attempting to use the Upload function which work fine for the .dop however unfortunately the X-T4 raw/raf files are too big to attach so for now I will bow out of this one and maybe contact support directly as I don’t use DropBox or the like to share it anywhere else.
Suffice to say macOS Monterey issues aside something is not working right for me and reinstalling has so far failed to rectify the issue and I’m inclined to say the machine health is fine and its not a hardware fault as I’m having no issues with Capture One/Affinity Photo or Adobe Lightroom Classic and can also edit and export drone footage fine using iMovie or Rush. Yes its hardly fast but they all succeed.
Hopefully future updates from both parties rectify the issue and I will continue to make use of PL5 as I like the software.
Try it my way. Open the folder in “Finder”, locate the image file, right-click on it, and COPY it, then come back to the forum and PASTE it into place.
Or, do it the lazy way like I’m doing now - and someone else here (Wolfgang??) discovered it, not me. Have FINDER open in one window, showing your file, and have this discussion open in another window. Then just drag the image from you FINDER folder, and drop it into the Forum discussion, then go away to make lunch or whatever. When you come back to your computer, it will be here in the forum. If not, your computer has serious problems, or you’re out of disk space. Call Apple Tech Support and let them connect to your computer, and they will solve that problem - it has nothing to do with PL5, only copying from one place into another.
Best of luck - don’t give up. I have the same issue, with giant files from my Fuji, because unlike all the other camera manufacturers, Fuji does NOT compress the raw file.
I was just reading this discussion on dpreview:
https://www.dpreview.com/forums/thread/4515373
How do you move your images from your XT-4 to your Apple Computer?
Is your XT-4 set to compress those images?
Hopefully you are using a card reader, and not copying them directly from your camera.
