Shout out to
jaytaylor@gmail.com, and anyone that has the jarring stream stops momentarily, buffers, and then whizzes by for a second or two. I've found another way this can happen -- if the input stream is missing any TS packets (continuity errors), this will also happen. I'm currently experiencing this on TNT-HD here.
For me, it's weird, it happens at precisely on an hour marker. It's like clockwork, if I'm on TNT I can count down to the glitch in 5, 4, 3, 2, 1, boom. I posted an inquiry in the hardware forum since I'm not sure why this is happening, if it's my tuner, or if it's the RECORD engine, but I
think I can rule out the source stream itself.
Regardless, I have a job for y'all, if you're game

I now know it's definitely not the PVR that glitches, it's the audio sink in Kodi that freaks out and tries to catch up. This is why there are never any logs or anything from the PVR saying it had a problem, it didn't. So, here's what I would request from those so inclined to play around since my pool of bad channels is very small.
- Record some stuff on the channels causing you the problem
- Install "TSDuck" somewhere (it's safe) -
https://tsduck.io/
- Run the command-line tsfixcc application against some of the recorded .mpg files.
IMPORTANT: Use the "-n" option. E.g. -- "C:\Program Files\TSDuck\bin\tsfixcc.exe -n {path to .mpg file}"
- Let me know if you find these files frequently have errors in them.
Here is a full example of me running tsfixcc against a program I recorded on TNT-HD, and what I saw. This recording will glitch very briefly when viewed after the fact, but when I watch TNT-HD live Kodi freaks out:
Code: Select all
C:\Program Files\TSDuck\bin>tsfixcc -n "\\xxxxxxxxxx\hdhomerun\movies\The Mummy Returns 20010504 [20200129-2230].mpg"
packet index: 26,216,352, PID: 0x177B, missing 1 packets
packet index: 26,216,353, PID: 0x177B, missing 9 packets
packet index: 26,216,354, PID: 0x177B, missing 8 packets
packet index: 26,216,356, PID: 0x177B, missing 4 packets
packet index: 26,216,357, PID: 0x177B, missing 3 packets
packet index: 26,216,359, PID: 0x177C, missing 7 packets
packet index: 26,216,360, PID: 0x177B, missing 11 packets
packet index: 26,216,362, PID: 0x177B, missing 3 packets
packet index: 26,216,364, PID: 0x177B, missing 1 packets
packet index: 26,216,376, PID: 0x177C, missing 7 packets
packet index: 26,216,423, PID: 0x177D, missing 1 packets
packet index: 26,216,425, PID: 0x177F, missing 1 packets
packet index: 26,216,522, PID: 0x177A, missing 4 packets
packet index: 26,291,441, PID: 0x1780, missing 5 packets
packet index: 61,720,304, PID: 0x177B, missing 6 packets
packet index: 61,720,306, PID: 0x177B, missing 2 packets
packet index: 61,720,308, PID: 0x177B, missing 11 packets
packet index: 61,720,310, PID: 0x177B, missing 5 packets
packet index: 61,720,320, PID: 0x177A, missing 1 packets
packet index: 61,720,327, PID: 0x177F, missing 15 packets
packet index: 61,720,752, PID: 0x0000, missing 7 packets
Note there are two "instances" of missing packets here, it's not 20+ individual errors. In this particular case I think the first instance is because I was spinning up more tests, but the latter instance may have occurred at exactly 7:00PM my time.
Optional stuff, of course, and only if you're comfortable with it. If this is what is happening for jaytaylor, there is nothing I will be able to do to fix it, missing packets are missing packets, but I can still try to find where in Kodi this causes it to completely flip out instead of just glitching a bit like I think it should. But, if others are having the same problem on different sources, perhaps there is something SD may be able to do to help us make the problem go away, which would also solve it
Thanks gang!!!