<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-GB" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi,</p>
<p class="MsoNormal"><br>
Xiph has done some really good work but since Speex things have seemed quite quiet.<br>
Devs to hobbyists have a huge battle with VoiceAI audio processing and even when available extremely similar routines are separated across libs so that much process duplication occurs and increases load.<br>
<br>
The Alsa-plugins of Speex echo just don’t seem to work whilst repos using the speex libs do.<br>
<a href="https://github.com/voice-engine/ec">https://github.com/voice-engine/ec</a><br>
<br>
I actually use the speex AGC Alsa-plugin as its a great tool and then run Echo via the above.<br>
Coupled to WebRTC_VAD and a python based MFCC routine.<br>
Beamforming and DOA I have given up hope for as I am running so many extremely similar FFT routines concurrently in different process space that my load usage makes me believe there isn’t a chance.<br>
<br>
All of them have extremely similar frame based spectra analysis collection that collate and process over different windows for different process but much of the input process are almost identical heavy load FFT process that for some reason we duplicate because
the Linux landscape is one of scattered audio processing libs.<br>
<br>
Linux currently has much work in terms of open source ASR, TTS, TensorFlow frameworks but what we have available in terms of audio pre-processing are scattered individual segments of the audio chain and create a seriously inefficient chain.<br>
These are old tools but the whole chain to MFCC output just doesn’t exist.<br>
<br>
Stuart<br>
<br>
</p>
<p class="MsoNormal">Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">
Mail</a> for Windows 10</p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>