Videos suddenly starts stuttering and shutting down

[Phobios]

I cannot recall having made any upgrades recently, but I may be wrong.

The issue is when I try to play videos, from 720p to 4k, they will eventually start buffering and then shutting down, sometimes hanging the entire system. 4k videos are shutting down almost immediately, while 720p and 1080p takes a while.

This has never happened before, and I’ve been very happy with my Vero so far.

This is the relevant part of the log. If you need more, let me know.

2019-12-21 18:36:19.010 T:4066172928  NOTICE: VideoPlayer::OpenFile: nfs://<username>@<ip-address>:video.mkv
2019-12-21 18:36:19.012 T:3558863584  NOTICE: Creating InputStream 
2019-12-21 18:36:23.032 T:3558863584  NOTICE: Creating Demuxer                            
2019-12-21 18:36:23.339 T:3558863584  NOTICE: Opening stream: 0 source: 256
2019-12-21 18:36:23.340 T:3558863584  NOTICE: CVideoPlayerVideo::OpenStream - Creating codec: 173                                   
2019-12-21 18:36:23.340 T:3558863584  NOTICE: Creating video thread                                
2019-12-21 18:36:23.340 T:3491750624  NOTICE: running thread: video_thread
2019-12-21 18:36:23.341 T:3558863584  NOTICE: Opening stream: 1 source: 256
2019-12-21 18:36:23.341 T:3558863584  NOTICE: Finding audio codec for: 86060
2019-12-21 18:36:23.342 T:3558863584  NOTICE: Creating audio thread    
2019-12-21 18:36:23.342 T:3483357920  NOTICE: running thread: CVideoPlayerAudio::Process()
2019-12-21 18:36:23.342 T:3558863584  NOTICE: Opening stream: 3 source: 256
2019-12-21 18:36:23.358 T:3483357920  NOTICE: Creating audio stream (codec id: 86060, channels: 8, sample rate: 48000, pass-through)
2019-12-21 18:36:23.360 T:3483357920   ERROR: CAEStreamInfo::GetDuration - invalid stream type
2019-12-21 18:36:23.623 T:3491750624   ERROR: Previous line repeats 1 times.         
2019-12-21 18:36:23.623 T:3491750624  NOTICE: CAMLCodec::OpenDecoder - using V4L2 pts format: 64Bit
2019-12-21 18:36:49.283 T:3483357920  NOTICE: CVideoPlayerAudio::Process - stream stalled pts:25.299 clock:25.347
2019-12-21 18:36:55.642 T:3491750624   ERROR: CAMLCodec::AddData: packet to big: 131493, probably corrupted
2019-12-21 18:36:57.693 T:4066172928   ERROR: Previous line repeats 1522 times.
2019-12-21 18:36:57.694 T:4066172928  NOTICE: CVideoPlayer::CloseFile()
2019-12-21 18:36:57.695 T:3491750624   ERROR: CAMLCodec::AddData: packet to big: 131493, probably corrupted
2019-12-21 18:36:57.695 T:4066172928  NOTICE: VideoPlayer: waiting for threads to exit
2019-12-21 18:36:57.754 T:3558863584  NOTICE: CVideoPlayer::OnExit()       
2019-12-21 18:36:57.755 T:3558863584  NOTICE: Closing stream player 1  
2019-12-21 18:36:57.755 T:3558863584  NOTICE: Waiting for audio thread to exit        
2019-12-21 18:36:57.755 T:3483357920   ERROR: Got MSGQ_ABORT or MSGO_IS_ERROR return true
2019-12-21 18:36:57.755 T:3483357920  NOTICE: thread end: CVideoPlayerAudio::OnExit()                                                                                           
2019-12-21 18:36:57.756 T:3558863584  NOTICE: Closing audio device
2019-12-21 18:36:57.791 T:3558863584  NOTICE: Deleting audio codec
2019-12-21 18:36:57.800 T:3558863584  NOTICE: Closing stream player 2      
2019-12-21 18:36:57.800 T:3558863584  NOTICE: waiting for video thread to exit                   
2019-12-21 18:36:57.801 T:3491750624   ERROR: Got MSGQ_ABORT or MSGO_IS_ERROR return true
2019-12-21 18:36:57.802 T:3491750624  NOTICE: thread end: video_thread    
2019-12-21 18:36:57.802 T:3558863584  NOTICE: deleting video codec         
2019-12-21 18:36:57.862 T:3558863584  NOTICE: Closing stream player 3       
2019-12-21 18:36:57.989 T:4066172928  NOTICE: VideoPlayer: finished waiting
2019-12-21 18:36:57.990 T:4066172928  NOTICE: CVideoPlayer::CloseFile()                   
2019-12-21 18:36:57.990 T:4066172928  NOTICE: VideoPlayer: waiting for threads to exit
2019-12-21 18:36:57.990 T:4066172928  NOTICE: VideoPlayer: finished waiting

[bmillham]

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

• enable debug logging at settings->system->logging

• reboot the OSMC device

• reproduce the issue

• upload the log set either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

• publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

[Phobios]

Here is the link to the full logs. When I reproduced it now the video never shut down, but was just constantly buffering. Not as bad as yesterday though. Lots of ERROR: CAMLCodec::AddData: packet to big: 530939, probably corrupted in the log.
https://paste.osmc.tv/pehutofapa

[fzinken]

@Phobios

just constantly buffering

Check your network with iperf3? Not that something changed in your WLAN that causes this issues?

[Phobios]

I copied the same video file locally to my vero and the video was playing just fine. A couple of weeks back I had switched from using a wired to connection to a wireless, and it worked just fine initially.

I just tried playing the same video from another device (a Samsung tablet, also wireless obviously) and it worked without any of the issues I suffered on the Vero.

[fzinken]

@Phobios

from using a wired to connection to a wireless,

[How To] Check Network Performance with iperf3

Sometimes it is important to check the network performance between your OSMC Device and the device providing your media (NAS, Server, PC). Especially when you are connected via wireless the throughput variations can harm you viewing experience. This short How To should give you the required information how to install iperf3 and how to run the respective tests. When doing these tests it is suggested to have a simple setup (single switch between Sender and Receiver and avoid other traffic on the …

[Phobios]

Looks like it should be enough. Still, all things point to a network issue.

[osmc@osmc ~]$ iperf3 -R -c
Connecting to host , port 5201
Reverse mode, remote host is sending
[ 4] local port 52365 connected to port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 4.76 MBytes 39.9 Mbits/sec
[ 4] 1.00-2.00 sec 6.42 MBytes 53.8 Mbits/sec
[ 4] 2.00-3.00 sec 7.97 MBytes 66.8 Mbits/sec
[ 4] 3.00-4.00 sec 7.53 MBytes 63.1 Mbits/sec
[ 4] 4.00-5.00 sec 6.51 MBytes 54.6 Mbits/sec
[ 4] 5.00-6.00 sec 7.38 MBytes 61.9 Mbits/sec
[ 4] 6.00-7.00 sec 9.23 MBytes 77.5 Mbits/sec
[ 4] 7.00-8.00 sec 10.2 MBytes 85.5 Mbits/sec
[ 4] 8.00-9.00 sec 4.70 MBytes 39.4 Mbits/sec
[ 4] 9.00-10.00 sec 2.87 MBytes 24.0 Mbits/sec

---

[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 68.1 MBytes 57.1 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 67.9 MBytes 57.0 Mbits/sec receiver

iperf Done.
[osmc@osmc ~]$ iperf3 -c
Connecting to host , port 5201
[ 4] local port 52367 connected to port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 3.87 MBytes 32.5 Mbits/sec 0 147 KBytes
[ 4] 1.00-2.00 sec 3.60 MBytes 30.2 Mbits/sec 0 147 KBytes
[ 4] 2.00-3.00 sec 6.15 MBytes 51.5 Mbits/sec 0 308 KBytes
[ 4] 3.00-4.00 sec 3.20 MBytes 26.9 Mbits/sec 0 324 KBytes
[ 4] 4.00-5.00 sec 3.93 MBytes 33.0 Mbits/sec 0 324 KBytes
[ 4] 5.00-6.00 sec 5.45 MBytes 45.7 Mbits/sec 0 339 KBytes
[ 4] 6.00-7.00 sec 2.47 MBytes 20.7 Mbits/sec 1 339 KBytes
[ 4] 7.00-8.00 sec 6.01 MBytes 50.4 Mbits/sec 0 387 KBytes
[ 4] 8.00-9.00 sec 6.21 MBytes 52.1 Mbits/sec 39 211 KBytes
[ 4] 9.00-10.00 sec 3.76 MBytes 31.5 Mbits/sec 31 161 KBytes

---

[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 44.7 MBytes 37.5 Mbits/sec 71 sender
[ 4] 0.00-10.00 sec 43.4 MBytes 36.4 Mbits/sec receiver

iperf Done.

[fzinken]

@Phobios

Looks like it should be enough.

@Phobios

37.5 Mbits/sec

Well that depends on the bandwidth requirements of your files (check with mediainfo).
Maybe just try shortly wired if that solves the problem then you know where to dig.

[Phobios]

But 37.5 is for Vero to server. Server to Vero (the really important metric, no?) is 57.1.

The reason I switched to wireless was because of a move of the device that resulted I needed to go from 20m cable to 25m, which I didn’t have. I guess I will have to buy one then, lol.

[Phobios]

Ok, so a rebooted router and rebooted Vero seem to have solved it. Temporarily anyways.

Still odd that I could play wirelessy from another device, but not with my Vero.

[Phobios]

Issue is back again. Still only the Vero device that is affected.

[sam_nazarko]

Can you attach a cable temporarily to see if it helps?

[Phobios]

I did and it helps.

[sam_nazarko]

Are you using an fstab based mount? That may boost performance sufficiently.