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
I get that creating a directory structure within the "books" aka library folder is difficult. What about creating a book.json that identifies all the parts and pieces of a book. The book.json file could contain the path to all the individual audio files that comprise the audiobook. This would eliminate the need of copying all the files into books aka library. Almost all the information is already collected and created in the current books.json file. The books.json file could point to the "Book".json file i.e. RedRiver.json. I would suggest that this becomes and option on Library creation. Thoughts anyone!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I get that creating a directory structure within the "books" aka library folder is difficult. What about creating a book.json that identifies all the parts and pieces of a book. The book.json file could contain the path to all the individual audio files that comprise the audiobook. This would eliminate the need of copying all the files into books aka library. Almost all the information is already collected and created in the current books.json file. The books.json file could point to the "Book".json file i.e. RedRiver.json. I would suggest that this becomes and option on Library creation. Thoughts anyone!
Beta Was this translation helpful? Give feedback.
All reactions