Le forum des utilisateurs de Siril

Nouvelles:

  • L'équipe de développement de Siril est heureuse de vous accueillir dans ce forum.

    Siril est maintenant en version RC1 ;-)

    Le forum a été migré vers l'adresse www.forum.siril.org mettez à jour vos favoris !!!
  • We are delighted to welcome you to this forum

    Siril is now in RC1 version ;-)

    The forum has been migrated to www.forum.siril.org update your bookmarks!!!

Nouvelles

We are delighted to welcome you to this forum

Siril is now in RC1 version ;-)

The forum has been migrated to www.forum.siril.org update your bookmarks!!!

Messages récents

1
User assistance / Re : Reporting data for time series photometry
« Dernier message par lock042 le mai 22, 2019, 04:50:29 16 »
Julian date is no more truncated.
2
Vos propositions d'évolutions / Re : Interface
« Dernier message par lock042 le mai 20, 2019, 02:40:42 14 »
Il y a en effet une regression dans la version 0.9.11 que nous allons corriger avant la sortie de la version stable.
3
User assistance / Re : Re : View window vs. Transformation
« Dernier message par elladan le mai 14, 2019, 05:43:56 05 »
The thing is also that many users use siril results to start the final processing of their images in an image manipulation program. In that case, they need to keep the 16 bits.

But I understand your need. We assume that the histogram tool is more powerful than having the rendering modes and cursors like the display window, maybe we are wrong. We also assumed that the histogram tool was fast enough.

We'll think about it and see how we can integrate the best of both worlds.
Thanks

Thanks for the comments! I also like to process my images into an external editing tool, but I find it convenient to do the first pass in Siril.

Just to clarify here, applying the visualization mapping doesn't imply reducing the bit depth. You can just scale whatever transformation is being displayed to map the pixel values into a 16-bit linear space.
4
User assistance / Re : View window vs. Transformation
« Dernier message par vinvin le mai 13, 2019, 10:22:25 22 »
The thing is also that many users use siril results to start the final processing of their images in an image manipulation program. In that case, they need to keep the 16 bits.

But I understand your need. We assume that the histogram tool is more powerful than having the rendering modes and cursors like the display window, maybe we are wrong. We also assumed that the histogram tool was fast enough.

We'll think about it and see how we can integrate the best of both worlds.
Thanks
5
User assistance / Re : -debayer
« Dernier message par vinvin le mai 13, 2019, 10:18:45 22 »
Precisely :)
6
User assistance / Re : Reporting data for time series photometry
« Dernier message par vinvin le mai 13, 2019, 10:17:39 22 »
Hi, thanks for the information, we'll try to improve that.
I don't know more than what lock posted on the error computation.
Best regards
7
User assistance / Re : crash using dark frames
« Dernier message par alacant le mai 13, 2019, 03:52:39 15 »
Thanks.
Great work on a great app:)
8
User assistance / Re : -debayer
« Dernier message par elladan le mai 13, 2019, 09:46:37 09 »
I have been looking at the various scripts and I am not sure about the use of -debayer.

I'm certainly not an authority on this, but consider that the Bayer pattern image sensor is only providing sparse values for each of the R, G, B color channels. That is, it's a mono image which you just happen to know was run through a bayer filter. When you debayer, what this is doing is applying some sort of interpolation function to this sparse color data to supply computed RGB values for each pixel.

When you record bias and dark current frames, you're recording the noise data from the image sensor itself, unrelated to the Bayer filter in front of it. So, when you subtract these frames, you need to do that before you do the interpolation -- otherwise, you'd be trying to remove real signal from interpolated data. Or alternatively, you'd need to debayer the calibration frames too, which wouldn't be good.
9
User assistance / Re : Re : View window vs. Transformation
« Dernier message par elladan le mai 13, 2019, 09:34:19 09 »
Hello, this is the expected result with the recent versions. As you found out, you need to change the pixel values before saving the file, it's not related any more to the screen transfer function of the view.

Using the asinh or histogram is indeed the way to go now, I'm sorry if you don't find it good. In recent versions previewing is possible. We'll think about adding the values in the GUI.

Regards

Thanks for the response. Siril is a great tool, and I'm really enjoying using it. :-)

My criticism of the pixel transform approach is primarily just that the GUI for the screen transfer is much nicer in certain ways. In addition to the fine control problem, I guess I should note also that there just doesn't seem to be an option for log, sqrt, or squared transforms in case someone wanted those. I did notice that autostretch was available as a button in the histogram tool.

That said, an "apply this transform to the pixel values" button in the view window would seem quite convenient. Certainly right clicking (on the RGB preview!) didn't seem like a particularly intuitive interface in the past.
10
User assistance / Re : View window vs. Transformation
« Dernier message par vinvin le mai 13, 2019, 12:34:50 00 »
Hello, this is the expected result with the recent versions. As you found out, you need to change the pixel values before saving the file, it's not related any more to the screen transfer function of the view.

Using the asinh or histogram is indeed the way to go now, I'm sorry if you don't find it good. In recent versions previewing is possible. We'll think about adding the values in the GUI.

Regards