19 June 2021: Our upload server https://upload.astropixelprocessor.com/ has been migrated successfully to our new office with higher upload and download speeds (nearly 10MByte/sec up/down ) ! We now have 1 general upload user called: upload with password: upload. The users upload1 - upload5 have been disabled.
31 May 2021: APP 1.083-beta2 has been released ! APP 1.083 stable will follow soon afterwards. It includes a completely new Star Reducer Tool, New File Saver Module, Improved Comet registration and much more, check the release notes here!
[Solved] Division by Zero Exception when processing Pentax DNG files
i tried the long awaited feature to process DNG files from my Pentax K5 DSLR with APP 1.075 beta6, but anytime i got an Division by Zero Exception in the module MedianDPAapproachFilterDouble. The exception occurs in the calibrate module when processing darks and bias files and also in the star analyse module when processing lights.
kind regards from Düsseldorf/Germany
Dear Heiner @djones,
Thank you for sharing this issue.
Chances are the error is not related to APP's ability to process Adobe DNG frames, but due to an issue with your data. I did test the DNG conversion on a lot of Pentax camera models successfully.
I will be happy to sort this out quickly and have a look at your data. Can you upload the data that gives the problem including calibration data?
Which Adobe DNG converter version did you use? The most recent one?
You can upload the data here:
login and password : appuser
Make a directory with your name and upload some frames and I will have a look.
thanks for your prompt response. As proposed i uploaded some sample pictures to your file station. These dng files came native from my Pentax K5. With Pentax there is no need for Adobe DNG Converter.
Hope, you can fix this
Hi Heiner @djones,
Thank you very much for uploading your Pentax frames 😉
Indeed, there was an issue with the metadata that the Pentax camera stored in the DNG metadata. It's a bit different from how Adobe DNG converter would do it. But luckily, it was a minor issue, so I have fixed it and it will work in APP 1.075 which I will release tomorrow !
Thanks for your support 😀