I have uploaded a new version of x-newa to the repo to address a few issues
- Error logging certain characters in web client causing video player issues in all versions
- Updated web client skins for Classic and Confluence skins. Caused black screen in v18
- Minor error in text colour for status in native details popup in all versions
- Fixed Busy notification after v18 dialog change
If you have automatic updates enabled you should get it today.
This version should work on v17 and v18, not sure about earlier version.
If you don't use Confluence or Estuary skins for Kodi you will need to select Classic.
Hello,
I am a new user of NextPVR. I set up the software and it seems to be working well. The only issue I have is that the modern web interface does not ask for a password. I am looking to password protect the web gui. I changed the web password in the setting but the issue remains. I apologize if this has been answered. I googled for 30 minutes and was unable to find the answer. Advice appreciated.
I have a problem with scheduled recordings where the channel EPG changes and the show is no longer planned -- but the recording still is done taking up a tuner/time/space on the drive. Is there any logic to double-check that a scheduled recording is still in the EPG table?
From Scheduled_Recordings:
"1104" "1104" "Jorinde und Joringel" "" "0" "2019-02-01 13:00:00" "2019-02-01 14:00:00" "23" "7373" "0" "rbb Berlin HD" "<Event>
<OID>895658</OID>
<Title>Jorinde und Joringel</Title>
<SubTitle></SubTitle>
<Description>Jorinde und Joringel träumen von einer gemeinsamen Zukunft. Doch da Joringel nur als Knecht am Hof von Jorindes Vater arbeitet, hält der ihn für einen Taugenichts und Tunichtgut. Er will etwas Besseres für seine Tochter. Als er ihnen die Hochzeit verbietet, fliehen die Liebenden. Der einzig sichere Weg vor den suchenden Eltern führt durch den Zauberwald.</Description>
<ChannelOID>7373</ChannelOID>
<StartTime>2019-02-01T13:00:00.0000000Z</StartTime>
<EndTime>2019-02-01T14:00:00.0000000Z</EndTime>
<FirstRun>false</FirstRun>
<OriginalAirDate>2011-01-01T00:00:00.0000000</OriginalAirDate>
<Quality>HDTV</Quality>
<Genres>
<Genre>Movie</Genre>
<Genre>Adventure</Genre>
<Genre>Children</Genre>
</Genres>
<MD5>MV006127620000</MD5>
<UniqueID>MV006127620000</UniqueID>
</Event>
" "" "30" "30" "3"
From EPG_Event
"1251840" "1251840" "Kesslers Expedition" "Unterwegs auf der Schiene: Vom Bodensee über Köln bis nach Amsterdam" "Diesmal geht die Reise vom Bodensee über Köln bis nach Amsterdam. In Konstanz bieten sich dem flüchtigen Kessler neue Karrieremöglichkeiten. Eine Laienspielgruppe stellt ihm eine Rolle in einem Stück in Aussicht, wenn er es durch das Casting schafft." "2019-02-01 13:00:00" "2019-02-01 13:45:00" "7373" "EP015689890052" "" "2013-06-14 00:00:00" "7" "3" "0" "65535" "Travel;Documentary" "N" "HDTV" "" "stereo" "" "Host:Michael Kessler" "" "YxGxYpTJ+aeIHzQh50gzuA" ""
Hmm -- the event numbers in scheduled -- some are not on the EPG list anymore -- like they were stuck from some corrupted DB data. Is there a *safe* way to delete the EPG and planned recordings, and restart the process without losing all of my lineups?
Hi
I have a Winfast DTV Capture Card running with Windows 10. For months now, I have had what appear to be either Signal Issues or Decoder Issues. Every now an again, I manage to get NEXTPVR running smoothly. It may be OK for a couple of weeks, but then, the prime culprit a "Windows Update " kicks in an kills my signal.
I have tried everything from Decoders, Decoders, and more Decoders. I have tried EPG updates, Channel Updates, I had a TECHO guy around and he checked out my signal and the end result was that everything seemed to be fine. In last couple of weeks, I have had nothing but signal issues again and I have run out of things to try to fix the problem.
My question is ...................... Would it be the TV Capture Card? That is the only thing that I have not been able to try and have avoided going and spending heaps of dollars in case it does not fix the issue. Do different TV cards have better signal receiving capabilities than others. I really enjoy NEXTPVR, when it is going OK, but lately it has been doing my head in trying to get it to receive the signals without the interference. I have tried LAV, Microsoft DTV-DVD, and ffdshow, Video and Audio Decoders, both as Video Decoders and Audio Decoders, as I have no idea which one is the problem.
If any one can shed any advice on this it would be greatly appreciated.
Many Thanks
mvallevand Wrote:Comskip is not implemented in curl http on Kodi however in v18 the addon is configured to use http over their new inputstream streaming which does support comskip in my testing.
Martin
Just watched an hour long program tonight using Kodi 18 rc 5 with the XNEWA add on, unfortunately comskip didn't really skip, not like the PCH at least. Hmmm. Tried the native nextpvr Android app but no comskip. Will try to supply logs.
Hi all. I'm looking for help for a fairly persistent looping issue I have when recording IPTV streams through NPVR. Basically, my IPTV provider streams are very consistent (and rarely loop) when watching LiveTV. However, when the same service is used to record those streams, I consistently experience a looping (repeating) of content throughout the recording. When it loops, it will return back 10-15 seconds and then play through the problem area. I followed the information contained in the thread here: https://forums.nextpvr.com/showthread.ph...only/page5 and provided logs and sample recording. I am using the latest NPVRShared.dll here https://forums.nextpvr.com/showthread.ph...post529004
Some of my specs:
- Intel NUC i5 w/ 500GB SATA3 SSD, 16GB RAM
- 50 GB/s Internet - With 3 simultaneous recordings and 1 LiveTV stream, I max out at less than 20 GB/s
- Motorola Surfboard modem support DOCSIS 3.0
Attached are the log files. At the time where the looping occurred, the FillBuffer was taking too long to refresh and the socket then disconnected and reconnected. Couple other anecdotes: Occasionally, when this recording repeats, I will notice that the leading number will grow to a number very large (e.g 17 hours) out of a 30 minute show - this didn't happen during the bad recording I'm referencing here. I have a sampling of the video uploaded here: https://www.mediafire.com/file/h7i9719ll...nk.ts/file.
Thanks guys. Great product. Looking to help make it even better.
Hi all,
I have a series of MP4 files and when I try and play them NPVR hangs and I have to kill it with task manager. I am aware that NPVR only handles TS files directly so I thought the files might be corrupt - but they play fine in VLC and WMP.
Logs attached, no dump file in C:\temp.
Any thoughts greatly appreciated.
Thanks.
Stanno
My HDHomeRun Prime suffered an untimely death and had to be replaced. I just got the replacement setup, and all appears to work just fine. NPVR see's the new device and scans the channels, however, when I try to watch live TV from NPVR I get "Unable to find available capture device".
I don't see anything obvious. Any thoughts? I attached the logs.
In previous versions, in config.xml, section "Recording", the "ManualRecordingDays" parameter allowed to set the number of days for recurring recording to appear in the Pending Recording section. I think the original value was 10 and for my purpose, I set it to 16. So I could see 2 weeks of recurring recordings (as I program manually my recordings for 2 weeks, it allows me to be warned of conflicts).
I upgraded to 4.2.3 (181112).
Everything is working fine except that I see only 10 days of recurring recordings, but the "ManualRecordingDays" parameter is still set to 16.
I did restard the npvr recording service many times, I did reboot the computer many times, still the same.
What did I miss ?
Thanks,
I know this looks like an Emby forum issue, but I was directed here because Luke told me it was an NPVR server error causing the problem.
I do not have any issues playing NPVR live streams anywhere else. The issue only happens on my Roku 2XSs through the Emby LiveTV NPVR Plugin. It will load and play content for 10 seconds, then stop to load and gets stuck at 80%.