2020-10-26, 02:48 AM
I had to look and I misread your post, it wasn't timeshift live tv it is an-progress recording so I will need that kodi debug log.
Martin
Martin
NextPVR Forums
Public
Kodi / XBMC
Reverse proxy - ssl - kodi client
Reverse proxy - ssl - kodi client
|
2020-10-26, 04:27 AM
(2020-10-26, 02:48 AM)mvallevand Wrote: I had to look and I misread your post, it wasn't timeshift live tv it is an-progress recording so I will need that kodi debug log. Ok, got the kodi debug log going. This is a log starting the finished recording and then hitting the right arrow button to jump ahead. Same results, player closed.
2020-10-26, 12:29 PM
Thanks that is much clearer and it seems more related to an issue being discussed on github https://github.com/kodi-pvr/pvr.nextpvr/issues/152 and not an https error at all. It could be all recordings not just in-progress.
Basically Kodi is determining your recording is not seekable. For a first test could you edit config.xml and change <UseCompression>true</UseCompression> to false? If that fails could you try another test but this time in Kodi enable libcurl and ffmpeg logging in Settings->System->Enable Component Logging. Martin
2020-10-27, 05:18 PM
(2020-10-26, 12:29 PM)mvallevand Wrote: Thanks that is much clearer and it seems more related to an issue being discussed on github https://github.com/kodi-pvr/pvr.nextpvr/issues/152 and not an https error at all. It could be all recordings not just in-progress.Hi Martin, I skimmed the github ticket mentioned in this post and read this was a linux only issue? I changed the backend in haproxy to point to my Windows 10 nextpvr server and saw the same issue where the player exited when advancing in time.
2020-10-27, 05:35 PM
Thanks for confirming. That would have been a linux NextPVR difference though which I don't see as being too likely. What I wanted the @wmarler to confirm on the issue was to try another linux Kodi client since he was using a self-compile on Arch
I do have my debug ready to try again when I can test your server again just in case I spot anything. I am worried that it might be a general Kestrel web server issue with seeking on recordings an it will become a bigger problem. Martin
2020-10-28, 04:47 PM
@VCR58 attached is an update with a fix I'd like you to test. Rename the pvr.nextpvr.dll in and copy in the attached.
C:\Users\rex\AppData\Roaming\Kodi\addons\pvr.nextpvr It using different logic for accessing recordings. Martin
2020-10-28, 05:11 PM
(2020-10-28, 04:47 PM)mvallevand Wrote: @VCR58 attached is an update with a fix I'd like you to test. Rename the pvr.nextpvr.dll in and copy in the attached. Hi Martin, This dll works great! I can jump ahead or back without fail.
2020-10-28, 05:26 PM
Thanks for confirming.
Martin
2021-05-26, 05:47 PM
(This post was last modified: 2021-05-31, 09:58 AM by randyisscott.)
Did you research on how to set up Nextpvr on a Linux server or you followed a youtube tutorial? Some years back, I built a multi-room DVR system, based on Nextpvr, which featured automatic antenna rotation, automatic deletion of old recordings (to make room for new ones), and commercial stripping from recorded programs. Each TV had a small noiseless set-top box that received commands from the remote and decoded the streaming video from the server. I was also receiving and recording over-the-air digital TV several years before the federal mandate. Unfortunately, my server broke, and my PCI tuner card would no longer work in a modern computer, so I have not gotten the thing working again, much to my wife's dismay.
2021-12-07, 08:46 PM
This thread just about addresses a solution to reverse proxy with the kodi pvr addon. What I need is for the addon to STOP inserting the port into the url. Example; currently it's working like this "https://test.net:8866/npvr/services...", what I need is "https://test.net/npvr/services...". How do I remove the port part of the equation?
|
|
|
