[arm-allstar] modifying write-node-callsigns script

Wed Jan 29 05:08:04 EST 2020

I have better time compression algorithms available -- iZotope Radius, 
Elastique 2.28/3.x, FlexTime, etc. plus the ulaw/PCM wav source of 
Allison should I wish to speed her up, though I'm personally glad to not 
have her in my life anymore.

I also plan to record royalty/restriction free material myself in the 
coming weeks.

Re quality, I thought the same until I showed a few people what I was 
doing locally, with direct comparisons between GSM and ULAW, even 
without direct patching. People immediately noticed the difference even 
on HT speakers, more so than I thought.

On 1/29/2020 1:19 AM, "Doug Crompton via ARM-allstar" wrote:
> Patrick,
>
>   Please keep in mind that just about any good TTS has distribution
> restrictions. In other words if you bought it you cannot legally distribute
> it other than for your own use. This would be true even if it was part of
> another package and you did not directly purchase it. Some TTS packages
> also have broadcast restrictions. If there was something really good out
> there that was free we would be using it! The Google TTS that was free up
> to a few years ago was great but now it is a cost item and that would be on
> an individual basis. You couldn't legally gather up all their sounds and
> distribute them in a package.
>
> That being said if your goal is to speed up our existing Allison sounds the
> sox tempo command works well. You could experiment with the letters A-Z and
> digits 0-9 with call letters. I also use ocenaudio in Ubuntu to edit audio
> files. You could tighten up the space before and after the utterance. As
> far as quality is concerned I doubt most would really care about that
> especially those who use digital voice modes! Just make sure you save the
> sounds before you change them somewhere so you can go back to them if
> necessary.
>
> # Change tempo EXAMPLE
> # Less than 1.0 is slower, greater is faster
> sox /tmp/tmpaudio.wav /tmp/tmpaudio2.wav tempo 1.15
> echo -e "\nChanged Tempo by 1.15"
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Tue, Jan 28, 2020 at 3:15 AM "Patrick Perdue via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
>> This is true. What I am proposing is to basically make a new version of
>> that script which doesn't use any of the pre-existing sound files, but
>> rather, creates a new one by passing the callsign string through some
>> formatting directly to a TTS engine, putting a space after every
>> character in the callsign field before it is sent to the TTS.
>>
>> What I eventually would love to do after building a few sound packs
>> using different TTS voices is offer a public directory through rsync for
>> each of several voices, keeping things up-to-date, with a file in the
>> main /var/lib/asterisk/sounds/ or /var/lib/asterisk/sounds/rpt directory
>> that can be used as a reference, in combination with a script that pulls
>> new nodenames with rsync, to get files matching your currently installed
>> sound pack so that voices are consistent.
>>
>> My ultimate goal is to make everything more efficient by replacing
>> Allison and cutting down on TX time per utterance, while maintaining
>> intelligibility.
>>
>>
>> On 1/27/2020 10:40 PM, "Doug Crompton via ARM-allstar" wrote:
>>> Patrick,
>>>
>>>      You don't pass the entire text to be interpreted. There is a
>>> speaktext.sh file in /usr/local/sbin that does this as an exampple. It
>>> takes each letter and processes it individually like  W A 3 D S P not
>>> WA3DSP.  Each letter has a gsm file in /lib/asterisk/sound/letters  or
>>> digits, etc.
>>>
>>>
>>> *73 Doug*
>>>
>>> *WA3DSP*
>>>
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>
>>> On Mon, Jan 27, 2020 at 9:23 PM "Patrick Perdue via ARM-allstar" <
>>> arm-allstar at hamvoip.org> wrote:
>>>
>>>> Hi:
>>>>
>>>> I've been toying with the idea of making a modified write-node-callsigns
>>>> script, using an up-to-date astdb.txt as the source, but on a machine
>>>> not running HamVoIP, using a Mac to generate the TTS clips. However,
>>>> instead of concatenating existing GSM or ulaw files, I want to have it
>>>> say the entire text string of the callsign field with a space between
>>>> each character, so that TTS weirdness doesn't happen. I'm already using
>>>> a bash script on a Mac to generate replacement sound packs for HamVoIP
>>>> (more on that in the future.) In the name of efficiency, I would like to
>>>> have callsigns spoken at a single utterance. I'm not the most well
>>>> versed shell scripter around, so just looking for ideas of how to go
>>>> about formatting a text string in this way, which can then be fed to the
>>>> say command, then SoX to convert to ulaw as <node_number>.ul. The rest I
>>>> think I can handle.
>>>>
>>>> This may be a little overkill, but as a daily TTS user, I thought it
>>>> would be a nice touch, especially considering the availability of TTS
>>>> voices of Mac OS is greater than what is generally available in Linux.
>>>>
>>>> Also, the sound packs I've generated so far use ulaw, as it sounds
>>>> considerably better than GSM. Thus, I have to do a batch find/replace on
>>>> the HamVoIP scripts that specifically look for .gsm files. I'll probably
>>>> make both GSM and ULAW versions of these sound packs available when I
>>>> smooth some things out, and perhaps even a test in the scripts to use
>>>> either GSM or ULAW, depending on what is available, rather than only
>>>> assuming GSM.
>>>>
>>>> _______________________________________________
>>>>
>>>> ARM-allstar mailing list
>>>> ARM-allstar at hamvoip.org
>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>>
>>>> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>>>>
>>> _______________________________________________
>>>
>>> ARM-allstar mailing list
>>> ARM-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>> _______________________________________________
>>
>> ARM-allstar mailing list
>> ARM-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>>
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org