PL 9.x workarounds?

Every driver sends back back data? Several versions of Intel drivers (when I had my Arc card) and same thing for the AMD drivers? And what does that say about the PL coding, that it’s not doing proper error handling? That’s basic programming. In any case, we can’t fix the drivers or the PL coding. That’s for the company to do.

Think more like a ‘glue’, but yes, its very-very important. If its ‘fail’ or miss the things, all thing fail. And error handling for GPU stuffs seems not so trivial.

I am running PL9 on a mac mini m2 pro.

ZERO PROBLEMS.

If you are using a windows machine maybe that’s the problem?

1 Like

Was that comment intended to be helpful :thinking: ?

6 Likes

Windows is one of the supported platforms, last I checked.

3 Likes

And may you remember when this crash happen? Its still happen with PL 9.3.1?
May in there?

Common. This is pure whining. Forums are made of people with issues. That does not mean everybody have issues. If you go to the hospital, do you come out concluding darn everybody is sick we are all going to die ? I am very pleased with DXO, so are many many users. Your issues can be related to all kind of stuff, including a shitty computer. You should work with their support. This is a user forum, you will never get any DXO staff to respond here. I have an ongoing issue, unrelated to yours, and have an open ticket with DXO support, they have been very responsive and the issue is being worked on.

5 Likes

@Martin868 That’s your lived experience, which doesn’t mean it’s everyone’s lived experience.

Many of us have tried (unpaid) support and found it supremely frustrating.

It’s true that when issues exist, the number of people complaining about them in an online world will increase.

In my use of the various versions of PhotoLab since around version 5… version 9 has had the roughest launch and continues to have the most ongoing critical (hard crashes or unable to export) and performance (extreme slowdown) bugs.

This has not always been the case with previous versions of the software. Therefore blaming individual’s computers is nonsensical. Dismissing the real issues folks are facing as “whining” sounds like something a paid shill would say.

1 Like

You’re very lucky, most other people have been ignored. I must have submitted close to 50 crash reports, NOT A SINGLE ONE has been looked at or deemed worthy of an answer from DxO. The tickets that I submitted asking for a refund a few days after the purchase, when it was obvious that the software was non-functional for me, were closed without any answer or acknowledgement, not even a “sorry we don’t do that”. In other words, DxO has behaved like a scam company, they took my money and ran away. And I’m not the only one in this situation. So again I’m glad it works for you. To negate or dismiss the experience that myself and others have had so far is condescending and makes you part of the problem.

1 Like

I appreciate all your help, which is more than DxO has offered so far. My test case is very simple, I open an image (any image, in particular one with sky or water); put a mask on it, leave it there and just stare at the image and in a few minutes, it crashes. Or it does when I export it. It’s not a mysterious situation, and the error can’t be fixed by installing a different driver. I’ve posted an extract of one of the crash logs in another post but I’ll put it here, too, for simplicity. The error is spelled out, it tells exactly where it crashed and why. It’s there for everyone to see. This is poor coding, not hardware, not drivers, no insufficient performance. Coding, bad coding, plain and simple. And the worst part is that nobody gives a rat’s ass at the company. Not an answer, not an acknowledgement of any kind. There are similarly clear errors in other logfiles but I won’t bother posting them because we can’t fix them.

1 Like

I have asked 3 times for a copy of 8 on my new Laptop. They won’t provide it.

Is that for Windows?

By sheer dumb luck I’ve kept a copy of the PL8 executable. I’m tempted to find a way to get it online (although it’s 350mb so not sure how).

I don’t see why this would break any terms or EULAs as you’d still need a valid license key to use it.

May if you upload the photo, and the related .dop - if i have a time, i try it. With the exact (yours) photo.

put a mask on it,

Sometimes “the devil in the details” → like: and what type of mask? ‘Pre-defined AI mask’, like: People, Sky? One mask or lot of masks? Or just one some simple Control Point? What’s happen when no Mask at all? And so on…
That’s why the .dop file also good to ‘see the mask’.

leave it there and just stare at the image and in a few minutes, it crashes.

I think that’s the ‘witchcraft’. And its may (just may) suggest the issue is somewhere else than PL. As without external thing(s), seems no reason to ‘crash’ if you just stare. And i guess you not a witch or hydra to turn software’s to stone just with your gazing :wink: Overclocking? For me even the AMD Adrenaline own ‘Fine tuning’ overclock raise issues - a funny think its not cause issues in PL but in ‘Sid Meier’s Civilization VI’ - small overclock → ‘Civ VI’ crash once per hour, no overclock its just fine. May some other apps ‘hit’ PL? Pfff, who know now.

Also, may small things also count, like: you use ‘Loupe’ or not. Usually ‘crash’ happen after when you Exports something?

Or it does when I export it

Yep, that’s the thing, the Export. Its use additional resource(s).

I have only 4GB GPU (AMD), so i can’t test it with ‘Pre-defined’ AI masks, only with Manual AI masks (Selection, Area), and only with DP3 (and not with DP XD2s). But its still more than nothing.

Anyhow, please also write what is the settings in there (DeepPrime rendering):


If its enabled, than please disablee (and not forget to restart PL) and try.

Also, what’s in here:


May better to get to ‘1’ (one) for sure.

In the meantime, can you test it in ‘CPU Only’ mode? (don’t forget restart PL after change to this) → To ‘double-check’ the thing.
I’m quite sure in CPU mode its needs to work fine (of course, with CPU as-it-is speed)

I appreciate all your help, which is more than DxO has offered so far.

That’s the ‘spirit’ of the forum. Sometimes i have a little time for this type of help. May helps, may not. Holiday season is coming, so seems less time for that…
I think sometimes good if someone try to help himself, and its may helps for support also (to find out the issue in more details). Support is hard- i do various support things for 25 year - and its never easy, especially for ‘magic’ situations.

I’m not at home and don’t have access to any image now but from what I remember it’s images (any) that use AI masking that cause the most crashes. And yes, I can disable the GPU and DeepPrime and OpenGL and it may not crash but it takes 10 minutes to export an image; so what’s the point? I didn’t pay full price for a software that only works when most features are disabled. Especially when AI masks were the selling point. It’s like you pay full price for a Ferrari but can’t use it unless you take the engine out and push it down the street and when you ask the dealer, he’s no longer in town and nobody answers your phone.

‘The point is’ → For testing to ‘rule out’ things → To know things what works → Narrow down the issue area.

Like: “with 'CPU only its ‘not freeze’ when you just look at it”. Or if it’s: ‘its also ‘freeze’ in CPU only’ → its also can be an important bit of information.

OpenCL can be enabled, its safe.

And what type of AI masks? ‘Pre-defined AI mask’ like ‘Sky’, ‘Peoples’, ‘Subject’? Or ‘Manual AI mask’ like ‘Selection’, ‘Area’?

Even both ‘pre-defined’ AI masks and ‘manual’ AI masks is ‘just AI’ → but quite a difference ‘pre-defined’ vs ‘manual’ AI and also in resource needs, and also can cause quite different problems.
Frankly, most of the issues looks related with ‘pre-defined’ AI masks as far as i see. May not a bad idea check what with only the ‘manual AI masks’ first ?

I still have it on my old laptop. I hope… Either way, it’s time to table this piece of trash. Update came today with bug fixes…. Downloaded massive update. 1 image… software crash. Unreal. I’m out. PL9 will collect dust while I touch base to see if they get somewhere.

2 Likes

It doesn’t really matter because ultimately, we can’t do anything about it. It’s a coding issue, improper error handling, and a ton of other things that we can’t change. If the way to make the software work is to disable everything, then that’s not really an option. It’s up to DxO to look at all the errors and make changes. They’ve chosen to ignore their customers while at the same time, upsell support services (I wonder how they’ll be able to provide that). We’re spinning our wheels here.

Gabe,

As-tu mis à jour les drivers de la carte mère ?

Quand j’ai changé de carte graphique, j’ai eu des problèmes d’utilisation CPU, de chauffe, etc. et la mise à jour des drivers de la carte mère a résolu mon problème.

Je pense que c’est une piste à explorer.

Okay, i get it. As you like/think.

Oui, j’ai tout essayé. Drivers video, drivers carte mère, dernier bios, etc. Mais PL9 continue à crasher et envoyer des fichiers log à DxO mais je n’ai jamais reçu de réponse.