So that message box might become concealed.
#AAX TO MP3 ANDROID WINDOWS#
But this does not always work, if windows are rearranged. And it also centered on it, using the Win32 API. It has the AAX Audio Converter main window as its owner, so, z-order-wise, it should be on top of it. Could it be the final message box, with the result of the conversion? This is a modal window.
That's new to me and has not been reported before. My version of AAX has the annoying bug of refusing to shut down when no longer in use. As written in the opening post above, version 1.12 addressed MP3 "Chapter" mode and made it much faster. Depending on mode, AAX Audible Converter applies different strategies which may affect the outcome. I guess inAudible has at least just as many. What mode(s) did you compare? AAX Audio Converter has 4 conversion modes and 2 output formats, 8 variations in total. However AAX is still a bit slower than inAudible - i have done side by side tests and inAudible always finishes first. As far as I understand the history, the author of inAudible is also the one who added AAX decryption to FFmpeg. User guide (also included in the setup package): AaxAudioConverter.pdf
#AAX TO MP3 ANDROID DOWNLOAD#
So, I now downgrade to ID3v2.3 when running on such a system and Win 7 is happy.ĭirect download of the setup package: AAX Audio Converter always used ID3v2.4 but Win 7 cannot read some fields then. This is usually ID3v2 but there are different versions. Reason here turned out to be the MP3 meta data encoding. And we still have millions of Win 7 systems in the world. In conjunction with this I noticed that the optional “Length” column in Windows Explorer showed the MP3 duration on a Win 10 system but not on a Win7 system.
VLC accepts it and other tools like MediaInfo also report the correct duration.
So, without it, media players estimated the duration from the bit rate of the audio stream, more or less successfully. It appears that MP3 meta data does not have an explicit field for duration that is recognized by all media players. It was brought up again by a user here on reddit and that finally made me analyze the matter.
#AAX TO MP3 ANDROID MANUAL#
I have added a new “Performance” chapter to the manual with a few more details and a table of conversion times for all modes for one particular book. It always depends on many factors, of course, in particular on the chapter structure of the book, but the conversion tests I made with 1.12 were 2 to 3 times faster than before. The program now separates decryption and transcoding very similarly to what it does in “Split chapter” mode. In 1.12 I have modified the internal workflow.FFmpeg, which does the real work here, had more or less to repeat the same stuff for each chapter as if it were the whole book, but actually only needed to convert a single chapter. While (unsplit) “Chapter” mode also uses parallel processing since version 1.3, this has not been very efficient. For MP3, “Split chapter” mode has been the fastest until now.Performance boost for MP3 output and “Chapter” mode: What’s new in version 1.12? No new features this time, but some changes “under the hood”.