NextPVR doesn't allow recording of non-standard iptv streams that ffmeg can't transcode. You could record them as extras if you don't care about browser playback but it is not trivial.
I'm not sure I understand that. I don't care about playback through a browser. I watch recordings through Kodi on a Firestick. What I care about most is recordings being captured reliably, instead of finding zero byte .ts files. I only tried to play the streams in a browser to check if they were actually working, and that's when I found I couldn't play the live streams either. What do you mean by recording "as extras"?
I believe I already explained it. It is sub's decision that NextPVR IPTV input must be h264/aac for browser compatibility. With many users now wanting to use a browser player (which I don't understand for recordings either) this makes sense but for me it is extra overhead.
Still your stream is particularly bad and you should be complaining to your provider.
2020-12-27, 10:52 PM (This post was last modified: 2020-12-27, 10:53 PM by Graham.)
(2020-12-27, 10:28 PM)NND Wrote: I'm not sure I understand that. I don't care about playback through a browser. I watch recordings through Kodi on a Firestick. What I care about most is recordings being captured reliably, instead of finding zero byte .ts files. I only tried to play the streams in a browser to check if they were actually working, and that's when I found I couldn't play the live streams either. What do you mean by recording "as extras"?
It appears that this is a ffmpeg issue and not a NextPVR issue.
NextPVR transcodes using ffmpeg when you use the browser for live tv or recordings. If you only use NextPVR.exe or Kodi then ffmpeg is not used and the playback is acceptable.
So, if I schedule recordings through the NextVR.exe Windows client, they should be OK - right? I guess I just need to use the Browser client for anything to do with Settings, but then use the Windows client for scheduling recordings. A quick test just now did seem to confirm that works.
The client has nothing to do with it. I am surprised to hear that recordings are failing though. Did you have post an example of a recording that fails on start?
(2020-12-27, 10:47 PM)mvallevand Wrote: It is sub's decision that NextPVR IPTV input must be h264/aac for browser compatibility.
That is not correct. It doesn't have to be h264/aac, but in a default install it does assume IPTV is h264/aac. (but will take note if a channel is not, and force a full transcode next time the channel is viewed)
Try unticking 'Avoid transcoding where possible (for better performance)' on the Settings->Transcoder screen.
(2020-12-27, 11:38 PM)sub Wrote: That is not correct. It doesn't have to be h264/aac, but in a default install it does assume IPTV is h264/aac. (but will take note if a channel is not, and force a full transcode next time the channel is viewed)
Try unticking 'Avoid transcoding where possible (for better performance)' on the Settings->Transcoder screen.
Sorry I misunderstood this. I thought all IPTV ts streams that are not h264/aac were sent to ffmpeg instead of direct download to file.
I checked your logs for recent recordings and you have a url or provider issue so your problem is not just with transcoding.
2020-12-25 11:39:27.910 [DEBUG][207] Unexpected error in HTTP input source: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
2020-12-25 14:17:01.003 [DEBUG][32] Unexpected error in HTTP input source: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
2020-12-25 18:28:47.972 [DEBUG][139] Unexpected error in HTTP input source: System.Net.WebException: The remote server returned an error: (401) Unauthorized.
If fact there was only one recent good one in the last couple of days.
2020-12-26 13:59:01.541 [DEBUG][9] StartStream [I:\TV Programs\Sky News at Ten\Sky News at Ten_20201226_14001430.ts] allocated handle: 32