Conversion aborts on a very large file.

[github-monkey]

I have a massive file of about 8GB, downloaded with Book Lib, with a playtime over 260 hours and about 950 chapters. While other files I downloaded at the same time all converted without issues (into chapters) this large file aborts after about a minute. I downloaded the file again with Book Lib, in case there were abnormalities in the download, but it didn't solve the issue.

It could still be an issue with Book Lib, even though it completes successfully, but I don't know how to narrow down the problem either way.

How should I proceed?

[audiamus]

I guess that even this large book is not offered as a multi-part download?

Does the decryption work in BookLibConnect? Is the .m4b result playable?

In AaxAudioConverter there is a memory limitation with FFmpeg. By default, AaxAudioConverter uses an older 32bit version of FFmpeg, because it is faster. But this can only allocate a limited amount of memory. However, the program should detect the size of the book and then switch to the newer 64 bit version of FFmpeg automatically. This would theoretically allow to allocate unlimited memory, provided the hardware is equipped sufficiently. (I cannot tell you why FFmpeg uses so much cache. I would believe it could execute in stream mode, at least with .m4b and the the AAC codec.) You could also try the latest FFmpeg build, and point AaxAudioConverter to it. The is setting for this, Basic Settings | General.

[github-monkey]

My apologies for the late reply.

Yes, the 7.9 GB MB4 and AAX files play in VLC without any issues. The PC has 32 GB of memory, I assume that should be enough. It has never had issues before with AAXAC and it had no issues with the other AAX files that I converted in the same batch. Only this file aborted.

Given your suggestions, I downloaded ffmpeg64 7.1.1 and pointed AAXAC to it. This time ffmpeg chewed on step 1 out of 953 for almost exactly one hour -- at about 30 - 35 % CPU and 800 - 2500 MB -- and then AAXAC split the file into its 954 chapters in about 3 minutes. At 7.9 GB perhaps that's understandable.

If there is any diagnostic data you would like, to examine the issue, let me know. Thanks for pointing me in the right direction.