Audiobook ordering problem

[markand 9]

I'm running Emby on QNAP, version 4.3.1.0, using the Web UI. The issue also appears in the app UI of my Sony TV.

 

I created an Audiobook Library and added a single book, The Bible. I went through and renamed the files according to the documented audiobook naming guide. It has 2 folders for OT & NT. Emby picked it up perfectly and downloaded the correct image of David Suchet. However, everything else gets screwed up. 

 

Here is a snapshot of file naming:
 

 

First, the names of the folders are all wrong. Despite the fact that they're named New/Old Testament, the name they get is of one of the tracks (Note: The missing "The" in Holy Bible is because I copied the folder into a different folder name)

 

 

And despite having named the chapters with numbering such as "1- Genesis", "2- Exodus", etc. The ordering is odd. Most of it is alphabetical minus the "n- " numbers. Such as "1 Chronicles", "1 Kings", ...., "Amos", "Daniel", etc. (Some names of the chapters in the Bible have numbers.) However, 3 of the files are named and ordered INCLUDING the chapter numbers, minus the -: "37 Haggai", "38 Zechariah", etc.  

 

 

I was able to fix the folder names and ordering issues via the Metadata Manager. However it took a long time. It seems like audiobooks are broken.

 

Is this a bug/set of bugs?

 

I've attached the log file.

audiobook-renaming-bug-logfile.txt

[Luke 42080]

Hi @@markand what is the content type of the library in emby library setup?

[markand 9]

Ok, very odd. So the content type of the old library was Audiobook. I just created ANOTHER one pointing to the same Folder and after creation and selecting Albums, everything (book name, chapter ordering) was correct.

 

Could the system have the ordering from the other library? Previously, I had done it a few times (as you might be able to see in the logs) and it was always wrong.

 

I did manage to listen to a chapter using my Sony TV and the playback (skip, rewind, ff) was wonky and got lost.

[Luke 42080]

It's possible there was some issue created by an older version. I would just remove the other library. Thanks for the feedback.