New submission from Ho Tuan <[email protected]>: There is a problem with the current ffmpeg implementation of RTMP publishing.
I'm having a reliability problem with publishing live, h.264 streams from FFMPEG (using the rtmp publish ability now built into FFMPEG, where I can set an rtmp address as the output). After a random period of time (usually between an hour and several hours), the default "live" application in FMS 4 (or 3.5) eventually drops the connection from the FFMPEG encoder. This is what appears in the log for the application: "Dropping application (live/_definst_) message. Clients not allowed to broadcast message." I posted this issue to the Adobe Flash Media Server list, and got the following response: "It seems a problem in FFMPEG implementation.. Baiscally they have put a wrong stream id in the rtmp message which shows its a broadcast message." You can see the original Adobe forum post here: http://forums.adobe.com/message/3141896#3141896 The relevant ffmpeg code seems to be in libavformat/rtmpproto.c. Any thoughts on how to fix this issue that is causing ffmpeg rtmp publishing to crash? ---------- messages: 11954 priority: normal status: new substatus: new title: RTMP streaming crashes after some time with Flash Media Server (FMS) type: bug ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2236> ________________________________________________
