“Doing an update instead of a rebuild might avoid this but might require a more sophisticated database structure and more code in the firmware.”
Its not just that, it may make the player’s interface much more sluggish.
@promisedplanet wrote:
@marqck wrote:
it should be the same with the fuze, add songs by connecting to computer, after you uplug, “refreshing database” will show…
take out the card, use a card reader to add songs, after you insert the card, it should say “refreshing data base”
My point is that the Fuze would re-read the contents of the card even if they weren’t changed, but the contents of internal memory were changed.
It doesn’t necessarily have to be the same way with the Clip+, does it? Unless they share the same portion of the firmware that deals with database updates. The Sansa Connect doesn’t do this.
i don’t think the player can know if the contents of the card were changed or not.
maybe SanDisk can just add an option called “refresh data base” and under it you can choose “automatic” or “manual”. if you choose manual, you’ll have the options “refresh internal”, “refresh external” and “refresh both”. what do you think?
Edit: spell check
Message Edited by marqck on 09-05-2009 01:30 AM
marqck wrote:
“i don’t think the player can know if the contents of the card were changed or not.”
As I said, the Sansa Connect does this. I’m not sure how. Maybe the card contains some kind of hash value of its contents, or a date-last-modified, or something. Or maybe it’s an MTP function.
“maybe SanDisk can just add an option called “refresh data base” and under it you can choose “automatic” or “manual”. if you choose manual, you’ll have the options “refresh internal”, “refresh external” and “refresh both”. what do you think?”
Yep, that’d work.
