...
Note that ffmpeg sends orientattion value but not angle itself.
Decoding buffer size management
When RTMP stream is published from software encoder supportin hardware acceleration on NVIDIA GPU, and contains B-frames, the stream picture can twitch in some RTMP or HLS players. To workaround this, since build 5.2.863 the parameter was added to set the maximum decoding buffer size passed in SPS
Code Block | ||
---|---|---|
| ||
h264_sps_max_dec_frame_buffering=-1 |
By default, buffer size is not limited. This eliminates picture twitching, but can inscrease latency due to excessive buffering. In this case, the buffer size can be limited to 2 frames (default value before build 5.2.863)
Code Block | ||
---|---|---|
| ||
h264_sps_max_dec_frame_buffering=2 |
or more frames to eliminate twitching without viewable latency.
Known issues
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
...
Solution: set Opus encoding bitrate as published one, foe for example
Code Block | ||
---|---|---|
| ||
opus.encoder.bitrate=160000 |
if RTMP stream is published with audio bitrate 160 kbps
9. High CPU load when stream H264+speex is published (for example, using Flash client) with audio transcoding
Symptoms: high CPU load while audio transcoding from speex to AAC or Opus
Solution: use native speex decoder implementation
Code Block | ||
---|---|---|
| ||
use_speex_java_impl=false |
10. Stream with unsupported codecs cannot be published
Symptoms: RTMP stream with MP3 or AC3 audio is not publishing with the following warnings in server log
Code Block | ||
---|---|---|
| ||
11:01:00,921 WARN ServerHandler - RTMP-pool-15-thread-1 Codecs not supported! audio: NoCodec, video: NoCodec |
Solution: reencode stream to supported codecs using corresponding encoder settings