Ludek wrote: ↑Thu Dec 09, 2021 7:29 am
It sounds to me that it rather used the mask
Classical Music: \MyMusicCollection\MediaMonkeyTranscode\<Folder:2>\<Track #:2> $Left(<Artist>,20) - <Title>
i.e. the tracks are classical music, aren't they ?
If you put the same masks for the 'Music' and 'Classical Music' then I guess you will get consistent results, right ?
No, no & no. ... not even close to understanding what I am trying to say.
The tracks marked red in the top image are not Classical music.
They have used the default mask,
ie. they used \Music\
<Album Artist>\<Album>\<Track #:2> $Left(<Artist>,20) - <Title>
not my mask which was \Music\
<Folder:2>\<Filename>
ie. look at the folder name that it created by joining the two albumartist tags together with a semi-colon ... see the 2nd image in the post, that shows that actual source folder names
Forget I mentioned the classical music mask ... I meant to cut that line out of the post.
The issue is that:
- sync to device works as expected with my custom mask in all situations
- sync to Google Drive fails to use the custom mask in a situation where there are multiple AlbumArtist tags ... maybe it fails in all situations .. I can't tell because the default and my custom mask both would give the same results in that case
- and something appears to be wrong with the "Enforce use of the sync mask" option ... I will have a closer look at that if you fix this first problem
Background to this issue. I am wanting to use MM5 to transcode a terabyte of flac tracks to .mp3 and store them on Google Drive. I want the source and target dataset to use the exact same folder structure.
I want this because it is not hard, while testing MM5, to do a mass change to a big bunch of my tracks. eg. Autotag, or testing album art operations. This would trigger requirement to re-sync a lot of data up to Google Drive again, just because the track time stamps have been altered. ... Which is a pain obviously.
If the file structures are identical I van use a tool to "touch" my tracks, or the Google drive copies, so that each set has the same timestamps ... and therefore avoiding a lot of expensive and pointless resyncing,.
ie. MM5 sync to cloud is a good thing, but it is a crude tool because I don't have explicit control over what needs to be synced ... there is a simple workaround, but the file structures on each side need to be identical in this Use Case. MM5 should do this, but it has a bug IMO.