Closed
Bug 923038
Opened 11 years ago
Closed 11 years ago
[Meta][User Story] Record video clip from standard API (OmxEncoder + MP4) for Camera / Camcorder
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
1.4 S1 (14feb)
People
(Reporter: ITsay, Assigned: ITsay)
References
Details
(Keywords: meta, Whiteboard: [ucid:multimedia3, 1.4, ft:multimedia-platform][NPOTB])
This is the user story meta bug for media recording v1.3
Assignee | ||
Comment 1•11 years ago
|
||
Provide Encoding support for OmxEncoder + MP4, VP8 + WebM.
blocking-b2g: --- → 1.3+
Whiteboard: [ucid:mediacording3, ft:media-recording, 1.3:p1]
Assignee | ||
Updated•11 years ago
|
Blocks: 1.3-media-recording
Updated•11 years ago
|
Keywords: meta
Whiteboard: [ucid:mediacording3, ft:media-recording, 1.3:p1] → [ucid:mediacording3, ft:media-recording, 1.3:p1][NPOTB]
Assignee | ||
Comment 2•11 years ago
|
||
Change the title to reflect the correct user stories
Summary: [Meta][User Story] Video recording standard API → [Meta][User Story] Video encoder and interface for media recording
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Target Milestone: --- → 1.3 Sprint 6 - 12/6
Updated•11 years ago
|
Flags: in-moztrap?(pyang)
Assignee | ||
Comment 3•11 years ago
|
||
(In reply to Ivan Tsay (:ITsay) from comment #1) > Provide Encoding support for OmxEncoder + MP4, VP8 + WebM. Update the implementation scope to be on video encoding support for OmxEncoder(audio/video) + MP4. So far we narrow down the scope for b2g only. VP8+WebM is mainly for desktop.
Comment 4•11 years ago
|
||
Per discussion offline - targeted features don't block, so we don't need to continue blocking on this.
blocking-b2g: 1.3+ → -
Comment 5•11 years ago
|
||
Moved out of scope for 1.3, so pulling from tracker bug.
No longer blocks: 1.3-media-recording
Assignee | ||
Comment 6•11 years ago
|
||
Reset target milestone since this on is moved to v1.4
blocking-b2g: - → ---
Target Milestone: 1.3 Sprint 6 - 12/6 → ---
Comment 7•11 years ago
|
||
Update whiteboard tag to follow format [ucid:{id}, {release}:p{1,2}, ft:{team-id}]
Whiteboard: [ucid:mediacording3, ft:media-recording, 1.3:p1][NPOTB] → [ucid:mediacording3, 1.3:p1, ft:media-recording][NPOTB]
Assignee | ||
Comment 8•11 years ago
|
||
Update to P2 in whiteboard since this is target feature.
Whiteboard: [ucid:mediacording3, 1.3:p1, ft:media-recording][NPOTB] → [ucid:mediacording3, 1.3:p2, ft:media-recording][NPOTB]
Updated•11 years ago
|
Blocks: 1.4-multimedia
Updated•11 years ago
|
Whiteboard: [ucid:mediacording3, 1.3:p2, ft:media-recording][NPOTB] → [ucid:mediacording3, 1.4:p1, ft:multimedia-platform][NPOTB]
Updated•11 years ago
|
Whiteboard: [ucid:mediacording3, 1.4:p1, ft:multimedia-platform][NPOTB] → [ucid:multimedia3, 1.4:p1, ft:multimedia-platform][NPOTB]
Updated•11 years ago
|
Summary: [Meta][User Story] Video encoder and interface for media recording → [Meta][User Story] Record video clip from standard API (OmxEncoder + MP4)
Assignee | ||
Comment 9•11 years ago
|
||
All the dependency bugs are targeted to be finished by the end of sprint 2
Target Milestone: --- → 1.3 C2/1.4 S2(17jan)
Comment 10•11 years ago
|
||
Closing - all dependent eng. bugs are fixed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
Paul - gUM camera support isn't needed to test this feature (and isn't related actually) - gUM video isn't captured in MP4. You need to use media streams derived from mp4 files.
No longer depends on: 853356
Comment 12•11 years ago
|
||
Hi Jason, Although it can be tested by media stream instead, it doesn't make any sense if we commit to have video recording without camera enabled.
Comment 13•11 years ago
|
||
(In reply to Paul Yang [: pyang] from comment #12) > Hi Jason, > Although it can be tested by media stream instead, it doesn't make any sense > if we commit to have video recording without camera enabled. There's a separate intention being tracked here for this user story that's not dependent on camera support. Product should be able to clarify the need.
Comment 14•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #13) > (In reply to Paul Yang [: pyang] from comment #12) > > Hi Jason, > > Although it can be tested by media stream instead, it doesn't make any sense > > if we commit to have video recording without camera enabled. > > There's a separate intention being tracked here for this user story that's > not dependent on camera support. Product should be able to clarify the need. Agree that product should clarify. ni? Marvin
Flags: needinfo?(mkhoo)
Comment 15•11 years ago
|
||
agree this verification should not have any dependency.
Flags: needinfo?(mkhoo)
Assignee | ||
Comment 16•11 years ago
|
||
Assign to EPM for tracking purpose.
Assignee: nobody → itsay
Whiteboard: [ucid:multimedia3, 1.4:p1, ft:multimedia-platform][NPOTB] → [ucid:multimedia3, 1.4, ft:multimedia-platform][NPOTB]
Target Milestone: 1.3 C2/1.4 S2(17jan) → 1.4 S1 (14feb)
Comment 17•11 years ago
|
||
Sadly with the existence of bug 973504, this doesn't achieve a FC signoff, so based on our new FC signoff criteria, this user story is being reopened.
Assignee | ||
Comment 18•11 years ago
|
||
Move to v1.5 due to feature de-scoping in v1.4.
Whiteboard: [ucid:multimedia3, 1.4, ft:multimedia-platform][NPOTB] → [ucid:multimedia3, 1.5, ft:multimedia-platform][NPOTB]
Assignee | ||
Updated•11 years ago
|
Target Milestone: 1.4 S1 (14feb) → ---
Assignee | ||
Comment 19•11 years ago
|
||
Recover the target milestone field
Target Milestone: --- → 1.4 S1 (14feb)
Comment 20•11 years ago
|
||
(In reply to Ivan Tsay (:ITsay) from comment #18) > Move to v1.5 due to feature de-scoping in v1.4. This isn't what we discussed offline. We weren't pulling video recording from 1.4 unless there's a regression risk present in the feature currently, which isn't the case based on the analysis I gave.
Flags: needinfo?(itsay)
Assignee | ||
Comment 21•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #20) > (In reply to Ivan Tsay (:ITsay) from comment #18) > > Move to v1.5 due to feature de-scoping in v1.4. > > This isn't what we discussed offline. We weren't pulling video recording > from 1.4 unless there's a regression risk present in the feature currently, > which isn't the case based on the analysis I gave. If we want to claim this feature complete in v1.4, we need the full QA test on this. We cannot say it is completed with code landed only. By the decision made in drivers meeting, for the feature that has been fully landed, we just leave it and turn it off. But it does not mean the QA will put effort to test on it. Actually I am confused if QA will still cover the test for the landed feature other than DSDS and QC blockers.
Flags: needinfo?(itsay) → needinfo?(jsmith)
Assignee | ||
Comment 22•11 years ago
|
||
If the feature will be tested, We shall keep this one in v1.4 as it is a fully landed feature before de-scoping.
Comment 23•11 years ago
|
||
(In reply to Ivan Tsay (:ITsay) from comment #21) > (In reply to Jason Smith [:jsmith] from comment #20) > > (In reply to Ivan Tsay (:ITsay) from comment #18) > > > Move to v1.5 due to feature de-scoping in v1.4. > > > > This isn't what we discussed offline. We weren't pulling video recording > > from 1.4 unless there's a regression risk present in the feature currently, > > which isn't the case based on the analysis I gave. > > If we want to claim this feature complete in v1.4, we need the full QA test > on this. We cannot say it is completed with code landed only. By the > decision made in drivers meeting, for the feature that has been fully > landed, we just leave it and turn it off. But it does not mean the QA will > put effort to test on it. Actually I am confused if QA will still cover the > test for the landed feature other than DSDS and QC blockers. No, that's not what we decided on the drivers meeting. If the feature has already fully landed & it does not have regression risk to rest of the product (self-contained), then it can stay in the release until proven otherwise. Paul is actively testing this & I'll be assisting, so this is being looked into. However, I don't think the argument presented is compelling to currently argue this out of the release, as we need proof of either severe bugs or regressions to turn off the feature if it's fully landed. This stays in 1.4 as it stands.
Flags: needinfo?(jsmith)
Updated•11 years ago
|
Whiteboard: [ucid:multimedia3, 1.5, ft:multimedia-platform][NPOTB] → [ucid:multimedia3, 1.4, ft:multimedia-platform][NPOTB]
Comment 24•11 years ago
|
||
Turns out the issue I saw wasn't related to Video recording, so closing the story out again.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
Summary: [Meta][User Story] Record video clip from standard API (OmxEncoder + MP4) → [Meta][User Story] Record video clip from standard API (OmxEncoder + MP4) for Camera / Camcorder
Updated•8 years ago
|
Flags: in-moztrap?(pyang)
You need to log in
before you can comment on or make changes to this bug.
Description
•