Can NextPVR import TitanTV .TVPI files to schedule a recording

[mvallevand]

Thanks but there is no OTA data in that guide, so nothing to compare with. Basically I'm look to see why certain shows don't match when there is guide data. Next time it fails zip the database again and let me know the show name.

Martin

[FM5]

Heh, I was wondering what you wanted it for.  Since TitanTV's file wouldn't schedule with any EPG data in NextPVR, and since OTA EPG data in NextPVR is only good for 8 or so hours, I can't think of any reason to use NextPVR's EPG at all if the updates are from the stations' OTA, so I just kept the NextPVR EPG empty after the first fails.  

Everyone here says not to bother with OTA station EPG anyway and then asks why the person isn't using Schedules Direct.   

I'll do an OTA EPG update and run some fails to zip.

[FM5]

Clicked the update EPG button in NextPVR, EPG listings are now there.  Tried 4 or 5 programs from TitanTV.  None scheduled.  All were channel 2 and its subchannels.  My scheduled recordings I did pre-EPG that start 20 minutes from now are still listed in EPG.  Figured trying to schedule new recordings with content in the EPG wouldn't affect them.  If it does, I'll let you know.

[mvallevand]

There seems to be glitch in either the source data significant digits or the ATSC parsing, many of the times are exactly 18 seconds past the minute so my time matches are too preciss @sub any thought on why the time is often off by eighteen seconds?

I will see about ignoring the seconds from the EPG to see if that helps.

Martin

[sub]

I’m out for a bit, but can take a look after.

[mvallevand]

Probably not a major issue anyway sub, just something for you to think about when you are looking at ATSC OTA scanning logic.  It might cause some recordings to not be scheduled back-to-back on different channels.  Not all have the 18 second offset, some are zero and a few have a different offset.

This attached version strips seconds from the NextPVR start time to see if matches are better.

Martin

[FM5]

My recording that was scheduled from TitanTV when the NextPVR's EPG was blank now started fine as expected with the EPG now full (full for 8 hours anyway).

Mainly writing this post to say there may be channel lineup problems with 2.1 and 2.3. I've been doing this with little sleep and sick, (hopefully it's covid since it's not too bad), so I currently only have 5 or so channel IDs that I know are correct between NextPVR and TitanTV.

Also, very strangely, during the last week or two here, TitanTV's guide has literally doubled many of the channels on the guide screen. Maybe the local TV stations are moving some signal channels around, or preparing to. On TitanTV, I literally have two 2.1 channels on the programming grid. And many other doubles. One or two of the other channels have different episode listings. I only have one channel lineup set: ATSC OTA by zip code.

So, my zip file in post 53 probably has two tries of channel 2.1. One from each of the TitanTV listings. But only one of those has the same station ID as 2.1 does in NextPVR.

Channel 2.3 is wrong ID.

2.2 is the 24/7 weather channel. That ID is correct.
2.4 correct.
2.5 correct.
So whatever you're looking at, focus on those last three. And probably just the last two since those have normal programming. And none of those three channels have doubles on TitanTV.

[mvallevand]

I'd rather you focus on 1.0.8 since it could explain things best. This new logic is solely based on channel name matches.

Martin

[FM5]

ahaha. It's good you said something because when you posted 1.08 you were telling sub to think about seconds of offset, and then said your zip file deletes some seconds, so I thought your zip file was for him to look at.

1.08 installed.
Scheduled a couple recordings on each of 3 different channels. 2.2, 2.4, 2.5.
Works.
The schedule times look correct.
Also set it to record a program already in progress. Works.

[FM5]

Actually, I missed it before. The scheduled recordings start exactly at the top or half past the hour, but they end with an additional 18 seconds. Example: 8:00pm start, 9:00:18pm end.

It apparently works fine, but letting you know in case it's not what you expected.