You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many audiobooks found in the wild are packaged with subdirectory representing "discs" or section. That's how I understood the use for "directory containing subdirectories with files". However, it's not great as subdirectories aren't grouped together. Or maybe it's for a top-level directory containing a library of "books", in which case the former use case doesn't fit.
How about simply adding a "library directory" or a "book directory". A library directory expects book subdirectories. A book directory may contain files or subdirectories with files (sections), which the app can just treat as a book functionally, or expand as a heading if keeping a flat list of files is easier.
It seems like the UI components are already in place for this. It would save us manually adding and removing "books" from the library. In my case, the top library directory is managed by Synthing.
The text was updated successfully, but these errors were encountered:
I normalize books on pc to flat structure, eliminate volumes, CD123s. Instead of adding scan directories manually. but even so, this way is limited: now I need a level of "author" of book folders because of mess created by flat structure
Many audiobooks found in the wild are packaged with subdirectory representing "discs" or section. That's how I understood the use for "directory containing subdirectories with files". However, it's not great as subdirectories aren't grouped together. Or maybe it's for a top-level directory containing a library of "books", in which case the former use case doesn't fit.
How about simply adding a "library directory" or a "book directory". A library directory expects book subdirectories. A book directory may contain files or subdirectories with files (sections), which the app can just treat as a book functionally, or expand as a heading if keeping a flat list of files is easier.
It seems like the UI components are already in place for this. It would save us manually adding and removing "books" from the library. In my case, the top library directory is managed by Synthing.
The text was updated successfully, but these errors were encountered: