Instead of having to create the registry key HKEY_LOCAL_MACHINE\Software\NPVR\SlipSeconds=xxxx to increase the Live TV buffer, can this be an option listed on the Settings -> Misc section?
It would be nice, but there are permissions related problems with that. I guess if the installer creates the registry key and sets the permissions on that key correctly, then NextPVR running as a regular user could modify the setting.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
It's not really permissions, it is the fact that the DirectShow graph components don't read config.xml, they use the registry (great if you want to use them without an install. That being said, this isn't really a buffer as I think about it controls how much time-shifting you can do. I personally think you can get yourself in trouble if it is too large.
mvallevand Wrote:It's not really permissions, it is the fact that the DirectShow graph components don't read config.xml, they use the registry (great if you want to use them without an install. That being said, this isn't really a buffer as I think about it controls how much time-shifting you can do. I personally think you can get yourself in trouble if it is too large.
Martin
I typically put on Live TV (especially sports) and always end up pausing it for 15-30 minutes to do something else. Before I came across this registry setting, I had about a 6 minute buffer and then I'd lose my place in the show. With the larger buffer it's nice to skip through all the commericals, halftime, etc. and just actually watch the game itself. Is this a setting that could be incorporated into the config.xml if there are constraints by adding it to the registry?
mvallevand Wrote:It's not really permissions, it is the fact that the DirectShow graph components don't read config.xml, they use the registry (great if you want to use them without an install.
Yes, but my point was that permissions would possibly prevent NextPVR.exe from changing that registry value, unless the permissions were properly set on the value during installation (which runs elevated).
Quote:That being said, this isn't really a buffer as I think about it controls how much time-shifting you can do. I personally think you can get yourself in trouble if it is too large
I once asked sub that exact question, whether there would be any adverse consequence to setting the SLIPSECONDS too big (aside from the obvious possibility of running out of disk space), and he said no, nothing he could think of.
server: NextPVR 5.0.7/Win10 2004/64-bit/AMD A6-7400k/hvr-2250 & hvr-1250/Winegard Flatwave antenna/Schedules Direct main client: NextPVR 5.0.7 Desktop Client; LG 50UH5500 WebOS 3.0 TV
I used to use a large buffer, but too many times a recording kicked in when I was timeshifted and I lost everything I wanted to watch. The short buffer makes me remember to record things I want to watch.
Having searched a bit, it's not clear whether, for example, to set the buffer to 7200 seconds, you should go into HKEY_LOCAL_MACHINE\Software\NPVR and create a DWord called "SlipSeconds=7200", or create a DWord called SlipSeconds, and then set the value to 7200 (decimal).