Ciao Carlo, first of all, sorry for the late reply. Artemis, in the end, is a big archive of several parameters per signal and some advanced filtering...

Hi W4AFK, thanks for asking. We have few updates, yes: the up-to-date version of the new DB is almost ready (no big news, because it's a scheduled upd...

Yes, the project is still Active. The actual version is pretty stable and when few new signals will be available on sigidwiki I'll upload a new versio...

This is quite strange but, to be honest, it depends on several things: first of all is where you placed the package. For instance, the program doesn't...

Thanks Konsumer for reporting this issue. You can try with this legacy version of the dmg: If it still doesn't work out, we'll figure out what's wr...

Hi Andrew, that's right. The problem is solved but not yet released or better: the last master version on GitHub already contains the bugfix (), so if...

The problem has been solved

Thanks Andrew for the detailed report. I've added an official issue on GitHub (). I'll keep you updated

Hi Jan, do you have an error log? What happens when you launch the app? EDIT: I guess that your problem could be related to the wrong architectu...

@wheezye Perfect, thanks again! The version of Artemis for raspberry is now on the main page but the download is temporarily suspended in order to...

I'm pleased to hear that, and I'm sorry I couldn't help you more. You have done a really huge and exceptional job on the ARM processor port. I think t...

First of all, thanks for keeping track of your trials. I'll try to give you some suggestion but I cannot be super helpful since I have no Raspberry Pi...

Hi WheezyE, thank you! We are always happy to hear people that appreciate our work! Back to your issue: it's a bizarre situation when the binary sta...

Thank you for the report. We are investigating the problem...I'll add an official issue to the GitHub repository

This sound really strange...the only problem with the version 3.1.0 was on updating the propagation data. The problem has been fixed in the new 3.2.0....