mythtv-users2 at dwilga-linux1
Jun 13, 2012, 8:11 AM
Post #4 of 4
(315 views)
Permalink
|
|
Re: what does /buffers DDAAAAAAADAAAA et al/ mean?
[In reply to]
|
|
On 6/13/12 10:52 AM, Jim Stichnoth wrote:
> On Tue, Jun 12, 2012 at 8:08 PM, Evuraan <evuraan [at] gmail> wrote:
>> Does the last field mean anything ?
>>
>> 2012-06-12 18:59:26.576987 N Player(2): Waited 205ms for video
>> buffers AAAAAAAAAAAAAA
>> 2012-06-12 18:59:27.860222 N Player(2): Waited 104ms for video
>> buffers AAAAAAAAAAAAAA
>> 2012-06-12 19:34:43.859614 N Player(3): Waited 104ms for video
>> buffers AAAAAAAAAAADDD
>> 2012-06-12 19:34:45.078640 N Player(3): Waited 101ms for video
>> buffers AAAAAAADAAADDA
>> 2012-06-12 19:34:46.242639 N Player(3): Waited 104ms for video
>> buffers AAAAAAAAAAAAAA
>> 2012-06-12 19:34:46.344642 N Player(3): Waited 206ms for video
>> buffers AAAAAAAAAAAAAA
>> 2012-06-12 19:37:29.626656 N Player(5): Waited 107ms for video
>> buffers AAAAAAAAAAADDD
>> 2012-06-12 19:37:29.727892 N Player(5): Waited 208ms for video
>> buffers AAAAAAAAAAADDD
>> 2012-06-12 19:37:29.828364 N Player(5): Waited 309ms for video
>> buffers AAAAAAAAAAADDD
>> 2012-06-12 19:37:29.931076 N Player(5): Waited 411ms for video
>> buffers AAAAAAAAAAADDD
>> 2012-06-12 19:37:30.156585 N Player(5): Waited 104ms for video
>> buffers fLAAAAAAAAAAAA
>> 2012-06-12 19:37:32.827973 N Player(5): Waited 103ms for video
>> buffers DDAAAAAAAAAAAD
>> 2012-06-12 19:37:32.929460 N Player(5): Waited 205ms for video
>> buffers DDAAAAAAAAAAAD
>> 2012-06-12 19:37:33.047083 N Player(5): Waited 102ms for video
>> buffers AAAfAAAAAALAAA
>>
>>
>> $ grep AA myth-tv.log |tail -20 | awk {'print $NF'} | sort -u
>> AAAAAAAAAAAAAA
>> AAAAAAAAAAADDD
>> AAAAAAADAAADDA
>> AAAAAAAfLAAAAA
>> AAAfAAAAAALAAA
>> AAALAAAAAAAAuA
>> ALAAAAAAAAAAff
>> DDAAAAAAAAAAAD
>> DDAAAAAAAAADAA
>> fLAAAAAAAAAAAA
> Those strings are created in the method VideoBuffers::GetStatus(int n)
> which is defined at about line 800 of
> https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmythtv/videobuffers.cpp
> . I don't really know how to interpret the data.
>
Looks like each letter corresponds to the state of a frame buffer. See
the large comment block, starting at line 48:
* available - frames not in use by decoder or display
* limbo - frames in use by decoder but not released for display
* decode - frames in use by decoder and released for display
* used - frames released for display but not displayed or paused
* displayed - frames displayed but still used as a reference frame
* pause - frames used for pause
* finished - frames that are finished displaying but still in use by
decoder
It looks like the OP has lots of A's there, which suggests to me that
the decoder is starved for data. I can only speculate as to reasons for
this (network slowness? capture device slowness?).
--
Dan Wilga "Ook."
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users
|
