Closed Bug 911238 Opened 11 years ago Closed 9 years ago

[AudioChannel] Consider to let normal channel play in the background.

Categories

(Firefox OS Graveyard :: AudioChannel, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(tracking-b2g:backlog)

RESOLVED DUPLICATE of bug 1190434
tracking-b2g backlog

People

(Reporter: mchen, Unassigned)

References

Details

(Whiteboard: [AUDIO_COMPETING] [UX_TRIAGED])

Hi all, I want to change the normal channel's behavior so 1. normal channel can be played in the background. (changed) 2. it is allowed to play in background only when there is no any others on playing. (content channel can play in the background when normal is playing later on foreground) 3. normal channel playing in background will be paused by any others on playing. 4. normal channel still can't compete any others channel. Then we can remove the hack of visibility change on Gaia side. May I know all your thought?
We still need to remove sizemodechange hack in b2g:shell.js ;) Any I vote for this change!
Looks good.
Flags: needinfo?(jonas)
Flags: needinfo?(amarchesini)
Component: General → AudioChannel
Flags: needinfo?(amarchesini)
I think this is a UX question. Before we make any more changes, I really think we need to go through and create a comprehensive approach to how we're going to handle audio going forward. I'd really like to be part of those discussions, but ultimately I really defer to the UX team here.
Flags: needinfo?(jonas)
NI UX
Flags: needinfo?(firefoxos-ux-bugzilla)
And to be clear: I think the next step here is to collect the various strategies that we are currently using, the problems that we have with those strategies and capabilities that we have and could add. Then get everyone together and explain these things to the UX team, then have the UX team create a new comprehensive design. Right now I don't think we have documented anywhere all the interactions between speakers, channels, foreground/background, etc. Having that seems like a good first step.
Marco, let's brain storm together to dump all the audio channel following TBD work?
Jonas, that would be very helpful to UX. Audio was high on our list for 1.3, but we didn't have the time for a full re-evaluation of it. Instead, we're focusing on ringtones for 1.3, and want to do a more comprehensive audit and redesign of Audio later (hopefully for 1.4). Having what you describe on hand would be really helpful.
Flags: needinfo?(firefoxos-ux-bugzilla)
https://wiki.mozilla.org/WebAPI/AudioChannels The link as above can be the beginning of what we have now.
Please refer to section of Audio Competing Policy.
Whiteboard: [AUDIO_COMPETING]
[UX_TRIAGED] The ux team is working on the audio competing guideline for gaia, and this issue is important so definitely will be included. And once the gaia audio management is enabled, we should be able to let/not to let the normal channel to play in the background, depends on what's the finial ux decision.
Whiteboard: [AUDIO_COMPETING] → [AUDIO_COMPETING] [UX_TRIAGED]
blocking-b2g: --- → backlog
Flags: needinfo?(jelee)
Depends on: NewAudioChannel
Hi there, I will upload 2.2 Sound spec to Bug 1068219 - (2.2 UX) Sound Design Updates once it's ready around late November, thanks for your patience!
Flags: needinfo?(jelee)
blocking-b2g: backlog → ---
No longer depends on: NewAudioChannel
Priority: -- → P2
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.