Client very slow to start

[KiwiGlen]

I have NextPVR running as a server on one PC and a second PC that runs as a client.

When I start NextPVR on the client PC its takes about 30 seconds to load.

Looking at the log there seems to be a big gaps between two of the entries (see below)
2014-09-30 20:53:36.896 [DEBUG][1] Load@7
2014-09-30 20:53:57.910 [DEBUG][1] Setting override for <ExtraRecordingDirectories> to:
2014-09-30 20:53:57.910 [DEBUG][1] Load@8

I've tried changing a few things but can't seem to fix this.

I tried adding an extra recording directory on the client but that seems to get dropped as soon as I exit.

Anybody got any ideas?

[HarryH3]

Bump. I'm seeing the same thing, only the delay is even longer. I'm seeing a delay of 60+ seconds, as shown here:

014-12-29 08:31:14.574 [DEBUG][1] Load@4
2014-12-29 08:31:14.574 [DEBUG][1] Load@5
2014-12-29 08:31:14.574 [DEBUG][1] Load@6
2014-12-29 08:31:14.650 [DEBUG][1] Load@7
2014-12-29 08:32:17.669 [DEBUG][1] Setting override for <ExtraRecordingDirectories> to:
2014-12-29 08:32:17.669 [DEBUG][1] Load@8
2014-12-29 08:32:17.669 [DEBUG][1] Load@exit
2014-12-29 08:32:23.194 [DEBUG][1] Frame Render Rate=7.28650188446045

Is there a setting I need to change on the client?

Thanks!

[Reddwarf]

Are you guys using server name or ip-address in the fields for server/share? Address may be faster.

[HarryH3]

Aha! I had \\192.168.104.105\npvr for the share name, but had the "friendly" name (DVR-1) in the server field. Why would that take a full minute to timeout or resolve? Changed the server name to \\192.168.104.105 and now the client fires up almost instantly.

I now recall this coming up in the past, but I don't remember it making such a huge difference. I guess I was too focused on what "Load@7" meant in the log.

Thanks Reddwarf!

[Reddwarf]

Why it is taking so long is a little mystery, but I'v found that if you have all your computers with fixed ip listed in the \windows\system32\drivers\etc\hosts file it is much faster with names. Something in windows is taking a long time to resolve names (sometimes).

[HarryH3]

The delay seems to be unique to NPVR here. I can connect to the same system via UltraVNC or Remote Desktop using just the friendly name instantly. I also get instant responses when I ping it using just the name. Just another of lifes' mysteries...

[Reddwarf]

The delay seems to be unique to NPVR here. I can connect to the same system via UltraVNC or Remote Desktop using just the friendly name instantly. I also get instant responses when I ping it using just the name. Just another of lifes' mysteries...

Yeah, perhaps something for Sub to look into.

[sub]

If you bump the thread tomorrow (when I'm back from few days away), I'll check it out.

[HarryH3]

Bump, as requested.

[sub]

2014-12-29 08:31:14.650 [DEBUG][1] Load@7
2014-12-29 08:32:17.669 [DEBUG][1] Setting override for <ExtraRecordingDirectories> to ...

All it's doing between these two points is asking the server what it's recording directory is. I suspect you've got something slow happening with the name resolution, or something similar, leading it to being really slow to find the server.

You could maybe try specifying the ip address instead of the name.