Recent Posts

Pages: 1 2 [3] 4 5 ... 10
General / Re: Sumofsquares formula from statistics
« Last post by Juan Conejero on 2019 November 14 04:38:35 »
Hi Roberto,

This bug is now fixed with an update for all platforms. The update is available after upgrading to the latest 1.8.8-1 core version. Thank you for your support.
Announcements / PixInsight 1.8.8-1 Released
« Last post by Juan Conejero on 2019 November 14 04:27:27 »
Hi all,

I am glad to announce a new version of the PixInsight core application: 1.8.8-1. This version is now available as an automatic update to version 1.8.8 for FreeBSD, Linux, macOS and Windows.

Main Bug Fixes and Improvements

* Fixed a bug where a wrong warning message was shown when closing an image, after working on it in the Real-Time Preview interface with multiscale processing tools (MultiscaleLinearTransform and MultiscaleMedianTransform). Original bug report:

* Fixed an object dereferencing bug that was causing a memory leak of 32 bytes per image. This bug has not been reported by users.

* Implemented several improvements to the Real-Time Preview interface, which is now faster and provides more robust previews with respect to the initial 1.8.8 version.

* Build numbers are now definitely deprecated and will no longer be used (although they are still available from JavaScript code for compatibility with existing scripts). Build numbers have been replaced by revision numbers, which are exclusive for each release (for example, this new 1.8.8-1 version).

* The application's main window title no longer shows version numbers. The title is from now on just "PixInsight".

Breaking Changes

New syntax of update repository information XML files. The deprecation of build numbers, along with several improvements implemented in this version, change the way update repositories must define their XML repository information files ('updates.xri' files) from now on. A complete description of these changes will be published, but to keep existing third-party repositories working right now, below is a description of an important change that should be implemented by third-party repositories in 'updates.xri' files to provide updates since version 1.8.8-1.

Until version 1.8.8-1 of PixInsight, the 'version' attribute of 'platform' XML elements can include optional build numbers as fourth elements of version specifications. Here is an example:

   <platform os="all" arch="noarch" version="">

Since version 1.8.8-1, build numbers are no longer allowed and version specifications must always have three components separated by dots. To address a particular range of PixInsight core versions, you should specify a revision number in the third element of each version specification, separated by an hyphen character. Examples:

   <platform os="all" arch="noarch" version="1.8.8-1:1.8.8-3">
   <platform os="linux" arch="x64" version="1.8.8-1:1.8.8-1">

In practice, this means that if you want to differentiate between specific core versions released before and after 1.8.1-1, you'll have to build separate repositories to distribute your scripts and/or modules, and inform your users about the different repository URLs.

If you are not using build numbers to distribute your scripts or modules selectively, then you don't have to make changes for now. For example, the following platform XML element will continue working correctly in PixInsight 1.8.8-1:

   <platform os="all" arch="noarch" version="1.8.6:1.8.8">

Should you have any doubts or problems with these changes, please don't hesitate to ask here.


Thank you for your attention.
You can use the split CFA Process to get separate channels for each element of the colour matrix. For RGGB, CFA0 will contain the Ha, CFA1 and CFA2 the OIII and CFA3 shouldn't contain too much at all. Now you can combine CFA0 with either one of the OIII channels or an average of the two and then do a Pixelmath Synth for the other. I tend to put CFA0 to red, CFA1 and 2 to blue and do a Pixelmath expression for half of each to green. You will need to play with the colour balance but it works pretty well.
I've tried to come up with a "theorem" for the global light and dark settings, thinking there could be some sort of correlation with a given set of LP, exposure and other parameters and build an excel macro to spit out the light and dark settings.  I gave up though.  It seems to be totally unique to the image in question and the set of prevailing circumstances regarding the capture of that image's data.


I will be speaking on this very topic at the Advanced Imaging Conference on Friday as part of my presentation.
The two parameters you need to adjust are the global dark and the perhaps you may need to adjust the synthetic
PSF if the tails are too large. You did not mention your global dark setting.
The "trick" is to find the right parameter that minimizes the ringing where stars are embedded in nebulosity *AND* not have
the global dark brighten stars that are against the dark sky (which will be your next complaint!).

The complex local support image you indicate may not be necessary? Usually you just want to not sharpen only the very brightest stars.


How does everyone deal with Deconvolution on images with high dynamic range? Specifically, I am having issues with ringing of small stars surrounding larger bright stars as well as bright areas like the core of M31, where the background quickly approaches the value of small stars in the foreground. The image is Linear and has had no other processes applied to it aside from Background Extraction.

I am running a Decon process using (per Inside PixInsight by Warren Keller):

 - An external PSF rendered using the PSF Image Script

 - A non-linear image clone as an image mask for application

 - A star mask for deringing support. This star mask was made from 3 different star masks targeting various star sizes combined using Pixel Math with a Screen blend: 1-(1-A)*(1-B)*(1-C...

Decon looks fine when running on any number of previews on most of the image, but these bright areas seem to require different settings altogether. I have tried creating a Range Mask of brighter areas and subtracting it from the Luminance Mask, but this sidesteps the issue since I do want to run Decon on the brighter core of M31 (as I see a lot of detail improvement in the dust lanes at the cost of ringed stars). My second and latest attempt (used for the attached screenshot) was to make another star mask targeting small yet bright stars, convolute and brighten it to increase the star sizes, then combine it with the other star masks, but it does not seem to provide sufficient protection.

Any suggestions would be welcome, I'm stuck on multiple images due to this apparent impasse
General / Re: Photometric Colour Calibration
« Last post by brent1123 on 2019 November 13 20:21:18 »
I had this issue but solved it by changing servers. Maybe the one in Paris is down for maintenance?
Announcements / Re: PixInsight 1.8.8 Released
« Last post by jeffweiss9 on 2019 November 13 20:12:14 »
Thanks, Juan-
I understand the print options are below PixInsight standards, but it's just handy to have the options there once in a while for a quick snapshot of something.
The recent updates are great.
Announcements / Re: PixInsight 1.8.8 Released
« Last post by jeffweiss9 on 2019 November 13 20:07:58 »
Thanks, Herbert-

I just added
to the the target in the properties
of the PixInsight Shortcut on my Win10 desktop and it worked fine;
i.e., the printer commands are back on the file menu.

Clear Skies,
General / Re: Am I doing DBE correctly?
« Last post by johndias on 2019 November 13 18:06:07 »
Thanks, I did reduce the samples to 6.  Much easier to work with anyway. 

So, I tried saving the STF and applying but the stretch comes out not so good.  But, I'm not worried because I did a preview in HT and it looks much better and I think I can work with this.

Thanks Steve!

Pages: 1 2 [3] 4 5 ... 10