[BUG]Canon camera not supported

[guitch]

Hi!

I'm trying to load CR2 files from my EOS Kiss F (Japanese name of the EOS 1000D) but ASP fails to read them with the following error on the console:
parseMaker failed for "/home/user/Documents/IMG_3392.CR2" in CR2Reader
Loading EXIF failed

I'm using:
ASP Version 1.0.1.10
OS: Ubuntu Linux 64bits (also tested on Windows, still doesn't work)
test file: http://dl.dropbox.com/u/43549636/IMG_3392.CR2

FYI, the raw file loads fine with Lightroom, darktable and gimp (UFRaw plugin), and since ASP doesn't seem to support converted DNG files either, I can only work on JPEG files right now.

[ogrizzo]

Hi!

I'm trying to load CR2 files from my EOS Kiss F (Japanese name of the EOS 1000D) but ASP fails to read them with the following error on the console:
parseMaker failed for "/home/user/Documents/IMG_3392.CR2" in CR2Reader
Loading EXIF failed

I'm using:
ASP Version 1.0.1.10
OS: Ubuntu Linux 64bits (also tested on Windows, still doesn't work)
test file: http://dl.dropbox.com/u/43549636/IMG_3392.CR2

FYI, the raw file loads fine with Lightroom, darktable and gimp (UFRaw plugin), and since ASP doesn't seem to support converted DNG files either, I can only work on JPEG files right now.

ASP doesn't know that a Kiss F is a 1000D: if you change the exif tag the image will be loaded correctly:

Code: Select all

exiftool -Model="Canon EOS 1000D" IMG_3392.CR2

Of course, always backup your raw file if you are going to modify them in any way, and please submit a bug report.

Ottavio

[afx]

Brain dead Canon...

Upload some sample test files at http://aftershotpro.com/AfterShotUploader/ with an explanation so
that they can recognize it in the next update.

cheers
afx

[MTF]

Brain dead Canon...

Gotta hear an explanation ... if you will ... of what the intent/meaning is behind that statement and how it pertains to the problem as discussed.

afx please .... one must be meticulous in their choice of words ..... as one never knows when a credulist is looking on.

You wouldn't by any chance be a Nikan user?

Regards

Mike

[afx]

Gotta hear an explanation ... if you will ... of what the intent/meaning is behind that statement and how it pertains to the problem as discussed.

Using different names for one and the same camera for marketing purposes is already stupid, but then messing up EXIF is definitely a sign of deficient mental capabilities. It just creates trouble for no good reason as you already could notice.

This is not the first time this has happened. And Canon is not the only manufacturer who messed that up...

cheers
afx

[MTF]

Using different names for one and the same camera for marketing purposes is already stupid.

This is a marketing ploy that has been utilized (successfully I might add) for eons ...... cameras, automobiles, soft drinks, confectionery ..... it is far from "stupid" and has advanced the sales of many products and/or extended the shelf life of existing ones ....... A particularly popular "name" in the Americas could be considered taboo in the middles east ..... as just one quick example.

but then messing up EXIF is definitely a sign of deficient mental capabilities. It just creates trouble for no good reason as you already could notice.

Having the exif information matching the model name on the camera is absolutely correct.

What would your reaction be if someone informed you ... their exif didn't match the model ID on their Canon camera?? ... or if a problem was created or exacerbated by mismatched exif - model ID's .. The resulting hew and cry would be deafening.

I fully realize Canon is not the only camera manufacturer to do this ... Nikan also utilizes this stratagem amongst many others.

The point is .... this needed to be brought to Corel's attention .... (It has been) and corrected (It should be ... one hopes) no mud slinging required ..... there never seems to be a shortage of mud around.

Regards

Mike

[maggus]

Having the exif information matching the model name on the camera is absolutely correct.

Hi,

agree, but the main problem is that one assumes the "name" of the cam to be an indicator for the format of the file !
Depending on firmware version within the cam I could imagine that raw format could change for whatever reason, but the cameras name would still be the same .... there should just be a separate EXIF field with some ID or info about the raw format within this file ... that´s it.
Of course this should be really unique, at least within one brand. But a real company should be able to manage this.

cheers
Markus

[afx]

This is a marketing ploy that has been utilized (successfully I might add) for eons ......

Depends on what you call success. Definitely not a success for the users.
I consider it an utter failure, just like region codes on DVDs or Corels insistance to use different Web pages based on the IP address a user is coming from.
This is a global world, time to get rid of the silly little fiefdoms.

Having the exif information matching the model name on the camera is absolutely correct.

What would your reaction be if someone informed you ... their exif didn't match the model ID on their Canon camera?? ... or if a problem was created or exacerbated by mismatched exif - model ID's .. The resulting hew and cry would be deafening.

Model ID and Marketing names do not need to match. They are two different items.
Most people don't ever look close at their exif model id anyway unless they run into messups created by using different model ids for one and the same cam.


cheers
afx

[ogrizzo]

Of course this should be really unique, at least within one brand. But a real company should be able to manage this.

cheers
Markus

Actually it is so: the CanonModelID tag is unique for the different names:

Code: Select all

pc2109:AfterShot Pro otto$ exiftool -s ~/Pictures/ORIG/ORIG-002/Zoo/100410-Zoo-71.cr2|grep Model
Model                           : Canon EOS 450D
CanonModelID                    : EOS Digital Rebel XSi / 450D / Kiss X2

Ottavio

[maggus]

Of course this should be really unique, at least within one brand. But a real company should be able to manage this.

cheers
Markus

Actually it is so: the CanonModelID tag is unique for the different names:

Code: Select all

pc2109:AfterShot Pro otto$ exiftool -s ~/Pictures/ORIG/ORIG-002/Zoo/100410-Zoo-71.cr2|grep Model
Model                           : Canon EOS 450D
CanonModelID                    : EOS Digital Rebel XSi / 450D / Kiss X2

Ottavio

thanx for the info (never searched for it ).
So when I get you right the "Model" changes depending on country, etc. but the "CanonModelID" is the same as long as it´s the same type of camera.
So Corel could focus on the CanonModelID ... if it´s available also in all the old EOS models.
Or simply keep the list of "Model"s up to date.

[KeithR]

This is not the first time this has happened. And Canon is not the only manufacturer who messed that up...

And yet it's only ASP that has a problem with it.

[KeithR]

Nope, I'm not going to play silly games so that you can change the subject, Gerard.

Yes, I know everything has faults, but as long as they're defended, excused, dismissed or ignored, they don't get fixed.

[grubernd]

And yet it's only ASP that has a problem with it.

(..) excused, dismissed or ignored, they don't get fixed.

neither do they get fixed from adding snarly, unconstructive comments with the constant sub-text that everything is better everywhere except in corel aftershot land, something you seem to imply and put into peoples mouths. so please stop the negativity and do something constructive. calibrate a lens or two. write a good howto. present some clever presets. or even a workaround for a problem you found and then feeding the monkey a precise, reproducable description of that problem. believe me, no one will want to talk about your car then.

[Gerard2]

Ha ha, Keith I can appreciate that. I was going to make a remark that you must be very active on a different car forum. I am sure the analogy will be crooked because you own ASP as well.

But I am with Grubernd on this one : whenever you post it is a negative one (although I could find a positive twist in one. On the bibble forum, you have announced for a year or more that you had enough. If you dont like a product, there is the option to stop using it. Nobody forced you to continue to ASP. So it just seems that you are on some personal beef against bibble/ASP. Maybe I am wrong, maybe you just would like ASP to become a better product but you have your own way ?

[Jeff Stephens]

The issue of not loading images from the Japanese version of this camera has been fixed in our internal development code. This will be added in our next update.