Opened 8 years ago
Closed 6 years ago
#228 closed defect (needs_more_info)
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: | yes |
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 (2)
Change History (8)
Changed 8 years ago by burek
Changed 8 years ago by burek
comment:1 Changed 8 years ago by burek
comment:2 Changed 7 years 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.
comment:3 Changed 7 years ago by burek
This ticket was created 20 months ago.. Unfortunately, I don't have the same environment as I had back then, so I can't (easily) check what you ask :( Sorry about that..
comment:4 Changed 7 years ago by cehoyos
What about this ticket is environment-specific?
My problem is simply that I don't know what to do with the conf-files...
comment:5 in reply to: ↑ description Changed 6 years ago by saste
- Analyzed by developer set
- Status changed from new to open
Replying to burek:
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? :)
There is any way to test this issue again? Otherwise it should be probably closed.
Note also that your file contains a few mistakes, RTSPPort and RTSPBindAddress should be defined as global options (they are not per-stream).
Also provide the ffmpeg command used to generate the FFM stream, and the command used to play the stream, otherwise this is only wild guessing.
comment:6 Changed 6 years ago by saste
- Resolution set to needs_more_info
- Status changed from open to closed
Please reopen the ticket if you are able to reproduce the issue with a recent ffserver version.
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.