I ran “Activity Monitor” while Exporting.
I have no idea what “XPCCor1” is or does, but when I’m not using PL5, its CPU is 0 %
While Exporting I got this:
I thought I saw it up to over 600. And when Exporting finished:
I have no idea if this is a useful clue. However, this link mentioned it for an earlier version of macOS:
https://forum.dxo.com/t/dxo-photolab-2-3-1-b43-export-doesnt-work/9420
Hey sir I’m still operating on PL4 and I have had pretty much nonstop issues and problems with respect to processing and exporting files ever since I updated the software on my MacBook Air… I’ve encountered similar problems throughout my time that I found this photo editing program, it gets quite annoying and I’m terrible at troubleshooting tech issues… In addition to getting the same exact notification that you did with respect to the file not exporting, now I’m getting an even larger problem with Photo out for only allowing me to now use the prime option as when I try to select the deep time there is a grade out area where the preview window is for the noise reduction of the deep prime and it says it will be offered soon by Apple’s new software… So the only thing I can do is run it through the prime which isn’t nearly as good for some of my high ISO images and try to do it like that which sucks because I paid all this money specifically for the one thing that’s not working
That’s the fun part for early birds.
Hello,
Could you please try to collect logs either by copy-paste it from Console or using diagnostics script you can find here https://download-center.dxo.com/PhotoLab/diagnostics/DxODiagnostic.command.zip ?
If you need any help about how to use this script just ping me.
Best regards, Alex
Hello,
There is a known issue with macOS Monterey and DeepPRIME. We expected this to happen mostly only with the loupe, which is why loupe is disabled in this case. This was one important reason for DxO PhotoLab 5.0.1 release. In the meantime, export with DeepPRIME remains enabled.
We’ll see with the logs that @akarlovsky asked if the issue that you and @mikemyers noticed are the same issue as what we already know for the loupe.
Regarding the issue with loupe, here is the information we have so far:
Best regards,
Lucas
Certainly!! Will do, later today. I think this is exactly the right tool, so DxO will understand where the real problem is. Thank you!!!
I should add that for me, while this is an annoying issue, I can, and still, use PL5 exactly the same as before. The program has never yet “crashed”. When the EXPORT fails, I just switch to PRIME instead of DeepPRIME and that always works.
Also, an image that breaks DeepPRIME does so no matter how many times I try. The next image in my photo sequence usually works fine. I can post two very similar images here, taken within minutes of each other, and you can use my .dop file and probably get consistent results as to breaking the process, or not.
When I get home this morning, I will take an image that “breaks” DeepPRIME and un-do all the changes I have made, so I’m back to the original image, and ONLY select DeepPRIME and test if it works. If it does work, then something else I have done is what causes DeepPRIME to break. This will be an interesting test.
Lucas, if you look over my Halloween photos, the ones that I used DeepPRIME for are the ones that processed correctly. The very similar images that you’ll find where I only used PRIME were the images with the problem.
When I tracked it down to DeepPRIME, I thought I was finished with what I was able to do or test, but thinking about it now, it might be because of DeepPRIME, and ALSO one of my other corrections. I’ll see if I can figure this out.
In the meantime though, I’m now able to do just about everything I want, and if DeepPRIME doesn’t work, I just use PRIME. For me, it’s not that big a deal - sort of like getting a piece of cake that came without the icing on top. The cake still tastes great!! …and I am still happy. I’ve been doing computes since I started out with IBM punch cards, and I’'m always surprisingly happy when things DO work as they should. I’ve learned to always expect problems, and then try to figure them out. I used to work in the Quality Control Dept. at a software company, because I was so good at getting software to break. 
Small problem:
Here is the file that I’ve been working on - (VC1 crashes)
_MJM9431 | 2021-10-31.nef (29.2 MB)
_MJM9431 | 2021-10-31.nef.dop (24.9 KB)
This is a screen capture that shows the “clipping”:
In the (M)aster file, I removed all the history except for “Applied Default Preset”, and then turned DeepPRIME ON. It worked, twice in a row, taking around a minute and a half. I’m no longer so sure DeepPRIME is causing the problem. You can examine my .dop file and see the other changes I made (not that many).
I prefer Wolfgang’s explanation - the Devil did it!
You need to right-click on the app and then authorise it.
I tried right clicking on the above message, and I tried right clicking on the file in my downloads folder:
I don’t see any place to authorize it???
Probably best if DxO downloads my files, and replicates the issue on their test computers.
Sorry, I meant right-click then choose Open, then you should see the authorisation dialog.
I’m closer, but not sure what to do next?
If I click OPEN then I get the error message I posted. Or, I can click “OPEN WITH” which gets me here:
I suspect it wants me to open it with TERMINAL.APP but that’s just a guess - and if it does open in TERMINAL.APP, what do I do next?
This may or may not be related to the DeepPRIME issue. My Apple ScreenSaver used to show my photos, but on two of my Apple computers, that is now broken. A screensaver showing “glowing patterns”, or whatever, designed by Apple works fine, but when I try to use images, I get an all black screen. I told the tech I was talking to about XPCCort, and he was aware of it. He told me my screen saver issue would be corrected in an update.
Who knows - maybe this is related to DeepPRIME issues? I’m just wondering out loud…
If human help is not fast enough here is the official howto 
I only use the method described in the note.
Sorry I am not on my Mac so no screenshots.
On your MacBook Air, it would help if you clicked on the Apple logo at the top left, then clicked on “About this Mac”.
(image deleted for now, until I can edit it)
Then you could capture the first screen, as well as “Storage”, and “Memory”. With all that information, we can understand a lot more about your computer.
Have you done all of Apple’s updates when they became available?
On my Mac mini, with a powerful processor and lots of memory, and all the updates, it takes a minute and a half to Export a large file. Your MacBook Air might not have enough resources to do it.
You may want to run “Activity Monitor” that came with your MacBook Air (I think), and there is also “XRG-3” which is an even more powerful monitor with nice graphs. I plan to use XRG-3 while exporting, but will do so tomorrow. I’m getting sleepy.
https://gaucho.software/Products/XRG/
You might also want to call Apple Tech Support - it’s free, they will connect to your computer safely, and suggest things you can do to identify problems. They will also check if you are fully up-to-date. Depending on a lot of things, including age, you may not be able to talk advantage of everything DxO offers. I suspect the. graphs from XRG-3.
This may or may not be helpful.
I was running XRG-3, so I closed it, and re-started, giving me an “empty” screen.
I then started an Export of the image that I knew would fail.
Before the failure, I did a screen capture for CPU, GPU, and Memory, which I’ll copy below.
Please disregard the partial boxes before and after these three.
To me, CPU went way up, GPU went up quit a bit, and Memory went off the scale. If the yellow and red bars indicate danger, the Memory went quite a bit higher.
I don’t know how useful this may or may not be, but just in case, I’m posting it here for DxO to review:
No issue whatsoever here, with DPL5.0.1.41 on macOS12.0.1 on MacBook Air (M1, 2020)
These are the sidecars I used:
1 and 2 are Mike’s, the others are new from scratch.
I’m surprised about the file names shown above, actual file names are:
Note that I renamed the sidecars (removed the -n suffix) and imported them manually for each test. Automatic import/export of sidecars was disabled, which is my default setting. 
You’re running on the new Apple chip, and I’m running on the older Intel chip. At some point I’m going to need to update, but I’ve only had this Mac mini for half a year or so now, buying it used from my nephew, who wanted the new Apple chip in his Mini. The older Intel based Mini has many more ports than the new Mini - until they improve that, I can’t update.
No need to rush it, Apple might bring back some ports like in the new MacBooks.
