Say and voice actions slow to initially respond

[Scott S]

Say and voice-related actions are initially, extremely slow to respond to inquiries; it may take 2-3 secs to respond. After a few uses, each responds almost immediately. Is there a means of 'caching' or setting high priorities of these uses/actions so that they respond immediately every time? I realize the G TTS must connect via Internet, which causes delays, though not certain that is the cause of all these delays.

[Matt R]

I don't recall if it's in the last stable version, but in the beta and definitely in the next stable version of Tasker you can uncheck "reduce resource usage" in the Tasker preferences.

Matt

[Scott S]

Thanks @Matt. I have the latest beta; had not seen that new option. I don't see much discussion about this option herein; any idea how much 'savings' is provided when enabled, on average/otherwise?

[nanobrain]

AFAIK this setting came from this discussion: https://groups.google.com/d/msg/tasker/LbhXFMtMOJI/Q4Qw7RZAO94J

[Scott S]

Thanks @nonbrain. I disabled this option and rebooted. It doesn't seem to speed up the initial use of say/voice actions.

My question...is such a delay in initially using say/voice actions normal? Voice actions when phone is not handy is great, i.e. using bt headset, or when I have already used say/voice actions, but I find I can access phone functions faster by tapping my way through. Is this just an evolutional issue or is my device slow?

Moto droid razr m

[Matt R]

Try a different TTS engine.

Matt

[Scott S]

I've tried Ivona, but didn't seem to get much of a speed difference. With that said, it doesn't seem to be an overall speed issue, as once say/voice actions are used, they seem to respond much faster in subsequent/immediate re-use.

The problem is in initially accessing the actions. This seems there is data to be cached or priorities set; is there not a way to cache the TTS data/intents/code, whatever it may be, or set higher priorities, initially? As an example, I use renice to set Tasker at a higher priority.

Here's an example use for me. Initially, when this Profile is started, it takes 2-3 secs for the Say Action (83-A1) to run. Then, it takes another 2+ secs for the reply Say Action (65-A1) to run. Subsequent uses of the Say Action, if used within responsible time period again, run as I would expect with not much delay.

Profile: SMS Received-contact (83)

Priority: 4 Notification: no

Event: Received Text [ Type:SMS Sender:C:ANY Content:* ]

State: Variable Value [ %Profile !~ Exercise/Sleep/Work ]

State: Not Profile Active [ Name:Silent Mode ]

State: Not Call [ Type:Any Number:* ]

Enter: Anon (88)

A1: Say [ Text:Text from %SMSRN Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focus:Off Network:Off Continue Task Immediately:Off ] 

A2: [X] Stop [ With Error:Off Task: ] If [ %BATT < 15 | %PACTIVE !~ *Sunshine* | %Profile !~ Home ]

A3: Say [ Text:%SMSRB, Do you want to reply? Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focus:Off Network:Off Continue Task Immediately:Off ] 

A4: AutoVoice Set Cmd Id [ Configuration:Setting Last Command Id to "reply to text" Package:com.joaomgcd.autovoice Name:AutoVoice Set Cmd Id Timeout (Seconds):0 ] 

A5: AutoVoice Recognize [ Configuration:

Prompt Text: Yes or No

Language Model: Web SearchVoice command without headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 Continue Task After Error:On ] 

Profile: Reply to text-yes (65)

Restore: no Notification: no

State: AutoVoice Recognized [ Configuration:Event Behaviour: true

Command: "yes"

Last Command Id: reply to text ]

Enter: Anon (129)

A1: Say [ Text:What is your reply? Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focus:Off Network:Off Continue Task Immediately:Off ] 

A2: AutoVoice Recognize [ Configuration:

Prompt Text: What is your reply? 

Language Model: Web SearchVoice command without headset Package:com.joaomgcd.autovoice Name:AutoVoice Recognize Timeout (Seconds):0 ] 

A3: [X] Wait [ MS:500 Seconds:0 Minutes:0 Hours:0 Days:0 ] 

A4: AutoVoice Set Cmd Id [ Configuration:Setting Last Command Id to "confirm reply" Package:com.joaomgcd.autovoice Name:AutoVoice Set Cmd Id Timeout (Seconds):0 ] 

[Matt R]

"Initially" meaning after a reboot? You could just do a dummy say action after each reboot.

Matt

[Pent]

The option Reduce Resource Usage only speeds up subsequent messages.

Things have gotton slow recenty because Google upped the amount of data that needs loading by a huge amount.

To make it more consistent, as Matt says, you just need to uncheck the option and do an initializing Say when it's not so important.
Turn the sound down first if you want.

Pent

[Scott S]

Not only are the say/voice actions slow upon reboot, they are slow if I don't use those actions for a while. Hopefully, the combo of initializing a say action upon reboot (saying...phone has rebooted :-) ) and unchecking the resources switch will help. Thanks!

[xander vlasveld]

Hi Scott,

I don't know if we are talking about the same issue but I'm using Tasker in combination with Autovoice and Svox TTS and I'm experiencing the following:

My profiles seem to take about 5 seconds to start to run (the first task is TTS to confirm the spoken command) and this delay only happens when I didn't use tasker for a while. I'm only using tasker icw Autovoice, if the first profile has run the following profiles start almost instantly after the spoken command.

I think this all started after upgrading to GE 4.4.X, so maybe related to a new Google Search version. Are we talking about the same issue? 

It's driving me crazy :). 

[Matt R]

Did you uncheck "reduce resource usage" as directed?

Matt

[xander vlasveld]

Hi Matt,

That's a good one, will do that and report back. 

[Scott Almond]

I have the same issue and always have. From what I understand its due to android initialing tts and caching its resource to RAM. once in the deceives RAM, tts actions will respond instantly. Since android manages its own RAM, tts will be flushed out when you need RAM for other things. hence, next time you call a tts task it has to re-cache to RAM again causing the delay. The best solution would be to try and figure out a way for tts to stay cached in the RAM. if you have root/xposed, there's a module called "keep running" (https://play.google.com/store/apps/details?id=de.defim.apk.keeprunning). and the free version allows you to set 3 apps. may be worth a try. Haven't got spare time to check and test at the moment, but I expect I will try it my self at some point. let us know if you try it.

Regards
Scott

[xander vlasveld]

Hi Scott,

I did already play with another xposed module (can't remember the name) to keep the involved apps (Autovoice, TTS and Tasker) resident in memory.

But that didn't resolve the issue, strangely it was working instantly/perfect before updating to another version of Android (i think it was this).

On the other hand this could be logically cause of different ram management. 

I changed the Tasker setting as Matt advised, will report back how that panned out. 

[xander vlasveld]

Unfortunately the "reduce resource usage" setting didn't help. Will play again with a "keep resident/in memory" app to see if that helps.  

 

[xander vlasveld]

Talking to myself here :)

Even with all the 4 apps resident in memory I'm still getting the 5 seconds delay. what could be the cause of the initial delay? strange...

Op vrijdag 29 augustus 2014 10:22:28 UTC+2 schreef xander vlasveld:

[Scott S]

Are you experiencing this delay after touching the Home button? If so, this may be the built-in 5 sec delay KK has. There's an Xposed mod that removes the delay: http://goo.gl/qj4ZwH

My only other thought is that TTS needs to phone home and it may be related to your Internet connection. I changed over to using an app called Utter! for most of my voice prompts. It allows lauching AV tasks, and can also use Google Now. It is quick, because it's local. It doesn't need to connect to Internet resources before starting. I've decided to stop using AV until I upgrade my phone.

[Scott Almond]

Google TTS is local also. Google voice recognition is the service that uses an internet connection by default but also has an offline mode.

Xander, are using the high def voice in Google TTS? (the 200+mb voices). if so, I recommend using the default voice instead (4+mb voice). The standard voices are a lot better quality now (I find it hard to tell the difference between the 2) and respond a hell of a lot quicker in Tasker. I know when I tried using the high def voices it would sometimes delay up to 15+ seconds)

Regards
Scott

[Scott Almond]

also Utter is a voice recognition service not a text to speech service. important not to get these 2 confused as they are very different things.

Regards
Scott

[xander vlasveld]

It's not the homebutton delay, Autovoice opens instantly. After the beep from the Autovoice/google search prompt nothing happens for 5 seconds.

Op vrijdag 29 augustus 2014 16:05:02 UTC+2 schreef Scott S:

[xander vlasveld]

I'm using a separate TTS app "Svox" (needed Dutch voices). You think it's related to the TTS engine I'm using?

Op vrijdag 29 augustus 2014 16:18:55 UTC+2 schreef Scott Almond:

[xander vlasveld]

Utter is a replacement for AV? Also with Google search integration?

Op vrijdag 29 augustus 2014 16:21:40 UTC+2 schreef Scott Almond:

[Scott S]

Although Utter! is not a true TTS engine as Scott says, it works for me. I use it to text, make calls, execute any Tasker Task, search using Google Now/Search, etc. For me, AV issue may just be a phone problem, so I'll stick with Utter! until I upgrade.

[Scott S]

It may be the TTS engine you're using. Is there still a delay for you when using the default G TTS engine? If not, there's your answer.

[Rich D]

> It's not the homebutton delay, Autovoice opens instantly.

Have you tried with just the tasker 'get voice' without using Autovoice ?

[xander vlasveld]

Do you have a short instruction for that? Thx

[xander vlasveld]

Will Google the instructions, sorry for my laziness.

[xander vlasveld]

Tried utter and I like it, just missing Dutch language support.

Some other observation:when starting a task from Tasker TTS is instantly working. When running a task with autovoice right after that it takes 5 seconds again. So my logic says it's not related to TTS. Cause TTS should still be in memory.

[Rich D]

> Some other observation:when starting a task from Tasker TTS is instantly working. When running a task with autovoice right after that it takes 5 seconds again.

I am thinking it is auto voice.  Are you trying to use autovoice with the google now integration?  If I recall correctly the mod that supports that was broken in one of the last android updates.

[xander vlasveld]

Nope, not using Google now. Love the autovoice / tasker combo but like to have my delay less performance back. I had it working perfectly for about 6 months. Till something got updated. Still think it's new Android (4.4.x),searching like a madmen for a solution and probably with Android 5 everything is solved again :-P.

[xander vlasveld]

I think I solved it, I noticed that with a newer version of Autovoice / Google search the GPS icon always lighted up when doing a voice command. So I disabled gps in my android settings and tested it for a few days. And voila, no more delays and instant executing of the command. I elenabled gps again and installed the exposed app "App Settings" and disabled the location permission for Google search.

So now I can use gps again and the commands are executed instantly again.
If anything changes or the delay will come back I will post here again.

Everyone thanks for there help.

[Spam Bus]

After disabling GPS the responce time is faster, but still not what it used to be, without GPS the responce time is still between 4-7 seconds on my Nexus 7 2013 and Motorola Moto G, with GPS on it can take as much as 12-20 seconds for a reponce

It used to be like 1-2 seconds in the past...

[Spam Bus]