From RTSP H.265 to RTMP, you first need to extend the RTMP protocol. At present, our country has corresponding promotion standards, and domestic developers basically promote in accordance with this agreement. Issues at the protocol level have been resolved. The key remaining issue is implementing the RTMP H.265 push module.
rtmp h265 server supports it. Currently, the commonly used nginx-rtmp and srs do not support rtmp h265 and need to be modified. After communicating with multiple SRS users, some people have already done some simple support. The key point is to add h265 type support.
For nginx rtmp, since the nginx rtmp module has less code, it is very convenient to support 265. It is also possible to add the 265 type, parse the HEVCDecoderConfigurationRecord, and process the corresponding module.
To support rtmp h265 playback, you must first parse 265 from rtmp, and you need to parse out h265 nal unit and HEVCDecoderConfigurationRecord. 265 has more vps than 264 and needs to be parsed. In addition, nal type needs to be processed for h.265. After parsing out nal units. The next key point is decoding. Currently, some Android phones already support h265 hard decoding, or you can also use soft decoding.
rtmp h265 push support, if you already have h265 nal unit, use vps, sps, pps to construct HEVCDecoderConfigurationRecord, and package the rtmp package according to the extended protocol.
How to convert rtsp h265 to rtmp in the live video on demand station? This article also gives you a brief introduction. Our liveweb video streaming server can also be implemented at present. Interested friends can consult us.