Unable to communicate with server "ServerName"

[johnsonx42]

So, could the new version cause a few second stutter on skipping ahead, pause and resume - like i am seeing since upgrading to 3.5.7?

maybe, I really don't know.

(but I'm certainly not seeing anything like that here; it's smooth as ever, on bother server and client)

[sub]

Can you see if this helps when using a client pc?

[2leftfeet]

Let me preface this by saying that the play/pause/resume/skip works okay with the 3.5.7 upgrade, just not as smooth as before, IMO - I can learn to live with it. I don't feel this issue is a game changer.

I tried the attached file, on both client and server - and cycled back & forth between the attached and 357 versions several times to try to get the best comparison.

I would have to judge that the attached file handled play/resume a little smoother than 357 in this way: when resuming/skipping ahead in the 357 version, I was noticing a second or two of slo-mo play, then afterwards at normal speed. With the attached version, resume/skip ahead play seemed to be at normal speed from the get-go.

The most noticeable issue is when pausing, where it takes a few seconds of pause-stutter-then finally complete pause. This is apparent on either version.

I still have a W8.1 client laying around somewhere running 348. I am going to give it a try to see if i can discern any differences.

[sub]

With that patch, you're back to exactly the same as 3.4.8 when you're a client connecting to a remote server. When you're operating locally on a file, then it continues to run the new 3.5.7 approach.

[2leftfeet]

I just tried running my W8.1 client, with 348, and W7-based server running 357 using the attached file on the server.

Absolutely seamless and smooth! _Every function was snappy with no delays or stutter - very sharp contrast between the 348 and 357 client.

I am not imagining what I am seeing (I think? lol).

[sub]

That patch is a client side patch. It won't do anything on the server. There was only a very small change between 3.4.8 and 3.5.7, and that patch puts it back to the original 3.4.8 logic when used as a client.

[donschjr]

attached are the logs from the client.

[liteswap]

you could try swapping in the NPVRTSReader2.ax from 3.4.8 and see if it works, and if it corrects your performance issue. I'm not aware of any changes in related code that would require the 3.5.7 version of the reader in order to function (I wouldn't necessarily be aware of any such change though, but worst case it just doesn't work).

you can extract the NPVRSetup_3_4_8.exe (download it from the 3.4.8 announcement thread) using 7-zip, then just copy over the reader like any other patch, backup your existing file of course.

OK, that worked, thanks.

[liteswap]

@turbofeet - the npvrtsreader2.ax swap was for liteswap, it's not related to your problem. please put yours back.

(yes, liteswap inadvertently hijacked your thread, I'm sure he's very, very sorry )

Humble and repentant. Sorry.

[2leftfeet]

That patch is a client side patch. It won't do anything on the server. There was only a very small change between 3.4.8 and 3.5.7, and that patch puts it back to the original 3.4.8 logic when used as a client.

Then I guess that there is something else going on. One of my clients dual boots W10 (using 357)/ and W8.1 (using 348) - same server, same client hardware, same network connection and same set of decoders (ffdshow); different client and different OS.. The 348 client handles pause/resume/skip noticeably smoother than 357. If not npvrtsreader2.ax then what is might be causing difference in play?