Feedback: V5 slow start up compared to V4

[dpr59]

Hi,

first off thanks for a great product.  The reason for this post is to provide feedback which I hope is useful.

I have been using V4 of NextPVR as my PVR "backend" for Kodi, on a dedicated Windows 10 PC.  I have just made the change to V5 and hit a problem that has taken me several hours to sort out.  The root cause of my problem was the change made to the start-up priority of the NextPVR service from "Automatic" in V4 to "Automatic (Delayed Start)" in V5.  On my setup this meant the NextPVR service took another ~90 seconds to start.

As my setup is a dedicated media PC used by all the family, I have tried to make it very user friendly.  Kodi is set to start automatically when the PC boots up.  It then looks to connect to NextPVR for guide information, etc.  This was fine with a "fast" starting V4, but not with the default "slow" start of V5.  It has taken me several hours to work out what was going on and then find the solution on the forum:  "You can change the service to be more like earlier version of NextPVR by changing the Startup type of the "NextPVR Service" to Automatic in Windows Service."

I would have thought my type of setup isn't that uncommon and suggest it would be helpful to mention this in the installation guide.  Something like:

“V5 of NextPVR default installation has a “delayed start” when the Windows first boots up.  If you want a fast start, this can be achieved by using the Windows Services utility to change the "NextPVR Service" start-up type from "Automatic (Delayed Start)" to “Automatic”."


Hope this feedback is useful.

[mvallevand]

This issue gets reported regularly and you should read my concern I posted yesterday https://forums.nextpvr.com/showthread.ph...#pid553025. The question is it worth losing recordings?

Note I made changes to the Kodi addon for Matrix and it will retry the connection so it will be a little smoother dealing with this delay

Martin

[sub]

As mentioned in that link, I used the delayed start option, so I could ensure tuners etc were available before NextPVR actually started, otherwise you can have recordings fail to start etc. Most people would probably be fine to switch it to start without delayed start (but some will not).

(this was an issue for v4 too)

[dpr59]

Thanks for the feedback, things are never as straightforward as they first appear.

However, you may have missed the point I am making.  V4 defaults to auto start, whilst V5 to delayed start.  This change caused the issues I described, and a lot of wasted time.  I think it would be helpful to make the issue more apparent to users, with the pros and cons explained, or my experience will just be repeated  by others.

One question.  I think it is suggested that I select the option to keep the tuners primed.  Whilst I know how to do this, I have know idea what this means.  Two questions:

1.  Will this reduce the risk of the turners not being available with a automatic start?
2.  Are there any reasons for not selecting this option?  For example, will it stop my PC from going to sleep when not in use?

Thanks again for your assistance.

Paul

[mvallevand]

The "wasted" time is time looking for drivers that NextPVR might need. You must have missed the point that sub and I both made is that this could lead to failed recordings so I pointed this out so that others would be aware that it is not necessarily a good ideas.

I personally wouldn't keep tuners primed if you use an HDHR since that means continuous network traffic. Ideally I think it is only needed if you want faster live tv response. I did suggest it to a user yesterday because his devices were failing after a long delay to see if keeping the device open would help.

There are certainly users having trouble with some devices not waking up well after sleep. Keeping them primed could make this worse.

Martin

[sub]

The 'keep digital tuners primed' shouldn't make any difference to this. It only effects the second and subsequent times are tuner is used after nextpvr is started.

[dpr59]

Thanks again for further prompt replies and your advice.

Martin, the "wasted" time I have mentioned wasn't related to the time difference between a fast and delayed start, but the time I spent trying to work out why V5 wouldn't work with my setup when V4 had. It took me several hours to determine that it was the slower start of a default V5 configuration when compared to V4, and then find the answer on your comprehensive forums. Hence, my suggestion that it may be helpful to make this change, and its potential consequenes, more apparent in the installation guide. Just trying to be constructive.

Paul

[Graham]

Hence, my suggestion that it may be helpful to make this change, and its potential consequenes, more apparent in the installation guide.  Just trying to be constructive.

Because you asked so nicely ...

https://github.com/sub3/NextPVR/wiki/Setup-Main

https://github.com/sub3/NextPVR/wiki/Troubleshooting

[dpr59]

Thanks.

I am sticking with V5 with a fast start for now. No problems so far, but with all the useful information provided above I know to look out for recording problems.

Best wishes,
Paul

[mvallevand]

Since it is on the wiki it comes across as a recommendation. There should be a warning that it is possible to lose recordings if they make the change.

Martin