[App_rpt-users] Recording your QSO's as an MP3 file

Wed Jul 10 02:03:17 UTC 2019

Thanks for sharing Steve. The idea is very cool and it would be fun to play
with it more. Personally, I am not a fan of bringing the home assistants
into the ham space, at least not on the air. I have used Amazon (echo)
Alexa and Google Home both to link and unlink from various nodes, announce
time/IP and reboot but the variables were pre-programmed with a few of my
favorites, kind of like memory stations/channels. I have heard Siri on the
air in the past. I do not like putting the audio on the air at all or
letting people know that my node can be controlled by anyone's voice.
Remember it is speech recognition, not voice recognition.

I think Pierre Martel is working on a project similar to what you describe,
using a keyword to start listening to commands on the node itself - inline
with the audio live. So if configured properly right in the middle of his
QSO transmission he could say "We've been getting a lot of rain here...
Allstar Connect to node 45373... Let's see what John's weather is like over
in Madrid". Interesting concept, and a great goal to practice scripting,
but far too insecure for my liking to be put into play on one of my public
nodes. Private node? Perhaps.

On Wed, Jul 10, 2019 at 8:39 AM Steve L <kb9mwr at gmail.com> wrote:

> There was some brief discussion back in January about using artificial
> intelligence (AI) to control Allstar.
>
> It was in response to a hackaday entry about a google assistant on ham
> radio.
>
>
>
> On Tue, Jul 9, 2019 at 2:02 PM Joshua Nulton <kg5ebi at gmail.com> wrote:
>
>> I uploaded a couple sample audio clips to see how quickly it could
>> transcribe. It is nothing that could be done in real time, they took 40-90
>> seconds on average. The accuracy results on the first file was pretty good,
>> I was impressed. The second file not so much haha.... Take a listen. Still
>> it would be fun, now I am looking forward to the humor honestly.
>>
>> Link to Audio File 1 <http://108.61.224.90/library/2019-07-05023732.mp3>
>>
>> *Resulting Transcription*
>> [image: Rec01.png]
>>
>> Link to Audio File 2 <http://108.61.224.90/library/2019-07-05023755.mp3>
>>
>> *Resulting Transcription*
>> [image: Rec02.png]
>>
>> On Wed, Jul 10, 2019 at 1:36 AM Joshua Nulton <kg5ebi at gmail.com> wrote:
>>
>>> First let me say thank you for the response Bryan, you have given this
>>> community so much and I personally am grateful for your work.
>>>
>>> So you are thinking of transcriptions of the audio recordings? I t would
>>> be a fun test! I like the idea. I would be curious how the tool would
>>> handle the nuances of radio. Issues such as the horrid static of RF out of
>>> range, the robotic narrow bandwidth of digital modes, the accents of world
>>> and so on. Again I think the test would be fun.
>>>
>>> As far as the forum vs. mail list thing... I just find it difficult to
>>> monitor so many channels and maillists have modlists/banlists as I am 90%
>>> sure you probably are aware. :P
>>>
>>> On Wed, Jul 10, 2019 at 12:19 AM Bryan Fields <Bryan at bryanfields.net>
>>> wrote:
>>>
>>>> On 7/8/19 3:56 AM, Joshua Nulton wrote:
>>>> > Installation and configuration of everything is demonstrated in the
>>>> YouTube
>>>> > tutorial video. If you don't want to type out the bash script it can
>>>> be
>>>> > downloaded here:
>>>> > https://drive.google.com/open?id=1-z9UgW_L81MKl9eBKqMmDeT0xO9jl7qE
>>>>
>>>> Cool, you should add this to the wiki.
>>>>
>>>> Another thing I've been thinking, since we both have google accounts,
>>>> take the
>>>> files and send them to the speech to text google service.  We could add
>>>> in a
>>>> small plugin to the node log and reference the filename and the text.
>>>> You
>>>> could grep for callsigns :)
>>>>
>>>> https://cloud.google.com/speech-to-text/
>>>> > Enjoy and if you have any questions, please post them on the official
>>>> > Allstar Community forum here: https://community.allstarlink.org/
>>>>
>>>> Well it's not really used by anyone.  Lists are superior they are not
>>>> subject
>>>> to the same sort of censorship as a web forum.
>>>> --
>>>> Bryan Fields
>>>>
>>>> 727-409-1194 - Voice
>>>> http://bryanfields.net
>>>> _______________________________________________
>>>> App_rpt-users mailing list
>>>> App_rpt-users at lists.allstarlink.org
>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>>>
>>>> To unsubscribe from this list please visit
>>>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>>> and scroll down to the bottom of the page. Enter your email address and
>>>> press the "Unsubscribe or edit options button"
>>>> You do not need a password to unsubscribe, you can do it via email
>>>> confirmation. If you have trouble unsubscribing, please send a message to
>>>> the list detailing the problem.
>>>>
>>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at lists.allstarlink.org
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>>
>> To unsubscribe from this list please visit
>> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and
>> scroll down to the bottom of the page. Enter your email address and press
>> the "Unsubscribe or edit options button"
>> You do not need a password to unsubscribe, you can do it via email
>> confirmation. If you have trouble unsubscribing, please send a message to
>> the list detailing the problem.
>>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and
> scroll down to the bottom of the page. Enter your email address and press
> the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20190710/8859357c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Rec01.png
Type: image/png
Size: 151422 bytes
Desc: not available
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20190710/8859357c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Rec02.png
Type: image/png
Size: 122139 bytes
Desc: not available
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20190710/8859357c/attachment-0001.png>