MoDementia wrote:I mean Alpha Testers for my new script SyncTheSync
What it does:
Keeps Converted Tracks MetaData in Sync with the Original Track and vice versa
wolfzell wrote:The "vice versa" part is making me think. For your concept I guess it is necessary (otherwise there would be no sync-back of changed ratings on portable devices), but I am not sure if this will not give you a huge headache later.
wolfzell wrote:1. Having the same data twice in a database and keeping it in sync seems risky to me and a very good way of getting into trouble when syncing somehow fails. It is hard enough right now sometimes to keep the metadata and the database in perfect sync.
wolfzell wrote:2. Personally I would like never having to see/manage/touch the converted tracks in MM at all. So I suppose the basic scenario for me would be to always have the filter active for the original library.
wolfzell wrote:But then: How does MM know that it should use the converted tracks when syncing? Does this mean I will have to switch filters before syncing?
3. How about the playlists and their management then? I mainly sync using my playlists. Does this mean, all playlists have to be there twice? Once with the original and once converted?
wolfzell wrote:4. What about file location? Renaming and sorting the files might get really tricky. MM does not have a way to sort the files into 2 different directories now, based on their format, or has it? And then: What happens if files in the original database do have the same format as their duplicates? For example, not 100% of my library is in MP3, but about 15% are in MP3 already. What is happening to them using your script?
MoDementia wrote:" sync-back of changed ratings on portable devices" This is the main reason for having it work both ways, I'm not expecting a huge headache.
In fact I think it could be written to to update different fields depending on the direction. Interesting
MoDementia wrote:I havent checked if views affect the setting up of directories and tracks to be synched but manaul playlists will need to be created in the correct view I think, but autoplaylists should be fine to create in any view, they will both sync/play etc in any view
MoDementia wrote:You can auto organise on many fields including bitrate which should help separate most of them.
MoDementia wrote:The scirpt actually establishes the link at the point of the conversion regardless of where it is located. Only the catch up script (Manual Build Table Script) might have trouble locating all the links but can be modified no end to cater for any setup.
All future conversions will automatically be tracked.
MoDementia wrote:Hope I've answered most of your concerns so far
wolfzell wrote:"playcount" or "times skipped"
What happens when ratings got changed on both sides?
wolfzell wrote:I am afraid that you are right. Well, many of my playlists are done manually and updated when adding new tracks. So this might be a challenge.
wolfzell wrote:Another challenge. As I mentioned, 85% of my library is in FLAC. But the other 15% are in 192kbps MP3. My sync settings are converting the FLAC files to 192kbps MP3 and the files already in MP3 format simply get copied.
wolfzell wrote:Still the auto organise function will be very critical. What would happen if the filter wasn't set? Ok, the resulting duplicates might be obvious to see, but still...
wolfzell wrote:Wouldn't it be much easier and safer to use one of the user tag fields for this script? I myself would very happily sacrifice one of them if this would ease the situation.
Added writetags option, also has the advantage of refreshing MMs main track list woot.
Users browsing this forum: No registered users and 25 guests