GNOME Bugzilla – Bug 578005
Preupdate database for Sansa Fuze as part of syncronization
Last modified: 2009-05-18 14:23:11 UTC
Please describe the problem: The Sansa Fuze uses it's own internal database which gets updated after each syncronization and unplug. It would be nice if this database could be updated and syncronized to the device to skip this step. Steps to reproduce: 1. Attach Sansa Fuze 2. Add or remove track(s) 3. Eject and unplug Actual results: The Fuze will update it's database Expected results: We know everything that database is likely to want, we should be able to update it and provide a smoother experience. Does this happen every time? 100% Other information: x86_64, da_DK.UTF-8, Fedora 11, Mono 2.4 pre and SVN revision 5188 of Banshee.
I don't think it would be reasonable for banshee to start messing around with the databases on devices. We would probably use this feature if it's provided by a library used to interface with the device (like libmtp in your case).
probably not, I was hoping there was some kind of standard in place or perhaps at least easy abstraction. I saw something like this being done in the support for Rockbox and I was hoping it could be extended easily. We are in full agreement, if the only way is manually reverse enginnering and hacking up a solution for each device then this is not worth it. Admittedly I know very little of portable player standards.
I've been reading the standard in the vague hope of doing a C# implementation one rainy day and there is no set standard for this. Since that is the case I agree that it is not the right place for Banshee to be messing about.