If you find an issue with PlanetaryImager, or you think of a new feature that can be implemented, you can use the GitHub Issue Manager to raise a new issue.

You can also use the application support and development channel, available both on IRC (#planetaryimager on freenode) and via riot/matrix, by clicking this link.

Frequently Asked Questions

Q: AVI recording doesn't seem to work.

A: AVI recording is not the best way to record images, and it's quite complicated to implement (dealing with media libraries like ffmpeg, compiling the right codec support, and dealing with performances), so right now there is a very minimal support provided by OpenCV. It's likely that AVI support will be entirely removed in one of the next releases. You should always choose SER (which is basically RAW) for recording videos:

SER is supported by the most popular preprocessing and processing tools: I personally recommend PIPP for preprocessing, and Autostakkert for stacking. AVI has the only advantage of producing smaller files (but remember, you pay this by loosing quality). You can still compress a SER file anyway for archiving, or, if you really want an AVI, use a third party application like PIPP to convert the files.

Q: PlanetaryImager crashes when scanning cameras using an ASI Camera. A: There's a known issue when using certain system libraries, most notably on Fedora. The libusb version provided by the sistem is too old or just bugged, and opencv uses libusb too causing a library conflict. This was solved in the most recent binary releases, so using a recent binary package should solve the issue.

Q: PlanetaryImager crashes at startup using an ASI Camera. A: ZWO ASI SDK reads an XML file at startup with some camera settings. On GNU/Linux system this is usually in the $HOME/.ZWO directory. If this file is corrupted, the SDK causes the app to crash. Just delete the directory and try again.