This does not change the behavior of the app but resolves a somewhat nebulous issue with video capture and/or playback with certain applications on particular hardware configurations. Reseting gamma curve more proactively on quit, instead of counting on macOS to do it for us.
(Gamma Control uses the serial number to identify screens when possible.)
I'd then be able to install whatever packages are required, download the source code and build a version to debug. Well, I guess briefly the ideal would be to install a copy of the OS on a different SD card (so whatever I mess about with can't break anything for you and can just be ditched afterwards) and boot the RPi from that with the camera connected and then make whatever arrangements are necessary for me to be able to connect to the RPi using ssh and have root access.
Given I am currently confined to quarters anyway I have time on my hands. Of course if I would be more of a hinderance I quite understand How comfortable is comfortable? I am not an expert in Linux but am pretty comfortable, with guidance at least, doing most things on most OS's via command lines or anything else and would be happy to help if at all I can. Otherwise I'll have to look at what logging I can add to the code to help debug this problem in the next release. If anyone can do that for me then that's great, though it's probably only really practical if you're really comfortable with Linux. Unfortunately there's no way for me to work on that directly without access to the specific camera in question. Or perhaps there's some issue in the SDK that means they won't work in streaming mode (which is different from how INDI uses them as far as I recall), but I struggle to believe that. My code doesn't have a clue what camera is actually connected - it just asks the Altair SDK for frame size, what controls are available and so on - so if it works for one then in theory it ought to work for all, but perhaps I have subconsciously made some assumption that just isn't true for these particular cameras. The exception is one that has had support dropped from the Altair SDK and therefore won't work anywhere (though as previously mentioned I have hacked support for it, in a fairly ugly way).
The Altair cameras I can test against the latest Astroberry generally work. Well, I'm at a bit of a loss to explain this now. It doesn't make for an easy time debugging problems. On my development system where I usually have all the SDKs installed at the same time, at least one camera I have is recognised as four different brands (with a different camera name in each case). It's possible that the older Altair SDK used to recognise and work with some Opticstar-branded cameras, too. Actually it is even worse than that, as some use their own IDs for some cameras and Touptek's for others which can result in some surprising behaviour.įor instance, at least one of the Altair-branded cameras is no longer supported by the Altair SDK (it used to be in older versions), but is recognised by the current SDKs provided by Touptek for several other brands and works perfectly when used that way, though the SDK will tell you it's a completely different camera. However some (but not necessarily all) of the vendors of cameras manufactured by Touptek, and there are quite a few even just in the field of astronomy, use different USB vendor and product IDs. Altair cameras are rebranded Touptek so I don't think differentiating them using "genuine" is 100% accurate.