Clarification on CloudPlayer sync behaviour
Hi, I'm a very new Cloud Player convert, and I'd like to get some clarification on the syncing from the cloud. I recently found that if I correct some metadata (album year) on pre-exisiting albums on Google Drive, these changes aren't carried over to Cloud Player. I had to manually edit the metadata in all instances of Cloud Player (phone and two tablets), to correct the information.
Doesn't Cloud Player update the metadata on existing tracks, even when the timestamp of files on Google Drive has changed? Seems not.
When editing metadata in Cloud Player, are these changes sync'd back to the cloud?
When deleting tracks/albums in Cloud Player, are they also removed from the cloud?
In order to force Cloud Player to update tag fields that have changed in the cloud, would it make sense to delete these tracks from Cloud Player, and then initiate a re-sync? Any other way to achieve the same behaviour?
Could it be a feature enhancement to force the resync of all tag data from the cloud, when the timestamp of a file in the cloud has changed?
Many thanks.
-
Official comment
Hello,
Thanks for using CloudPlayer. I will try and address some of your questions.
1. After extracting metadata during the initial scan, CloudPlayer does not import changes to the metadata for a given file. Users have requested a "rescan" option so this is something we're looking into for the future. If you want to force a rescan, please ban/unban the folder.
2. If you make metadata changes using CloudPlayer, they are not pushed back to the cloud files. Unfortunately the cloud services do not support partial writes or have an API for updating metadata.
3. If you delete cloud songs in CloudPlayer, they will also be removed from your cloud account. If you wish to remove just the library entry, please use the "Ban Folder" option.
-
Thank you for the clarifications. A couple of suggestions then, if I may ...
1. In order to maintain CloudPlayer ease of use (I think you've done a great job on this) I would suggest extending the existing "Scan Cloud Storage" to force update of metadata when the timestamps of files in the cloud are more recent than those on the local device. Seems to me that introducing a new "Rescan" option is unnecessary.
2 & 3. I think it's a good thing that changes are *not* pushed back to the cloud. For many people I suspect that the cloud files represent their 'master' copy, and it might be desirable to have a settings option to disable removal of cloud files altogether. Or at least make it clearer by providing two options, delete from the local device only, or delete from both the local device and the cloud.
Many thanks again.
Nigel0 -
Hello,
Thank you for the additional feedback, I will forward them to the product manager and QA/Dev team.
0
Please sign in to leave a comment.
Comments
3 comments