So I've been googling this as well as asked for support over on the emby forums where I was informed this might be a better venue for seeking support.
I'm not a super advanced user, but I know enough to be dangerous, so hopefully I can detail enough here to get my question properly across.
Context:
I have Emby running on a terramaster NAS that is underpowered in CPU and unable to handle any transcoding. I'm running NPVR on a somewhat decent older windows PC that has a hauppage USB TV Tuner.
When connecting directly to NPVR through the web ui on any of my other devices it works beautifully and the NPVR host machine is able to transcode the video feed just fine per my transcode settings in the settings menu.
When I attempt to connect Emby to NPVR either directly through the NPVR plugin on emby, or by pointing to the M3U playlist, Emby receives the live stream in whatever native format it was broadcast in. From there if I connect a client device to Emby, it will only work if said client can ALSO handle that same native feed and all of the bandwidth required for it. If not the Emby server steps in and attempts to transcode, which results in either a crash or very broken up video as it stops to buffer frequently.
My question is this:
Is there a way to force NPVR to always transcode the feed to something more universally friendly like a lower bandwidth H.264 so that Emby is less likely to need to intervene?
In my searching for a solution I've found the config.xml file, and inside that I've found "<TranscodeHLS>" which seem promising, but I've been unable to find any documentation on what the options are for this value?
I would definitely appreciate any advice anyone can offer.
Hello,
Merry Belated Christmas to all.
My mother has had this occur several times where she is watching a program then exits the channel to go back to the program guide. When trying to open a channel again she gets the unable to connect error. I have had to go and reboot the server to allow the client to talk to the server.
Logs provided.
I installed a new drive in my server, mounted it in the usual manner, then put NextPVR in the group that owned the drive. Linux naturally made root the owner of the mount point. This should have worked just fine. I should have been able to make recording folders on that drive. But I couldn't. Then I temporarily made NextPVR owner of the mount point, set up the folders, then returned mount point ownership to root. Everything works fine now. Why did I have to do this?
The SD website says Jason data is available for up to 20 days. So I set my config file to pull 20 days. But the EPG is limited to 14, and I have some channels where that is filled up. Is there something in the config file to expand the EPG to say 3 weeks so it can display all the data possibly available from SD?
I just installed UIDroid on my Firestick HD Max and it plays great. However, the remote FF and RW do not work. I see the channel up and down does a 1 minute skip forward or back. Can these times be changed?
I would like to set the skip back to 15 seconds.
I have jellyfin and nextpvr in dockers. both working independently fine. I installed the plugin for jelly fine, pointed it properly and all seems swell. When i go to live tv, i have a channel listing in the guide, but no information i.e. epg. Also, the recordings tab is blank. I have hit refresh guide data in the dashboard already. Im stumped.
thanks for any info that could help
I have written a NextPVR UI client for Samsung Tizen TV's and monitors and if anyone is interested in testing it let me know or post other comments below. I am looking at getting a bit of feedback and if it works as well for others as it does for me, I will see about getting it published to the Samsung App store.
I did target a version of the API that is meant for TV's from 2020 and above. I could try targeting older versions if necessary. Generally the performance of the integrated media player is better every year.
I know with ATSC I should be able record all sub=channels on a frequency with a single tuner. But when I tried using all tuners to record, then attempted to watch another sub-channel of one I was recording I got a not tuner available error. ????? I have 1 HDquad USB tuner and 1 HD Homerun extend (2 tuners).
I have NextPvr running in a docker container on my nas. It works flawlessly. However when i install the kodi add on and try to configure it, Kodi pops up a message saying server found and auto inputs the Docker containers ip address which isnt real as far as the local network is concerned. When i manually change it to the dhcp address of my nas, a message says "need to restart" but when i go to do that, kodi auto finds the original docker ip and replaces the info i entered and it happens over and over. Not sure how to rectify.
When I click on the listing for the tv series "Washington Week on PBS, then select "Record Series", nothing happens. Same thing if I select "Advanced" and select any option. But if I select "record Once" it schedules the recording. If I search for "Washington Week from the search page the same thing happens. I look through the entire guide and the series is never set to record. The series WAS set to record, but I deleted it and attempted to redo the record after I noticed some episodes were missing. It's almost like NextPVR still thinks the series is set to record and is keeping me from double selecting. I experianced this on the same channel before. Some series are scheduled in multiple slots and NextPVR won't let me record the same episodes twice, unless I select the all episodes option, OR IF I SELECT SINGLE EPISODE RECORDING Could something have gone haywire when canceled the recordings, so that NextPVR still thinks canceled recordings are scheduled? I tried rebooting and that didn't help.
UPDATE: I might have figured it out. The exact same thing happens if I try to record a show that is not a series (a sappy Christmas show.)Could there be an error in the listings where each episode is listed as single show, with season and episode numbers simply text in the description? If so, would this be an error at SD, or with the data the station is sending? If anyone want's to recreate the issue on their own server, I'm getting 70194 OTA listings from SD.
