[FFmpeg-trac] #1457(avcodec:new): Add support for libshine-fxp fixed point math MP3 encoder

FFmpeg trac at avcodec.org
Sun Oct 28 17:47:20 CET 2012


#1457: Add support for libshine-fxp fixed point math MP3 encoder
-------------------------------------+-----------------------------------
             Reporter:  patters      |                    Owner:
                 Type:  enhancement  |                   Status:  new
             Priority:  wish         |                Component:  avcodec
              Version:  git-master   |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by patters):

 I was able to finally devote some time to this and I realised that I
 didn't need that multithreaded perl in the end. I ran the libshine
 bootstrap on a Ubuntu VM and then I realised that once created, the
 configure script could be transported and run on any destination CPU
 architecture. However, I ended up cross compiling - my method here:
 http://pcloadletter.co.uk/2012/10/12/ffmpeg-shared-libs-for-synology/

 FFmpeg with libshine seems to work nicely for music encoding. I did once
 spot a crash while transcoding a video file with an error relating to
 having run out of temporary buffer space, but I didn't make a note of the
 exact error. I also noticed the issue richardpl reported above - that
 libmp3lame will crash when support for both lame and shine libraries is
 compiled in. Is it normal that they would be mutually exclusive? I notice
 that when only libshine is compiled in and when no encoder is specified
 but output format mp3 is declared, libshine is automatically used, so
 maybe that's why.

 I did notice that libshine seems to produce garbage audio when the input
 source is a surround stream (observed this with AC3 and DTS), but other
 than that it seems fine.

 Is libshine support likely to get officially included into FFmpeg?

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


More information about the FFmpeg-trac mailing list