How can I debug a DVB radio channel that keeps getting cut off? Playback lasts about 7 minutes, and then the browser just stops receiving data. Other radio channels are ok. It happens in both web apps but not in kodi. This is where I reckon the log becomes different:
[160] reached end of rolling file. Dropping connection...(2) (available=752 of=1316)
[160] StopStream @cleanup
[160] StopStream(1638407)...
[160] clientHandle[b05cd258-396f-43b2-ad66-b6021a6e1cc7] = 1638407
[160] Calling StopStream()
[160] http://localhost:8866/stream/stop?handle=7
[5] Got GET request: /stream/stop?handle
[5] Getting ready to stop stream
[5] stopping stream
[5] stream stopped
[5] activeHandleTargets count = 0
[5] No more active streams. Stopping device.
[5] Graph stopping...
I'm trying to put this into text that is understandable but having a hard time explaining
Ok, so I have the same iptv provider, but I have two separate accounts with them (one for the parents and 1 for me) these include two different xc logins
I want to run the NextPVR client from my PC only, at my home and have my kodi at my home pull from my xc login device from the backend client running on my PC
And I want my parents household Kodi to pull streams from my PC under their device from my PC
Is this possible ?
How would Kodi know which device to pull from in the next PVR client on my PC when I run it in my home compared to running it in their home?
Martin,
I've seen this before, when I choose Exit (Enter), nothing happens. Alt + F4 does work.
I pressed the Exit menu several times at the bottom of the log.
Art
Hello,
I am experiencing recurring Live TV playback interruptions when using the NextPVR PVR client in Kodi.
My setup:
NextPVR Server: 7.1.1.260616
NextPVR running in Docker on a Synology NAS
Kodi 21 with pvr.nextpvr 21.3.2.1
IPTV channels configured in NextPVR
Kodi and NextPVR are connected over the local network
The problem:
Live TV playback works normally for approximately 30–60 minutes, then suddenly stops and Kodi returns to the channel guide.
The issue occurs with different IPTV sources, not just one channel. Playback through the NextPVR web player appears stable.
Tests already performed:
I tested different NextPVR Live TV buffer settings:
I also tested the Kodi NextPVR client's Real Time and Timeshift playback methods.
For the latest test:
Live TV method: Timeshift
Direct Streams: Disabled
NextPVR Live TV buffer: 120 minutes
Kodi
Code:
advancedsettings.xml
:
Code:
curllowspeedtime=60
Unfortunately, the problem still occurs.
Relevant log messages:
Kodi reports:
Code:
CVideoPlayerAudio::Process - stream stalled
followed by:
Code:
Reconnect, (re)try 1
and:
Code:
Failed: Requested range was not delivered by the server (33)
The NextPVR logs show messages including:
Code:
stream@2 got zero bytes
client disconnected
Live stream expired without 15 second renewal.
After the stream disconnects, Kodi attempts to reconnect using an HTTP byte-range request, but playback cannot recover.
My questions:
Is this a known issue with the Kodi NextPVR client or NextPVR's Live TV streaming?
Could the HTTP range/reconnect behavior be responsible for the playback stopping?
Is there a recommended fix or workaround?
I have attached sanitized Kodi and NextPVR logs from the latest playback failure. Sensitive URLs, credentials, network addresses and identifiers have been redacted.
Any help would be greatly appreciated.
Thank you!
I've seen some posts from a few years back noting multirec not being supported on hdhr devices in Linux pointing towards silicon dust API limitations. I was wondering if this is still unsupported in nextpvr?
Being the curious type, I went looking for silicondusts API documentation to see what they make available. I noticed their API documentation was updated in the last few months. The section about tuning to frequency instead of vchannel drew my attention. Am I looking at the appropriate API documentation NextPVR utilizes for hdhr devices? And am I interpreting this piece of the article correctly? https://info.hdhomerun.com/info/http_api...f_vchannel
In my custom-made client, I can select a recording in progress and issue a "cancel recording" command which basically changes the DB status of that recording to "2".
However, the show continues to record. What other steps do I need to do to get the recording to actually stop?
Scheduled Recurring recordings tend to accumulate endlessly and can use some periodic house keeping. But as currently listed, that is difficult. It would be nice to have some control over the sort order. For my purposes, listing them alphabetically would be helpful because I could at least see duplicates that may be redundant or obsolete. But it would sometimes also be handy to sort by "Recording type". That would, for instance, group all of the "New Episode" scheduled recordings together and I can delete any I recognized as cancelled shows that won't ever have a "new" episode again.
My STB/Hauppauge HDPVR/NextPVR setup ran smooth as a cat's fur until this weekend when the MLB Division Series began. Throughout the baseball regular season, it worked so reliably that when it came time for the playoffs there was no thought of verifying the new recordings.
But when I looked this morning out of curiosity, I discovered that the weekend's playoff games had not recorded. The error message given in Web NPVR goes as follows:
[Failed: No errors, but no data delivered. This is usually because the device failed to lock a signal."]
When I try to tune a channel, the NPVR GUI displays either "please wait" (usually) or "Unable to find capture device" (once or twice).
Curiously, with the TV set to the TV's HDMI input for the STB, when I change channels via NPVR the new channel is displayed on the TV itself, but not on the laptop screen, where the NPVR GUI shows one of the above messages.
Hoping for a simple solution, I've taken the following steps:
Closing and relaunching NPVR.
Power-cycling the PC.
Power-cycling the HDPVR 2 1512.
Power-cycling the STB to which the HDPVR is connected.
None of this has helped.
Something seems to have happened somewhere along the device chain between October 1 (the date of the last successful recording) and October 3 (when the ALDS and NLDS started). I'm attaching the log file, in the hope that they will help someone knowledgeable about these things to pinpoint the cause of the problem.
Thank you in advance for any insights or suggestions.
TV show set to record at 6:30. Turn on TV, click on in-process recording and nothing. Stop recording. Go to Guide, click on channel and watch Live.
Still using exact same signal, watching show via NextPVR.
What is it that prevents the recording that allows the live viewing of a perfectly clear broadcast with no glitches?
Yes, I know the answer is that NextPVR is pulling data from the HD HomeRun, but it starts the session, and would run the 30 minutes and then display that it couldn't lock signal or similar. Yet, it could, because I watched it live via NextPVR...
