Exiv2 bug reports

[AndriusWild]

Gilles,

I keep submitting bugs to Exiv2 bugzilla but I am not sure they really want to investigate anything. I am feeling like their goal is to blame it on something else (e.g. on digiKam) and close the file as soon as possible. Or maybe exiv2 from the command line and exiv2 via API call are two completely different things.

I guess we are on our own here.

Sorry I could not help it.

[Gilles Caulier-4]

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[Simon Frei]

Which exiv2 revision is included in the appimage? He could genuinely not
reproduce the dysfunction with the provided example file in their most
recent revision, so maybe that was fixed in the meantime.

[AndriusWild]

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[Gilles Caulier-4]

AppImage use current implementation from svn/trunk of Exiv2. So typically the 0.26 not yet released, but 98% ready for production :

http://dev.exiv2.org/versions/52

Gilles Caulier

2017-03-10 22:29 GMT+01:00 Simon Frei <[hidden email]>:

Which exiv2 revision is included in the appimage? He could genuinely not
reproduce the dysfunction with the provided example file in their most
recent revision, so maybe that was fixed in the meantime.

[Gilles Caulier-4]

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[AndriusWild]

It was me who proposed to use bento4. I tried it and it worked well to import metadata from a text file as an atom to mp4.

I think treating images and videos the same way is why exiv2 isn't working. For example, images would store creation date as "Date created" while videos would have it as "Date Encoded". Just an example.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:52 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[Gilles Caulier-4]

This report is clear also :

https://bugs.kde.org/show_bug.cgi?id=376661

With video file, DK in unstable. There is no other solution to disable video metadata support as it's specified here :

https://bugs.kde.org/show_bug.cgi?id=375646

Gilles Caulier

2017-03-10 23:20 GMT+01:00 Andrey Goreev <[hidden email]>:

It was me who proposed to use bento4. I tried it and it worked well to import metadata from a text file as an atom to mp4.

I think treating images and videos the same way is why exiv2 isn't working. For example, images would store creation date as "Date created" while videos would have it as "Date Encoded". Just an example.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:52 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[AndriusWild]

Is there a way to add a launcher of external bash/python scripts to digiKam?

Right now I am working on a bash script that compresses video files using ffmpeg and moving metadata atoms from the original to the output using bento4 (apparently some metadata gets lost during conversion even though there is an option in ffmpeg to preserve it).

After that I want to write a script to read video file creation date (exiftool or mediainfo or both) and overwrite the wrong date that digiKam writes to XMP sidecar file.

Next step will be reading tags (keywords) and people tags from XMP sidecar files and write them to video files using exiftool probably (this one should be easy to accomplish).

Next step will be a script to read GPS location for video files from XMP sidecar and write it to video files using bento4.

If I could call each script right from the context menu in digiKam that would help a lot.

On 2017-03-10 03:36 PM, Gilles Caulier wrote:

This report is clear also :

https://bugs.kde.org/show_bug.cgi?id=376661

With video file, DK in unstable. There is no other solution to disable video metadata support as it's specified here :

https://bugs.kde.org/show_bug.cgi?id=375646

Gilles Caulier

2017-03-10 23:20 GMT+01:00 Andrey Goreev <[hidden email]>:

It was me who proposed to use bento4. I tried it and it worked well to import metadata from a text file as an atom to mp4.

I think treating images and videos the same way is why exiv2 isn't working. For example, images would store creation date as "Date created" while videos would have it as "Date Encoded". Just an example.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:52 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[Gilles Caulier-4]

In BQM, there is a tool to run external script for each file plug in a queue.

Gilles Caulier

2017-03-11 0:12 GMT+01:00 Andrey Goreev <[hidden email]>:

Is there a way to add a launcher of external bash/python scripts to digiKam?

Right now I am working on a bash script that compresses video files using ffmpeg and moving metadata atoms from the original to the output using bento4 (apparently some metadata gets lost during conversion even though there is an option in ffmpeg to preserve it).

After that I want to write a script to read video file creation date (exiftool or mediainfo or both) and overwrite the wrong date that digiKam writes to XMP sidecar file.

Next step will be reading tags (keywords) and people tags from XMP sidecar files and write them to video files using exiftool probably (this one should be easy to accomplish).

Next step will be a script to read GPS location for video files from XMP sidecar and write it to video files using bento4.

If I could call each script right from the context menu in digiKam that would help a lot.

On 2017-03-10 03:36 PM, Gilles Caulier wrote:

This report is clear also :

https://bugs.kde.org/show_bug.cgi?id=376661

With video file, DK in unstable. There is no other solution to disable video metadata support as it's specified here :

https://bugs.kde.org/show_bug.cgi?id=375646

Gilles Caulier

2017-03-10 23:20 GMT+01:00 Andrey Goreev <[hidden email]>:

It was me who proposed to use bento4. I tried it and it worked well to import metadata from a text file as an atom to mp4.

I think treating images and videos the same way is why exiv2 isn't working. For example, images would store creation date as "Date created" while videos would have it as "Date Encoded". Just an example.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:52 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[Gilles Caulier-4]

I dislike a lots this kind of message :

http://dev.exiv2.org/issues/1267#change-5904

Seriously... If a crash appears in Exiv2 implementation, we report as UPSTREAM. It's normal. And i'm sorry, but if a crash appear, it's because a bug is inside the code, especially if the backtrace is explicit...

Gilles Caulier

2017-03-11 7:08 GMT+01:00 Gilles Caulier <[hidden email]>:

In BQM, there is a tool to run external script for each file plug in a queue.

Gilles Caulier

2017-03-11 0:12 GMT+01:00 Andrey Goreev <[hidden email]>:

Is there a way to add a launcher of external bash/python scripts to digiKam?

Right now I am working on a bash script that compresses video files using ffmpeg and moving metadata atoms from the original to the output using bento4 (apparently some metadata gets lost during conversion even though there is an option in ffmpeg to preserve it).

After that I want to write a script to read video file creation date (exiftool or mediainfo or both) and overwrite the wrong date that digiKam writes to XMP sidecar file.

Next step will be reading tags (keywords) and people tags from XMP sidecar files and write them to video files using exiftool probably (this one should be easy to accomplish).

Next step will be a script to read GPS location for video files from XMP sidecar and write it to video files using bento4.

If I could call each script right from the context menu in digiKam that would help a lot.

On 2017-03-10 03:36 PM, Gilles Caulier wrote:

This report is clear also :

https://bugs.kde.org/show_bug.cgi?id=376661

With video file, DK in unstable. There is no other solution to disable video metadata support as it's specified here :

https://bugs.kde.org/show_bug.cgi?id=375646

Gilles Caulier

2017-03-10 23:20 GMT+01:00 Andrey Goreev <[hidden email]>:

It was me who proposed to use bento4. I tried it and it worked well to import metadata from a text file as an atom to mp4.

I think treating images and videos the same way is why exiv2 isn't working. For example, images would store creation date as "Date created" while videos would have it as "Date Encoded". Just an example.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:52 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

[Gilles Caulier-4]

What i can respond seriously :

http://dev.exiv2.org/issues/1280#note-4

Now, i'm a "mess" builder... better and better...

Gilles Caulier

2017-03-11 11:55 GMT+01:00 Gilles Caulier <[hidden email]>:

I dislike a lots this kind of message :

http://dev.exiv2.org/issues/1267#change-5904

Seriously... If a crash appears in Exiv2 implementation, we report as UPSTREAM. It's normal. And i'm sorry, but if a crash appear, it's because a bug is inside the code, especially if the backtrace is explicit...

Gilles Caulier

2017-03-11 7:08 GMT+01:00 Gilles Caulier <[hidden email]>:

In BQM, there is a tool to run external script for each file plug in a queue.

Gilles Caulier

2017-03-11 0:12 GMT+01:00 Andrey Goreev <[hidden email]>:

Is there a way to add a launcher of external bash/python scripts to digiKam?

Right now I am working on a bash script that compresses video files using ffmpeg and moving metadata atoms from the original to the output using bento4 (apparently some metadata gets lost during conversion even though there is an option in ffmpeg to preserve it).

After that I want to write a script to read video file creation date (exiftool or mediainfo or both) and overwrite the wrong date that digiKam writes to XMP sidecar file.

Next step will be reading tags (keywords) and people tags from XMP sidecar files and write them to video files using exiftool probably (this one should be easy to accomplish).

Next step will be a script to read GPS location for video files from XMP sidecar and write it to video files using bento4.

If I could call each script right from the context menu in digiKam that would help a lot.

On 2017-03-10 03:36 PM, Gilles Caulier wrote:

This report is clear also :

https://bugs.kde.org/show_bug.cgi?id=376661

With video file, DK in unstable. There is no other solution to disable video metadata support as it's specified here :

https://bugs.kde.org/show_bug.cgi?id=375646

Gilles Caulier

2017-03-10 23:20 GMT+01:00 Andrey Goreev <[hidden email]>:

It was me who proposed to use bento4. I tried it and it worked well to import metadata from a text file as an atom to mp4.

I think treating images and videos the same way is why exiv2 isn't working. For example, images would store creation date as "Date created" while videos would have it as "Date Encoded". Just an example.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:52 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

yes. The problem is that metadata abstraction use the same interface for image and video. It's homogeneous. If we want to use another frameworks for video only, this will increase the complexity of DK code, so the probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata with ffmpeg, but we don't receive a favorable response from QtAV team :

https://github.com/wang-bin/QtAV/issues/820

A digiKam user has proposed to use this tool :

https://www.bento4.com/

But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <[hidden email]>:

Would it be a big deal to switch to something else for video metadata support ?

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-10 2:26 PM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

Hi,

yes, i agree. this is not the first time that Exiv2 team drop as well the report. 

I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly designed. Technically the crash is in Exiv2 while parsing metadata. The architecture is the same in digiKam for image and video. We don't see any dysfunction about images. I use it everyday. For video support, Exiv2 has a not stabilized code yet. This is the problem.

The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....

Gilles

Le 11/03/2017 à 11:55, Gilles Caulier a écrit :
> I dislike a lots this kind of message :
>
> http://dev.exiv2.org/issues/1267#change-5904
>
> Seriously... If a crash appears in Exiv2 implementation, we report as
> UPSTREAM. It's normal. And i'm sorry, but if a crash appear, it's
> because a bug is inside the code, especially if the backtrace is explicit...
>

the man works too much and is easily upset. I very often notice such
reactions in open source world, where people works on free time after
the usual work and easily burn out :-(

I too have such reaction, but given my age and experience, I try not to
make others receive it :-)

https://www.youtube.com/watch?v=wugWGhItaQA

:-)
jdd

[Gilles Caulier-4]

I understand very well the burn out state.

But all peoples working in open source make the puzzle in same manner. We have a job and we work while the free time on extra projects. I'm working myself like this since... 2001 now, for digiKam...

I'm trying to have a safe life, with family, and with a real plan to dedicate working hours on this project.

More, i teach also, in my 3rd life. This will not mean that i will jump through the windows, because i'm overloaded. I just plan well my working hours. When it's too much, i pass my time to sport, make garden, trip, take photo, dog-walk, etc...

Last point : Robin is retired. He have certainly more free time than me to work on open source, with less pressure. So he has no right to judge me has a man who make a mess. This point of view is just inacceptable.

Gilles Caulier

2017-03-11 12:06 GMT+01:00 jdd <[hidden email]>:

Le 11/03/2017 à 11:55, Gilles Caulier a écrit :

I dislike a lots this kind of message :

http://dev.exiv2.org/issues/1267#change-5904

Seriously... If a crash appears in Exiv2 implementation, we report as
UPSTREAM. It's normal. And i'm sorry, but if a crash appear, it's
because a bug is inside the code, especially if the backtrace is explicit...

the man works too much and is easily upset. I very often notice such reactions in open source world, where people works on free time after the usual work and easily burn out :-(

I too have such reaction, but given my age and experience, I try not to make others receive it :-)

https://www.youtube.com/watch?v=wugWGhItaQA

:-)
jdd

Le 11/03/2017 à 12:24, Gilles Caulier a écrit :

> Last point : Robin is retired. He have certainly more free time

don't think so :-(. I'm also retired and never had so much work for
family ("dad, now that you are retired, can you do that for me..."

I I'm tiring faster :-(

:-)
> me has a man who make a mess. This point of view is just inacceptable.

of course, I know your involvement and greatly appreciate it :-)

jdd

[Gilles Caulier-4]

I currently rebuild all digiKam bundle with Exiv2 video metadata support disabled.

At least all crashes inside Exiv2 about video file will disappear.

Another question is about the future of Exiv2. Look well in this message :

http://dev.exiv2.org/issues/1280#note-6

Robin Mills will left the project in December. Following the other message in Exiv2 bugzilla :

1/ Exiv2 don't care about digiKam.

2/ Exiv2 drop all UPSTREAM reports from digiKam.

3/ Exiv2 will not spare more time to finalize video support.

4/ Exiv2 think about to drop video implementation from the library.

5/ Exiv2 future goals do not follow the digiKam requirements.

What's the next stage ?

Gilles Caulier

2017-03-11 12:46 GMT+01:00 jdd <[hidden email]>:

Le 11/03/2017 à 12:24, Gilles Caulier a écrit :

Last point : Robin is retired. He have certainly more free time

don't think so :-(. I'm also retired and never had so much work for family ("dad, now that you are retired, can you do that for me..."

I I'm tiring faster :-(

:-)

me has a man who make a mess. This point of view is just inacceptable.

of course, I know your involvement and greatly appreciate it :-)

jdd

[AndriusWild]

What tool is creating xmp sidecar files for the video files at the moment? Exiv2 ?

But anyways, there has to be something else in the FOSS world that can handle the job.

Video format is just too different from the image format so it is tough to find a tool that can handle both very well. Exiftool came pretty close to that but it still lacks of ability to write many of tags.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-11 6:06 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

I currently rebuild all digiKam bundle with Exiv2 video metadata support disabled.

At least all crashes inside Exiv2 about video file will disappear.

Another question is about the future of Exiv2. Look well in this message :

http://dev.exiv2.org/issues/1280#note-6

Robin Mills will left the project in December. Following the other message in Exiv2 bugzilla :

1/ Exiv2 don't care about digiKam.

2/ Exiv2 drop all UPSTREAM reports from digiKam.

3/ Exiv2 will not spare more time to finalize video support.

4/ Exiv2 think about to drop video implementation from the library.

5/ Exiv2 future goals do not follow the digiKam requirements.

What's the next stage ?

Gilles Caulier

2017-03-11 12:46 GMT+01:00 jdd <[hidden email]>:

Le 11/03/2017 à 12:24, Gilles Caulier a écrit :

Last point : Robin is retired. He have certainly more free time

don't think so :-(. I'm also retired and never had so much work for family ("dad, now that you are retired, can you do that for me..."

I I'm tiring faster :-(

:-)

me has a man who make a mess. This point of view is just inacceptable.

of course, I know your involvement and greatly appreciate it :-)

jdd

[Gilles Caulier-4]

2017-03-11 16:48 GMT+01:00 Andrey Goreev <[hidden email]>:

What tool is creating xmp sidecar files for the video files at the moment? Exiv2 ?

yes

 

But anyways, there has to be something else in the FOSS world that can handle the job.

Video format is just too different from the image format so it is tough to find a tool that can handle both very well. Exiftool came pretty close to that but it still lacks of ability to write many of tags.

Exiftool is perl based, not C++

Gilles Caulier

[AndriusWild]

Can this help ?

http://owl.phy.queensu.ca/~phil/cpp_exiftool/

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-11 9:17 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

2017-03-11 16:48 GMT+01:00 Andrey Goreev <[hidden email]>:

What tool is creating xmp sidecar files for the video files at the moment? Exiv2 ?

yes

 

But anyways, there has to be something else in the FOSS world that can handle the job.

Video format is just too different from the image format so it is tough to find a tool that can handle both very well. Exiftool came pretty close to that but it still lacks of ability to write many of tags.

Exiftool is perl based, not C++

Gilles Caulier

[Gilles Caulier-4]

Effectively, it's interesting. I will take a look...

Gilles Caulier

2017-03-11 18:09 GMT+01:00 Andrey Goreev <[hidden email]>:

Can this help ?

http://owl.phy.queensu.ca/~phil/cpp_exiftool/

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: Gilles Caulier <[hidden email]>

Date: 2017-03-11 9:17 AM (GMT-07:00)

To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>

Subject: Re: Exiv2 bug reports

2017-03-11 16:48 GMT+01:00 Andrey Goreev <[hidden email]>:

What tool is creating xmp sidecar files for the video files at the moment? Exiv2 ?

yes

 

But anyways, there has to be something else in the FOSS world that can handle the job.

Video format is just too different from the image format so it is tough to find a tool that can handle both very well. Exiftool came pretty close to that but it still lacks of ability to write many of tags.

Exiftool is perl based, not C++

Gilles Caulier