Wei-Hao Wang · May 22, 2026, 10:14 AM
Is 1.9.4 for AS stable now? Or it is still buggy?
It’s great. Some people have had issues with plug-ins, but I haven’t experienced it. I also use a homegrown javascript to run through my gauntlet of inital tasks, and it works perfectly with JS v8.
Charles Hagen, Night Photons, just updated his scripts to V8.
Repository remained the same: https://raw.githubusercontent.com/charleshagen/pixinsight/main/updates/
On his website, it’s not yet mentioned. He emailed me yesterday.
With PI 1.9.4 ARM version, I tested PhotometricContinuumSubstraction (version 1.3.1) and it worked, giving (as far as I can visually check) the same result as the last pre-V8 version, with PI 1.9.3
Best regards.
Michael
PS: So far, 1.9.4 ARM is stable, mouse glitches are much less - but still no palm detection.
PPS: I have now up&running:
- BXT, SXT, NXT
- GHS
- CosmicPhoton scripts
- NightPhoton scripts
- SetiAstro
- and the scripts ported by Masters of PixInsight, especially DBXtract and DSE. Thank you, guys.
Such a shame we have to put up with these issues. Wish I hadn’t “upgraded” to 1.9.4 as it’s been nothing but problems and irritation, especially when some of the Pixinsight software people over at the Pixinsight Forum seem so cavalier about the problems this update has caused. I’m quite disappointed….
Steve Heath · May 25, 2026, 09:49 PM
Such a shame we have to put up with these issues. Wish I hadn’t “upgraded” to 1.9.4 as it’s been nothing but problems and irritation, especially when some of the Pixinsight software people over at the Pixinsight Forum seem so cavalier about the problems this update has caused. I’m quite disappointed….
They did some major surgery in this version, including delicate architectural changes to the obsolete scripting engine and upgrading to a recent version of cross-platform UI layer which allows them to support Apple Silicon natively (which boosts wbpp performance *significantly&, at least for me).
Add to that an echo system of (many old) 3rd party scripts, and you have the perfect recipe for disruptions in the short/medium term.
But the only alternative to not have disruptions is to never change - and even that eventually bites you.
Rostokko · May 25, 2026 at 10:00 PM
(which boosts wbpp performance *significantly&, at least for me).
Same here, process time divided by 2 approximately. Up to the point that I don’t bother to use the fast integration option any longer…
Michael · May 25, 2026 at 09:48 PM
Charles Hagen, Night Photons, just updated his scripts to V8.
Repository remained the same: https://raw.githubusercontent.com/charleshagen/pixinsight/main/updates/On his website, it’s not yet mentioned. He emailed me yesterday.
With PI 1.9.4 ARM version, I tested PhotometricContinuumSubstraction (version 1.3.1) and it worked, giving (as far as I can visually check) the same result as the last pre-V8 version, with PI 1.9.3
Best regards.
MichaelPS: So far, 1.9.4 ARM is stable, mouse glitches are much less - but still no palm detection.
PPS: I have now up&running:
- BXT, SXT, NXT
- GHS
- CosmicPhoton scripts
- NightPhoton scripts
- SetiAstro
- and the scripts ported by Masters of PixInsight, especially DBXtract and DSE. Thank you, guys.
Just the same scripts I have now updated to V8. I finally decided to give a chance to the last 1.9.4 build for Apple Silicon ( 1693 ) and since that ( 4 days ago ) it seems many script developers have been updating their tools. Some have changed the repository link ( so I have had to search for the new one, bad communication ) and others kept the previous ( 👏🏼👏🏼 ). But it remains some older tools that seems to be abandoned by their creators, so we will have to find an alternative if they never update them. But for now with the latest PI built, all seems to work fine both in my M1 Max and M5 Pro computers.
About the mouse/trackpad issues, at PI they consider this as if we are experiencing and UFO encounter. They never can corroborate this bug, but there are many people like us who suffer it daily. They should have an alternative dimension Mac ( or may be is us who live in a parallel Apple’s planet ) 😁😜
Though now all processes and scripts I use for linear processing, stretching, Narrowband-processing are available vor 1.9.4 ARM, I reverted to 1.9.4 x86 …
… because I noticed that many (most?) of the image analysis tools are not available for v8 engine:
SubframeSelector, AberrationInspector, FWHMEccentricity - all I use regularly.
Best regards.
Michael
PS: Someone ported today FWHMEccentricity - but I rather would like to have the native PI scripts.
Michael · May 26, 2026, 08:43 PM
SubframeSelector, AberrationInspector, FWHMEccentricity - all I use regularly.
SubframeSelector is there - it’s a process.
Rostokko · May 26, 2026 at 09:55 PM
Michael · May 26, 2026, 08:43 PM
SubframeSelector, AberrationInspector, FWHMEccentricity - all I use regularly.
SubframeSelector is there - it’s a process.
But - it’s not working in 1.9.4 ARM. Known bug - partially crashing PI, partially the result window is not shown. “Cannot reproduce” 🤣
Steve Heath · May 25, 2026, 09:49 PM
Such a shame we have to put up with these issues. Wish I hadn’t “upgraded” to 1.9.4 as it’s been nothing but problems and irritation, especially when some of the Pixinsight software people over at the Pixinsight Forum seem so cavalier about the problems this update has caused. I’m quite disappointed….
you can switch to the x86-64 version of 1.9.4 which still has the old javascript interpreter.
Michael · May 26, 2026, 09:58 PM
it’s not working in 1.9.4 ARM
Strange, it seems to work fine for me; but I’m likely not stressing it as you do.
pfile · May 26, 2026, 10:03 PM
Steve Heath · May 25, 2026, 09:49 PM
Such a shame we have to put up with these issues. Wish I hadn’t “upgraded” to 1.9.4 as it’s been nothing but problems and irritation, especially when some of the Pixinsight software people over at the Pixinsight Forum seem so cavalier about the problems this update has caused. I’m quite disappointed….
you can switch to the x86-64 version of 1.9.4 which still has the old javascript interpreter.
Yes I’ve heard that and I may just do that. Reverting back to 1.9.3 was a failure as WBPP failed to work. Tried loading the Terminal fix suggested by Juan (from Pixinsight Forum) but didn’t work and WBPP simply was DOA. I’m now back on 1.9.4 (build 1693) and trying to cope with other oddities that have popped up like, (I’m using a MBP M4Max) when scrolling the courser over an open image and getting an unwanted zooming in. Plus, I’m getting strange intermittent STF behavior where it seems to change the image to a state somewhere between linear and screen transfer stretch and can’t go back to a linear state. I’m sure these issues would be classified as “not a bug”, and I’m no software engineer….
Steve Heath · May 27, 2026, 12:17 AM
pfile · May 26, 2026, 10:03 PM
Steve Heath · May 25, 2026, 09:49 PM
Such a shame we have to put up with these issues. Wish I hadn’t “upgraded” to 1.9.4 as it’s been nothing but problems and irritation, especially when some of the Pixinsight software people over at the Pixinsight Forum seem so cavalier about the problems this update has caused. I’m quite disappointed….
you can switch to the x86-64 version of 1.9.4 which still has the old javascript interpreter.
Yes I’ve heard that and I may just do that. Reverting back to 1.9.3 was a failure as WBPP failed to work. Tried loading the Terminal fix suggested by Juan (from Pixinsight Forum) but didn’t work and WBPP simply was DOA. I’m now back on 1.9.4 (build 1693) and trying to cope with other oddities that have popped up like, (I’m using a MBP M4Max) when scrolling the courser over an open image and getting an unwanted zooming in. Plus, I’m getting strange intermittent STF behavior where it seems to change the image to a state somewhere between linear and screen transfer stretch and can’t go back to a linear state. I’m sure these issues would be classified as “not a bug”, and I’m no software engineer….
i’m not really sure why this 1.9.3 problem with WBPP happens even if people delete all the settings files/cache files. really confusing.
unfortunately juan tests on computers that have a fresh OS install and only pixinsight installed. this is convenient for him but clearly not representative of a normal operating environment. i’m sure if he ran PI like the rest of us did he would find bugs and fix them, even if they are not directly caused by his code or Qt. but there’s nothing we can do about that other than to find workarounds and share them amongst ourselves.