×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

indi_canon_ccd, CR3 format and Ubuntu 20.04 (Solved)

  • Posts: 10
  • Thank you received: 1
Hello,
this is an issue I could finally solve but for those who may be stuck with it, it's worth sharing.
I have just acquired a Canon EOS Rp and encountered the "famous" "Unsupported file format or not RAW file", due to the CR3 format.
For those who may not have heard before, this comes from an external library (libraw) used by ekos/Indi to convert RAW format, display it and store in the FITS.
Canon used to have .CR2 format in the past but now propose (impose in the latest DSLR) the new .CR3 one.
Unfortunately, the indi_canon_ccd (actually linked to indi_gphoto_ccd binary) is linked with a libraw19 version WHICH DOES NOT UNDERSTAND CR3 format:
<code>(base) deneb-l@astroserv:~$ ldd /usr/bin/indi_gphoto_ccd | grep libraw
libraw.so.19 => /lib/x86_64-linux-gnu/libraw.so.19 (0x00007f8646b10000)</code>
... leading to the error "Cannot open /tmp/indi_xxxxxx: Unsupported file format or not RAW file" in indi canon driver log.
I am really surprised because some of the threads on indilib forum mention that it has been solved months ago.
I have updated kstars and 3rdparty libs (dated of July 2022), trying stable or indinights branch with no success.

I believe this may be due to my distro (Ubuntu 20). The indi repository even if built recently may not use libraw20 in the "focal" packages.
Anyway, to sort this out, I had to:
- git clone LibRaw source code and build (does not change anything, obviously, indi_gphoto_ccd is still linked with libraw version 19)
- git clone the source of libindi-3rdparty and make install the indi-gphoto --> Crash indiserver
- git clone the source of libindi, rebuild all and make install.
--> Works
Now the indi_gphoto_ccd is using my custom latest libraw:
<code>(base) deneb-l@astroserv:~/Projects/build/indi-gphoto$ ldd /usr/bin/indi_gphoto_ccd | grep libraw
libraw.so.23 => /home/deneb-l/source/LibRaw/lib/.libs/libraw.so.23 (0x00007f2fb91fc000)</code>
And kstars/ekos can read my EOS Rp format.
Anyway, it would be interesting to understand why the stable and unstable ppa of indi_gphoto_ccd does not use a more recent version of libraw.
Maybe a mistake or maybe because Ubuntu 20 does NOT have libraw20 official package available:
libraw search in Ubuntu 20 repo
when Ubuntu 22 has:
libraw search in Uuntu 22 repo

Next step will be to upgrade my distribution and see if I can go back to standard ekos/indi packages rather than built myself (will do as soon as I will have free enough disk space).
Hope this can help anyone.
Last edit: 1 year 6 months ago by Deneb-l.
1 year 6 months ago #86012

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

  • Posts: 10
  • Thank you received: 1
... and it turns out that, indeed, Ubuntu version was the one to upgrade in order to install the latest drivers via apt and have everything running smooth without the need to do my rebuild hack.
Of course, my release upgrade totally failed with the "Oh No" message and I lost my installation of kstars and indi.
Just has to re-apply standard procedure:

sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full gsc
sudo apt-get install indi-full kstars-bleeding

as mentioned here: indilib.org/download

I could retrieve all my settings and everything works as expecting now :)

Ps: As a check of the symptoms, now, the "standard" indi_gphoto_ccd has been linked with libraw20:
(base) deneb-l@astroserv:~$ ldd /usr/bin/indi_gphoto_ccd | grep libraw
libraw.so.20 => /lib/x86_64-linux-gnu/libraw.so.20 (0x00007fc986dc3000)
1 year 6 months ago #86016

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

Time to create page: 0.462 seconds