Lightroom Ventura

[Cary Polachek]

Iam seemingly able to install and select from the list the new CUPS driver, when I go to Lightroom I can see the driver, when I launch the settings dialog, the option to adjust printer settings isn't responsive. Can't change anything there, the "OK" button is enabled but doesn't actually do anything. I can only click "Cancel", and that causes Lightroom to immediately, and predictably crash every time.

I have similar problems. I did updated according to a Canon support Specialist.

Driver is not saving the presets. always revert back to the default paper, and rendering. If you save a different preset is not maintained. Color renderinf is totally off. previous canon diver didn't have theses problems.

After you download and install the Canon CUPS driver you need to add the printer in the Printers & Scanners app. When you select the "+" add icon you need to wait several minutes for the IJ Series driver to appear. The AirPrint version appears first and many folks select that.

I Clearly believe is an Issue with Mac OS Ventura (I have 13.01). I have sort of a work around it. I realized that my printer firmware was outdated. Once updated, it start working if im not saving presets at the printer level. What Im doing is saving the presets to each paper size I use as a Lightroom classic Preset. So, I normally use Canon Semi Gloss. Saved the lightroom printing preset with that, and if I need to change the paper type, that is the only thing I do. I know is a weird work around but at least im printing correctly.

At this point there is only to possible scenarios (unless you find another work around easier than this one):

1. Go back to the previous Mac OS. I know its possible but I will call Apple to assist you in the process. Or

2. keep using the work around until apple updates the OS, hopefully in the next update.

By the way, Adobe and Canon were not very much contributing on this matter. Im amazed that Adobe and canon will not discuss this matter with Apple, as Im sure its an issue that is more general.

I am experiencing the same problem. After much paper and ink, I am led to conclude that the latest MacOS Ventura driver (24-20) does not work correctly. This leads me to wonder about the integrity of the quality control for the software. As a former software engineer, I conclude that the problem is quite obvious to anyone conducting a competent test of the software. Unfortunately, until Canon releases a working driver, I am unable to print.

I don't have a Pro-200 (I have a Pro-100) so I can't troubleshoot your issue, but what you are describing frequently is the result of having the AirPrint driver installed and not the IJ Series driver.

Thanks John - I tried to make sure I did not install AirPrint - and could see the IJ Series driver, would select it, add, etc. - never worked. In the end, quite frustrated, as I've been installing print drivers for Epson and Canon printers for years, I ended up calling Canon - and a super nice support guy walked me to the steps, but we deleted a bunch of files in my computer, and I used a link he gave me for the new drivers. Took about 25 minutes, and many steps, but worked. Something was persisting in my system... But I am super happy to report Canon was very very helpful.

I see the Pixma PRO-200 equivalent of the first screenshot. That leads me to suspect that the problem has nothing to do with AirPrint. Needless to say, I would like to be incorrect about it. I have never had to wait several minutes for the correct entry to appear in the list when adding the printer. Moreover, the firmware on the printer is up to date. By the way, I tried defining and saving presets for each print type, but the system would save the defaults no matter what I did. I will conduct a few more experiments, but I am not yet confident that I will end up with a solution or workaround. Right now, my PRO-200 printer would serve well as a boat anchor.

I recently sent a JPG file to a friend of mine and he opened the file in Photoshop. The JPG was exported from AP v2.0.4 (Mac Ventura). When he opened the file in Photoshop, it automatically opened the file in Adobe Camera RAW instead of opening it normally, as if the file I sent him was a RAW file instead of a JPG. I tried it myself on another computer I own that has Photoshop installed and got the same result. It launches Adobe Camera RAW, with a lot of crazy slider settings in the Basic Tab.

The original file was a RAW DNG file from my Canon DSLR. I processed the original RAW DNG file in AP v2.0.4 (Develop Persona) and I chose to import it into the Photo Persona with the RAW file (linked or embedded, I forget which). I wanted to retain the ability to go back and forth between AP and the Develop Persona so I could make adjustments in the Develop Persona. That all worked fine, as designed.

When I exported the file from AP to JPG, I suspect AP must have written something in the metadata so the JPG looks like a RAW file, which is what caused Photoshop to launch Camera Raw. To me, JPG is an industry standard file format and should not look or open as a RAW file in any program (even AP). The original AfPhoto file format is a different matter, since you want to retain that active link to the original raw file (if linked).

I have experienced this a few times, but could not find now a file that is causing this, and I think that when you post JPG files here on the forum they will be resaved at upload and the property that is causing the behavior is lost. Could you repost placing a JPG file showing this behavior in a zip file? It might also be related to specific Photoshop version so if possible, please specify!

I've been using LightRoom v6 and Photoshop CS6 for many years on my old Mac Pro running OS X 10.8.5. More recently I am working on my MacBook Pro 2017 running Ventura v13.2.1. My laptop cannot load Photoshop, but LightRoom v6 still works on Ventura. I am using AP v2.0.4 on my laptop.

My normal routine was, and still is, to upload my RAW images (Canon 5DmkII) to LightRoom. I have LR set to Convert the CR2 file to DNG format, apply my custom DNG Canera Profile to the image, and to write copyright Metadata, name, address, etc into the DNG file. All "Auto" settings are set to OFF. In the past, I would make edits to the DNG file inside of LR. If I wanted to do more editing, I would open the file (from LR) into PSCS6, including all LR adjustments, edit, then resave as a PSD and/or JPG file. OK, that's the background.

I ran some experiments this morning. First, I developed a RAW CR2 file (IMG-5931.CR2) using AP v2.0.4. I did NOT import this file into LR first, as I normally do. in the Develop Persona, I set the Develop Persona to export to AP with the RAW file "Linked". I edited the file, then Exported it to JPG from AP. I left Embed Metadata checked (as shown in the following screenshot).

I then opened this JPG in PSCS6 on my old Mac Pro and it opened normally as a JPG (in other words, it did NOT force ACR to open it). This file never went to LightRoom and was not converted to DNG format. The original AfPhoto file, and exported JPG file are in the attached Zip file.

Then I processed two additional RAW files using AP. Both of these files had been previously imported into LRv6 on my laptop. in one image, 5684.DNG) I "linked" the original DNG file in the Develop Persona before exporting to AP for further processing. I saved the file (which is included in the zip file) and exported it to JPG twice, once with Metadata embedded, and once without Metadata embedded. I opened both files in PSCS6 on my old Mac Pro. The file WITH METADATA opened in Adobe Camera RAW. The JPG file WITHOUT metadata opened normally in PS, without being forced to open in ACR.

I repeated this experiment with my original problem photo, 5765.DNG. This also had previously been imported into LR.. I opened it in AP Develop Personal, but this time I set the RAW file to be embedded when exporting to AP. As with the previous image, with a "link" to the DNG file, a JPG opened in ACR if the JPG was saved WITH Metadata, but opened normally if Metadata was NOT embedded.

My conclusion is that LightRoom is writing metadata to the file, which is retained even after edited in AP and the Develop Persona. When exporting to JPG, this LR Metadata is probably retained if "Embed Metadata" is Checked. If Metadata is UNchecked, that metadata which flags the file as a "RAW" file is stripped away, and the JPG opens normally in Photoshop. I have also notice then when a JPG Exported file is loaded back into LR, if the Metadata is left embedded, all the colors are whacked out in LR, since I assume LR is applying metadata to the finished JPG file. So, if using LR, and perhaps other similar software, it is best to save the JPG export from AP with "Embed Metadata" Unchecked. Unfortunately, this also strips metadata that we might want to retain in the file, such as copyright information, etc.

Thanks for the update. Yes, it seems that Raw data cannot be stripped (or marked as having been processed), while some other data selectively can. I can also confirm that the latest Photoshop also opens the raw interface.

What data can "selectively" be stripped, or altered, and how? I figured the "Embed Metadata" checkbox was an all-or-nothing thing. I'd love to be able to strip JUST the metadata that tags the JPG file as RAW and forces other Apps to see it as such.

3a8082e126