RPI3 - 7.95.010 - Random Video Issue

shanemarsh28 · January 14, 2017 at 1:46 PM

Hi Guys,

I'm sorry if this has been posted before but I have noticed on the latest version of your Alpha build that Kodi occasionally decides that it will not play any videos. I have attached the logs.

It appears to be an issue with the OMX player as I see in the log:

Code

13:03:51.410 T:1309549472   ERROR: OMXPlayerVideo: Got MSGQ_IS_ERROR(-1) Aborting

The only way to start playing content is to reboot the Pi and then all is well

I initially thought it was a network issue but I can confirm that the network is fully accessible by the PI but it will not play content until it is restarted. Any ideas or help will be appreciated.

Shane

**Iridium** · January 15, 2017 at 8:09 PM Official Post

I had something similar on IMX6 streaming videos from NAS via NFS. The screen would freeze with the round buffer symbol at 100%. I only needed to restart Kodi.

I had been playing around with advancedsettings.xml to improve video caching, but by removing those sections. i.e. going back to default (in my case deleting the whole file) seemed to cure the issue. Could be worth a try.

shanemarsh28 · January 15, 2017 at 8:24 PM

Hi Iridium,

Thanks for your reply. I see what you mean, I too have been struggling to get to grips with the buffering and caching on Kodi 17 but I can't see how those settings could randomly prevent video play?

I have thought of removing the advanced settings.xml file but you'll see from the logs, there is quite a lot in it and I need the Sql settings in there at a minimum so unless I can put those settling elsewhere .. the file has to stay. The only reason I put the caching settings was because video play via the PVR was utterly unwatchable without them.

Shane

**Iridium** · January 15, 2017 at 10:17 PM Official Post

Looking at the Kodi.log it states Kodi 16 whereas hardware and system.log states 7.95.010 which is Kodi 17.

Have you upgraded? If you are running Kodi 17 then you need to be aware that the cache naming convention changed.

It should look like: This is what I tried.

This didn't work:

shanemarsh28 · January 16, 2017 at 11:45 PM

Hi Guys,

I think I might have resolved this now. It turns out I had two tuners within my DVBLINK/Media server that had malfunctioned in a rather horrible way. The tuners looked like they were operating correctly, the system recognised them as present and active but for some reason they could not tune a channel. Difficult to spot as the other two tuners were ok. Only when a dead tuner was selected did Kodi crash over. I also thought the issue described above affected all video playback but it seems that since the tuner issue is now fixed, things have stabalised.

Thanks for your help!

Shane
[hr]

Quote from Iridium

Looking at the Kodi.log it states Kodi 16 whereas hardware and system.log states 7.95.010 which is Kodi 17.

Have you upgraded? If you are running Kodi 17 then you need to be aware that the cache naming convention changed.

It should look like: This is what I tried.

<cache>
<buffermode>1</buffermode>
<memorysize>139460608</memorysize>
<readfactor>20</readfactor>
</cache>

This didn't work:

<cache>
<buffermode>1</buffermode>
<memorysize>209190912</memorysize>
<readfactor>60</readfactor>
</cache>

Display More

I'm running kodi 17 for sure. I also saw kodi 16 in the log files .. I can't explain that. Very strange. I upgraded from 7.0.3 to 7.95.010 about a week ago via a manual upgrade (tar file in upgrade dir). Maybe I need to do a clean build rather than an upgrade at some point just to be sure all is up to date. I'll wait i think till the next version is released. (Must be any day now surely?)

Thanks for the settings above I will check and make sure I'm following the right convention.

Shane