https://bugs.documentfoundation.org/show_bug.cgi?id=98743
--- Comment #24 from xordevore...@gmail.com --- Created attachment 180750 --> https://bugs.documentfoundation.org/attachment.cgi?id=180750&action=edit original bug report's file, exported as a tif from paint.net Paint.net uses three parameters with TIF exports: a dithering level (1 to 8) bit depth (1, 4, 8, 24, 32) and a quantization algorithm dependent on selected bit depth (Median Cut, Octree) With me using paint.net's auto-detect setting, paint.net selected Octree for the algorithm and a dithering level of 7 when re-saving the original bug reporter's attachment as a TIF file. Paint.net forces use of the octree quantization algorithm for bit depths 24 and 32, and the user is given the choice between octree and median cut for depths 1, 4, and 8, but does not report on the UI what the actual bit depth was if set to auto-detect (but because Octree was defaulted, the auto-detected bit depth had to be either 24 or 32). Wild guess here, perhaps the engine you're using for the TIF export is not reporting everything it's implementing during the export process and is locked to a particular export format, or is using an optimization algorithm other than the one paint.net is using (which wouldn't of itself be a bug, just a different approaching to performing the export). I did not see any visual difference between the original and paint.net's export, so I'm not sure what information got lost between the original's 417K and paint.net's 277K export. -- You are receiving this mail because: You are the assignee for the bug.
