×
INDI Library v1.8.6 Released (21 Aug 2020)

August 2020 release of INDI Library v1.8.6 introduces new drivers while providing fixes and improvements to existing devices and core framework.

Imaging with SER video - bad result - PIPP and Autostakkert show strange frames

11 months 1 week ago 11 months 1 week ago by maxthebuilder.
maxthebuilder
Gold Boarder
Gold Boarder
Posts: 368
More
Topic Author
Imaging with SER video - bad result - PIPP and Autostakkert show strange frames #44526
Hello,
Tonight tried to shoot the Moon as SER video capture.
SM 1.4.3 RPI4 with yesterday's updates (KS 3.3.7)
ZWO ASI294MC
0 Gain
16 bit
0.007 sec/frame.

Looked nice in Ekos (in Live View)
Histogram was going up to 30000, not over-saturated.

Tried to open in PIPP. PIPP said there were no frames.
Tried to open in PIPP SER viewer. It said there's a problem with the file and offered to fix it.
Agreed to fix. Below is the result (single frame).
(Autostakkert produces the same result but doesn't complain).


Here's file info reported by ser viewer before fixing:
Filesize: 2147483647 bytes.

Header Details:
 * FileID: LUCAM-RECORDER
 * LuID: 0x0
 * ColorID: 8 (BAYER_RGGB)
 * LittleEndian: 1
 * ImageWidth: 4144
 * ImageHeight: 2822
 * PixelDepth: 16
 * FrameCount: 0
 * Observer:                         Unknown Observer
 * Instrument:                       Unknown Instrument
 * Telescope:                        Unknown Telescope
 * DateTime: 11/09/0119 20:53:00.367145 (0x0085120c44ade39a)
 * DateTime_UTC: 12/10/2019 03:53:00.367185 (0x08d74ec7acf8fd2a)

Error: FrameCount is 0

and after fixing:
Filesize: 2147483647 bytes

Header Details:
 * FileId: LUCAM-RECORDER
 * LuID: 0
 * ColorID: 8 (RGGB)
 * LittleEndian: 1
 * ImageWidth: 4144
 * ImageHeight: 2822
 * PixelDepth: 16
 * FrameCount: 91
 * Observer:                         Unknown Observer
 * Instrument:                       Unknown Instrument
 * Telescope:                        Unknown Telescope
 * DateTime: 11/09/0119 20:53:00.367145 (0x85120c44ade39a)
 * DateTime_UTC: 12/10/2019 03:53:00.367185 (0x8d74ec7acf8fd2a)

Timestamps:
 * Out of order timestamps detected
 * Min timestamp: 18/12/0182 12:04:11.567332 UT
 * Max timestamp: 28/01/0215 16:00:03.673319 UT
 * Min to Max timestamp difference: 11728 days 3 hours 55 min 52.106 s
 * Average frames per second: 8.88175e-8

First time using SER...
Any idea?
Has to be 8 bit? (Edit: same with 8 bit)

Thanks!

Max S.

RPI 4 B (4Gb) with SMate
Nikon D5500 H-a modified. Nikon D5500 stock
AT72EDII, TPO RC6
ZWO ASI294MC Pro, ASI071MC Pro
ZWO ASI120MC-S on ZWO 30F4
ZWO EAF x 2
SW AZ-GTi x 2
SW HEQ5
Attachments:

Please Log in or Create an account to join the conversation.

11 months 1 week ago
maxthebuilder
Gold Boarder
Gold Boarder
Posts: 368
More
Topic Author
Imaging with SER video - bad result - PIPP and Autostakkert show strange frames #44543
The above was done with internal RPI client.
With Windows client there is another problem:
When Ekos tries to save SER file to say C:\video folder it tries C-\Video instead (note dash instead of colon) and of course fails

Max S.

RPI 4 B (4Gb) with SMate
Nikon D5500 H-a modified. Nikon D5500 stock
AT72EDII, TPO RC6
ZWO ASI294MC Pro, ASI071MC Pro
ZWO ASI120MC-S on ZWO 30F4
ZWO EAF x 2
SW AZ-GTi x 2
SW HEQ5

Please Log in or Create an account to join the conversation.

11 months 6 days ago 11 months 6 days ago by DerPit.
DerPit
Platinum Boarder
Platinum Boarder
Posts: 505
Karma: 1
More
Imaging with SER video - bad result - PIPP and Autostakkert show strange frames #44600
The SER recording in 16bit is (at least for ZWO cameras) broken. I had posted about it some time ago, but cannot find it at the moment. It is creating a proper header, but not updating the stream information and dumps wrong data :(
AFAIR, 8bit full frame will work, but only that....

Edi: Here it is

openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI1600+EFW+EAF+ASI290 mini

Please Log in or Create an account to join the conversation.

Time to create page: 0.359 seconds