Closed Bug 989891 Opened 11 years ago Closed 7 years ago

Leverage MediaCache for RTSP

Categories

(Firefox OS Graveyard :: RTSP, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: bechen, Unassigned)

Details

No description provided.
Now the rtsp streaming is more stable than before, so we can consider to leverage the MediaCache to re-write the RtspMediaResource. Obviously the MediaCache is designed for byte-based stream, so we will encounter some problems such as: 1. How to store the data into MediaCache? - We should maintain a new table when data comes from RtspChannel. - The table contains: timestamp, frameSize... 2. How to read data from MediaCache? - |RtspMediaSource| access the table above to know how many bytes should be read. 3. How to handle seek operation? - Access the table above. - When seeking forward to an "un-cache" position, the thread should be blocked in MediaCache but we don't know the byte offset of the target time. 4. Rtsp is video/audio separately, how to use MediaCache. - Create 2 MediaCacheStream? 5. Play a realtime stream. - Should we still use MediaCache? Or we can fallback to current implementation? 6. A/V sync - After apply MediaCache, it should be fine if we play a stream without seeking.
blocking-b2g: --- → backlog
We should take the buffer size into consideration while rewriting RtspMediaResource to use MediaCache. Steve Workman has some suggestion here: https://bugzilla.mozilla.org/show_bug.cgi?id=998239#c6
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.