PL 9.x has been a disaster for a vast majority of users. Yes, except you at the back, you’ve had a fantastic experience but that’s not the case for most of us that have to live with the constant crashes and deafening silence by DxO. What other possibility do we have until PL9 is fixed? Is there a way to download PL8 in the meantime, as a workaround, a gesture of good faith by the company? I’ve asked for a refund several times, earlier on when it was clear that the crashes would not be fixed anytime soon but my tickets were closed on the spot without even an acknowledgement or apology. It’s obvious to me at this point that DxO is a scam company. Any ideas?
6 Likes
You’ve made up your mind.
Yet everything has been explained.
I grant you DxO’s silence.
Pascal
3 Likes
To be fair we are used to silence, you should have surprised him with sound.
2 Likes
ON1 is pretty good but a steep learning curve and Luminar Neo is very good, not much of a learning curve either. It will work on much lower spec machines and renders really quickly. I still think I’ll keep my PL7, that works really well too.
1 Like
What’s been explained to me? Please, enlighten me. Tell me why masking or exporting causes my (and many other’s) computers to crash, in configurations that far exceed DxO requirements. Tell me why I (we) don’t deserve an answer to our tickets. You must be one of the company’s paid influencers that go singing the praises for a product that’s unusable for many of us.
2 Likes
There is, if you have a license.
Log into shop.dxo.com and download the installer
or dig in your backups for it.
As for refunds, common practice is that you agree to the EULA by activating the product. Whether this voids the right to return an item within a given amount of time depends on local law and regulations. But I suppose that any interaction with a lawyer will cost more than a license for PL.
Other than that, DxO has so far published fixes and updates that made initially difficult products quite usable. This can take some time though.
1 Like
- But for some not a ‘disaster’ (may for a lot). If you has like 12-16GB GPU, thing just great at general, you can do everything. For some 8GB is fine, for some even 4GB is enough what they does.
- Forum has a big bias → as in here usually peoples come with problem.
- Even DxO specifications just say like "Minimum: 6GB for AI mask and DP3’. Just say ‘AI mask’, and not say ‘pre-defined mask’, just say DP3 and not DP XD2s. May some not realize this. And not forget, now lot of other running apps use GPU VRAM, even web browsers can use a visible amount.
- PL9 Manual AI mask + DP3 export can work even with 4GB GPU VRAM (withs some workaround). I even write a post about that. May worth to check it here in the forum (DxO 9.2.1 + Manual AI mask + DP3 NR Export can work even with 4GB GPU VRAM! - #5 by andras.csore).
- If you use PL9 like PL8 - like without AI masks, your just fine as with PL8, and you can do more advance Masking what comes with PL9 (layering, mask intersect (invert shape)), etc. If you cant work with GPU mode for whatever reason (like you have only 1 or 2GB GPU) you able to use AI Masking with ‘CPU only’. Of course, with CPU speed - but for manual AI mask and DP3 is still useable.
3 Likes
I have a Ryzen 5950x-64gb RAM-AMD Radeon RX 9060xt 16Gb VRAM (I had an Intel ARC A770 16gb before that and PL also has problems wit it). Latest Windows version, drivers, everything is at least double the recommended (not minimum) requirements. No other application crashes, Adobe Photoshop, Lightroom, Topaz, On-1, games of all kind, databases, virtual machines, design tools, benchmarking tools, etc. Again, not a single app crashes. I haven’t received any answer from DxO. I’m glad it works for you.
3 Likes
Quite nice setup. However, frankly, i not see written in this post/comments what is the issue of yours (if any)? PL9.3 do, what? When? How?
Crashes when using masks, crashes when exporting, crashes when picking an option from a dropdown list, crashes even when I have an image open, choose a mask and leave it there; I’m just looking at it and it crashes. The logs indicate that the main executable crashed. I must have submitted close to 50 diagnostic files, opened several tickets, and not a word. My experience is not unique, as you probably know. Throw me a bone; come out and recognize there’s a problem with the software but you’ll extend the support period until the issues are worked out, or give us access to a previous, functional version, anything to show that DxO cares about their customers. Choosing silence says the exact opposite.
2 Likes
Is it not fixed in version 9.3?
Hi there.
You don’t really give the forum readers any real information which might allow them to help you.
If you include your specs, drivers info etc and attach a problematic image and its .dop side car - it might allow them you look at it a bit better.
1 Like
No, for me.
Majeur a poll to Knowles who has issues and with which OS.
I ma not an expert in english but it is a pain to answer in english when French with the most intelligent smartphone in the world !
From TimE to time, it miss to recognize english and makes corrections in French.
So create a poll !
2 Likes
Please remember that tech forums are filled with folks who are having problems. Most users are not.
The phenomenon is similar to sitting in a hospital lobby and thinking the vast majority of people are sick or dying because of the environment around you.
that being said, DxO could mitigate our anger and frustration by being more transparent and verbose about support issues.
10 Likes
Gabe, they don’t know what the problem is, that’s why there is silence and that is what is worrying.
Or may its unique. As i see most of the issues is related with something like: ‘But if i have 3 pre-defined AI mask and try to export then…’ or sort of it.
So, seems witchcraft. May against witchcraft fight with ‘science approach’, of course its takes time. Even small details may count. I not know what ‘tests’ you already over, but i suggest to start with some ‘base tests’ and if its no results, then start ‘steps up/raise the bar’ in test steps.
Try basic test ones, like:
- No overclocking, etc.
- Close other applications as possible (no web browsers, nothing as possible)
- Disable antivirus for like 15 minute and try editing
- Revert-back GPU river like: 2 version before actual, 5 version before actual, 1 year older
- If DeeprimeRendering is turned on, than turn it off. Note: restart PL after that.
- Set this ‘paralel export count’ to one (1). Note: restart PL after that.
- Etc.
See if its helps you out or not. May something happen, may not.
‘Step up’ based testing.
Lot of small steps.
Create a folder like: ‘C:\PL9_test’, inside of like ‘Step01’, ‘Step02’, ‘Step03’ and so on.
Not put any photo to any yet.
Step 1:
- Navigate in ‘Photo Library’ to ‘C:\PL9_test\Step01’
- Quit and Start PL
- PL start with this ‘C:\PL9_test\Step01’ folder. (its empty)
- Wait for a while, PL is ‘crash itself’ or not. I not known what can be a ‘while’, what you think for enough for: ‘I’m just looking at it and it crashes’
Step 2:
- Put one (1) jpg to ‘C:\PL9_test\Step02’
- Navigate in ‘Photo Library’ to ‘C:\PL9_test\Step02’
- Quit and Start PL
- PL start with this ‘C:\PL9_test\Step02’ folder.
- Wait for a while, PL is ‘crash itself’ or not.
Step 3:
- Copy the step 2 jpg to ‘C:\PL9_test\Step03’
- Navigate in ‘Photo Library’ to ‘C:\PL9_test\Step03’
- Do some basic editing on that, like change exposure.
- Quit and Start PL
- PL start with this ‘C:\PL9_test\Step03’ folder.
- Wait for a while, PL is ‘crash itself’ or not.
Step 4. - 5: same with RAW. Folders of course like ‘step04’ and so on. Set NR to ‘Standard’.
Step 6: A add some local adjustments, simple, like 1 Control Point.
Step 7: Export the previous
Step 8: Set NR to DP3 and export
Step 9: Set NR to DP XD2s and export
Step 10: … whatever looks logical
Step what’s seems logical to ‘rule out’ / ‘narrow down’ cases where / until its okay.
Steps can be ‘larger jumps’.
As you describe the situation, may (just may) something wider thing may can be an issue. I don’t know, may ‘virus checker’ don’t like PL. May GPU driver quality not in his finest moments.
May its note easy to ‘catch’.
Don’t get me wrong the good people here are generous in their time trying to sort out DxOs problems. So much so, maybe DxO should employ them? But not many solutions will be generated here. DxO are the ones that need to pull their finger out.
1 Like
Sometimes they don’t know, and sometimes the problem is staring them in the face. Look at this portion of the error log, it tells exactly what the problem was and the procedure where the crash happened. This doesn’t get fixed by switching to an older (or newer) driver; this is buggy coding, and DxO has to fix it.
It will be on their To Do List 
Logs can helps, of course. But may not say what cause, may the ‘exactly’ not so exact and so on.
Or if the driver send back something wrong, than may the driver is the issue?