Yes. In the meantime I have opened a case at ZWO. It seem to be a bug that shows up at some few installations. I doubted my sanity...
ASIAIR Beta v2.0.0
- Edited
andybutt I tried with guiding dark frames turned on and it actually made guiding worse.
Hmmm, when I tried it, turning on dark frames has not been worse than not turning it on (see my post in this thread from last week).
One thing that you must make sure is that there is no light leak when you cap the guide scope while taking the dark frames, if you don't remove the camera from the guide scope to take the dark frames. You can try testing if light leak is a problem by taking the dark frames with the camera off the guide scope and capped.
ZWO, in pursuit of their "Simple as 1,2,3" slogan, do not give the user the ability to inspect the dark frames.
When I did my guiding dark frames, I simply capped my guide scope (having previously tested against light leaks), but I also covered my guide scope with one of these focusing hoods to further prevent stray lights from reaching the camera:
https://www.amazon.com/gp/product/B01M9B4993
Chen
- Edited
Kring For me the portrait orientation is just for the first "splash" screen. That is a little bit strange. After that everything is in landscape mode how it is supposed to be.
On the MBP, the splash screen is in portrait but upright, i.e. readable... on the iPad it is rotated to fit the screen.
Running the app without being connected to the ASIAIR Pi cannot work, since most of the program is running on the Pi, AFAIK. The Asiair App is like a VNC or some type of remoter interface. Image processing, stacking etc is all happening on the Pi and not on the iDevice. Except for the SkyAtlas GUI. That's running locally.
So far I like the new version 2.0.0. Indeed, one has to get used to the new layout and location/menu of features.
One minor thing, when clicking on the Moon in SkyAtlas it selects a background object, rather than the Moon. Have to try several times until the Moon is actually being selected. Then it tries plate solving with the Moon covering 95% of the FoV, which obviously is failing. These are very minor things.
The histogram is very small. I prefer the triangular indicators/sliders rather than the elongated and wide buttons.
I feel bad "complaining". This new version is great. Everything I have tested so far works. The AF GUI is cleaner now as well. The star image is in the top left corner and not on the graph itself anymore. Much nicer this way.
I cannot test the Guiding Mode. Still having the issue that the Avalon StarGO2 Mount controller is not fully supported by the ASIAIR. Very annoying. This is an issue that has to be fixed between Avalon Instruments and ZWO directly.
- Edited
Obs30 On the MBP, the splash screen is in portrait but upright, i.e. readable... on the iPad it is rotated to fit the screen.
Yep, macOS reorients the iPad display automatically on its display (as any reasonable GUI should :-).
If my suspicions are correct, that splash screen is not really an ASIAIR splash screen. ASIAIR is just one of the entry points. I think ZWO thinks that we are gullible enough to use some social media stuff they have come up with. Just like Facebook, I won't be using that "community" nonsense (people are just going to post out of focused images :-).
Too bad that unlike DECsystem-20, macOS has no way to freeze a program, so we can always start a frozen copy at the ASIAIR level.
Chen
Kring Now that you are expanding the platform, you need to consider and option of having the ASIAir proxy through a DDNS so that users can remotely access their AA from off local wifi. E.g. I am out to dinner and I want to see if I’m still tracking and taking photo’s. The ability to access the AA from anywhere would be a huge feature.
I'm currently doing just that using a VPN-service of my router provider. The router sends the public IPv4 to the provider and he maps this IP to my IPSec VPN-address. This allows me to connect to my home network using the same settings from my phone (independent of the dynamic IP). Works perfectly.
- Edited
Obs30 How did you do this? I installed the v2.0.0. Then moved it into another folder on the desktop. Then trying to install 1.9.2... I get an error message:
Weird.
Check your Applications folder, see if the iOS app is still in there... I do know that macOS locks downloaded iOS apps so that you can copy but not delete (from Applications folder) unless you give it admin priviledge.
My own "account" is also an admin account (although I still need to sudo for critical stuff), and it allows me to remove the copy in the Applications folder only after I give it my password.
My squirreled-away folder looks like this (I renamed the apps):
(Yes, I have a v1.5.1 ipa squirreled away :-). My own wayback machine :-).
By the way, someone else complained about the new ASIAIR icon. You can change the app icon in both macOS and iOS quite easily. Change it even to the turd emoji if you wish :-). E.g.:
FWIW, I think the original icon is the cleanest -- most Apple like.
Chen
So, I've found a problem why TestFlight is not installing ASIAIR 2.0.0 on macOS Ventura Beta. The log below, maybe @tech@zwo will find it useful.
[TFUA9D320FC/com.ZWO.ASIAIR:1367782034] Failing installation after receiving error: Error Domain=IXUserPresentableErrorDomain Code=14 "Unable To Install “ASIAIR”" UserInfo={NSLocalizedDescription=Unable To Install “ASIAIR”, NSLocalizedFailureReason=This app cannot be installed because its integrity could not be verified., NSLocalizedRecoverySuggestion=Failed to verify code signature of /var/db/appinstalld/Library/Caches/com.apple.mobile.installd.staging/temp.B0WedV/extracted/Payload/ASIAIR2.app : 0xe800802a (The application's signature is valid, but a provisioning profile can not be found that matches this version.), NSUnderlyingError=0x12d708df0 {Error Domain=MIInstallerErrorDomain Code=13 "Failed to verify code signature of /var/db/appinstalld/Library/Caches/com.apple.mobile.installd.staging/temp.B0WedV/extracted/Payload/ASIAIR2.app : 0xe800802a (The application's signature is valid, but a provisioning profile can not be found that matches this version.)" UserInfo={LibMISErrorNumber=-402620374, LegacyErrorString=ApplicationVerifi
gutaker i don't run the Ventura Beta but i have seen others experiencing the problem that you are mentioning as well: for example see https://www.reddit.com/r/MacOSBeta/comments/w4ty9y/cant_install_testflight_apps/
Looks like a bug in the macOS Beta.
- Edited
w7ay Got it to work.... Had to use intermediate copies on a USB thumb drive. Even when creating a duplicate of v1.9.2 and copying that to another directory, it was overwritten by the TestFlight v2.0.0. Never seen that before. I used cmd-drag&drop and cmd-C/cmd-V, which should create an actual copy and not symbolic links. Maybe next time I try copying via terminal window... Anyway, now I have the two separate versions.
Stupid question... Did anyone of you try to use the SkyAtlas to go to M2? In my case it always goes to the wrong DEC coordinate, the exact same value but positive: +0°43' instead of -0°43'.
- Edited
Obs30 the exact same value but positive: +0°43' instead of -0°43'.
I don't know whether to laugh, or to cry :-).
By the way, it just occurred to me that perhaps the ASIAIR multiple copies had worked for me right off the bat is because the folder I have created for it is on a different volume from my main Applications folder.
I have 6 SSD (a couple of them are NVMe) attached to my Mac Studio. The reason is to segregate a lot of my work, and also to keep the main drive as small as poosible for when I migate to newer Macs. My music folder is on an external drive, my astronomy sub frames are on another external SSD, the processed frames are on yet a different SSD, and the folder used by AstroPixelProcessor is linked to an NVMe Thunderbolt drive (I have 128 GB of RAM [not typo] in the Mac Studio, but AstroPixelProcessor needs even more temporary memory than that :-).
One of my external drives is named "Local," and another is named "Etc." You should get a laugh out of that as a Unix user :-).
Chen
- Edited
w7ay Wow... you are very well organized 
Yes, I have a few of those external drives... Hard to keep track what's on which though. 
And of course I am admiring that Studio Mac!
I guess that's the reason why the link between the application and its copy was "broken". At first I had used another folder on the same volume. You cannot trick APFS that easily. With the thumb drive the "problem" was gone. Feature or bug...
I would still like to see if anyone else has this issue with slewing to M2 (the globular cluster, not the equally dense CPU/GPU combo). I guess I will need to report it to ZWO directly via TestFlight.
Obs30 after you get used to that GUI... if ever ;-)
Hey, the developer is an astrophysicist, not a computer scientist :-).
Works well if you are using the default workflow, though. But if you have to do color separations, it is a pain. There is also no global cropping state. You need to go into tools to crop the calibration files, and then do the same to the subframes.
What I like is the star color tools. One of the few apps that actually try to match Planck.
Chen