Slow startup

[arrbee99]

Further to comments over on Emby Forum, and briefly mentioned on this forum, item 'syncing', am finding v5 starts to play channels in Chrome using localhost:8866 in about 17 seconds, while the same starting in vlc take about 9 seconds. Am hopefully attaching a log from NextPVR from the localhost:8866 Settings page.

[mvallevand]

I don't see the /live attempt from Emby, it should contain /live?channeloid=##&client=EMBY.## I think there is too much spam for playing through a browser which will have slow startup.

I think you need to see what the startup time is using NextPVR.exe as a baseline.

Martin

[arrbee99]

I have no idea what those logs show or how far back they go, but they were asked for. The most recent attempts to play anything in there were in localhost:8866 and I think sub wanted to see why it takes so long from pressing play to it starting playing.

Personally I wouldn't have though NPVR logs would mention Emby at all, but you would of course know a lot more about such things.

Nextpvr.exe averages 15 seconds.

Edit - forgot to mention, this is using a Hauppauge pci-e dvb-s card.

[sub]

It's a bit hard to follow the logs with logs going on.

Can you restart NextPVRServer (so that it creates a new empty log file), then try watching one channel via VLC. Once you see video, leave it running for say 30 seconds, then zip and attach the logs and I'll take a look. Hopefully that should give us a log just showing the live tv startup, streaming to VLC.

[arrbee99]

Hopefully this worked. If not, let me know.

[sub]

Thanks - those are better logs.

[sub]

I can see it is taking 5+ seconds to start the device:

2019-06-20 15:51:52.122 [DEBUG][4] Starting graph...
2019-06-20 15:51:57.445 [DEBUG][4] Calling LockChannel()

I can see it's taking 2.4 seconds to tune to a frequency

2019-06-20 15:51:57.483 [DEBUG][4] About to submit tuning request
2019-06-20 15:51:59.872 [DEBUG][4] tuning request submitted (12456000)

So about 7.5 seconds is taken up these two calls. These are both hardware/driver things that unfortunately cant be avoided, so it's sounding like a fairly slow device. This isn't ideal, and there is probably not much that can be done to trim these.

While the startup time is disappointing, at least once it's started you shouldn't get that same type of hit changing channels etc. Also, in NZ you'll often be changing to channels on the same frequency (ie, TV1 -> TV2 etc), where no tuning is required.

[sub]

We might able to do something down the road, like adding an option to auto start the devices when NextPVRServer.exe starts, trimming off that 5+ seconds. (and we just throw away any data that comes from the device until it's needed)

[arrbee99]

Oh well, am stuck with dvb-s, there's a hill in the way of dvb-t and Homeruns and stuff. Hopefully they'll come up with a few more channels on iptv.

True it is quicker changing channels once started. Wish Emby had proper channel swapping...

You don't think its possible to speed up start up under localhost:8866 at all ?

Edit: that option sounds handy.

[sub]

You don't think its possible to speed up start up under localhost:8866 at all ?

Edit: that option sounds handy.

The time required to start device is ultimately down to that how quickly the device and it's drivers are. There is no real way to remove that time.

I could look into that option of starting the device at startup, and leaving it running, so that that 5+ seconds happens long before you actually try to use the device. That'd help the perception with your device. I've tried to avoid that type of thing in the past, so that other applications can use the device if they need to.