I am experiencing very broken playback whilst watching BBC iPLayer Live Stream.Can anyone make head or tail of this log?it appears to show a multitude of errors.
10:34:43 33186.046875 T:1957163952 ERROR: Control 51 in window 10001 has been asked to focus, but it can’t
10:34:56 33198.535156 T:1513952240 WARNING: Attempt to use invalid handle -1
10:34:58 33201.019531 T:1957163952 NOTICE: DVDPlayer: Opening: http://vs-hls-uk-live.edgesuite.net/pool_34/live/bbc_news_channel_hd/bbc_news_channel_hd.isml/bbc_news_channel_hd-pa4%3D128000-video%3D2812000.m3u8
10:34:58 33201.019531 T:1957163952 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
10:34:58 33201.019531 T:1637872624 NOTICE: Creating InputStream
10:34:58 33201.347656 T:1637872624 NOTICE: Creating Demuxer
10:35:00 33202.597656 T:1637872624 NOTICE: Opening stream: 1 source: 256
10:35:00 33202.617188 T:1637872624 NOTICE: Creating video thread
10:35:00 33202.617188 T:1637872624 NOTICE: Opening stream: 0 source: 256
10:35:00 33202.625000 T:1637872624 NOTICE: Creating audio thread
10:35:00 33202.625000 T:1637872624 NOTICE: OMXClock using audio as reference
10:35:00 33202.644531 T:1513952240 NOTICE: Display resolution USER : 1360x768 (1360x768) @ 60.00 - Full Screen (25)
10:35:49 33251.796875 T:1637872624 NOTICE: OMXDoProcessing - Reopen stream due to interlace change (0,2,1,1)
10:35:49 33251.800781 T:1637872624 NOTICE: Closing stream player 2
10:35:49 33251.800781 T:1513952240 ERROR: OMXPlayerVideo: Got MSGQ_IS_ERROR(-1) Aborting
10:35:49 33251.800781 T:1513952240 NOTICE: thread end: video_thread
10:35:49 33251.855469 T:1637872624 NOTICE: Opening stream: -1 source: 0
10:35:49 33251.855469 T:1637872624 ERROR: COMXVideo::Open : Video codec unknown: 0
10:35:49 33251.855469 T:1637872624 ERROR: OMXPlayerVideo : Error open video output
10:35:49 33252.000000 T:1637872624 WARNING: error while seeking
10:35:50 33252.742188 T:1637872624 NOTICE: Opening stream: 1 source: 256
10:35:50 33252.777344 T:1637872624 NOTICE: Creating video thread
10:35:59 33262.000000 T:1637872624 NOTICE: OMXDoProcessing - Reopen stream due to interlace change (2,1,1,1)
10:35:59 33262.000000 T:1637872624 NOTICE: Closing stream player 2
10:35:59 33262.000000 T:1513952240 ERROR: OMXPlayerVideo: Got MSGQ_IS_ERROR(-1) Aborting
10:35:59 33262.000000 T:1513952240 NOTICE: thread end: video_thread
10:35:59 33262.015625 T:1637872624 NOTICE: Opening stream: -1 source: 0
10:35:59 33262.015625 T:1637872624 ERROR: COMXVideo::Open : Video codec unknown: 0
10:35:59 33262.019531 T:1637872624 ERROR: OMXPlayerVideo : Error open video output
10:36:03 33265.726562 T:1637872624 WARNING: error while seeking
10:36:03 33265.726562 T:1637872624 NOTICE: Opening stream: 1 source: 256
10:36:03 33265.750000 T:1637872624 NOTICE: Creating video thread
10:36:14 33277.140625 T:1513952240 NOTICE: Display resolution USER : 1360x768 (1360x768) @ 60.00 - Full Screen (25)
Always post complete logs to a paste site and include a link.
Does disabling deinterlace make a difference?
Does disabling omxplayer make a difference?
That was the complete log…I can put it in a pastebin though.
The system was working fine yesterday,nothings changed.I found that with live streams turning de-interlacing off always seemed to work better.I have not tried disabling omxplayer,as I have never needed to,but can give it a shot.
No, a kodi log will start with “NOTICE: Starting Kodi (16.1 Git:2016-06-06-f003801). Platform: Linux ARM 32-bit”. You have cut the log down.
Also you need to enable debug logging in system/logging settings before playing the file and capturing the log.
Ooops I forgot to enable debug:
This log doesn’t start with “NOTICE: Starting Kodi (16.1 Git:2016-06-06-f003801). Platform: Linux ARM 32-bit”
but is most definetly the entire log as you can see the run command at the start
I can’t paste full log with debug enabled as it is too large for pastebin at only 30seconds long!
Here is the jist of it though:
You are viewing with “tail” which just shows the end of the file. Use less to view the file and you will see the “NOTICE: Starting Kodi…” near the top of the file.
1 Like
In future please use the grab-logs command, paste-log command or My OSMC log uploader to upload your logs to our paste server - it has a much higher file size limit and is specifically designed for this purpose. It is documented here:
1 Like
OK so I did a grab logs…but where does this get sent and how do you know who sent it?
My system by the way is:
Pi3
64GB Samsung EVO Card
OSMC latest update
This issue seems to show up after a week or two of having a freshly installed OSMC.Every time I build a new image it seems to work smoothly for about a week and then little ‘quirks’ like this tend to start rearing their ugly heads.I have no unofficial Add-On’s installed and was just about ready to clone this image as I was happy with the setup.
When you run grab-logs then you have to provide the resultant URL.
Where do I find this URL?It doesn’t display any URL other than ‘Uploads vital logs to http://paste.osmc.io.’ on output
If you had actually run the command to upload logs you would have been presented with a URL to provide here.
Is this not running the command correctly?
osmc@osmc:~$ grab-logs
usage: grab-logs [-h] [-A] [-T FILENAME] [-C] [-P] [-I] [-p] [-v] [-k] [-r]
[-s] [-f] [-O] [-o] [-a] [-J] [-l] [-i] [-d] [-K] [-m] [-D]
[-b] [-X]
Uploads vital logs to http://paste.osmc.io. If the network is unavailable,
logs are copied to the SD Card.
optional arguments:
-h, --help show this help message and exit
-A, --all Include all logs
-T FILENAME Override default name and location of temporary log file
-C, --copy Copy logs to /boot (SD Card)
-P, --print Print logs to screen (no upload or copy)
-I, --systeminfo System Information
-p, --piconfig Pi config.txt
-v, --advset advancedsettings.xml
-k, --keyboard keyboard.xml
-r, --remote remote.xml
-s, --sources sources.xml
-f, --fstab fstab file
-O, --packages OSMC Packages
-o, --othpack All Other Packages
-a, --apt APT term.log, history.log, sources.list, apt.conf.d,
preferences.d
-J, --sysjrn System Journal
-l, --lirc lirc.conf file
-i, --initd init.d directory
-d, --systemd systemd directory
-K, --kernel Kernel Message Log
-m, --memory System Memory (total & available)
-D, --disk Diskspace (total & available)
-b, --boot Contents of /boot/
-X, --kodi, --xbmc Kodi log files (includes log from previous boot)
Are you still get lock-up with iPlayer? Did you find a resolution?