by Fontman » Wed Dec 13, 2017 1:51 pm
Re<< I don't understand exactly what you mean. You can set the Destination to be used in the Device Profile. What corruption? >>
I'm unsure of the exact nature of the corrupted folders, but in their odd state, I was unable to manually copy anything into that folder or its sub-folder. I was able to rename the offending folders and recreate the properly named folders which subsequently allowed me to copy files into the these areas. I then deleted the corrupted folders.
I was adding a comment about what appears to be a rather odd default destination string which appears as:
\Music\<Album Artist> - <Album>\<Track#:2> $Left(<Artist>,20) - <Title>
Surely, even referring to tracks is now outdated and having way too many folders and sub-folders only raises the risk of experiencing some sort of corruption. I realize you can change it and I try to save a simpler device profile for each device which has not always worked, meaning I always have to check the destination prior to any copying or syncing.
Re<< I don't understand exactly what you mean. You can set the Destination to be used in the Device Profile. What corruption? >>
I'm unsure of the exact nature of the corrupted folders, but in their odd state, I was unable to manually copy anything into that folder or its sub-folder. I was able to rename the offending folders and recreate the properly named folders which subsequently allowed me to copy files into the these areas. I then deleted the corrupted folders.
I was adding a comment about what appears to be a rather odd default destination string which appears as:
\Music\<Album Artist> - <Album>\<Track#:2> $Left(<Artist>,20) - <Title>
Surely, even referring to tracks is now outdated and having way too many folders and sub-folders only raises the risk of experiencing some sort of corruption. I realize you can change it and I try to save a simpler device profile for each device which has not always worked, meaning I always have to check the destination prior to any copying or syncing.