Creating a requested feature list

Archive
2

Greetings:

Here are a few I can think of off the top of my head.

  1. Add a way to prioritize the audio of specific nodes. I.E. the way ducking works in monitor mode. Let’s say your repeater is controlled by ASL3, and you want local repeater traffic to duck the audio of stuff coming in from the outside by a few DB, or for a specific list of nodes only. This is a feature requested by a club I am helping set up a multi-receiver RTCM repeater. I thought of a way this could possibly be implemented without modifying the code, but it would be messy.
  2. Mute transmitted audio to the network when the command character (* by default) is detected, but continue to pass the command through locally. This is a feature Echolink has had for years, to avoid noisy transmissions as people fumbling with DTMF entry, as they try to disconnect from a node. This is especially annoying when the majority of nodes on your system are half duplex.
    I brought this up once, and someone suggested this could create false detection. I would think this would be extremely unlikely if this were only triggered by one specific frequency pair.
  3. Add an equivalent to usbradio’s rxsquelchdelay in simpleusb. I think there is already an issue on Github about this.
  4. This is probably way out there, but for systems that have enough processing power to not make this slow and awkward, send spoken telemetry text through an external TTS rather than static files, with cached audio to avoid unnecessary regeneration, and the ability to parse node numbers and call signs in a way appropriate for TTS processing, I.E. node 508429 = node 5 0 8 4 2 9, or N2DYI = N 2 D Y I. Add a switch to announce call signs rather than node numbers sent to TTS processing, similar to what Echolink is supposed to do. This, if done properly, could significantly improve spoken repeater telemetry without having to create a large number of static files to be concatenated. The node could say something like node 5 0 8 4 2 9, connected to node 5 0 8 4 2 0 in one fluid utterance. Or, with calls enabled, if node 508429 connects to node 51018, it could say W6EK, connected to N2DYI, again, in one fluid utterance rather than a bunch of individual prerecorded files. For probably obvious reasons, this shouldn’t be the default behavior, as Piper, for example, takes quite a while to start on rPi, but is very fast on X64.

Just some thoughts.

73
N2DYI

1 Like