Issue with Android DAI contentSourceId in Sample

[gourav...@gmail.com]

Hi There,

I was trying a content (tears-of-steel) from Android DAI Sample. I can see a issue with this content.

Steps:

1. Open tears-of-steel.

2. Let the pre-roll play.

3. Seek to the middle.

4. Mid-roll first frame is stuck. It will not play.

This issue is intermittent.

-Thanks

Gourav

[IMA SDK]

Hi Gourav,

Thank you for reporting this, I attempted to replicate this in an API 30 emulator many times and failed. The only thing I see is the delay from the end of midroll to start of seeked content in the Advanced Example. Are there any steps I am missing?

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[gourav...@gmail.com]

Hi Aryeh,

Your observation was intended I guess because now, if I am trying to play, it is playing for me as well. It is totally random. But it was not playing yesterday for me. I will shoot a video in case, if I find it again.

But can you please ask the team if this ID has some issue or any restriction based on the user-agents ? 

Or else if you have any other HLS + VOD contnentSourceId, please share.

[gourav...@gmail.com]

Hi Aryeh,

Video link: https://drive.google.com/file/d/1X-FF8Gg4-MM5bt50qQDzKonp77NsyhUX/view

I tried it more than 10-20 times.

[IMA SDK]

Hi Gourav,

Thank you for sharing the video. For our reference, could you also share with us the SDK version and the device/OS information you are using here?


Regards,

Sherwin Diesta IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[Gourav Saxena]

Hi Sherwin,

Android-10, MotoG6 India

IMASDK Version v3.22.3

Regards,

Gourav

[IMA SDK]

Hi Gourav,

Thank you for this information. Upon further testing, I was able to replicate the issue successively by seeking back after the first midroll. Please see attached screen recording. I’m using a Pixel 3 XL emulator API 29 / Android 10 for this. With that, I’m going to share this with the team to investigate further. We will let you know once we have our findings.

[Gourav Saxena]

Hi Sherwin,

Thanks for the update.

Regards,

Gourav

[gourav...@gmail.com]

Hi Sherwin,

Please let me know if there is any update or ETA.

[IMA SDK]

Hi Gourav,

Thank you for following up. But I’m afraid there’s no update yet. Let me follow up this with the team and will let you know for any feedback.


Regards,

[Gourav Saxena]

Sure Sherwin.

Regards,

Gourav

[gourav...@gmail.com]

Hi Sherwin,

Please let me know if we have any update on it.

[IMA SDK]

Hi Gourav,

We don't have an update now. We will get back to you as soon as possible.

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[gourav...@gmail.com]

Hi Aryeh,

Any chance that you got any update from the team ? Please let me know.

[IMA SDK]

Hi Gourav,

 

I work with Aryeh.

 

Upon checking, I'm afraid we haven't gotten any feedback from the team. I will follow up this one and will get back to you as soon as possible.

Regards,

Michael Angelo Legaspi IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[IMA SDK]

Hi Gourav,


My teammates confirmed this behavior on 'com.google.android.exoplayer:exoplayer:2.13.2', but it is fixed in 'com.google.android.exoplayer:exoplayer:2.13.3'. I tested it and found the same. Please get back to us if this doesn't fix it for you.

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[Gourav Saxena]

Hi Aryeh,

The crash logs and video which I shared earlier, that was on v2.13.3 itself. Could you please check with the team again ?

Regards,

Gourav

[IMA SDK]

Hi Gourav,

 

I tried to replicate this issue on my end with Pixel 3a API 29 & API 30, Android 10 & 11, but was unable to do so as the video content continues to play after seeking back from the first midroll ad.

Unfortunately, I cannot see the video you shared before on your previous email as I am getting an error that it doesn't exist anymore.

Could you please provide us another screen recording that shows this kind of behavior using this version 'com.google.android.exoplayer:exoplayer:2.13.3'? So I can share and confirm with the team that the issue still exist on the latest version.

Regards,

Michael Angelo Legaspi IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[Gourav Saxena]

Hi Michael,

Please check the video which I shared earlier. I will also try on my end.

Here is the start of the email thread.

I was trying a content (Big Buck Bunny) from Android DAI Sample. I can see an issue with this content.

AssetId: sN_IYUG8STe1ZzhIIE_ksA

Steps:

1. Open tears-of-steel.

2. Let the Ad Play (3 ads)

3. Let it play for 5-10 times.

4. You should see playback error.

Error Log:

2021-04-29 15:20:25.508 27749-27749/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/IMASDK: Received displayContainer message: hide for invalid session id: 0400d24c-5cdf-49f6-8425-e818cc53ac8e

2021-04-29 15:22:14.108 27749-28017/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/ExoPlayerImplInternal: Playback error

      com.google.android.exoplayer2.ExoPlaybackException: Unexpected runtime error

        at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:586)

        at android.os.Handler.dispatchMessage(Handler.java:102)

        at android.os.Looper.loop(Looper.java:193)

        at android.os.HandlerThread.run(HandlerThread.java:65)

     Caused by: java.lang.IllegalStateException

        at com.google.android.exoplayer2.util.Assertions.checkState(Assertions.java:86)

        at com.google.android.exoplayer2.source.hls.HlsMediaChunk.getFirstSampleIndex(HlsMediaChunk.java:319)

        at com.google.android.exoplayer2.source.hls.HlsSampleStreamWrapper.skipData(HlsSampleStreamWrapper.java:638)

        at com.google.android.exoplayer2.source.hls.HlsSampleStream.skipData(HlsSampleStream.java:86)

        at com.google.android.exoplayer2.BaseRenderer.skipSource(BaseRenderer.java:427)

        at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.maybeDropBuffersToKeyframe(MediaCodecVideoRenderer.java:1059)

        at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.processOutputBuffer(MediaCodecVideoRenderer.java:891)

        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.drainOutputBuffer(MediaCodecRenderer.java:1854)

        at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:824)

        at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:947)

        at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:477)

        at android.os.Handler.dispatchMessage(Handler.java:102) 

        at android.os.Looper.loop(Looper.java:193) 

        at android.os.HandlerThread.run(HandlerThread.java:65) 

2021-04-29 15:23:52.016 27749-27749/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/ConstraintLayout: layout_constraintHeight_default="wrap" is deprecated.

    Use layout_height="WRAP_CONTENT" and layout_constrainedHeight="true" instead

Regards,

Gourav

[IMA SDK]

Hi Gourav,

The error that you are bringing up is from this thread  and the bug was filed - https://github.com/google/ExoPlayer/issues/8890. I am asking if the issue that started this thread - midroll frame is stuck when seeking to halfway through VOD Tears of Steel and then seeking a quarter of the way back, this behavior occurs on 'com.google.android.exoplayer:exoplayer:2.13.2', but it is fixed in 'com.google.android.exoplayer:exoplayer:2.13.3'. Please get back to us if this is still an issue for you on the newer version of Exoplayer.

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[gourav...@gmail.com]

Hi Aryeh,

Sorry for the very delayed response.

The video which i shared here. This video was on ExoPlayer v2.13.3 https://drive.google.com/file/d/1X-FF8Gg4-MM5bt50qQDzKonp77NsyhUX/view

Sherwin was able to reproduce it: https://groups.google.com/g/ima-sdk/c/-Q2jekaVWdA/m/CHbbumrjBQAJ

[IMA SDK]

Hi Gourav,

There is confusion about which issue is under discussion. Unfortunately, the link you supplied presently doesn't work. The Exoplayer version 2.13.3 was released on April 14 and Sherwin reproduced it on March 25 . Your original video posted in this link is even older, and we haven't been able to reproduce this issue shown in Sherwin's video on version 2.13.3.

I just now checked on our latest Advanced Example and I couldn't reproduce the issue shown in the video Sherwin created. When I tried version 2.13.2 I was able to reproduce the behavior and no error showed in the logcat. It appears that there may have been that error shown in the logcat in your unreachable video and you were talking about a different issue. Could you supply us with the steps to reproduce what you saw in version 2.13.3?

[Gourav Saxena]

Hi Aryeh,

Thanks for the details. I will definitely check it and will get back to you.

Regards,

Gourav

[gourav...@gmail.com]

Hi Aryeh,

Thanks for the confirmation. I have tried on 2.14.0 and 2.13.3. It works fine. Sorry for the misunderstanding. 

You may close this thread.

[gourav...@gmail.com]

But if possible, may i know that this issue was fixed on ExoPlayer level then what was the root cause of it ?

[IMA SDK]

Hi Gourav,

 

I'm glad to hear that the issue has been resolved. You may want to raise out your question to their support team if you want to know the root cause of it as we don't have a full visibility on their fixes. You may also refer to their release notes for additional information.

Regards,

Michael Angelo Legaspi IMA SDK Team

ref:_00D1U1174p._5004Q2Ems9N:ref

[gourav...@gmail.com]

Hi Michael,

I raised a question to ExoPlayer and got the response that the other ticket (Which has issue on exoplayer and Aryeh has already raised a ticket to exo team) is related to this issue. 

https://github.com/google/ExoPlayer/issues/8984

[IMA SDK]

Hi Gourav,

 

I see that this problem was caused by the HLS implementation of exoplayer and I am glad that it is now fix in their latest updates.

 

Feel free to get back to us if you have any other concerns related to IMA SDK.

Regards,