XISF support

XISF support - INDI Forum
  • Posts: 365
  • Thank you received: 114

XISF support was created by nou


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: 55
  • Thank you received: 8

Replied by Paolo on topic XISF support

Thanks a lot, that'd be a really nice feature to have.
Do you plan to add also support for LZ4-HC and byte swapping?
1 year 7 months ago #90021

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

  • Posts: 365
  • Thank you received: 114

Replied by nou on topic XISF support

Yes all Zlib, LZ4 and LZ4-HC with byte shuffling will be supported.
The following user(s) said Thank You: Jasem Mutlaq
1 year 7 months ago #90033

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


×

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

Bi-monthly release with minor bug fixes and improvements

Read More...
  • Posts: 365
  • Thank you received: 114

Replied by nou on topic XISF support


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: 474
  • Thank you received: 168

Replied by Jarno Paananen on topic XISF support

Very nice work! Did a quick test and didn't notice any problems. After enabling compression from INDI control panel the files were roughly half size which is quite welcome :) PixInsight was happy with the files so no complaints from me.
1 year 7 months ago #90323

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

  • Posts: 365
  • Thank you received: 114

Replied by nou on topic XISF support


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: 466
  • Thank you received: 69

Replied by Jerry Black on topic XISF support

Using today's release for 3.6.4 Beta, Build: 2023-02-21T18:07:04Z choosing XISF in my indi_nikon_ccd driver (with a Z7) using NEF (raw), XISF, compression (enabled or disabled), capture Target RAM, kills the driver.
It works when I choose FITS as the storage format.

Not sure if it was ever intended to work on a DSLR driver.

Cheers
1 year 7 months ago #90759

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

  • Posts: 474
  • Thank you received: 168

Replied by Jarno Paananen on topic XISF support

I don't see any fundamental reason why it would not, but it also requires version of INDI with XISF plugin and drivers compiled against that version (no changes required in the driver as such, it's handled by the INDI camera base class). If there is nothing meaningful in the logs, it's worth checking that you have libindixisf.so plugin installed and so on.
1 year 7 months ago #90762

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

  • Posts: 365
  • Thank you received: 114

Replied by nou on topic XISF support

gphoto driver do conversion CR2->FITS. I added XISF to that codepath. It should work with this. github.com/indilib/indi-3rdparty/pull/736
Last edit: 1 year 7 months ago by nou.
1 year 7 months ago #90763

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

  • Posts: 466
  • Thank you received: 69

Replied by Jerry Black on topic XISF support

It looks like github.com/indilib/indi-3rdparty/pull/736 needs libopencv-dev to be added to the build environment.
Last edit: 1 year 7 months ago by Jerry Black.
1 year 7 months ago #90764

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

  • Posts: 466
  • Thank you received: 69

Replied by Jerry Black on topic XISF support

So for me at least, this doesn't work. Probably my build environment, or just not doing the correct things. I have downloaded the nightly PPA and separately tried a build from source.

My log file is attached. The telescope isn't attached, I start with a FITS capture and then switch to a XISF.
The FITS capture works
2023-02-25T11:47:00.712 AST INFO ][ org.kde.kstars.ekos.capture] - "Captured /home/blackastro/Images/garbage/garbage/Light/LPR/garbage_2023-02-25T11-46-59_Light_LPR_008.fits"

Note that after choosing XISF, the file path appears to be wrong

[2023-02-25T11:47:45.124 AST DEBG ][ org.kde.kstars.ekos.capture] - Preparing capture job "/home/blackastro/Images/garbage/garbage/Light/LPR/garbage_\\d\\d\\d\\d-\\d\\d-\\d\\dT\\d\\d-\\d\\d-\\d\\d_Light_LPR" for execution.
the driver crashes at this point.

Is this just me and evidence that my build is wrong? or is there something more here?
Thanks
1 year 6 months ago #90864
Attachments:

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

  • Posts: 2885
  • Thank you received: 819

Replied by Rob Lancaster on topic XISF support

I just added a Craft formula after Jasem told me about the new libxisf. This will allow building on MacOS and Windows.

invent.kde.org/packaging/craft-blueprint...1b12692fd431c7c438e8
1 year 6 months ago #90879

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

Time to create page: 1.017 seconds