Fooling Adobe Lightroom into thinking that a Canon S95 RAW comes from a S90

[Albo75]

So...

Canon RAW to DPP to jpg = no bar
Canon RAW to ExifTool to DPP to jpg = no bar
Canon RAW to ExifTool to ExifTool to DPP to jpg = no bar
Canon RAW to ExifTool to LR = bar
Canon RAW to ExifTool to LR to DNG = bar
Canon RAW to ExifTool to PS Camera RAW = bar

... which means #2: that the Lightroom/Photoshop CR2 reader isn't very robust? 

[Phil Harvey]

... which means #2: that the Lightroom/Photoshop CR2 reader isn't very robust? 

Yes, it would seem that way.  It looks like your only hope to get this working with the Adobe products is to wait for an update for the S95.  All of the Adobe products use the same converter.

- Phil

[JavaJunky]

I'd just like to chime in because I've been playing with ExifTool today trying to get my S95 raws working with Adobe Lightroom. I am happy to say I got it working though I did have some black bars in some cases. Here's what I did:

I ran ExifTools with the following command: exiftool -canonmodelID="PowerShot S90" /Volumes/MBP_BACKUP/S95_Files/cr2 -ext cr2
MBP_BACKUP is just my external firewire drive. I only changed the canonmodelID and not the model tag. I first tried using Adobe's DNG converter on the new CR2 files, but when I imported the converted DNG files into Lightroom 3, I got the black bars. I decided to delete the DNG files and import the new CR2 files into Lightroom and have that convert them to DNG files. This worked. I exported a quick JPG from one of the new DNG files and there were no black bars. Out of curiosity, I opened one of the Lightroom converted DNG files with Photoshop CS3 (yes, I need to upgrade) and surprisingly, Adobe Camera Raw was showing the black bar.

My theory is that my version of ACR, which Photoshop uses to open raw files, is too old and is misreading the DNG file somehow. I have Camera Raw 6.2 running in Lightroom 3, but Photoshop CS3 can't upgrade to ACR 6. That is my guess. Hope this is relevant info.

Took three shots just now and converted with Canon software to jpg. All three came out fine.

Great.  Now we have a good starting point.

Ran ExifTool and then imported to LR and converted to DNG. The second image has the black on the left.

Do you get the same thing when importing this image into DPP?  If so, does the black go away if you use exiftool again to change the model values back to S90 and import this double-edited image into DPP?  There are a few possible outcomes:

1) black bars show up on the edited image in DPP but go away when the model is changed back to S90
    --> indicates that there is some real difference between the S90 and S95 images causing the black bar

2) black bars don't show up in either image
    --> indicates that the Lightroom CR2 reader isn't very robust

3) black bars show up on both images
    --> indicates that ExifTool is causing the problem.  If this is the case, I want to know.

I tried some tests here, but I only have one S95 CR2 and it didn't give a black bar when I changed the model to S90 and imported into LR2.

- Phil

[Albo75]

Not the same for me. I get random black edges no matter which way I import.

I appreciate all your help Phil!

[foosion]

The command line would be:

exiftool -model="Canon PowerShot S90" -canonmodelID="PowerShot S90" FILE

As JavaJunky says, it's not necessary to set model, you can just set canonmodelID.  That way, Adobe will edit the picture as if it were an S90, but list the camera as an S95 for searching, etc. purposes.  I'm confident enough in the results to add -overwrite_original.

The black bar can easily be cropped out.  Other than the black bar, pictures seem to work fine in Photoshop CS5 and Lightroom 3.  With luck Adobe will release an update sometime soon.

Phil, thanks for a fantastic program!

[dtour]

Forgive me, Im a beginner with a really stupid question.  I installed exiftool onto my desktop. After I drop a picture into the program the exif data shows up but it closes after I press a key. How do I go into the command to change the camera model name?

[Phil Harvey]

Sorry for the late response, I missed this post somehow.

I installed exiftool onto my desktop. After I drop a picture into the program the exif data shows up but it closes after I press a key. How do I go into the command to change the camera model name?

If you rename the program to "exiftool(-k).exe" it will pause before quitting.  (This is the function of the -k option).  To change the camera model name, it is best to run from the command line.  Install exiftool for command-line use (see the install instructions) then open a cmd window (choose "Run..." from the Startup menu, then type "cmd" and press OK).  At this point you can start typing the commands indicated in this thread.

- Phil

[foosion]

In case you haven't seen it, Adobe now has release candidates for LR and PS CS5 that will process S95 raw files. Final versions are expected in a few weeks.

http://labs.adobe.com/downloads/lightroom3-3.html
http://labs.adobe.com/technologies/cameraraw6-3/

[littlespaceman]

Hi Phil

I'm trying todo a similar thing with a Canon G12, and fooling Lightroom 2 in to thinking it is a G11 so it will import CR2 files for editing.

I'm using OS X 10.6.6 and I'm new to using Terminal - so I'm opening Terminal and typing 'Exiftool' to open Exiftool. I'm then selecting the 'New Command' menu option and typing this in

exiftool -model="Canon PowerShot G11" -canonmodelID="PowerShot G11" Desktop/IMG_0396.CR2

(The image file is on my desktop, and is called IMG_0396.CR2)

When I press 'Run' I get this message

Warning: Can't convert Canon:CanonModelID (not in PrintConv)
Error: File not found - PowerShot
Error: File not found - G11"
Error: File not found - G11"
   1 image files updated
   3 files weren't updated due to errors

[Process completed]

Any ideas please?? Many thanks

[BogdanH]

Hi,

I don't know OS X, but maybe you should use single quotes instead of doublequote...? As far I recall, doublequotes should be used on Windows (only).
Just an idea 

Bogdan

[littlespaceman]

Thanks for the idea

The command line was cut and pasted directly from Phils suggested command line at the beginning of this thread though, the "'s were in his original. All I did was replace the words 'Canon Powershot S90' in his line with 'Canon Powershot G11'...

[Phil Harvey]

You have to be careful cutting and pasting because often web pages and documentation translate ASCII characters to other UTF-8 equivalents.

Type the command using either a standard single or double quote and it should work.

- Phil

[littlespaceman]

Thanks Phil - I'll give that a try.
Couple of questions for you -

1) Does the spaces in the command line matter - on the examples you've put up (eg: exiftool -model="Canon PowerShot S90" -canonmodelID="PowerShot S90" FILE) there appear to be spaces between some of the words and not others.

2) Do I enter the camera I want it to change TO (i.e the G11) or the camera I want it to change FROM (i.e the G12)? Do I have to enter a specific title for the camera name - eg Canon Powershot G**?

Thanks again

[littlespaceman]

Hi Phil

No luck I'm afraid

I typed manually this line - exiftool -ext cr2 -model='Canon Powershot G11' -canonmodelID='Powershot G11'/Users/Olly/Desktop/IMG_0396.CR2

(I dragged the file in to the command line to automatically get the /Users/Olly/Desktop/IMG_0396.CR2 part)

and it came up with the message


Warning: Can't convert Canon:CanonModelID (not in PrintConv)
Error: File not found - Powershot
Error: File not found - G11"
Error: File not found - G11"
Error: File not found - /Desktop/IMG_0396.CR2
    0 image files updated
    4 files weren't updated due to errors

[Process completed]

Any ideas at all please?

[Phil Harvey]

Your command works fine for me on OS X 10.6.6 after I add a space before the file name (even with cutting and pasting).

But re-reading your original post, I don't understand what you are doing.

Just do this:

1) Open the Terminal application.

2) In the window that appears, type:

exiftool -ext cr2 -model='Canon Powershot G11' -canonmodelID='Powershot G11' /Users/Olly/Desktop/IMG_0396.CR2

This should work.

- Phil

(Note that the -ext cr2 is redundant in this case because the command specifies only a single .CR2 file.)