[FFmpeg-trac] #527(avcodec:new): NellyMoser codec reports zero frame size and bitrate

[FFmpeg]

#527: NellyMoser codec reports zero frame size and bitrate
-------------------------------------+-------------------------------------
             Reporter:  DrLex        |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avcodec
              Version:  unspecified  |               Resolution:
             Keywords:  nellymoser   |               Blocked By:
  codec                              |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by DrLex):

 The test is pretty simple in theory, an example of a command that triggers
 the problem can be found above. The biggest problem however is getting an
 FLV stream that uses the NellyMoser codec. In an attempt to give you
 something ready-to-use, I have just wasted an hour trying in vain to
 create such a stream with ffmpeg and ffserver. I believe it would be much
 simpler and more reliable to use Wowza Media Server with a free developer
 license. It should be pretty simple to configure Wowza to redistribute
 audio streams. Or, use any other streaming server of your liking. Then,
 send the stream to the server with something like:

 ffmpeg -f alsa -i hw:0,0 -acodec nellymoser -ar 22050 -ac 1 -f flv
 'rtmp://127.0.0.1:1935/your_stream_name_here'

 And then you can run
 ffmpeg -i "rtmp://127.0.0.1:1935/your_stream_name_here live=1" out.wav

 However, I have wasted enough time on this for the time being, especially
 considering that the solution is of no use anymore to me. So if anyone
 wants to do the small effort of documenting how to get a basic Wowza or
 other server demo setup working, the few people that are still required to
 work with the ASAO codec will be thankful.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/527#comment:12>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker