More > Media Center 12 (Development Ended)
Playlists (Backup discussion)
Frobozz:
Playlists and other aspects of MC that break just because a file was renamed or modified outside of MC is not good. Almost always not what the user would want to have happen.
Brainstorming ideas here.
What about storing a magic key value (maybe a GUID) in the tag for each file. If a file is renamed and lost from a playlist it can be found again by searching all files for that GUID. That would only work with files that have tagging support and the user would also need to enable writing to tags.
What about doing the same but using NTFS ADS (Alternate Data Stream). Write a magic key to the ADS for each file. That would only work if the files are saved on an NTFS drive. Wouldn't work for FAT32 drives or various network storage drives. The ADS will stay with the file even if the file is renamed. The ADS might be lost though if a third party application rewrites the file.
Peter_T:
I really like where you're going here... it would at least work for (most) music and photos.
--- Quote from: Frobozz on April 22, 2009, 10:38:04 pm ---Brainstorming ideas here.
What about storing a magic key value (maybe a GUID) in the tag for each file. If a file is renamed and lost from a playlist it can be found again by searching all files for that GUID. That would only work with files that have tagging support and the user would also need to enable writing to tags.
What about doing the same but using NTFS ADS (Alternate Data Stream). Write a magic key to the ADS for each file. That would only work if the files are saved on an NTFS drive. Wouldn't work for FAT32 drives or various network storage drives. The ADS will stay with the file even if the file is renamed. The ADS might be lost though if a third party application rewrites the file.
--- End quote ---
Matt:
--- Quote from: Frobozz on April 22, 2009, 10:38:04 pm ---Playlists and other aspects of MC that break just because a file was renamed or modified outside of MC is not good. Almost always not what the user would want to have happen.
Brainstorming ideas here.
What about storing a magic key value (maybe a GUID) in the tag for each file. If a file is renamed and lost from a playlist it can be found again by searching all files for that GUID. That would only work with files that have tagging support and the user would also need to enable writing to tags.
What about doing the same but using NTFS ADS (Alternate Data Stream). Write a magic key to the ADS for each file. That would only work if the files are saved on an NTFS drive. Wouldn't work for FAT32 drives or various network storage drives. The ADS will stay with the file even if the file is renamed. The ADS might be lost though if a third party application rewrites the file.
--- End quote ---
Auto-import will already fix broken links, as long as you have it looking in the new location so it finds the moved file.
AoXoMoXoA:
--- Quote from: Frobozz on April 22, 2009, 10:38:04 pm ---Playlists and other aspects of MC that break just because a file was renamed or modified outside of MC is not good. Almost always not what the user would want to have happen.
--- End quote ---
Not sure what was meant by a playlist 'breaking' or what you would expect MC (or any other software) to do in such a situation.
Of course the file you moved/renamed/changed outside of MC will no longer be in the MC Library/database or will show as missing since MC has no way of knowing what you did "behind it's back" . . . . MC is not omniscient.
MC has many handy and powerful tools for file management, which when used maintains the integrity of your Library/database and all of it's Playlists. Problem solved ;)
tunetyme:
--- Quote ---Problem solved
--- End quote ---
How? It seems that the problem hasn't been explained clearly and/or it hasn't been understood. Both Peter_T and Frobuzz get it.
If you can import and export to M3U file format why can't you automatically store the playlist information in that standard format? If it is stored external to MC database then there is no problem if something is done outside MC.
I turned off automatic import because it does things without my specific knowledge. For example if a folder with some music is damaged an unreadable I will never know it unless I specifically seek that folder from my own memory. I have over 14,000 songs in my database and I don't remember all of them. That's why I have MC and not just a library of CD's.
This isn't a wish list item this is vital to the integrity of the system as a whole. I want to know if some file is damaged, lost, or duplicated. I use multiple disks to store my music and at times I need to rearrange my files. There have been times when I have lost files or they were damaged. When I can identify that, then I can replace them from my hard copy. The problem is not solved and it appears that some just want to blow it off.
Tunetyme
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version