×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

INDI Client Development in C++ Property Problems

  • Posts: 6
  • Thank you received: 0

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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

  • Posts: 421
  • Thank you received: 102
I think when you receive the BLOB (the image) from INDI, one of the fields is "format". So you may have to wait until you actually receive an image before deciding what type it is.

Also, one of the standard INDI properties is CCD_CFA, which has information needed for debayering (if appropriate).

Keep in mind I don't write many INDI clients. I work mostly on the driver side of things. So I might be wrong. :)
Last edit: 1 year 11 months ago by Kevin Ross.
1 year 11 months ago #86666

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

  • Posts: 6
  • Thank you received: 0
Hi Kevin and thanks for your response.

I've just had a look at IBLOB::format but this just contains ".fits" and not the pixel format information such as "RAW-8, RAW16 etc".

Any other ideas?

Amanda.
1 year 11 months ago #86681

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

  • Posts: 421
  • Thank you received: 102
I guess you'll just have to look in the FITS header then, which presumably you're doing anyway in order to decode the image.
1 year 11 months ago #86689

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

  • Posts: 6
  • Thank you received: 0
Thanks Kevin. I appreciate your help.
1 year 11 months ago #86863

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

That's CCD_CAPTURE_FORMAT property
1 year 11 months ago #86890

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

Time to create page: 0.427 seconds