[FFmpeg-trac] #11351(undetermined:new): Native AAC-enocoder doesn't create constant bitrate.

[FFmpeg]

#11351: Native AAC-enocoder doesn't create constant bitrate.
-------------------------------------+-------------------------------------
             Reporter:  maxmanus     |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:  native aac   |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by maxmanus):

 Replying to [comment:4 maxmanus]:
 > Ok, but when I write just -b it does show as constant bitrate in
 mediainfo.
 > If -b:a 320k it shows as variable. I want it to show as constant. No way
 to fix this?
 > I'm using qaac now because of this, but seems buggy when muxing together
 after with ffmpeg.
 >
 > Replying to [comment:3 Balling]:
 > > Neither of those produce true constant bitrate, you need
 -bit_rate_tolerance 0 option. b92af7b64e7acd015aea3ae1da2228c5a7e677bf
 > >
 > > >Output is then variable bitrate.
 > >
 > > it does decrease bitrate if the sound does not need needed amount of
 data, but bit_rate_tolerance 0  has bugs
 https://patchwork.ffmpeg.org/project/ffmpeg/patch/517a57ef18398a39952fcc1d02e51ef423cf80ae.1726262133.git.pav@iki.fi/



 Is there any difference though? Quality and support wise on TVs and other
 platforms?
 I started messing with this because I used to convert to 384k before, and
 noticed sound dropping out on my samsung tv under playback. Might av been
 because of too high bitrate. Haven't reproduced this issue after chaning
 to 320k.

 Is it true that the native encoder at 320k variable is same quality as
 with qaac 320k constant?
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11351#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker