• 1
  • 10
  • 11
  • 12(current)
  • 13
  • 14
  • 48
Vu+ PVR addon is getting updates again
Here's another peculiarity I stumbled upon. No real clue what might be causing it to happen either. Was setting a timer for tonight from my guide screen and noticed the programme duration was incorrect:-

Image

You will notice the orange focused bar has the programme start/end time from 20:00-22:00Hrs which is correct, but the duration at the top of the screen is showing 1Hr, instead of 2Hrs. There is nothing wrong with the variable I've used for displaying the duration. Even stranger is when I pull up the PVR Info Dialog, as that's showing the duration correctly as 2hrs:-

Image 

Initially, I thought this was an isolated case/quirk, since other programme items seemed to be showing the correct duration, but I discovered another instance just 2 channels below the original:-

Image

So I'm not sure if the problem is being caused by the PVR addon, Kodi core or neither and something else completely?

UPDATE: Have updated from Kodi RC3 to RC5.2 and from 3.15.2 to 3.16.1 to see if that would make any difference. The good news is the original item mentioned is now showing the correct duration of 2 Hours. The bad news, I now have many items now displaying the wrong the duration on the guide screen, but displaying the correct info on the PVR info Dialog. A 5min TV entertainment update for instance is displaying a duration of 1hr 20mins. Most items are displaying durations correctly, so can't fully understand what is happening here......
Reply
The addon only supplies start time and end time. There is no notion of duration for an epg entry.

Do you calculate duration?
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
(2019-01-13, 20:26)phunkyfish Wrote: The addon only supplies start time and end time. There is no notion of duration for an epg entry.

Do you calculate duration?
Yes, for list items on guide and other PVR screens. Also for video player for the OSD. Example of 1Hr show:-

php:
<value condition="String.StartsWith(ListItem.Duration,01:00Smile">1h00m</value>
 
I had problems quite a few months back where the duration on the recording screen which had been working fine, suddenly stopped working using this method. At the time I was told it was a backend issue and nothing got done. Then without reason, months later something must have been changed, because is started displaying the duration correctly again. The incorrect duration I'm seeing currently on the guide screen is a carbon copy of the previous error with recording durations.

Have just checked my current recordings and timers. All are showing correct durations and use the exact same variable.
Reply
Is it possible for you to subtract start time from end time instead so you’re not dependent on duration?

Sorry, I have very little knowledge of skin development 😉
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
(2019-01-13, 21:36)phunkyfish Wrote: Is it possible for you to subtract start time from end time instead so you’re not dependent on duration?

Sorry, I have very little knowledge of skin development 😉
You would think that such a feature would exist, but I'm not sure it does.
A little frustrating, particularly as things had been working so well previously.
No worries.
Reply
I would report the issue on the xbmc github. If they are at rev 2 of RC5 it’s when they get to fix the little niggles.
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
@garret 

Can you try the following URL in a browser and tell me output you see? A screenshot is fine:

http://<your-ip>/api/event

If the api is available then the fix will work for you. Otherwise you would need to upgrade your version of openwebif for it to work.
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
(2019-01-14, 13:45)phunkyfish Wrote: @garret 

Can you try the following URL in a browser and tell me output you see? A screenshot is fine:

http://<your-ip>/api/event

If the api is available then the fix will work for you. Otherwise you would need to upgrade your version of openwebif for it to work.
Here:

Image
Reply
@garret That’s a good start.

Also a screen shot of this: http://<your-ip>/api/event?sref=blah&idev=7

Then the output of:

http://<your-ip>/api/deviceinfo

For the above deviceinfo call can you use https://paste.kodi.tv as I need the formatting kept intact.

Thanks, then I should have what I need to put the fix in place.

BTW the cause is to do with description and extended description. In OpenWebIf it loads the EPG entry before creating the timer and this is where the description comes from. In kodi we don’t have the epg entry so I would need to query it and constructor the description so it works for your use case.
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
(2019-01-14, 17:01)phunkyfish Wrote: Also a screen shot of this: http://<your-ip>/api/event?sref=blah&idev=7
https://paste.kodi.tv/eyuyipixud
(2019-01-14, 17:01)phunkyfish Wrote: Then the output of: http://<your-ip>/api/deviceinfo
https://paste.kodi.tv/winarawiki
(2019-01-14, 17:01)phunkyfish Wrote: BTW the cause is to do with description and extended description. In OpenWebIf it loads the EPG entry before creating the timer and this is where the description comes from. In kodi we don’t have the epg entry so I would need to query it and constructor the description so it works for your use case.
Please do not misunderstand me, but how can it be possible? Because when you are for example in program guide, you have all information in Kodi. Start time, end time, channel, description, etc.

I was in that belive that when parsing query for sending new timer to STB, there is something wrong in code and it takes wrong variable or something, and sends this wrong infromation to Enigma's timer.xml - file. 

Can you point to me where is this part (sending timer to STB) in source code? https://github.com/kodi-pvr/pvr.vuplus/tree/master/ Just for my interest purposes.
Reply
You're correct, the data is in Kodi, however not in the addon (the addon passes it from the engima device to kodi). I could keep a set of the data in the addon but it wouldn't make sense as it would use a bunch of memory with little or no purpose.

If the info is stored in long description then the timeradd call correctly populates the right field in the recording data. However if it's in short description it doesn't but in this case it can be overidden in the timeradd call. This is a function of the engima platform and not the addon. I can however load a single event using the json API in this case.

There is a call to use only the epg id called timeraddbyevent however this does not work for recordings that start partway trough a recording. Fixing this in Openwebif won't help anyone on an older version. So the solution would be to use timeradd (populating description in your use case) for instant recordings and timeraddbyevent for those in the future where we let enigma handle it.

Here's the AddTimer code:
https://github.com/kodi-pvr/pvr.vuplus/b...s.cpp#L445
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
Perfect!

Now I understand. Thanks mate.
Reply
On second thought will probably just use timeradd for everything. By eventid doesn’t add any benefit.
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
v3.16.2 released

- Fixed: Seg fault on shutdown - Timer Updates thread accessing released object, fixes #172
- Fixed: Incorrectly used time_t instead int64 in GetStreamTimes, fixes #171
- Added: Load Addon Version
- Fixed: Clean up/partition addon debug log, fixes #159
- Added: Add user defined delay between EPG Channel Updates, fixes #158
- Added: Enable Trace Logging in debug mode
- Added: Integrate Stream API details with Tuners
- Fixed: JSON API requires version 1.3.5+ of OpenWebIf, fixes #169
- Added: updated language files from Transifex
Maintainer of Enigma2 PVR addon: repo, docschangelog
How to create a full debug: here
Reply
Okay, things are getting very strange now.
In this example, guide is showing start time of 21:00Hrs, which is correct but an end time of 21:30Hrs which is incorrect. End time should be 22:00Hrs. Duration of 1 Hour is correct.

Image

The programme info for the above recording is actually showing the below description on the recording screen, which is completely wrong. This programme description appears to relate to a snooker championship currently being broadcast in the UK:-

Image

It looks like the above programme description is coming from a programme item listed for the 20th January (4 days time) according to my EPG:-

Image

Of course I can raise this as a bug on the GitHub, but the problem seems to be quite random since not every item is affected with wrong data. I did notice a couple of similar instances over xmas with wrong programme descriptions, so reverted back to an earlier version of the addon but I'm now back to using version 3.16.1. I have refreshed the TV Channel and EPG data a few a times and even deleted the EPG DB. I'm thinking of un-installing Kodi completely and re-installing to see if that will make any difference.
Observations are not limited to just my own skin mod, as I have tested using Estuary Stock and Confluence skins, which are displaying exactly the same erroneous data as well.
But very strange and odd behaviour indeed....
Reply
  • 1
  • 10
  • 11
  • 12(current)
  • 13
  • 14
  • 48

Logout Mark Read Team Forum Stats Members Help
Vu+ PVR addon is getting updates again3