NextPVR Buffer Directory Question

[mvallevand]

Those logs are ok now. You probably sent logs for a session with no playback. In Kodi timeshift mode I am not sure if the rolling file logic matters. If the drive fills make sure it is not the system drive.

Martin

[chairmanfaust]

Those logs are ok now. You probably sent logs for a session with no playback.

Yeah, those logs were from when i had the opensocket statement in my xml which caused the NPVR service to crash when trying to tune to a channel

In Kodi timeshift mode I am not sure if the rolling file logic matters. If the drive fills make sure it is not the system drive.

So I thought KODI had a timeshift limit set as default to 120mins but this is just the instant record setting. I don't see any setting in the NextPVR addon (or in KODI TV settings) that allows you to limit the Live TV buffer time, I've been running a tv stream now for almost 3 hours and my .TS file is almost 23GB and climbing, this could present a bit of a problem. My next test will be to create a new partition and see what happens when it fills up.

I saw an earlier post that mentioned a registry key HKEY_LOCAL_MACHINE\Software\NPVR\SlipSeconds=x (DWORD) to limit buffer sizes. I don't seem to have this key but was wondering if this would work

[sdf]

just wanted to point out that it's many years (and many nextpvr versions) that i have the same problem in my configuration.
The directory where livetv buffer is stored fills with many .ts files with the name of the channel zapped.
Seems like nextpvr creates the buffer and then it doesn't delete it.
But, i repeat, it's a problem that next(gb)pvr always had.
Bye,
sdf

[sub]

So I thought KODI had a timeshift limit set as default to 120mins but this is just the instant record setting. I don't see any setting in the NextPVR addon (or in KODI TV settings) that allows you to limit the Live TV buffer time, I've been running a tv stream now for almost 3 hours and my .TS file is almost 23GB and climbing, this could present a bit of a problem. My next test will be to create a new partition and see what happens when it fills up.

Unfortunately this is problem with the way the NetworkRecorder works. It just creates a file that continuously grows while watching live tv.

The devices natively supported by NextPVR, then you wont have this problem. Instead they only hold a maximum of about 30 minutes on disk (spread across a few files, with oldest one being deleted every few minutes).

I saw an earlier post that mentioned a registry key HKEY_LOCAL_MACHINE\Software\NPVR\SlipSeconds=x (DWORD) to limit buffer sizes. I don't seem to have this key but was wondering if this would work

This isn't used by NetworkRecorder. It's used by the natively supported devices.

[sub]

One of these days I'll have to get around to adding native support for Ceton devices.

[chairmanfaust]

The directory where livetv buffer is stored fills with many .ts files with the name of the channel zapped.
Seems like nextpvr creates the buffer and then it doesn't delete it.

It turns out that I was using an older version of the networkrecorder.dll from the nextpvr wiki page, martin posted an updated one a few posts back in this thread... this dll is newer and it fixed my problem with nextpvr not deleting multiple .ts files when channels are changed.

I've found out from others that when the buffer runs out of space in KODI, TV shuts down and goes back to the home screen, I have an 80GB dedicated partition to the live tv buffer... I can live with that 'problem' for now

One of these days I'll have to get around to adding native support for Ceton devices.

sub... nextpvr is a great product! I've since donated and appreciate all the work and effort you and martin put into this. I also think that Ceton's PCIe tuner card is a great product too.. 6 tuners makes for a nice central media/TV server... its too bad they banked on MS WMC and then MS abandoned the product, i would hope that Ceton steps up and contributes to these open source projects.

If down the road you find time to write code to natively support Ceton's InfiniTV card, let me know, i'll be glad to test

[sub]

The issue with the Ceton device is that it is the only device I can't use or replicate the behaviour of here in NZ, so it's not straight forward to do any development for it. ie, pretty much have to develop by guess work, with no way to test it myself, which isn't really practical.

Its painful to develop this way, but at some stage I'll probably need someone to make available remote access for a day or so, to machine with a Ceton device in it.

[sub]

sub... nextpvr is a great product! I've since donated and appreciate all the work and effort you and martin put into this. I also think that Ceton's PCIe tuner card is a great product too.. 6 tuners makes for a nice central media/TV server... its too bad they banked on MS WMC and then MS abandoned the product, i would hope that Ceton steps up and contributes to these open source projects.

I should also mention, I've tried to contact Ceton a couple of times in the past, and they seem totally unwilling to talk to be me, so I'm not a big fan of the company. Other companies like Hauppauge and SiliconDust are a lot more developer friendly.

[mvallevand]

Unfortunately this is problem with the way the NetworkRecorder works. It just creates a file that continuously grows while watching live tv.

SageDCT actually. The advantage is you can actually skip and pause more than 20 minutes. Ideally I would like if NRecord supported EPGMode for streaming it makes the most sense for PVR use. As an added bonus the pause for the filename changes would be enough to keep most shows on a small drive.

Martin

[ElihuRozen]

The issue with the Ceton device is that it is the only device I can't use or replicate the behaviour of here in NZ, so it's not straight forward to do any development for it. ie, pretty much have to develop by guess work, with no way to test it myself, which isn't really practical.

Its painful to develop this way, but at some stage I'll probably need someone to make available remote access for a day or so, to machine with a Ceton device in it.

I can volunteer my machine for that. In case I forget to mention it then, the Fox owned channels are no longer usable because they forced Verizon to change the copy flag. You did provide a test for native support a while back. I think I sent you my results in a PM.