4.0.4 Skips Hang Playback

[jd1940]

I'm not sure I understand what you're supposed to do with the patch. I know where it goes but does it replace the reader2.ax that's there or do you just add it to the .ax files that are there.

[sub]

I'm not sure I understand what you're supposed to do with the patch. I know where it goes but does it replace the reader2.ax that's there or do you just add it to the .ax files that are there.

Assuming you're using NextPVR 4.0.4, then you'll have an existing NPVRTSReader4.ax file. The updated version, will replace that existing file of the same name.

[jd1940]

I'm using 3.9 for the client. Does that mean the patch doesn't work for that version? It has the reader2.ax.

[sub]

I'm using 3.9 for the client. Does that mean the patch doesn't work for that version? It has the reader2.ax.

No - I only ever do patches and updates for the current release.

[mvallevand]

I'm using 3.9 for the client. Does that mean the patch doesn't work for that version? It has the reader2.ax.

You posted you updated https://forums.nextpvr.com/showthread.ph...post517617 Also again note you need to run the same version on the client and the server.

Martin

[jd1940]

I've gone back and forth on the client trying to find something stable. I'm currently running the early 4 on the server and 3.9 on the client. The client is the most stable this way. I virtually never use the server version to watch, just for scheduling. Currently, the client is stable except for the occasional 'freeze'. But, both of the 4 versions were very poor on the client/server, with skip problems, non-functioning ComSkip. numerous screen aritifacts, jumpy playback and numerous freezes. It was so bad I called my cable company out on three different occasions to complain about the TV quality. On each occasion they found nothing and then I noticed my other TV, which doesn't use NPVR, and which I almost never watch, was working just fine. It was so bad I installed both Kodi and Plex in an attempt to improve video viewing but really didn't care for either's format, although they both played better than NPVR 4.0.4. I could roll the server back to 3.9 but it wasn't any improvement over what I'm doing now so I just haven't bothered. I don't want to complain constantly so I've just decided to set back and hope that sometime in the future 4.0.4 becomes more stable.

[sub]

The new combined TSReader+Demux introduced in 4.0.4 was a very substantial change. It gives the application control over a lot of things it had no control over in the past, giving faster channel changes, and compatibility with popular free decoders like LAV etc. This was a big change, and gone ok - there was always going to be some teething problems, and it is complex. When time permits, I'm working through issues people have reported, and we've fixed a lot of the things reported.

I left the old TS Reader / Microsoft Demux as an option, so that those who were having serious problems had the option of going back to the original playback components.

It's worthwhile people continuing to hassle me over issues, because if you've got an issue, it's likely to be exactly the same in the next release unless you help me work through it.

While the move to the new component has been a bit painful for some, it's definitely worth it for the project in the long run.

[Tacoma]

I have stumbled across a combination of patches for 4.0.4 along with K-Lite 13.5.8 LAV codecs that is functioning without any playback problems on my 2 PC's. I posted the information and a zip file of the patch file combination under in the post heading "Playback problems resolved" yesterday.

[pBS]

seems to me like it's trying to play too fast before data is ready..[the non-starting channels, and maybe solve the jittery play too]
could you add a delay to see if this is the case? [with old buffer setting]

the added buffer is really messing up *all* my mpeg2 playback.. i figure the added buffer is delaying start so maybe only seems like solve for problem..

[pBS]

still working on this? so close..

anyways, a bit off topic but it still thinks it's somewhere that it's not when skipping...it assumes it's 1 place, and when you skip, it takes you to where it thinks you should be, which is off by a predictable amount...[the longer it plays, the farther off it is] something does seem to update it properly, like pause maybe, or after skip it updates timeline? [pause works]
i doubt skipping will ever work right until that is fixed..
this is on *any* video type, not just mpeg2..

confirmed, after just 2 minutes of playback, a skip forward 8 secs actually takes me backwards 1 second..
the timeline at top shows that it skipped ahead 8 secs..but the video shows otherwise...!
and it does seem like a pause before skipping is updating current playtime..if i pause before the skip, it skips as it should..

i have a feeling this is all about ntsc framerates.. [tho i easily could be completely wrong!] how the framerate isn't actually 29.971.. but actually 30000/1001..or other common probs when dealing with ntsc standards..
tho i could be totally wrong about that.. so many possible places of failure. but i think the problem lies in this area...[current playback position and total]

it just seems so predictably off, has been for years with npvr. back in pvrx2 days was last time it was perfect knowing where it currently was for skips.
and i notice people have had problems with skipping oddly ever since.

i would just go back to old reader, but it seriously has a problem..locks up npvr...not a single lockup with new reader so something definitely is different there..
the filter may be the same, but maybe it's interfacing with program isn't. it plays along fine... then all of a sudden it chokes to death..needing end task to restart.