I'm probably missing the obvious again, but...
When I first began to use Calibre to manage my eBook library and I added books, Calibre created directories under it's main Calibre Library folder as needed, with the author's name as directory name, and further books by that author went into that sub-directory. When I used Calibre to transfer books to my Android tablet, it retained that structure.
On my Android tablet, eBooks are stored in the /eBooks directory on an external 32GB microSD card. Calibre knows to place books transferred to device there, and FBReader knows that's the directory eBooks live in.
Recently I discovered that new books I add to Calibre aren't being placed in existing sub-directories, and new directories aren't being created. All books are winding up in the top level eBooks directory.
I have made no changes I'm aware of in Calibre's config that might affect this, so I'm confused as to why it's occurring. I looked at the Calibre docs, and unless I am misunderstanding them, the default action Calibre takes when transferring books to device should replicate the directory structure Calibre maintains on the desktop.
I'm trying to debug a recent problem with FBReader Premium on the tablet. When it scans for new books, it never successfully completes - a background library scan process continues endlessly, and chews up enough CPU to make reading the current book problematic.
FBReader's author has been sent a copy of the books.db file where FBReader stores its list, and I await commentary. This is not the first time I've had this sort of problem. I don't know if I have the largest library on device that FBReader is called upon to deal with, but I suspect I'm well up on the shortlist. :p (I am a pack rat who likes carrying a large library around with me.) FBReader's author says there isn't an arbitrary limit in library size. Not in his code, perhaps, but I suspect third-party code he uses might be choking.
Meanwhile, when thousands of eBooks are winding up in the top level directory when they all should be in sub-directories, my spider sense tingles and I wonder if it's a contributing factor.
What should the format string Calibre uses to determine how to transfer books to device be to make it create directories and store books in them? I want to make sure that's what it's using, and eliminate one variable.
Thanks in advance,
______
Dennis
When I first began to use Calibre to manage my eBook library and I added books, Calibre created directories under it's main Calibre Library folder as needed, with the author's name as directory name, and further books by that author went into that sub-directory. When I used Calibre to transfer books to my Android tablet, it retained that structure.
On my Android tablet, eBooks are stored in the /eBooks directory on an external 32GB microSD card. Calibre knows to place books transferred to device there, and FBReader knows that's the directory eBooks live in.
Recently I discovered that new books I add to Calibre aren't being placed in existing sub-directories, and new directories aren't being created. All books are winding up in the top level eBooks directory.
I have made no changes I'm aware of in Calibre's config that might affect this, so I'm confused as to why it's occurring. I looked at the Calibre docs, and unless I am misunderstanding them, the default action Calibre takes when transferring books to device should replicate the directory structure Calibre maintains on the desktop.
I'm trying to debug a recent problem with FBReader Premium on the tablet. When it scans for new books, it never successfully completes - a background library scan process continues endlessly, and chews up enough CPU to make reading the current book problematic.
FBReader's author has been sent a copy of the books.db file where FBReader stores its list, and I await commentary. This is not the first time I've had this sort of problem. I don't know if I have the largest library on device that FBReader is called upon to deal with, but I suspect I'm well up on the shortlist. :p (I am a pack rat who likes carrying a large library around with me.) FBReader's author says there isn't an arbitrary limit in library size. Not in his code, perhaps, but I suspect third-party code he uses might be choking.
Meanwhile, when thousands of eBooks are winding up in the top level directory when they all should be in sub-directories, my spider sense tingles and I wonder if it's a contributing factor.
What should the format string Calibre uses to determine how to transfer books to device be to make it create directories and store books in them? I want to make sure that's what it's using, and eliminate one variable.
Thanks in advance,
______
Dennis