#228(FFserver:new): FFserver: reordering of "<Stream>"s in config file makes difference
#228: FFserver: reordering of "<Stream>"s in config file makes difference ------------------------+---------------------------------------- Reporter: burek | Owner: baptiste Type: defect | Status: new Priority: important | Component: FFserver Version: git | Keywords: ordering items config file Blocked By: | Blocking: Reproduced: 0 | Analyzed: 0 ------------------------+---------------------------------------- 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? :) -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/228> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#228: FFserver: reordering of "<Stream>"s in config file makes difference ---------------------------------------+----------------------- Reporter: burek | Owner: baptiste Type: defect | Status: new Priority: important | Component: FFserver Version: git | Resolution: Keywords: ordering items config file | Blocked By: Blocking: | Reproduced: 0 Analyzed: 0 | ---------------------------------------+----------------------- Comment (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. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/228#comment:1> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#228: FFserver: reordering of "<Stream>"s in config file makes difference -----------------------------------+------------------------------------ Reporter: burek | Owner: baptiste Type: defect | Status: new Priority: important | Component: FFserver Version: git | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+------------------------------------ Changes (by cehoyos): * keywords: ordering items config file => Comment: Is this reproducible with current git head? If yes, please add the necessary command lines together with complete, uncut console output. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/228#comment:2> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#228: FFserver: reordering of "<Stream>"s in config file makes difference -----------------------------------+------------------------------------ Reporter: burek | Owner: baptiste Type: defect | Status: new Priority: important | Component: FFserver Version: git | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+------------------------------------ Comment (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.. -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/228#comment:3> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#228: FFserver: reordering of "<Stream>"s in config file makes difference -----------------------------------+------------------------------------ Reporter: burek | Owner: baptiste Type: defect | Status: new Priority: important | Component: FFserver Version: git | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 0 | -----------------------------------+------------------------------------ Comment (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... -- Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/228#comment:4> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
The first config file (ffserver1.conf) made ffserver drop rtsp connections, with error message "'''[NULL @ 0x1be7ba0]AAC with no global
#228: FFserver: reordering of "<Stream>"s in config file makes difference -----------------------------------+------------------------------------ Reporter: burek | Owner: baptiste Type: defect | Status: open Priority: important | Component: FFserver Version: git | Resolution: Keywords: | Blocked By: Blocking: | Reproduced by developer: 0 Analyzed by developer: 1 | -----------------------------------+------------------------------------ Changes (by saste): * analyzed: 0 => 1 * status: new => open Comment: Replying to [ticket:228 burek]: 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. -- Ticket URL: <https://trac.ffmpeg.org/ticket/228#comment:5> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
#228: FFserver: reordering of "<Stream>"s in config file makes difference -------------------------------------+------------------------------------- Reporter: burek | Owner: baptiste Type: defect | Status: closed Priority: important | Component: FFserver Version: git | Resolution: Keywords: | needs_more_info Blocking: | Blocked By: Analyzed by developer: 1 | Reproduced by developer: 0 -------------------------------------+------------------------------------- Changes (by saste): * status: open => closed * resolution: => needs_more_info Comment: Please reopen the ticket if you are able to reproduce the issue with a recent ffserver version. -- Ticket URL: <https://trac.ffmpeg.org/ticket/228#comment:6> FFmpeg <http://ffmpeg.org> FFmpeg issue tracker
participants (1)
-
FFmpeg