Mooneer Salem

Closing this out as https://freedv.org/radio-autoencoder/ covers system requirements.

FreeDV shows everything that pipewire knows about IIRC. Maybe taking a look at [the unit test script](https://github.com/drowe67/freedv-gui/blob/v2.0-dev/test/test_rade_reporting.sh) will help? It's basically doing the following to accomplish loopback on the "radio"...

BTW the filter might not be necessary once RADEv2 is out. I'm not fully sure if it'll cause RX problems on the other end with v1, either, but considering that...

> I now have a similar but slightly different issue. I am adding a Loudness Compensation Module between the Mic and FreeDV. > > The lv2 loudness module (mono) is...

> I think this is a sensible change, however it would be useful to allow access to the ALSA name via something like a tooltip for cross-checking purposes. Some other...

Closing as no action has been taken on this since it was originally created.

I'm honestly not sure how the timeout stuff interacts with Hamlib exactly. What version of the latter are you running? It's possible that there may still need to be kinks...

Can you try running `rigctl` separately, once with `-C timeout=1000 -C retry=1 -C timeout_retry=1 ` and once without those arguments for comparison? Does it still take 10 seconds to error...

Yeah, this seems like a Hamlib problem. Maybe @mdblack98 has an idea? It's also possible that I'm misunderstanding the exact meaning of `timeout`/`retry_timeout`/`retry` (for example, maybe timeout isn't actually in...

> Notice the message: kenwood_open: no response to get_id from rig...continuing anyway It keeps trying. Starting things with the rig off is not supported very well as we have to...