This should be fixed, use “id-ID”
Wow fantastic!! It works like a charm!!! Thank you very much for your quick response and solution.
Jump to content
Please can you help. I've been using the plugin now for about a month after I purchased it from the market store and managed to get everything working great. Its a wonderful plugin however its stopped working today. I've gone through the code in my app with a fine brush to make sure there are no problems there but could find none. To make sure I also tested the voiceToText demo app on an android device. Both my app and the demo came back with the same runtime error:
This runtime error appears when calling;
Please could you check things on your side of things as I think there may be error or something has changed that has stopped the plugin from working properly when a function call is made to start recording. Sincerest apologise if I'm wrong but I've exhausted all possible reason on this side of things. I've checked both the device is working properly with wifi working fine and also all the code related to the plugin and not related to the plugin in the app is working fine. Thank you for your help.
That mainly all there is, however the above error message is for an app in release mode in debug mode it comes back with:
/user/liamyoung/Desktop/Mirror/Smart Mirror/SCENES/menuScene.lua:1012:java.lang.illegalArgumentException:illegal index
Here the code at 1012 in menu scene:
1006 if(voiceToText.isRecording())then 1007 voiceToText.stopRecording(); 1008 recordingMic.alpha = 0; 1009 timers.voiceCount = timers.voiceMax - 60; 1010 return; 1011 end 1012 voiceToText.startRecording(); -- place of Runtime Error 1013 recordingMic.alpha = 1; 1014 timers.voiceCount = 0;
It was from these results I then check if the voice to text demo was working okay. Again it came back with the same error but relevant to where the call to voiceToText.startRecording() is in the app. If i remove the call to the voiceToText.startRecording() there no Runtime error so its definitely seems a problem with the function for some reason. Unfortunately though this is all I have to go on sorry Scott.
I'm finding that this has no effect - voiceToText.startRecording(nil, nil, 5000,5000,5000)
Recording stops 2.2 seconds after start. I'm recording "1,2", so a very short recording session.
When I record a longer session, still stops immediately on a pause.
This is on 2 phones Android 4.4.4 and 6.
Update. It seems that the timeout is delayed if the voice recognition needs time to work out what is said. I spoke gibberish into the app, paused and spoke proper words. Because my gibberish was still being processed, the pause was 'accepted' and my proper words after the pause also accepted.
Probably not be of any use of course...
It looks like Google either removed this feature to set inputSilenceLength or it is a bug. Either way, it looks like it is not working for anyone.
I have also tried a couple apps that use this android api and they seem to have the same issue. I can not do anything on my end to fix this google issue.
Your plugin is awesome!!!
Is it possible to add support for Apple TV? Apple TV 4th generation and 4K has a microphone in the remote control (for Siri). If Apple TV can be supported it would be a game changer for me
I have my Android phone (6.0.1) working well with this plugin, but I have a timing problem.
Context: my app is for helping young children volcalize; a word is read to them, then they say it back.
Problem: No matter what I have tried, I cannot get any sound out after voiceToText.startRecording(...) -- it blocks all audio, and I have tried audio.play as well as a texttospeech app. If I can fix this, that might do it for me.
That wouldn't be fatal except for the delay. I now play the phrase (eg, "Say bubble"), and start Recording as soon as that completes. But then the recording does not actually start for 1+ seconds after I send the startRecording message, and children are not that patient. I need to get this difference down to 200-300ms or less.
I did note that doing an initial start/stop at app startup shortens the time for the first start after that, but they are still far too long.
So, 2 problems: the time after startRecording and when it accepts sound is much too long for my use, and 2) I cannot start the recording ahead because it blocks all audio output.
From the specs (and other comments) it seems that blocking all audio is probably a bug on my side? (I use "false" for the second argument, but it makes no difference what I put there, all sound is stopped.)
Phone is alcatel idol 3, but these children will not have high end phones/tablets anyway.
OK, thank you for the answer. I think I have improved it a lot by abandoning texttospeech (instructions of what word to say; I just use pre-recorded batch transactions from Amazon Polly) and just playing audio. That makes it a shorter and more reliable gap. We already use visuals, but these are very young kids (3-5) who have various attention issues, so the instructions "Harry, say bubble" is critical.
But now, today, voiceToText does not work at all. It was all working fine the past two days, but today, I get no error, I never get the 'started' e.response, and never get any recording. Did something happen to any servers or something? Is there a way for me to debug this? There is nothing at all in the log, just my own record that I did init and start (and stop), but nothing more.
Nothing is printed out, how do I figure out if it is my problem? I changed a lot of things in my code, but none of it in the routines that call voiceToText. Any suggestions?
Yes, lots of stuff wouldn't work if that were a problem. But I borrowed back a different device that has the version I made yesterday and it works, so it clearly is something interacting with code I changed today (mostly replacing texToSpeech with audio.play). Do I have to worry about audio channels? But now that I know that the problem is somewhere in my app, I will track it down. But I am concerned that it stopped working after I changed other things.
Anyway, thank you for your help. Feel free to suggest anything else I should check. I will try to roll back to get it working again.
Solved it. Somehow, microphone permissions were turned off, even though they were explicitly requested in install. If my grandson had been playing with the phone, I would have blamed him, but must have been something I did. Anyway, no problem.
My delay is much shorter and more reliable using audio.play instead of textToSpeech, might be enough to get by with it. We'll see with user testing.