Closed
      
        Bug 894848
      
      
        Opened 12 years ago
          Closed 12 years ago
      
        
    
  
[User Story] [Media Recording] Microphone API
Categories
(Firefox OS Graveyard :: General, defect, P1)
Tracking
(blocking-b2g:koi+, firefox26 fixed)
People
(Reporter: ITsay, Unassigned)
References
Details
(Keywords: dev-doc-needed, Whiteboard: [ucid:audio1, FT:Media-Recording, koi:p1])
      No description provided.
|   | Reporter | |
| Updated•12 years ago
           | 
Blocks: koi-media-recording
|   | Reporter | |
| Updated•12 years ago
           | 
| Comment 1•12 years ago
           | ||
What is this bug about?  I'm trying to understand why it depends on bug 856361.
|   | ||
| Comment 2•12 years ago
           | ||
(In reply to :Ehsan Akhgari (needinfo? me!) from comment #1)
> What is this bug about?  I'm trying to understand why it depends on bug
> 856361.
It's a tracker bug to track completion of the 1st 1.2 user story for Media Recording - https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AtVT90hlMtdSdEd4TVVjWXNfU3ctMlVhWFRrWkpweVE#gid=25. The notes in the user story indicate that Roc identified that we need bug 856361 for collecting/processing raw audio samples to meet this user story's requirements.
| Comment 3•12 years ago
           | ||
Cool.  Please let me know if there is anything specific that I need to be aware of.  Thanks!
|   | Reporter | |
| Updated•12 years ago
           | 
Summary: [User Story] [Media Recording] Microphone and recording API → [User Story] [Media Recording] Microphone API
|   | ||
| Updated•12 years ago
           | 
Depends on: MediaRecording
|   | Reporter | |
| Updated•12 years ago
           | 
blocking-b2g: --- → koi+
|   | ||
| Updated•12 years ago
           | 
No longer depends on: MediaRecording
|   | Reporter | |
| Updated•12 years ago
           | 
Whiteboard: [ucid: audio 1, koi:1] → [ucid: audio 1, FT: Media Recording, koi-p1]
|   | ||
| Updated•12 years ago
           | 
QA Contact: jsmith
|   | Reporter | |
| Comment 4•12 years ago
           | ||
Adjust white board keyword to compile with the format agreed in EPM discussion.
Whiteboard: [ucid: audio 1, FT: Media Recording, koi-p1] → [ucid:audio1, FT:Media-Recording, koi:p1]
|   | ||
| Updated•12 years ago
           | 
Flags: in-moztrap?(jsmith)
|   | ||
| Comment 5•12 years ago
           | ||
Flags: in-moztrap?(jsmith) → in-moztrap+
| Comment 6•12 years ago
           | ||
Ivan, what is the acceptance criteria of audio-capture?
Do we need to support multiple audio-capture source before 9/16?
Flags: needinfo?(itsay)
|   | ||
| Comment 7•12 years ago
           | ||
Fred, what audio types are we capturing with current implementation? We are primarily trying to enabler some third parties to capture audio, so we can check with our partner engg if the current formats supported would cover what they need.
| Comment 8•12 years ago
           | ||
cc alfredo since I'm not familiar with that audio types detail
Flags: needinfo?(ayang)
|   | ||
| Comment 9•12 years ago
           | ||
When you are saying audio types, are you referring to internal mic vs. other available input devices such as bluetooth?
| Updated•12 years ago
           | 
Keywords: dev-doc-needed
|   | ||
| Comment 10•12 years ago
           | ||
(In reply to Fred Lin [:gasolin] from comment #8)
> cc alfredo since I'm not familiar with that audio types detail
I don't know what "audio type" means here.
If my recall is correct, the audio stream (raw data) retrieved via gUM is passed from Android layer and Android layer (audio policy, audio HAL) will do others when input device changed.
Upper layer doesn't need to pay special attention.
|   | ||
| Updated•12 years ago
           | 
Flags: needinfo?(ayang)
|   | Reporter | |
| Comment 11•12 years ago
           | ||
(In reply to Fred Lin [:gasolin] from comment #6)
> Ivan, what is the acceptance criteria of audio-capture?
> Do we need to support multiple audio-capture source before 9/16?
Hi Fred,
No, since it is not supported yet in gecko now, we don't need it before 9/16. It's also need to be discussed if the requirement is necessary.
Flags: needinfo?(itsay)
|   | ||
| Comment 12•12 years ago
           | ||
In terms of what's needed for feature complete - bug 898986 is still needed to be able to call this user story feature complete. bug 914494 is a followup issue, but not needed for feature complete.
|   | Reporter | |
| Comment 13•12 years ago
           | ||
The two open bugs are the follow up bug and we can fix it during the bug fixing period.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
|   | ||
| Comment 14•12 years ago
           | ||
(In reply to Ivan Tsay (:ITsay) from comment #13)
> The two open bugs are the follow up bug and we can fix it during the bug
> fixing period.
bug 898986 isn't a bug - it's part of the feature landing, so I don't agree with that. I'm not granting a FC signoff without that fixed. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|   | Reporter | |
| Comment 15•12 years ago
           | ||
Hi Jason,
The bug 901559 and 913896 are the bugs to resolve the feature of 898986. That's why I think it is completed.
Flags: needinfo?(jsmith)
|   | ||
| Comment 16•12 years ago
           | ||
Looks like the bug in question was already fixed then per Ivan's comments, so this is FC.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Flags: needinfo?(jsmith)
Resolution: --- → FIXED
| Updated•12 years ago
           | 
          status-firefox26:
          --- → fixed
          You need to log in
          before you can comment on or make changes to this bug.
        
Description
•