2018-02-10, 01:32 AM
Thanks that logging is collecting some good info now - can you supply one of those defective recordings? I'd like to match up what I'm seeing in the logs against an actual file.
2018-02-10, 01:32 AM
Thanks that logging is collecting some good info now - can you supply one of those defective recordings? I'd like to match up what I'm seeing in the logs against an actual file.
2018-02-10, 01:47 AM
sub Wrote:> Thanks that logging is collecting some good info now - can you The files are quite big, since I didn't cancel. Can I use your CutChunk program, and if so, what size?
2018-02-10, 02:42 AM
Maybe something in the 50MB - 100MB range? Put it somewhere like dropbox or one drive.
It'd be worth confirming if you can play that chunk or not. Hopefully it'd still be defective.
2018-02-10, 02:49 AM
You're using an HDHomeRun Prime right? Are you actually using a CableCard, or are these QAM channels? Looking at the logs I'm starting suspect you're using QAM, rather than a CableCard lineup, and this is a major factor in the problem you're seeing.
2018-02-10, 03:53 AM
sub Wrote:> Maybe something in the 50MB - 100MB range? Put it somewhere like Here are the two uncut files, each about 1 GB in size: http://jxenakis.com/gdgraphics/FNC-6-7pm...8001900.ts http://jxenakis.com/gdgraphics/CNN-6-7pm...8001900.ts sub Wrote:> You're using an HDHomeRun Prime right? Are you actually using a I am absolutely, positively using an HDHomeRun Prime with a Comcast CableCard. I really don't know anything about QAM channels but take a look at my message in the previous thread about setting up the HDHR: https://forums.nextpvr.com/showthread.ph...post520553 One of the setup issues had to do with QAM channels, which I didn't understand and I ignored. Maybe that has something to do with the problem.
2018-02-10, 04:02 AM
Quote:I am absolutely, positively using an HDHomeRun Prime with a Comcast CableCard.I can see from your tuning strings that it is using QAM channels on this device, not CableCard channels. This causes the streams to start a different way than you'd usually get with a Prime configured correctly for using a CableCard. Quote:<sid>2607</sid><tsid>0x6555</tsid><map>us-irc</map><chan>19</chan> I'm not sure if you remember scanning NextPVR on your cable card device? You should have got the complete channel list immediately, like a second or so after the scan started. I suspect you didn't get that, and instead your saw it work through different frequencies etc, looking for channels. I'm not in the US, so don't use these devices myself, but I suspect either your CableCard wasn't activated in your Prime, or your needed to do a scan in the SiliconDust app before scanning in NextPVR. I would backup your npvr.db3, so you can get back to it later, delete your channels (on the Settings->Channels screen), then try scanning a device again to see what happens.
2018-02-10, 04:38 PM
johnsta Wrote:I am absolutely, positively using an HDHomeRun Prime with a Comcast Your comments indicate that you were using the instructions from the non-CableCard section of those instructions (labeled "NextPVR Configuration â ATSC/QAM/DVB-T/DVB-C") instead of the CableCard section of the instructions (labeled "NextPVR Configuration â HDHomeRun PRIME"). I'd suggest following sub's advice to back up your npvr.db3 file and then have it create a new database to test with. But make sure that you follow the steps to configure the HDHR Prime first. Specifically, steps 5-9: Code: 5. On the Tuners tab, set the Signal Source to CableCARD for each of your HDHomeRun PRIME tuners.
2018-02-10, 06:42 PM
sub Wrote:> "I am absolutely, positively using an HDHomeRun Prime with a That's kind of a big project, and a little scary. I'll try it, but first I'd like to ask you to check something else out. I know that Comcast changes its digital cable encoding at times, and this includes issues involving QAM. I'm giving you links to two articles. I'm not claiming that these articles are directly relevant to our situation, but only to illustrate the fact that encoding formats frequently change, and that Comcast was planning encoding changes by the end of 2017: http://www.dslreports.com/forum/r3133742...Year-Rumor http://forums.xfinity.com/t5/Non-X1-Serv...-p/2806786 I also make note of the fact that this defective TS file problem also occurred with my Ceton card, though a lot less often. As a matter of fact, I installed the HDHR on Dec 6, but the problem only started getting bad on Dec 26. For example, the "WBZ news at 11" files were OK before Dec 26, but were defective after that date. Nothing that I did changed on Dec 26. So what I'm suggesting is that this problem always existed, that it had nothing to do with the switch from Ceton to HDHR, but is caused by Comcast encoding formats are the source of the problem, and that Comcast end-of-year encoding changes have made the problem worse. The following are two half-hour shows that have the same defective recording problem. They were both recorded using my Ceton card. One is from May, 2016, and the other is from October 2017. http://jxenakis.com/gdgraphics/blackish...._100208.ts http://jxenakis.com/gdgraphics/Brooklyn...._093001.ts Here's some additional information that seems strange: blackish recordings in both 5/16 and 10/17 are almost all defective. Brooklyn99 recordings in 10/17 are almost all defective. In 5/16 and 10/17, there are almost no other defective recordings. Once again, this indicates to me that, as in the case of "WBZ News at 11," Comcast is broadcasting these particular programs in a uniquely different way that has nothing to do with the NPVR scan. Please check out these two files, and see if they have the same issues as the latest recordings. If they do, I believe that would isolate the issue to Comcast's encoding formats. Thanks, John
2018-02-10, 08:11 PM
johnsta Wrote:That's kind of a big project, and a little scary. I'll try it, butIt should only take you a few minutes to try that theory. Just make sure you backup the npvr.db3 first, and you can just rename it back when you've finish testing. This will get you back to where you were originally. What you want to see, is that when you view the 'HDHR' device on the Settings->Devices screen, then hit 'Scan', you want the full list of channels to appear within a couple of seconds. (ie, it wont make its way through scanning different frequencies etc)
2018-02-10, 09:08 PM
BrettB Wrote:> Your comments indicate that you were using the instructions from sub Wrote:> It should only take you a few minutes to try that theory. Just OK, I'll try it tomorrow. In the meantime, if you want any data from the data base, let me know and I'll get it. Even better, give me a sql statement and I'll run it for you. |
|
Possibly Related Threads… | |||||
Thread | Author | Replies | Views | Last Post | |
ts file shows length too long? | SuttonWillow | 2 | 1,931 |
2021-03-15, 01:56 PM Last Post: mvallevand |
|
ts file shows length too long | SamM | 4 | 2,342 |
2020-10-06, 02:45 AM Last Post: Ehrlichia |
|
Possible to record in different format than .ts files? | gadgetgaz | 29 | 12,911 |
2020-10-04, 03:05 PM Last Post: Ehrlichia |
|
Log files | Brucek2839 | 1 | 1,210 |
2020-03-23, 02:37 AM Last Post: mvallevand |
|
Generate missing thumbnails for video files imported into NextPVR | Jimixter | 7 | 3,169 |
2019-12-17, 01:32 PM Last Post: mvallevand |
|
Incorrect length of recording | Ehjay | 11 | 3,372 |
2019-11-28, 08:08 PM Last Post: mvallevand |
|
Comskip edl files ignored | dbguru | 3 | 2,220 |
2019-10-24, 06:11 PM Last Post: mvallevand |
|
log files for streaming outside network | MaxOne72 | 9 | 2,647 |
2019-07-26, 05:32 AM Last Post: persim |
|
nfo files not deleted on show deletion? | jksmurf | 30 | 8,787 |
2019-02-18, 12:13 AM Last Post: jksmurf |
|
Local Files | snaitaz | 3 | 1,889 |
2019-01-02, 01:32 PM Last Post: snaitaz |