On Sat, Oct 12, 2019 at 12:29 PM Andre Natal wrote:
> We tried to capture everything here [1], so please if you don't see your
> question addressed in this document, just give us a shout either here in
> the thread or directly.
...
> [1]
> https://docs.google.com/document/d/1BE90kgbwE37fWoQ8vqnsQ3
Hi Fabrice,
Thanks for letting us know. I'm cc'ing jvo here so she can open them.
On Sun, Oct 13, 2019, 1:53 AM Fabrice Desre wrote:
> Hi André :)
>
> The links to the last 3 docs seem to not be publicly accessible:
> - Are you adding voice commands to Firefox?
> -> mana is not public.
>
> W
I believe there was a slight misunderstanding. The current work being made
is on the recognition part of the API only. The synthesis part landed a
while ago, and is already enabled by default. You can find some
documentation here:
https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API
On
Hi André :)
The links to the last 3 docs seem to not be publicly accessible:
- Are you adding voice commands to Firefox?
-> mana is not public.
What’s next?
-> private google doc.
Have a question not addressed here?
-> private slack channel.
On 10/12/19 3:14 PM, Andre Natal wrote:
> The d
The doc should be open now, please let us know if you still can't access it.
On Sat, Oct 12, 2019, 4:40 PM wrote:
> The link to the FAQ is posted in the public group, in a thread meant for
> audiences outside MoCo. Please consider opening the doc to be readable to
> everyone, or at least copy t
The link to the FAQ is posted in the public group, in a thread meant for
audiences outside MoCo. Please consider opening the doc to be readable to
everyone, or at least copy the questions which already have answers (that you
consider "done") in a reply to this thread.
Thanks
Tomislav
On Satu
The document says "The WebSpeech API allows websites to enable speech
input within their experiences." and that it is emphatically NOT
"Text-to-speech/narration".
This doesn't correspond to the original email here:
As of October 11th, the Emerging Technologies Team intend to turn "Web
Speech
Hello everyone,
sorry for the delay, but besides the patch itself we were working in an FAQ
to address all the questions raised in this thread along others we got from
other teams.
We tried to capture everything here [1], so please if you don't see your
question addressed in this document, just g
On Monday, October 7, 2019 at 12:55:23 PM UTC+11, Marcos Caceres wrote:
> As of October 11th, the Emerging Technologies Team intend to turn "Web Speech
> API" on by default in *Nightly only* on Mac, Windows, and Linux. It has been
> developed behind the "media.webspeech.recognition.*" and
> "med
(Apologies for top-posting. I've asked the folks from ET to reply to the
questions - Andre said he will respond soon! I was just helping them post the
Intent, but I'm personally not involved with the implementation so I can't
answer these really good questions... I'm just helping with our proces
On 07/10/2019 09:53, Henri Sivonen wrote:
On Mon, Oct 7, 2019 at 5:00 AM Marcos Caceres wrote:
- speech is processed in our cloud servers, not on device.
What should one read to understand the issues that lead to this change?
+1. This seems like a change of direction which has *huge* im
On 07/10/2019 02:55, Marcos Caceres wrote:
- speech is processed in our cloud servers, not on device.
Is this the case for both recognition and synthesizing? It's not clear
from this concise description.
Also, hasn't window.speechSynthesis been shipped before now? It's used
from e.g. read
On Mon, Oct 7, 2019 at 5:00 AM Marcos Caceres wrote:
> - The updated implementation more closely aligns with Chrome's
> implementation - meaning we get better interop across significant sites.
What site can one try to get an idea of what the user interface is like?
> - speech is processed in
As of October 11th, the Emerging Technologies Team intend to turn "Web Speech
API" on by default in *Nightly only* on Mac, Windows, and Linux. It has been
developed behind the "media.webspeech.recognition.*" and
"media.webspeech.synth" preference.
Other UAs shipping this or intending to ship i
On Tue, Nov 3, 2015 at 9:42 AM, Eitan Isaacson wrote:
> As of this week, I intend to turn on the speech synthesis API on by default
> for the desktop browser. It has been enabled in b2g for the last few years.
> Thanks to work by Makoto Kato, and Yash Girdhar, we now have support for
> speech in a
As of this week, I intend to turn on the speech synthesis API on by default
for the desktop browser. It has been enabled in b2g for the last few years.
Thanks to work by Makoto Kato, and Yash Girdhar, we now have support for
speech in all desktop platforms.
The pref that will be flipped is "media.
Chris,
I was discussing with sphinx leaders and we can build models from
audiobooks as well.
This approach saves a lot of time and enhances the quality since the
narrative is well accurate and clear.
We are currently defining a way to create hindi and brazilian portuguese
models.
Thanks
Andre
November 8, 2014 8:50:44 PM
> Subject: Re: Intent to ship: Web Speech API - Speech Recognition with
> Pocketsphinx
> Hi Olli,
> > How much does Pocketsphinx increase binary size? or download size?
> In the past was suggested to avoid ship the models with packages, but yes to
&
uot; , dev-platform@lists.mozilla.org
> Sent: Saturday, November 8, 2014 8:50:44 PM
> Subject: Re: Intent to ship: Web Speech API - Speech Recognition with
> Pocketsphinx
> Hi Olli,
> > How much does Pocketsphinx increase binary size? or download size?
> In the past was sugges
issue? or ?
>>
>> Thanks,
>> Sincerely yours.
>>
>> --
>> *From: *"Andre Natal"
>> *To: *dev-platform@lists.mozilla.org, "Sandip Kamat" ,
>> "Olli.Pettay"
>> *Sent: *Friday, October 31,
From: *"Andre Natal"
> *To: *dev-platform@lists.mozilla.org, "Sandip Kamat" ,
> "Olli.Pettay"
> *Sent: *Friday, October 31, 2014 7:18:06 AM
> *Subject: *Intent to ship: Web Speech API - Speech Recognition with
> Pocketsphinx
>
> I've been resear
age -
> >
> > From: "Andre Natal"
> > To: dev-platform@lists.mozilla.org, "Sandip Kamat" ,
> "Olli.Pettay"
> > Sent: Friday, October 31, 2014 7:18:06 AM
> > Subject: Intent to ship: Web Speech API - Speech Recognition with
> Pocketsphi
Hi Chris.
For new languages, after the decoder get integrated inside gecko, you only
need to build new models (acoustic and language), since the decoder is
language agnostic.
The procedure of model building is the same for every language: in pretty
big picture, you need to record thousands of hou
Hi Olli,
> How much does Pocketsphinx increase binary size? or download size?
In the past was suggested to avoid ship the models with packages, but yes
to create a preferences panel in the apps to allow the user to download the
models he wants to.
About the size of pocketsphinx libraries itself
Thanks Nick, I appreciate your help.
I created two versions of Fennec apk: one [1] with the english models
bundled (43.7 mb), and other [2] without it (34.6mb). This was the
mozconfig I used [3]
Actually, I had a conversation with Jonas Sicking some months ago and we
agreed that the ideal scenar
gt; emscripten -> performance issue? or license issue? or ?
>
> Thanks,
> Sincerely yours.
>
> - Original Message -
>
> From: "Andre Natal"
> To: dev-platform@lists.mozilla.org, "Sandip Kamat" ,
> "Olli.Pettay"
quot; ,
"Olli.Pettay"
Sent: Friday, October 31, 2014 7:18:06 AM
Subject: Intent to ship: Web Speech API - Speech Recognition with Pocketsphinx
I've been researching speech recognition in Firefox for two years. First
SpeechRTC, then emscripten, and now Web Speech API with CMU po
On 31/10/2014 11:45 AM, Chris Hofmann wrote:
The place we really need this is b2g, but phones are only shipping in
international markets right now so english only is not all that helpful.
While this doesn't change the point you are making in any way, FWIW,
Firefox OS phones are on sale in Aust
On 10/30/14 5:24 PM, smaug wrote:
On 10/31/2014 02:21 AM, smaug wrote:
Intent to ship is too strong for this.
We need to first have implementation landed and tested ;)
I wouldn't ship the implementation in desktop FF without plenty of
more testing.
But I guess the question is what people t
Intent to ship is too strong for this.
We need to first have implementation landed and tested ;)
I wouldn't ship the implementation in desktop FF without plenty of more testing.
-Olli
On 10/31/2014 01:18 AM, Andre Natal wrote:
I've been researching speech recognition in Firefox for two year
On 10/31/2014 02:21 AM, smaug wrote:
Intent to ship is too strong for this.
We need to first have implementation landed and tested ;)
I wouldn't ship the implementation in desktop FF without plenty of more testing.
But I guess the question is what people think about shipping the pocketspinx +
On 2014-10-30, 4:18 PM, Andre Natal wrote:
I've been researching speech recognition in Firefox for two years. First
SpeechRTC, then emscripten, and now Web Speech API with CMU pocketsphinx
[1] embedded in Gecko C++ layer, project that I had the luck to develop for
Google Summer of Code with the m
I've been researching speech recognition in Firefox for two years. First
SpeechRTC, then emscripten, and now Web Speech API with CMU pocketsphinx
[1] embedded in Gecko C++ layer, project that I had the luck to develop for
Google Summer of Code with the mentoring of Olli Pettay, Guilherme
Gonçalves,
33 matches
Mail list logo
