You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using an Alcor OMEA allsky camera, which seems to be based on a DMK 51AU02.AS camera by The Imaging Source. This camera (and others in its family) has the unfortunate feature that it lies about its pixel format: it reports BA81 (a BGGR pattern) while in fact the correct format would be SGBRG8. This leads to the debayering being done with the wrong pattern and messed-up colours.
Since there's no way to force the correct pattern when the camera itself is wrong, I had to made a fork with an ugly hack that basically just skips the check against the value given by the camera. That works fine for me, so it's not a big deal now. This is more of a FYI.
I'm using an Alcor OMEA allsky camera, which seems to be based on a DMK 51AU02.AS camera by The Imaging Source. This camera (and others in its family) has the unfortunate feature that it lies about its pixel format: it reports
BA81
(a BGGR pattern) while in fact the correct format would beSGBRG8
. This leads to the debayering being done with the wrong pattern and messed-up colours.Since there's no way to force the correct pattern when the camera itself is wrong, I had to made a fork with an ugly hack that basically just skips the check against the value given by the camera. That works fine for me, so it's not a big deal now. This is more of a FYI.
The same issue is dealt by the oaCapture software with a similar hack, https://github.com/openastroproject/openastro/blob/master/liboacam/v4l2/V4L2getState.c#L117
The text was updated successfully, but these errors were encountered: