Pause/Resume Amazon Audible App

730 views
Skip to first unread message

Brad Minion

unread,
May 21, 2014, 12:19:04 PM5/21/14
to tas...@googlegroups.com
After searching the group I see that this topic has come up several times before but I don't see an answer. While listening to an audio book and I receive a text message I want to pause Audible, say the text message and then resume Audible. Some answers imply that this should be working automatically with the newest version of the "Say" command. For example, here is an excerpt of a post by Wes Stacey back in September.

These Beta's made a change to the "Say" command so that it will take control from the current application, how that application reacts to loosing control is based on how the developer programmed it to react. It can either pause playback until it receives control again (Audible is an example here), or it can lower it's own volume until it receives control again (Google Music is an example of an app that reacts this way). 
This change was put into place to prevent people from having to go through various hoops to pause/lower volume on music manually, and go through the headache of trying to figure out if music is playing in the background whenever they want to use a say action. And it's worked great for me. 
I haven't noticed any issues with handing control back and forth between the apps i use (Audible and Google Music). You can try to downloading another audio app maybe Google Music to use as a test to see if it is an issue with handing control between apps on your phone or if it is an issue with the way Slacker handles the loss of control.

This implies to me that the say command would take control of the audio stream and Audible would respect that because I have the Audible audio notifications setting set to "Pause and then resume playback". However, this does not work on my Verizon G2. Both Audible and the say command speak at the same time. What's interesting is that Audible pauses while my notification tone plays and then resumes when it's done. Thinking Audible is respecting the notification stream, I tried changing the say command to use the notification stream instead of the media stream, but that still doesn't work. 

So far the best I've been able to do is to cause Audible to pause before the say command executes. I accomplished this by using the "Headphone Buttons" plugin set to the "Play" command. Unfortunately, no setting in this plugin can get Audible to resume. So, I either have it pause and then manually resume or I have to listen to both simultaneously. 

Has anyone gotten Tasker to pause/resume the Amazon Audible app?

Brad
Verizon G2, 4.4.2, Tasker 4.3u4m

Marta Hintz

unread,
May 21, 2014, 4:20:52 PM5/21/14
to tas...@googlegroups.com
You are using the "focus" with the say action?

Brad Minion

unread,
May 21, 2014, 4:56:11 PM5/21/14
to tas...@googlegroups.com
Do you mean the "Respect Audio Focus"? I tried that, but I assume since Audible is already using the media channel, Tasker just keeps quiet respecting that Audible has the focus.


On Wed, May 21, 2014 at 3:20 PM, Marta Hintz <lar...@gmail.com> wrote:
You are using the "focus" with the say action?

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

Matt R

unread,
May 21, 2014, 5:07:33 PM5/21/14
to tas...@googlegroups.com
Add a wait (start with 5 seconds) before the say.  You can then try reducing the wait time if it works.

Matt

Brad Minion

unread,
May 22, 2014, 9:46:41 AM5/22/14
to tas...@googlegroups.com
I figured out what my problem was. As Marta suggested, I needed to turn on the "Respect Audio Focus". Apparently, when I tested with this option before my test was invalid and that's why I thought it didn't help. Trying it again today I realized what I was doing wrong in my test. Now with this option on and a valid test (feeling a little stupid...), it worked perfectly.

Thanks for the help.


On Wed, May 21, 2014 at 4:07 PM, Matt R <matthew.r...@gmail.com> wrote:
Add a wait (start with 5 seconds) before the say.  You can then try reducing the wait time if it works.

Matt

--
Reply all
Reply to author
Forward
0 new messages