Start then stop then start again failed !

Question

Start then stop then start again failed !

zamrokk opened this issue 7 years ago · comments

First time start is called, I receive data on my buffer
Then I call stop, the capturing is false

If I call start again, the capturing says true, but I receive nothing on my buffer.
Neither the event listener for success or error is called in fact ...

I tried to remove it each time and adding it again but it changes nothing :(

edin · Answer 1 · Tue Aug 22 2017 22:40:28 GMT+0800 (China Standard Time)

Could you please tell us something about your environment: Do you run in on iOS, Android, emulator, Cordova version etc?

benjamin fuentes · Answer 2 · Tue Aug 22 2017 22:43:21 GMT+0800 (China Standard Time)

ionic 2
cordova 7.0.1

using emulator on iOS

edin · Answer 3 · Tue Aug 22 2017 22:44:54 GMT+0800 (China Standard Time)

I haven't actually tested this plugin on an emulator. Does it work as expected on a real device?

benjamin fuentes · Answer 4 · Tue Aug 22 2017 22:49:24 GMT+0800 (China Standard Time)

I do not have an iPhone 2017-08-22 16:44 GMT+02:00 Edin Mujkanovic <notifications@github.com>:

…

I haven't actually tested this plugin on an emulator. Does it work as expected on a real device? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACazsJdXzWKL2VpdkTKpfuRrplbLXiMmks5saulmgaJpZM4O-WAh> .

edin · Answer 5 · Tue Aug 22 2017 22:50:57 GMT+0800 (China Standard Time)

Does it work on any real device? Android included.

benjamin fuentes · Answer 6 · Tue Aug 22 2017 22:58:26 GMT+0800 (China Standard Time)

Not yet tested. I have passed to another solution using a native speech recognizer as the speech to text api i was using with the audio was poor :/ 2017-08-22 16:50 GMT+02:00 Edin Mujkanovic <notifications@github.com>:

…

Does it work on any real device? Android included. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACazsB9hlno_ng1qkXciARED05ZJV3ARks5saurSgaJpZM4O-WAh> .

edin · Answer 7 · Thu Aug 24 2017 17:50:56 GMT+0800 (China Standard Time)

Ok, sounds like a good solution.

benjamin fuentes · Answer 8 · Thu Aug 24 2017 18:00:26 GMT+0800 (China Standard Time)

I don't know yet.... I see bugs too on the native recognizer. Maybe I will finally be back and test with another speech to text API . Lol Le 24 août 2017 11:50, "Edin Mujkanovic" <notifications@github.com> a écrit :

…

Ok, sounds like a good solution. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#48 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACazsF22BReqURUqWEkUqraQQaBTfotaks5sbUeAgaJpZM4O-WAh> .

edin · Answer 9 · Thu Aug 31 2017 20:55:37 GMT+0800 (China Standard Time)

Well, good luck. I'm closing this issue for now, but feel free to reopen it or create a new one should the need arise.