Test build for PSK Reporter improvements

[Mooneer Salem]

Hi all,

I've been working on improvements for the PSK Reporter feature in FreeDV, mainly to make it more reliable than it has been. I just uploaded a test build with these changes at https://www.dropbox.com/sh/044azug3aj6zsnt/AAAh573m0tv-MGweRa0mt-1ba?dl=0. A few notes:

1. This is incompatible with previous versions of FreeDV in that a completely different encoding scheme is now being used for the text field. In other words, if PSK Reporter is enabled (in Tools->Options), this version will be unable to decode any text sent by users running earlier versions.

2. As with earlier versions, both sides must have PSK Reporter enabled in order for FreeDV to properly decode the received text (and thus report the other person's callsign).

For reference, this build contains the following work:

https://github.com/drowe67/codec2/pull/209

https://github.com/drowe67/freedv-gui/pull/156

Let me know if you have any questions or run into issues.

Thanks,

-Mooneer K6AQ

[Mooneer Salem]

Hi all,

Here's a followup build that eliminates the requirement of using Hamlib to enable PSK Reporter capability in favor of a "Report Frequency" field on the lower right of the main window: https://www.dropbox.com/sh/snzs5q792lfjsn2/AAB9LCfa7MhnLfiRbRdBmHOKa?dl=0. Of course, this field will auto-update on start/switching between TX and RX if you do have Hamlib enabled. This new field will also turn red if the input is invalid, which indicates that reporting will not occur. As always, let me know if you have any questions or run into any issues.

Thanks,

-Mooneer K6AQ

[Mooneer Salem]

Hi all,

Turns out that previous build had an issue on Windows. https://www.dropbox.com/sh/0dwlherxbxbdr04/AADjcYRQA-3rtiGz4qXmNdX4a?dl=0 should resolve that particular issue. Sorry for the inconvenience.

Thanks,

-Mooneer K6AQ