7.12
#...
·
 |
|---|
| No issues to report here. I never checked luminence any way though. |
7.17
#...
·
|
|---|
Paul Huntley: That's interesting, I didn't use this feature at all, so how to explain it? |
0.00
#...
·
|
|---|
| I was trying new elements of workflow as well, so this is not the only change I made. I think I've convinced myself the BXT update is clean. |
2.33
#...
·
·
2
likes
|
|---|
| I have not found a solution yet. Does anyone know, how I can go back to v1.15 ? |
3.31
#...
·
·
8
likes
|
|---|
| I experienced the darkening issue on my Pac-Man nebula (Bok globules and some other areas went black to the point of almost being clipped) and reported the issue back to RC. Had an update from RC today. He says he’s working on a fix right now and it should be released in a day or two. |
|
2.33
#...
·
·
3
likes
|
|---|
Paul Puntin: Thanks! Good to know!🙂 |
3.91
#...
·
·
13
likes
|
|---|
| I've just released BlurXTerminator 1.1.18 which should resolve the over-darkening issue. It's very tricky to get this to work correctly for all images, so there's a chance it could still show up on certain images. If you find an issue, please submit a support request at https://www.rc-astro.com/submit-ticket/ and upload your original image using the dropbox link at the bottom of the form. |
|
3.31
#...
·
|
|---|
|
Update worked for my Pacman image, PROVIDED you do a background extraction first (ABE or DBE). Saw no difference between v1.17 and v1.18, i.e. darkened areas, unless you do a BE first (though I can't remember if I did a BE when I was testing v1.17 and I can't go back a version). Again, without a BE, either using a manual PSF or cropping in very close to minimize the amount of dark sky, or switching to AI v1, or using BXT with a luminance mask, the new version works OK. I've relayed this back to Russ. |
1.43
#...
·
|
|---|
|
Not sure what's gone wrong with BXT. My version is 1.1.18 AI version 2. After one month of miserable weather, I am processing some images from last night. I found some strange results using BXT on my star reduction then this on the starless image.... Where does that sign come from???   |
|
3.91
#...
·
·
2
likes
|
|---|
| Was this in luminance-only mode? There seems to be an issue with it that I’m looking into now. At the moment I recommend against using it. |
|
1.43
#...
·
|
|---|
Russell Croman: Yes, this was with luminance only. |
 #...
·
·
2
likes
|
|---|
Robert Eder:Paul Puntin: Robert, I have seen such effects occurring in the past from BXT and even NXT well before the latest release. At first, I hardly noticed the effect since it was a dark on dark issue and visibility depended on the screen stretch I was working under. It was problematic in some images because I did not want to lose delicate structures seen within those dark areas. Having said that, my attitude is that no functions ever work perfectly. And for me, I was happy that PI offers many alternatives for work arounds, even when using the offending function. In one case, noise reduction was the primary culprit. Please read the end of my description in:  SH2-155, the Cave Nebula and much much more, in OSC. For more detail. In this case the work around was designed to mask the areas "clipped" by NXT so that I could use the NXT on the bulk of the image. Then a simple invert of the mask, and then use MMT to bring the noise within the rest of the image in line with the NXT denoised regions. Voila! Dynamic range preserved. Also, note that later in the processing, I was able to use NXT without any negative effect. My work around was painful. The reason is that NXT works so well, being forced to use MMT became a drag! Diddling with MMT to get the right settings takes time and then executing the damn function is so painfully slow! If @Russell Croman comes up with a complete fix, then that is great. But I still love BXT and NXT and hope to never have to go back to the old ways! BTW, this issue has arisen very inconsistently within the images that I have applied NXT and BXT in processing. I have no idea what is the lead trigger within the data that may cause this to happen or prevent it from happening. Maybe some of the images were simply starved for data and starved of dynamic range at the stage I was applying the functions? But in PI, at least the tools are there to deal with it. |
|
2.33
#...
·
|
|---|
Alan Brunelle: Yes, it is very inconsistent. If I have different previews of the same region, I get different results with the same settings! Sometimes I can't get rid of the dark areas and if I close the image and reload it, the dark areas are gone (same settings V1.1.18). Looks like BXT is keeping something in memory. |
7.61
#...
·
·
1
like
|
|---|
I found some strange results using BXT on my star reduction then this on the starless image.... Just be glad it’s not a pentagram…… Cheers, Scott |
 #...
·
|
|---|
Scott Badger:I found some strange results using BXT on my star reduction then this on the starless image.... This has append to me...I ran light denoise first and it resolved the issue |
|
7.61
#...
·
|
|---|
|
BTW, I would *guess* that the large scale pattern shows the tiles that went astray for some reason. Since it's a starless image, you used manual PSF, right? Cheers, Scott |
|
2.39
#...
·
|
|---|
|
Anyone have issues with StarXterminator? It runs faster after the update but now I am getting an error message that reads *** PixInsight API Error: DeleteViewProperty(): Low-level API function error (0x0061): Undefined view property It will remove the stars but won't generate a star image. How does one revert to an older version? |
|
7.17
#...
·
|
|---|
Blaine Gibby: I play with the StarX (v. 2.0.5, AI v. 11 lite) now, works OK and generates the stars' image. |
10.16
#...
·
·
1
like
|
|---|
Not sure what's gone wrong with BXT. To me, it looks like the Chinese character for " center". (中) |
