Quote:
Originally Posted by ACGAuthor
All of that is true, and absolutely something I've considered. frankly it would be my preferred option, but I'm very concerned that the "audiobook specific stuff" is SO FAR outside the scope of what Calibre does (and has been very intentionally designed to do), that it really has no place in the Calibre project.
I mean, part of working with non-DRM encoded audiobooks is, for example, importing a batch of MP3 or M4A files, each one of which may be a chapter of a single book or just a chunk divided by an arbitrary size limit, then making sure those are sorted and metadata tagged so that they play in proper sequence, and then possibly converting them (whether by re-encoding or using pass-through file joining) to a single, chaptered M4B or MP3 file.
Since once of the things I saw when I first looked at Calibre as a possible option for handling my audiobook catalog is that it's meant to be "one file = one book" by design, the fact that some audiobooks come in multiple files(and many users require them to be that way, depending on their preferred method of listening) is right off the bat, outside the scope of what Calibre was designed to do.
My ideal program would also call up ffmpeg to re-encode, or possibly edit via pass-through, the metadata of audio files and maybe even "liberate" DRM-encrypted AAX files so that they can be used in other apps/devices. So there you're talking about incorporating a media file conversion program into Calibre and it's just...yeah.
I love Calibre with all my heart and think it's the best thing ever and I'm totally not worthy. But I'm not sure I'd get a very warm reception if I went to the Calibre developers and said "help me learn how to make your program do things it was never intended to do!"
|
many calibre users deal with with multiple MP3s audio books by adding an M3U playlist and keeping the MP3s elsewhere.
BR