With the given info is hard to tell. Have you checked that the port reconfiguration and the flushes execute correctly ? Those are 2 things that the application always does at the beginning of every playback. If everything looks good in that, probably you should look in lower layers.
- Alex. On Jul 14, 8:55 am, HV <harishv.athr...@gmail.com> wrote: > I added some more debug prints and noticed that the engine state is in > PREPARING state (while it should ideally be in STARTED state). From > the below log, it looks like the Start( ) command didn't complete (coz > I don't see a command complete message for this): > > ************************** > PVLOG:TID(0xcb308):Time=2655:PVMediaOutputNode::DoStart > E/ ( 836): HV: PVMediaOutputNode::SendMioRequest, aRequest = 4 > E/ ( 836): HV: PVMediaOutputNode::SendMioRequest, case EStart > E/ ( 836): HV: PVMediaOutputNode::SendMioRequest, Calling > iMIOControl->Start() > E/PV ( 836): > PVLOG:TID(0xcb308):Time=2655:AndroidSurfaceOutput::Start() called > E/PV ( 836): > PVLOG:TID(0xcb308):Time=2655:PVMediaOutputNode:SendMIORequest: Command > Issued to MIO component, waiting on response... > *************************** > > Any idea what I'm missing here? > > Best regards > HV > > On Jul 14, 3:43 pm, HV <harishv.athr...@gmail.com> wrote: > > > > > RockNCode, > > > Initially I had this wrong as I was updating in ms. Later, I checked > > out the s/w decoder for its implementation (which just slaps the input > > PTS onto the output buffer) and did the same. But this hasn't helped > > either, here is the dump: > > > FetchOutput is complete, nFilledLen = 195840 PTS = 0 > > FetchOutput is complete, nFilledLen = 195840 PTS = 34000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 67000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 100000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 134000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 167000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 200000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 234000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 267000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 300000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 334000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 367000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 400000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 434000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 467000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 500000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 534000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 567000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 600000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 634000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 667000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 700000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 734000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 767000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 800000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 834000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 867000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 900000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 934000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 967000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 1000000 > > FetchOutput is complete, nFilledLen = 195840 PTS = 1034000 > > > On Jul 13, 9:50 pm, RockNCode <alexgarci...@gmail.com> wrote: > > > > Hi. > > > > Have you printed you buffer timestamp values ? I've seen similar > > > issues when there is a problem with AV sync, probably your timestamp > > > resolution does not match PV's (it should be in microseconds). > > > > - Regards. > > > > On Jul 13, 8:02 am, HV <harishv.athr...@gmail.com> wrote: > > > > > Thanks Deva for your response. Yep, there are no issues in the > > > > underlying decoder/driver. If I hold the display from going into > > > > standby, I see prints all the way thru end-of-stream. If there were a > > > > problem with the overlay, then how is it able to display the 1st > > > > frame? Is there a call stack that I can compare against (once the > > > > output buffer has been handed over to PV)? > > > > > HV > > > > > On Jul 12, 8:51 pm, Deva R <r.deva...@gmail.com> wrote: > > > > > > If FillBufferDone keeps coming, its a indication that whole playback > > > > > cycle > > > > > is working (file has been read, decoder has been given > > > > > Emptybuffer/fillbuffer calls, got FillBufferDone)., > > > > > see what happens in overlay, when u post the buffer to > > > > > FillBufferDone., > > > > > > On Mon, Jul 12, 2010 at 3:13 PM, HV <harishv.athr...@gmail.com> wrote: > > > > > > Hi, > > > > > > > I've integrated my MPEG-4 hardware enabled decoder with the PVMF > > > > > > and > > > > > > implemented the necessary OMX calls. The trouble I'm having now is > > > > > > that once I click on the thumbnail within Gallery, the 1st frame > > > > > > shows > > > > > > up, but it stops right there!! I see that my driver/decoder is > > > > > > running > > > > > > in the background generating interrupts and churning out new YUV > > > > > > frames, but Gallery is stuck. I also see that I'm filling in data > > > > > > along with the FillBufferDone callback, but see no visual progress. > > > > > > Any idea what might be missing here? > > > > > > > Thanks in advance > > > > > > HV > > > > > > > -- > > > > > > unsubscribe: > > > > > > android-porting+unsubscr...@googlegroups.com<android-porting%2Bunsubscribe@ > > > > > > googlegroups.com> > > > > > > website:http://groups.google.com/group/android-porting -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
