Recording length error

[VCR58]

I'm having issues with playing some NextPVR recordings. The one I am currently having trouble with is NFL Football Dallas Cowboys at Philadelphia Eagles recorded 11/05/2023 at 3:25pm

The problem is the recording is over three hours long but in all the NextPVR clients and Web client the recording only reports 15 minutes in length. I have only seen this with recordings using the Tablo tuner + Extra so far.

The same recording actually plays fine in Kodi and reports the correct duration of 3hrs 21min.

Do the logs show any clues as to what is happening?

Thanks

[VCR58]

Even though Kodi reported the correct duration of 3:21:00 there is still a problem with the video file as I had issues with skipping so the file was corrupted.

A remux of the video file seems to correct the duration reporting with the NextPVR clients.

[sub]

Does it have a timing file?

If you've still got an example file not remuxed, I'm happy to take a look at it.

[mvallevand]

Kodi only reports time based on what is in the database bad seeking will be because of the bad time stamps.

I did make a request the UI client use the timing file but seeks are still based on media info which doesn't handle bad time stamps either

The original info for the database is good

Code:

2023-11-06 17:54:14.537    [DEBUG][47]    ClientGetActivity() returning:
{
  "level": 3,
  "url": "/stream?client=default&f=%2Fmnt%2Fsda1%2FRecorded_TV%2FNFL%20Football%2FNFL%20Football_20231105_15251830.ts",
  "screen": "player",
  "recording_id": "24556",
  "recording_name": "NFL Football",
  "recording_title": "NFL Football",
  "recording_description": "The Cowboys visit the Eagles. Philadelphia sits atop the NFL with a 7-1 record, and paces the NFC with 224 points scored. A.J. Brown (PHI) became the first player in NFL history to record 125-plus receiving yards in six consecutive games on Oct. 29.",
  "recording_subtitle": "Dallas Cowboys at Philadelphia Eagles",
  "recording_duration": "12060",
  "recording_size": "16168918944",
  "supports_server_skip": "true",
  "file": "/mnt/sda1/Recorded_TV/NFL Football/NFL Football_20231105_15251830.ts"

}

but seeks have the wrong duration so the calculated range header is bad.

Code:

2023-11-06 17:54:37.443    [DEBUG][94]    ClientGetActivity() returning:
{
  "level": 3,
  "url": "/stream?client=PC&seek=78&f=%2Fmnt%2Fsda1%2FRecorded_TV%2FNFL%20Football%2FNFL%20Football_20231105_15251830.ts",
  "screen": "player",
  "skip_to": "78",
  "duration": "928",
  "range": "14964303492-"

}

I'd be curious to see the timing file too

Martin

[VCR58]

Thanks.

Here is the timing file. And a link to Cut Chunk of the unremuxed file

https://1drv.ms/v/s!ArMMuDTvT3Aivn9eWyop...a?e=xeHlPN

[mvallevand]

That's what I expected and why I like the v4 timing.info better since it doesn't care about bad timestamps.

Code:

frame,95639.112389,14766074224
frame,195.644944,14766531252

You would need the cutchunk to start about 14754616000 bytes or maybe a bit earlier to capture the timestamp issue.

I will check to see if that is a TabloTV issue after 95k ms.

Martin

[VCR58]

Cut Chunk maxes at 1G so from the end of the file that won't do. 15G is my total Google drive capacity and One drive is only about 4G I think.

If it matters, this recording is the second of back to back NFL recordings on the same channel. The first one played fine I think. Also, NextEnd was running.

[mvallevand]

On Linux you can use dd maybe something like this (dd is powerful be careful)

dd if=filename.ts of=chunk.ts bs=188000 skip=78542 count=1000

Martin

[VCR58]

Here is what I got using "bs=188000 skip=78542 count=1000" https://1drv.ms/v/s!ArMMuDTvT3AivwDsr63b...w?e=aYmsHL

Hopefully it's in the right spot.

[mvallevand]

It isn't corret but I might be able to give better directions if I get the calculator out tomorrow.

If possible can you give a link from normal OneDrive and not photos next time? These are are hard to download with Firefox.

Martin