NLite/comskip

[sub]

Keep the next recording and supply it to me, so we can compare results on the same file.

[mvallevand]

Just tested another recording. NLite ignores the comskip markers, NextPVR skips them with the same recording. This is on the same machine.

Is it a comskip 0 file?  If so edit the  edl file and set the start value to 5 and see if it skips properly.

Martin

[sub]

The previous example file he supplied did have a comskip advert that started at 0, and it started really well with playback at 75 seconds in. Right when the show started.

[mvallevand]

Did you try with a resume? The bug I refer to which you are are well aware of, is that you don't supply the recording_id API open on resume so it forces /stream?f= which is not good at comskip in my experience.

Martin

[sub]

No, I didn't try a resume. I just started playback.

[sub]

is that you don't supply the recording_id API open on resume so it forces /stream?f= which is not good at comskip in my experience.

FYI, I have made a slight change to /stream?f= to help with skipping in ts files. (support for range= url param)

I had notice an issue skipping at all with video library playback in NLite. Skipping in recording playback was fine, because it was using /live?recording=

[artmetz]

Sending another recording via PM. (KREM 2 News at 5)
NLite log included.

Edit: this one skips the beginning comskip section, but not the second.

[mvallevand]

That  will have a comskip 0 problem but NLite isn't sending range requests with recordingid which is a second problem.

Martin

[sub]

Edit: this one skips the beginning comskip section, but not the second.

I was seeing this same behaviour. I've updated client.zip. Let me know if it helps. (slight chance you'll also need the next release of NextPVR to fix)

[artmetz]

sub,
Better now. Did a quick test with the KREM 2 recording and it skipped at the start and the second comskip location. I'll do more testing tomorrow.
Art