Login at Kodi Home

flitter2009 · (This post was last modified: 2017-06-21, 00:28 by flitter2009.)

Hi, in Krypton is anyone noticing Kodi UI freezing when hitting stop in a recording being streamed through the mythtv add-on, or flickering of the recordings list when you return to it from playback? (the logs show that it's running GetDeletedRecordings and it's flickering one time for each of the CPVRRecording::CPVRRecording warning entries in the log after that). Channel ID 2010 is a standard channel and doesn't produce the warning message when trying to get the artwork for non-deleted recordings).

08:12:41.179 T:140592597694208 DEBUG: AddOnLog: MythTV PVR Client: GetDeletedRecordings
08:12:41.179 T:140592597694208 DEBUG: AddOnLog: MythTV PVR Client: GetPreviewIconPath: preview: 2010_1497864000_84f
08:12:41.179 T:140592597694208 DEBUG: AddOnLog: MythTV PVR Client: GetArtworkPath: coverart: 2010_1497864000_84f
08:12:41.179 T:140592597694208 DEBUG: AddOnLog: MythTV PVR Client: GetArtworkPath: fanart: 2010_1497864000_84f
08:12:41.179 T:140592597694208 WARNING: CPVRRecording::CPVRRecording - unable to determine channel type. Defaulting to TV.

I'll try to get a clean debug log in the next few days. I'm not sure I can get a stack trace as Kodi isn't actually freezing (Platinum and RunHouseKeeping are continuing to log entries but the UI becomes unresponsive). PVR add-on version is 4.15.0 and the freeze doesn't happen when running off the end of a recording, only when hitting stop.

krbvroc1 · 2017-06-25, 02:26

Since updating to Kodi 17, I am experiencing either:
1) System notification hung on PVR Manager 'Importing guide from clients' - When it doesn't hang (requiring a reboot), the speed of the guide data downloads will be either really snappy or really slow.
2) Occasionally a notification of 'Timer deleted' that stays on the screen forever. I think I need a reboot to get rid of it - don't remember.

nickr · 2017-06-25, 03:21

Would you please update to 17.3 and see if the problems persist?

krbvroc1 · 2017-06-25, 03:42

(2017-06-25, 03:21)nickr Wrote: Would you please update to 17.3 and see if the problems persist?

Actually I am already running the latest osmc which is on version 17.3.

afremont · (This post was last modified: 2017-06-25, 04:57 by afremont.)

Slow guide loading has been around for a while. If you have local guide caching turned on, there are two loads. The first is collecting the cached data which goes fast. The second is pulling client guide data, and it crawls. If the cached data is current, then the second load is skipped. I see this on raspberry pi and odroid, and I believe on Intel as well. The more days you have set to load, the longer it takes. I usually set mine for one day; the default is three days.

Edit:. I can't be sure if the guide load became slow with Krypton. Too many other things going on, plus I ran a lot of special Milhouse builds before trying to stick with the official releases. I have a giant debug crash log from a different odroid problem that I was trying to resolve. Looking through it tells me nothing about the crash reason, but it seemed like there is a lot of data transfer to the myth box that seems unnecessary. The file is too large to pastebin. My mythbuntu box is a few years old (Ubuntu 14) and maybe that is the root of my problem. I'm afraid to try and bring it current with a dist upgrade and switching to .28 since I have thousands of tv recordings, and haven't had time to experiment with backing up all the myth data, setting up a later mythbuntu release on a different drive and importing the data. Risking breaking the .27 install isn't going to happen.

Sent from my Moto G (4)

thezencowsaysmu · 2017-06-26, 20:36

(2017-06-25, 04:39)afremont Wrote: My mythbuntu box is a few years old (Ubuntu 14) and maybe that is the root of my problem. I'm afraid to try and bring it current with a dist upgrade and switching to .28 since I have thousands of tv recordings, and haven't had time to experiment with backing up all the myth data, setting up a later mythbuntu release on a different drive and importing the data. Risking breaking the .27 install isn't going to happen.

Off-topic, but I found that a dist-upgrade from mythbuntu 14.04 to 16.04 was a complete disaster.

What worked with no problems for me was backing up my myth database, nuking the os drive, installing Lubuntu 16.04 from scratch, installing mythtv using the mythbuntu ppa, and restoring my mythtv database.

disclaimer: While I was running mythbuntu 14.04, I upgraded mythtv to 28 (which also went completely smoothly).

Smallmountains · 2017-07-15, 18:45

(2017-04-23, 16:29)metaron Wrote:
(2017-04-23, 01:20)Smallmountains Wrote: Yes, I can set a recording from mythweb and it works fine. I've checked and double checked date and time on all my boxes. No problems there. They all use the same NTP source.

Can you post a log file with 'extra debug info' turned on? It might provide just enough information to confirm what's happening.

It's been some time since I was able to get back here but I have discontinued using Kodi on windows. It seems to work properly on my android box. I notice the MythWeb has the original air date listed but I don't see that in the mythtv plugin...other than year only. Not all that useful for determining if something is new or not. Just a thought.

Anyway thanks for the suggestions on my recording issue. It only happens on windows as far as I can see and that doesn't apply to me anymore.

nickr · (This post was last modified: 2017-09-19, 09:11 by nickr.)

Nothing to do with MythTV, please start a new thread, or look at the addon development sections of the wiki.

nickr · 2017-09-19, 09:14

@shajeer I am beginning to think you are simply a spammer.

dapharsyde · (This post was last modified: 2018-02-18, 06:51 by dapharsyde.)

UPDATE: created my own thread

LeKodeur · (This post was last modified: 2018-06-11, 03:22 by LeKodeur.)

Post DELETED

glubbish · 2018-06-23, 11:29

Can anyone tell me what these errors mean? (kodi 17.6 ubuntu 16.04)

19:25:00.302 T:139959525693184 NOTICE: AddOnLog: MythTV PVR Client: Launcher stopped
19:25:00.421 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.421 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!
19:25:00.421 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.421 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!
19:25:00.421 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.421 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!
19:25:00.421 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.421 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!
19:25:00.421 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.421 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!
19:25:00.422 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.422 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!
19:25:00.422 T:139959517300480   ERROR: CPVRTimerType::CreateFromIds unable to resolve numeric timer type (17, 632756738)
19:25:00.422 T:139959517300480   ERROR: CPVRTimerInfoTag: no timer type, although timers are supported by client 632756738!

janbar · (This post was last modified: 2018-11-15, 17:05 by janbar.)

Announcement:

Since my liked friend Mr Jenkins build the package of the addon on the fly after all released changes, my ppa at launchpad is no longer needed. I invite any user using my ppa to switch as soon as possible to the official ppa of Kodi: http://ppa.launchpad.net/team-xbmc/xbmc-nightly/ubuntu.
The janbar ppa won't build any more new release for the addon.

Up-to-date documentation can be found here: http://janbar.github.io/pvr.mythtv/

janbar · (This post was last modified: 2018-11-27, 11:43 by janbar.)

Brief about new features included in the addon for Leia release 5.10.2:

- show addon status in queued message on startup. The old dialog (on failure) has been removed because it locked UI with Leia.
- yellow colorized title for damaged recording.
- improve of grouping recordings by title: Only the base of the title is used, and extra info are cleaned.
- data stream caching to close stuttering with slow network.
- announcement as frontend: your kodi players are showed as frontend with status in web backend page.
- including french categories telerama by default for the guide. Also you can always provide your categories by uploading file in the addon user data.
- new client actions to show recording or program guide exta info from the backend.
- new option to use the Default recording group as root for recordings.

Next feature: EPG bulk loading to improve guide import.

Note: All these features have been merged in a special release (3.6.1) for Kodi Jarvis. (I still use it for my rpi2). You will find the binary in the release page of my github.

jfabernathy · 2018-11-28, 14:31

(2018-11-11, 14:17)janbar Wrote: Announcement:

Since my liked friend Mr Jenkins build the package of the addon on the fly after all released changes, my ppa at launchpad is no longer needed. I invite any user using my ppa to switch as soon as possible to the official ppa of Kodi: http://ppa.launchpad.net/team-xbmc/xbmc-nightly/ubuntu.
The janbar ppa won't build any more new release for the addon.

Up-to-date documentation can be found here: http://janbar.github.io/pvr.mythtv/

I'm running Kodi and pvr.mythtv on my RP3 under Raspbian Stretch. When I installed it, it came with a much older pvr.mythtv version. Can that to updated to your latest?