Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
Add an optional parameter to the command line where the replaybot can be instructed to perform a muted pause between samples.
The parameter could look like this: --pause <seconds|random:min,max> to indicate a fixed pause in seconds, or a random one between a minimum and a maximum.
Describe alternatives you've considered
Do this in a looped fashion from a shell script. However:
that will spawn a fresh bot per iteration.
also, the max lifetime of the bot is circumvented, as it is only honored per bot instance.
Is your feature request related to a problem? Please describe. No.
Describe the solution you'd like Add an optional parameter to the command line where the replaybot can be instructed to perform a muted pause between samples. The parameter could look like this:
--pause <seconds|random:min,max>to indicate a fixed pause in seconds, or a random one between a minimum and a maximum.Describe alternatives you've considered Do this in a looped fashion from a shell script. However:
Additional context Idea brought up in the FGFS forum when planning for a SAR mission where a human downed pilot would broadcast random radio help calls: https://forum.flightgear.org/viewtopic.php?p=399649#p399649
Code position for the new feature probably here: https://github.com/hbeni/fgcom-mumble/blob/5b8b7fde02fb58f9dc5b53cc4075e3a01fdd7a30/server/fgcom-radio-playback.bot.lua#L309-L311