Xtrans Sensor workflow

Hi there !
I own a Fuji X-T3 and use Siril since few weeks. What a great software !

I have then few questions on the support of XTrans Sensor :

  • What is the best “debayer” algorithm for this kind of Fuji sensor ?

  • From the pre-processing screen, are the “cosmetic” options relevant because the console log seems to say that it’s not for Xtrans sensors…?

  • In the same window, do we have to check or not the “CFA” options then ?

Finally, CFA extraction (or Ha, OIII…) fails (console says it’s not supported for Xtrans).
Is there a workaround (or a planned roadmap) to make it work ?

If I process the file (pre-process/align/stack) with “debayer” option for each sequence (RGB / OIII / Ha), then, if i use “split into RGB”, i can obtain 3 FIT files (R,G,B).

At the end, it is possible to mix FIT files from different sequences (taking R,G,B from seq1/seq2/seq3) with the RGB compose menu and process the final file (gradient, sin transform, etc…)

Is this workflow correct and can produce the same result/quality than the “official ha extraction” for “bayered” sensors ?

Thanks a lot for your answers (hope @lock042 will connect and see this post :wink: )

PS : Cyril, Bravo encore pour tout ce travail et suivi incroyable !!!

Hello and welcome.

You have no choice. Automatically the algorithm will be chosen by Siril to be Markesteijn which is the one we have implemented for X-TRANS sensor.

No, cosmetic correction from dark image won’t work with XTRANS images.

In consequence this option has no effect.

Unfortunately no. No workaround or planned roadmap. Moreover, due to the special pattern of this kind of sensor, I’m not sure that an extract algorithm would give good results.

The debayer option must be checked during image caibration, to be done just after. As explained in our tutorials.

IT probably won’t give same quality, because they are two different ways to produces images. However this is the best you can do and I think the result should be fine.

Do you think there’s a real interest for example, to pre-process files outside of Siril via an external-specialized software and then make .seq from TIFF files in Siril for processing or it is not worth it at all ?

Ok, understood.
In “cosmetic correction from dark images”, it’s only about removing"hot pixels" that’s it ?
i.e. master-dark is still used, nevertheless, for processing read noise, even with XTrans, you confirm ?

Why would you do that? Markesteijn is a really good algorithm, I think you can use it.

Sure. The only thing you cannot do ir is removing hot and cold pixel. But of course, all the calibration step is done with no issue.

Ok, that what i wanted to read because i know that the Xtrans Sensor is sometimes difficult to manage ! I will continue to use the full Siril process because i find the final result as good as it could be regarding the whole processing workflow.

Ok, i know there is a “pixel mapping” option now in my Fuji firmware but never used it, i will try to enable it and see what it produces (maybe worth than letting it disabled :slight_smile: )

Thanks for your answers !

1 Like

This is the algorithm used by just about all of the FOSS raw processors for Fuji files. If you read about other (non astro) raw programs for Fuji files, several of them show aritfacts, but AFAIK the one we use is good and right up there with specialized comerical software like silkipix.