Thanks, Ravi. I will have a look at updateclock. The crash eventually lies in video decoding thread but before that, I find GetCurrentTime64 returning unreasonable data.
On Thu, Jul 23, 2009 at 11:07 AM, RaviY <yend...@pv.com> wrote: > > Have you tried logging the android_audio_mio.cpp ... function: > AndroidAudioMIOActiveTimingSupport::UpdateClock(). Check if the clock > value is overflowing. > > Also, when you did see a crash, did you get a stack trace, or do you > know where it is crashing? > > -Ravi > > > > On Jul 22, 9:37 pm, Andy Quan <androidr...@gmail.com> wrote: > > My video clip is 80min but it crashed sometime in the mid of somewhere, > and > > othertime after 1-2 round playing. But According to Dave, it was 5 Hrs. I > > thought this might be different due to hardware platform. > > > > Do you have any idea of this? > > > > > > > > On Thu, Jul 23, 2009 at 10:11 AM, RaviY <yend...@pv.com> wrote: > > > > > How long is the "long duration"? > > > > > On Jul 22, 11:08 am, Andy Quan <androidr...@gmail.com> wrote: > > > > Hi all & esp. PV engineers, > > > > I am working on a hard bug found during long duration video playback > by > > > > OpenCORE v1.0 and it hangs mediaserver. > > > > > > I find an extremely old email talking about bugs related to long > duration > > > > avsync playback of opencore by Dave Sparks. It seems to be about > OpenCORE > > > > v1.0. I'd like to know the details about this bug, e.g. description > and > > > root > > > > cause and workarounds? Thanks. > > > > > > Please refer to the following statements by Dave Sparks. Thanks. > > > > On Thu, Feb 26, 2009 at 4:02 PM, Dave Sparks < > davidspa...@android.com > > > >wrote: > > > > > > > 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. > > > > > -- > > > > > Thanks, > > > > > Andy > > > > -- > > Thanks, > > Andy > > > -- 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 android-framework@googlegroups.com To unsubscribe from this group, send email to android-framework+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
