0.90
...
·
·
2
likes
|
---|
That is the way it is. There is also starXterminator from Russell Croman, they have just minor performances differences. I like to use it AFTER I have stretched the image (masked stretch usually). Otherwise, you will stretch the starless far beyond than the star_mask and it will make a poor merge when you combine them back. Even by re-stretching the star_mask will be difficult to match the intensities. |
8.66
...
·
·
1
like
|
---|
It does a decent job I'd reckon. Are you screening the stars in and out? Also, I'd remove stars in the linear phase and then process them separately, if at all feasible. |
8.99
...
·
·
1
like
|
---|
andrea tasselli: This. Starnet2 has always worked great for me and there are no signs of its use when the stars are removed while the image is linear screened back on at the end. It's normal to see the black circles where the stars used to be in the starless image. Removing the stars in linear form also has gives you control over how much you want the stars to be stretched. Basically a method of star reduction. |
9.63
...
·
·
1
like
|
---|
Looks about normal for Starnet2. StarX is far superior, but that's not to say it doesn't have it's quirks. StarX is more likely to eat filamentary structures in your data, so use it carefully. Starnet2 has always left behind a mottle in my work, and because of that, it's no longer in my processing workflow. |
8.66
...
·
·
2
likes
|
---|
I just finished testing starnet++ 2.1.1 against SXT and starnet came out clearly on top on a linear image, with or without BXT applied beforehand. And thank goodness for that, too... |
11.80
...
·
·
2
likes
|
---|
As far as I know, StarNet++ is designed to work best on stretched images. I get very good results in the middle of the several stages of stretching. |
3.61
...
·
|
---|
alright, so it sounds like I need to use it after streching. them image, that does make sense, since I don't see those artifacts when I don't strech it to far. It's just a little frustrating when I captured enough data but I can't strech the image because of the artifacts Starnet 2 creates. I haven't had those issues with Starxterminator when I used the text version. |
11.25
...
·
·
1
like
|
---|
I find StarNet 2 excellent, and in the rare case something is left behind, it can be managed with a retouching tool. Regarding your image, I believe the real problem is the lack of SNR for which StarNet 2 can't do anything about it, it just reveals the issue for you. Happy Holidays and Clear Skies! |
5.12
...
·
·
1
like
|
---|
The original version of Starnet++ only worked on stretched images. The current version supposedly works on linear images, but I have never gotten good results that way. I only use it on stretched images. I get less ringing that way. |
2.94
...
·
|
---|
The result you have obtained looks good from my perspective. As mentioned by others, I usually do Starnet++ after image stretching. My recommendation is always to verify the starless version versus the image prior Starnet++. As a matter of fact, it happens sometimes that thin filaments are deleted in the starless version. Of note I saw a detailed comparison between Starnet and Starexterminator. In some cases Starnet is superior, in other cases it is the reverse. I use Starnet because is significantly faster. CS, Nicola |
11.80
...
·
|
---|
Kathy Walker: I probably am still using the same 2.0 version. It does work well on linear images for me, but works excellently on somewhat stretched images. Do you mean the 2.1 version should work on linear images? That will be nice. |
8.66
...
·
|
---|
Wei-Hao Wang: Starnet++ 2.1.x works on linear images better than SXT in most circumstances. |
0.00
...
·
|
---|
works perfect for me, I always stretch my images first in Maxim, then starnett them |
0.00
...
·
·
1
like
|
---|
A comment from my side. I´m using StarNet2 for a while. I´m always processing the background and the stars separately. The star picture is generated by substracting the starless picture from the original. By inspecting the areas between the stars the picture values are definitively zero. That means by generating the starless picture no artefacts are introduced. Only in the direct neighbourhood of the stars there are artefacts. By recombinig the two seperately processed pictures the result is in most cases satisfying. |
2.11
...
·
|
---|
Where are you guys downloading StarNet2? About a year ago it stopped updating in Pixinsight for me and when I did a search I read it didn’t work any longer. I just did a Google search and when I click on the StarNet website, it never opens. I liked having it because, as Nicola stated, some images work better with StarNet and others work better with SXT. |
0.00
...
·
·
1
like
|
---|
Im not a Pix insight user, so Im using the M1 optimised version in terminal on my Mac, it's lightening fast. I altered the script so it produces the starless and the star mask . |
10.32
...
·
·
1
like
|
---|
Hi @Jens, Are you sure you're using the last Starnet 2? All this talk about linear does not make sense, it works perfectly well for linear images and it even has a tick box for selecting if the data is linear or not. These spots are very unusual, they were visible for both SN2 or SXT in their first versions, now they work really well. I prefer SN2, you have interesting options with it (like 2x upsample). The problems are usually the very big, bright stars and their halos. The problem I see with your image is that is very noisy. Sometimes this can influence how the AI is reconstructing (or making up) the blank space behind the stars. Clean data works much better since the background values are more uniform. Second, if this is an auto-stretch it will exaggerate those differences. I would check if it's the last Starnet version and try some light noise reduction before applying it. All best, Bogdan |