Audio takes priority over video because a dropped audio buffer is VERY obvious and intrusive, but a dropped video frame is barely noticeable. In general, you want video decoding to be at lower-than-normal priority, because otherwise video decoding could easily make the UI unresponsive (e.g. all of the time would be spent decoding as much video as it can, and there wouldn't be enough CPU left to respond to the 'stop' button, so you'd be stuck)
On Mon, Feb 2, 2009 at 7:38 AM, Andy Quan <[email protected]> wrote: > Hi, > There are previous threads in the group talking about the mechanism of > "scheduler" in pv engine. I am interested in the priority setting for each > node during creation. I find in pv_player_node_registry.cpp: > > * if (KPVMFOMXVideoDecNodeUuid == aUuid) > { > priority = OsclActiveObject::EPriorityLow; > } > else > { > priority = OsclActiveObject::EPriorityNominal; > }* > I dont quite understand why Video Dec node is given lower priority than > others. I have concerns whether this mechanism will make Video easily left > behind when the content is actually a combination of Video+Audio. > > My observation in real PV player performance on real hardware is that when > it is playing stand-alone video, it is going smoothly even with relatively > high resolution. However, it is easily caught by "video can't catch up" > during A/V sync. Even if this warning does not come up, there is still > visible frame drop. At that moment, CPU cost is only around 90% so I am a > bit confused. > > Anybody has comment? > -- > Thanks, > Andy > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
