Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - eganz

Pages: [1]
Wish List / HDR mix
« on: 2018 April 15 06:09:07 »
 It would be nice to add an option to mix in a percentage of the original image when doing HDR  Multiscale transformation

  For example, I often find that when doing HDR on Luminance on galaxies,  I end up mixing in 50%  of the original image using pixel math. Would be nice to include this option in the original HDR box.

Thanks, Eric

Wish List / Export to Photoshop
« on: 2017 December 14 05:59:06 »
 This could be a quick shortcut key or Menu item.

  This would quickly export an image to a 16 bit, zip tiff file.



New Scripts and Modules / Apply STF
« on: 2017 September 09 05:27:48 »
The apply STF script by mike schuster  does not seem to work anymore in the current version of pixinsight.   It will not load into a windows 10 64-bit system.  Is there a new version of this script?


Wish List / MMT, BPP , Apply STF
« on: 2016 December 10 08:32:18 »
Here are some simple changes that might be nice:

Multiscale median transform:
Linear mask section, the amplification should be float, instead of integer. Currently, for stretched images, it would be desirable to be able to choose numbers between 1 and 2 for example.

Batch preprocessing:
It would be nice if BPP would open up the integrated images, and apply an STF. Then one could see the results, and potentially change the integration parameters etc.
(currently this can be done by opening up a 2nd instance of PixInsight, but that seems awkward).

Also, when writing the flat master files, the program should distinguish between East and West, when constructing the name.

This module should remember its settings (like batch  subframe selector), and then it would not be necessary to ask if you want to leave. (and yes, we already can drag the instance onto the desktop to save the settings which is very useful).

Integration Module:
It would be desirable for the STF to be applied (for viewing) automatically after integration. (i.e. no need to press control A). This could save a lot of clicks.

Apply STF:
it should be possible to apply the STF permanently to the image (i.e. stretch image) in an even easier way in the main program without having to use the "apply STF" script (which I currently use).

For example, sometimes one might use the STF to touch up a stretched image by using the sliders. This is convenient, and would be more convenient if you could apply the STF from the STF box, with one click.

Certainly, one will sometimes use the histogram box, or use masked stretch etc. to carefully stretch the image, but nevertheless, I find that I often use STF either to make a quick look at an image, or to modify the other stretch results.

Actually, we've heard that there may be a new stretch tool coming based upon the STF. This would be an ideal solution as it would satisfy your philosophical criteria about the original STF tool, while also allowing sliders and quick and reproducible application of stretching using the method based on this technique.



Wish List / Mure denoise, TIFF, and STF
« on: 2016 July 30 07:16:40 »

I suggest:

Incorporate Mure denoise as a normal process. This would speed the use of this very important process. More people should use this in the linear stage of processing.

Add a button or hotkey to the screen transfer function window to enable stretching. Currently one needs to drag the process to the histogram transformation tool etc., and this is a function that one does repeatedly. One button on STF could improve efficiency at this point, there should be no need to involve the histogram tool at all.

Increase the range of values for the global scaling parameter to allow a larger range of Windows 10 scaling parameters on 4K screens.

Improve the ability to output files into tiff format. Currently the defaults are all incorrect for most people, and must be reset every single time you output a file. Instead, either make the default 16 bit integer, and zip, or allow the user to change the default settings. In any case the program should remember the settings that the user is using. This does not need to take so many steps.



Bug Reports / Windows 10 and high DPI 4K screens
« on: 2016 July 25 05:59:15 »

Normally, I run with 350% scaling in Windows 10 with my 24 inch 4K screen which is 185 dpi, but pix insight has trouble with this.
However, if I turn it down to 250% scaling, and reboot, then pix insight behaves much better.

None of the memory errors are seen, and everything works well including zooming etc.
However, often the fonts are very tiny.
If I adjust these in the global settings, then I end up with a UI scaling factor of 1.0, and font dpi setting of 130.
The program operates normally in this state, with the full-screen visible, including the lowest readout bar.

It would be very helpful if you could allow even smaller UI scaling factors down to 0.7 .
This is an easy fix, and you could even allow a wider range between 0.5 to 4 for this parameter.

In this case, I might be able to fit my original and desired 350% Windows 10 scaling with the program.

At some point, it would be nice if you could test the program more on high dpi monitors, and make it more resilient to larger Windows 10 scaling factors.


First of all, let me say that pix insight is an incredible astrophotography editing program. :)

However, when I move the mouse over the histogram transformation box, It draws incorrect material from other parts of the screen, or from behind the screen onto the two black boxes which are supposed to hold the dynamic histogram.
Therefore, in order to use this box properly, I need to very carefully avoid letting the mouse be over these black boxes.
The entire histogram box will redraw correctly if I move it slightly from the top.

I also have various problems with memory errors (similar to those in others have reported) such as PCL Win32 system exception -access violation: invalid memory read operation at address…
these seem to occur when I first load in .FIT files that I have downloaded from online telescopes. These also occur if I tried to do image registration from "views" of these files. So far, I found that if I'm very careful not to use the mouse wheel to zoom in on these files, and to immediately change to the local file format .xisf, then I'm able to avoid these errors. For image registration, I use "files" not views as the sources In the StarAlignment process.

I'm using Pix Insight Standard Edition Ripley X64, QT 5.5.1, Windows 10, 64 bit on a PC, Nvidia Quadro video card, 4K screen. I never have these kinds of errors in other applications, and am able to run prime 95 Etc. without problems.

Pages: [1]