search

Kalpanika / x3f

Tools for manipulating X3F files from Sigma cameras
86 stars 28 forks source link

Kalpanika and Capture One #106

Open alextitov75 opened 6 years ago

alextitov75 commented 6 years ago

Hi,

when i open the created dng in Capture One, the overexposed areas are filled with yellow. Could you please look into this issue?

rolkar commented 6 years ago

What camera are you using? Do you get yellow with Adobe raw converters, such as ACR or Lightroom?

alextitov75 commented 6 years ago

SD1

alextitov75 commented 6 years ago

Any news?

Понедельник, 11 декабря 2017, 0:53 +03:00 от Roland Karlsson notifications@github.com:

What camera are you using? Do you get yellow with Adobe raw converters, such as ACR or Lightroom? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

rolkar commented 6 years ago

Sorry, I have had no time to look at this.

Have you tested if it is also yellow with adobe products?

If not - can you provide a faulty file so I can take a look?

alextitov75 commented 6 years ago

In Adobe it is fine.

Четверг, 21 декабря 2017, 0:38 +03:00 от Roland Karlsson notifications@github.com:

Sorry, I have had no time to look at this. Have you tested if it is also yellow with adobe products? If not - can you provide a faulty file so I can take a look? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

alextitov75 commented 6 years ago

Hi, could you please look into it.

Четверг, 21 декабря 2017, 0:38 +03:00 от Roland Karlsson notifications@github.com:

Sorry, I have had no time to look at this. Have you tested if it is also yellow with adobe products? If not - can you provide a faulty file so I can take a look? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

rolkar commented 6 years ago

There are four possible reasons for this that I can think of

  1. The RAW channel is clipped. Then something extra ordinary is necessary, as otherwise the conversion formula will just go bananas. Maybe Adobe is taking that into account and Capture One not. There are several possible strategies for fixing this. The problem being that fixing it might degrade the Adobe conversion.

  2. It is a matter of clipping in the RGB color space. I am not sure why the image should become yellow though. So, this one is not likely.

  3. It is a matter of wrap around in RGB space. In that case, Capture One is the problem. We cannot do much about that, except handle the RGB clipping, which is outside of the scope of our converter, as it do no color space transformation.

  4. Some strange bug in Capture One.

Only 1. of those is anything we can fix.

Can you somehow supply the RAW and the Capture One output?

rolkar commented 6 years ago

Note though that there are several problems with DNG and non Adobe programs. It does not seem like other are fully following the specs. We cannot fix them all. Actually some are unfixable.

alextitov75 commented 6 years ago

Hi,

here is the original file.

Thanks

Понедельник, 15 января 2018, 13:34 +03:00 от Roland Karlsson notifications@github.com:

There are four possible reasons for this that I can think of

  • The RAW channel is clipped. Then something extra ordinary is necessary, as otherwise the conversion formula will just go bananas. Maybe Adobe is taking that into account and Capture One not. There are several possible strategies for fixing this. The problem being that fixing it might degrade the Adobe conversion.

  • It is a matter of clipping in the RGB color space. I am not sure why the image should become yellow though. So, this one is not likely.

  • It is a matter of wrap around in RGB space. In that case, Capture One is the problem. We cannot do much about that, except handle the RGB clipping, which is outside of the scope of our converter, as it do no color space transformation.

  • Some strange bug in Capture One. Only 1. of those is anything we can fix. Can you somehow supply the RAW and the Capture One output? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

alextitov75 commented 6 years ago

Roland, if you give me your email, i will send the Raw file. Thanks

rolkar commented 6 years ago

You can send it to contact@proxel.se. Both the RAW and the faulty JPEG.

The RAW is big and I am not sure mail will make it. But we will see. If it fails, you could try some means of sharing via the web.

rolkar commented 6 years ago

OK. I have taken a look at the JPEG. And also at the RAW in RawDigger. And now I know what the problem is. The topmost, and also sometimes the middle, channel is clipping where it is yellow. And, we are sending the channels as is (except for noise reduction) to the DNG file. We are doing nothing to the color balance in the file.

It is then up to Adobe or Capture One to use the color conversion tables and the data to make a picture. It seems like Adobe makes that intelligently and clip all channels when one input channel is clipping, while Capture one handles this poorly.

It is probably so that Capture One do not consider it to be a problem, as Bayer images do not have this kind of strong color conversions. While Adobe find it more important.

I cannot really find anything we can do about this.

rolkar commented 6 years ago

As an extra info - we do have a TIFF mode that has exactly this problem. We have on our TODO to fix that problem for TIFF. Id we do, which is not all that likely, then there could be a switch in X3F Tools to output RGB instead of X3. Then it might work with Capture One. This is messy work though.

alextitov75 commented 6 years ago

Hi,

Thanks for your help.

No news om RGB mode?

Thanks, Alex

Пятница, 26 января 2018, 23:59 +03:00 от Roland Karlsson notifications@github.com:

As an extra info - we do have a TIFF mode that has exactly this problem. We have on our TODO to fix that problem for TIFF. Id we do, which is not all that likely, then there could be a switch in X3F Tools to output RGB instead of X3. Then it might work with Capture One. This is messy work though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

alextitov75 commented 6 years ago

Hi,

are there any news on the RGB mode?

Пятница, 26 января 2018, 23:59 +03:00 от Roland Karlsson notifications@github.com:

As an extra info - we do have a TIFF mode that has exactly this problem. We have on our TODO to fix that problem for TIFF. Id we do, which is not all that likely, then there could be a switch in X3F Tools to output RGB instead of X3. Then it might work with Capture One. This is messy work though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

alextitov75 commented 6 years ago

Hi,

any news?

Среда, 4 апреля 2018, 15:45 +03:00 от Alexander Titov aleks_titov@mail.ru:

Hi,

are there any news on the RGB mode?

Пятница, 26 января 2018, 23:59 +03:00 от Roland Karlsson < notifications@github.com >:

As an extra info - we do have a TIFF mode that has exactly this problem. We have on our TODO to fix that problem for TIFF. Id we do, which is not all that likely, then there could be a switch in X3F Tools to output RGB instead of X3. Then it might work with Capture One. This is messy work though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

-- Alexander Titov

rolkar commented 6 years ago

Sorry! Activity have been very low - actually zero. I cannot promise anything :(

alextitov75 commented 6 years ago

I have developed a color profile for C1: http://www.lux-et-color.ru/wordpress/?p=3399  

If we could solve the overexposure probem, this would be the  best color solution for Sd1. 

Понедельник, 20 августа 2018, 21:43 +03:00 от Roland Karlsson notifications@github.com:

Sorry! Activity have been very low - actually zero. I cannot promise anything :( — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub , or mute the thread .

-- Alexander Titov