FreeDV v1.9.2 released

135 views
Skip to first unread message

Mooneer Salem

unread,
Sep 14, 2023, 1:55:10 AM9/14/23
to freetel...@lists.sourceforge.net, digita...@googlegroups.com, ham-radio-...@groups.io
Hi all,

FreeDV version 1.9.2 has been released, which contains the following:

1. Bugfixes:
    * Initialize locale so that times appear correctly. (PR #509)
    * Fix issue with Voice Keyer button turning blue even if file doesn't exist. (PR #511)
    * Fix issue with Voice Keyer file changes via Tools->Options not taking effect until restart. (PR #511)
    * Eliminate mutex errors during Visual Studio debugging. (PR #512)
    * Add timeout during deletion of FreeDVReporter object. (PR #515)
    * Fixes bug preventing display of reporting UI if enabled on first start. (PR #520)
    * Adjust vertical tick lengths on waterfall to prevent text overlap. (PR #518)
    * Adjust coloring of text and ticks on spectrum plot to improve visibility when in dark mode. (PR #518)
    * Resolve issue preventing proper device name display in Easy Setup for non-English versions of Windows. (PR #524)
    * Fix intermittent crash on exit due to improperly closing stderr. (PR #526)
2. Enhancements:
    * Add tooltip to Record button to clarify its behavior. (PR #511)
    * Add highlighting for RX rows in FreeDV Reporter (to match web version). (PR #519)
    * Add Distance column in FreeDV Reporter window. (PR #519)
    * Add support for sorting columns in FreeDV Reporter window. (PR #519)
    * Allow use of FreeDV Reporter without having a session running. (PR #529, #535)
    * Adds support for saving and restoring tab state. (PR #497)
      NOTE: Requires 'Enable Experimental Features' to be turned on, see below.
    * Adds configuration item allowing optional use of experimental features. (PR #497)
      This option is called "Enable Experimental Features" in Tools->Options->Debugging.
    * Add FreeDV Reporter option to have the band filter track the current frequency. (PR #534)
3. Build system:
    * Upgrade wxWidgets on binary builds to 3.2.2.1. (PR #531)
    * Fix issue preventing proper generation of unsigned Windows installers. (PR #528)
    * Update code signing documentation and defaults to use certificate provider's token instead of our own. (PR #533)
4. Cleanup:
    * Remove unneeded 2400B and 2020B sample files. (PR #521)

More information and download links can be found at https://github.com/drowe67/freedv-gui/releases/tag/v1.9.2.

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 15, 2023, 7:23:56 PM9/15/23
to digita...@googlegroups.com

Hi Mooneer,

With this release it takes much longer (20 seconds) for the waterfall starts after I click the start button.
That is with the MAC version and compared with version 1.9.0 for the same OS.

Bob VE3TOK

--
You received this message because you are subscribed to the Google Groups "digitalvoice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digitalvoice...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digitalvoice/CAAzDfxOBqbiOAuzxYhmeM-Myj2aUcfqeg-SF41sY_%2B47UYYxyA%40mail.gmail.com.
-- 
There is nothing permanent except change
 
-Heraclitus

Mooneer Salem

unread,
Sep 15, 2023, 8:10:32 PM9/15/23
to digita...@googlegroups.com
Hi Bob,

I took a quick look and I'm not sure anything changed that would cause that to happen. A few questions:

1. Does 1.9.1 also show this?
2. If you push Stop and then push Start again, does it still take ~20 seconds to fully start?
3. What version of macOS are you running? (I typically test with the latest stable version on a 2019 MBP and an M1 Mac Mini, which as of this writing is macOS Ventura 13.5.2.)

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 16, 2023, 3:18:34 PM9/16/23
to digita...@googlegroups.com

Hi Mooneer,

Yes, 1.9.1 also show this and I made a mistake in my previous email as it also shows up in 1.9.0 and earlier.
Went even back to 1.8.11, same thing. I found out that the problem is caused by CAT, it doesn't happen if
I switch to serial port PTT (CAT off). OS version is Catalina 10.15.7 as it is an older MacBook Air. The settings
for CAT are Hamlib Net rigctl, so over tcp/ip. Push stop and push start again makes no difference in time.
This issue doesn't happen in Linux (Ubuntu) with the same setup in my other PC and the same HL-2 rig and
SparkSDR.

73,

Bob VE3TOK

Mooneer Salem

unread,
Sep 16, 2023, 10:19:16 PM9/16/23
to digita...@googlegroups.com
Hi Bob,

It *shouldn't* matter but something that might be worth a shot is to use "127.0.0.1:..." instead of "localhost:..." for the serial port/host field. It might also be worth trying different SDR clients if possible as some may respond to CAT control better than others on your hardware.

(BTW it looks like the Hamlib library was last upgraded on FreeDV version 1.8.9 to version 4.5.5, in case that matters. Trying 1.8.8 or earlier could be an option, too, just to see if the Hamlib version upgrade is a factor.)

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 18, 2023, 1:05:52 PM9/18/23
to digita...@googlegroups.com

Hi Mooneer,

With version 1.8.8 the delay is 10 seconds after I press START, so 50% less compared with version 1.9.2.
127.0.0.1 is always used here instead of localhost.

Bob VE3TOK

On 2023-09-16 22:18, Mooneer Salem wrote:

In version 1.8.8 the delay is 10 seconds after I press START, so 50 % less compared with version 1.9.2.

I always used 127.0.0.1 instead of localhost.

Mooneer Salem

unread,
Sep 19, 2023, 2:21:48 AM9/19/23
to digita...@googlegroups.com
Hi Bob,

It might be worth going to Tools->Options->Rig Control and checking "Use USB/LSB instead of DIGU/DIGL." If that doesn't make a difference, unchecking "Enable frequency and mode changes" may also help. The rig control stuff may be adding additional overhead compared to prior versions (and DIGU/DIGL especially may cause issues on radios or SDR programs that don't have separate digital modes).

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 20, 2023, 4:48:42 PM9/20/23
to digita...@googlegroups.com

Hi Mooneer,

The best here is to leave them both unchecked as with that it will be 10 seconds before the waterfall
appears after start is pressed, 50% less. Stop works right away with those settings.

73,

Bob VE3TOK

Mooneer Salem

unread,
Sep 20, 2023, 7:16:37 PM9/20/23
to digita...@googlegroups.com
Hi Bob,

I'm glad the suggested changes helped! I suspect you just need "Enable frequency and mode changes" unchecked and not necessarily "Use USB/LSB instead of DIGU/DIGL", but having the latter unchecked as well shouldn't hurt. In any case, it may very well just be something related to running on an older system, though it would be good to know if other ham radio related applications have significant startup delays on your system too.

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 20, 2023, 10:20:15 PM9/20/23
to digita...@googlegroups.com

Hi Mooneer,

If I leave "Use USB/LSB instead of DIGU/DIGL" checked and  "Enable frequency and mode changes" unchecked I will have 20 seconds delay.
This is why both are unchecked to get 10 seconds delay. I also use FLDIGI on the MAC with the same setup and don't have these delays at all.

73,

Bob VE3TOK

Mooneer Salem

unread,
Sep 22, 2023, 3:08:31 PM9/22/23
to digita...@googlegroups.com
Hi Bob,

I'm actually able to duplicate this with my own HL2 and SparkSDR as well on a newer machine (2019 MBP running macOS 13.5.2). Based on the debug output it seems like it's potentially hamlib-related:

Setting callsign to K6AQ
rig_init: rig_model=Hamlib NET rigctl
rig_init: rig does not have tx_range!!
rig_init: rig has VFO_A
rig_token_lookup called for rig_pathname
rig_confparam_lookup called for rig_pathname
rig_set_conf called
rig_confparam_lookup called for 1073741834
rig_set_conf: rig_pathname='localhost:51111'
rig_token_lookup called for ptt_pathname
rig_confparam_lookup called for ptt_pathname
rig_set_conf called
rig_confparam_lookup called for 1073741855
rig_set_conf: ptt_pathname='localhost:51111'
 1:rig.c(817):rig_open entered
rig_settings_load_all: settings_file (/Users/mooneer/.config/hamlib_settings): No such file or directory
rig_open: cwd=/Users/mooneer/devel/freedv-gui/build_osx
rig_open: /Users/mooneer/devel/freedv-gui/build_osx/hamlib_settings does not exist
connect to localhost:51111 failed, (trying next interface): Network error 61: Connection refused
  2:rig.c(7481):async_data_handler_start entered
  2:rig.c(7488):async_data_handler_start returning(0)
rig.c(254):add_opened_rig returning2(0)
rig_open: 0x7f7f0380f41c rs->comm_state==1?=1
  2:rig.c(6084):rig_get_powerstat entered
netrigctl_get_powerstat called
netrigctl_transaction: called len=15
network_flush called
read_string_generic(): Timed out 10.004 seconds after 0 chars, direct=1

Weirdly, PTT and CAT control seemed to work after the ~20 second delay (I noticed SparkSDR switching to 14.236 MHz from the 14.094 MHz it started at). Maybe we can just reduce the timeout if all else works fine otherwise. 

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 22, 2023, 11:05:18 PM9/22/23
to digita...@googlegroups.com

Hi Mooneer,

Thanks for the update, luckily you could duplicate it. I used netcat to connect to port 51111 as a test.
It was refused but right away after that it says connected, so yes maybe it is hamlib.

73,

Bob VE3TOK

Mooneer Salem

unread,
Sep 22, 2023, 11:08:34 PM9/22/23
to digita...@googlegroups.com
Hi Bob,

I dug into this further and I'm leaning towards it being a SparkSDR issue. It seems that SparkSDR gets a "get_powerstat" command (which Hamlib itself is sending, not FreeDV) and simply does nothing, only continuing after Hamlib itself times out on getting a response for that command. Hamlib also sends this command for mode queries, which is probably why both checkboxes got the startup delay down to 10 seconds from ~20.

Hamlib output (using rigctl tool):

Mooneer6MBP2461:bin mooneer$ ./rigctl -Z -vvvv -m 2 -r localhost:51111

2023-09-22T19:55:08.886180-0800: rigctl.c(445) Startup: ./rigctl -Z -vvvv -m 2 -r localhost:51111

2023-09-22T19:55:08.886224-0800: rigctl Hamlib 4.5.5 Apr 05 11:43:08Z 2023 SHA=6eecd3

2023-09-22T19:55:08.886233-0800: Report bugs to <hamlib-d...@lists.sourceforge.net>


2023-09-22T19:55:08.886255-0800: initrigs4_dummy: _init called

2023-09-22T19:55:08.886266-0800: rig_init: rig_model=Hamlib NET rigctl

2023-09-22T19:55:08.886299-0800: rig_init: rig does not have tx_range!!

2023-09-22T19:55:08.886319-0800:  1:rig.c(817):rig_open entered

2023-09-22T19:55:08.886412-0800: rig_settings_load_all: settings_file (/Users/mooneer/.config/hamlib_settings): No such file or directory

2023-09-22T19:55:08.886460-0800: rig_open: cwd=/Users/mooneer/devel/freedv-gui/hamlib/bin

2023-09-22T19:55:08.886484-0800: rig_open: /Users/mooneer/devel/freedv-gui/hamlib/bin/hamlib_settings does not exist

2023-09-22T19:55:08.889574-0800: connect to localhost:51111 failed, (trying next interface): Network error 61: Connection refused

2023-09-22T19:55:08.889787-0800:   2:rig.c(7481):async_data_handler_start entered

2023-09-22T19:55:08.889811-0800:   2:rig.c(7488):async_data_handler_start returning(0) 

2023-09-22T19:55:08.889826-0800: rig.c(254):add_opened_rig returning2(0) 

2023-09-22T19:55:08.889835-0800: rig_open: 0x7fe4f900bc1c rs->comm_state==1?=1

2023-09-22T19:55:08.889847-0800:   2:rig.c(6084):rig_get_powerstat entered

2023-09-22T19:55:08.889863-0800: netrigctl_get_powerstat called

2023-09-22T19:55:08.889874-0800: netrigctl_transaction: called len=15

2023-09-22T19:55:08.889887-0800: network_flush called

2023-09-22T19:55:18.892746-0800: read_string_generic(): Timed out 10.002 seconds after 0 chars, direct=1

2023-09-22T19:55:18.892773-0800: netrigctl_get_powerstat: PS command failed (ret=-5) so returning RIG_POWER_ON

2023-09-22T19:55:18.892784-0800:   2:rig.c(6109):rig_get_powerstat returning(0) 

2023-09-22T19:55:18.892795-0800:   2:netrigctl.c(261):netrigctl_open entered

2023-09-22T19:55:18.892804-0800: netrigctl_transaction: called len=9

2023-09-22T19:55:18.892815-0800: network_flush called

2023-09-22T19:55:18.893375-0800: netrigctl_open: vfo_mode=0

2023-09-22T19:55:18.893395-0800: netrigctl_transaction: called len=12

2023-09-22T19:55:18.893412-0800: network_flush called

2023-09-22T19:55:18.894832-0800:   2:netrigctl.c(652):netrigctl_open returning(0) 

2023-09-22T19:55:18.894852-0800:   2:rig.c(2928):rig_get_vfo entered

2023-09-22T19:55:18.894875-0800: netrigctl_get_vfo called

2023-09-22T19:55:18.894883-0800: netrigctl_transaction: called len=2

2023-09-22T19:55:18.894893-0800: network_flush called

2023-09-22T19:55:18.895296-0800: rig_parse_vfo called

2023-09-22T19:55:18.895343-0800:   2:rig.c(2991):rig_get_vfo returning(0) 

2023-09-22T19:55:18.895362-0800: rig_get_freq(2034) called vfo=VFOA

2023-09-22T19:55:18.895389-0800: rig.c(2043) vfo=VFOA, curr_vfo=VFOA

2023-09-22T19:55:18.895420-0800: rig_get_freq(2130): vfo_opt=0, model=2

2023-09-22T19:55:18.895432-0800: netrigctl_get_freq called, vfo=VFOA

2023-09-22T19:55:18.895447-0800: netrigctl_transaction: called len=2

2023-09-22T19:55:18.895459-0800: network_flush called

2023-09-22T19:55:18.896067-0800: rig_get_freq(2034) called vfo=VFOB

2023-09-22T19:55:18.896093-0800: rig.c(2043) vfo=VFOB, curr_vfo=VFOA

2023-09-22T19:55:18.896121-0800: rig_get_freq(2130): vfo_opt=0, model=2

2023-09-22T19:55:18.896131-0800: netrigctl_set_vfo called

2023-09-22T19:55:18.896139-0800: netrigctl_set_vfo: cmd='V VFOB

'

2023-09-22T19:55:18.896147-0800: netrigctl_transaction: called len=7

2023-09-22T19:55:18.896158-0800: network_flush called

2023-09-22T19:55:18.896609-0800: netrigctl_get_freq called, vfo=VFOB

2023-09-22T19:55:18.896637-0800: netrigctl_transaction: called len=2

2023-09-22T19:55:18.896654-0800: network_flush called

2023-09-22T19:55:18.897083-0800: netrigctl_set_vfo called

2023-09-22T19:55:18.897105-0800: netrigctl_set_vfo: cmd='V VFOA

'

2023-09-22T19:55:18.897118-0800: netrigctl_transaction: called len=7

2023-09-22T19:55:18.897132-0800: network_flush called

2023-09-22T19:55:18.897592-0800:   2:rig.c(5130):rig_get_split_vfo entered

2023-09-22T19:55:18.897635-0800: netrigctl_get_split_vfo called

2023-09-22T19:55:18.897657-0800: netrigctl_transaction: called len=2

2023-09-22T19:55:18.897701-0800: network_flush called

2023-09-22T19:55:18.898083-0800: rig_parse_vfo called

2023-09-22T19:55:18.898107-0800:   2:rig.c(5195):rig_get_split_vfo returning(0) 

2023-09-22T19:55:18.898116-0800: rig_open(1380): Current split=0, tx_vfo=VFOA

2023-09-22T19:55:18.898125-0800:   2:rig.c(2453):rig_get_mode entered

2023-09-22T19:55:18.898169-0800: netrigctl_get_mode called, vfo=VFOA

2023-09-22T19:55:18.898183-0800: netrigctl_transaction: called len=2

2023-09-22T19:55:18.898192-0800: network_flush called

2023-09-22T19:55:18.898549-0800: rig_parse_mode called

2023-09-22T19:55:18.898608-0800:    3:cache.c(35):rig_set_cache_mode entered

2023-09-22T19:55:18.898630-0800:    3:cache.c(108):rig_set_cache_mode returning(0) 

2023-09-22T19:55:18.898651-0800:   2:rig.c(2586):rig_get_mode returning(0) 

2023-09-22T19:55:18.898665-0800:  1:rig.c(1403):rig_open returning(0) 

Opened rig model 2, 'NET rigctl'

2023-09-22T19:55:18.898724-0800: Backend version: 20230328.0, Status: Stable


Rig command: m

2023-09-22T19:55:36.000585-0800:  1:rig.c(6084):rig_get_powerstat entered

2023-09-22T19:55:36.000603-0800: netrigctl_get_powerstat called

2023-09-22T19:55:36.000612-0800: netrigctl_transaction: called len=15

2023-09-22T19:55:36.000623-0800: network_flush called

2023-09-22T19:55:46.004646-0800: read_string_generic(): Timed out 10.003 seconds after 0 chars, direct=1

2023-09-22T19:55:46.004669-0800: netrigctl_get_powerstat: PS command failed (ret=-5) so returning RIG_POWER_ON

2023-09-22T19:55:46.004681-0800:  1:rig.c(6109):rig_get_powerstat returning(0) 

2023-09-22T19:55:46.004700-0800:  1:rigctl_parse.c(2240):rigctl_get_mode entered

2023-09-22T19:55:46.004709-0800:   2:rig.c(2453):rig_get_mode entered

2023-09-22T19:55:46.004751-0800: netrigctl_get_mode called, vfo=currVFO

2023-09-22T19:55:46.004767-0800: netrigctl_transaction: called len=2

2023-09-22T19:55:46.004778-0800: network_flush called

2023-09-22T19:55:46.005336-0800: rig_parse_mode called

2023-09-22T19:55:46.005403-0800:    3:cache.c(35):rig_set_cache_mode entered

2023-09-22T19:55:46.005427-0800:    3:cache.c(108):rig_set_cache_mode returning(0) 

2023-09-22T19:55:46.005446-0800:   2:rig.c(2586):rig_get_mode returning(0) 

Mode: PKTUSB

Passband: 2850

2023-09-22T19:55:46.005462-0800:  1:rigctl_parse.c(2263):rigctl_get_mode returning(0)


SparkSDR logs:

09/22/2023 19:55:08 v2.0.33.0

Received connection request from 127.0.0.1:53343

09/22/2023 19:55:08 v2.0.33.0

0 rigctl ->\get_powerstat

09/22/2023 19:55:08 v2.0.33.0

Rigctrl Unhandled cmd -\get_powerstat-

09/22/2023 19:55:08 v2.0.33.0

0 rigctl <-NULL

09/22/2023 19:55:08 v2.0.33.0

Rigctrl running

09/22/2023 19:55:18 v2.0.33.0

10002 rigctl ->\chk_vfo

09/22/2023 19:55:18 v2.0.33.0

10003 rigctl <-0


09/22/2023 19:55:18 v2.0.33.0

10003 rigctl ->\dump_state

09/22/2023 19:55:18 v2.0.33.0

10003 rigctl <-0

2

1

100.000000 6000000000.000000  0x000f -1 -1 0x1 0x0

0 0 0 0 0 0 0

100.000000 6000000000.000000  0x000f 100 5000 0x1 0x0

0 0 0 0 0 0 0

0 0

0 0

0

0

0

0



0x0

0x0

0x0

0x0

0x0

0


09/22/2023 19:55:18 v2.0.33.0

10004 rigctl ->v

09/22/2023 19:55:18 v2.0.33.0

10005 rigctl <-VFOA


09/22/2023 19:55:18 v2.0.33.0

10005 rigctl ->f

09/22/2023 19:55:18 v2.0.33.0

10005 rigctl <-14236000


09/22/2023 19:55:18 v2.0.33.0

10006 rigctl ->V VFOB

09/22/2023 19:55:18 v2.0.33.0

10006 rigctl <-RPRT 0


09/22/2023 19:55:18 v2.0.33.0

10006 rigctl ->f

09/22/2023 19:55:18 v2.0.33.0

10006 rigctl <-14236000


09/22/2023 19:55:18 v2.0.33.0

10007 rigctl ->V VFOA

09/22/2023 19:55:18 v2.0.33.0

10007 rigctl <-RPRT 0


09/22/2023 19:55:18 v2.0.33.0

10007 rigctl ->s

09/22/2023 19:55:18 v2.0.33.0

10007 rigctl <-0

VFOA


09/22/2023 19:55:18 v2.0.33.0

10008 rigctl ->m

09/22/2023 19:55:18 v2.0.33.0

10008 rigctl <-PKTUSB

2850


09/22/2023 19:55:36 v2.0.33.0

27110 rigctl ->\get_powerstat

09/22/2023 19:55:36 v2.0.33.0

Rigctrl Unhandled cmd -\get_powerstat-

09/22/2023 19:55:36 v2.0.33.0

27111 rigctl <-NULL

09/22/2023 19:55:46 v2.0.33.0

37114 rigctl ->m

09/22/2023 19:55:46 v2.0.33.0

37115 rigctl <-PKTUSB

2850


Unfortunately Hamlib 4.6~git behaves even worse, simply not allowing certain queries entirely because the radio is "off". 

Anyway, I suspect if SparkSDR can be updated to provide a reasonable response for the "get_powerstat" command, both Hamlib and FreeDV will behave a lot better.

Thanks,

-Mooneer K6AQ

Boudewijn (Bob) Tenty

unread,
Sep 23, 2023, 2:35:25 PM9/23/23
to digita...@googlegroups.com

Hi Mooneer,

Thanks for looking further into this, I will contact Alan M0NNB the developer of SparkSDR about this.
By the way, where are the logs of FreeDV located in the MacOS and Linux version?

73,

Bob VE3TOK

Mooneer Salem

unread,
Sep 23, 2023, 7:45:13 PM9/23/23
to digita...@googlegroups.com
Hi Bob,

Right now the logs are available when run from Terminal. For example:

$ /Applications/FreeDV.app/Contents/MacOS/FreeDV
[2023-09-23 16:44:06] [connect] Successful connection
[2023-09-23 16:44:06] [connect] WebSocket Connection [2602:fffa:fff:108a:216:3eff:fe32:ba39]:80 v-2 "WebSocket++/0.8.2" /socket.io/?EIO=4&transport=websocket&t=1695512646 101
Start .....
Setting callsign to K6AQ
freedv_get_n_speech_samples(tx): 1280
freedv_get_speech_sample_rate(tx): 8000
startRxStream .....

...

Thanks,

-Mooneer K6AQ

Reply all
Reply to author
Forward
0 new messages