[wyild1]

Hey

I dont know if this is a PVR addon issue or a skin issue, so if not please direct me to the best spot for it.

On the LiveTV tab on the main screen, the Next recording isnt always correct. It will show recordings that wont happen.

Ill try to explain. So I record NBA games, but i have a higher priority recordings set for Raptor (#WETHENORTH) games. So there is ALOT of conflicts. So there is an NBA game at 6pm, but it wont be recorded because at 7PM the Raptor game will be recorded. But the next recording widget thingy shows the next recording being 6pm....which is incorrect. It will show all the conflicts as the next recording even though they wont be recorded

Can this be fixed?

If this doesn't make sense what im talking about, let me know and ill explain with screen shots S

Cheers!

[nickr]

I am unsure but I was just playing with my system, and noticed in Settings|PVR Service|Client Specific, click on "client specific settings". There is an option "Show/hide rules with status 'not recording'". Try it as I'm not 100% sure what that does.

[wyild1]

Thanks for that tip! I enabled it and will see if that fixes it. My next recording is to be recorded so will have to see after if that fixes it

[wyild1]

Nope that wasn't it. Show is recording now for 3 hrs but next recording says starts in 30 min.

Thanks for the help though!

[nickr]

How does it compare to the mythweb upcoming recordings page?

[wyild1]

OK take a look at this:

https://www.dropbox.com/s/uir2jz4h5tcr8g...b.png?dl=0

This is for tomorrow. Recording at 11:59 am that is 7 hours. Now Kodi widget will show that it is recording that, but it will show the next recording at 2:30 or after that the next one will be at 3pm.

So the widget will show the conflicts, which I believe it shouldn't. the next recording should be the actual one the be recorded.

Cheers!

[nickr]

I agree it should work like you want. How to fix it, I dunno. I have multiple tuners so rarely get conflicts so it's hard for me to reproduce!

[janbar]

Unfortunely Kodi widget does not matter of record status and show the next considering only the start time.
Which version of Kodi please ?

[wyild1]

Unfortunely Kodi widget does not matter of record status and show the next considering only the start time.
Which version of Kodi please ?

Using the latest 15.2 on Android and Linux

[metaron]

It seems that pvr.mythtv is working as designed (well, OK, maybe not how you would want it to in this case...)
The idea was it shows the conflict as such, so you can see it is there and potentially do something about it (if you want to).

MythScheduleManager::GetUpcomingRecodings() should be detecting your conflict (Myth::RS_CONFLICT) and passing it to Kodi PVR core as an upcoming timer with status 'PVR_TIMER_STATE_CONFLICT_NOK'
(see https://github.com/janbar/pvr.mythtv/blo...r.cpp#L232 and https://github.com/janbar/pvr.mythtv/blo....cpp#L1566)

If memory serves, Kodi's PVR core in 15.2 (Isengard) still treats 'Conflict Not OK' items as upcoming recordings which will record and announces them :-(. Not the best part of the kodi PVR user interface imho...

PVR has been seriously re-worked in Javis which may 'fix' this, although I'm not sure. I added another tuner to my backend and don't see them much anymore

Personally I'd stick with mythweb to schedule recordings until 16.0 Jarvis hits the streets. Timers in Isengard with pvr.mythtv are OK for occasional use, but not good enough the way I see it. (I'm running a recent 16.0 Millhouse build on my RPi frontends and at least at the moment, it rocks).

Edit: Just seen your dropbox image and it looks like my theory was correct - status will be 'RS_CONFLICT'. It may be that the idea of handling recording conflicts in this way still needs 'tweaking'.

I'd be interested in knowing how you would expect them to be handled as you are obviously someone who sees them a lot, especially if you manage to try out what they do in Jarvis as well
Is it just a case of the misleading widget on the home screen (which I agree is daft), or something else as well?

Can you explain a bit more about the conflicting rules and the number of tuners on your backend?

[metaron]

I am unsure but I was just playing with my system, and noticed in Settings|PVR Service|Client Specific, click on "client specific settings". There is an option "Show/hide rules with status 'not recording'". Try it as I'm not 100% sure what that does.

This will (temporarily - i.e. until you turn it off or restart kodi) turn on display of upcoming recordings with status:
case Myth::RS_EARLIER_RECORDING: //will record earlier
case Myth::RS_LATER_SHOWING: //will record later
case Myth::RS_CURRENT_RECORDING: //Already in the current library
case Myth::RS_PREVIOUS_RECORDING: //Previoulsy recorded but no longer in the library

In the Timers list.

Unfortunately this probably also means they will be announced as upcoming recordings by 15.2 Isengard's PVR core :-(.

[wyild1]

It seems that pvr.mythtv is working as designed (well, OK, maybe not how you would want it to in this case...)
The idea was it shows the conflict as such, so you can see it is there and potentially do something about it (if you want to).

MythScheduleManager::GetUpcomingRecodings() should be detecting your conflict (Myth::RS_CONFLICT) and passing it to Kodi PVR core as an upcoming timer with status 'PVR_TIMER_STATE_CONFLICT_NOK'
(see https://github.com/janbar/pvr.mythtv/blo...r.cpp#L232 and https://github.com/janbar/pvr.mythtv/blo....cpp#L1566)

If memory serves, Kodi's PVR core in 15.2 (Isengard) still treats 'Conflict Not OK' items as upcoming recordings which will record and announces them :-(. Not the best part of the kodi PVR user interface imho...

PVR has been seriously re-worked in Javis which may 'fix' this, although I'm not sure. I added another tuner to my backend and don't see them much anymore

Personally I'd stick with mythweb to schedule recordings until 16.0 Jarvis hits the streets. Timers in Isengard with pvr.mythtv are OK for occasional use, but not good enough the way I see it. (I'm running a recent 16.0 Millhouse build on my RPi frontends and at least at the moment, it rocks).

Edit: Just seen your dropbox image and it looks like my theory was correct - status will be 'RS_CONFLICT'. It may be that the idea of handling recording conflicts in this way still needs 'tweaking'.

I'd be interested in knowing how you would expect them to be handled as you are obviously someone who sees them a lot, especially if you manage to try out what they do in Jarvis as well
Is it just a case of the misleading widget on the home screen (which I agree is daft), or something else as well?

Can you explain a bit more about the conflicting rules and the number of tuners on your backend?

Thanks for this info Metaron.

I have 1 backend and 1 tuner. I have rules for "NBA" games or "NFL", and I will ALWAYS have conflicts as every night there is like 10 NBA games. That doesnt bother me and i use mythweb for scheduling and if i want to change anything around.

I just would like the widget that shows next recording to be the one that actually records. I dont use that widget/kodi PVR for conflict resolution, i just would like to know what is really going to be recorded next without me having to go to mythweb to see for sure

It really is just a cosmetic/misleading thing.

Cheers!

[rpcameron]

Looking at this, it appears that the widget pulls from the Timers. Even if Myth doesn't record something because of a conflict, the timer still exists. I believe this is because Kodi only sees its stuff, and Myth isn't removing the timer, just deactivating when it comes time to start because of the conflict.

So, I guess this is a Myth backend issue of the backend populating Kodi with timers, regardless of Myth's priorities. This is probably something that would need to be fixed in the backend logic.

[raptorjr]

Looking at this, it appears that the widget pulls from the Timers. Even if Myth doesn't record something because of a conflict, the timer still exists. I believe this is because Kodi only sees its stuff, and Myth isn't removing the timer, just deactivating when it comes time to start because of the conflict.

So, I guess this is a Myth backend issue of the backend populating Kodi with timers, regardless of Myth's priorities. This is probably something that would need to be fixed in the backend logic.

Don't know anything about this, but since MythWeb can show conflicts, which recordings are inactivated and such, this must already be possible to read from the backend. In the same way it should be possible for Kodi to read the same information and find out what is going to be recorded and what is inactivated. Or does MythWeb have some secret backdoor to the information?

And it looks like the MythTV WebFrontend also sees this information, and there I'm pretty sure that they use some protocol to query the backend for information. In the same way the MythTV PVR addon should be able to.

[metaron]

Ok I've done a bit more investigating using my 0.27.4 backend:

With mythweb showing the first four entries as:
Conflict Heartbeat: Dog Days 110 - ITV3 +1 Fri Nov 13, 2015 (06:55 PM) 1 hr 5 mins Record This Never Record
Conflict Coronation Street 105 - ITV1 Fri Nov 13, 2015 (07:00 PM) 30 mins Record This Never Record
Conflict ITV News Wales at Six 106 - ITV1 +1 Fri Nov 13, 2015 (07:00 PM) 30 mins Record This Never Record
DVB-S HDThe One Show 001 - BBC One HD Fri Nov 13, 2015 (07:00 PM) 30 mins Don't Record Never Record

Using OE 6.0 (Kodi 15.2) on an RPi2 with pvr.mythtv 2.7.4 shows:
ITV3+1 Heartbeat 13/11/2015 18:55 to 20:00 Conflict error
ITV1 Coronation Street 13/11/2015 19:00 to 19:30 Conflict error
ITV1+1 ITV News Wales at Six 13/11/2015 10:99 to 19:30 Conflict error
BBC One HD The One Show 13/11/2015 19:00 to 19:30 Enabled

And the home screen widget shows:
Next recording
Start time - 13/11/2015 18:55
Heartbeat - (ITV3 +1)

Using a Millhouse 16.0 Jarvis build on an RPi with janbar's latest 'doityourself' with some custom hacks of my own:
ITV3+1 Heartbeat 13/11/2015 18:55 to 20:00 Record this Conflict error
ITV1 Coronation Street 13/11/2015 19:00 to 19:30 Record this Conflict error
ITV1+1 ITV New Wales at Six 13/11/2015 10:99 to 19:30 Record this Conflict error
BBC One HD The One Show 13/11/2015 19:00 to 19:30 Record this Enabled

And the home screen widget shows:
Next recording
Start time - 13/11/2015 18:55
Heartbeat - (ITV3 +1)

Conclusions

• The mythtv backend and pvr.mythtv correctly identify these as 'broken conflicts' - i.e. won't record in all cases.
  
• The timers list shows the conflicts correctly 'Conflict error'
  
• The home screen widget incorrectly displays simply the first 'upcoming' as the next 'upcoming recording' (both Isengard and Jarvis), completely disregarding the fact that it wont record because is has status 'Conflict not OK'.
  

I'm busy this weekend but will try and work on a patch some time next week (unless ksooo or someone fixes it first). Feel free to check kodi's bug database to see if it's already been reported. If not, raise a new bug referring to this thread and post a link here.