Bug 762 – FFmpeg: AAC Quality slider has no effect with libvo-aac encoder.

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 762 - FFmpeg: AAC Quality slider has no effect with libvo-aac encoder.


Summary:	FFmpeg: AAC Quality slider has no effect with libvo-aac encoder.

Status:	CLOSED DUPLICATE of bug 344

Product:	Audacity
Classification:	Unclassified
Component:	Formats
Version:	2.0.6
Hardware:	Per OS All

Importance:	P3 RepeatableAll
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Duplicates:	408 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-09-25 08:33 UTC by Gale Andrews
Modified:	2019-06-11 06:30 UTC (History)
CC List:	5 users (show)

See Also:
Steps To Reproduce:	1. Try using the AAC quality slider. It has no effect.
Release Note:	GROUP:Imports and Exports (FFmpeg) * M4A (AAC) exports: The Quality Slider in "Specify AAC Options" has no effect if the FFmpeg library is built with the libvo-aac encoder, as are recommended builds of FFmpeg for Windows and Mac OS X.
First Git SHA:
Group:	FFmpeg
Workaround:	You can specify a constant bit rate if you select "Custom FFmpeg Export". Click the Options... button, choose "mp4" in the formats list and "libvo_aacenc" in the codecs list, then set bit rate in bits per second. Up to 320000 bps (320 kbps) is supported. Given the alternative AAC encoders for FFmpeg also have problems as described in these notes, you can instead export as WAV and convert to AAC in iTunes on Windows and Mac.
Closed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gale Andrews 2014-09-25 08:33:13 UTC

Audacity bug with dynamic library export. Bitrate specification works OK with Audacity command-line export (or standalone FFmpeg) configured with libvo-aacenc. 

The slider also works with libfaac or the FFmpeg AAC encoder.

Comment 1 Gale Andrews 2014-09-27 00:32:33 UTC

*** Bug 408 has been marked as a duplicate of this bug. ***

Comment 2 Peter Sampson 2019-05-08 14:03:48 UTC

See also Bug #344

Comment 3 Peter Sampson 2019-06-11 06:30:21 UTC

*** This bug has been marked as a duplicate of bug 344 ***