Hi. I'm struggling to get reliable streaming of recorded programmes to my desktop browser using the new modern interface.
I can stream a Live TV channel from my NPVR server to the Edge browser on my Windows 10 PC however if I try to stream a previously recorded programme, I get one of two things....

If I select a programme from the recently recorded section and click on Watch....nothing seems to happen.
If a select a recording from the All recordings screen and click watch, I get a black window with buffering at the bottom ....which proceeds to 100% and then I get the rotating circle in the middle of the screen....and that's it...no sound or picture.

Checking the Web log file I see an error saying the file doesn't exist.... but it does and can be played on the NPVR server using NPVR.

I've attached the log file.

Any help appreciated.

I'm running NextPVR on a dedicated fairly low end nettop box (Acer AspireRevo AR1600) under Windows XP. Works great. I have 2 HD-PVRs and do Live TV through Kodi on Android tablets and Fire TV devices. I recently purchased the iOS application and once I had installed an XP compatible version of ffmpeg can get Live TV to start but not run. By start I mean an HD-PVR fires up, the CPU on the server gets pegged at 100%, the HD-PVR stops (the log says - Live stream expired without 15 second renewal.) and eventually the short TV clip plays on my iPhone.

Pretty sure it is the transcoding that's killing me here. Hence my question as to why it's necessary? Streaming live TV to Kodi on the Android boxes works great without transcoding. The HD-PVR produces an h.264 stream right?

Mike

Hi!
I think that Close should be in place of Watch.

Now that i've discovered new 3.9.2, i'm pointing out some bugs.
1) Scanning fails sometimes, with certain transponders, both on dvb-t and dvb-s.
Sometimes changing slightly the frequency works with dvb-s: for example on 13E Hotbird transponder 11727 V 27500 fails (quite immediately, it seems it doesn't even try to scan): but if i put 11726 in the frequency it scans and finds channels. The right frequency is 11727 and all other dvb software finds channels on that frequency. The same happens also with certain other transponders now i can't remember of (3-4 of 100).
The same happens on dvb-t: frequency 642000 doesn't find channels at all, neither changing it slightly (+-125 or 500). That frequency has channels and all other software finds them. BTW it could be a good thing to implement manual scan also on dvb-t.
2) It could be implemented a better way of handling channels,too. It was a while i wasn't using NPVR and had an old scan (both dvb-t and dvb-s).
Well, it took me a whole afternoon only to renew the channels list i've already had, changing order with new found channels. The most time consuming part is the number assignment to the channel.
a) What about a drag and drop of channel and then an automatic numbering based on the "visual" order?
b) In the bulk map what about give to the enter (return) key ability to pass to the next channel number edit?
There are only examples of little things that are very useful to the user that needs a certain channel order
Thank you,
sdf

I was playing a little bit with the new /channels playlist.
It works perfectly with vlc and kodi (iptv pvr plugin), but not with smart tvs (lg and samsung).
The difference between smarttv and vlc and kodi is that smart tvs send a burst of requests of channel, and nextpvr answer immediately to all that requests (there are 2-3 .ts files per channel).
It should be that nextpvr, after receives a channel change request, filters the fake requests from smart tv and elaborates only one channel change, and then send the buffer back to the smart tv (ony 1 .ts, as happens with vlc and kodi). This problems exists also with other software, and has been faced with filtering "fake" requests coming from smart tvs, verifying their user-agents, and/or sending immediately a 200 ok and the mime type, thus avoiding them to make further requests.
Sub, what do you think about it?
Thank you,
sdf

My wife was trying to schedule a recording and it crashed NPVR. Windows threw an exception and I see this in the log: "Unexpected error looking up metadata: System.InvalidCastException: Unable to cast object of type 'Newtonsoft.Json.Linq.JObject' to type 'Newtonsoft.Json.Linq.JArray'.
at NShared.SchedulesDirectJSONEPGSource.LookupMetadata(MetadataEntity entity)" at 20:03.

Any ideas what it's looking for?

Logs attached.

Thanks!

Hi all, first time poster,

Both my parents are blind and relied heavily on WMC for controlling their TV, Music and Videos, unfortunately windows BTFO'd WMC and killed Zune so I've installed Kodi as a stop gap with VoxCommando. This isn't great and although you can control aspects with your voice the narration of content is non existent, so I've whipped up my own windows app that allows full voice control and narration of both the Plex service and the Groove Music service. I've just come to sort the TV side out and have got the EPG and channel narration and navigation down using the Next APIs but I'm having issues displaying the actual channel, I've hit the API and got the URL for the channel and this displays fine in an external player like VLC but when I pass that to the inbuilt MediaElement in windows it states it's not a supported format (works fine with Plex's TS format).

Has anyone had any experience in getting this to work???

If this is a non fixable issue I've noticed there is a transcode API, is there any documentation on this to start a transcoding stream and retrieve the URL for display?

I prefer to use Rest APIs than any SDKs.

Any and all help is appreciated.

I am trying to pick up some reruns to complete a series that I am archiving. The show airs twice/day. I have most of the episodes in my media library, but they were mostly not recorded by NPVR and, regardless, have been processed and moved. Not to mention the several times I've "rebooted" my NPVR installation...

What I'd like to do is get NPVR to record only the episodes that I'm missing (I had been doing this manually). Is there a way to import or add records to the NPVR database of the episodes I have so that selecting "Avoid Duplicate Recordings" will only schedule those I am missing?

TIA - Bob

In my config NextPVR (client part) never worked: didn't work with codecs different from ffdshow and microsoft, changing channel often (quite always) hanging, have to admit was quite discouraged, and was several months didn't use NextPVR too much.
Then tried new 3.9.2, mostly to test new NLite client.
Was quite astonished to find that (nearly) all the problems had before are completely gone (with exactly the same pc and configuration)! NextPVR client now works quite flawlessly, can use LAV filters both with Mpeg2 and h264, channel change is fast. Only minor flaws (sometimes screen is blank in fullscreen), but NextPVR (both Backend and Frontend) is rock solid.
Also the new possibility to expose /channels and /recordings playlists opens nextpvr to smarttvs world.
A suggestion: what about exposing also a /guide.xml, so that (iptv) clients can use it?
I have 2 smarttv, an LG and a Samsung.
LG works perfectly, with channel change rock solid and fast.
Samsung has some problems: sometimes channel change hangs, some channels (4fun.tv, which are sd but h264 and ac3) are not visible, i think because of the codecs used, don't know if it's related to buffering or http request headers, or something like that. Have to say that the same samsung smarttv works perfectly with other tv servers.
Tried also with Kodi iptv client (both windows and android) and /channels playlist works perfectly; also vlc is lightning fast.
Anyway, thank you for the really really big improvement.
With some small adjustments NPvr will soon become the perfect HTPC server software.
There's no need to say that i'm ready to test anything.
Thank you,
sdf

I've updated the nlite build at http://www.nextpvr.com/nlite-win32.zip.

- moved from RGB to YUV to reduce CPU usage.
- added experimental "-gpu" command line parameter for using dxva2 hardware acceleration during playback.

Any feedback much appreciated.