Closed
Bug 1083413
Opened 10 years ago
Closed 10 years ago
[Media Recording API] Error when recording mp4 video file
Categories
(Core :: Audio/Video: Recording, defect)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
b2g-v2.1 | --- | affected |
b2g-v2.2 | --- | unaffected |
People
(Reporter: ychung, Unassigned)
References
Details
(Whiteboard: [2.1-flame-test-run-3])
Attachments
(2 files)
Description:
When the user tries to record a mp4 video file, [object RecordErrorEvent] message appears. The user is unable to record the file.
Repro Steps:
1) Update a Flame device to BuildID: 20141015001201.
2) Go to http://mozilla.github.io/qa-testcase-data/webapi/mediarecorder/
3) Setup a stream for media recorder by file with:
** File: gizmo.mp4
** Media Type: video
** Mime Type: video/mp4
4) Select play on both media controls that appear.
5) Select start recording.
-> [object RecordErrorEvent] message appears.
6) Select stop recording.
7) Play blob URL generated.
Actual:
Unable to play the video. "Video can't be played because the file is corrupted".
Expected:
No error message appears. The video should playback what was recorded.
Environmental Variables:
Device: Flame 2.1
BuildID: 20141015001201
Gaia: 379ea4c9dd6d3f8ca2f79ce59c15f6afe6e557c3
Gecko: 4853208cb48a
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/11583/
See attached: logcat, screenshot
Reporter | ||
Comment 1•10 years ago
|
||
This issue does NOT reproduce on Flame 2.2:
Flame 2.2
Device: Flame 2.2 Master KK (319mb) (Full Flash)
Build ID: 20141015040201
Gaia: 5f1f0960ae9d22acf2a324ad37a48174d6df87f6
Gecko: 62f0b771583c
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 36.0a1 (Master)
Firmware Version: v180
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
The video records and plays back properly. This issue is verified fixed on Flame 2.2 on Bug 997593
=================================================
This issue also reproduces on flame 2.0:
Flame 2.0
Environmental Variables:
Device: Flame 2.0 KK (319mb) (Full Flash)
Build ID: 20141015000206
Gaia: c6c6116ca225c2c934220ae6867e5a3256d65e00
Gecko: 24a2aa6bf1c4
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 32.0 (2.0)
Firmware Version: v180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Unable to play the video. "Video can't be played because the file is corrupted".
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Reporter | ||
Comment 2•10 years ago
|
||
Comment 3•10 years ago
|
||
Hi John,
Is it possible to uplift the patch that fixed mp4 file trasncoding?
Comment 4•10 years ago
|
||
Sure, as long as bug 1067422 will also be uplifted. But is it wise to do so after 2.1 FC? :-)
Comment 5•10 years ago
|
||
[Blocking Requested - why for this release]:
Nominating this 2.0? since it was nominated before on 1.4 but got pushed to backlog.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 6•10 years ago
|
||
Hi Blake:
Could you please help check this issue first?
Thanks!!
Shawn
Flags: needinfo?(bwu)
Comment 7•10 years ago
|
||
(In reply to John Lin [:jolin][:jhlin] (PTO Oct. 9 - Oct. 15) from comment #4)
> Sure, as long as bug 1067422 will also be uplifted. But is it wise to do so
> after 2.1 FC? :-)
Correction: it's bug 1067442.
Comment 8•10 years ago
|
||
(In reply to shawn ku [:sku] from comment #6)
> Hi Blake:
> Could you please help check this issue first?
> Thanks!!
> Shawn
Sorry. I am not familiar with recording.
John should be the proper person you should ask help for.
Flags: needinfo?(bwu) → needinfo?(jolin)
Comment 9•10 years ago
|
||
(In reply to Blake Wu [:bwu][:blakewu] from comment #8)
> (In reply to shawn ku [:sku] from comment #6)
> > Hi Blake:
> > Could you please help check this issue first?
> > Thanks!!
> > Shawn
> Sorry. I am not familiar with recording.
> John should be the proper person you should ask help for.
While the risk of uplifting is not very high, this bug is urgent enough to 'block' 2.0 IMHO.
The test case, IIUC, uses Mozilla-only API (mozCaptureStreamUntilEnded) to achieve transcoding. It seems to me that it's unlikely that apps/pages following current media capture standard will do this.
I would suggest not to uplift the fix to 1.4/2.0/2.1, unless we think transcoding is an important feature of media recording.
Randy, what do you think?
Flags: needinfo?(jolin) → needinfo?(rlin)
Comment 10•10 years ago
|
||
(In reply to John Lin [:jolin][:jhlin] (PTO Oct. 9 - Oct. 15) from comment #9)
> (In reply to Blake Wu [:bwu][:blakewu] from comment #8)
> > (In reply to shawn ku [:sku] from comment #6)
> > > Hi Blake:
> > > Could you please help check this issue first?
> > > Thanks!!
> > > Shawn
> > Sorry. I am not familiar with recording.
> > John should be the proper person you should ask help for.
>
> While the risk of uplifting is not very high, this bug is urgent enough to
> 'block' 2.0 IMHO.
Sorry, I mean 'NOT urgent enough...'
> The test case, IIUC, uses Mozilla-only API (mozCaptureStreamUntilEnded) to
> achieve transcoding. It seems to me that it's unlikely that apps/pages
> following current media capture standard will do this.
> I would suggest not to uplift the fix to 1.4/2.0/2.1, unless we think
> transcoding is an important feature of media recording.
> Randy, what do you think?
Comment 11•10 years ago
|
||
I agree with you. mozCaptureStreamUntilEnded is mozilla specific API and this usage(transcoding) is rare on mobile device.
Flags: needinfo?(rlin)
Comment 12•10 years ago
|
||
Per comment 9 from John, suggest not to uplift the fix to 1.4/2.0/2.1.
denominate 2.0 ?.
blocking-b2g: 2.0? → ---
Comment 13•10 years ago
|
||
Since bug 1067442 is closed, can we retest whether this still reproduces, and if not close the bug? Thanks!
Keywords: qawanted
Comment 14•10 years ago
|
||
Bug 1067442 hasn't done anything on v2.0 nor v2.1, which are the affected branches of this bug. In other words, bug 1067442 has nothing to do with this bug.
Also we currently can't test this because the test URL at comment 0 is obsolete. We have an updated URL which is http://mozilla-b2g.github.io/qa-testcase-data/webapi/mediarecorder/MediaRecorder.html but links on that page don't work so we can't test it.
Flags: needinfo?(npark)
Comment 15•10 years ago
|
||
Sorry for my oversight. The policy for media bug now is that unless it's a show-stopper, we are no longer fixing the bug for 2.0 and 2.1. I think it's most reasonable to close this bug and raise a new one when it appear again. pinging hema for feedback.
Flags: needinfo?(npark) → needinfo?(hkoka)
Comment 16•10 years ago
|
||
We are not fixing bugs in 2.1 unless it is a super-critical issue. This particular one should be triaged for a release by Steven's team who own the audio/video recording area now. Ni'ing him.
Thanks
hema
Flags: needinfo?(hkoka) → needinfo?(slee)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(slee)
Resolution: --- → WONTFIX
Updated•10 years ago
|
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•