diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawlnhME0DDX-SviTAJ_NOH8nZmfgli3z6YQ <Emmanuel@web> | 2013-12-07 08:19:49 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-12-07 08:19:49 +0000 |
| commit | 77bb3e72ad7d0c755556b85fd5113decce806a6a (patch) | |
| tree | 4084f9919c909d6259ee79bf387dd1258a13cd73 | |
| parent | 9066b589ae8bf7fb728b36308d1801a5929c0372 (diff) | |
| -rw-r--r-- | doc/forum/handling_MP3_metadata_changes.txt | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/forum/handling_MP3_metadata_changes.txt b/doc/forum/handling_MP3_metadata_changes.txt new file mode 100644 index 000000000..9b6caa27a --- /dev/null +++ b/doc/forum/handling_MP3_metadata_changes.txt @@ -0,0 +1,12 @@ +Hello, + +I'm still looking for a way to version control the metadata (title, artist, album name, ...) of my MP3s, I wonder if git annex could help for this problem ? +The method I use now (without git annex) is to export the MP3 metadata to an textual format with one line per tag. +It's this textual file I handles with git. +The problem is to handle the mapping between the orignal file and the export file with file renaming or moving. +I consider to use the checksum of the audio content (without metadata, this checksum never changes) to handle this problem. +Maybe git annex has a different approach (better) to solve this problem ? +How git annex would be use to solve the orignal problem ? + +Regards, +Emmanuel Berry |