After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 651275 - Imported audiobooks don't show up
Imported audiobooks don't show up
Status: RESOLVED DUPLICATE of bug 608381
Product: banshee
Classification: Other
Component: Importing
2.0.0
Other Linux
: Normal enhancement
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-05-27 18:05 UTC by Victor Vargas
Modified: 2011-06-04 02:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Victor Vargas 2011-05-27 18:05:32 UTC
This report was originally filled at:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/778963


First I kept all my music in "~/music" (*not* "~/Music"), including audiobooks. After importing this in Banshee, I was able to play them. In order to keep them from mixing too much with the rest of the music, and perhaps enable some separate features like *resuming playback after restart*, I dragged and dropped some audiobooks to the "Audiobooks" browser item. Worked fine. Then I discovered out that "Audiobooks" was tied up to "~/Audiobooks", so I figured it would be better to use that for storage (after changing it to "~/audiobooks" (but that is a rant for another time ;)). However, after moving the files to ~/audiobooks, and even trying to manually import from this folder in Banshee, nothing shows up in "Audiobooks" anymore.

In summary, I suggest the following:
* Make sure import works.
* Autodetect changes in the folders linked to Music and Audiobooks.
* Make it more obvious which folders are supposed to be used for different contents (maybe ask the user if they want to create them if they don't exist?).
Comment 1 Michael Martin-Smucker 2011-06-04 02:05:27 UTC
Importing audiobooks is incomplete at this point.  I think most of these concerns are already covered by Bug 608381, so I'm marking this as a duplicate.

*** This bug has been marked as a duplicate of bug 608381 ***