Ticket #228 (new defect)
FFserver: reordering of "<Stream>"s in config file makes difference
| Reported by: | burek | Owned by: | baptiste |
|---|---|---|---|
| Priority: | important | Component: | FFserver |
| Version: | git | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
The first config file (ffserver1.conf) made ffserver drop rtsp connections, with error message "[NULL @ 0x1be7ba0]AAC with no global headers is currently not supported."
After just a simple reordering of <Stream> items (ffserver2.conf), everything started to work properly?
Is this expected behavior? :)
Attachments
-
ffserver1.conf
(1.1 KB) -
added by burek 2 years ago.
-
ffserver2.conf
(1.1 KB) -
added by burek 2 years ago.
Change History
comment:1 Changed 2 years ago by burek
More precisely, didn't everything start to work properly; rtp stream gets to the player (vlc) i.e. ffserver does not stop with the previous message for AAC and global headers, but only few of the first frames (2-3) are displayed and the rest is Lost (according to VLC's Tools - Codec information / Statistics) and audio plays fine.
Anyway, the exact bug report would applies to the fact that the error message is not shown anymore, if <Stream>s' order is switched.
comment:2 Changed 6 months ago by cehoyos
- Keywords ordering items config file removed
Is this reproducible with current git head?
If yes, please add the necessary command lines together with complete, uncut console output.
