New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 782492 link

Starred by 9 users

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Add pcm/float32 support to MediaRecorder

Project Member Reported by ttai@google.com, Nov 8 2017

Issue description

Chrome Version       : 62.0.3202.89
OS Version: 

The MediaRecorder requires that all audio be compressed with the Opus codec. It'd be nice to have a way to record lossless audio. PCM/float32 is a good choice, as it's simple and it's what comes out of the microphones natively.

UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36



 

Comment 1 by ttai@google.com, Nov 8 2017

Sadly, I submitted a few changes already before creating this bug. Sorry :(.

crrev.com/c/749864
crrev.com/c/753929
crrev.com/c/749866
Cc: ttai@google.com
Components: Blink>MediaRecording
Labels: -Pri-3 M-64 OS-Android OS-Chrome OS-Mac OS-Windows Pri-2
Owner: mcasas@chromium.org
Status: Assigned (was: Unconfirmed)
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 8 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2ffd605a2b7871dc284c62ebf9836ae963672b83

commit 2ffd605a2b7871dc284c62ebf9836ae963672b83
Author: Terry Tai <ttai@google.com>
Date: Wed Nov 08 06:07:17 2017

Modify MediaRecorderHandler to support PCM.

Adds PCM support to MediaRecorderHandler by "codecs=pcm" support.
Detect the audio codec and then choose the right encoder in the
AudioTrackRecorder. Pass through the codec to the WebmMuxer so that it
can choose the right mkv audio tag.

Bug:  782492 
Change-Id: I80c1742320b0531ca7d2a851d423e3693f0918bd
Reviewed-on: https://chromium-review.googlesource.com/750302
Commit-Queue: Terry Tai <ttai@google.com>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514769}
[modify] https://crrev.com/2ffd605a2b7871dc284c62ebf9836ae963672b83/content/renderer/media_recorder/media_recorder_handler.cc
[modify] https://crrev.com/2ffd605a2b7871dc284c62ebf9836ae963672b83/content/renderer/media_recorder/media_recorder_handler.h
[modify] https://crrev.com/2ffd605a2b7871dc284c62ebf9836ae963672b83/content/renderer/media_recorder/media_recorder_handler_unittest.cc
[modify] https://crrev.com/2ffd605a2b7871dc284c62ebf9836ae963672b83/third_party/WebKit/LayoutTests/fast/mediarecorder/MediaRecorder-isTypeSupported.html

Cc: gov...@chromium.org
Labels: Hotlist-Google M-63
The above fix requires a merge to M63?

Comment 5 by ttai@google.com, Nov 9 2017

Sorry...what does that mean? I'm a noob.
I'm seeing the issue reported on M62 Chrome, so the fix need to be merged to M63 as well?

Comment 7 by ttai@google.com, Nov 9 2017

I don't know standard chrome procedures..., but it'd be insanely amazing if we could get this out sooner than M64.
Labels: -M-63
It's landing on ToT and rolling from it. No merge to 63.
Cc: mcasas@chromium.org chfremer@chromium.org emir...@chromium.org ttay@google.com
 Issue 781744  has been merged into this issue.
Cc: -ttay@google.com jbnesl...@gmail.com
Hey ttai@ did you land all the CLs needed?

Comment 12 by ttai@google.com, Nov 15 2017

Yep. All done. As far as I can tell anyway.
Status: Fixed (was: Assigned)
Marking as Fixed per #12
Cc: niklase@chromium.org
 Issue 658754  has been merged into this issue.

Sign in to add a comment