Opened 4 years ago
Last modified 3 years ago
#7615 open enhancement
Support converting *TO* AAX (Audible's proprietary format)
|Reported by:||C0rn3j||Owned by:|
|Blocking:||Reproduced by developer:||no|
|Analyzed by developer:||no|
Support was added at some point to convert from AAX to other formats. This works great.
However, ffmpeg does not appear to support converting TO this format.
Why is this needed? Some devices do not ship with a music player, and the only way to play audio is through Audible's app, which in turn does not seem to recognize any audio files besides their own proprietary ones. Example of this device would be Kindle Paperwhite 4 (10th gen), which let's you play audio through Bluetooth, but only through Audible.
Converting FROM AAX works great -
% ffmpeg -activation_bytes aabbccdd -i Anomaly_B074TZ7Q5Q.aax -vn -c:a copy output.mp4 ffmpeg version n4.1 Copyright (c) 2000-2018 the FFmpeg developers built with gcc 8.2.1 (GCC) 20180831
Converting TO AAX however -
% ffmpeg -activation_bytes aabbccdd -i output.mp4 -vn -c:a copy output.aax ... [NULL @ 0x562448a9bac0] Unable to find a suitable output format for 'output.aax' output.aax: Invalid argument
Change History (6)
comment:1 by , 4 years ago
|Status:||new → closed|
comment:2 by , 4 years ago
What do you mean no reason? I explained a valid use case in the OP.
comment:3 by , 4 years ago
|Component:||undetermined → avformat|
|Priority:||normal → wish|
|Version:||unspecified → git-master|
I believe this ticket has similarities with a valid enhancement request.
comment:4 by , 4 years ago
|Status:||closed → reopened|
comment:5 by , 4 years ago
This limitation affects me, too. I didn't find a non-disruptive button to signal that, so I'm posting a comment.
No reason to write DRM files.