For 64bit Raspbian yes.

Thank you very much for posting the apt install command line to enable armhf libraries needed for FireCapture on Pi 64-bit ubuntu!

Unfortunately I still get an error for a missing library here:
mpi:/usr/share/FireCapture_v2.6_armhf $ ./start.sh
Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/share/FireCapture_v2.6_armhf/jre/lib/arm/libawt_xawt.so: libXi.so.6: cannot open shared object file: No such file or directory

I've tried fixing this by doing
sudo apt install libXi:armhf

But apt can't find any such package:
E: Unable to locate package libXi:armhf

Any advice about how to resolve this?

Lot of problems with FireCapture on Raspberry PI. As this software is not part of INDI or KStars/EKOS, perhaps you will find more support on its own group groups.io/g/firecapture/topics

Hi,

you should not use capital X , and forgot the 6

After al lot of searching this solved it for me: sudo apt install libxi6:armhf

Regards,

Paul

Paul,

Perfect -- that was it! Thanks so much.

Scott

So I’ve installed FC on my SM 1.5.5. I had to change the permissions and also ran into the heap size issue. I’ve got it to where FC will run and recognize my QHY camera. But it is extremely slow as other people have noticed. It’s not usable it’s so slow. Has anyone figured this out? I haven’t ran an apt update, as this can occasionally mess up SM itself. The libxi6 is updated to the latest.

Hi there,

for everyone who has problems with the speed of Firecapture in Stellarmate.
Here is my solution:

sudo nano /boot/config.txt
change "dtoverlay = vc4-fkms-v3d"
in:
# dtoverlay = vc4-fkms-v3d

3D support is deactivated and the system works with the old (native) driver. This relieves the system and allows Firecapture to run faster.


Tino

On my system (after SM 1.5.5 update?) dtoverlay = vc4-fkms-v3d is already commented out.
Yes, FireCapture is more responsive now but still sluggish.

Giving up on FireCapture.
For my limited planetary needs, with its latest improvements (and coming too), Ekos is good enough for me.

Perhaps a naive question, but how hard would it be to integrate Planetary Imager into Ekos?
That is a dynamite platform for planetary work with monochrome or a OSC camera. Unfortunately, with my feeble Linux skills I have so far not been able to compile it on the Pi4, although it ran on the original Pi3B+.
If that could be integrated into Ekos, it would be a mind-blowing addition to the system.
Jo

planetaryimager.gulinux.net/

As far as I understand there is a plan to add planetary to Ekos: www.indilib.org/forum/ekos/8292-ekos-planetary-imaging.html

I'm running 1.5.6 and dtoverlay = vc4-fkms-v3d is in there twice, once commented out.
FC V2.7 beta

I've commented the first mention of it out too and now I have freed another 20-30% of CPU usage
It can't cope with the full frame of my ASI1600MM but it can with BIN2x2 or a small ROI
Will experiment with the moon tonight.

Note: I have found that vc4-fkms-v3d is necessary to use a second HDMI display.