after fixing everything i had on errors in NPVR, i have found something strange, and i hope you can perhaps help.
Me and a friend have both similar behavior, i have DVB-C he has DVB-S.
On some channels there is EPG data for about 14 days. The data is loaded without problems, but:
- For shows that in far future, only basic information is provided
- If the show is then in near future, more EPG data is added
- This change is not updated, the data stays basic.
If i delete all EPG data, and let is grab new, the extended EPG is available, but without that -> no chance.
It would be very very nice, if this could be "fixed".
I guess that, that in the background the data is not updated, because EPG data is already in the database. But the data changes over the time.....
I hope i could explain it in a way, that you understand, what i mean, my english is not perfekt... :-)
title says it all... is there a way i can have nextpvr use different (smb share) folders for recording TV shows and Movies, using the metadata it got when grabbing the artwork or similar?
i want to set Kodi to import recordings to its library, but i cant set content to be both movies and TV in the same source in Kodi. i tried setting two separate sources to the same folder in kodi, one using host and set as TV and one using IP set as Movies, but it does not work well with some movies scanning as TV shows and vice verse when i update library.
i read the wiki about secondary paths and archive option or manually selecting path when initiating a recording, that would work, but i am hoping to automate having two locations it so it just 'happens'. anything more than just hitting record is too much to ask of my young kids (and wife!)
Hello, been using NextPVR5 installed on my PC, and mainly use Kodi as frontend on Windows PC, and NVidia Shields.
Have both Digital DVB-T tuners in PC, and also Hauppauge Colossus.
The colossus card is feed from HDMI source from my STB, and uses HaupBlast.exe to IR blast channel changes.
This has been working really well.
However, something weird has just started happening when switching STB channels using the Colossus card.
What is happening, is that when switching to an STB channel, I am presented with an error requestor that states:
'Playback Failed' 'One or more items failed to play' 'Check the log for more information about this message'
If I then close that requestor, and select switch again, the channel usually plays just fine.
(although on the odd time the same error will appear)
So, basically, when changing channels from the STB, I need to switch channel choice 2 or more times before it is successful.
I tried the NextPVR desktop app, and it behaves similar, and requires me to switch more than once before the channel finally works.
NextPVR desktop app brings up the following error message when 'watch channel' is selected from an STB source:
'The request was aborted' and something about a timeout.
Am running the latest release version of NextPVR5, and also the latest release version of Kodi Matrix.
Yes, I still haven't transitioned to v5... if it ain't broke, don't fix it... especially for those who are less technically inclined, shall we say...
Here's my "if it ain't broke" dilemma: my IPTV provider is eliminating m3u and moving to XC logins exclusively. I don't see how that would work with NextPVR, and searching on this forum for "XC" doesn't work, obviously, as the two-character string isn't accepted.
I also tried searching "xtream", but the results seem to relate to Xtream Editor rather than an XC login.
I've also checked the Wiki, which appears to cover v5 only (understandably!) and didn't see anything related to XC.
Am I SOL or is this just a less-obvious feature in v5?
powercfg /requests shows "Legacy kernel driver" is the culprit. At the time this shows, there is no recording in progress in NextPVR, or any EPG update, or any client connected (I only use the local client).
If I stop the NextPVR service using NET STOP "NextPVR Service", there is no longer anything showing up in powercfg /requests afterwards, and the machine is able to go to sleep on its own according to the OS power plan.
Once I restart the NextPVR service manually, the output of powercfg /requests is also clear and all is fine.
I have concluded that the NextPVR service is somehow holding the OS from going to sleep automatically.
If I put the machine to sleep manually, it wakes up at the next recording, and then stays awake indefinitely. Any scheduled recording in NextPVR appears to trigger the problem.
Is there any way to diagnose the issue further and get it fixed ?
I wasn't having this problem in NextPVR 4.x, so this is a regression for me. I'm thinking of downgrading back to NextPVR4 since this bug is costing me money in wasted power every day.
I have nextpvr for windows 10 installed on an hp ml30 gen 10 with 2 colossus 2 cards, a quadro p2200 gpu and a pcie intel nic. I also have channels dvr setup as an m3u source. The colossus 2 cards share the same lineup but have different blaster commands. One is for a verizon stb the other a tivo. Both cards use hdmi video and audio. Whenever I change the priority of a colossus 2 tuner and it switches places with another colossus 2 tuner, the blaster commands copy automatically from one card to another thus leaving me with the same blaster configs on both cards when I initially set them up to be different. I am using an usbuirt with 2 different usbuirtsend binarys in 2 different folders but this bug still occurs. I am not sure if my explanation is the best so please ask if you have any questions. Thanks.
that is supposed to cause a prompt after the recording has finished playing that asks if you want to delete the recording. Since the setting is "true" I would expect the prompt to happen, but it doesn't it just returns to the previous menu.
Is this setting still valid for NextPVR.exe?
I watched a 30 min recording and waited until it finished, then captured logs.
I have had a couple of these Astrometa DVB-T2 sticks for many years, and they have a Panasonic demod chip in them (2013 version). They work fantastically. One is on my main HTPC and produces hours of error free recordings every day.
I recently got another one, looks the same on the outside but it's the 2018 version, it has a Sony demod chip in it ("Sony guts!"). Unfortunately it has issues working in most programmes - it appears as though it is getting a very weak signal, lots of errors in it.
I had thought I'd just got a bad device, but I read online that I should try the bundled TV utility "TVRPlayer" and sure enough, that works and I can receive programmes loud and clear. The signal strength it reports is consistent for what I would expect on my various multiplexes.
So, there must be some weird non-standard quirk of the driver. It was cheap, and I had largely written it off until I saw this thread - https://forums.nextpvr.com/showthread.php?tid=58540 - Another NextPVR user appears to have this same "sony guts" version of the tuner and it's working okay with NextPVR.
I did read somewhere that there may be an issue in the driver that it does not by default turn on the pre-amplifier on the board. That makes sense to me, as the issue does look like weak signal. I've no idea how to fix though.
Does anyone else have one of these? Could you perhaps share with me what version of the Windows drivers you are using? Did anyone else have this issue?
