https://bugs.kde.org/show_bug.cgi?id=385726
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Image Framework DImg|Plugin-DImg-HEIF
--
You are
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #35 from Glassed Silver ---
(In reply to caulier.gilles from comment #31)
> About Apple Live Photo, Samsung's Motion Photos, and Huawei's Moving
> Picture, i'm not sure where the differences are located.
>
> I'm sure that Apple Live Photo
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #34 from Ritesh Raj Sarraf ---
(In reply to Ritesh Raj Sarraf from comment #20)
> (In reply to Ritesh Raj Sarraf from comment #19)
> > @Gilles Caulier
> >
> > Here's a link to Google Motion Photo.
> >
> >
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #33 from caulier.gil...@gmail.com ---
Huawei's Moving Picture file format => i cannot found technical details about
this container on the Web. So we need reverse engineering...
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #32 from caulier.gil...@gmail.com ---
Samsung's Motion Photo format consists of a picture (jpeg) and movie (mp4)
merged into a single file. Between them there is a special marker. The script
finds the marker and splits it accordingly.
It's
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #31 from caulier.gil...@gmail.com ---
About Apple Live Photo, Samsung's Motion Photos, and Huawei's Moving Picture,
i'm not sure where the differences are located.
I'm sure that Apple Live Photo is HEIF based.
in all cases libheif must
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #30 from Glassed Silver ---
Just checked the release notes for 7.2 and noticed that Apple Live Photo
Support has been scheduled for 7.4, which is fantastic!
I have one question though, are competing, similar formats like Samsung's
Motion
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #29 from caulier.gil...@gmail.com ---
Git commit c23ccd2c0e40c624631e748237aacbd26527eda8 by Gilles Caulier.
Committed on 16/03/2021 at 03:36.
Pushed by cgilles into branch 'master'.
Exiv2 0.27.4 will introduce Base Media File format
https://bugs.kde.org/show_bug.cgi?id=385726
Julien Lerouge changed:
What|Removed |Added
CC||julien.lero...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #28 from Glassed Silver ---
(In reply to caulier.gilles from comment #27)
> Don't be afraid. HEIF and CR3 support are popular format, and Bugzilla is
> here to remember the important entry (you can vote for this support here
> too).
>
>
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #27 from caulier.gil...@gmail.com ---
Don't be afraid. HEIF and CR3 support are popular format, and Bugzilla is here
to remember the important entry (you can vote for this support here too).
HEIF is Android and Apple used format -> very
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #26 from Glassed Silver ---
Thank you so much for your input.
I wasn't trying to advocate for a work-around, I was just trying to make sense
of why you're optimistic, since this seems like it could go either way over at
that project. At
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #25 from caulier.gil...@gmail.com ---
digiKam already rely on Exiv2 to all file format metadata support. There is no
exception for HEIF and CR3. We need to still homogeneous and not to make a big
puzzle. I'm fighting against this idea since
https://bugs.kde.org/show_bug.cgi?id=385726
--- Comment #24 from Glassed Silver ---
(In reply to caulier.gilles from comment #23)
> yes, HEIF is supported in digiKam 7.0.0 right now, but not yet the video
> embeded.
>
> The problem is with Exiv2 which refuse to support HEIF due to possible
>
https://bugs.kde.org/show_bug.cgi?id=385726
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|Add Support For Apple Live |Add Support For Apple Live
15 matches
Mail list logo
