When using ASICAP and my ASI183MM Pro to shoot videos of the moon I run into this issue.
Both PIPP and Autostakkert autodetect the videos as having a bayer RGGB format instead of mono.
Here I attach some examples of this:
This has caused me problems when having the manually choose to process videos as monochrome or colour frames input on PIPP. If I choose monochrome input then the final result introduces fake colour into the images with random blue and red pixels. If I choose colour input then it is fully greyscale (as I would expect from a mono camera), but the image sharpness is much worse! Can someone clarify with me whether a raw frame from a mono camera is treated as a monochrome or colour frame for the purposes of processing?
I dont know if I explained this very well. All I know is that I expected the software to detect the videos as mono but they think it has a bayer pattern...
Thank you in advance,
This is from a document about .SER format descriptions. See here
http://www.grischa-hahn.homepage.t-onli ... %20V3b.pdf
Based off of that information should I not expect to see the colour ID of my mono files as 0 ?
PIPP and also .SER Player read the files as having colour ID 8.
Is there any way to modify a .SER file via a config or something so I can try changing to value to 0 see if that fixes the problem?
We tested the problem you described and it turned out to be a bug. We are sorry for trouble of the bug has caused you. We will fix this bug as soon as possible.
Thanks for your feedback.
ZWO Software Engineer
Since downloading the new and latest version of ASI Studio (on Windows 10 Home) and running ASICAP_V2.0.1(64bit) when capturing videos with the ASI183MM-Pro and ASI120MM-S it is still encoding them with incorrect data about the bayer patterns... It is mono so there should be none.
On the ASI183MM-Pro for 16bit video - PIPP, SER Player, and Autostakkert are recognising them as RGGB bayer matrix, ColorID: 8 (BAYER_RGGB). For 8bit videos they are correctly recognising them as mono/grey.
On the ASI120MM-S for 16bit video - PIPP, SER Player, and Autostakkert are recognising them as GRBG bayer matrix, ColorID: 9 (BAYER_GRGB). For 8bit videos they are correctly recognising them as mono/grey.
It has been almost a year since I highlighted this problem on the forums, and I still cannot use my cameras to shoot 16bit video. Why is this still happening!? It causes very weird stacking artifacts when I try to override the autodetected bayer patterns, so high quality lunar video is still not an option for me.
Please fix this.
Any response on this issue?
Also, what is the meaning and cause of discard frames? When capturing video at full resolution I've noticed I am discarding almost twice as many frames as I am saving for any given period of time.
We have solved the bug. The new version will be released.
The speed of saving files depends on the speed of hard disk writing. Our strategy is to write to the hard disk as fast as possible. If the write speed cannot keep up with the preview frame rate, some frames will be discarded.
ZWO Software Engineer