Closed
Bug 787812
Opened 12 years ago
Closed 12 years ago
Unable to copy video frames from Camera to Canvas
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-basecamp:-, firefox19 fixed, b2g18+ fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix)
People
(Reporter: gerard-majax, Assigned: gerard-majax)
References
Details
Attachments
(1 file, 1 obsolete file)
877 bytes,
patch
|
gerard-majax
:
review+
akeybl
:
approval-mozilla-b2g18+
|
Details | Diff | Splinter Review |
Trying to make a Gaia app that performs roughly what's described in https://developer.mozilla.org/en-US/docs/Manipulating_video_using_canvas, I'm getting this JavaScript error:
JavaScript Error: "NS_ERROR_NOT_AVAILABLE: Component is not available"
Right when performing the ctx1.drawImage() call.
If my <video> is fed from a local file, not the Nexus S camera, then it works.
Assignee | ||
Comment 1•12 years ago
|
||
Maybe a dupe of bug 778682 ?
Comment 2•12 years ago
|
||
(In reply to Alexandre LISSY from comment #1)
> Maybe a dupe of bug 778682 ?
Possibly, although that's related to WebRTC MediaStreams. Is this a problem in the general case? Mike - Thoughts?
Updated•12 years ago
|
blocking-basecamp: --- → ?
Comment 3•12 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #2)
> (In reply to Alexandre LISSY from comment #1)
> > Maybe a dupe of bug 778682 ?
>
> Possibly, although that's related to WebRTC MediaStreams. Is this a problem
> in the general case? Mike - Thoughts?
Sorry, jsmith--this is outside my realm of knowledge.
Comment 4•12 years ago
|
||
Jonas suggests this isn't a common enough use case to block basecamp. As always, if someone disagrees, please re-nom.
blocking-basecamp: ? → -
Assignee | ||
Comment 5•12 years ago
|
||
Since the blocker landed, I'll retest as soon as my gecko is rebuilt.
Assignee | ||
Comment 6•12 years ago
|
||
My gecko has commit cc33c225c154762e4a036ead13957ffdad4461cb, which is bug 794061, but I'm still getting the issue :(
This is on a Nexus S, if it has a link somehow ...
Comment 7•12 years ago
|
||
bug 794061 only add support of qualcomm's some color formats. Nexus S uses Samsung Exynos processor, it seem that it is necessary to add color format support for Exynos. But I do not know about Exynos...
http://en.wikipedia.org/wiki/Nexus_S
Assignee | ||
Comment 8•12 years ago
|
||
I've been able to successfully add the missing bits for GonkIOSurfaceImage to be able to convert a frame: adding printf_stderr() debug, I can reach the 'return imageSurface.forget()' statement. This is the (trivial) patch attached.
However I'm still getting an error "NS_ERROR_NOT_AVAILABLE: Component is not available".
Assignee | ||
Updated•12 years ago
|
Attachment #673675 -
Flags: review?
Comment 9•12 years ago
|
||
Comment on attachment 673675 [details] [diff] [review]
Making Nexus S video frame copiable.
Trying cjones for review
Attachment #673675 -
Flags: review? → review?(jones.chris.g)
Comment on attachment 673675 [details] [diff] [review]
Making Nexus S video frame copiable.
Sorry, this got lost in a tab earlier today :(.
We don't need the comment here, you can drop that.
Looks fine to me, but I'd like Kan-Ru to take a look.
Attachment #673675 -
Flags: review?(kchen)
Attachment #673675 -
Flags: review?(jones.chris.g)
Attachment #673675 -
Flags: feedback+
Updated•12 years ago
|
Attachment #673675 -
Flags: review?(kchen) → review+
Assignee | ||
Comment 11•12 years ago
|
||
Removing comments, as suggested.
Attachment #673675 -
Attachment is obsolete: true
Attachment #676944 -
Flags: review+
Updated•12 years ago
|
Keywords: checkin-needed
Comment 12•12 years ago
|
||
Comment 13•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 14•12 years ago
|
||
This is not fixed, even if the patch adding colors for Nexus S was needed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 15•12 years ago
|
||
(In reply to Alexandre LISSY :gerard-majax from comment #14)
> This is not fixed, even if the patch adding colors for Nexus S was needed.
Please file a followup bug and link it as a dependency.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Comment 16•12 years ago
|
||
It's strange, I don't see this on b2g-18 tree, confere https://github.com/mozilla/mozilla-central/blob/b2g18/gfx/layers/GonkIOSurfaceImage.cpp
Assignee | ||
Comment 17•12 years ago
|
||
After ensuring this patch is here, and with bug 832745, I still have endianess isues when copying the frame to canvas: red and blue are inverted (on Nexus S at least).
Depends on: 832745
Assignee | ||
Comment 18•12 years ago
|
||
Can someone explain me why the fix that has been landed does not appear in b2g-18 ? It landed before the branch got created.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 19•12 years ago
|
||
Fixing flags. Set the status flags when this happens...
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
status-b2g18:
--- → affected
status-b2g18-v1.0.0:
--- → affected
Resolution: --- → FIXED
Comment 20•12 years ago
|
||
b2g18 was branched in the first week of October IIRC. AFAICT, this never had bb+ or approval to uplift and hence never was. At this point, you'll need to request approval for uplift to the affected branches.
Assignee | ||
Comment 21•12 years ago
|
||
Okay, thanks for this clarification, I was convinced branching got performed much more later, and I have of knowledge of those processes. I'll see with paul and julien, regarding bug 832745, since this bug might be a blocker.
Assignee | ||
Comment 22•12 years ago
|
||
It's now available on http://lissyx.github.com/heart-rate/
Comment 23•12 years ago
|
||
I'm sorry, I wasn't very clear in my last reply. b2g18 was branched off mozilla-beta last month, however, Gecko 18 was branched off m-c to aurora in October, which is when additional uplifting would have begun. Since this landed on m-c in November, it landed on what is now Gecko 19 and never got uplifted to an 18 branch.
Updated•12 years ago
|
Comment 24•12 years ago
|
||
Batch edit: Bugs still affected on b2g18 after 2/13 merge to v1.0.1 branch are affected on v1.0.1 branch.
status-b2g18-v1.0.1:
--- → affected
Updated•12 years ago
|
Comment 25•12 years ago
|
||
Comment on attachment 676944 [details] [diff] [review]
Patch ready to be checked in
This is a very low risk patch as this only introduces a new mapping.
Attachment #676944 -
Flags: approval-mozilla-b2g18?
Updated•12 years ago
|
tracking-b2g18:
--- → +
Updated•12 years ago
|
Attachment #676944 -
Flags: approval-mozilla-b2g18? → approval-mozilla-b2g18+
Comment 26•12 years ago
|
||
status-firefox19:
--- → fixed
Target Milestone: --- → B2G C3 (12dec-1jan)
You need to log in
before you can comment on or make changes to this bug.
Description
•