Track Redirection & Synchronization 3.4 (2012-10-08) [MM3+]

[nynaevelan]

I do not know anywhere where I can load my db for free, it is almost a gig in size.

Your database is a GB in size? By database, do you mean about audio files? I asked for your c:\Documents and Settings\your_username\Local Settings\Application Data\MediaMonkey\MM.DB - this is a database file, not audio files.

I know exactly what you meant and my db file is 840mb, as I said almost a gig.

I think my problems may be stemming from script conflicts,

Did you install some new script this days, before this started to happen? Maybe you could try temporary to remove all scripts from Auto folder except this one, just to check if this is a case. I know there are some nasty scripts, like Advanced Find & Fix/Tagging Inconsistencies, because of their .ini handling I lost my hardly written MN masks and RegExp presets several times. This is not connected with your case, but maybe there is a conflict with some another script.

The only new script I installed was the Export to Itunes script which I could not get to run so I uninstalled it and yours. And I do not know about nasty scripts or not but I have both ADFF and TI installed, and they have been for some time, and NO I am not uninstalling either because they are both critical scripts in my arsenal. I do know that this script and the Add/Remove Playstats script cannot or do not work well together. I do not know if this is because they are both trying to write to the track at the same time but I need that script and I am not uninstalling that one either. This script also interferes with the autosync of my portable player. Every since I installed it I have not been able to get the updated playcounts from my player.

if I uncheck the Syncronize metadata.... option does this turn off automatic syncronizing?

Yes, this option from the Options dialog box is only for automatic synchronization, if you turn it off the manual sync would be still available using the Synchronize Metadata of Redirected Tracks option from a menu. However, as I said most probably this option will not work if automatic sync already doesn't work since they both use the same function for synchronization - only the calling functions are different.

Because this script appears to offer some functionality that I would really like to use in order to keep my alternate versions up to date with my primary mp3 version, I would like to use it. However, I do not think the automatic syncing will work with my library and my needs. So, I will try to keep using it with the automatic syncing turned off. Hopefully this way it will play nice with my other installed scripts. I think the manual/autosync was not working on those particular tracks because something might have gotten corrupted with them or conflicts with other scripts. I tested the auto and manual syncing on other tracks and they worked. And once I removed the redirection on those tracks and re redirected them, they appear to be working manually.

[ZvezdanD]

I have not encountered these problems you are describing. What version of MM do you use?

You don't need to quote that Jiri's description. I still think that their decision to change .ini handling is discussable and one of the most problematic. I am using 3.1.0.1256. If you don't believe me, try this, Test 1:
- remove all scripts;
- install Magic Nodes;
- install ADFF;
- enter some new mask into MN;
- click Save;
- open MediaMonkey.ini file into Notepad or similar -> there is not a new mask.
- exit MM program;
- open MediaMonkey.ini file -> there is a new mask.

Test 2:
- remove all scripts;
- install only Magic Nodes;
- enter some new mask;
- click Save;
- open MediaMonkey.ini file -> there is a new mask.

[ZvezdanD]

my db file is 840mb, as I said almost a gig.

Wow! How did you get that? Maybe this is a reason for such things happening.

Maybe you could try temporary to remove all scripts from Auto folder except this one

NO I am not uninstalling either because they are both critical scripts in my arsenal.

I said temporary, just for five minutes... You don't need to uninstall them, just move .vbs files to some temporary folder and after test you could return them back.

once I removed the redirection on those tracks and re redirected them, they appear to be working manually.

Did you try to edit metadata of those problematic tracks, e.g. with the Properties dialog box? If you could do that, then my script should be able to modify their metadata as well.

[nynaevelan]

Wow! How did you get that? Maybe this is a reason for such things happening.

I just tripled the number of tracks in my library so I guess I shouldn't complain the db almost doubled in size. Also, I have a lot of script tables in my db.

I said temporary, just for five minutes... You don't need to uninstall them, just move .vbs files to some temporary folder and after test you could return them back.

I'll try the script in my test installation, that one doesn't have any scripts in it.

[Did you try to edit metadata of those problematic tracks, e.g. with the Properties dialog box? If you could do that, then my script should be able to modify their metadata as well.

Yes I did and it worked. I haven't tested yet if it captures changes that are made in the main tracklist or the now playing list, which is where I do alot of my editing.

[Bex]

I have not encountered these problems you are describing. What version of MM do you use?

You don't need to quote that Jiri's description. I still think that their decision to change .ini handling is discussable and one of the most problematic. I am using 3.1.0.1256. If you don't believe me, try this, Test 1:
- remove all scripts;
- install Magic Nodes;
- install ADFF;
- enter some new mask into MN;
- click Save;
- open MediaMonkey.ini file into Notepad or similar -> there is not a new mask.
- exit MM program;
- open MediaMonkey.ini file -> there is a new mask.

Test 2:
- remove all scripts;
- install only Magic Nodes;
- enter some new mask;
- click Save;
- open MediaMonkey.ini file -> there is a new mask.

Well, you need to use the Flush method to ensure that your changed (or created) ini values are immediately saved to the disk. Your scripts will otherwise get the behaviour you describe.
http://www.mediamonkey.com/wiki/index.p ... ile::Flush

Using a variable for the ini file is imo the preferred method since it's way faster. Many scripters do do.

[ZvezdanD]

Well, you need to use the Flush method to ensure that your changed (or created) ini values are immediately saved to the disk.

I knew that you will say that. Well, I don't need to use the Flush method since my scripts work just fine without it (and without installed your scripts). And it is not true that SDB.IniFile is a way faster if it is used with a global variable. Anyway, I don't need to write to .ini file so often to get some slow-downs because of such use. In my opinion reliability is more important than speed. If I need reliability I need to use Flush method every time after oSomeGlobalIniVarialble.StringValue = ..., so I would get same slow-downs as when I use SDB.IniFile directly. You are not using Flush method either, so if the program crashes your .ini settings made during last session would be lost as well.

[nynaevelan]

Well, I don't need to use the Flush method since my scripts work just fine without it (and without installed your scripts)...

I hate to jump in the middle of this debate, but isn't this a big assumption that no users of your script(s) will also be using Bex's or anyone else's scripts?? Knowing there could be a conflict, couldn't/shouldn't this be taken into consideration??

[ZvezdanD]

I hate to jump in the middle of this debate, but isn't this a big assumption that no users of your script(s) will also be using Bex's or anyone else's scripts?? Knowing there could be a conflict, couldn't/shouldn't this be taken into consideration??

Yes, Bex should take this into consideration and change his code to not use global variable for SDB.IniFile, like he did with PlayHistory. There is also a lot of old scripts which are written before that problematic .ini change, their authors are not maintaining those scripts anymore to add some strange Flush method or similar.

[nynaevelan]

I did some tests of the manual syncing and this seems to work but it appears the option to only update any changes except playcount is not evident. When manually syncing, is there a way to limit the updates from the redirected track to only include the playdata and not any metadata??

[ZvezdanD]

I did some tests of the manual syncing and this seems to work but it appears the option to only update any changes except playcount is not evident. When manually syncing, is there a way to limit the updates from the redirected track to only include the playdata and not any metadata??

I just tried and Playcount/LastTimePlayed are synchronized correctly. Yes, you could synchrronize only playcount/lastplayed if you turn off all other metadata in the Options dialog box (Artist, Album , Title, ...) - same settings for metadata are for automatic and manual synchronization. By the way, if some metadata, e.g. Artist, is same between master and redirected track, it would not be written during sync at all (there is no need to write same data over existing tag).

[nynaevelan]

I don't think I explained myself correctly. I changed some metadata info on the redirected track as well as the playcount. When I clicked on the Syncronhize Metadata option it updated the playcount and the metadata on the master track. For me I would want the metadata to stay as it is on the master track, but I would want the updated playcount info.

Nyn

[ZvezdanD]

I changed some metadata info on the redirected track as well as the playcount. When I clicked on the Syncronhize Metadata option it updated the playcount and the metadata on the master track. For me I would want the metadata to stay as it is on the master track, but I would want the updated playcount info.

I suppose you have turned off the Synchronize metadata - Master only option. Sorry, you are right, there is a problem with that. I need to add one more check box to turn on/off automatic synchronization and those two existing check boxes (master or redirected / master only) should have an effect no matter which mode is used (auto or manual).

Until I add such new option, you could try with the Synchronize metadata - Master option turned on and your metadata/placounts would be updated only for redirected tracks. However, in that case you would have automatic synchronization turned on as well, but currently this is only way. I will try to finish the next version as soon as possible...

[nynaevelan]

Thanks, I will wait for your update. I cannot turn on automatic because of the conflicts and I think it is save to use the manual because I do not make any changes on the alternate versions.

Nyn

[ZvezdanD]

I think it is save to use the manual because I do not make any changes on the alternate versions.

I am not sure that understand, but maybe you could use the Synchronize Metadata menu option even now - when you get displayed the dialog box asking you "Do you want to synchronize metadata for linked tracks to match the selected ones or all redirected tracks to match their masters?" you could choose Yes to All and script will update only redirected tracks leaving masters unchanged. However, you could use this option only to synchronize all redirected tracks, not just selected ones...

[nynaevelan]

I think it is save to use the manual because I do not make any changes on the alternate versions.

I am not sure that understand, but maybe you could use the Synchronize Metadata menu option even now - when you get displayed the dialog box asking you "Do you want to synchronize metadata for linked tracks to match the selected ones or all redirected tracks to match their masters?" you could choose Yes to All and script will update only redirected tracks leaving masters unchanged. However, you could use this option only to synchronize all redirected tracks, not just selected ones...

Thanks for the tip, that makes it easier to figure out which ones need updating. I assume it will only update the ones that have changes?