Luke Berndt

Ah - This looks like it is Phase 2 audio... it is possible that something could be screwed up for Phase 2.

@johnrockie Just to double check - you were on version 4.0.2? That version fixed some duplicate call errors. If I am hearing it right there was some overlap on the...

Unfortunately it is probably something I can't do. Running that search on the DB would probably grind it to a halt if it was done a lot... I will can...

I will look through it tonight. I don't have an AirSpy, so I was just using code that someone submitted. It maybe that the way the driver handles gain has...

Hmm... I am making the same calls as GQRX. If you check here, the values should be configurable: https://github.com/robotastic/trunk-recorder/blob/3e4ed87eac7534e4584569af3320576f02c79537/trunk-recorder/main.cc#L302 Maybe try including a `gain` setting too. If one is not...

I could be wrong, but I believe Gain is still a valid setting on the AirSpy. The OsmoSDR driver maybe mapping it to one of other gain settings. The other...

I reverted this change - the detailed gain was clobbering the general gain and setting it to zero. I think I have to add tests around the detailed gains before...

Ok - give the latest release on the master branch a try. All of the gain settings only get applied if they are set. Try leaving Gain unset, it looks...

Ah! So the problem is actually around the Error / PPM. Error is specified as the amount of Hz the tuning is off by. This is the more reliable way...

Agreed! What would be the ideal flow? Should a single transmission that is part of a call mark the whole call as being emergency? This seems decent, so it wouldn't...