The audio MIO counts the number of audio samples output to the audio sink and divides by the frame rate. This value is adjusted by the latency reported by the audio sink (which ultimately comes from the audio HAL plus the latency in the software mixer engine). For some reason with OpenCore 1.0, we could never reconcile the real hardware latency with the presentation of video frames in the MIO, so we had to add a fudge factor. We are hoping that OpenCore 2.0's new media playback clock will resolve this issue.
I think there is an outstanding bug related to the playback clock and long streams, but I seem to recall that was 5 hours. For most mobile devices, the battery is going to die long before that if the DSP and backlight are powered up the entire time. On Feb 25, 6:39 pm, hdandroid <[email protected]> wrote: > What is the AVsync algorithm for AVplayback on cupcake? I think it > estimates the position of PCM playback on hardware. There might be > audio or video start up latencies that needs to be compensated. Can > somebody give a high level overview of the logic. What is the size or > duration of PCM buffer used? Does this logic work well for long > duration clips (1Hr+). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
