Prime Digital Tuners setting

[Red5ive]

I see there is a 'Prime digital tuners primed' tick box under devices. What does this setting actually do and what advantages/disadvantage are there to me using it.
I have a Hauppage Quad DVBT tuner as my primary device.

[sub]

On Windows, it basically tell the application to keep the tuners running after their first use, allowing subsequent attempts to start live tv / recordings to trim off the couple of seconds required to hook them up and start them. The disadvantage is they're in use if you've got other applications which want to use the tuners.

On Linux it does nothing.

[Red5ive]

NextPVR will be the only application using the tuners so thats not a problem.
Does it mean they will be using more power/resources though? Do they power down again after a set amount of time?

[sub]

Does it mean they will be using more power/resources though? Do they power down again after a set amount of time?

No, it doesn't power them down again. I doubt most TV tuners use much power though. If you want them to power down, leave it unchecked.

[mvallevand]

On Linux DeviceHostLinux does hold the tuner after use so it can't be used by other apps.

Martin

[sub]

On Linux DeviceHostLinux does hold the tuner after use so it can't be used by other apps.

Yeah, but that's a bug rather than anything to do with this setting.

[Red5ive]

In the server window I see a lot of activity with these same lines appearing over and over again, even with no clients open or recordings taking place:

[105] http://localhost:56986/status
[105] http://localhost:52207/status
[105] http://localhost:50157/status
[69] http://localhost:56986/status
[69] http://localhost:52207/status
[69] http://localhost:50157/status
[69] http://localhost:56986/status
[69] http://localhost:52207/status
[69] http://localhost:50157/status
[101] http://localhost:56986/status
[101] http://localhost:52207/status
[101] http://localhost:50157/status
[105] Got request [::1]: /service (recording.lastupdated)
[105] method=recording.lastupdated
[105] parameters:
[105] method: recording.lastupdated
[105] sid: 06e3874c20d54ad38ee0e77ceac15c1b
[105] format: json
[105] client_ip: ::1
[105] host_callback: localhost:8867
[105] LastUpdated
2020-01-20 12:05:07 Renewing session: 06e3874c20d54ad38ee0e77ceac15c1b
[105] {"last_update":1579491440}

I assume this is from having the digital tuners primed option on. Will this be creating tons of server logs or does it have minimal impact on performance?

[sub]

In the server window I see a lot of activity with these same lines appearing over and over again, even with no clients open or recordings taking place:

[105] http://localhost:56986/status
[105] http://localhost:52207/status
[105] http://localhost:50157/status
[69] http://localhost:56986/status
[69] http://localhost:52207/status
[69] http://localhost:50157/status
[69] http://localhost:56986/status
[69] http://localhost:52207/status
[69] http://localhost:50157/status
[101] http://localhost:56986/status
[101] http://localhost:52207/status
[101] http://localhost:50157/status
[105] Got request [::1]: /service (recording.lastupdated)
[105] method=recording.lastupdated
[105] parameters:
[105]    method: recording.lastupdated
[105]    sid: 06e3874c20d54ad38ee0e77ceac15c1b
[105]    format: json
[105]    client_ip: ::1
[105]    host_callback: localhost:8867
[105] LastUpdated
2020-01-20 12:05:07    Renewing session: 06e3874c20d54ad38ee0e77ceac15c1b
[105] {"last_update":1579491440}

I assume this is from having the digital tuners primed option on. Will this be creating tons of server logs or does it have minimal impact on performance?

These /status calls are just related to the tray app polling the current status of the services. These have very minimal impact.