Photolab 5 Today?

I saw that, so it seems it is part native. I hope it becomes fully native soon, as Apple transition should be completed by this time next year. I hope we don’t have to wait for PL 6.

Can any DXO staff shed any light on this?

Thanks

DeepPrime is the slowest action in DXO. Is the rest of Photolab slow on M1 Macs, I use Windows and everything is instant apart from DeepPrime.?

I haven’t PL 5 that much on my M1, but it is faster than PL4. Same on my 2017 27" intel iMac. The M1 is a bit faster than the iMac. Deep Prime significantly faster on both machines with the M1 being even faster.

Not even in your wildest dreams. C1 releases a new version every year. If there was a 12 month upgrade guarantee it would mean that the first year’s upgrade after purchase would be free.

I completely agree, I’m new to DxO - buying PL4 less than 3 months ago, now I find there’s an 80 euro fee to upgrade just 3 months later. Most software I’ve bought in the past this close to an update has been good enough to give it for free.

2 Likes

This feels like a 4.4 update. The only significant addition for current users is the Chroma and Luma sliders taken from Nik Collection Silver Efex and Vivenza. I expect the next Nik Collection update to add these tools to the rest of the collection. :face_with_raised_eyebrow:

If they’re going to charge for minor updates, they should both offer a far more generious discount, while also extending discounts to users of Photolab 2 and earlier. If you’ve spent a small fortune on Photolab, Film Pack, View Point, Nik Collection, you shouldn’t feel racked into a 2 year upgrade cycle, particularly if updates are as minor as this one.

3 Likes

It’s not twelve months but for the last couple of years every September CaptureOne starts to sell the current version with the next version (usually drops in February the following year) bundled. So six months. Which would have covered the purchaser above.

1 Like

New C1 versions are released in November or December, C1 22 is announced for December. A free update is usually possible from the date of purchase in July or September - so about 3 months.

As a C1 Fuji user, I can tell you that PhaseOne is not as customer oriented as you think.

Announcement from what I remember is not release (very strange behaviour btw, announcing new releases and selling them without a feature list and without software to deliver) and actual release comes in February or March.

As a C1 Fuji user, I can tell you that PhaseOne is not as customer oriented as you think.

I agree. DxO is driving me off with a stick. The new control over U-point masks is exactly what I need to be able to continue with PhotoLab and not have to go over to C1 for anything. But I’m not going to be forced to update my OS every year to the latest version or latest version minus one to continue to use PhotoLab.

DxO has shortened product support to the point it’s laughable. Current -1 is not what professional applications do.

BTW, there is a path back for DxO. Release PhotoLab 5 with Mojave support and commit to supporting current OS -2 going forward. @StevenL Real men recognise their mistakes and correct them.

But this will mean load of conditional code to cope with having to support both M1 and Intel for things like DeepPRIME.

As it is, Mojave is the last version to run 32-bit code and that has meant, up until now, DxO has had to write conditional code in some places where necessary, just to cope with a non-64 bit platform.

And this has been the breakpoint for a lot of software, not just PhotoLab - the need to continue to support conditional code, going forwards, is an unnecessary burden.

Don’t forget, Apple signalled the move to 64 bit as far back as 2014 (to the best of my memory); when I was working on an app for macOS and iOS. We were warned that, if we didn’t provide 64 bit apps, they would not be approved for the App Store. This is in 2014!

So we have had 7 years to plan for that inevitable day. I just tried to run the iPad app that I created back then in Xcode on Catalina and it wouldn’t even compile. Why? Not because my code was incapable but because it relied on a cross-platform external library, written in a 32 bit only language that we couldn’t recompile.

In order to revive that app, we would have had to rewrite, from scratch, several thousand lines of code, translating from one language to another. Our choice was to either do that or fold the project before it even go to see the light of day. Unfortunately, not being a megalithic company like Adobe or such, we ended up folding it with the loss of over two years effort and money.

So, my question to you is, what do think DxO should do? Spend enormous resources on supporting legacy 32 bit code, or move on with the majority?

Not to mention the market share of Catalina over Mojave…

4 Likes

Hello @uncoy,
At DxO we know your point of view (and from other users who voted on the related thread) on macOS support for a long time. Based on the cost of supporting more macOS versions and the number of PL4 users on macOS Mojave, we still decided to drop macOS Mojave support, even if it means losing some customers.

We apologize for the frustration brought by this change but we still believe that this is the right decision so that most users can enjoy more and better features in the future.
There is no plan to go back on this decision.

Lucas

2 Likes

Strangely enough, brand new FilmPack 6 is Mojave-compatible…

DxO FilmPack 6 - Shop is not listing macOS Mojave in supported system requirements.

This means that:

  • We may drop macOS Mojave compatibility anytime even in a minor update
  • You will not get support from DxO if you have an issue with FP6 while on macOS Mojave

“supported” precisely means that we provide support. Unsupported may work by luck or break anytime.

OK, goodbye :broken_heart:

4 Likes

Announcement from what I remember is not release (very strange behaviour btw, announcing new releases and selling them without a feature list and without software to deliver) and actual release comes in February or March.

It was announced in August and is scheduled to be available in December. The iPad app is scheduled for release in early 2022, but exclusively for iPad Pro with M1 processors.

Thank you for taking the time to directly address my complaint.

This is a very poor calculation, as you are not just losing revenue you are losing goodwill and turning your advocates into detractors.

It’s a very poor and primitive decision. MBA’s are not known for their ability to run a company properly. Generally great companies are created by engineers, boosted by talented marketers and then run into the ground by modern MBA style thinking. Hélas, it appears DxO has gone through the brilliant engineers phase, unfortunately missed the talented marketers stage and gone straight to the short-sighted MBA phase.

As for counting the numbers on Mojave, I for one have disabled and blocked most of your telemetry and I’ll bet many of the others on Mojave take similar care of unsolicited outbound communication from their computer.

Many, many photographers and creative people will see DxO’s lack of support for anything but the latest OS and will now run for the hills. What artist wants to buy into software which requires immediate OS updates and forces its users to buy new computers?

It’s no wonder that the DxO community has the lowest percentage of first rate photographers (sorry to all of us, I’m one of that community too) among all the major photo tools, far less than the quality of the software would normally command.

Strangely enough, brand new FilmPack 6 is Mojave-compatible…

Funny about that @scribe. I spent about forty minutes trying to get PhotoLab 5 to open on Mojave with no luck today (expecting it to crash even if I got it to run but interested in where it would crash). I’ll give FilmPack 6 a try.

@Lucas You wrote to @Scribe

You will not get support from DxO if you have an issue with FP6 while on macOS Mojave. “supported” precisely means that we provide support. Unsupported may work by luck or break anytime

Strange, DxO does something right for a change and now tries to make sure doing the right thing doesn’t pay off (by declaring no Mojave compatibility in the specs and now in your person publicly announcing that there are developers in DxO keen to break that compatibility).

I would be fine living with partial support for PhotoLab 5 on Mojave. I.e. Mojave users will miss out on some new library features for instance or some speed increases (DeepPrime is plenty fast in PhotoLab 4) but would get:

  1. the improved U-point technology with the ability to control U-point luma and chroma sensitivity for each mask. This is breakthrough technology for PhotoLab users, allowing us to enjoy real mask selection with much less hassle and trouble than either Lightroom or CaptureOne users.
  2. Fuji X-Trans support. I have a bunch of files shot on Fuji X-Trans which I’d love to process in PhotoLab and would consider adding a Fuji camera as a carry camera again. I’ve already given up Fuji cameras for the sake of PhotoLab.1

Neither of those changes require any features from the new OS.

Yes, there may be a small amount of hassle to maintain a Mojave version (and to make PhotoLab current OS -2, which was what was promised but is not currently being delivered) but reasonable OS support 2 would certainly make PhotoLab a far more attractive product to artists and photographers. DxO should be there to help its customers, not help itself, whatever the selfish, miserable US educated MBA’s may say.

If DxO helps us, we will help DxO.


  1. DxO is now asking too much, demanding I throw away computers with 96 GB of memory and 100 TB of internal storage, PCIe cards, upgradeable graphic cards (with my RX580 and Radeon VII, I’m now on generation four of reasonably priced graphic card upgrades which is impossible with any other Mac).
  2. Let’s be very clear about what I’m asking for. I’m asking for current OS -2 (Apple unreleased beta versions do not count), not “forever support” for Mojave. By the time the next PhotoLab rolls around in a year I will be ready to move on to a new OS.

Generally to minimise update hassle, I move two to three OS versions at a time. I moved my computers from 10.6.8 to 10.8 Mountain Lion. From 10.8 I moved to 10.11 El Capitan (tried 10.10 but it was a disaster with broken networking and troubled graphic drivers). Then I went from 10.11 to 10.13 High Sierra.

The only reason Mojave is on my computers already is PhotoLab 4. Otherwise, I would still be running 10.13 this year. I would then move from 10.13 to either the final version of 11 Big Sur or 12 Monterrey but not for another year or two. Which I would choose would depend on stability and compatibility and general low-hassle factor. As in this more reasonable alternative scenario, PhotoLab 6 would remove support for Mojave (Catalina would support would remain) I’d have to make a decision next fall about to which OS I would move. OS -2 gives me the flexibility to plan and manage my IT decisions. OS -1 is quite simply customer-hostile, inflexible and unreasonable.

Is that the kind of image DxO is trying to build for itself? Ask your marketing department how much they like this characterisation your hardline developers are creating for the company and how much advertising money will have to be spent to counteract such impressions. The marginal development costs for support OS -2 will look cheap in comparison.

This whole section is complete nonsense, Joanna. Mojave is entirely 64-bit but can run some 32-bit applications. There’s absolutely no reason that DxO has to put a single 32-bit piece of code in their applications to support Mojave. If you are talking about external plugins, it’s very easy for DxO to announce “PhotoLab 5 no longer supports 32-bit plugins.” And that would be a much more reasonable position to take than just throwing all the Mojave users off the pier with cement boots on.

Speaking of which, let’s move on to your OS share numbers. You don’t give your source.

  1. It’s probably based on internet numbers which undercount creative studio computers, some of which are not even online.
  2. what they don’t take into account are the number of creatives running MacPro 4,1 and 5,1 with Mojave as the last OS they can accept.
  3. Many pro creatives deliberately stay a version or two behind for the purposes of stability and productivity. Those pro creatives are exactly the people who are not using DxO products en masse. There’s almost no pro endorsements of DxO for anything except emergency noise reduction or Silver Efex.

Dealing directly with the numbers, what I’m seeing is that Mojave users make up over a third of the Mac users who are not on latest OS (Catalina). I would guess that the those running 10.11 El Capitan or 10.10 Yosemite are secondary computers which are not kept up with latest software and are used mainly as internet appliances and office computers (I have just such an El Capitan MBP which came in handy for testing SSL compatibility this week, and is still a great macOS experience). Counting this way Mojave users are close to half of the Mac users not on Catalina.

In short, if DxO would support OS -2, DxO would be pissing on half as many of their customers. OS -2 makes users comfortable. OS -1 turns DxO into a dictatorial ogre, pushing their customers around.

Please don’t project your issues as a one-man band trying to support multiple OS onto a full development team. My team currently supports 11 WordPress releases with complex video software. Occasionally we have to remove support for 3.7 to jump to 4.5 minimum version or remove support from PHP 5.6 to jump to 7.2. But we try to support our publishers as long as possible. We are not actively looking to force upgrades on them or bully them.

And frankly I couldn’t imagine doing so or why we would or why DxO has decided to do so. It’s one of the stupidest marketing or “cost-cutting” decisions I have ever seen in my life. It’s a great pity as the engineering is first rate and deserves better executive decisions.

@uncoy
I don’t understand…

What you’re asking, I quote “I’m asking for current OS -2”, is already the case :upside_down_face:

Next week = Monterey
Monterey -1 = Big Sur
Monterey -2 = Catalina

Unless the issue is all about the ‘one week difference’ between PL5’s release and the new macOS’s release, we already offer exactly what you’re asking for…

I quote “OS -2 makes users comfortable”.
So, why all the fuss??

Steven.

2 Likes

Thank you for your note @StevenL

According to your post, DxO now considers OS X versions which are unreleased as released. Nice. Released or not, a brand new OS is not even close to production ready.

OS -2 means OS -2 which is Mojave (issues resolved, good version running well) - Catalina (a dog) - Big Sur (still has issues but has potential). Monterey doesn’t even enter the picture. The sophism of your answer is shocking as PhotoLab does not run reliably on Monterey.

If you don’t see the problem yet, you will see the problem very clearly eventually. I’ve invested a lot of time and money in DxO, supporting DxO even when you held loyal customers hostage to buy a second copy of PhotoLab to be able to buy Nik 2 or Nik 3. With these Nik releases there really should have been an initial version and one update, not three. v4 is a travesty which makes Nik run worse and reduces compatibility. Loyal customers have been paying for DxO to steadily make the software worse. There may be good intentions behind Nik v4 (trying to rebuild the core code for a different future) but in its current state it’s not release quality software.

I mention the slow burn Nik fiasco just to be clear about how DxO is bilking its most loyal customers now and building a lot of ill will where there was good will before. Good will gets good word of mouth and makes customers advocates for DxO. Ill will creates bad word of mouth or silence.

Cutting off users because your development team is too lazy to maintain a Mojave build (OS -2) is really very stupid. But I’ve explained that above. I’ve provided the internal feedback I can at this point on DxO’s short-sighted customer-hostile policies. Future feedback will mostly be external.

The irony is hilarious. Impecunious DxO has put me (and dozens of others of their keenest users) in the position of not celebrating a new PhotoLab release but being extremely angry that we cannot give DxO our money again. In particular the new local adjustment features are exactly what I need to push my post-processing/photography forward. Instead I’ll have to go to CaptureOne as C1 support OS -2 (or even OS -3).1

Way to score an own goal, DxO. You’ve alienated one of your top ten advocates and are in the process of driving him to the competition.2


  1. I’m not going to throw out two ideally configured computers which perform superbly with PhotoLab, FCPX and even DaVinci Resolve. To replace these computers with like for like in terms of graphics cards and storage would cost over €20,000. There are a lot of pros out there still happily running Mac Pros. But in general the whole issue of pushing users on to new OS before they are ready is customer hostile.
  2. There’s a huge community of pro users on C1 who share amazing tutorials on how to get the most out of layer masks, its superior colour tools and its new healing tools to create astonishing professional work. With OS -1, DxO will never built the same kind of pro photo community around the product and will always be forced to heavily advertise to acquire new users. You guys just don’t get it (your unwillingness to properly partner with existing DAM solutions and Affinity Photo and other HDR and Panorama tool builders is also inexplicable).
3 Likes