Open
Bug 1187334
Opened 9 years ago
Updated 2 years ago
Allow other forms of audio capture than tab capture
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
backlog | webrtc/webaudio+ |
People
(Reporter: padenot, Assigned: padenot)
References
(Blocks 1 open bug)
Details
This includes window and browser capture.
Updated•9 years ago
|
backlog: --- → webRTC+
Rank: 19
Priority: -- → P1
Comment 1•9 years ago
|
||
Hey Paul, I'm assigning this to you for now, but I can offload this to someone else if your find yourself getting swamped over the next couple of weeks.
Assignee: nobody → padenot
Comment 2•9 years ago
|
||
Is there someone else who would be good to help with this? Can we write down what's needed to do these? (Window capture might be hard/impossible, and system (screen) audio capture may be tough on some systems.)
Flags: needinfo?(padenot)
Assignee | ||
Comment 3•9 years ago
|
||
We can do full-browser capture pretty easily. It's just a matter of sending the output of the MSG to the capture stream. We cannot capture an arbitrary window that is not the browser by default. It may be possible to do so under specific, rare, circumstances, though. We can capture the system output on Windows Vista+ and Linux/PulseAudio only. It's easier to do that with full duplex, since the plan for full-duplex includes using those "monitoring" streams to feed the AEC, we could just use reuse the stream to feed into the capture stream.
Flags: needinfo?(padenot)
Comment 4•7 years ago
|
||
On Linux with Pulseaudio, the Microphone doorhanger already includes "Monitor of XXX" entries for system audio capture.
Comment 5•7 years ago
|
||
(In reply to Thomas Daede [:TD-Linux] from comment #4) > On Linux with Pulseaudio, the Microphone doorhanger already includes > "Monitor of XXX" entries for system audio capture. to be honest, for normal microphone requests (audio:true) we *shouldn't* be offering those to users, or at least putting them at the bottom of the list of options.
Comment 6•7 years ago
|
||
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Comment 7•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•