[Aenima99x]

Just curious if anyone else is experiencing a video freeze when you try to seek in a playing video? This is anything longer than just the 10 second skip.
When trying a seek during video playback, the video freezes in-place and stays stuck. Sometimes it will skip to correct place, but can be up to a 20+ second delay. Other times the skip doesn't complete and Kodi must be force-closed.
I'm seeing this in the debug log  -ERROR : CMediaCodecVideoBuffer::ReleaseOutputBuffer error in render(0)

This is happening on multiple Nvidia Shields (2017 & 2019) and also a Jetstream Android device.
I've tried Matrix 19.0, 19.1 and the latest nightly (kodi-20210509-6234ab30-Matrix-arm64-v8a) - all have the same issue.

Debug log - https://paste.kodi.tv/irelucimaj.kodi

Github issue opened here - https://github.com/xbmc/xbmc/issues/19713

[Punchbuggy]

Just curious if anyone else is experiencing a video freeze when you try to seek in a playing video? This is anything longer than just the 10 second skip.
When trying a seek during video playback, the video freezes in-place and stays stuck. Sometimes it will skip to correct place, but can be up to a 20+ second delay. Other times the skip doesn't complete and Kodi must be force-closed.
I'm seeing this in the debug log  -ERROR : CMediaCodecVideoBuffer::ReleaseOutputBuffer error in render(0)
<snip>

Hi. Yeah, I'm seeing this also on my Shield 2017. Only seen the issue since moving to Matrix, and only with specific videos - not all. I haven't interrogated the log, nor attempted to work out the specific codecs in common, but symptoms are as you described with the exception that if I stop the playback, I can restart it from the beginning i.e. don't need to shut-down Kodi.

[Aenima99x]

Just curious if anyone else is experiencing a video freeze when you try to seek in a playing video? This is anything longer than just the 10 second skip.
When trying a seek during video playback, the video freezes in-place and stays stuck. Sometimes it will skip to correct place, but can be up to a 20+ second delay. Other times the skip doesn't complete and Kodi must be force-closed.
I'm seeing this in the debug log  -ERROR : CMediaCodecVideoBuffer::ReleaseOutputBuffer error in render(0)
<snip>

Hi. Yeah, I'm seeing this also on my Shield 2017. Only seen the issue since moving to Matrix, and only with specific videos - not all. I haven't interrogated the log, nor attempted to work out the specific codecs in common, but symptoms are as you described with the exception that if I stop the playback, I can restart it from the beginning i.e. don't need to shut-down Kodi.

Yeah needing to shutdown has been very rare and I'm guessing the video would eventually resume if I left it long enough.
I'm also finding that if I try and start a video from a resume-point, it's a very long delay to start just like on the seek.

[Punchbuggy]

..

Yeah needing to shutdown has been very rare and I'm guessing the video would eventually resume if I left it long enough.
I'm also finding that if I try and start a video from a resume-point, it's a very long delay to start just like on the seek.

That's not my experience - I did try leaving it for a while as a test, but it would stay frozen indefinitely. My guess is that on fast-forward and then pressing Play, Kodi loses its position in the file or alternatively whatever it needs to have kept in sync with to continue normal playback. That's why I suspect it'll be specific to a particular video stream, but I'm yet to test on a variety of containers/formats to test my theory.

Let's hope that your log and description is enough to trigger some thinking with one of the clever cookies here. 

[Filmbuff]

I'm seeing this same behaviour on my Shield Pro 2019 when pausing and resuming playback, it plays for a few seconds, then freezes. To get it working again, I have to either stop the playback or skip to next/previous chapter.

[Stormlord777]

 

Yeah needing to shutdown has been very rare and I'm guessing the video would eventually resume if I left it long enough.
I'm also finding that if I try and start a video from a resume-point, it's a very long delay to start just like on the seek.

That's not my experience - I did try leaving it for a while as a test, but it would stay frozen indefinitely. My guess is that on fast-forward and then pressing Play, Kodi loses its position in the file or alternatively whatever it needs to have kept in sync with to continue normal playback. That's why I suspect it'll be specific to a particular video stream, but I'm yet to test on a variety of containers/formats to test my theory.

Let's hope that your log and description is enough to trigger some thinking with one of the clever cookies here. 

I have the issue with fast farwarding and freezing of the picture alter pressing play. What I noticed was that it was related to aac sound. Other sound formats  did not cause the issue. I created an issue for this https://github.com/xbmc/xbmc/issues/19436
I do not know if it’s the same issue. In the logging it I see that Kodi has an issue with syncing the sound after going from fast forward to play

[Aenima99x]

Yeah needing to shutdown has been very rare and I'm guessing the video would eventually resume if I left it long enough.
I'm also finding that if I try and start a video from a resume-point, it's a very long delay to start just like on the seek.

That's not my experience - I did try leaving it for a while as a test, but it would stay frozen indefinitely. My guess is that on fast-forward and then pressing Play, Kodi loses its position in the file or alternatively whatever it needs to have kept in sync with to continue normal playback. That's why I suspect it'll be specific to a particular video stream, but I'm yet to test on a variety of containers/formats to test my theory.

Let's hope that your log and description is enough to trigger some thinking with one of the clever cookies here. 

I have the issue with fast farwarding and freezing of the picture alter pressing play. What I noticed was that it was related to aac sound. Other sound formats  did not cause the issue. I created an issue for this https://github.com/xbmc/xbmc/issues/19436
I do not know if it’s the same issue. In the logging it I see that Kodi has an issue with syncing the sound after going from fast forward to play

I did see your open issue on Github, but I haven't isolated it to being just aac sound issues so I opened my issue. It's a little worrisome that your issue has been open for 2 months and has no comments from devs at all.

[kcook_shield]

This sounds similar to an issue I had on Shield 17 when kodi upgraded to Matrix.

For me, I found that if I disabled "MediaCodec (surface)" and "MediaCodec" that the issues went away with only downside being that 4K content would then not play correctly.

However, I found a way to "fix" the issue (at least in my situation), so if you find disabling the 2 Mediacodec settings fixes the issues (for all but 4K content), then a way to "fix" is to edit decoderfilter.xml

See:

https://forum.kodi.tv/showthread.php?tid...pid2840569

What I did was to adjust h263, h264 and h265 entries to set a min height of 1090 (if you find other codecs with issues, could try adjusting others as well), and then this allowed me to keep the Mediacodec settings enabled (thus 4K works), but when I watch lower resolutions, these changes prevent Medicodec from applying (as if disabled) which fixed my seek-resume issues I had on non 4K content.

My specific changes in this file were (adding min-height values):

<filter>
<name>OMX.Nvidia.h263.decode</name>
<allowed>true</allowed>
<stills-allowed>false</stills-allowed>
<dvd-allowed>true</dvd-allowed>
<min-height>1090</min-height>
</filter>

<filter>
<name>OMX.Nvidia.h264.decode</name>
<allowed>true</allowed>
<stills-allowed>false</stills-allowed>
<dvd-allowed>true</dvd-allowed>
<min-height>1090</min-height>
</filter>

<filter>
<name>OMX.Nvidia.h265.decode</name>
<allowed>true</allowed>
<stills-allowed>false</stills-allowed>
<dvd-allowed>true</dvd-allowed>
<min-height>1090</min-height>
</filter>

[Punchbuggy]

This sounds similar to an issue I had on Shield 17 when kodi upgraded to Matrix.

For me, I found that if I disabled "MediaCodec (surface)" and "MediaCodec" that the issues went away with only downside being that 4K content would then not play correctly.
...

I can confirm that disabling both MediaCodec settings had not affect on the fast-forward-then-play issue for me - the video still froze (with time indicator resetting to zero). So, with Matrix, I currently need to avoid trying to jump ahead in a video. Sigh.

[dandirk]

I have seen this a few times, last night (2019 shield).  One symptom I had is if I stopped the video, the resume will clock forever and wouldn't start (though I am horribly impatient).

Was insanely frustrating as we were over an hour into the movie.  10min/chapter skip would seem to freeze.  FF would do the same if using x32, x16 seemed to work but eventually froze, but did seem to work...  The image/time would freeze and if I waited a min or 2 it would skip straight to another time/frame and repeat the process.  Hit play, then it eventually started up after another 1-2min.

The 10sec skip even had similar behavior unless I let it play for a bit...

Completely just a guess but seems like some sort of buffer behavior, probably also something to do with the vid/audio sync/timers (pulling guesses out of my you know what...)

The "feeling" I got was the player was trying to perform the action in the buffer only, if that part wasn't there it would basically freeze until it could find it...

Using unraid, wonder if there is some sort of network issue/setting not allowing the access it wants fast enough?

[popy]

Hey guys.

Same issue here on an shield 2019 with kodi 19.1 and zattoo pvr addon.
Also have created an issue here with full debug log: https://github.com/xbmc/inputstream.adaptive/issues/785
and that is referenced to the original from OP.

Same error in the log:

CMediaCodecVideoBuffer::ReleaseOutputBuffer error in render(0)

[popy]

This sounds similar to an issue I had on Shield 17 when kodi upgraded to Matrix.

For me, I found that if I disabled "MediaCodec (surface)" and "MediaCodec" that the issues went away with only downside being that 4K content would then not play correctly.

However, I found a way to "fix" the issue (at least in my situation), so if you find disabling the 2 Mediacodec settings fixes the issues (for all but 4K content), then a way to "fix" is to edit decoderfilter.xml

See:

https://forum.kodi.tv/showthread.php?tid...pid2840569

What I did was to adjust h263, h264 and h265 entries to set a min height of 1090 (if you find other codecs with issues, could try adjusting others as well), and then this allowed me to keep the Mediacodec settings enabled (thus 4K works), but when I watch lower resolutions, these changes prevent Medicodec from applying (as if disabled) which fixed my seek-resume issues I had on non 4K content.

My specific changes in this file were (adding min-height values):

<filter>
<name>OMX.Nvidia.h263.decode</name>
<allowed>true</allowed>
<stills-allowed>false</stills-allowed>
<dvd-allowed>true</dvd-allowed>
<min-height>1090</min-height>
</filter>

<filter>
<name>OMX.Nvidia.h264.decode</name>
<allowed>true</allowed>
<stills-allowed>false</stills-allowed>
<dvd-allowed>true</dvd-allowed>
<min-height>1090</min-height>
</filter>

<filter>
<name>OMX.Nvidia.h265.decode</name>
<allowed>true</allowed>
<stills-allowed>false</stills-allowed>
<dvd-allowed>true</dvd-allowed>
<min-height>1090</min-height>
</filter>

Thanks the partial workaround.
It works for me also with pvr zattoo with two issues:

• pvr zattoo does'nt work in widevine mode because of SW renderer
  
• "zappn" addon which also need's widevine does'nt work (because of SW renderer)
  

So thats no real workaround if no content which needs widevine is working.

Any other hints or ideas.
I am here to test and can reproduce the issue 100%.

Thanks

[AtomicPotato]

I've been having the same issue for the last few days - I hadn't changed anything on the Shield or Kodi; hell I'd barely even changed my undies.

After an hour or so of combing thru logs, Googling, and more weeping than I care to admit, I thought I'd run a Clean Library as there were several directories I'd deleted since the last clean.

During the clean run, the log message box popped up with several NFS errors, bawwing about how it couldn't find some directory and how it's mother never held it as a child.

After the clean run was done, back into TV shows and ran an update to pick up any new shows, then went back into the same show I'd been using as a test ep.

Boom

Worked perfectly. I rewound and ffwd with careless abandon, drunk with audiovisual power.

It's been half an hour or so, still working fine. Probably a fluke, but if this helps just one other person, I may yet avoid my vast karmic imbalance and avoid being reincarnated as a pair of Prince Charles's undies.