Last week my recordings no longer had a timeline at the bottom of the screen. Instead it was the program description. From what I recall it was about the same time as I installed Google Chrome as my internet browser. That can't possibly be related can it?
In a rush to free up space tonight I deleted an entire series we hadn't gotten round to watching and doing it via NPVR is a bit tedious when you have 20 recordings to delete so I did it through explorer. Will NPVR eventually pick up the missing files and clean up the recordings list or am I going to have to still delete them manually?
No a biggie but I've been down this road before when we realise the 1TB is filling up and have to go through and do a purge.
Posted by: mobiusnz - 2017-11-28, 08:03 AM - Forum: Wishlist
- No Replies
Had a bunch of recordings fail due to lack of disk space. Found one freak recording that was 125GB and made the wife go through and she found 200GB of stuff she didn't need
I had setup a second recordings folder on another drive but you can only set it to choose the drive with the most space - What about having a failover that it will record to if there is too little space on the primary.
My main recording space is on a 2 drive stripe to help it cope with multiple records symeltaneous without throughput issues. The OS drive has 700GB free but being a single drive I only want to use it in the even of otherwise missing recordings.
I'm not too bothers as TV is so bloody crap these days there are only about two series on Free to air TV I actually want to watch but happy wife happy life
Hi all, I'm utilizing live TV in Emby with the nextPVR plugin. I pulled EPG data from zap2it with the following command (manual execution of this specific command file):
That should have pulled 7 days of data, correct? But in Emby and in nextPVR, even after I've restarted nextPVR, there is only one hour of data showing. Any particular steps to follow before submitting a log? Thank you.
I installed nextpvr to use with emby, and i have a problem where the NPVR service stops randomly and needs to be manually started again. This occurs when using emby as the front end, through kodi, and also just using the nextpvr player itself. It happens with quite a high frequency, and makes the server nearly unusable as a PVR. Could someone point me in the direction of a fix for this issue or help me troubleshoot what might be causing this? I'm using the latest release on windows 10 x64, and I'm using an m3u IPTV service. All channels come in clearly and buffering is not a big issue.
I've attached my log directory. I also am wondering if it is possibly related to the decoders I'm using. Is there a preferred decoder configuration for all codecs, such as LAV, or is it best only to use the Microsoft codec for stability? (or is this even related to this particular problem?)
One thing I've noticed is a 'graph stopping...' message at the end of the log file when the crash occurs, but I don't know how to troubleshoot that error.
Thanks
EDIT: I also noticed that a crash.mdmp file was requested in another thread that might be related, so I've attached that file as well.
Hi all, I've got a channel that I'm trying to watch (18.9). It shows up fine in the HDHR app inside Windows, but when trying to view on NextPVR in its own application or via Emby it does not load anything. Logs attached. Thank you.
EDIT: Also to add, I am able to watch other channels in nextPVR.
I'm currently looking to build a whole house DVR using a mini pc running NextPVR and hdhomerun as a tuner. I order to minimise costs by cutting the PC performance, can someone tell me which device is technically recording the stream between the hdhomerun and the running PC? (i.e. which one is working hard on cpu usage).
I can't find the info I'm looking for anywhere so I decided to ask it here..
To people using nextpvr and hdhomerun tuner, do you still need to pay the annual 35$ subscription for the hdhomerun app? Is using nextpvr alone (without hdhomerun app) working fine to schedule recordings?
This morning I attempted to view a live TV channel in Kodi and got a tuner not available message.
My NextPVR server is a Windows 10 PC running NextPVR 4.0.4.
My first attempt was at 07:17:54 which failed. My second attempt at 07:18:20 succeeded.
The NRecording log shows numerous lease renewal failures until the successful connection occurred.
Is this lease renewal issue a source of the problem I'm experiencing?
Is there anything I can do to eliminate this problem?
I'm hopefully attaching the appropriate logs I saved for you to examine including the Kodi log.
I've been fiddling with the latest 4.0.4 release (including the latest release with the latest ts reader patch), and I was having an audio sync issue where skipping ahead would get out of sync (see below for details). However, after some fiddling, I decided to make sure I had the very latest LAV decoders installed (0.70.2), selected LAV for everything (rather than my usual CyberLink video decoders), and now it's behaving itself (if there is a slight sync issue after a skip, it quickly corrects itself). So, for me, I'm giving this new LAV setup a try and hope that things will behave themselves.
Now, let's jump back in time just a bit to when I was trying to get 4.0.4 working with a CyberLink video decoder (MPEG2) along with an older LAV (0.68.1) AC3 Audio decoder: The issue was really simple. On some recordings all I had to do was to skip ahead a bit and the audio would be just slightly off from the video. I could fix the issue with a (10-sec) skip backwards, or by using the Legacy TS checkbox (which made forward skips work fine). However, here's the weird part: I noticed that if I copied the misbehaving ts file from the recording directory into a directory for NPVR to play via the "Videos" menu, the show would play just fine -- skipping ahead had no issues (I also verified that going back to the Recordings version continued to have issues after the Videos version worked OK). Does the Video area have different playback decoders from the Recordings area?
