Great Job on this,
I installed it on Linux Mint Tessa and works perfectly. I added a few auto start scripts and
the system runs excellent I have one question I am using the nextPvr Client the old one for Kodi
My question is when is timeshifting coming to that? I just swapped from myth tv to this to give this a try
I like it very much it is fast and responsive. One other question I am using schedules direct and when
i go to download the icons it doesn't work is it because its not finding them or do i have to download
my local ones myself either way i am happy with it and it seems to run really good on the 64 bit edition
I have a total of 9 silicon dust tuners prime editions with cable cards. My set up is a main tv server and then i
have several windows and linux clients that the server is feeding. Just want to put in my 2 cents. Keep
up the great work

Tony

Hi,

I've been scratching around trying to find an answer to this, but with no luck. Basically I have got a capture card to play a device connected to it with VLC by using the following dshow commands:

vlc dshow:// :dshow-vdev="Video (00 Pro Capture HDMI 4K+)" :dshow-adev="Audio (00 Pro Capture HDMI 4K+)" :dshow-aspect-ratio=16\:9 :dshow-chroma=RV32 :dshow-vcodec=libx265 :dshow-fps=60 :dshow-acodec=mp4a :dshow-ab=96 :dshow-channels=2 :dshow-samplerate=48000 :no-dshow-config :no-dshow-tuner :live-caching=100 --sout-keep

...using either dshow or ffmpeg, can I do the same with NPVR? I know you can with TVHeadEnd, but I'm finding Ubuntu in a virtual machine so unreliable, I'd rather do it all via NPVR if possible.

Thanks

i think the current state of Sat>ip is not bad but there should somethings implemented too

in the Rtsp stack is the session timeout ignored
the Session Timeout param can you get from the RTSP Setup Response
and this timeout param need you for an Keepalive thread who send an RTSP Options to the server so knows the Server that there is an client is listen
without this thread means the server there is no one that listen and close the connection

RTCP is very use full to look for connection infos

RTCP APP hold informations for the tuned frequency wich tuner/ frontend , how strong the Signal (Level Quality) values are and is signal present locked
sure RTSP Describe Response hold this infomation too but not all server support ways some use RTCP others use RTSP

RTCP Bye send by the server and the client should than stop all Threads RTP RTCP RTSP
Servers send this RTCP Bye packets if they should reboot

Hi, I had a good look around the beta area but couldn't find anything that helped me with this. I have a RPI3 running raspbian with a couple of ancient Twinhan DVB-T usb tuners connected. The devices appear under /dev/dvb and work find with tvheadend but nextpvr doesn't seem to detect them at all. I did see a post where someone added --device=/dev/dvb to the command line for NextPVRServer but that hasn't helped.

Logs attached, any assitance appreciated

Small gripe in the latest version in the Devices screen. Can it be changed back to white letters on black like the other screens in Settings?

Hi everyone, just to say I’ve noticed I can’t skip fwd or back on my iPad. Works fine on my iPhone 8 but the 5th gen iPad just ignores the swipe completely?

I’ve seen another three similar thread but thought it was better for a clean new thread as that had a few topics.

Anyone else seeing this?

I installed v5 beta for x64 Linux and all appeared to go well but when I try to use web access I'm prompted for a username and password. I only have one user setup and these credentials don't work, is there a default username / password or do I have to edit a file to access NextPVR?

I noticed that when using the web app with MS Edge browser to watch a video stream, the full screen button is not working. The button works in Chrome.

Hi all -

I have setup a NextPVR backend (4.2.4) that I want to point into a Kodi frontend (v18.3). Ultimately, I will use Kodi on several Nvidia Shield boxes around the house, but for simplicity sake, I am going to first start by configuring Kodi on the same windows 10 PC that is running NextPVR.

NextPVR is working great on my PC. I am able to watch live TV, record, and the guide is working very well.

I added the NextPVR addon in Kodi, and configured it accordingly (192.168.1.95:8866) - and yes I can access this via a browser. While playing around in NextPVR, I recorded a couple of shows and to my surprise - they showed up in Kodi with artwork and everything!

I am struggling to get my channels/EPG up and running here. I have attached my NextPVR logs.

Any help is very much appreciated! I feel like I'm really close here.

Thanks in advance!

Over the last 6 Months or so there have been various NPVR users in the UK with epg update problems, which either caused crashing during EPG update or large amounts of "No Show Details" throughout the logs.
Recently after re-allocating 2 of 6 tuners to v5 testing it returned with a vengeance.
After investigation, I discovered that there was only one frequency left in the advanced EPG setup screen (Misc 2) which would not populate again with re-scanning the devises.
The only way I found was to bulk map all channels to none, followed by going in to each channel details and resetting epg source to DVB/ATSC (there is a bug or feature, where doing this in bulk mapping is not saved).

It looks as though every time there is a frequency change for a mux,(there have been 4 in the last year and a bit, here on Mendip) a rescan updates the frequency for the channels, but not the source for the epg in Channels - NPVR can probably cope with one frequency missing due to the all channels being broadcast on every mux, but as the number of frequencies changed increases there will be more holes in the guide, due to the time required for a full cycle of all channels on one mux being around 12 minutes.

There was also a problem - may still be - with spurious illegal Characters.