Not all EPG data shown in Guide

[mmortal03]

Ah, sorry - I didn't think to check it on an 'HDHR' style device. That fix was for BDA style device, ie USB/PCIe device connected to the machine, or HDHomeRun devices using the BDA drivers ('DVB-T' / 'DVB-C' device types on the Devices screen). The 'HDHR' style EPG is done a slightly different way. I'll check that too and fix.

Any update on this? Do you want me to test this on my Windows and docker instances? Is this fix scheduled for next release, if so any ETA? 
Thanks appreciate it.

Tangential to this, but speaking of HDHR device style versus ATSC device style, it reminds me that I noticed a completely separate bug two weeks ago where I had originally selected the two HDHR devices to use from my tuner, and had scheduled a recurring recording with those, but then realized that I needed to use the ATSC devices to pull the EIT data. So, in the process of switching over to the ATSC device style, I also went in and edited the recurring recording to match the ATSC devices, but something still happened in the recording database where no timers were getting scheduled. So, I ultimately just deleted that recurring scheduled recording and created a fresh one, and that one has worked ever since.

@sub, regarding this 3 hour EIT guide data bug I'm experiencing, please let me know if you need further logs other than what I posted above or further testing from me. It'd be awesome to get it working.

[sub]

@sub, regarding this 3 hour EIT guide data bug I'm experiencing, please let me know if you need further logs other than what I posted above or further testing from me. It'd be awesome to get it working.

For me to look into this, I need to get someone to capture a 1 minute full transport stream from one of their ATSC frequencies. Unfortunately, it needs to done when I have immediate time available to look into it, since old listings won't get kept.

[mvallevand]

He posted it here https://forums.nextpvr.com/showthread.ph...#pid552018 (he hijackd this thread which makes it a bit difficult to follow)

Martin

[sub]

He posted it here https://forums.nextpvr.com/showthread.ph...#pid552018 (he hijackd this thread which makes it a bit difficult to follow)

It's got stale data. When I've got some time ready to look into it, someone will need to post a file with future data in it, and I immediately look at it, so I can see it go through the various NextPVR logic. (old data is usually just thrown away and not processed)

[mvallevand]

Sorry I forgot about that.

Martin

[mmortal03]

He posted it here https://forums.nextpvr.com/showthread.ph...#pid552018 (he hijackd this thread which makes it a bit difficult to follow)

It's got stale data. When I've got some time ready to look into it, someone will need to post a file with future data in it, and I immediately look at it, so I can see it go through the various NextPVR logic. (old data is usually just thrown away and not processed)

I'm willing to produce these for you anytime. Just let me know and I'll jump to it. mvallevand was able to find more than three hours of EIT EPG data in that clip I posted, but based on NextPVR's current code, it'll only see, at best, three hours ahead, so we'll probably have to do it at a coordinated time. Like I said the other day, I'm also willing to start a new thread. When I replied to this thread, I was completely new to NextPVR, and it was because of the similar thread title and because the OP also happened to be using an HDHomeRun brand tuner. I'm willing to learn to use the analysis software, as well -- I'm not a computer novice, just unfamiliar with the specifics here. I've downloaded DVB Inspector and have been playing around with it.

[mmortal03]

@janoonk, any chance you've tried the program "EPG Collector" on Windows? It might be useful as a test comparison, and if you get good results, you might be able to use it on your server to work around the bug you're experiencing. It's available on SourceForge (which looks to be down at this very moment for maintenance), but people have used it to produce a XMLTV file that they can import into their PVR server. If it happened to give you the missing information, you could set up a batch command and a scheduled task on Windows to run it to produce an XMLTV file at a regular interval, and then you could have NextPVR import that file on that schedule. It may take you a little bit of time to learn how to configure its ini file to fit your TV signal, but once you have that configured, you can easily create a batch file to run it and a scheduled task to run that on a regular basis. I spent some time with it in the last day or so and was able to pull more EPG data from my OTA signal than what NextPVR is finding.

[janoonk]

Thanks for the tip. First impression: lot's of parameters!! Unfortunately don't have time right now to dive into this... but will look in the future. Thanks.
Btw: EPG Collector/Centre is Windows only and I want it to run on my (Linux) NAS... don't know if that's gonna work inside a Docker Windows container since host is Linux

I know sub is working on supporting EPG extended description, want to test that first. Have not heard anything about the status

[sub]

I know sub is working on supporting EPG extended description, want to test that first. Have not heard anything about the status

To be honest, I'd entirely forgotten I needed to revisit this for HDHR style devices. Any chance you could supply a new full transport stream capture?

There was a patch posted earlier in the thread for Windows users, with BDA devices.

[mvallevand]

Here are the instructions for the capture https://info.hdhomerun.com/info/troubles...al_channel the instructions are slightly different for DVB.

Martin