I hope this is the correct place for this question. I'm still learning but can anyone tell me how to use Titan TV listings with NextPVR? My current source is giving me problems and the Titan listings are more complete. I checked the forums and came up empty. Thanks!
I upgraded to the latest and greatest last week end and ever since then if I connect via NEWA and do an "episode search", choose a previous search, click "submit", then select one or more and click "Record selected" I get an error page back - titled "Server Error in '/' Application." but contains no useful information (I suspect that it's from FFox and not NEWA).
Issue: Only on "certain" channels, during LiveTV, NPVR hangs. Majority of channels do not have this problem.
Environment: NPVR in client/server mode. Wired gigabit Ethernet, 3 tuner HDHR Prime. Fiber Optic cable delivered to premise. High quality signal measured by HDHR on subject channel during the issue. All DRM channels have been removed in settings:HDHR devices - only non-DRM channels are available. Have tried multiple A/V decoders, including MS & those is SAF. Clients include Win7, Win8.1 & Win10. Server on W7, quad-core cpu.
Symptoms:
1. Whether watching subject channel Live on client, recording the subject channel or watching subject channel Live on server, NPVR hangs, requiring a channel change away, then back to restore the signal.
2. HDHR VIEW will not hang on subject channel, but sometimes the video will pause for a few seconds then will resume back to normal without user intervention, but audio is not interrupted while there is a pause in the video. That said, I have not yet established a correlation between the HDHR VIEW video pause and the NPVR hang.
3. VLC - no issues or hang ups of any sorts on subject channel during LiveTV, while at same time NPVR is hanging.
Conclusions:
Something NPVR is doing or not doing when compared to HDHR VIEW and VLC that is causing LiveTV hangs.
Questions:
What could be causing this? (logs attached)
Does NPVR use a timeout for a lost/corrupt signal before it stops play on LiveTV? If so, can this timeout be changed by the user and how would one go about doing it?
I have been having a problem with my PC ever since we moved house and I ended up having to move from a Hauppage terrestrial receiver card to a DVB Sattelite card (TBS6289 Dual)
I have tried full re-installs and lots of different settings but now I am slowly losing the argument with the damn thing...
Problem 1- Film4 seems to not work at all. I discovered that when viewing the channel in KODI it would hang after about 2 minutes and then render the software inoperable. After trying to watch the same channel in NPVR, I am greeted with a black screen and no sound and NPVR not responding. After a forced quit, it would hang on start-up. I played with the codecs, and am using the LAV decoders so after a play about and a full restart of the machine. It's all back up and running but still with no film 4.
Problem 2 - I've recreated the above problem a few times and each time I have to do a restart of the machine, I then find that the guide has huge chunks of info missing across all channels and I end up having to do a EPOG Update.
I have attached the logs (i hope) to see if anyone can point me in the right direction.
I'm having challenges with NextPVR when recording NCIS: New Orleans. NCIS and NCIS: Los Angeles work fine.
When I look at the TV Guide in Next PVR (I use zap2xml to create the EPG data) I can see both NCIS and NCIS New Orleans in the guide and are marked to record.
When I look at Recordings under Reoccurring Recordings I see NCIS, NCIS: New Orleans and NCIS Los Angeles
When I look at Recordings under Pending Recordings NCIS and NCIS: Los Angeles both show fine, but NCIS New Orleans appears as just NCIS. I figured I need to address this before I can look at any issues with imageGrabLite. If NPVR does not see the show name correctly in Pending Recordings it is likely passing the wrong info to imageGrabLite.
It is very odd that the guide and reoccurring recordings shows it correctly and pending records does not. The file being saved is named NCIS instead of NCIS New Orleans even before imageGrabLite is run.
Here is a sample of the EPG data for the next NCIS New Orleans from my xmltv.xml file used by NextPVR.
<programme start="20160322200000 -0500" stop="20160322210000 -0500" channel="I11299.labs.zap2it.com">
<title lang="en">NCIS: New Orleans</title>
<sub-title lang="en">Means to an End</sub-title>
<desc lang="en">Agent Pride's daughter is attacked.</desc>
<date>20160322</date>
<episode-num system="dd_progid">EP01922310.0042</episode-num>
<new />
<subtitles type="teletext" />
</programme>
message appears saying "recording sheduled" When watching a channel and pushing the record button in kodi... Pushing the record button again relays a message saying "recording started"
in order to stop the recording, i have to push the record button a further two times.
This however is not always the case... Sometimes if i click the record button kodi will start recording straight away returning the message "recording started" after just one click, which is how it should work.
using 3.6.6 NPVR and latest openelec nightlies for RPi2
I've been using Tvheadend as a backend in kodi since day one and have only just moved over to NPVR, so i'm really unsure if the NPVR plugin has always acted this way.
however instant recording works as it should when using the TVheadend addon so it appears to be related to the NPVR addon
Wondering if there has been a change in kodi api... If the addon needs updating or perhaps NPVR itself needs updating to handle these requests differently.
I had setup NPVR to record while I was away, and set all the programs to record and all that, and then, I noticed I didn't have much room left on the recording drive.
So, went to the shop and got a new HD, and hot swapped it and did a format & assigned it the same drive letter as before.
Well, seems NPVR didn't like this, since it instead recorded all the shows to the SSD instead of the recording directory I told it while I was away.
Sure enough, when I got back, looked at the HD, and saw nothing new, puzzled, looked in event viewer and saw drive out of space errors, so I look at the SSD, and found some of the recordings, then I look at the NPVR settings and my old drive setting was there, however, there was a default above that set to the SSD drive.
Ack!
So, yeah, ran out of space on the SSD.
Now, since explorer and all other programs could access the new HD, why did NPVR instead chose to add the default drive recording location again, instead of using the preferred device I had specified?
In the logs, I just see
day before
Code:
[DEBUG][9] DefaultDirectoryChoice: first
[DEBUG][9] allocating recording target filename: J:\tvtvtvtv\...
after...
Code:
[DEBUG][9] DefaultDirectoryChoice: first
[DEBUG][9] allocating recording target filename: C:\Users\Public\Videos\...
Nothing in the logs about the change back to the SSD (c:\) drive, it just started using it.