We are using the latest version of Wowza Streaming Engine (4.4.1)ĭoes the H.265 ffmpeg encoded streams need any concrete profile or parameter to ease the later encapsulation at Wowza? We have also tried to use an encoding template, with no real encoding, as it uses the “Pass-through” encoding option. We want Wowza to just reencapsulate our H.265 content and distribute by HLS. But this is not our objective, as we want the encoding to take place in a previous stage. We are able to access H.265 streams by HLS when using the H.265 Wowza Transcoder from an original H.264 stream. When using RTSP, a very low bandwidth output stream is stablished, far from the expected bitrate, and there’s no signal at VLC. We h- ve tried both 1sec and 10sec segments. When using HLS, a new connection is briefly opend, but there’s no output bandwidth consumed. This is the ffmpeg command we use to send one test stream: ffmpeg -i 'udp://X.X.X.X:XXX' -filter_complex 'yadif=0:-1:0,scale=1280:720' -c:v libx265 -vb 1050000 -maxrate 1050000 -bufsize 1050000 -tune zerolatency -preset veryfast -r 25 -x265-params 'keyint=25:no-scenecut' -acodec libfdk_aac -ab 96000 -strict experimental -f rtsp -muxdelay 0.1 we are failing to access these streams on Wowza using VideoLAN, neither by HLS nor RTSP:

We are capable of generating such H.265 streams from ffmpeg, sending them to Wowza over RTSP, and they correctly appear as incoming streams with the desired bitrate. As our target players are now capable of decoding HEVC/H.265 streams, we intend now to migrate to this codec. These streams are created by an ffmpeg process at a separate host, encoding in H.264 and AAC. We’ve been using Wowza Streaming Engine for a while to broadcast keyframe-aligned streams using HLS adaptive streaming.

Ffmpeg hevc to h264