Closed choxnox closed 2 years ago
Thank you for the issue. @choxnox
I've moved it to the backlog to schedule it. I think we can schedule it in next week or the week after.
Thank you
Hi @mekya, any updates on this issue?
Hi @choxnox ,
It's still in the backlog and scheduled for the next week. I hope we can schedule on Monday. Sometimes due to workload and unfinished tasks, we cannot schedule enough issues. Sorry for that.
Hi all,
The issue is resolved in 2.4.1 version, please reach back to us if you face the issue again.
Thanks
There is another feedback that is not directly related to this issue. Anyway I'm creating an issue for this.
The Antmedia server does support AAC.
We believe we have identified the problem.
The ant-media server is susceptible to inbound streams that do not contain the AAC header in the FLV container. While the elementary stream contains the header the FLV container does not. This causes the antmedia server to have a problem.
One of the sending systems was modified to use ffmpeg with the aac_seq_header_detect flag, and the antmedia server works correctly. See:
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2015-November/183483.html
It would still be good if the antmedia server would accept streams without this header (since we have at least two systems that send RTMP streams without this header).
Short description
We're testing the possibility of restreaming an existing external HLS stream to RTMP. It's supported by FFMPEG but we're not sure if it's supported by media server.
However, trying to do so crashes the server.
Environment
Steps to reproduce
Expected behavior
Ant media server to not crash
Actual behavior
Ant media server crashed and restarted every time we start the playlist broadcast
Logs