{"push_id":708410670,"size":1,"distinct_size":1,"ref":"refs/heads/fix-icc-with-swapped-matrix-and-lut","head":"199e7316f9dacbf9a9c23fbe8facf6dd6e660400","before":"92a04717390c7a050c40fabf515408c62aaae56e","commits":[{"sha":"199e7316f9dacbf9a9c23fbe8facf6dd6e660400","author":{"email":"c247390a474ba78064f3a5ec8d0ca3a56d88a36b@gmail.com","name":"Roman Lebedev"},"message":"get_matrix_from_profile(): if there is a LUT, give up. Fixes #10552\n\nIf profile contains only a LUT, we would fall-back to LCMS codepath.\nIf profile contains a matrix + LUT, we would just use matrix in our\nfast matrix codepath.\n\nBut, if profile contains a LUT, it might contain a swapped matrix, so\nsome apps (like us right now) would use matrix, and get an image with\nswapped colors, and some would use LUT and get image with right colors.\n\nThe matrix in a XYZLUT profile is intended for older outdated CMS\nimplementations and should not be used.\n\nFalling back to matrix used to kinda-sorta make sense when our fastpath\nwas an order of magnitude faster than our LCMS2 path,\nwhich is no longer true. (pr #495 + pr #509)","distinct":true,"url":"https://api.github.com/repos/LebedevRI/darktable/commits/199e7316f9dacbf9a9c23fbe8facf6dd6e660400"}]}