夏楚

其实 我甚至怀疑，是否有必要在hls拉流中添加平滑输出的逻辑。因为没这个逻辑照样能工作正常，也不会存在onShutdown后，部分残余数据没有输出的问题。其实在转协议时，zlm也没必要确保拉hls转协议后能平滑输出其他流，流平滑播放的责任是播放器的，流媒体服务器没必要确保数据输出的平滑度。

这个代码注释很详细，api接口也很简单，可以拆分成一个个独立的小单元，demo也健全，基本可以不用单独的文档了。

这个已经支持 通过配置文件enable_hls_fmp4开启

```json { "aliveSecond": 82, "app": "live", "bytesSpeed": 328895, "code": 0, "createStamp": 1675606096, "isRecordingHLS": true, "isRecordingMP4": false, "originSock": { "identifier": "3-30", "local_ip": "192.168.31.106", "local_port": 8000, "peer_ip": "192.168.31.106", "peer_port": 61081 }, "originType":...

How about this: ```json { "code" : 0, "data" : [ { "aliveSecond" : 39, "app" : "live", "bytesSpeed" : 319331, "createStamp" : 1676878619, "isRecordingHLS" : true, "isRecordingMP4" : false,...

I think the best way to raise demand is to submit a pull request。 Many times, some requirements are only business related and not universal. If I don't use them,...

> 业务开发 zlm有时候做其它非流 现在文件都是放内存的 几MB还行

Currently, this feature is not supported. In what scenarios does this feature need to be implemented? For multi-tenant virtual host?

> Thank you very much for answer! > Scenario is Let's Encrypt certificate + very undesirable to stop or interrupt incoming streaming's process. What protocol are you using with zlmediakit?...

NET_DVR_SetESRealPlayCallBack回调 可能就不是H264 你先保存264文件 看看能否播放