libexif-devel — This is the place where your questions about libexif will be answered.

[Libexif-devel] Re: exif configure.in,1.18,1.19

[Arnaud L. <as...@la...>]

Le Sun, Nov 17, 2002 at 04:47:23PM +0100, Hans Ulrich Niedermann a écrit:
> > I deeply prefer this way than the other. What about you, people ?
> The --with-xyz is the only way to make something optional.

Ok. Thought there would be some way for pkg-thing to support
optional dep, but it seems not...

	Arnaud.

Re: [Libexif-devel] Re: exif configure.in,1.18,1.19

[Hans U. N. <gp...@n-...>]

Arnaud Launay <as...@la...> writes:

> Le Sat, Nov 16, 2002 at 07:33:00PM -0800, rw...@us... a=
 =E9crit:
> > Removed my erroneous change (Lutz had already done it in a better way).
> > -PKG_CHECK_MODULES(LIBMNOTE, libmnote >=3D 0.5.4)
> > -AC_SUBST(LIBMNOTE_LIBS)
> > -AC_SUBST(LIBMNOTE_CFLAGS)
>=20
> I deeply prefer this way than the other. What about you, people ?

The --with-xyz is the only way to make something optional.

Gru=DF,

Uli

[Libexif-devel] Re: exif configure.in,1.18,1.19

[Arnaud L. <as...@la...>]

Le Sat, Nov 16, 2002 at 07:33:00PM -0800, rw...@us... a écrit:
> Removed my erroneous change (Lutz had already done it in a better way).
> -PKG_CHECK_MODULES(LIBMNOTE, libmnote >= 0.5.4)
> -AC_SUBST(LIBMNOTE_LIBS)
> -AC_SUBST(LIBMNOTE_CFLAGS)

I deeply prefer this way than the other. What about you, people ?

	Arnaud.

[Libexif-devel] libmnote (Exif MakerNote support alongside libexif)

[Rod W. <lis...@rw...>]

I wouldn't consider libmnote to be stable enough for a release just yet.  I
have only done some preliminary testing on Pentax images - it needs to be
tested on lots more different maker images.  The library is *very* heavily
based on the work that Lutz had done in exif-note - I consider it a
derivative work rather than a new authorship (and therefore left the
Copyright in his name for courtesy reasons).

-- Rod Whitby


----- Original Message -----
From: <lu...@ba...>
To: <lib...@li...>
Sent: Saturday, November 16, 2002 7:53 AM
Subject: Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23
configure.in,1.15,1.16


> Ahem. What the heck is mnote?

A library for parsing, viewing and editing the EXIF tag "MakerNote". Now
in CVS (module) libmnote. I haven't tested it yet as I just checked in
what I got from Rod Whitby (the library has been written by him, though he
put my name in every file).

I'll change the configure.in script to detect libmnote if available.

Lutz





-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Libexif-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libexif-devel

[Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[Arnaud L. <as...@la...>]

Le Fri, Nov 15, 2002 at 11:13:45PM +0100, Hans Ulrich Niedermann a écrit:
> One more point:
> - Arnaud knows gphoto-meta well enough to let it build libmnote for
>   himself if he wants it to
> :-)

Gna. Resolved my bug for building the libgphoto2_port in
libgphoto2, by using gmake instead of make. Wonder if I need to
add gnu-make to the package to build, though.

I hate that, automake builds b0rken Makefile. Grrrrrrr.

As soon as the release will be out, I'd like libgphoto2_port to
be taken out libgphoto2, and exist as a separate module.

(fu2 gp-dev)
	Arnaud.

Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[Hans U. N. <gp...@n-...>]

<lu...@ba...> writes:

> > Le Fri, Nov 15, 2002 at 10:23:39PM +0100, lu...@ba... a =E9crit:
> > Hmmm. Can't we add libmnote functionality directly into libexif,
> > instead of using it ? From what I see in the source, this
> > shouldn't be *that* difficult, and does not add so much "crap" to
> > the library.
>=20
> Sure you can. But there is absolutely no need for it.
>  - libgphoto2 doesn't need libmnote at all.
>  - libexif is based on a spec, libmnote tries to catch up with
>    numerous different undocumented MakerNote-formats.
>  - libexif is all about tags. libmnote is all about one tag.
>  - I prefer smaller libraries, one library for each task.
>  - There is no need for putting them together.

One more point:

- Arnaud knows gphoto-meta well enough to let it build libmnote for
  himself if he wants it to

:-)

Gru=DF,

Uli

Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[<lu...@ba...>]

> A library for parsing, viewing and editing the EXIF tag "MakerNote". Now
> in CVS (module) libmnote. I haven't tested it yet as I just checked in
> what I got from Rod Whitby (the library has been written by him, though
> he put my name in every file).

I added libmnote/test. As I haven't looked at the hp code yet, I am not
surprised that the test fails for the images of my camera.

But feeding an image taken by an Olympus camera results in some output. I
guess Pentax should work even better.

Lutz

Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[<lu...@ba...>]

> Le Fri, Nov 15, 2002 at 10:23:39PM +0100, lu...@ba... a écrit:
> Hmmm. Can't we add libmnote functionality directly into libexif,
> instead of using it ? From what I see in the source, this
> shouldn't be *that* difficult, and does not add so much "crap" to
> the library.

Sure you can. But there is absolutely no need for it.
 - libgphoto2 doesn't need libmnote at all.
 - libexif is based on a spec, libmnote tries to catch up with
   numerous different undocumented MakerNote-formats.
 - libexif is all about tags. libmnote is all about one tag.
 - I prefer smaller libraries, one library for each task.
 - There is no need for putting them together.

Lutz

[Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[Arnaud L. <as...@la...>]

Le Fri, Nov 15, 2002 at 10:23:39PM +0100, lu...@ba... a écrit:
> > Ahem. What the heck is mnote?
> A library for parsing, viewing and editing the EXIF tag
> "MakerNote". Now in CVS (module) libmnote. I haven't tested it
> yet as I just checked in what I got from Rod Whitby (the
> library has been written by him, though he put my name in every file).
> I'll change the configure.in script to detect libmnote if available.

Hmmm. Can't we add libmnote functionality directly into libexif,
instead of using it ? From what I see in the source, this
shouldn't be *that* difficult, and does not add so much "crap" to
the library.

	Arnaud.

Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[<lu...@ba...>]

> Ahem. What the heck is mnote?

A library for parsing, viewing and editing the EXIF tag "MakerNote". Now
in CVS (module) libmnote. I haven't tested it yet as I just checked in
what I got from Rod Whitby (the library has been written by him, though he
put my name in every file).

I'll change the configure.in script to detect libmnote if available.

Lutz

Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[Hans U. N. <gp...@n-...>]

<lu...@ba...> writes:

> > Le Fri, Nov 15, 2002 at 11:59:55AM -0800, lu...@us... a
> > =E9crit:
> >> 2002-11-15  Lutz M=FCller <lu...@us...>
> >> 	* configure.in: Make exif depend on libmnote. This library isn't used
> >> 	  yet, but that's subject to change.
> >> +PKG_CHECK_MODULES(LIBEXIF, libexif >=3D 0.5.4 libmnote)

Ahem. What the heck is mnote?

It is not among the 11000+ packages available in Debian unstable. So I
think some kind of link to libmnote should be added.

> > Are you sure it's a good idea, at 15 days of a release ?
>=20
> exif will be released, too? I didn't know that. If yes, you are right. But
> why releasing exif together with gphoto2? libexif yes, but exif is a
> totally separate program.

We can always release an older exif version if needed :-)

Gru=DF,

Uli

[Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[Arnaud L. <as...@la...>]

Le Fri, Nov 15, 2002 at 09:31:01PM +0100, lu...@ba... a écrit:
> > Are you sure it's a good idea, at 15 days of a release ?
> exif will be released, too? I didn't know that. If yes, you are
> right. But why releasing exif together with gphoto2? libexif
> yes, but exif is a totally separate program.

I believe Hans would release everything at the same time, not
sure about his plans.

BTW, what is libmnote ?

	Arnaud.

Re: [Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[<lu...@ba...>]

> Le Fri, Nov 15, 2002 at 11:59:55AM -0800, lu...@us... a
> écrit:
>> 2002-11-15  Lutz Müller <lu...@us...>
>> 	* configure.in: Make exif depend on libmnote. This library isn't used
>> 	  yet, but that's subject to change.
>> +PKG_CHECK_MODULES(LIBEXIF, libexif >= 0.5.4 libmnote)
>
> Are you sure it's a good idea, at 15 days of a release ?

exif will be released, too? I didn't know that. If yes, you are right. But
why releasing exif together with gphoto2? libexif yes, but exif is a
totally separate program.

Lutz

[Libexif-devel] Re: exif ChangeLog,1.22,1.23 configure.in,1.15,1.16

[Arnaud L. <as...@la...>]

Le Fri, Nov 15, 2002 at 11:59:55AM -0800, lu...@us... a écrit:
> 2002-11-15  Lutz Müller <lu...@us...>
> 	* configure.in: Make exif depend on libmnote. This library isn't used
> 	  yet, but that's subject to change.
> +PKG_CHECK_MODULES(LIBEXIF, libexif >= 0.5.4 libmnote)

Are you sure it's a good idea, at 15 days of a release ?

	Arnaud.

Re: [Libexif-devel] MakerNote support

[Lutz <lu...@us...>]

On Tue, 2002-11-12 at 05:06, Rod Whitby wrote:
> Let me know if you'd like to see the code (either a tarball or diffs).

cvs diff -u3 -p?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] MakerNote support

[Rod W. <lis...@rw...>]

On Fri, 2002-11-08 at 09:04, Lutz M=FCller wrote:
> You can always
> set up new objects like exif-mn-[entry,content,tag] (mn =3D MakerNote)
> inheriting from the exif-equivalents.
> (Me looking at the source...)
> I think I have already done something like that in
> libexif/libexif/olympus. Could you give me your opinion on that?

I've used what you've provided in libexif/libexif/olympus, and made the
following changes:

1/ Added a "note" field to ExifData to store an ExifNote (looks like an
ExifContent), which is a set of ExifNoteEntry (looks like an ExifEntry). =
The
new data structures are in exif-note.c and in the maker-specific
directories.

2/ Added code to exif_data_load_data_entry and exif_data_save_data_entry =
to
load and save the MakerNote entry to and from the "note" field in ExifDat=
a.
Added code to allow dumping of the makernote (so a test-tree run will dum=
p
out the individual makernote entries).

3/ Added lots of new methods in ExifNote to handle accessing individual
ExifNoteEntry entries.

My big question going forward is to do with the exif/exif/main.c file and
how these new individually named things (ExifNoteEntry, accessed via the
ExifNoteTag) should be identified by the user.  The options are the re-us=
e
the -tag switch, and just have a new -ifd option for the MakerNote (but I
know that you're not keen on this option), or to add a new set of switche=
s
(-note, -list_notes) for handling MakerNote entries separately.

Let me know if you'd like to see the code (either a tarball or diffs).

-- Rod Whitby

Re: [Libexif-devel] MakerNote support

[Rod W. <lis...@rw...>]

I agree with your points in the previous message about not re-using the I=
FD
structure for MakerNotes.

I'd like to have a common MakerNote data structure format (like what you =
had
in the previous message), and then have each maker-specific piece of code
conform to that format (even if they have to create dummy tags).  Then th=
e
top-level code can operate on makernotes without having to care what
specific maker it came from.

The code in .../olympus/... has data structures with "Olympus" in the nam=
es
of the data structures (and similarly for each of the other maker modules=
).
I want to have a common makernote data structure which each of the
maker-specific modules use (and do whatever is required to insert the
makernote information into the common data structure.  The common code wo=
uld
have pretty much an identical interface to all the other ExifContent stuf=
f,
so it can be loaded, modified and saved just like anything else.

I'll sort out what I mean in the code, and then send an example.

-- Rod Whitby


----- Original Message -----
From: "Lutz M=FCller" <lu...@us...>
To: <lib...@li...>
Sent: Friday, November 08, 2002 6:57 PM
Subject: Re: [Libexif-devel] MakerNote support


On Fri, 2002-11-08 at 09:04, Lutz M=FCller wrote:
> You can always
> set up new objects like exif-mn-[entry,content,tag] (mn =3D MakerNote)
> inheriting from the exif-equivalents.

(Me looking at the source...)

I think I have already done something like that in
libexif/libexif/olympus. Could you give me your opinion on that?

Lutz
--
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Libexif-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libexif-devel

Re: [Libexif-devel] MakerNote support

[Lutz <lu...@us...>]

On Fri, 2002-11-08 at 09:04, Lutz M=FCller wrote:
> You can always
> set up new objects like exif-mn-[entry,content,tag] (mn =3D MakerNote)
> inheriting from the exif-equivalents.

(Me looking at the source...)

I think I have already done something like that in
libexif/libexif/olympus. Could you give me your opinion on that?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

Re: [Libexif-devel] MakerNote support

[Lutz <lu...@us...>]

On Fri, 2002-11-08 at 07:25, Rod Whitby wrote:
> It seems that the MakerNote fields for the currently supported cameras
> (Canon, Olympus, and now Pentax) follow a pseudo-IFD structure, and I'm
> wondering if it would be useful to just add another entry into the IFD en=
um
> (EXIF_IFD_MAKER_NOTE), and then just re-use the existing exif_data_load_.=
..
> routines to load in the data (after any maker-specific prefix has been
> skipped over).

The problem is that most maker notes follow a _pseudo_-IFD structure.
That is, some screw up with the byte order, others with the offset,
others somewhere else... The code in exif-data will get unreadable.

Please keep libexif as close as possible to the standard. You can always
set up new objects like exif-mn-[entry,content,tag] (mn =3D MakerNote)
inheriting from the exif-equivalents.

For example, introduce=20

typedef struct _ExifMNContent ExifMNContent;
struct _ExifMNContent {
	ExifContent parent;

	/* Insert here whatever you like */
};

etc. and=20


and use this object like an ExifContent:

ExifMNContent *mn_content;
ExifMNEntry   *mn_entry;

ExifMNContent *
exif_mn_content_new (void) {
	ExifMNContent *mn_content;

	mn_content =3D malloc (sizeof (ExifMNContent));

	exif_content_init ((ExifContent *) mn_content);
}

void
exif_mn_content_some_function (ExifMNContent *mn_content) {

	ExifMNEntry *mn_entry;

        (...)
	exif_content_add_entry ((ExifContent *) mn_content,
                                (ExifEntry *) mn_entry));
}

> The only thing which needs to be handled specially is that
> the tags in the makernote are in a different namespace from the normal IF=
D

This is the case _now_. I wouldn't rely on manufacturers sticking to
that convention, as it isn't fixed in the spec.

> tags.  It would also mean that the existing interface for editing tags in
> the exif program can be re-used (you just specify a different IFD for
> makernote tags).

See above. I think keeping the MakerNote stuff separate leads to code
that is easier to maintain.

What do you think?

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

[Libexif-devel] MakerNote support

[Rod W. <lis...@rw...>]

[The weird email address is a spam-prevention measure.  It will reach me
until I start to get spam on that address (and I will know that the spamm=
er
somehow got the address from this list), at which time it will be bounced
and I will start to use a new address.  You can also contact me via
sourceforge.]

Lutz M=FCller wrote:
> If you think the framework that is in CVS is useful, you could code for
>  example along libexif/olympus. But if you have other ideas on how to
>  handle MakerNotes, please tell them.

I'm going to add MakerNote support to libexif for the Pentax Optio
230/330/430 range of cameras (I have a 330 myself).  My goal is to allow
makernote entries to be edited just like any other tag and then saved bac=
k
to a new file.

It seems that the MakerNote fields for the currently supported cameras
(Canon, Olympus, and now Pentax) follow a pseudo-IFD structure, and I'm
wondering if it would be useful to just add another entry into the IFD en=
um
(EXIF_IFD_MAKER_NOTE), and then just re-use the existing exif_data_load_.=
..
routines to load in the data (after any maker-specific prefix has been
skipped over).  The only thing which needs to be handled specially is tha=
t
the tags in the makernote are in a different namespace from the normal IF=
D
tags.  It would also mean that the existing interface for editing tags in
the exif program can be re-used (you just specify a different IFD for
makernote tags).

Does this sound like a reasonable idea ?  I'm happy to write the code (an=
d
have actually started already) ...

-- Rod Whitby

[Libexif-devel] Re: exif tag modification problem

[Arnaud L. <as...@la...>]

Le Wed, Oct 30, 2002 at 05:55:48PM -0500, Kirk Bauer a écrit:
> $ ./exif --tag='Model' test.jpg 
> Segmentation fault

May you send us a link to test.jpg, please ?

	Arnaud.

[Libexif-devel] exif tag modification problem

[Kirk B. <ki...@ka...>]

I am trying to modify an EXIF tag and I receive a few segfaults when
(presumably) not doing the correct thing:

$ ./exif --tag='Model' test.jpg 
Segmentation fault

$ ./exif --tag='Model' --set-value='testing' test.jpg 
Segmentation fault

But when I finally do (what I think is) the correct thing, I get this:

$ ./exif --ifd=0 --tag='Model' --set-value='testing' test.jpg 
Internal error. Please contact <lib...@li...>.

Any help would be appreciated.  I am using exif version 0.5 with libexif
0.5.6.

-- 
 Kirk Bauer -- CmpE, Georgia Tech -- ki...@ka... -- Avid Linux User
     http://linux.kaybee.org | www.autorpm.org | www.logwatch.org
    Opinions expressed are my own, but they should be everybody's.

Re: [Libexif-devel] TIFF supports, MakerNotes and others

[Lutz <lu...@us...>]

On Mon, 2002-10-28 at 05:46, German Poo Caaman~o wrote:
> I don't understand, why TIFF support don't belong to this
> list.

I have never said that it doesn't belong to this list. It is just that
nobody has come up with a patch to libexif (yet) to add support for TIFF
files.

> Well, this link also show differents MakerNotes, and formats
> for JPEG and TIFF data.

I ran out of ideas on how to represent all those MakerNotes in a common
structure. Patches welcome.

> At last, but not least, metacam[1] allow me to get the EXIF
> information from TIFF and JPEG files.  However, I'd miss
> some features from exif.  Are there any plans to join
> both efforts?

Please understand the different history: There are lots of standalone
programs to read EXIF information. There are lots of c++ libraries. But
there hasn't been a single c library. That is why libexif has been
written. exif is just a proof-of-concept that libexif works. If other
utilities would like to use libexif, they are very welcome.

Lutz
--=20
+----------------------------------------------+
| Lutz M=FCller                 +49 (7156) 34837 |
|                                              |
| Hans-Sachs-Strasse 5                         |
| 71254 Ditzingen       http://www.topfrose.de |
| Germany           lu...@us... |
+----------------------------------------------+

[Libexif-devel] TIFF supports, MakerNotes and others

[German P. Caaman~o <gp...@ub...>]

Hello,

I'm new here, but I read latest posts on this list.

exif works fine for me with JPEG, and I made some
basic scripts that allow me rotate a picture with
its thumbnail rotated, all thanks to exif :-)

However, I can't do it the same with TIFF files :-(
Or at least, retrieve EXIF information.

I don't understand, why TIFF support don't belong to this
list.  According to 
http://www.ba.wakwak.com/~tsuruzoh/Computer/Digicams/exif-e.html
basically EXIF uses TIFF format to store data.  So, why
libtiff?

Well, this link also show differents MakerNotes, and formats
for JPEG and TIFF data.

At last, but not least, metacam[1] allow me to get the EXIF
information from TIFF and JPEG files.  However, I'd miss
some features from exif.  Are there any plans to join
both efforts?

[1]: http://www.cheeseplant.org/~daniel/pages/metacam.html

Best regards,

-- 
German Poo Caaman~o
mailto:gp...@ub...
http://www.ubiobio.cl/~gpoo/chilelindo.html

RE: [Libexif-devel] libexif and TIFF files

[Duane H. H. <dh...@an...>]

On 29-Sep-02 Jason Van Patten wrote:
> Greetings folks -
> 
> Lutz pointed me at this mailling list after I asked him about TIFF support. 
> I see there have been a number of discussions on it during the summer
> months, but haven't seen anything recent.  Has anyone done any work on it? 
> Any guinea pigs needed? :-)
> 
> I have a camera (D1x) that produces TIFF files.  It does look like there's
> some sort of interesting data stored in the file.  Dunno if it's
> technically EXIF or not?  In any event, I'll be happy to test code, etc, if
> anyone needs any help.
> 
> My ultimate goal would be to have an EXIF patch for the TIFF plug-in
> in GIMP, similar to the one Lutz wrote for the JPEG plug-in.  I'd like to be
> able to open TIFFs in GIMP, edit them, and then save them back as JPEGs with
> the appropriate information stored.
> 
> Thanks!
> 
> jas
> -- 
> Jason Van Patten
> AOL IM: Jason VP 
> 

I have some modifications to 'libtiff" which might be of interest to you.
Since this is a 'libexif" list, it would be inappropriate to discuss them
here.  Contact me at the address below if you are interested.
--------------
Duane H. Hesser
dh...@an...