When the player engine issues a "SetDataSourcePosition" to the source node with a iTargetNPT, it is the source node's responsibility to set the iActualNPT and the iActualMediaDataTS. It is based on these values that the player engine will (i) set the clock value, and (ii) decide what frames to skip.
I suggest looking at the mp4 parser node to see how the APIs are being used. -Ravi On Feb 15, 10:17 am, "[email protected]" <[email protected]> wrote: > I have integrated WMV fileformat into opencore. > The normal playback is working fine, but when I try to seek the video > forward or reverse, most of the time > video freezes and takes around 3-4 secs to come up, which is > unacceptable. > Is it the issue with application or the engine or is it some > scheduling issue. > Do the source node needs to inform something to the engine. > > On Feb 14, 7:48 pm, rktb <[email protected]> wrote: > > > Please furnish more details. > > > On Feb 14, 5:09 am, sandy boss <[email protected]> wrote: > > > > I tried implementing seek during WMV playback.It's taking more time and > > > many > > > a times video freezes but the audio is seeked properly. > > > Can any one tell if the it is from player engine side or some scheduling > > > issue and > > > how to tackle it. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
