[Feature Request] Switchable configurations

[peterbmarks]

Contact Details

peterbmarks@gmail.com

Feature for this project

I would like to be able to easily switch between different transceivers as is possible in other apps such as Fldigi and WSJT-X. This would involve switching between named INI files.
This could be done with a script outside FreeDV gui.
Peter

VHF/UHF

No

Deprecated features

No

Non-standard compiler

No

Legal worldwide

Yes

Implementation assistance

Happy to test.

Support assistance

Yes.

[tmiw]

See https://github.com/drowe67/freedv-gui/blob/master/USER_MANUAL.md#multiple-configurations. Is the request for something other than this?

[peterbmarks]

I'm asking for a user interface within the app to switch configs. Rather like WSJT-X or Fldigi does. This is a low priority but I think would be useful.

[tmiw]

Ah OK. I thought there was a previous feature request in here for this but I can't seem to find it at the moment, so we'll keep this open until there's more demand.

[Tyrbiter]

I think this would be a good idea to implement when we have resource available but it's possible to workaround with multiple .freedv files and some scripting, I think @barjac has something like this in use.

[barjac]

I think @barjac has something like this in use.

Yes, I use freedv-start scripts which start rigctld with the correct parameters for the radio in use.
They then run freedv with the -f (config) option for that radio.

After close of freedv, the rigctld daemon is stopped and the script exits.

With suitably named 'freedv-start-*' scripts and *.desktop files, freedv can be started for any radio.

The basics of this are described and partly implemented in freedv-rade-build

I have run two instances of freedv concurrently using this but only tested using one with transmit and CAT capability.
Note that freedv shows the config file name in both the main and reporter window headers just for this use case to avoid confusion.

Running two radios with CAT from two instances of freedv would also involve using two instances of rigctld using different sockets.

TBH I feel that doing this outside FreeDV is far more flexible and less bug prone than to try to incorporate it into an already complex project. I may be wrong. :)