LiViD   Oms Sync UserPreferences
 
Help Search Diffs Info Edit Print View
 MoinMoin Wiki   LividWiki   RecentChanges   TitleIndex   WordIndex   Help 

The following 96 words could not be found in the dictionary of 581 words (including 581 LocalSpellingWords) and are highlighted below:
Buffering   Current   Display   Don   Future   M3   Mobility   Much   Rage   Requires   State   Wait   actually   allowing   basic   before   besides   best   better   both   breaks   buffered   buffering   buffers   check   choppy   computers   css   decoded   demand   display   double   drop   dropped   dropping   even   frame   framework   freely   give   great   ie   implemented   instruct   key   known   knows   let   lets   mpeg2dec   much   needless   nothin   options   partial   post   pre   priority   proper   queue   re   really   render   rendered   rendering   repeat   right   say   screens   seconds   senses   similar   slow   smoothness   someone   stamps   streaming   supports   syncronization   systems   than   they   those   thread   till   timestamps   too   updated   verify   wait   waits   want   who   worse   write   written  

Clear message

OpenMediaSystem needs a proper syncronization framework.

Current State

Requires audio output. Here's the basic idea now: (someone please verify)

  1. decode audio and write to output
  2. decode as much video as you can
  3. wait till audio buffers can be written to
  4. repeat
... and on too slow computers we instruct the video decoder to drop some frames (on demand)

No time stamps or nothin! - we do have timestamps, be they're not used at the output right now.

No audio output lets the video display freely... ie, really fast.

Future

Wait for updated Mpeg2Dec support to have a queue of frames to display. (???)

Have time stamps on output frames. Display thread (or whatever) waits till correct time to output frame.

Audio similar. BUT we want to give priority to audio! Don't let audio have breaks if at all possible. Much worse on the senses than some dropped video frames.

frame dropping? pre or post decode? would be better to not decode the frame if possible. allowing both would be best.

partial frame decoding?

Buffering, buffering, buffering, buffering.... needless to say, buffering is the key, buffer those decoded screens like, 10-15 seconds if possible, check memory, and then render, like streaming video on most systems, buffering is good for you, even sound can be buffered.

multiple buffers could also be implemented, i.e. a buffer for the point of css decoding, then the buffer after mpeg2dec before it's actually rendered, even rendering should be double-buffered for smoothness, but, options would be there for card support, I have a great card for DVD, supports all known features besides hardware decoding (ATI Rage 128 Mobility M3) and I have oms working fine, but, it's choppy video with good sound... who knows.

PythonPowered EditText of this page (last modified 2001-05-22 09:39:13)
FindPage by browsing, searching, or an index
Or try one of these actions: LikePages, SpellCheck

MoinMoin 1.108, Copyright © 2000-2001 by Jürgen Hermann

spellread = 0.020
config = 0.000
total = 0.850
imports = 0.480
spellcheck = 0.050
send_page = 0.130