The video explains the critical problem with CDR 2022.
I am hoping CDR developers take note.
https://youtu.be/E1GHcI7-0jU
If anyone knows what the problem is please let me know.
video part 2 deonstrati9ng the difference between CDR 2019 and 2022
https://youtu.be/DG8-o7KJtv8
This is clearly not a system problem it is a CorelDRAW technical issue.
Working on a video (as I learn) to post for you guys now. Just FYI 2019 was so bad it was the only version of Draw in 20 years I never used for production. I don't even have it now so I cannot tell you how it works.
The eyedroppers are weird on my system, but they provide proper conversion just as one would expect. The document palette is also a bit odd; I never would have noticed as I never use it if it were not for the posts.
Wow I really got back into this it seems that if you create a CMYK object, convert it to a spot color and then convert it back to CMYK, THE FIRST TIME, it returns to the original CMYK build.
By the rules of the ICC that's not supposed to happen, however I wonder if Corel will call this a feature? The second time you take the spot color object and convert it back to CMYK it converts correctly.
If you start with a pantone color and convert it to CMYK it works correctly the first time, I went all the way back to 2018 and all but 2018 fail. The 2018 version completes the conversion from pantone to CMYK as it should.
I expect to have the video to post tomorrow.
David, you are correct 2018 was superior to 2019, I had uninstalled 2018 a while back not thinking I was going to need it. CDR2019 was to show how the color picker was working in that version compared to 2022
Well, we're into the world of the bizarre and weird here, I have it mapped out, but I'd bet dollars to beans that (if anyone at Corel remembers) Corel did the behavior in 2019 going forward as a safe return from a CMYK conversion to spot color to the correct the source CMYK build as an OOPS cure.
If you start originally with a pantone color and convert to CMYK the result is as expected. (The expected CMYK color is not a CMYK build that would generate the source pantone color if you started with CMYK and converted to pantone), I know that's weird but it's the truth. The ICC is odd that way.
If you start from a CMYK color to a pantone color the resulting pantone color is as expected. If you take the resulting pantone color and convert it back to CMYK it returns to the source CMYK numbers, (like an undo), that's unexpected. If you do it a second time it produces the expected result. It's been doing that for 4 versions now, 5 if you count the September update.
I'll post my video tomorrow if the rendering works out.