Post

1 follower Follow
7
Avatar

Pausing audio instead of audio ducking

If you are listening to music then ducking makes sense. What if you want to listen to a podcast or an audio book while you are training? Wouldn't pausing the track make more sense, and resuming it when the audio cues stop?

Either you'd need to use an Android intent to make the player stop and restart (I mean the players that users select by touching the music icon (two quavers) top right in the Android app), -or- you would need to add your own Runkeeper music-playing service. Probably you don't want to do that, so if none of the currently supported players support it, look for one that does and support it.

Settings screen could then have an option "prefer pause over ducking" that would pause if possible but revert to audio ducking otherwise.

Tim

Please sign in to leave a comment.

5 comments

0
Avatar

Until about 2 weeks ago my podcasts via Stitcher on Android behaved as described here, pausing rather than reducing in volume during Runkeeper progress updates/audio cues.
Now the audio cues from Runkeeper stomp on top of the podcast.
I'll either figure out how to get back to pausing, or turn off the audio cues.

AndyP 0 votes
Comment actions Permalink
0
Avatar

Thanks for commenting Andy. Since raising this feature request I have been using MortPlayer on Android 6.0.1 and it does already do what I want, i.e. when Runkeeper makes an audio announcement, the audio book I am listening to is paused and resumes from the same place after the announcement. Not sure what mechanism is in play here - perhaps there is a broadcast when the announcement is made and another when it finishes that MortPlayer (and other registered receivers) pick up in order to effect the pause/resume of the audio track. Andy, it is possible that a software update has caused the change you have seen. You might want to try another player (like MortPlayer) to see whether you get the same results as I do, in which case it's not a Runkeeper update that has caused this. Which version of Runkeeper are you using BTW?

Tim 0 votes
Comment actions Permalink
0
Avatar

I am using the Basic (not premium). MortPlayer looks to specialize in books, but Google just added Podcasts which is what I use. Tonight I worked out and Runkeeper paused (not talked over) the podcast from Google Music.
I'm switching to Google over Sticher on account of this, at least for working out. Google doesn't yet have enough Podcasts to become my morning news fix.

AndyP 0 votes
Comment actions Permalink
0
Avatar

Thanks Andy! Okay, well since we have identified two players for which this feature request is actually already working, I guess we should mark this feature request as resolved... if only there were a way to do that - ha! I am going to "unfollow" it and leave it here as a zombie. Thanks again for your comments. - Tim

Tim 0 votes
Comment actions Permalink
0
Avatar

Hi Tim & others.
I reached out to Runkeeper feature request and they had a great answer and this is being released soon.
Snippet from their response below.
-Andy

Our apologies for the trouble, but the change to Audio Ducking behavior was intentional per Google guidelines and for Android Auto program compliance. For system beeps and other short notification sounds for which silence is not required, Stitcher now properly lowers its output volume by 90% for the duration of the sound rather than pausing and resuming playback. This ensures the active app's audio and media button focus does not change or become indeterminate when handling phone calls or performing voice command input. However, many users have requested a Stitcher Setting to use the older pause-ducking style behavior, especially when using the turn-by-turn navigation in Google Maps, which performs its announcements without requiring silence from all other audio applications.

Stitcher 3.5.8 includes a new Stitcher Setting to Use Pause Ducking rather than volume-based ducking for notifications and other audible interruptions such as turn-by-turn map navigation. In addition, this upcoming release includes a new auto-caching feature intended to improve playback reliability with 3rd-party direct-streaming providers. Stitcher will now automatically cache the current and next episodes in the playlist, in advance whenever possible, so that playback will not be interrupted by an unreliable network or an incompatible 3rd-party audio server configuration.

AndyP 0 votes
Comment actions Permalink