Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

H.265 Issues while streaming to other server #24

Open
husudosu opened this issue Dec 4, 2017 · 1 comment
Open

H.265 Issues while streaming to other server #24

husudosu opened this issue Dec 4, 2017 · 1 comment

Comments

@husudosu
Copy link

husudosu commented Dec 4, 2017

I've two servers:

  • First server doing the encoding process have a NVIDIA Quadro P2000 GPU (NVIDIA HEVC Encoding) 28 IPTV channels with around ~5MBIT/source MPEG2-MPEG4 streams. The output bandwidth of one channel between 1MBIT/1.5MBIT using VBR.
  • Second server going to be something like a CDN server where only the NGINX and MPEG-TS plugin runs.
    I'd like to stream instantly to the second server which is doing only the HLS processing. But when I do that there's some issues. Stdout of MPV media player on my local machine:

[ffmpeg] NULL: PPS id out of range: 0
[ffmpeg/video] hevc: PPS id out of range: 0
[ffmpeg/video] hevc: Error parsing NAL unit #2.

It seems there's no issues with the FFMPEG encoding process on the first server. I didn't see any issues on NGINX error log either. Nginx configuration based on your example. The only difference is I've set the worker process count to 4.
When I play the stream from STB the first frame appears and there's audio and after 2-3 seconds the stream is going to be absolutely fine.

When I'm doing both encoding and segmenting on the first server and HLS again on the second server it works perfectly.
I'm not sure if it's possible to do that correctly.

@AleXoundOS
Copy link

[ffmpeg] NULL: PPS id out of range: 0
[ffmpeg/video] hevc: PPS id out of range: 0

This may be related to #42 if the second servers starts reading HLS fragments skipping the first. Maybe try @wellttllew's workaround/fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants