I have created an account with schedules direct, but the guide is stuck with the following status EPG Update complete. [0 inserted, 0 updated, 0 skipped]
I found your app via a recommendation from someone on the Plex forums.
I followed the install instructions :-)
Is there a manual? I have guessed at Admin/admin for username and password but have no clue how to proceed from here. I cannot find a readable file in the NPVR directory (like a config file) to set the username and password.
...sorry of this really is a dumb question and I have missed the big sing saying "instructions here".
NPVR is waking computer for epg update at 02:44 and appears to complete. Computer then stays awake for the rest of the night. (Should be sleeping after 30 mins)
On opening Kodi, going to TV Guide and starting first Channel in the list Live TV fails to start. Requires a Control C and restart of NPVR to get Live TV working - I have also had it freeze completely requiring a Reboot to get it working.
For the rest of the day, Kodi starts Live TV every time.
This has happened almost every day since installing v5 (the last 2 versions)
Still only testing v5, using v4 for primetime - it's more the complexity of Kodi for the prime user than problems with NPVR.
In the attached logs NRecord shows 2 attempts for live TV (wasn't sure the button had pressed the first time) after line 27912 along with exceptions being thrown.
This latest build (5.0.0.190629) does not seem to work as well for streaming live TV for me. The logs should show the TV stream starting and freezing a couple times. I'm running Docker for win 10 pro.
I believe that there is still something wrong with tuner use and pre/post-padding.
The log.2 shows at 19:59 on 6/30:
- Tuner 21 was assigned to record "Burden of Truth."
- Tuner 22 was assigned to record "Good Witch."
at 20:59:
- Tuner 32 was assigned to record "Big Little Lies."
At this point, recording "City on a Hill" should start recording and could have been assigned to tuner 23 but it wasn't. Instead, NextPVR waited until the recording on tuner 21 entered its post-padding interval causing the loss of post-padding on "Burden of Truth and the pre-padding on "City on a Hill."
I know you've explained that any padding is expendable. But I'd like to know why it is not better to honor any padding when a perfectly good tuner is available for use. Wouldn't it be better to test for an available tuner before cutting off any padding?
I'm not sure if this is a knewc problem or a V5 server problem... I put the kodi debug log in with the other logs. If you look at the end of them, you'll see that I watched an episode of Rescue 911 (Boomer's Rescue; 911 It's a Boy). Then I pressed the Blue button to set the blue dot. The display shows a blue dot. Everything looks good. Then I exit knewc and go back to the Kodi menu. And immediately go back into knewc. Go back to the Recordings list and find that Rescue 911. But now, instead of a blue dot, it's showing a red dot! Initial testing indicates that the green, yellow, and red dots work ok. Only the blue dot gets converted to a red dot when going back into knewc.
There is something "strange" going on with the scheduler in the latest version.
See the Nrecord.log.3 file for last night's EPG update. Every recording is being marked as "Conflict Alternative Airing" except for Rescue 911s -- in that case, I'm getting 2 pending recordings for each episode--one normal and one marked "Conflict Alternative Airing".
I've got 5 tuners configured. The 4 on the HDHR Quatro with OTA channels and 1 of the HDHR Prime CableCard tuners. I have NOT merged the Quatro channels with the Prime channels. All of the recordings for OTA channels were scheduled from the Quatro channels (the 4.1, 11.3, etc. ones) and the cable only recordings (Chrisley Knows Best on USAHD) were scheduled from the Prime channels (825, etc.).
All of the recurring recordings are for Season, New, This Channel Only except for Rescue 911 which is for Any Channel.
I have a number of recordings that failed because the computer was not on when it was time for them to be recorded. If I try to delete them, I get an "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. No connection could be made because the target machine actively refused it 127.0.0.1:8968."
The files are still listed under recordings after seeing this.