Hi,

[Update]
recompiling GTK and DT did not help in terms of GTK errors.

Opening a copy of this file for the first time brings following messages:

[rawspeed] (_DSC6849.NEF) void rawspeed::HuffmanTable::setCodeValues(const 
rawspeed::Buffer&), line 176: Corrupt Huffman. Code va

BR, Micha.

Am Samstag, 31. März 2018, 19:19:57 CEST schrieb Michael Fritze:
> Hi,
>  
> I have since some time problems to open some files in DT. I don't know if it
> is a DT or camera problem. When I remember correct it started after I
> upgraded both DT to 2.4.1 and firmware of my Nikon D5500. 
> This is what happens on console:
> LANG= darktable
> [rawspeed] (_DSC4981.NEF) void rawspeed::HuffmanTable::setCodeValues(const
> rawspeed::Buffer&), line 176: Corrupt Huffman. Code value 92 is bigger than
> 16
>                                                                            
>                                                                             
>                                                            
> (darktable:12090): GLib-GObject-CRITICAL **: g_object_set_data: assertion
> 'G_IS_OBJECT (object)' failed  (darktable:12090): Gtk-CRITICAL **:
> gtk_widget_get_has_tooltip: assertion 'GTK_IS_WIDGET (widget)' failed
> [rawspeed] (_DSC4988.NEF) void rawspeed::HuffmanTable::setCodeValues(const
> rawspeed::Buffer&), line 176: Corrupt Huffman. Code value 92 is bigger than
> 16 [temperature] failed to read camera white balance information from
> `_DSC4988.NEF'! allocation failed???
> 
> 
> On desktop, DT says it could not read white balance.
> These files are already added to the database, importing the files was no
> problem. I think for the preview DT reads the embedded thumbnail. Problem
> is opening the raw data itself. 
> Distro is Gentoo. DT is 2.4.1.
> But I tried recently DT on a Win10 64bit machine. At least one file made
> also problems. 
> I guess here are some problems.
>  
> The GTK messages appear independent of having buggy raw files. I don't know
> if this comes from GTK or DT. However I'm rebuilding x11-libs/gtk+-3.22.19
> and then DT. Maybe that helps. 
> Then there are rawspeed/temperature errors. Since it only affects some raw
> files, I'd guess it is a ramdom bug in the raw files. 
> Is there a way of scanning a folder for such buggy raw files?
> What can I do to fix these pictures?
> How can I find out what the root cause of this is?
>  
> Best Regards, Micha.
> 
> ____________________________________________________________________________
> darktable user mailing list to unsubscribe send a mail to
> [email protected]



____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to