Something I've noticed.
For a while now, I have not been getting multiple messages per second when decoding on the Mac mini. I used to, but it had stopped.
I know this as I have a program to take the decodes binary files and upload them to a PostgreSQL DB. While importing, it prints out stats. At the end, it shows some totals.
For the win10 box:
Defined Timestamps: 658587 ** Number of timestamps as stated within the .dec file
Total Timestamps: 658587 ** Number of timestamps that the program counted (it better equal the previous one)
Unique Timestamps: 546327 ** Number of unique timestamps (taking into account multiple per second. There can be a max of 2 full messages and a part of a third. Unknown how ADGPS assigns messages to a timestamp).
Unfortunately, I do not have the stats from the Mac mini for this day, as I thought I saved the decodes before starting, but... I did not. I closed ADGPS before realizing this and all that I have is the printed list above.
But I do remember that the three numbers were equal on previous days. Thinking that my program had a bug for not counting right, when run through with the Win10 decodes, it clearly did have multiple per second. There were none > 3 per second as that's a hard coded check and will abort, since it is impossible at 200 bps to have 4 messages.
Chris, can you make a version (for Mac & winders), where we can set the number of decoding threads, from 1 to max? Also, would like an option to pick a set of frequencies to decode. Mainly so I can see if limiting the number of threads makes it more deterministic and also on received signal strength. Not sure how easy this would be.