ufraw-0.4-2.i386.rpm
This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
ufraw-0.4-2.i386.rpm | Orlando Figueiredo | 13 Oct 22:54 |
ufraw-0.4-2.i386.rpm | Rikard Johnels | 13 Oct 23:08 |
ufraw-0.4-2.i386.rpm | Orlando Figueiredo | 13 Oct 23:44 |
ufraw-0.4-2.i386.rpm | Nir Dremer | 14 Oct 00:07 |
ufraw-0.4-2.i386.rpm | Orlando Figueiredo | 14 Oct 00:24 |
ufraw-0.4-2.i386.rpm | Carol Spears | 14 Oct 03:40 |
ufraw-0.4-2.i386.rpm
Hello everybody
A few days ago I put here a a message about the instalation of dcraw. I did the instalation of the package referred on subject and everything went OK. After the instalation the Gimp open window included the the option for raw files. The problem is that when I try to open my EOS350D raw files (*.cr2 - that is included in the file extensions listed in ufraw) I get a message saying that EOS350D is not available yet. I found a at rpm.pbone.net newer releases of the package but for Fedora 4 the one mentioned on subject is the newer. I wonder if anybody here worked with raw files from that machine and how did it work? Or if anybody has any ideas to sove the problem.
Thanks a lot.
Orlando
ufraw-0.4-2.i386.rpm
On Thursday 13 October 2005 22.54, Orlando Figueiredo wrote:
Hello everybody
A few days ago I put here a a message about the instalation of dcraw. I did the instalation of the package referred on subject and everything went OK. After the instalation the Gimp open window included the the option for raw files. The problem is that when I try to open my EOS350D raw files (*.cr2 - that is included in the file extensions listed in ufraw) I get a message saying that EOS350D is not available yet. I found a at rpm.pbone.net newer releases of the package but for Fedora 4 the one mentioned on subject is the newer. I wonder if anybody here worked with raw files from that machine and how did it work? Or if anybody has any ideas to sove the problem.
Thanks a lot.
Orlando
_______________________________________________ Gimp-user mailing list
Gimp-user@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
I myself havent got a 350D but i did a grep on the ufraw source.
~/Build/ufraw-0.5> grep EOS *
Binary file dcraw matches
dcraw.c: fseek (ifp, strstr(model,"EOS-1D") ? 68:50, SEEK_CUR);
dcraw.c: if (((!strcmp(model,"Canon EOS DIGITAL REBEL") ||
dcraw.c: !strcmp(model,"Canon EOS 300D DIGITAL"))) && wbi == 6)
dcraw.c: if (!strcmp(model,"Canon EOS D30")) {
dcraw.c: if (!strcmp(model,"Canon EOS 10D"))
dcraw.c: if (wbi == 0 && !strcmp(model,"Canon EOS D30"))
dcraw.c: { "Canon EOS D2000",
dcraw.c: { "Canon EOS D6000",
dcraw.c: { "Canon EOS D30",
dcraw.c: { "Canon EOS D60",
dcraw.c: { "Canon EOS 10D",
dcraw.c: { "Canon EOS 20D",
dcraw.c: { "Canon EOS-1Ds Mark II",
dcraw.c: { "Canon EOS-1D Mark II",
dcraw.c: { "Canon EOS-1DS",
dcraw.c: { "Canon EOS-1D",
dcraw.c: { "Canon EOS",
dcraw.c: { "KODAK EOSDCS1",
dcraw.c: { "KODAK EOSDCS3B",
dcraw.c: } else if (!strcmp(model,"EOS D2000C")) {
dcraw.c: } else if (!strcmp(model,"EOS-1D")) {
dcraw.c: } else if (!strcmp(model,"EOS-1DS")) {
dcraw.c: } else if (!strcmp(model,"EOSDCS3B")) {
dcraw.c: } else if (!strcmp(model,"EOSDCS1")) {
Binary file dcraw-dcraw.o matches
Binary file dcraw_nomain.o matches
Binary file ufraw matches
Binary file ufraw-batch matches
Binary file ufraw-gimp matches
So it seems the support is yet to be implemented.
I cant bet on this; but you MIGHT be able to hack the dcraw.c file and add "Canon EOS..." (exact syntax probably according to the EXIF header of a JPEG photo from the camera)
It may or may not work...
ufraw-0.4-2.i386.rpm
Thanks Rikard. I think that is too hack the file is a little bit too
much for my knowledge.
Anyway the strange thing is that if you go to David Cofin's web page
http://www.cybercom.net/~dcoffin/dcraw/ he has a list of cameras with
which dcraw is supposed to work and the Canon EOS350D is listed there.
Thanks for the help Orlando
Qui, 2005-10-13 às 23:08 +0200, Rikard Johnels escreveu:
On Thursday 13 October 2005 22.54, Orlando Figueiredo wrote:
Hello everybody
A few days ago I put here a a message about the instalation of dcraw. I did the instalation of the package referred on subject and everything went OK. After the instalation the Gimp open window included the the option for raw files. The problem is that when I try to open my EOS350D raw files (*.cr2 - that is included in the file extensions listed in ufraw) I get a message saying that EOS350D is not available yet. I found a at rpm.pbone.net newer releases of the package but for Fedora 4 the one mentioned on subject is the newer. I wonder if anybody here worked with raw files from that machine and how did it work? Or if anybody has any ideas to sove the problem.
Thanks a lot.
Orlando
ufraw-0.4-2.i386.rpm
I highly recommend checking the cvs version (which is the soon to be 0,6).
There are many changes there, and one of them might be this (though i didnt have time to check for you).
cheers
On Thu, 2005-10-13 at 22:44 +0100, Orlando Figueiredo wrote:
Thanks Rikard. I think that is too hack the file is a little bit too much for my knowledge.
Anyway the strange thing is that if you go to David Cofin's web page http://www.cybercom.net/~dcoffin/dcraw/ he has a list of cameras with which dcraw is supposed to work and the Canon EOS350D is listed there.Thanks for the help Orlando
Qui, 2005-10-13 às 23:08 +0200, Rikard Johnels escreveu:
On Thursday 13 October 2005 22.54, Orlando Figueiredo wrote:
Hello everybody
A few days ago I put here a a message about the instalation of dcraw. I did the instalation of the package referred on subject and everything went OK. After the instalation the Gimp open window included the the option for raw files. The problem is that when I try to open my EOS350D raw files (*.cr2 - that is included in the file extensions listed in ufraw) I get a message saying that EOS350D is not available yet. I found a at rpm.pbone.net newer releases of the package but for Fedora 4 the one mentioned on subject is the newer. I wonder if anybody here worked with raw files from that machine and how did it work? Or if anybody has any ideas to sove the problem.
Thanks a lot.
Orlando
ufraw-0.4-2.i386.rpm
Hi Nir
Can you be a little more specific how can I check the cvs version. You
know I am kind newbie to Linux and Gimp was one of the reasons to
change.
Thanks
Orlando
Sex, 2005-10-14 às 00:07 +0200, Nir Dremer escreveu:
I highly recommend checking the cvs version (which is the soon to be 0,6).
There are many changes there, and one of them might be this (though i didnt have time to check for you).
cheers
On Thu, 2005-10-13 at 22:44 +0100, Orlando Figueiredo wrote:
Thanks Rikard. I think that is too hack the file is a little bit too much for my knowledge.
Anyway the strange thing is that if you go to David Cofin's web page http://www.cybercom.net/~dcoffin/dcraw/ he has a list of cameras with which dcraw is supposed to work and the Canon EOS350D is listed there.Thanks for the help Orlando
Qui, 2005-10-13 às 23:08 +0200, Rikard Johnels escreveu:
On Thursday 13 October 2005 22.54, Orlando Figueiredo wrote:
Hello everybody
A few days ago I put here a a message about the instalation of dcraw. I did the instalation of the package referred on subject and everything went OK. After the instalation the Gimp open window included the the option for raw files. The problem is that when I try to open my EOS350D raw files (*.cr2 - that is included in the file extensions listed in ufraw) I get a message saying that EOS350D is not available yet. I found a at rpm.pbone.net newer releases of the package but for Fedora 4 the one mentioned on subject is the newer. I wonder if anybody here worked with raw files from that machine and how did it work? Or if anybody has any ideas to sove the problem.
Thanks a lot.
Orlando
ufraw-0.4-2.i386.rpm
On Thu, Oct 13, 2005 at 11:24:39PM +0100, Orlando Figueiredo wrote:
Can you be a little more specific how can I check the cvs version. You know I am kind newbie to Linux and Gimp was one of the reasons to change.
there are fairly good instructions about how to use cvs to get a
checkout on gimp.org:
http://www.gimp.org/source/howtos/stable-cvs-get.html
it should be relatively easy to take the gimp parts out and use the parts that would be relevant to a different repository.
even in this example, it is more complicated to get a specific version than it is to get the current developer version. for instance, from this how to: "cvs checkout -r gimp-2-2 gimp" should become: "cvs checkout gimp" if you are interested in todays version.
the cvsrc that was can be found there was written to be nice to the cvs server and to your own system.
i am rather proud of this document here. i had only a little to do with the writing of it. gimp has occasionally had some really excellent document writers.
carol