开云体育

You can't do that through app.rpt. Telemetry isn't really configurable other than if it's on all the time, off, or on for a couple of minutes after each command. One could theoretically write a script that replaces that functionality, which is then tied to connpgm and discpgm in rpt.conf, then set telemdefault=0. Not something I've tried to do, but I know how it might work in theory.

That being said, I use the write_node_callsigns script on my nodes, which runs every morning at 3:16 AM EST on cron to pick up new node numbers for the day. I have it run at 3:16 AM, because this is one minute after the astdb.php job runs, which is a local list of all nodes on the allstarlink.org registration system, not just active nodes.

Ideally, I would use a local TTS engine and have everything in one utterance rather than using pre-recorded sound files, which could give you the same or more information in a lot less time without losing clarity, but there aren't really any good local TTS options that will actually run on a Raspberry Pi, and don't depend on someone's online API. I don't count eSpeak. There are the Cepstral voices, I guess, but I don't like their version of diphone concatenation. It's very choppy.

As it is, I replaced Allison on my nodes a long time ago using a very fast formant synthesis by rule engine, in this case, the Apple Fred voice. Not something you'd want to use on a repeater, but as a daily user of TTS (I'm blind and use a screen reader,) it became tedious very, very quickly listening to the stock voice. Yes, I could have sped it up, but with all or most of the sound files already being compressed with a lossy codec, I didn't want to add even more artifacts.

Anyway, that's probably way more than you asked for without actually telling you what you wanted to know.