P: Full Screen mode: Print & Book modules show wrong colors but output correctly

Does anyone know if the actual rented images on Blur are affected or if it is just the preview in LR that appears washed out?

Does anyone know if the issue is just the preview or if the actual Blurb printed book images are washed out too?

Google translation: "In the latest Lightroom and the Mac OS BigSure 11.4 software, there is STILL the error in the Print module that the colors are displayed incorrectly (washed out) when the Fill in checkbox is ticked."

Why conversations get merged:

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-auto-import-to-folders-organized-by-date/5f5f44f14b561a3d422ab0ba?commentId=5f5f48984b561a3d422bdf45 

Im neusten Lightroom und der Software Mac OS BigSure 11.4 besteht IMMER NOCH der Fehler im Modul Drucken, dass die Farben falsch (verwaschen) angezeigt werden, wenn der Haken Ausfüllen gesetetzt ist.

Agreed!  That was one of the steps I use for bulletproof exports to Bay Photo.

 It seems that LRC is not a priority.  There are multiple updates to PS to every LRC update.

It can't be THAT difficult to fix!

I'm glad it's not just me having this problem. It started for me once I update to Big Sur. Consequently I have not printed a book for over a year as I was hoping it get fixed. Very frustrating that the new update doesn't fix it. 

I thought Blurb would be interested and put pressure on Adobe as I suspect others are putting workflow on hold until it's sorted. They didn't seem that interested and just said raise it with Adobe.

I think we just need to keep make making noise so that Adobe start to listen and sort it out!!!

It is frustrating. I don't know when an employee last read this bug-report thread, but it is marked as Acknowledged and it has an internal tracking ID assigned, so at least it's in their internal system.

Hi,
I just updated to 10.3, and yes it's still a problem!

IS ANYONE AT ADOBE READING THIS?  IT'S BEEN GOING ON FOR OVER A YEAR!

in new version Lightroom Classic 13.3 this issue doesn't seem to have been changed!