[digiKam-users] DigiKam 6.0.0b appimage Photograph Properties

[VALÍK Robert]

Hey there,

I have noticed that the Photograph Properties don't display photograph's
Aperture and Exposure correctly - both are "unavailable".

If I look up the photo in DigiKam core DB and view ImageMetadata, the
aperture and exposureTime fields have correct values. Anyone else
noticed that?

It seems that the Aperture is displayed correctly if it has an integer
value (p.e. 4, 5, 16) but not if it is decimal (p.e. 1.8, 6.3).

Thanks.

--
Robert Valík
https://robert.valik.sk/

Sent from my MUA

[Gilles Caulier-4]

Hi,

There is no reason for that. Can you share the image to test here on my computer. I will try to reproduce the problem.

Gilles Caulier

2018-09-01 9:54 GMT+02:00 VALÍK Robert <[hidden email]>:

Hey there,

I have noticed that the Photograph Properties don't display photograph's
Aperture and Exposure correctly - both are "unavailable".

If I look up the photo in DigiKam core DB and view ImageMetadata, the
aperture and exposureTime fields have correct values. Anyone else
noticed that?

It seems that the Aperture is displayed correctly if it has an integer
value (p.e. 4, 5, 16) but not if it is decimal (p.e. 1.8, 6.3).

Thanks.

--
Robert Valík
https://robert.valik.sk/

Sent from my MUA

[VALÍK Robert]

Hey,

it is not "image specific" - the database seems to be OK. Every image
with non-integer Aperture has the "unavailable" - doesn't matter if it
is from RAW from DLSR or JPEG from iPhone.

Even images that were OK in the 5.9.0 are affected.

When I get home, I will provide an image.

Robert

On 2018-09-01 10:19, Gilles Caulier wrote:

> Hi,
>
> There is no reason for that. Can you share the image to test here on my
> computer. I will try to reproduce the problem.
>
> Gilles Caulier
>
> 2018-09-01 9:54 GMT+02:00 VALÍK Robert <[hidden email]>:
>
> > Hey there,
> >
> > I have noticed that the Photograph Properties don't display photograph's
> > Aperture and Exposure correctly - both are "unavailable".
> >
> > If I look up the photo in DigiKam core DB and view ImageMetadata, the
> > aperture and exposureTime fields have correct values. Anyone else
> > noticed that?
> >
> > It seems that the Aperture is displayed correctly if it has an integer
> > value (p.e. 4, 5, 16) but not if it is decimal (p.e. 1.8, 6.3).
> >
> > Thanks.
> >
> > --
> > Robert Valík
> > https://robert.valik.sk/
> >
> > Sent from my MUA
> >

--
Robert Valík
https://robert.valik.sk/

Sent from my MUA

[VALÍK Robert]

Forgot to mention, I use Slovak locale - we use comma separated decimal
(2,8) places instead of dot (2.8).

On 2018-09-01 10:19, Gilles Caulier wrote:

> Hi,
>
> There is no reason for that. Can you share the image to test here on my
> computer. I will try to reproduce the problem.
>
> Gilles Caulier
>
> 2018-09-01 9:54 GMT+02:00 VALÍK Robert <[hidden email]>:
>
> > Hey there,
> >
> > I have noticed that the Photograph Properties don't display photograph's
> > Aperture and Exposure correctly - both are "unavailable".
> >
> > If I look up the photo in DigiKam core DB and view ImageMetadata, the
> > aperture and exposureTime fields have correct values. Anyone else
> > noticed that?
> >
> > It seems that the Aperture is displayed correctly if it has an integer
> > value (p.e. 4, 5, 16) but not if it is decimal (p.e. 1.8, 6.3).
> >
> > Thanks.
> >
> > --
> > Robert Valík
> > https://robert.valik.sk/
> >
> > Sent from my MUA
> >

--
Robert Valík
https://robert.valik.sk/

Sent from my MUA

[Maik Qualmann]

MySQL and AppImage? We have a locale problem with converting to a double value by comma or dot. The problem could not be solved yet. It depends on their set system locale.

Maik

VALÍK Robert <[hidden email]> schrieb am Sa., 1. Sep. 2018 10:46:

Hey,

it is not "image specific" - the database seems to be OK. Every image
with non-integer Aperture has the "unavailable" - doesn't matter if it
is from RAW from DLSR or JPEG from iPhone.

Even images that were OK in the 5.9.0 are affected.

When I get home, I will provide an image.

Robert

On 2018-09-01 10:19, Gilles Caulier wrote:
> Hi,
>
> There is no reason for that. Can you share the image to test here on my
> computer. I will try to reproduce the problem.
>
> Gilles Caulier
>
> 2018-09-01 9:54 GMT+02:00 VALÍK Robert <[hidden email]>:
>
> > Hey there,
> >
> > I have noticed that the Photograph Properties don't display photograph's
> > Aperture and Exposure correctly - both are "unavailable".
> >
> > If I look up the photo in DigiKam core DB and view ImageMetadata, the
> > aperture and exposureTime fields have correct values. Anyone else
> > noticed that?
> >
> > It seems that the Aperture is displayed correctly if it has an integer
> > value (p.e. 4, 5, 16) but not if it is decimal (p.e. 1.8, 6.3).
> >
> > Thanks.
> >
> > --
> > Robert Valík
> > https://robert.valik.sk/
> >
> > Sent from my MUA
> >

--
Robert Valík
https://robert.valik.sk/

Sent from my MUA

[VALÍK Robert]

Hello,

thanks for clarification. Starting digikam using:

LC_NUMERIC="en_US" ~/Applications/DigiKam/digikam.appimage

Seems to be a workaround for me for now.

Thanks.

Robert

On 2018-09-01 10:55, Maik Qualmann wrote:

> MySQL and AppImage? We have a locale problem with converting to a double
> value by comma or dot. The problem could not be solved yet. It depends on
> their set system locale.
>
> Maik
>
> VALÍK Robert <[hidden email]> schrieb am Sa., 1. Sep. 2018 10:46:
>
> > Hey,
> >
> > it is not "image specific" - the database seems to be OK. Every image
> > with non-integer Aperture has the "unavailable" - doesn't matter if it
> > is from RAW from DLSR or JPEG from iPhone.
> >
> > Even images that were OK in the 5.9.0 are affected.
> >
> > When I get home, I will provide an image.
> >
> > Robert
> >
> > On 2018-09-01 10:19, Gilles Caulier wrote:
> > > Hi,
> > >
> > > There is no reason for that. Can you share the image to test here on my
> > > computer. I will try to reproduce the problem.
> > >
> > > Gilles Caulier
> > >
> > > 2018-09-01 9:54 GMT+02:00 VALÍK Robert <[hidden email]>:
> > >
> > > > Hey there,
> > > >
> > > > I have noticed that the Photograph Properties don't display
> > photograph's
> > > > Aperture and Exposure correctly - both are "unavailable".
> > > >
> > > > If I look up the photo in DigiKam core DB and view ImageMetadata, the
> > > > aperture and exposureTime fields have correct values. Anyone else
> > > > noticed that?
> > > >
> > > > It seems that the Aperture is displayed correctly if it has an integer
> > > > value (p.e. 4, 5, 16) but not if it is decimal (p.e. 1.8, 6.3).
> > > >
> > > > Thanks.
> > > >
> > > > --
> > > > Robert Valík
> > > > https://robert.valik.sk/
> > > >
> > > > Sent from my MUA
> > > >
> >
> > --
> > Robert Valík
> > https://robert.valik.sk/
> >
> > Sent from my MUA
> >

--
Robert Valík
https://robert.valik.sk/

Sent from my MUA

[Rafael Linux]

Talking about "not showed" properties, I miss compression format in TIFF
files. It's important to know if image file is compressed or not. Nowadays I need
to add to the name info about kind of compression (internal archive). My
personal TIFF photos are compressed, but for work, it should be stored
without any kind of compression, so for me it's important to show that
file info.

Thank you



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html