From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: Tensorflow audio recognition
Date: Fri, 1 Feb 2019 06:08:30 -0800 [thread overview]
Message-ID: <b0ca0b88-acad-8007-2061-0d34d306f841@gmail.com> (raw)
In-Reply-To: <CA+XASoVUmffN6DeRQ9TbLrqWDwh8XoWf5Lkiv6MJFJ2EWL1rRQ@mail.gmail.com>
On 1/31/19 2:48 PM, Aleix Conchillo Flaqué wrote:
> On Thu, Jan 31, 2019 at 2:37 PM Jan Wedekind <jan@wedesoft.de> wrote:
>> Hi,
>> I got a Tensorflow neural network for audio recognition of 4
>> different words working.
>> There are three Scheme programs:
>> * software for recording audio training data
>> * software for performing the training
>> * software for testing using live audio input
>>
>> I used the software to remote control a Raspberry Pi Zumo robot.
>>
>> [1]: http://www.wedesoft.de/ai/2019/01/27/speech-recognition/
>>
> This is great! Thanks for sharing.
>
> Aleix
>
>
Ditto.
Matt
prev parent reply other threads:[~2019-02-01 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 22:37 Tensorflow audio recognition Jan Wedekind
2019-01-31 22:48 ` Aleix Conchillo Flaqué
2019-02-01 14:08 ` Matt Wette [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0ca0b88-acad-8007-2061-0d34d306f841@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).