#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:6 Balling]:
> Qaac is much superiour than two-loop in ffmpeg.
>
> That option if for headphones, bluetooth likes close to perfect constant
bitrate.
I'm not sure I understand.
At that bitrate, shouldn't the quality be the same? I've not heard any
difference with 320k with ffmpeg natice aac as variable and qaac with 320k
constant. Just thinking about support on devices. Strange ffmpeg makes it
variable for me, when I specify constant. I used fdk before, but such a
hassle to build ffmpeg every time.
Why is this still a problem though with ffmpeg. A good aac encoder
should'nt be a big deal in my eyes. I don't get it. I thought aac at these
bitrates should be the same.
Now when using qaac standalone together with ffmpeg the duration of the
audio and video always slightly different. Can't find sync problems, but I
read that if a delay is in the metadata it will get deleted with qaac.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11351#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
