https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #37 from Grix ---
Finally bug on ORF files in Windows versión of digikam is fixed in versión 5.8
I've tested in digikam 5.8, windows 10 creator's update and it Works ok.
Good work, I know those type of bugs are difficult to track so
THANKS
https://bugs.kde.org/show_bug.cgi?id=381432
Kristian Karl changed:
What|Removed |Added
CC||kristian.hermann.karl@gmail
|
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #36 from Paul ---
Glad the issue was found! Will this fix be included in the official 5.8
release?
Although, I would rather have the ability to create DNGs, it would indeed be a
shame to never have the option to write metadata to DNG. I hav
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #35 from Maik Qualmann ---
Hi Gilles,
currently the option write to RAW file is greyed out in the GUI. somehow I
still hope for a further development of Exiv2. A version 0.26.1 seems to be
planned. We know 3 RAW file types that have errors
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #34 from caulier.gil...@gmail.com ---
Hi, Maik,
With this kind of patch, the Setup/Metadata/Write to Raw option will have no
effect in background.
I recommend to drop definitively this option from the GUI, if there is no other
work around s
https://bugs.kde.org/show_bug.cgi?id=381432
Maik Qualmann changed:
What|Removed |Added
Version Fixed In||5.8.0
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=381432
Maik Qualmann changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #32 from Maik Qualmann ---
The cause is now found, Exiv2 kills the DNG. Depending on the memory contents,
I can also reproduce graphics artefacts in the created DNG file under Linux. We
remove an Olympus tag ("Exif.OlympusIp.BlackLevel") fro
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #31 from Paul ---
You've got it. Sending it now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #30 from Maik
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #29 from Paul ---
I emailed a file link to you through Dropbox. I hope it helps!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #28 from caulier.gil...@gmail.com ---
yes, an ORF test file will help. Please share through an Internet cloud link
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #27 from Paul ---
Would it be helpful to have an orf file to test with?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #26 from Paul ---
Sorry, pressed save too soon on that comment.
The problem persists with 5.8pr
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #25 from Paul ---
Sorry to report... the issue persists.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #24 from caulier.gil...@gmail.com ---
Please test if the problem is reproducible with current digiKam 5.8.0
pre-release bundle where libraw have been updated and where few bugs have been
fixed with parallel processing.
https://files.kde.org/
https://bugs.kde.org/show_bug.cgi?id=381432
Paul changed:
What|Removed |Added
CC||formyweb...@gmail.com
--- Comment #23 from Paul ---
I'm
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #22 from caulier.gil...@gmail.com ---
*** Bug 378929 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #21 from caulier.gil...@gmail.com ---
Yes digiKam 5.5.0 for windows also use Exiv2 0.26 (code not released at 5.5.0
date and taken from subversion repository)
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #20 from g...@grix.tk ---
I´ll try but, does digikam 5.5 for windows use Exiv2 0.26 ?
Remember that the problem was also on that version.
Thanks
Guillermo M.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #19 from caulier.gil...@gmail.com ---
Please try with the AppImage linux bundle 5.6.0, which use also Exiv2 0.26. If
problem is reproducible, well the dysfunction is certainly located in Exiv2
library
Gilles Caulier
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #18 from g...@grix.tk ---
Linux Ubuntu : digikam 5.5 Exiv2 0.25
Windows10 : digikam 5.6 Exiv2 0.26
G.M.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #17 from caulier.gil...@gmail.com ---
Which Exiv2 version do you use under Linux ? Look in digiKam Help/Components
Info for details.
Under Windows, the bundle is compiled with last Exiv2 0.26.
Gilles Caulier
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #16 from g...@grix.tk ---
Sorry, I´m not a programmer but in windows 10 nor CLI and exiv2 are recognized
as commands.
In linux (where the conversion works OK) the shell tells me that nor cli or
exiv2 are installed
thanks.
G.M.
--
You are
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #15 from caulier.gil...@gmail.com ---
CLI = Command Line Interface.
Exiv2 is a library and also a console tools used to play with metadata. Look
here :
http://www.exiv2.org/getting-started.html
Gilles Caulier
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #14 from g...@grix.tk ---
I said that because I read this in debugview log:
005010.30132675 [6184] digikam.metaengine: Will write Metadata
to file
"P:/3FOTOS/2017/05Mayo/rosaleda/BatchTool-Hp6184-_5210023.ORF.digikamtempfile.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #13 from g...@grix.tk ---
Exiv2 CLI tool ?
What is that ? where can I get it ?
sorry I don't know about programming, can I use it ?
thanks
Guillermo M.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #12 from caulier.gil...@gmail.com ---
If it's an Exiv2 failure with ORF, it must be easy to reproduce with Exiv2 CLI
tool. The DNG converter use Exiv2 to extract Exif information from original to
backport it to DNG. This include all the maker
https://bugs.kde.org/show_bug.cgi?id=381432
g...@grix.tk changed:
What|Removed |Added
Attachment #106192|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #10 from caulier.gil...@gmail.com ---
Do you have enough space of disk to process ?
Can you rename the ORF file without '_' in file name ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #9 from caulier.gil...@gmail.com ---
Can you share the ORF file to hack here ?
Do you have any Anti-Virus active ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #8 from caulier.gil...@gmail.com ---
These messages are strange :
005758.28675461 [5132] digikam.general: DNGWriter: Backup
Makernote ( 3350 bytes)
005858.28700638 [5132] digikam.general: DNGWriter: Bui
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #7 from g...@grix.tk ---
I send the debugview log.
The image I was triying to convert was "_5270021.ORF"
Thanks
Guillermo M
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #6 from g...@grix.tk ---
Created attachment 106192
--> https://bugs.kde.org/attachment.cgi?id=106192&action=edit
Debugview
dng.log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #5 from caulier.gil...@gmail.com ---
DebugView is a separated program to take from M$ repository. It trace all debug
statements printed by an application. This is typically done in a console under
Linux. Under Windows, it's of course differen
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #4 from g...@grix.tk ---
(In reply to caulier.gilles from comment #3)
> Do you see anything special on DebugView program while digiKam and DNG tool
> is running ?
>
> Gilles Caulier
Sorry, don´t know where is the debug view
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #3 from caulier.gil...@gmail.com ---
Do you see anything special on DebugView program while digiKam and DNG tool is
running ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=381432
--- Comment #2 from g...@grix.tk ---
(In reply to caulier.gilles from comment #1)
> Strange. Nothing has changed in DNG tool source code between 5.5.0 and 5.6.0
Exactly, nothing has changed. It STILL not working
the bug remains there since version 5.5
O
https://bugs.kde.org/show_bug.cgi?id=381432
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
39 matches
Mail list logo
