Copy/paste mostly from another reply I made:
I have a huge audiobook library, I was fully prepared to do all the processes to move and organize my mess of a library to get it working with Plex. I’m sure you’ve seen the GitHub guide floating around.
But when it came time to sit down and configure my server for audiobooks, ebooks, tv, movies, and music, I found that audiobookshelf just did a way better job with less of a headache. My current stack is Beet.io with audible support to move my already downloaded library into a better folder and naming structure. Once I get those all finished I won’t have to use this step. This gets stuff about ~80% of the way there except when the source is really messed up.
From there I have Readarr looking at the Beets destination folder and managing downloads. This is pretty good for getting most of the rest of the info with some clean up and is similar to setting up other Arrs. Then audiobookshelf for final tweaks and browsing/downloading.
It’s quite a pain to ingest an initial large library but for new downloads it’s been pretty seamless. Way easier and more consistent than having to do most of this anyway plus fight with Plex.
The audiobookshelf library is really great and can pull audiobook specific information from a lot of sources automatically. You can browse by series or narrator or genre too and if you listen through their app or through the browser it syncs your progress which is nice.
The audiobookshelf app is pretty good for browsing and downloading but I don’t like the player as much as my usual one. But you can just point the download at whatever folder your favorite player uses.
Since you’re already using Plex for audiobooks you can probably skip all these steps straight to audiobookshelf if your folder structure already matches
Have you ever checked out OrangePi? I was considering them before picking up a jetson nano. It’s crazy to think that a rpi4b is going for the same price from resellers as a jetson with cuda and tenserflow support.