search

amzn / exoplayer-amazon-port

Official port of ExoPlayer for Amazon devices
Apache License 2.0
173 stars 80 forks source link

FTV3 (AFTN) constantly logging "dataspace changed" #49

Closed tmm1 closed 6 years ago

tmm1 commented 6 years ago

I've noticed that on the FTV3, logcat will show these messages over and over again every few seconds:

06-27 13:24:34.165 8651-8812/? D/ACodec: dataspace changed to 0x10100 (R:0(Unspecified), P:1(BT709_5), M:0(Unspecified), T:0(Unspecified)) (R:0(Unspecified), S:1(BT709), T:0(Unspecified))
06-27 13:24:35.806 8651-8812/? D/ACodec: dataspace changed to 0x10100 (R:0(Unspecified), P:1(BT709_5), M:0(Unspecified), T:0(Unspecified)) (R:0(Unspecified), S:1(BT709), T:0(Unspecified))
06-27 13:24:37.496 8651-8812/? D/ACodec: dataspace changed to 0x10100 (R:0(Unspecified), P:1(BT709_5), M:0(Unspecified), T:0(Unspecified)) (R:0(Unspecified), S:1(BT709), T:0(Unspecified))

At the same time, the player will receive INFO_OUTPUT_FORMAT_CHANGED over and over even though nothing is changing.

peddisri commented 6 years ago

Can you confirm the OS Build Version?

tmm1 commented 6 years ago

Can you confirm the OS Build Version?

Fire OS 6.2.1.3 (NS6213/1196)

tmm1 commented 6 years ago

The same logging can be seen directly from the video decoder as well:

07-09 14:22:59.919 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0
07-09 14:23:01.601 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0
07-09 14:23:03.992 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0
07-09 14:23:05.845 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0
07-09 14:23:07.503 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0
07-09 14:23:09.229 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0
07-09 14:23:10.859 3277-25528/? D/AmlogicVideoDecoderAwesome: color_aspects =0, mLastsColorAspects=0
    OMX_EventDataSpaceChanged: data1=10100, data2=65536, color_primaries=0

It keeps firing OMX_EventDataSpaceChanged but the values are all the same and nothing is changing.

tmm1 commented 6 years ago

I'm seeing the same behavior on AFTA Fire OS 6.2.2.1 (NS6221/1326)

peddisri commented 6 years ago

Unable to repro in next OS release.

tmm1 commented 6 years ago

Unable to repro in next OS release.

Great news! Thanks for checking.

tmm1 commented 6 years ago

FYI this is still happening on AFTA after upgrading to NS6222/1537

peddisri commented 6 years ago

Logging is a minor thing. Does the output format change still occur? I was mainly referring to this issue of sending fake output forma changes.

peddisri commented 6 years ago

However, let me check internally if next release meant 6222 or not

rinoshs commented 6 years ago

In our testing, the Player does not get a input/output format change callback from the system when the DataSpaceChanged log line is seen. The log line does not cause additional callbacks to the Player.

The periodic DataSpaceChanged log lines seem spurious.