Closed drowe67 closed 3 years ago
Perhaps we can implement #104 as a command line option to specify a config file to partly implement this? I believe FreeDV uses the configuration registry (Windows Registry on Windows and wherever it's stored on other platforms), so it should be a simple code change to make it use config files instead.
Sure that would work, the config is stored in ~/.FreeDV
on Linux already (and perhaps MacOS). Not sure how to handle Windows, using the registry is kind of a convention. However most of our testing is on Unix type systems.
BTW, ~/.FreeDV is only used on Linux; ~/Library/Preferences/FreeDV Preferences is apparently used on macOS (and the Windows Registry used on Windows). I listed those defaults in the user manual as part of #119.
A way to run freedv-gui from the command line, put it into a mode (e.g 700D), set up input and output sound cards, and feed a signal through it. This way basic freedv-gui operation can be tested using a GitHub action.
codec2/unittest/tnc*
tests for examples).