Closed
Bug 1041884
Opened 10 years ago
Closed 10 years ago
[MADAI][Multimedia] When play video streaming using RTSP Streaming, playback was not smooth.
Categories
(Firefox OS Graveyard :: RTSP, defect)
Firefox OS Graveyard
RTSP
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1032065
People
(Reporter: jaemin1.song, Unassigned)
Details
(Whiteboard: [ LibGLA, dev , B ])
User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 Steps to reproduce: 1. Execute web browser and connect http://goo.gl/FyHFNs 2. Play "Video test link"-> "06. integration - link01" Actual results: When I check RTSP Streaming like above step, I have found that video is showing corrupted frame. ("07. integration - link02" was not occurred problem.) When I checked other RTSP link, I could find same problem. (Because of security problem, I cannot share RTSP link.) And during RTSP streaming playback, video and audio was not smooth. Please confirm this problem. And could you let me know about supported type of RTSP(codec/container)? Thanks.
Reporter | ||
Updated•10 years ago
|
blocking-b2g: --- → 2.0?
Component: General → RTSP
Whiteboard: [ LibGLA, dev , B ]
Comment 2•10 years ago
|
||
Hi Gerry, can you confirm this is still happening?
Flags: needinfo?(gchang)
Comment 3•10 years ago
|
||
Jaemin - Can we get a video for the bug? I'd like to better understand how bad the video frame corruption is visually. Also adding qawanted to see if we can reproduce on Flame 2.0.
Flags: needinfo?(jaemin1.song)
Keywords: qawanted
Comment 4•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #3) > Also adding qawanted to see if we can reproduce on Flame 2.0. Unable to reproduce the bug following STR. Video plays correctly on Flame 2.0. I've also check Buri 2.0 and issue not reproducible either. Tested on: Device: Flame Build ID: 20140721082721 Gaia: b9d19011123487009c80d1200937652d58c434a0 Gecko: d69cd84b6824 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Device: Buri Build ID: 20140721082721 Gaia: b9d19011123487009c80d1200937652d58c434a0 Gecko: d69cd84b6824 Version: 32.0a2 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Reporter | ||
Comment 5•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #3) > Jaemin - Can we get a video for the bug? I'd like to better understand how > bad the video frame corruption is visually. After applying Bug 1032065 patch, video frame does not be corrupted. The patch(Bug 1032065) was not applied yet in MADAI. But after applying the patch, video and audio still was not smooth. If you try to play "03. Hyperlink detection of RTSP feature" in web site, you can confirm it. And I have found two problems. 1. When I play below RTSP link and operate seek function, seek operation was not worked. rtsp://125.141.31.147:554/QE/Coverage20130826/R003_3gp_mpeg4(sp@l1@qvga@452kbps@15fps)_aac-lc(96kbps@32khz@2ch).3gp 2. Below RTSP link was not played. rtsp://125.141.31.147:554/QE/Coverage20130826/R006_3GP_H.263(qCIF@541Kbps@15fps)_AAC-LC(96Kbps@22.05kHz@2ch).3gp When I play it using android device, playback was worked well. To check other codec type, could you let me know RTSP supported type(codec/container)? Thanks.
Flags: needinfo?(jaemin1.song)
Reporter | ||
Updated•10 years ago
|
Summary: [MADAI][Multimedia] When play video streaming using RTSP Streaming, video frame is shown like frame corrupted. → [MADAI][Multimedia] When play video streaming using RTSP Streaming, playback was not smooth.
Comment 6•10 years ago
|
||
Jaemin - If we see a new issue after a certain bug is fixed, I believe it is a better to open a new bug for the issue, as it talks about new problem, which is different the issue we are seeing here. Could you open a new bug for the issue you saw & close this bug out?
Flags: needinfo?(jaemin1.song)
Reporter | ||
Comment 7•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #6) > Jaemin - If we see a new issue after a certain bug is fixed, I believe it is > a better to open a new bug for the issue, as it talks about new problem, > which is different the issue we are seeing here. Could you open a new bug > for the issue you saw & close this bug out? OK. I will close this issue and open new issue. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jaemin1.song)
Resolution: --- → DUPLICATE
Comment 8•10 years ago
|
||
I can't recreate this issue, either. Tested on: Device: Flame Gaia 91986777d0942b63e37fbfeec19d69d6176d6d74 Gecko https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/392054b2e899 BuildID 20140723160206 Version 32.0 Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Flags: needinfo?(gchang)
Comment 9•10 years ago
|
||
Clearing nom since a followup has been filed for the concern raised in comment 7.
blocking-b2g: 2.0? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•