getmusicbee.com

MusicBee & Add-Ons => Plugins => Topic started by: boroda on June 26, 2011, 08:01:00 PM

Title: Additional Tagging & Reporting Tools
Post by: boroda on June 26, 2011, 08:01:00 PM
Plugin adds several commands to MB main menu:

1. Copy tag

Allows you to copy one tag to another for selected files. It's possible to append one tag to the end of another tag or add one tag to the beginning of another tag placing custom text between them. Also, its possible to use '<Null>' pseudo tag as the source to append static text to the destination tag.

2. Swap tags

Swaps any two tags for selected files.

3. Change case

Changes letter case of a tag according to rather sophisticated rules for selected tracks.

4. Library reports

Allows to export some library statistics for currently displayed tracks to external file: HTML document (as a table), tab delimited text, M3U playlist (its only possible to export file paths to playlists, but considering filtering capability of command this option may be useful). This may be used for reimporting table in spreadsheet editor (including HTML table - it's the easiest way to import track list to MS Excel) for printing statistics or just content of your library, filtered content of library or your playlists.

5. Auto rate

Calculates auto rating on the basis of the number of plays per day for selected tracks. Also, its possible to auto rate all tracks of your library on MusicBee startup or update auto rating if currently played track is changed.

6. Reencode tag

Even ID3V2 tags are usually stored not in UTF encoding (which is independent of language), so in most cases reading ID3 tags is only useful if tags use the same encoding (in general - language) as your windows default encoding. This command allows you to convert any incorrectly interpreted not UTF tags to UTF tags. In this command 'initial encoding' is the suggested actual encoding of tag and the 'used encoding' is incorrectly interpreted encoding of tag (Usually it's your default windows encoding. The only sense to change 'used encoding' is if you get music file from another computer with different regional settings).

7. Advanced search and replace

8. Calculate average album ratings

Command averages all the ratings of the individual tracks on the album writing result to an Album rating. Any tags can be used as album and track ratings. This may be useful for calculating average album rating for auto rating stored in custom tag.



Provide feedback on this topic.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on June 26, 2011, 08:49:11 PM
thanks Boroda74.
I'll look to do the 2 missing items from the MB side next week
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on June 26, 2011, 09:18:54 PM
Nice plugin! Although I still can't figure out how to get that issue resolved from my custom search option, I think I just need to tinker around it more. I can tell this is a pretty powerful tool and, along with your Russian contributions, you must be one busy person :)

Anywho, I do have one thing I'm having a problem with, and it's the "Change Case" tag.

OK, let's say I have a song currently titled "The Way Of The North King And The Way Of The South Queen (The Most Awesome Title With A Beat)." For capitalization rules, in this example at least, "of", "the", "and", "with", and "a" should be lowercased, unless it's the first word of a title or the first word inside the parentheses. Thus, the title should be look like "The Way of the North King and the Way of the South Queen (The Most Awesome Title with a Beat)." However, I can't seem to make that work thus far...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 26, 2011, 09:40:09 PM
Although I still can't figure out how to get that issue resolved from my custom search option... :)
You are right. I forgot your initial problem implementing 'album count' tag. Well, what about selecting (in order) 'album artist'
, 'year', 'album', 'album count', 'url'? All is OK now? :)

OK, let's say I have a song currently titled "The Way Of The North King And The Way Of The South Queen (The Most Awesome Title With A Beat)." For capitalization rules, in this example at least, "of", "the", "and", "with", and "a" should be lowercased, unless it's the first word of a title or the first word inside the parentheses. Thus, the title should be look like "The Way of the North King and the Way of the South Queen (The Most Awesome Title with a Beat)." However, I can't seem to make that work thus far...
Yes, there is some bug with excluded words
Title: Re: Additional Tagging and Reporting Tools
Post by: cartman005 on June 26, 2011, 09:52:47 PM
I can see this plugin being super useful if I ever need to do some bulk tag operations. Will keep it in mind. Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on June 29, 2011, 09:24:43 PM
boroda74, i have updated the API - i will send you a PM with instructions
Title: Re: Additional Tagging and Reporting Tools
Post by: chuckmoore on July 07, 2011, 12:28:55 AM
I downloaded this plugin and it has a ".rar" extension. I don't know how I can use it. The format isn't compatible with Windows. Also, I would be happy if the "Auto-tag" feature would also tag the <Album Artist> field because I think that the <album artist> field is an important tag because most players and tag editors use that field. I would be grateful if that field was added with the auto-tag feature.
Title: Re: Additional Tagging and Reporting Tools
Post by: Elberet on July 07, 2011, 03:47:31 AM
".rar" files are compressed archives. The actual plugin file is inside the archive, and you need a program capable of handling RAR archives to read the archive and extract the plugin file, such as the free 7-zip program (www.7-zip.org (http://www.7-zip.org/)).
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on July 07, 2011, 06:19:38 AM
Also, I would be happy if the "Auto-tag" feature would also tag the <Album Artist> field because I think that the <album artist> field is an important tag because most players and tag editors use that field. I would be grateful if that field was added with the auto-tag feature.
If you are referring to the native MB autotagging, it already supports album artist. I also thought this (boroda74's) plugin already had album artist from what i have seen but perhaps he is best to answer that
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 07, 2011, 03:49:18 PM
I downloaded this plugin and it has a ".rar" extension. I don't know how I can use it. The format isn't compatible with Windows.
I'm using .rar archive format because it preserves all Unicode chars in file paths. Well, OK,, I'll use more common .zip format if no files are using non-ASCII chars in file paths.

Also, I would be happy if the "Auto-tag" feature would also tag the <Album Artist> field because I think that the <album artist> field is an important tag because most players and tag editors use that field. I would be grateful if that field was added with the auto-tag feature.
I'm not sure about what you name "Auto-tag" feature. "Auto-tag" feature is native function of MusicBee. If you mean 'Tag counter' virtual tag then its already capable to count any tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on July 07, 2011, 07:57:22 PM
Thanks, great work.  ;)
Title: Re: Additional Tagging and Reporting Tools
Post by: jrlx on July 14, 2011, 12:30:52 PM
I'm unable to run this plugin. I'm sure I'm missing something... I created a "Plugins" folder in my MB installation (C:\Program Files (x86)\MusicBee\Plugins) but no "additional tagging tools" entry appeared in the "Tools\Tagging Tools" menu. If I go to Edit\Preferences\Plugins I get a program crash.

If the plugins folder is renamed to "plugins" or "plugin" there is no crash when going to Edit\Preferences\Plugins but I still don't get any additional menu entry.

I'm sure this one is pretty basic but any help would be welcome.
Title: Re: Additional Tagging and Reporting Tools
Post by: ma_t14 on July 14, 2011, 12:46:25 PM
I'm unable to run this plugin. I'm sure I'm missing something... I created a "Plugins" folder in my MB installation (C:\Program Files (x86)\MusicBee\Plugins) but no "additional tagging tools" entry appeared in the "Tools\Tagging Tools" menu. If I go to Edit\Preferences\Plugins I get a program crash.

If the plugins folder is renamed to "plugins" or "plugin" there is no crash when going to Edit\Preferences\Plugins but I still don't get any additional menu entry.

I'm sure this one is pretty basic but any help would be welcome.


What MusicBee version are you using?

Try with the latest version installed. Download here: http://www.mediafire.com/?awg4bp3xkca6kgx (http://www.mediafire.com/?awg4bp3xkca6kgx)

Just extract the contents to musicbee program files folder and replace
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 14, 2011, 12:49:52 PM
I'm unable to run this plugin. I'm sure I'm missing something... I created a "Plugins" folder in my MB installation (C:\Program Files (x86)\MusicBee\Plugins) but no "additional tagging tools" entry appeared in the "Tools\Tagging Tools" menu. If I go to Edit\Preferences\Plugins I get a program crash.
Try MB version from 1.2.4197 to 1.2.4210 (probably you are using more later version).

Steven, it seems that my plugin causes MB to crash when I try to use latest MB version.
Title: Re: Additional Tagging and Reporting Tools
Post by: Lore on July 14, 2011, 12:55:51 PM
Hi,

Is there a way to create an action that performs something like "Wipe unneeded tags"? I like to keep only certain tags in my files (e.g. Artist, Artist Album, track # and name etc.) and I always remove the other ones manually; something to do this in an automatic way would be really appreciated :)
Thanks and regards,
Lore
Title: Re: Additional Tagging and Reporting Tools
Post by: ma_t14 on July 14, 2011, 12:57:19 PM
I'm unable to run this plugin. I'm sure I'm missing something... I created a "Plugins" folder in my MB installation (C:\Program Files (x86)\MusicBee\Plugins) but no "additional tagging tools" entry appeared in the "Tools\Tagging Tools" menu. If I go to Edit\Preferences\Plugins I get a program crash.
Try MB version from 1.2.4197 to 1.2.4210 (probably you are using more later version).

Steven, it seems that my plugin causes MB to crash when I try to use latest MB version.

It works for me with 1.3.4212  ::)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on July 14, 2011, 03:33:40 PM
boroda74, the last change i made to the API was on 9-july
i tried out your last beta with the 1.3 version a couple of days ago and had no probs, so could you confirm its definitely not something changed on the tags plugin thats causing the probs.
if you feel it is definitely something changed on the MB side, what is the error you get and is there anything in the error log?
Title: Re: Additional Tagging and Reporting Tools
Post by: jrlx on July 14, 2011, 03:43:50 PM
Thanks for the help. I was using v 176. I have MB installed in two different PCs but this one was not updated to the latest version 212. I can now see the new menu entry and I can use the plug-in. However there's still a problem in the Edit\Preferences\Plugins configuration: I get two new entries (additional tagging tools and mb_tagtools.resources.dll). I can enable the first one but the second cannot be enabled and produces the following error message when I try to enable it:

"Unable to initialise this plugin:
Dll entry point: MusicBee.Plugin was not found"

Please note that I copied the three files in the zip to the Plugins folder in my MB installation.

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 14, 2011, 04:09:53 PM
boroda74, the last change i made to the API was on 9-july
...
if you feel it is definitely something changed on the MB side, what is the error you get and is there anything in the error log?
First of all I had a power failure :) Then I had a many steps to make MB work, the last step was full reinstall of last RC version, then I replaced exe with latest version (and this didn't work - plugin simply wasn't initialized and going to prefs/plugins crashed MB) then I replaced exe with 1.2.4210 and now all works. Also I've made some modifications of plugin.

I think I need some time to clear myself whats happening :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 14, 2011, 04:24:53 PM
However there's still a problem in the Edit\Preferences\Plugins configuration: I get two new entries (additional tagging tools and mb_tagtools.resources.dll). I can enable the first one but the second cannot be enabled and produces the following error message when I try to enable it:

"Unable to initialise this plugin:
Dll entry point: MusicBee.Plugin was not found"

Please note that I copied the three files in the zip to the Plugins folder in my MB installation.

It seems that you didnt keep folder structure unzipping archive. mb_tagtools.resources.dll should be in 'ru' subfolder of plugins folder and therefore shouldn't be displayed in prefs/plugins. You may ignore this "plugin" or you may delete this .dll (it used only for Russian localization of plugin and is anyway ignored if your regional settings in not Russian).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 14, 2011, 04:55:11 PM
Is there a way to create an action that performs something like "Wipe unneeded tags"?
...
Lore
MB API doesn't provide function to delete tags. Possibly set_tag command is smart enough to delete tag at all if it has empty value. It better to ask Steven about this. If so you can copy some certainly empty tag (eg Custom9) to wiped tag for selected tracks. Also if its so I can allow to use <Empty value> source pseudo tag in copy command without the requirement to set custom text.
Title: Re: Additional Tagging and Reporting Tools
Post by: jrlx on July 14, 2011, 05:06:37 PM
It seems that you didnt keep folder structure unzipping archive. mb_tagtools.resources.dll should be in 'ru' subfolder of plugins folder and therefore shouldn't be displayed in prefs/plugins. You may ignore this "plugin" or you may delete this .dll (it used only for Russian localization of plugin and is anyway ignored if your regional settings in not Russian).

You are right. It's ok now. Thanks for the clarification.

Title: Re: Additional Tagging and Reporting Tools
Post by: cartman005 on July 14, 2011, 05:12:38 PM
Is there a way to create an action that performs something like "Wipe unneeded tags"?
...
Lore
MB API doesn't provide function to delete tags. Possibly set_tag command is smart enough to delete tag at all if it has empty value. It better to ask Steven about this. If so you can copy some certainly empty tag (eg Custom9) to wiped tag for selected tracks. Also if its so I can allow to use <Empty value> source pseudo tag in copy command without the requirement to set custom text.

That's too bad. I agree that it would be a good feature. Maybe in the future.
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on July 14, 2011, 05:38:21 PM
I've tested the latest beta of additional tagging tools plugin with MB 1.3.4212 and it seems to work as expected.
Note that when I ran it immediately after installation (namely after copying the *.dll to the Plugins subfolder) all the plugin commands were shown twice (Copy tag..., Swap tags..., Auto rate tracks ... and all the same below). Fortunately, when I close MB and restart the system the problem has gone.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on July 16, 2011, 01:56:54 PM
Maybe I lost track of how many stupid pills I took this morning, but I can't see the additional tools.  

I'm running MB 1.3.4213.  I dragged the 2011-07-14 beta dll from the zip and dropped it in g:\MusicBee\Plugins.  It's there and I see it.  I launch MB, click on TOOLS | Tagging Tools | Advanced and all that's there is "Synchronize Tags"

Am I looking in the right place for the advanced tagging tools?  

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: ma_t14 on July 16, 2011, 01:58:05 PM
Is the plugin enabled in preferences?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on July 16, 2011, 02:09:27 PM
GRRRRRrrrrr!!!
I -told- you I took too many stupid pills this morning.

No, of course it wasn't enabled in Preferences.  But now it is, and the additional tools are there.

I gotta find a way to get off these pills.

Thanks ma_t14
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on July 16, 2011, 02:13:28 PM
i've set up a topic to get peoples opinion about whether plugins should be enabled by default
http://getmusicbee.com/forum/index.php?topic=3956.0
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 16, 2011, 04:31:37 PM
Is there a way to create an action that performs something like "Wipe unneeded tags"?
...
Lore
MB API doesn't provide function to delete tags. Possibly set_tag command is smart enough to delete tag at all if it has empty value. It better to ask Steven about this. If so you can copy some certainly empty tag (eg Custom9) to wiped tag for selected tracks. Also if its so I can allow to use <Empty value> source pseudo tag in copy command without the requirement to set custom text.

That's too bad. I agree that it would be a good feature. Maybe in the future.

I dont think so. Currently API functions are intended to work with MB's interpretation of tags and this interpretation may be only partially mapped to tags in files, i.e. MB's tags can have different tag names for different file formats or may be stored in cache only. This is not intended for direct editing tags in files. Also there may be *a really many tags* stored in files that are invisible in MB interface at all.

I suggest that most useful feature for direct editing tags of files may be to implement tag inspector for multiple files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 16, 2011, 07:20:08 PM
I've tested the latest beta of additional tagging tools plugin with MB 1.3.4212 and it seems to work as expected.
Note that when I ran it immediately after installation (namely after copying the *.dll to the Plugins subfolder) all the plugin commands were shown twice (Copy tag..., Swap tags..., Auto rate tracks ... and all the same below). Fortunately, when I close MB and restart the system the problem has gone.
Yes, Steven, there is some bug. After upgrading to 1.3.4213 all commands were shown twice. But after restarting MB all is normal. Not a big problem for me, but may be it should be fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 16, 2011, 08:57:23 PM
Steven, the problem with latest MB releases (which don't replace 'swap artist and title' menu item, but add new 'additional tagging tools' menu item) is that if you unload plugin and load it again then all plugin's menu items will appear twice. It seems that MB doesn't remove plugin's menu items on plugin unload.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on July 17, 2011, 06:26:36 PM
I'm still having an issue with "Change Case"... it seems that it's not ignoring the words in the "except for words" section. Am I doing it right?

(http://i.imgur.com/PrdtQ.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 18, 2011, 11:17:36 AM
I'm still having an issue with "Change Case"... it seems that it's not ignoring the words in the "except for words" section. Am I doing it right?
I don't understand what you want to get in the tag. 'Ignore' means 'do not change'. If you speak about letter 'a' in ignored words list then case of this letter is not changed.

P.S. Sometimes its impossible to get required letter casing in just one step. You can do multiple steps in this situation using 'Change case of new tag' button (this will reapply rules to generated but yet not saved new tag).

EDIT:
If you want lowercase service words (and, of, or, the), but capitalize all other words then you need to make 2 steps:

1. Untick 'Ignore words'. Lowercase every word.
2. Tick 'Ignore words'. Capitalize tag leaving ignored words as is.

There is no way to leave very many words as is (no 'change case only for words' option), but sometimes 'ignore words after symbols' option may useful.
Title: Re: Additional Tagging and Reporting Tools
Post by: jimmanningjr on July 18, 2011, 10:14:44 PM
Thank you so much for this plugin . This is exactly what i was looking for. After I installed it it took me a couple minutes to figure out that I had to go into Preferences to enable it.
Seems to have a problem with my library of 65,000 tracks...will not preview...I am going to see if I can get it to export...which is what I want it for anyway.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on July 18, 2011, 10:30:39 PM
After I installed it it took me a couple minutes to figure out that I had to go into Preferences to enable it.
i've changed that now for the latest version of MB - it now enables plugins by default
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on July 19, 2011, 04:10:17 PM
With the latest release, change case now works to how I expected!!!! Thanks so much for the addition :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on July 19, 2011, 10:25:31 PM
do people have any views about auto-rating the entire library? I do have a field available for this purpose (i just need to do some fairly minor things so it becomes visible in the GUI and selectable in queries)
so you could still have a manual rating and have a auto-rated field as well (when i was thinking of doing this functionality myself, one of the inputs to an autorating was going to be the manual rating when it was available)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 20, 2011, 09:51:32 AM
do people have any views about auto-rating the entire library? I do have a field available for this purpose (i just need to do some fairly minor things so it becomes visible in the GUI and selectable in queries)
so you could still have a manual rating and have a auto-rated field as well (when i was thinking of doing this functionality myself, one of the inputs to an autorating was going to be the manual rating when it was available)
Steven, unfortunately I didn't get any feedback about auto-rating command at all. It was so many times requested and it seems nobody uses it.

About dedicated 'auto rating' field: I think it would very convenient to have this field in UI and it may be very easily added to the command (like any other tag, but currently I don't see any sense to save auto-rating in tags other then 'album rating', 'track rating' and custom tags).

Suggest its possible to define virtual tag that displays manual rating if its available and 'auto rating' otherwise (though I'm not sure how to 'unrate' track (its not the same as 0 stars) and how to get 'unrated' value).

EDIT:
Nope. Virtual tag cannot be displayed as stars. Well, its possible to modify command, so any manual rating (if present) will override auto-calculated value.
Title: Re: Additional Tagging and Reporting Tools
Post by: cartman005 on July 20, 2011, 04:08:05 PM
boroda, I have installed your plugin but I haven't gotten a chance to try out the autorating feature. I am worried if I don't like the outcome, I will have to restore my library from backup as I have already manually rated my library. Steven's idea sounds cool in that it would allow for the both to coexist. I am also surprised that there hasn't been more feedback regarding autorating. Maybe a separate topic would help?
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 20, 2011, 05:04:31 PM
Steven, unfortunately I didn't get any feedback about auto-rating command at all. It was so many times requested and it seems nobody uses it.

I'm not sure I understand I understand Steven's comment about the auto rating field but I can give feed back on the auto rating with this plugin.

I tend not to use ratings but I have dabbled a little with the AutoAccurate script when I used MM. I found that quite useful and it seemed to work but unfortunately I haven't got much use out of this one. I did run it, took a while with 20,000 songs but I realised a big flaw in it (for me at least).

I don't tend to play a song more than once a day so it seems impossible to set up auto rating in this plugin that gives any accuracy. It seems that whatever settings I use, with me not playing a song more than once a day, that everything will get more or less the same rating. I would prefer it to be based on track count in total and/or skip count.

It's not a biggie for me as I don't really use ratings. Maybe I'm using it incorrectly though?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 20, 2011, 05:59:48 PM
I don't tend to play a song more than once a day so it seems impossible to set up auto rating in this plugin that gives any accuracy. It seems that whatever settings I use, with me not playing a song more than once a day, that everything will get more or less the same rating. I would prefer it to be based on track count in total and/or skip count.
Hmmm... 'Plays per day' used for calculations is not an integer number (not only 0, 1, 2, 3, etc.). Its a fractional number (more exactly floating point number), it may be 0.0001 which means that you play track 1 time per 10000 days (on the average). Actually maximum 'plays per day' (for mostly played tracks) in my library is about 0.042 (much lesser than 1). Is doesn't somehow interfere with calculation of auto-rating.

EDIT:
Exact 'plays per day' values are not interesting at all. Its only service info. You may use 'Max. plays per day' and 'Average plays per day' hints in the command to set up thresholds manually or you may don't care about 'play per day' at all using 'auto-calulate thresholds' command. This command allows you to define that (for example) 5% of mostly played tracks must have 5-star rating, 10% of the rest of mostly played tracks must have 4-star rating, etc. 'Plays per day' thresholds still will be displayed in UI, but you can ignore (but do not change manually) these values.
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 20, 2011, 08:20:52 PM
Ah I see, I understand now (I think). Thanks for explaining.

I'm having a problem though, it keeps crashing on me. I set the percentages and change the standard rating for unplayed tracks to 0, click the auto calculate threshold at start up (will this scan my library every time I start MB?), and auto rate automatically if the track is changed. Then I press save settings.

This part is ok but what do I do after that? I try to close because I thought it would rate everything on the next start up but pressing Close crashes the MB.

Is it rating everything when I click Save Settings? There's no way to see if it is performing some activity.

By the way, I would like to say thanks for this plugin, the other features have been very useful.

EDIT: actually it seems that even if I just open the auto rate option box and press close without doing anything then it crashes/freezes MB.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 20, 2011, 11:53:35 PM
Clicking on 'Save setting' only saves settings and doesn't do anything else. 'Close' just closes the window.

What version of MB do you use? For 1.3.4216 all works fine for me.

P.S. You need to manually auto-rate all tracks of your library first (select all tracks (this can be done without closing 'auto rate' window) and click 'Calculate thresholds', then 'Auto rate now') because 'auto rate automatically if the track is changed' will only update auto-rating of playing tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 21, 2011, 01:31:38 AM
I'm using 1.3.4216.

I can't get the settings to save and just opening and closing crashes (not responding to be more specific) MB (possibly the reason for the settings not saving).

I did try to set up some albums (not all because it would take far too long) and I could see the rating in the custom9 field so it is working.

I still find it confusing though to be honest. Would some presets be a possibility for a future update?

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 21, 2011, 02:14:57 AM
I can't get the settings to save and just opening and closing crashes (not responding to be more specific) MB (possibly the reason for the settings not saving).
Actually 'auto rate' window calculates max. and avg. 'plays per day' just when window is opened. May be this is the issue? How large is your library? For me (~14 000 tracks) opening of window takes less than 1 sec. Anyway nothing is done when you close the window. And saving settings takes only milliseconds (they are saved to memory and saved to file only when MB exits).

I still find it confusing though to be honest. Would some presets be a possibility for a future update?
Do you mean presets of percentages for calculation of thresholds? I'm doubtful that somebody will constantly change presets. Percentages are actually set-and-use settings.
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 21, 2011, 04:45:19 AM
My library is 172gb. The opening of the window is not the issue, it opens pretty much as soon as I've clicked on the the option in the menu. I don't know what's going on, just that nothing is saving and it crashes every time I try to close the window, no matter how long I've had the window open for.

I don't know what's going on with it, I guess I'll just have to give up, I can live without it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 21, 2011, 03:52:19 PM
My library is 172gb. The opening of the window is not the issue, it opens pretty much as soon as I've clicked on the the option in the menu. I don't know what's going on, just that nothing is saving and it crashes every time I try to close the window, no matter how long I've had the window open for.

I don't know what's going on with it, I guess I'll just have to give up, I can live without it.
The last question. After 'auto rate' window is opened you can do anything: change settings, run 'Auto rate now' and 'Calculate thresholds' commands, even 'Save settings'? But clicking on 'Close' button freezes MB?
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 21, 2011, 06:44:31 PM
Yes, everything works fine as far as I can see except when I try to close the window.

I have noticed one other bug with it, when I change the percentages they often revert to 1 after I have put a number in a clicked away (to the next box).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 21, 2011, 08:49:45 PM
Yes, everything works fine as far as I can see except when I try to close the window.
If you opens window and immediately closes it then the same happens? And if you close window by clicking 'X' button on the top right corner of window also? Very strange.

I have noticed one other bug with it, when I change the percentages they often revert to 1 after I have put a number in a clicked away (to the next box).
Its because you dont't tick 'Set stars if' checkbox first. But this is bug. I'll fix it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 21, 2011, 09:00:58 PM
beeing good, I've cleaned up source code for 'Auto rate' command (for my own reasons). Could you try latest version? But if it doesn't solve freezing UI, I probably can't help more.
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 21, 2011, 10:18:25 PM
That's fixed it, no more crashes now. Thanks for the fix.

So...I have tried to set percentages and then press the calculate thresholds button but it results in 0 in all the boxes in the play count (before it set numbers in there). Sorry to be so stupid with this. As you can see from the playcount/custom9 field this results in seemingly random ratings. What am I doing wrong?

(http://img718.imageshack.us/img718/1514/clipboard02tu.jpg) (http://imageshack.us/photo/my-images/718/clipboard02tu.jpg/)

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 22, 2011, 01:04:36 AM
I need to see 'date added' and 'last played' tags also. 5-star rating is calculated rating (100% of ever played tracks in your case). 0-star is default rating for never played tracks. Track is considered to be never played even it was played, but is added to library today or yesterday. 'Plays per day' = ('Play count' - 'Skip count'') / ('Last played' - 'Date added'). If ('Last played' - 'Date added') < 1 day (i.e 0) then default rating is assigned. Actual percentage always is equal or more than desirable. Its more if most tracks have the same 'plays per day' value and its impossible to split library into groups on the basis of 'ppd'.

I can modify command so that ('Last played' - 'Date added') might be non-integer value, but this can help to differentiate only very recently added tracks or tracks that were played right after importing to library and were forgotten since that time. 
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on July 22, 2011, 04:50:59 AM
Ok thanks boroda, I will run it on the whole library and see how it works out after a while of building up some plays.
Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 22, 2011, 05:28:53 AM
I've modified command so that ('Last played' - 'Date added') is now non-integer value. I think its right because 0/0 = 'unknown value' (never played tracks) and 1/0 = 'infinity' (high 'ppd' - recently added tracks). 'Unknown' is not equal 'infinity' :)

Also I've added some new options.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 22, 2011, 09:56:06 PM
Added 'Settings' command which allows users to configure plugin. See 1st post on this topic for details.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 29, 2011, 07:14:20 PM
New command is added. See 1st post on this topic for details.
Title: Re: Additional Tagging and Reporting Tools
Post by: percy74 on August 02, 2011, 12:23:40 AM
I'm a bit late to the party here, but I thought I'd give some feedback on the auto-rating feature.  The formula seems a bit odd to me. Because it calculates the number of days between the date it was added, and the date it was last played, each track is rated on a different scale.  Here's an illustration of what I mean:

I set up MusicBee and imported all of my music files on Feb. 7 of this year.  That day I played a bunch of tracks.  Some of the tracks I played that day, I haven't played since.  It's now August 1, nearly 6 months later, but the plays per day for some of those tracks are very close to 1, which gives them the highest ratings in my library.  In most cases, I wouldn't give a higher rating to a track I've played once in the last 6 months, than to a track I've played, say, 20 times in the last 6 months.  I don't know if it's possible, but it would make sense to me to adjust the formula to (plays - skips)/(TodaysDate - DateAdded) so it would calculate the plays per day since the track was added, rather than between the date added and the last time it was played.

Other than that, it's awesome.  I'm still playing around with it, but love what I've discovered so far.  Great job!   :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on August 02, 2011, 05:46:56 AM
Hello! Unfortunately I had to remove this plugin... ever since I made auto-rate work from setup, it won't allow me to do anything else related to the plugin until it finishes... which, after a few days, still hasn't completed. I know I have a large library -- over 26,000 songs and just over 200GB worth of music-- but I don't think it should take that long to complete auto-rate. In addition, it also seems to have slowed MB to such a crawl that I have to use task manager to stop it. Finally, even if I uninstall and manually remove the plugin from the MB folder, if I reinstall the plugin (either beta or stable), auto-rate seems to start up again.  :'( :'( :'( :'(

I REALLY like this plugin and it saddens me that it will not work well with MB.
Title: Re: Additional Tagging and Reporting Tools
Post by: kstuart on August 04, 2011, 03:16:04 AM
The top post has a Stable download and a Beta download - but no indication of what the difference is - either in terms of version number or in terms of date or in terms of features.   There is a list of changes by date, but no indication of whether they apply to stable or beta...

And Banba is probably my least favorite Clannad. ;)
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 06, 2011, 07:57:43 AM
Hi boroda,
I have been playing with your tagging plugin. I'm finding it very useful, thank you.
I have been using the command copy to another field.
My cd albums which I am ripping to mp3 all have  index numbers on them. What I want to do is copy all these from the index field to a field where they can be sorted on. eg custom 3 field. I have entered the album index number into the start of the comments field with my ripping program. They have been entered as 1,2,3,4,5, etc and as you would know, to sort them I should have had 00001,00002 etc. I need 5 digits to cover the amount of albums I may have in the future.

Is it possible to have a routine that will add preceding "0's" to the copied number to make the number up to say 5 digits and exclude any other information from the copied field. Eg in a field that contained  number one it would transfer as 00001, 11 to 00011, 111 to 00111, 10000abcdefg would become 10000.
I realize this is a big ask, but you don't know unless you ask.
Any other ideas on how to achieve this would be welcome. thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 09, 2011, 11:36:52 PM
Sorry for late answers, my main computer is broken now and I cant see the source code or modify it currentlly. I'll try to answer all last posts in ondrer by memory and try to check and fix reported issues later, but I'm not sure when exectly.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 09, 2011, 11:53:02 PM
I set up MusicBee and imported all of my music files on Feb. 7 of this year.  That day I played a bunch of tracks.  Some of the tracks I played that day, I haven't played since.  It's now August 1, nearly 6 months later, but the plays per day for some of those tracks are very close to 1, which gives them the highest ratings in my library.  In most cases, I wouldn't give a higher rating to a track I've played once in the last 6 months, than to a track I've played, say, 20 times in the last 6 months.  I don't know if it's possible, but it would make sense to me to adjust the formula to (plays - skips)/(TodaysDate - DateAdded) so it would calculate the plays per day since the track was added, rather than between the date added and the last time it was played.
Real formula must be 'Plays-Skips/LastPlayed-FirstPlayed', not DateAdded. By FirstPlayed is not supporeted by MB and using DateAdded is a good approximation. Suggested by you formula is quite different, though it is reasonable. I could implement it as an option.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 10, 2011, 12:08:14 AM
Hello! Unfortunately I had to remove this plugin... ever since I made auto-rate work from setup, it won't allow me to do anything else related to the plugin until it finishes... which, after a few days, still hasn't completed. I know I have a large library -- over 26,000 songs and just over 200GB worth of music-- but I don't think it should take that long to complete auto-rate. In addition, it also seems to have slowed MB to such a crawl that I have to use task manager to stop it. Finally, even if I uninstall and manually remove the plugin from the MB folder, if I reinstall the plugin (either beta or stable), auto-rate seems to start up again.  :'( :'( :'( :'(
I don't recommend you to use 'auto-rate at startup' option at all. Its better to autorate all tracks manually first (although you cant use MB until process is finished), then check 'auto rate tracks if they are played' (this should happen mommentary for 1 track). Cant even imagine why initial auto-rating takes so long time. Cant check it now. Uninstallation doesnt remove settings file now, but you can delete it manually: see file like 'mb_TagTools.Settings.xml' in 'application data' dir (depends on your Windows version and if you run MB in portable mode).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 10, 2011, 12:17:46 AM
The top post has a Stable download and a Beta download - but no indication of what the difference is - either in terms of version number or in terms of date or in terms of features.   There is a list of changes by date, but no indication of whether they apply to stable or beta...
The only difference between beta and stable version is in the last command that is not fully implemented now. Either I'll wait until Steven adds support to MB for downloading custom presets or just will remove both 'download' buttons.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on August 10, 2011, 12:24:35 AM
I don't recommend you to use 'auto-rate at startup' option at all. Its better to autorate all tracks manually first (although you cant use MB until process is finished), then check 'auto rate tracks if they are played' (this should happen mommentary for 1 track). Cant even imagine why initial auto-rating takes so long time. Cant check it now. Uninstallation doesnt remove settings file now, but you can delete it manually: see file like 'mb_TagTools.Settings.xml' in 'application data' dir (depends on your Windows version and if you run MB in portable mode).

First off, hopefully your computer problems will be fixed; you are a valuable part of this community! Also, thanks for that info. Doing the above remedied the problem and the plugin now works as before.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 10, 2011, 12:28:33 AM
Is it possible to have a routine that will add preceding "0's" to the copied number to make the number up to say 5 digits and exclude any other information from the copied field. Eg in a field that contained  number one it would transfer as 00001, 11 to 00011, 111 to 00111, 10000abcdefg would become 10000.
I realize this is a big ask, but you don't know unless you ask.
Any other ideas on how to achieve this would be welcome. thanks.
I dont see C# help file now or MSDN, but can suggest that adding some more or less standard formatting (something like standard Excel formatting) should be very simple. Probably later.

EDIT:
I'm not sure what is the best way to sort *any* tag (I think Steven know it better), but 'export tags' command 1st tries to sort tags as integer, then (if conversion to integer failed) as floats, then (if conversion to float failed) as date-time, then as original strings. Maybe its better to request Steven to implement such sorting for all *custom* tags? (He can use my source code, but its written in c# and MB is written in VB). If Steven dont want to implement this, then of course I could implement this in copy/swap tags commands.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 10, 2011, 03:45:51 AM
thanks Boroda74, I'll wait to see if yourself or Stephen can implement this.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 11, 2011, 11:59:50 AM
thanks Boroda74, I'll wait to see if yourself or Stephen can implement this.
bluesbeat, install beta version of plugin, then download this 'advanced search and replace' preset  (http://www.mediafire.com/?n40n4qdgcj2dedt)to 'plugins/asr presets' folder (this folder should be already existing after installing plugin). Use 'Remove leading zeros' preset for selected tracks. It should work fine for examples given by you, but it would replace '00102b12' with '102', i.e all digits after first non-digit will be removed.

I'm happy that now there is one more use case for ASR commnd.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 11, 2011, 01:28:59 PM
Hi boroda74, unless I misunderstand you......what I wanted to do was add zeroes to the numbers so that they will sort properly, not remove the zeroes.
 I have a whole lot of index numbers in the comments tags and they don't sort properly eg 1,11,111 instead of 1,2,3,4,5 etc
Is this how all the tags sort, is there a better tag I should use for sorting by index number?
I need them to sort naturally, 1,2,3,4,5,6,7,8,9,10. 
By the look of your last message your preset will remove zeroes?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 11, 2011, 01:35:58 PM
Hi boroda74, unless I misunderstand you......what I wanted to do was add zeroes to the numbers so that they will sort properly, not remove the zeroes.
 I have a whole lot of index numbers in the comments tags and they don't sort properly eg 1,11,111 instead of 1,2,3,4,5 etc
Is this how all the tags sort, is there a better tag I should use for sorting by index number?
I need them to sort naturally, 1,2,3,4,5,6,7,8,9,10. 
By the look of your last message your preset will remove zeroes?
My mistake. But you can use preset partially to remove letters at the end of tag.

I need some time to think how your goal can be achived using regexp.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 11, 2011, 01:43:59 PM
thanks for your help.
Edit> by the way, i don't need to remove letters at the end of the tag, but I guess that may be handy for some other circumstance.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 11, 2011, 05:20:56 PM
Edit> by the way, i don't need to remove letters at the end of the tag, but I guess that may be handy for some other circumstance.
Eg in a field that contained  number one it would transfer as 00001, 11 to 00011, 111 to 00111, 10000abcdefg would become 10000.
Of course, this is unnessary for sorting only.

I didn't find the way to do what you want just in one step, but this is possible to do in 2 steps. Could you try these 2 presets (http://www.mediafire.com/?9rmsgmstkidqd2e)? You should 1st apply 'Add 4 leading zeros...' preset, then 'Extract 5 least chars...' for the same selected tracks. Probably I'll implement later more than 1 possible step in 1 preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 12, 2011, 12:53:58 AM
i'm not near my home computer at the moment, but will try tonight , thank you
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 12, 2011, 02:29:03 PM
That would seem to do the trick.
One last modification: Most of my comment tags have this in them-  number then text eg. 123 [space] text blah blah
Would it be possible to operate only on the numbers in the two step method above, but still leave the text in place?
That is, i want to end up with "04503 texttexttext".......in other words I don't want to remove any text.
I have copied all my comment tags to custon 3 just in case something goes wrong i can copy them back.
Also can you tell me if the custom tags in musicbee are actually written to the file or are they stored in musicbee?

thanks so much for your help.
EDIT: If there are no numbers at the start of the tag then nothing should be changed of course.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 12, 2011, 03:46:05 PM
That is, i want to end up with "04503 texttexttext".......in other words I don't want to remove any text.
Hmm... I thought you need to remove all text. I think its possble, but please confirm that you don't want to store 'index' and 'comment' in separate tags.

Also can you tell me if the custom tags in musicbee are actually written to the file or are they stored in musicbee?
Generally custom tags are strored in MB cache only unless you define some mapping to real tags. As far as I understand custom tag may be stored in real tag with any name, but other programs wont read such tags. Also its possible to map custom tag to any standard id3v2 or ape tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 12, 2011, 03:52:48 PM
Yes  I want the index and text all in the comment tag as in my ripping program it is easy to enter it there. Sometimes it is a bio on the artist and some times I just put the country of origin. They are all albums so shouldnt effect the sorting as the 5 digit number will be at the beginning of the tag.
This is something I should have told you at the beginning, sorry.
Also did you see my "edit" in the previous post?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 12, 2011, 04:17:17 PM
Yes  I want the index and text all in the comment tag as in my ripping program it is easy to enter it there. Sometimes it is a bio on the artist and some times I just put the country of origin. They are all albums so shouldnt effect the sorting as the 5 digit number will be at the beginning of the tag.
This is something I should have told you at the beginning, sorry.
No, your clarification was useful.

Also did you see my "edit" in the previous post?
Yes, but after I wrote my post.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 12, 2011, 07:53:15 PM
bluesbeat, try this presets (http://www.mediafire.com/?jrag25agkqqa3t0). I think you should delete previous presets because they have similar names and you don't need them.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 13, 2011, 05:00:12 AM
Well I tried that. This time it only added the 4 zero's to tags that had a number then text. Those fields that just had a number were not operated on.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 13, 2011, 08:43:08 AM
Hope this is (http://www.mediafire.com/?yp79gjhl3zeazm7) the final version :)
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 13, 2011, 09:05:58 AM
Thank you boroda74, I tried a small sample and that appears to work fine.
By the way the last preset adding the zero's took about 1 hour, during which music bee appears not to respond, but when the hard drive stopped flashing I figured it was done and closed the program from task manager. Iwas processing 210GB of files so probably why.

I am unsure what the buttons, submit, download new, dowload all are supposed to do? also unsure how "Tick presets which should be automatically applied if tags have changed?

Thank you once agin for your fine preset and patient help.
Geoff
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 13, 2011, 09:23:53 AM
By the way the last preset adding the zero's took about 1 hour, during which music bee appears not to respond, but when the hard drive stopped flashing I figured it was done and closed the program from task manager. Iwas processing 210GB of files so probably why.
I'm doubful that I can speedup this command, but 210GB is really large library (my library is ~40GB). Probably when the hard drive stopped flashing MB needs some time to refresh UI, but I wouldn't recommend to close MB from task manager.

I am unsure what the buttons, submit, download new, dowload all are supposed to do? also unsure how "Tick presets which should be automatically applied if tags have changed?
Its only a beta version of command. 'Submit' will e-mail me selected preset (this currenly works), both 'download' buttons don't work for now. Also there are a bugs with refreshing list of presets after creating/editing presets and creating/editing requires to run MB as admin, etc.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 14, 2011, 11:13:48 AM
boroda74, i dont know exactly what is being done but each plugin runs in its own thread so any tasks within the plugin shouldnt impact the MB GUI (apart from generally slowing down the computer of course). The only command which i expect you would be using that invokes the GUI thread is MB_RefreshPanels() and i wouldnt recommend using that too often as its a fairly expensive in terms of processing.

However, if you do anything in your plugin that invokes the MB GUI thread and runs that thread then it would lock up the MB GUI. As you have a dialog window I guess you might be doing that? If that is the case you could create your own thread when performing long tasks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 14, 2011, 01:04:30 PM
is MB_RefreshPanels() and i wouldnt recommend using that too often as its a fairly expensive in terms of processing.
I always call MB_RefreshPanels() only once after all file updates were done. Actually I think that MB_RefreshPanels() should be executed very quickly even if very large number of files were updated, so I'm not fully understanding how it can be that mb is still freezed and there is no hdd activity.

However, if you do anything in your plugin that invokes the MB GUI thread and runs that thread then it would lock up the MB GUI. As you have a dialog window I guess you might be doing that?
I'm not doing anything special to execute plugin in GUI thread.

each plugin runs in its own thread so any tasks within the plugin shouldnt impact the MB GUI (apart from generally slowing down the computer of course).
Yes, but this is true only when plugin command is invoked by receiving notification (like 'auto rate at startup' option which executes background task), but not when command is invoked from MB menu.

If that is the case you could create your own thread when performing long tasks
Yes, I thought about creating threads for long tasks, but there is problem: if one command executes QueryFiles/GetNextFile loop and another command (of the same plugin but in different thread) executes similar loop then 1st loop is terminated.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 14, 2011, 01:11:36 PM
On both occasions when I processed the batch for changes in the comments fields I waited until there was no hdd activity and then exited MB via task manager. I checked the tags and all appear to be processed. I am on Win 7 64 bit with a quad core processor....added that in case it helps.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 14, 2011, 01:28:25 PM
On both occasions when I processed the batch for changes in the comments fields I waited until there was no hdd activity and then exited MB via task manager.
How much time you were waiting between noticed no hdd activity and terminated MB from task manager?
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 14, 2011, 01:32:25 PM
each plugin runs in its own thread so any tasks within the plugin shouldnt impact the MB GUI (apart from generally slowing down the computer of course).
Yes, but this is true only when plugin command is invoked by receiving notification (like 'auto rate at startup' option which executes background task), but not when command is invoked from MB menu.
you are right about that and something i overlooked. I want to avoid as much as possible plugins interfering with the MB GUI, so i will look to have plugin commands that are invoked from the menu run in the plugin thread as well

If that is the case you could create your own thread when performing long tasks
Yes, I thought about creating threads for long tasks, but there is problem: if one command executes QueryFiles/GetNextFile loop and another command (of the same plugin but in different thread) executes similar loop then 1st loop is terminated.
that is right but is that really much of a problem? I dont think its too much of a restriction that the user can only run one tagging operation at a time and it would complicate things on the MB side. But if i address the first point above hopefully it will solve this issue, although i'm not sure how forms behave when created on their own thread - i do know its advisable not to access forms/controls and update them from a different thread.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 14, 2011, 01:56:18 PM
that is right but is that really much of a problem? I dont think its too much of a restriction that the user can only run one tagging operation at a time and it would complicate things on the MB side. But if i address the first point above hopefully it will solve this issue, although i'm not sure how forms behave when created on their own thread - i do know its advisable not to access forms/controls and update them from a different thread.
How plugin should notify user what is happening in friendly way? For example user opened several plugin windows then click 'Procced' in one window. What should be happened with other windows? Are they must just become disabled? Or clicking on 'procced' in other windows should display warning?

And the main problem: how user can terminate plugin background tasks?

I think it would be great if you provide a way to invoke 'MB background task' thread with some access to MB statusbar which already have means to terminate backgroud task.

EDIT:
I would want that plugin commands behave exactly as native commands.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 14, 2011, 02:10:09 PM
On both occasions when I processed the batch for changes in the comments fields I waited until there was no hdd activity and then exited MB via task manager.
How much time you were waiting between noticed no hdd activity and terminated MB from task manager?
Probably 10 minutes the first time and 5 minutes the second time.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 14, 2011, 02:23:48 PM
When you iterate through a query resultset, MB needs to keep a list of the matching files and the current position you have iterated to and there is no mechanism to associate a GetNext call with a specific query. The API is built around using standard string and integer datatypes so its easy to work with C++ - thats why it doesnt return an enumerator object for each query.
You could simply do a test when the user clicks Proceed and show a message if another of your commands is still running, or alternatively iterate though the query resultset quickly and build up your own internal resultset which you then use to run your file operations from.

MB internally has a class that can run tasks in the background and have them display the status on the taskbar with the termination button, so i will look to expose that via the API.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 14, 2011, 02:33:44 PM
You could simply do a test when the user clicks Proceed and show a message if another of your commands is still running, or alternatively iterate though the query resultset quickly and build up your own internal resultset which you then use to run your file operations from.
Very very good idea espesially about quickly querying files and stroring them in own list.

MB internally has a class that can run tasks in the background and have them display the status on the taskbar with the termination button, so i will look to expose that via the API.
Thanks.

By the way what MB displays in statusbar when 2 or more background tasks are performed? And how 'X' button in statusbar does work in this situation? Never ran 2 long background tasks simultaneously.
Title: Re: Additional Tagging and Reporting Tools
Post by: Elberet on August 14, 2011, 02:36:26 PM
The common way to do this is to have a central work queue. Whenever the user confirms an operation, an object representing that operation is pushed into the work queue and a thread backing the queue is pinged. The worker thread associated with the queue simply runs the operations in the queue in order and sleeps when the queue is empty. This provides serialization (i.e. operations which iterate through a library query do not overlap and close each others' queries) and you can add any kind of UI to this, such as a little window that pops up while the queue is non empty, showing a label for the operation in progress, a progress bar and an abort button. If you're careful not to do any actual work in that window's UI code (shouldn't be a problem, after all it merely controls the worker thread and doesn't do the actual work), you can even put this into the MB GUI thread without causing problems.

Steven, couldn't you return a query "handle"? The initual query returns a handle, GetNext requires this handle and once done, the handle is disposed with an EndQuery call. That'd allow for simulatenous queries in a C++-like fashion and C# devs could roll the handle into a custom enumerator which calls EndQuery upon disposal / finalization.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 14, 2011, 02:58:51 PM
This provides serialization (i.e. operations which iterate through a library query do not overlap and close each others' queries)
This is not very covinient for interactive operations (with UI). For example user opens 'Change case' command, clicks 'proceed', gets immediate responce 'operation is queued' then opens 'Copy tag' command. He will see old tag value in preview if tags are not changed by background task yet (but will be changed later).

Not sure how this should be properly organized.

Steven, couldn't you return a query "handle"? The initual query returns a handle, GetNext requires this handle and once done, the handle is disposed with an EndQuery call. That'd allow for simulatenous queries in a C++-like fashion and C# devs could roll the handle into a custom enumerator which calls EndQuery upon disposal / finalization.
This would be great.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 14, 2011, 04:53:54 PM
i'll add a way to get all query results in one go

and as mentioned i will expose the threadmanager class which also allows the taskbar to be updated with a status and ability to terminate the task. This class queues work items so they are executed in sequence

and lastly i'll look to invoke the menu callbacks on the plugin thread (rather than the GUI thread as now) - thats subject to input forms working normally when created and operated on in their own thread - not sure if that would cause any issues

edit:
i dont think its a good idea to create input forms in a thread as you cant set the owner to the musicbee application form. So i will leave the menu item callback as now (ie. in the GUI thread) on the basis that menu items are likley to be requireing some form of user interaction.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 14, 2011, 08:29:59 PM
API has been updated - see the MusicBee API topic for info on the new API and the updated interface definition file included with the examples: MusicBeeInterface.cs
http://getmusicbee.com/forum/index.php?topic=1972.msg22996#new

updated .exe required to support the new API methods:
http://www.mediafire.com/?xy72lud3hr129np
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 15, 2011, 03:08:07 AM
Does this mean I should remove the current plugin before updating MB? (in light of the new API)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 15, 2011, 06:19:15 AM
no, its backwards compatible - i expect boroda74 will make use of the new methods and provide an updated plugin at some point
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 15, 2011, 10:34:53 AM
New beta version is released. See 1st post on this topic for details.


P.S. Steven, I'll look later at new API. I've found that I don't need MB background task pool - I can manage it myself (all the same - I'm using some kind of serialization, more exactly commands cannot be overlapped). Also leaving menu items commands in GUI thread makes sense. But providing a way for working with statusbar text/buttons may be extremely useful.
Title: Re: Additional Tagging and Reporting Tools
Post by: percy74 on August 15, 2011, 08:47:53 PM
Thanks very much for the update boroda, especially the auto-tagging feature.  It's working great.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 15, 2011, 09:19:57 PM
Thanks very much for the update boroda, especially the auto-tagging feature.  It's working great.
What do you mean by auto-tagging feature?
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on August 15, 2011, 09:34:28 PM
Slight typo in "Advanced Search and Replace": Change multiple artit list from 'Artist1; Artist2' to 'Artist1 feat. Artist2'. Granted, it can be edited in the "Rename/Edit" section.
Title: Re: Additional Tagging and Reporting Tools
Post by: percy74 on August 17, 2011, 10:35:24 PM
Thanks very much for the update boroda, especially the auto-tagging feature.  It's working great.
What do you mean by auto-tagging feature?

Oh sorry.  I meant auto-rating feature. The "plays per days in library" option makes it work just the way I like.  Thanks for that.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 05:43:34 AM
Where do we get 1.3.4249 , 4243 seems to be the latest?
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 05:55:12 AM
ok, found it in the API forum. Must not be posted in the beta release forum yet.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 06:08:38 AM
I can only see the multiple artists plugin in Advanced search and replace box. I did delete most of the versions of the leadind zero's plugin except the version i may still use at some time. They appear to still be in the folder, just not visible in your plugin.

I am also getting this error when I close out of the plugin, and have to ctrl alt del to get out. I am on win 7 64bit
------------------------------------------------
MusicBee v1.3.4249.15886 (Win6.1), 21 Aug 2011 14:32:

System.ArgumentOutOfRangeException: Not a valid Win32 FileTime.
   at System.DateTime.ToFileTimeUtc()
   at System.IO.File.SetLastWriteTimeUtc(String path, DateTime lastWriteTimeUtc)
   at System.IO.FileSystemInfo.set_LastWriteTimeUtc(DateTime value)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.saveSettings()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.buttonCancel_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 21, 2011, 09:41:45 AM
Sorry that don't warn users. Latest version of plugin is not compatible with previous versions of presets and you should delete 'ASR Presets' folder before installing plugin. Preset that you need is included in archive, see 'Add up to 5 leading zeros to first digits of Custom9' preset. Alternatively you can open every existing preset in preset editor (after installing plugin) and click 'OK' to save preset in new format (probably it should work, not sure).
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 12:28:51 PM
I still get the error message when closing the advanced search and replace window?

Where do I find the "archive"?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 21, 2011, 12:55:20 PM
'Archive' is a .zip file you've probably downloaded. Just exit MB, delete 'Plugins\ASR Presets' folder and reinstall plugin after that (extract the content of downloaded .zip to 'Plugins' folder again).
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 01:10:51 PM
Yes I have already done that, but still get the error message
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 21, 2011, 01:12:00 PM
Forgot to mention that you need to import any new presets (including presets unpacked to 'ASR Presets' folder from 'official' plugin's .zip) to ASR command using 'Import new' or 'Import all' buttons.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 01:18:03 PM
I ticked then unticked the one preset that was there, and now I don't get the error. Just imported the other presets as well.
Not sure what was happening there, but seems ok now.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 21, 2011, 01:18:40 PM
There were many changes in presets handling in last few beta versions... Could you uninstall plugin (I mean clicking 'Uninstall' button in 'Edit/Prefs/Plugins' window, this should remove all automatically created files (which probably have obsolete format)), exit MB and reinstall plugin again.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 01:43:19 PM
tried to uninstall but it wouldn't remove the files. Uninstalled manually, reinstalled. All ok. then went to the configuration and changed a couple of settings under preferences/plugins. Now when i go to the advanced search and replace or to the configuration menu under plugins i get the following message-
MusicBee v1.3.4249.15886 (Win6.1), 21 Aug 2011 22:09:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.ToolsPluginTemplate.initializeForm()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.initializeForm()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin..ctor(Plugin inputTagToolsPlugin)
   at MusicBeePlugin.Plugin.asrEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I will uninstall again and try again.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on August 21, 2011, 01:49:20 PM
problem seems to occur when i select "use skin colors.." under configuration/Appearance. Can you replicate this? Also uninstall button does not uninstall the plugin still.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 21, 2011, 04:15:29 PM
clicking uninstall doesnt delete the .dll file in all cases at the moment. But any deletion of settings file could still be done by the plugin
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 21, 2011, 10:19:26 PM
problem seems to occur when i select "use skin colors.." under configuration/Appearance. Can you replicate this? Also uninstall button does not uninstall the plugin still.
Yes, I can reproduce this. Its very strange how this option can raise that exception. Need some time to determine whats the problem.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 22, 2011, 06:22:55 AM
Bug with 'use skin colors' option is fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on August 27, 2011, 03:21:20 AM
Hello! I keep getting this bug everytime I try to import the new presets:

Code
MusicBee v1.3.4255.31994 (Win6.1), 26 Aug 2011 19:20:

System.ArgumentOutOfRangeException: Not a valid Win32 FileTime.
   at System.DateTime.ToFileTimeUtc()
   at System.IO.File.SetLastWriteTimeUtc(String path, DateTime lastWriteTimeUtc)
   at System.IO.FileSystemInfo.set_LastWriteTimeUtc(DateTime value)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.saveSettings()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.import(Boolean importAll)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.buttonImportAll_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I'm on PST time (daylight savings is also in effect on my computer). It also makes it impossible to close the ASR window unless I use task manager to force close MB itself.
I'm using Windows 7 x64
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 27, 2011, 03:45:48 AM
It seems that bug with old presets is not yet fully fixed...

Could you try latest version (http://www.mediafire.com/?64u50xpxx984roc)?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 27, 2011, 03:55:17 AM
BTW, its better to delete all presets first (except for created by you - if any) or just delete 'ASR Presets' folder in your 'AppData' dir (this will do the same), because updated and old (coming from beta/RC version) presets have different names, but almost the same functionality.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on August 27, 2011, 05:42:21 AM
OK, did both, and re-downloaded the latest version, but now I have this issue:

Code
MusicBee v1.3.4255.31994 (Win6.1), 26 Aug 2011 21:41:

System.InvalidCastException: Unable to cast object of type 'System.String' to type 'Preset'.
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.presetList_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.CheckedListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.CheckedListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.CheckedListBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 27, 2011, 06:59:14 AM
Overlooked this issue (hope I'll stop changing preset's format in future). Try this version (http://www.mediafire.com/?b37sx368377o617).
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on August 27, 2011, 07:30:03 AM
And all is working again! Great and (Steven-like) fast fixing! Thank you!!
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on August 28, 2011, 05:02:02 PM
I do not understand the auto rating. I have set:

5 stars = 2 plays
4 stars = 1 plays
2 stars = 0 plays

But it still assigns five stars for one play time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 29, 2011, 04:26:46 AM
'Plays per day' equals to '(play count - skip count)/(last played - date added)' (and its a fractional number, i.e. it may be 0.001). I'm doubtful that any track in your library have 'plays per day' value equal to '2' (this would mean that you play this track 2 times per day on the average). You can use max./avg. plays per day hints on the left bottom corner of command window or don't care about 'plays per day' value and just set percentages of your tracks that must have certain auto-rating on the basis of 'pays per day'.
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on August 30, 2011, 08:41:45 PM
'Plays per day' equals to '(play count - skip count)/(last played - date added)' (and its a fractional number, i.e. it may be 0.001). I'm doubtful that any track in your library have 'plays per day' value equal to '2' (this would mean that you play this track 2 times per day on the average). You can use max./avg. plays per day hints on the left bottom corner of command window or don't care about 'plays per day' value and just set percentages of your tracks that must have certain auto-rating on the basis of 'pays per day'.

Hm, I really do not understand.
I want all the unplayed titles get 2 stars and the played tracks are automatically rated higher. What should I set it? Can you possibly show a screenshot?

Thank you.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 31, 2011, 12:28:47 AM
You should set 2 stars to 0 'ppd' tracks and other stars for greater 'ppd' values. Notice that standard rating for never played files deals with 'last played' tag - not with 'play count'/'skip count' (i.e. 'never palyed' tracks should have 'Unknown' 'last played' tag value). See auto-rating values in screenshot: 2, 4, 5. For tracks with greater than 0 'ppd' value you can set up percentages of tracks which must have certain rating (but keep in mind that its not always possible to satisfy your conditions for splitting library into groups with different rating (for instance if all tracks in your library have the same 'ppd' value then all tracks will be assigned highest possible rating). In case of usage of percentage you should calculate thresholds manually or every time on startup.

(http://www.mediafire.com/imgbnc.php/ebc6f9acd6c44d78a54f2d4f12a472cc0ded6905c276000af072e9ab88aba8026g.jpg)



EDIT: I've changed 'auto rate' command behavior for the next update so that if 'play count' is 0 then track is considered to be never played even if 'last played' tag is not equal to 'Unknown'.
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on August 31, 2011, 08:01:59 PM
yes thank you. now it works.
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on September 01, 2011, 10:19:31 PM
One question.
I set: store in rating auto tag "rating"
Now it is stored in two different tags. 5 stars in POPULARIMETER and 2 stars in RATING MM.

why not everything in the same tag? I've checked in MP3Tag.

(http://www.abload.de/thumb/bildschirminhalterfassou19.png) (http://www.abload.de/image.php?img=bildschirminhalterfassou19.png) (http://www.abload.de/thumb/bildschirminhalterfassiuxd.png) (http://www.abload.de/image.php?img=bildschirminhalterfassiuxd.png) (http://www.abload.de/thumb/bildschirminhalterfassnu0j.png) (http://www.abload.de/image.php?img=bildschirminhalterfassnu0j.png) (http://www.abload.de/thumb/bildschirminhalterfasskumh.png) (http://www.abload.de/image.php?img=bildschirminhalterfasskumh.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on September 01, 2011, 10:28:58 PM
its a mp3tag display thing - in all cases the tag is saved to POPM (check in the tag inspector)
mp3tag is trying to translate the POPM tag to a mediamonkey rating value
but mediamonkey changed its rating scheme a while ago
if you load the tracks into mediamonkey they should show the correct ratings
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on September 01, 2011, 10:33:02 PM
yes i checked it in the tag inspector. so it made me so suspicious.
But if it is correct, then I'm satisfied.

thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on September 02, 2011, 03:14:20 AM
A feature request: For the change case tagging tool (and others if applicable), I would like to see something telling me how many files were updated after everything finished.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 02, 2011, 04:33:19 AM
Maleko, yes, its good idea. I thought about some kind of 'statusbar' displaying number of displayed or selected/checked for updating/updated files. I'll try to implement this in future versions.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on September 07, 2011, 12:52:37 PM
The presets ASR archive appears to be no longer on mediafire?
Title: Re: Additional Tagging and Reporting Tools
Post by: ma_t14 on September 07, 2011, 02:32:13 PM
The ASR presets are now included in the plugin archive
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on September 07, 2011, 02:35:10 PM
yes sorry, I just realized that when I upgraded.
Title: Re: Additional Tagging and Reporting Tools
Post by: patocles on October 05, 2011, 05:28:08 PM
Hi, I got the plugin yesterday and whenever I try to export tags, in fact just the time I press 'preview' MB crashes.

I guess it must be due to the large amount of files I'm trying to manage (about 157.000 mp3 files, they weight more or less 1,08 TB on the hard disk) but I would like to ask you, if this is true, which is the maximum amount of files that the plugin could really manage, because it's the feature I'm most interested in.

Thank you all !!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 09, 2011, 04:38:57 PM
Plugin can easily manage ~15000 mp3's / 50 GB (size of my library). If you don't use <Tag counter> or <Tag value counter> fields then I don't see why 150000 mp3's should crash MB.

Can you filter out some subcontent of your library (eg using some playlist) and try to export sublibrary and provide feedback?
Title: Re: Additional Tagging and Reporting Tools
Post by: patocles on October 10, 2011, 04:11:06 PM
Thanks, boroda74:

I made a last test and the fact is that the plug in works but needs so much time to sort my library that it seems not to be working, so if you try to close the plug in window it appears that MB has crashed. Sorry for any inconvenience, great job ;-)

Best regards.
Title: Re: Additional Tagging and Reporting Tools
Post by: Greb on October 12, 2011, 10:29:44 AM
Congrats. Great plugin!!

(though comments in the source code are slightly difficult to understand  ;D)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 12, 2011, 09:07:18 PM
(though comments in the source code are slightly difficult to understand  ;D)
Sorry for my English :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Greb on October 13, 2011, 06:24:56 AM
Sorry for my English :)

Naaaa, don't worry, but it has quite a strong russian accent  ;D

(http://i53.tinypic.com/2s7ut7s.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 14, 2011, 09:33:41 AM
No, Greb, I didn't write this comment! :) This is automatically generated by VS and its not recommended to change it manually. Though usually you don't need even to see it, because this code should be edited in form editor.

btw, this comment says "don't change this code manually"... :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Merlin123 on October 18, 2011, 06:53:17 AM
Hi,

i'm looking for a solution to export my list of titles in a format which can be easily published on my website.
You're plugin support an HMTL export, but I'm missing to things:
1. Is it possible to sort the output (eg.: 1. Artist, 2. album, 3. track)?
2. Is it possible to create not a plain list but something like
    artist 1
    artist 2
    artist 3
   and when you click on artist 2 you get
   album 1
   album 2
   clicking on an album
   track 1
   track 2


Ou does anyboy know another plugin to do this?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 22, 2011, 07:52:43 PM
1. Sorting of table inherits the sorting of main panel view. You can define your custom sorting and then use 'export tags' command.,

2. Only by defining custom sorting.

P.S. Sorry for late answers, I didn't visit MB forum for a few days.
Title: Re: Additional Tagging and Reporting Tools
Post by: Antonski on November 01, 2011, 01:34:46 AM
Hi boroda74,

thank you for your plugin, good work!

I have one suggestion regarding 'Calculate average album ratings' command.
Can you make it (configurable perhaps) so that the plugin calculates the average album rating out of rated tracks only?
The reason is that I don't have enough time to listen to a full album recently, so I cannot rate all the tracks at ones. Instead, I listen randomly from all of my library and rate tracks from time to time. So it happens that there are really good albums in my library, but they have a low average rating, just because not all tracks are rated.
Do you think my request sounds reasonable?
Thanks in advance.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on November 01, 2011, 05:02:45 AM
+1 for that suggestion!
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on November 01, 2011, 02:18:44 PM
I would like to see the option of applying it to selected albums and/or just to the albums in the inbox.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2011, 06:33:56 PM
Hi boroda74,

thank you for your plugin, good work!

I have one suggestion regarding 'Calculate average album ratings' command.
Can you make it (configurable perhaps) so that the plugin calculates the average album rating out of rated tracks only?
The reason is that I don't have enough time to listen to a full album recently, so I cannot rate all the tracks at ones. Instead, I listen randomly from all of my library and rate tracks from time to time. So it happens that there are really good albums in my library, but they have a low average rating, just because not all tracks are rated.
Do you think my request sounds reasonable?
Thanks in advance.
Sounds reasonable. Steven, what's the difference between zero-rated and unrated songs in terms of api calls? Suggest that zero-rated songs should have rating "0" and unrated songs should have rating "" (empty string)

I would like to see the option of applying it to selected albums and/or just to the albums in the inbox.
Its possible but you have to select complete albums at this moment (there is no way to filter by albums in api calls currently).
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on November 03, 2011, 07:22:25 PM
i think thats what it would be doing
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on November 04, 2011, 12:07:35 AM
When I ran it on my collection it seemed to apply to the whole library regardless of what was highlighted, is that the intended behavior?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 04, 2011, 04:29:11 AM
When I ran it on my collection it seemed to apply to the whole library regardless of what was highlighted, is that the intended behavior?
At this moment, yes, intended.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on November 08, 2011, 02:07:11 PM
Thanks Boroda-
"1. 'Calculate average album ratings' command now ignores all unrated tracks to calculate averages.

Can this be optional please, can there be a switch to include/not include unrated tracks?
If I don't like some tracks on an album I don't rate them, therefore that should lower the album rating, imho.
I just want the average of all tracks, for standout tracks track rating is better.
I don't see much point in giving tracks one star rating as I probably won't listen to them, most of mine are between 2-5 stars, no star is not listened to much. thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 08, 2011, 03:43:54 PM
If I don't like some tracks on an album I don't rate them, therefore that should lower the album rating, imho.
You can make such tracks zero-rated. But, yes, this can be done as option.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 09, 2011, 04:25:58 AM
I've added this option.
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on November 10, 2011, 02:18:19 PM
This awesome plugin is so good that it should be distributed with the next major release of MusicBee.  8)

It has lots of useful features requested by many forum members and perfectly complements the main program.

What do you think ???
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 10, 2011, 05:14:39 PM
I have already suggested to Steven to make 'extended' installation package with all plugins included (though some plugins can be disabled by default).
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on November 10, 2011, 05:17:59 PM
I have already suggested to Steven to make 'extended' installation package with all plugins included (though some plugins can be disabled by default).

Good idea. +1 :)

BTW, I guess your plugin is available in Russian. Is it possible to get it in other languages supported with MusicBee  ???
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 10, 2011, 06:27:56 PM
BTW, I guess your plugin is available in Russian. Is it possible to get it in other languages supported with MusicBee  ???
Yes, plugin can be easily translated to any language, but I need translators.
Title: Re: Additional Tagging and Reporting Tools
Post by: Adson on November 11, 2011, 08:51:41 AM
+1  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: kruiz on December 01, 2011, 04:57:51 AM
Thanks a lot for this plugin, it's great stuff.

I'm beginner with regex, but I would like to learn. I can't figure out how to do this particular operation in Advance Search & Replace.

I have a lot of multiple-disc albums where the Track# tags are 101, 102, 103... 201, 202, 203 etc. The first digit is the disc number and the last two digits are the track number. I would like to search for any file where the Track# tag is three digits (characters), copy the first digit to the Disc# tag (which is currently null), and replace the three digits in Track# with only the last two digits.

It seems easy. I can search for a regex of "..." to find all three-character values in Track#. Are there functions for extracting substrings? The MSDN page is mind-boggling  :o

Thanks again.

Update: I tried this in TextPad which allows regex in search/replace.

Search: \([0-9]\)\([0-9]\)\([0-9]\)
Replace with: \1

For example, this matches "102" and replaces it with "1". But in this plugin, in Advanced Search & Replace, when I used these strings and try the Preview, it matches "102" and replaces it with "102". What am I doing wrong?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 04, 2011, 09:37:43 AM
I think search pattern should be (\d)(\d\d) and replacing pattern $1 and $2 for disk# and track# correspondingly.
Title: Re: Additional Tagging and Reporting Tools
Post by: kruiz on December 04, 2011, 04:33:22 PM
Excellent... I knew it should be easy! Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 05, 2011, 10:52:04 AM
kruiz, please share your ASR preset (select preset and click 'submit' button - this will send e-mail to me).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 06, 2011, 10:09:52 AM
.NET 4 version released.
Title: Re: Additional Tagging and Reporting Tools
Post by: Antkh on December 08, 2011, 05:27:13 PM
Can't download ASR-pack from the first post of this thread, "Invalid or Deleted File".
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 08, 2011, 06:05:02 PM
Its obsolete. All current presets are included in plugin zip.
Title: Re: Additional Tagging and Reporting Tools
Post by: Antkh on December 11, 2011, 11:38:00 AM
Some of my albums are with YEAR-tag "xx.yy.zzzz". How can i autocorrect them to show only year ("zzzz")?
Title: Re: Additional Tagging and Reporting Tools
Post by: Chinaski on December 11, 2011, 12:33:11 PM
Broked link to download presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: Antkh on December 11, 2011, 12:47:40 PM
Broked link to download presets.
See the post above by boroda74 - Its obsolete. All current presets are included in plugin zip.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 11, 2011, 02:28:55 PM
Some of my albums are with YEAR-tag "xx.yy.zzzz". How can i autocorrect them to show only year ("zzzz")?
Try to search (\d\d\.)(\d\d\.)(\d\d\d\d\) and replace with $3 in ASR command.
Title: Re: Additional Tagging and Reporting Tools
Post by: Antkh on December 11, 2011, 02:39:31 PM
Some of my albums are with YEAR-tag "xx.yy.zzzz". How can i autocorrect them to show only year ("zzzz")?
Try to search (\d\d\.)(\d\d\.)(\d\d\d\d\) and replace with $3 in ASR command.
So, I need to make a new filter in ASR presets menu? Were can I search it?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 11, 2011, 03:54:35 PM
Click 'create' button. Enter \d\d\.\d\d\.(\d\d\d\d) in the search pattern and $1 in the replace pattern, leave 2 optional steps blank. 
Title: Re: Additional Tagging and Reporting Tools
Post by: Antkh on December 11, 2011, 04:23:07 PM
Click 'create' button. Enter \d\d\.\d\d\.(\d\d\d\d) in the search pattern and $1 in the replace pattern, leave 2 optional steps blank. 
Works perfect, thank you!!!
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on December 21, 2011, 01:21:34 AM
OK, I'm sure ASR can do this, but I'm not sure how to do it. So, I have an album that has several "Feat. blah blah blah" for the artist field. I want to be able to put the "Feat. blah blah blah" part of the field to the end of the title of the appropriate tracks. So, for example:

Old:

Artist: Artist1 Feat. SubArtist
Title: Title1

New:

Artist: Artist1
Title: Title1 (feat. SubArtist)

How can that be done?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 22, 2011, 02:26:44 PM
ASR cant append one tag (or part of tag) to another, so you need to use combination of 'copy tag' and ASR commands. Maleko, I didnt test the following, so use this with caution:

FIRST: search for .*?\s+(feat\.\s.*)$ in 'artist' tag and replace with ($1) in some temp tag (eg custom9).
THEN: append ('copy tag') custom9 to the end of 'title' tag placing between them one space.
THEN: search for (.*?)\s+feat\.\s.*$ in artist tag and replace with $1 in artist tag.

P.S. You can combine 1st and 3d replacings as first 2 steps in ASR preset (leave 3d step blank), then append custom9 to title.

EDITED - slashes replaced by backslashes - now patterns should be correct
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on December 22, 2011, 05:13:10 PM
Thanks boroda74! When I said "ASR," I meant the entire suite of tools you developed. I also tweaked it a bit (now, in the first step, it does a search for "Featuring" and replaces it with "feat."). I love how powerful this plugin is :)
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 01:58:05 AM
Hi boroda, thanks for update. I am wondering if the zero rated tracks feature is broken? eg I have a 13 track cd with 4 tracks rated at 3 stars each, with this feature on or off the album still gets rated at 3 stars. Is this right? I am performing the operation in the inbox.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2012, 02:11:02 AM
Working for me. Are you sure that 'Treat unrated tracks as zero-rated' option is ticked?
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 02:22:17 AM
Yes, Ive tried both ways. It must have something to do with files. I have another album with 15 tracks 2 of which have 3 stars and the rest zero....the difference there is with treat zero rated tracks on Album = half star, off= 3 stars.
Both albums are VBR 0 encoded, I can't tell what is different between the files.
Edit: Both albums are ID3v2.3 and both are ncoded with Lame 3.98.4
Title: Re: Additional Tagging and Reporting Tools
Post by: paq on January 15, 2012, 02:41:31 AM
Is "auto-calculate album rating" in Preferences > Tags (1) enabled or disabled?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2012, 03:02:27 AM
paq, excellent! :)
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 07:55:21 AM
It is not enabled
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2012, 10:59:44 AM
If you change tracks rating from 1st album from unrated to 0-rated, then all works?
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 11:13:20 AM
No, as I said, whether I have it zero rated or unrated I still get the same result, 3 star album.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2012, 11:45:18 AM
I meant 'if you change track rating in tag editor', not 'if you tick option in plugin'.

Could you copy rating tag for 1 wrong track to temp custom tag and check it in tag editor? What is raw value?
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 11:58:17 AM

The little symbol that appears like a six with the round bit filled in, does that mean zero rated? I do not rate them zero to start with.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2012, 12:40:25 PM
You just have some dirt in rating tag of several files. Plugin never raises type conversion exceptions, for example if conversion from string to number is failed then 0 is used, suggest that MB does the same for displaying ratings.

Unrated track should have empty string in rating tag. 0-rated - string "0" (you wouldnt see " in tag editor).

Select all wrong tracks, open tag editor, set 5 star rating, then set 'unrated' (bomb) value.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 01:12:30 PM
not sure I understand what you mean.
There are several albums that only have two or three tracks rated, rest are unrated yet album rating is the same as the two or three 3star tracks?

The only way it seems to give a true album rating is if I manually change all my unrated tracks to zero rated tracks first.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2012, 01:37:00 PM
Unrated tracks of some albums are not really unrated, they are just displayed as unrated, but actually contains dirt in rating tag.

Rating tag should always contain (may be fractional) number. If you copy rating to custom tag it should be either empty (unrated) or contain numbers 0, 0.5, 1, 1.5, ... 4.5, 5

You should manually rate these tracks to overwrite incorrect values (yes, you can manually force 'unrated' status - bomb icon - instead of no stars).

P.S. Everywhere in this post I spoke about track rating. If track rating is correct for all tracks then album rating will be correctly calculated.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on January 15, 2012, 01:53:45 PM
thanks Boroda for clarification, I was not aware that there could be 'dirt' in the track rating tag. I will force the bomb on unrated soon as I get time on the entire collection.
Title: Re: Additional Tagging and Reporting Tools
Post by: tcman50 on February 02, 2012, 01:45:33 PM
Not to beat a dead horse again but I will, I still can't get export tag to give me an album duration, from the fields in the left I an choosing in order, album artist, album, time, tag counter value which them spits out the values but when i go to hit the save button to save the album durations as tag custom 9 it comes back and says no url tag field, what does that mean?

thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 02, 2012, 06:46:58 PM
You need to add 'URL' tag to save something in custom tag. Just add 'URL' tag (track path/filename) to the end of table tag columns (i.e. add tags in the table in order: 'album artist', 'album', 'time', '<tag counter value>', 'URL', <something else, but its useless for saving 'tag counter value', may be useful only for exporting tags to external file>). I'll change command description to make it more intuitive.
Title: Re: Additional Tagging and Reporting Tools
Post by: bryankook on February 04, 2012, 02:31:19 PM
Is a translation into german still needed? I could do that  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2012, 05:23:10 PM
Of course, just download these files (http://www.mediafire.com/download.php?u8k8mdjml3ldmli) and translate them. Read 'README.txt' first. Then send me translated files, so I could integrate them to plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on March 18, 2012, 01:26:10 PM
Hi boroda74.
Re: calculate average album ratings.  When this is used and I then backup up my music files from one drive to another it takes a long time because it copies all files. My question is: even for album ratings that have not changed is this calculated as well? I think it must change the date attribute on all files? Is there a way it can only operate on new files or files where the rating has changed so that I'm not backing up everything? I also would prefer to have the option to perform this on just the inbox so I can calculate on just new files? thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2012, 04:22:28 AM
My question is: even for album ratings that have not changed is this calculated as well?
Yes.

I think it must change the date attribute on all files?
It depends on how you store 'album rating' (either in MB cache only or in files).

Is there a way it can only operate on new files or files where the rating has changed so that I'm not backing up everything?
Currently there is no way to do this, but I think this is a good idea. I'll implement this later.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2012, 10:49:15 PM
Hi boroda74.
Re: calculate average album ratings.  When this is used and I then backup up my music files from one drive to another it takes a long time because it copies all files. My question is: even for album ratings that have not changed is this calculated as well? I think it must change the date attribute on all files? Is there a way it can only operate on new files or files where the rating has changed so that I'm not backing up everything? I also would prefer to have the option to perform this on just the inbox so I can calculate on just new files? thanks.
Its done.
Title: Re: Additional Tagging and Reporting Tools
Post by: ma_t14 on May 12, 2012, 04:11:25 PM
Is it possible to copy a specific tag from one file to another? I couldn't find such an option. I want to transfer playcounts between files
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2012, 05:13:04 PM
No and I don't see simple way to do this. You should select exactly the same number of files for copying and pasting and in the same order. BTW MB internally can copy/paste tags (not sure how it deals with multiple files).
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on June 19, 2012, 03:01:44 PM
Hi boroda74!

It has been a while (4 months) since bryankook offered his help for translation into German.

My question now is: Have you heard since then from him about the status of his translation?

I'm asking because I have also started to translate into German and 40% of the whole package are already translated by me.

Greetings

GoodWill41
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on June 22, 2012, 08:27:33 AM
Hi boroda74!

New information about status of German translation: 5 of 12 files (the bigger ones) to be translated.

Well, concerning the space, I have to admit that the translation is very difficult because I can only guess if it would fit. I can't see my results.

But as you stated in your initial post it is better for you to do it that way so it is ok for me.

Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on June 26, 2012, 03:11:56 PM
Is this plugin capable of extracting a certain part of a tag, and copy it to another?

e.g. when the 'Title' tag is:
Cello Sonata No.1 in E minor, Op.38 › I. Allegro non troppo

I want the part before ' › ' to be copied in a custom tag named 'Composition',
and the part after ' › ' copied to a custom tag named 'Movement'.

tia

edit:
I just learned how to accomplish this with MP3Tag.
Still curious if this would also be possible within MB though.
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on July 06, 2012, 10:05:54 AM
Hi boroda74!

Today I have got a question concerning the translation into German as follows:

File "TagTools.cs": I don't get the sense of the sentence in the section "default ASRPresetName" in the row beginning with "msgSwapTags SourceAndDestinationTagsAreThe Same". To me it seems that there is missing a word or more.

Could you please tell me which one(s) or explain the sense of that sentence.

BTW: That is the last missing file to complete my translation. After that I am going to start with the 56 XML-Preset-Files.

Thanks in advance!

Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on July 06, 2012, 10:11:59 AM
@jistme:

Well, I'm not 100% sure. Maybe there's a preset which is able to do that, but I haven't had a look at them yet. Or you have to create a preset for yourself.

Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on August 01, 2012, 07:38:01 PM
New status report for German translation:

20% of ASR-Presets (xml-files) have been translated,
1 file (txt-file) pending because of understanding (sense) difficulties. See my post dated 6th July 2012.

Greetings

GoodWill41
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on August 03, 2012, 07:38:16 PM
Here's a new status report:

22 ASR-Presets left to translate (60% of ASR-Presets translation finished),
1 file (txt-file - TagTools.cs) pending

Getting closer to the finish line....

Title: Re: Additional Tagging and Reporting Tools
Post by: bemis on August 09, 2012, 06:56:46 PM
hi,
i installed on my new laptop musicbee (the latest beta) and this plugin. but the autorating doesnt seem to work, it always shows "ever played tracks in your library: 0" i also installed the version 1.4 for testing and with this version it works like it should

Edit:
went back to MusicBee 2.0.4572, there it is working again
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on August 15, 2012, 06:02:51 PM
Hi boroda74!

I've finished German translation of the ASR Presets so far and sent you a PM with the download link.

1 file is still pending, waiting for your help.

Thanks in advance!

GoodWill41
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2012, 09:07:10 AM
Is this plugin capable of extracting a certain part of a tag, and copy it to another?

e.g. when the 'Title' tag is:
Cello Sonata No.1 in E minor, Op.38 › I. Allegro non troppo

I want the part before ' › ' to be copied in a custom tag named 'Composition',
and the part after ' › ' copied to a custom tag named 'Movement'.

tia

edit:
I just learned how to accomplish this with MP3Tag.
Still curious if this would also be possible within MB though.


Create new ASR preset. 1st step: search for (.*)›.* in title tag and replace with $1 in composition tag. 2nd step: search for .*›(.*) in title tag and replace with $1 in movement tag. Leave 3d step blank.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2012, 09:12:05 AM
Hi boroda74!

I've finished German translation of the ASR Presets so far and sent you a PM with the download link.

1 file is still pending, waiting for your help.

Thanks in advance!

GoodWill41

msgSwapTagsSourceAndDestinationTagsAreTheSame:

Using the same source tag and destination tag may be useful only for 'Artist'/'Composer' tags to convert ';' delimited tag value to the list of artists/composers (artist and composer tags support for multiple items) and vice versa. Nothing done.
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on August 16, 2012, 03:31:29 PM
Hi boroda74!

I have sent you a PM with the download link for the translation of the tagtools (.txt-files).

Concerning the PM you sent me today: Writing it that way here in the forum helped me a lot to get the sense of the sentence in that paragraph. Thanks for that.

GoodWill41

BTW: Sorry, I forgot to write a subject for my PM.

Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on August 30, 2012, 07:56:33 AM
Hi boroda74!

Well, here are my announced results (1 week ago in my last PM) I found out so far:

First, this is the status in my MusicBee plugin folder:

(http://img225.imageshack.us/img225/8679/pluginfolder1.jpg) (http://imageshack.us/photo/my-images/225/pluginfolder1.jpg/)

and this is what I found out:

1.) There is a mixture of German and French (yes, French) menu-items in the Extras-Menu (settings independent):

(http://img405.imageshack.us/img405/5185/musicbeegermanfrench.jpg) (http://imageshack.us/photo/my-images/405/musicbeegermanfrench.jpg/)

This happens due to the new file "mb_TagTools.dll" dated 2012/08/19. You sent me this together with the Beta-Version of the TagTools. The mixture does not happen when I take the old file dated 2012/05/12.

2.) So, this brought me to No. 2. I thought I should delete the folders named "fr" and "ru" to get rid of that mixture, but that results in English menu-items with German GUI.

3.) There are not always German tooltips, there are sometimes English ones, even in the same window:

(http://img651.imageshack.us/img651/7776/musicbeegertooltip.jpg) (http://imageshack.us/photo/my-images/651/musicbeegertooltip.jpg/)

This is a German tooltip in the Auto-Rate window.

And:

(http://img825.imageshack.us/img825/7408/musicbeeengtooltip.jpg) (http://imageshack.us/photo/my-images/825/musicbeeengtooltip.jpg/)

This is an English tooltip.

These two are only examples, there are more. If you choose the next item in the Auto-Rate window it would show an English tooltip.

So, that's all I found out so far.

Greetings

GoodWill41
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 31, 2012, 10:12:24 PM
GoodWill, thank you for your effort. I will post a new version of plugin with German localization on this weekend.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 31, 2012, 10:47:04 PM
GoodWill, please check localization of ASR Preset Editor window (I'm not sure if did that). To do this click 'Create' button in ASR command window (this will open ASR Preset Editor with new empty preset).
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on September 01, 2012, 11:42:23 AM
Hi boroda74!

Well, concerning Preset-Editor I found 4 issues by looking at the opened window and now I want to check my latest translation once again. So please, be patient. I am going to try hard delivering my results today (maybe late in the evening).

GoodWill41

Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on September 01, 2012, 03:48:33 PM
So, I am back again! And much earlier than expected.

My results:
1.) 2 of the 4 issues have already been fixed in my latest translation I had sent you.
2.) The other 2 issues are as followed:
a) Drop-Down-Menu not translated, and I am not able to do that because the menu-items are not addressed in any of the txt-files.
b) English Tooltip for "Custom Text" not translated, and I am not able to do that because it is not addressed in any of the txt-files.
For a and b see screenshots below:

a)

(http://img404.imageshack.us/img404/4641/musicbeepreseted1.jpg) (http://imageshack.us/photo/my-images/404/musicbeepreseted1.jpg/)

b)

(http://img685.imageshack.us/img685/6374/musicbeepreseted2.jpg) (http://imageshack.us/photo/my-images/685/musicbeepreseted2.jpg/)

And I have investigated a little bit more concerning the English Tooltips not been translated into German:

1.) Auto-Rate: 4th Checkbox-Option on the left down-row (not able to translate, because it is not addressed in any txt-file)
2.) Advanced Search and Replace: upper row of buttons - first 4 ones (not able to translate, because it is not addressed in any txt-file)
3.) Change Case: That is the one I have already mentioned before (See screenshot above in my earlier post). Here I am also not able to translate, because it is not addressed in any txt-file.

Now, I hope that are all issues that can be found.

GoodWill41
Title: Re: Additional Tagging and Reporting Tools
Post by: pvoulou on September 03, 2012, 06:54:26 PM
thank you very much
Title: Re: Additional Tagging and Reporting Tools
Post by: Moss on September 05, 2012, 07:12:14 AM
where can i find the german language file for this plugin?
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on September 05, 2012, 11:14:15 AM
Hello Moss!

I hope it is comming soon, because I have just finished translation into German. Boroda74 (the plugin developer) have to compile my translated files, so please, be patient.

Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on September 09, 2012, 03:20:19 PM
Hello.
For some time, the plugin seems to stop working correctly.
Playback is everywhere zero.

(http://www.abload.de/thumb/screen_120909_161653lhu8h.png) (http://www.abload.de/image.php?img=screen_120909_161653lhu8h.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on September 09, 2012, 07:55:23 PM
this MusicBee.exe update should fix the issue:
http://musicbee.niblseed.com/V2/MusicBee_Exe_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on September 10, 2012, 04:58:51 PM
this MusicBee.exe update should fix the issue:
http://musicbee.niblseed.com/V2/MusicBee_Exe_Patched.zip

Yes, works again. Thank you.
Title: Re: Additional Tagging and Reporting Tools
Post by: vaterp on September 10, 2012, 08:40:53 PM
Boroda, think this could be extended to allow for bulk tagging of play count and/or bulk synching of playcount with a special tag kept in the file? I have a bunch of custom tags in over 3000 files for play counts from other players that i would love to be able import into musicbee.

thx for consideration.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 15, 2012, 01:22:46 AM
MusicBee doesn't allow to write play/skip counts ((
Title: Re: Additional Tagging and Reporting Tools
Post by: duels on September 20, 2012, 04:39:37 PM
Can some please help, Where can I download this plugin from and installl it. Please new user Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: superstar19 on September 20, 2012, 09:57:42 PM
Thanks.  Just found these tools.  Even more reasons for me to forget about Mediamonkey.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 20, 2012, 10:28:37 PM
Can some please help, Where can I download this plugin from and installl it. Please new user Thanks
In the beginning of this topic, see first post.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 20, 2012, 10:29:23 PM
Thanks.  Just found these tools.  Even more reasons for me to forget about Mediamonkey.
Actually some commands were inspired by MM scripts.
Title: Re: Additional Tagging and Reporting Tools
Post by: Duels2 on September 21, 2012, 10:32:16 AM
Can some please help, Where can I download this plugin from and installl it. Please new user Thanks
In the beginning of this topic, see first post.

Thank you boroda74, but for the life of me I can't see where the link is in 1st post to download the plugin. Can you please post the link to me so I can download this amazing tool.

Joe
Title: Re: Additional Tagging and Reporting Tools
Post by: Duels2 on September 21, 2012, 02:33:31 PM
boroda,

I have managed to download your excellent plugin for Music Bee, Thank you so much for this, Can I ask one favour, a small addition.
Of all the libraries I have used none of them collect the Disc ID information this is the CD code to identfy the actual CD. The information is availble on freedb.org but to manually input this information into a large library of music would take forever to completed. Would it be possible to add this as a field in the tagging and reporting tools as part of the autotag and report.
Please click on the link an example fron freedb.org showing DISCID fb127c11 (Coldplay / Coldplay)
http://www.freedb.org/freedb/rock/fb127c11
Your help would be a realy help, thank you so much.

Joe
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 23, 2012, 01:46:04 PM
There is no autotag command in plugin. You can ask Steven about this addition to MB or you can use 'copy tag' command to manually fill disk id to all tracks of album (just select all tracks of album and fill in disk id in tag editor).
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on October 14, 2012, 11:53:39 AM
Hi Boroda,
Re Library reports:
I have been looking at your library reports under Advanced tags. Perhaps if I explain what I want to do-
basically I want to export an .m3u playlist to html so I can publish it onthe web. I have been able to do this, but one thing eludes me.....I want it to appear in the order as per the playlist order. I notice under the Playing Now screen the first column is "#", how can I sort my playlist export by this # column. An example of the table I need can be seen here (produced by another program) http://www.bluesbeatradio.com/930oct14.htm

Also is it possible to export the filepath, and which tag does the "URL" field equate to?
I do not understand the use of Function for new fields "Grouping" and calculate subgrouping totals?
Thanks for any help you can offer, i have only just started playing with the Library reports function, so I may have missed something obvious.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 17, 2012, 07:43:45 PM
I want it to appear in the order as per the playlist order.
I'll do this on weekend.

Also is it possible to export the filepath, and which tag does the "URL" field equate to?
'URL' is just a filepath for local files.

I do not understand the use of Function for new fields "Grouping" and calculate subgrouping totals?
Every function is calculated for every unique combination of grouping fields. For example you want to calculate duration of albums for every artist. Then you should define 2 grouping fields ('Artist' and 'Album') and 1 function field ('Time').

If you tick 'calculate subgrouping totals' option then duration will be calculated also for every 'Artist' (i.e. for 1st grouping filed, for every unique combination of 1st and 2nd grouping fields, for every unique combination of 1st, 2nd and 3d grouping fields, etc.).
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 19, 2012, 09:08:51 PM
Create new ASR preset. 1st step: search for (.*)›.* in title tag and replace with $1 in composition tag. 2nd step: search for .*›(.*) in title tag and replace with $1 in movement tag. Leave 3d step blank.

Thanks Boroda (I just now read your answer)
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 20, 2012, 04:52:57 PM
Hey Boroda,

In an endeavor to help somebody, and learn something myself on the side I am challenged with the following.

Suppose the three following possible title tags of a track:

"first-second-third-fourth.mp3"
"first-second.mp3"
"first second.mp3"

The wish is to have your tool find only the word "second" from the first two examples, and do nothing with the third example. (or any other form without at least one "-" )

The outcome ("second") is to be used to populate another tag.
(the title tag itself is not to be changed)

Having almost none knowledge with regex, I got some very helpful assistance from a regex forum, which suggested to use: (?<=^[^-]+-)[^-]+
This seems to indeed work perfectly when e.g. running it through a regex tester, but I can't for the life of me find out how to get the outcome in the field "replace by" in your tool.

Can it be done?

https://www.youtube.com/watch?v=KNnPks3CQWM


edit:

I changed it to: ((?<=^[^-]+-)[^-]+)
(added a bracket at beginning and end)

In an online regex tester like http://regexlib.com/RETester.aspx it now works perfectly, also giving the outcome in a $1 format.
But when I enter $1 in the  "Replace with:"  field in your plugin, it writes not only the outcome, but also what's behind the next "-".
Why is that?
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 20, 2012, 05:01:21 PM
I put out a request concerning your tool in the 'Wish' topic, and got a reply from Steven that this could be implemented by you if you would be sympathetic to it and be willing to do so:

http://getmusicbee.com/forum/index.php?topic=7665.msg44313#msg44313
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 21, 2012, 07:25:00 AM
Suppose the three following possible title tags of a track:

"first-second-third-fourth.mp3"
"first-second.mp3"
"first second.mp3"

The wish is to have your tool find only the word "second" from the first two examples, and do nothing with the third example. (or any other form without at least one "-" )
Try the following: search for: .*?-([^-]*).* and replace with $1
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 21, 2012, 09:41:48 AM
Try the following: search for: .*?-([^-]*).* and replace with $1

That's getting close, only example 3 goes wrong.
It will copy all contents of the title, even if there is no "-" present in the title.
Isn't that strange, since there is no match then?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 21, 2012, 10:47:25 AM
jistme, try this:

.*?-([^-]*).*|.*($)

Replace with:

 $1$2
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 21, 2012, 11:05:26 AM
Perfect!

Thanks boroda74.
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 21, 2012, 11:21:17 AM
Sorry, here I am again already.

While working great, it will now also write a new (empty) value in Custom3 when there is no "-" in the title.

Is it not possible to have your plugin making no changes when there is no regex match?
Wouldn't that be desirable behavior with regular expressions anyway?

 
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 21, 2012, 12:47:47 PM
Download latest version of plugin, search for: .*?-([^-]*).* and replace with $1
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on October 21, 2012, 01:02:07 PM
It looks like it's now working perfectly.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 23, 2012, 08:54:34 AM
Hi boroda74!

I'd like to thank you for offering this wonderful plugin. It helps me a lot in organizing my music library efficiently. 

Here is my situation. I'd like to fill "Album Artist" tag with the first artist of "Artist" tag and keep it running in the background. I looked around your presets and found one that does "Remove all items from multi-item 'Artist' tag except first one." I edited its saving tag from "Artist" to "Album Artist" tag. Well, it worked fine for some multiple-artist tracks, but it left "Album Artist" tag blank for single-artist tracks. And I'm not sure if this is related to the previously mentioned problem, but whenever I apply the edited preset to multiple (say more than 10) tracks MB keeps freezing. I guess the regular expression is not suited for this task or has some problem in its own? Can you help me to accomplish my goal? Thanks in advance!

Edit: Never mind! Somehow I've managed to do that. Thanks, anyway.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on October 23, 2012, 10:56:29 AM
Hi Boroda, Thank you for adding the # field so I could sort the Library report for my playlists, is it also possible to suppress the 000's in front of the sequence number?
Not a big one if you can't.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 29, 2012, 09:49:11 AM
Hi Boroda, Thank you for adding the # field so I could sort the Library report for my playlists, is it also possible to suppress the 000's in front of the sequence number?
Not a big one if you can't.
This would complicate sorting of #-tag
Title: Re: Additional Tagging and Reporting Tools
Post by: Theodor on November 23, 2012, 12:54:34 PM
Hi boroda74,

first of all, thank you for your plugin -- well, I haven't used it so far, but from what I've read, it is a great addition to an already great program.

Today, I tried to install the plugin but after I put the plugin files into Musicbee's plugin folder and started MB, the following message popped up: "Some tag names are duplicated. Plugin is not properly initialized." I checked the Tools Menu: all the  plugin entries were there but I think they didn't work as they're supposed to. For example, the Advanced Find and Replace dialog hadn't any presets to select from.

Can you think of any reason for this problem? I am using MB 2.0.4663 and downloaded the newest version of the plugin. Theater Mode and Screen Saver Mode are enabled, but not any other plugins.
Could it be that this has something to do with custom tags? I am using some custom tags which are written into the files' meta data.

It would be great if you could help me.

Theodor
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 25, 2012, 07:17:23 PM
Today, I tried to install the plugin but after I put the plugin files into Musicbee's plugin folder and started MB, the following message popped up: "Some tag names are duplicated. Plugin is not properly initialized." I checked the Tools Menu: all the  plugin entries were there but I think they didn't work as they're supposed to. For example, the Advanced Find and Replace dialog hadn't any presets to select from.

Can you think of any reason for this problem? I am using MB 2.0.4663 and downloaded the newest version of the plugin. Theater Mode and Screen Saver Mode are enabled, but not any other plugins.
Could it be that this has something to do with custom tags? I am using some custom tags which are written into the files' meta data.
This error means that localized tag names are duplicated. Most probable reason is that localized tag names "Lyrics" (this tag contains text of song) and "Lyrics?" (this pseudo-tag displays "Y" if song text is present and "N" if it is not) are the same. Part of plugin functionality wont be present in this case.

What is language of MB on your machine?

For example, the Advanced Find and Replace dialog hadn't any presets to select from.
You need to import ASR presets first by clicking 'Import All' or 'Import New' button.
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on December 24, 2012, 12:11:00 PM
Hello.
How can i remove words with []?

(.*?)\s* [www.xxx.xxx]* doesnt work.

And how can I remove all id3v1 tags?
I'm doing all this with mp3tag. Because it's much easier. But I want to get there to do everything in MusicBee.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 25, 2012, 10:27:13 PM
Hi
Search for '\[.*?\]' and replace with empty string.

You can't remove id3v1 tags and leave id3v2 tags with my plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: OOmatrixOO on December 27, 2012, 02:19:36 PM
Thank you.
Is it even possible with MusicBee to delete these tags completely?
Title: Re: Additional Tagging and Reporting Tools
Post by: Moss on December 27, 2012, 05:57:59 PM
still wait for the german translations...please  ;D
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 28, 2012, 10:59:13 AM
Thank you.
Is it even possible with MusicBee to delete these tags completely?
I think no.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 28, 2012, 11:00:10 AM
still wait for the german translations...please  ;D
What do you mean? Plugin supports for German for a couple of months.
Title: Re: Additional Tagging and Reporting Tools
Post by: Moss on December 29, 2012, 12:45:36 PM
ups... ;D  thx for the info.....
Title: Re: Additional Tagging and Reporting Tools
Post by: Ein on January 20, 2013, 02:18:48 AM
Using "Copy Tag" with "#" has a bug, depending on how you look at it:  If the numbers 1,2,3 ... 9,10,11 ... are saved into a custom tag and then the playlist view is sorted by this tag then the order will be

1
10
11
2
3
4
5
6
7
8
9
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on January 20, 2013, 06:29:47 AM
If the numbers 1,2,3 ... 9,10,11 ... are saved into a custom tag

Go to Preferences>>Layout>>main panel>>Configure Fields

In the Fields Layout Editor, find your Custom tag and set the type to "Number"

That should fix the sorting  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Ein on January 20, 2013, 04:58:22 PM
Excellent, thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: jamburglar on January 21, 2013, 12:09:24 PM
Question about the "Change Case" script: Is it possible to highlight the tags that would actually be changed (versus those that would be unaffected)? Right now they all appear red.

Here is how it's handled in the MediaMonkey change case script: http://i.imgur.com/8ZIqkYP.png

Question about the "Renumber Tracks" script: Is it possible to pad/add leading  zeros without also renumbering tracks?
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on January 21, 2013, 08:58:13 PM
Question about the "Renumber Tracks" script: Is it possible to pad/add leading  zeros without also renumbering tracks?

The "Renumber Tracks" option is part of the standard MB instal, to access the advanced features go to
Tools>>Tagging Tools>>Advanced>>Advanced search and replace
there you will find the option to Add up to 2 leading zeros or Add up to 5 leading zeros
further down the list is the option Remove leading zeros
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2013, 08:26:52 AM
Question about the "Change Case" script: Is it possible to highlight the tags that would actually be changed (versus those that would be unaffected)? Right now they all appear red.
Its hard to highlight unchanged tags. I'll do that unchanged tracks are unticked automatically.
Title: Re: Additional Tagging and Reporting Tools
Post by: jamburglar on January 22, 2013, 12:51:53 PM
Question about the "Renumber Tracks" script: Is it possible to pad/add leading  zeros without also renumbering tracks?

The "Renumber Tracks" option is part of the standard MB instal, to access the advanced features go to
Tools>>Tagging Tools>>Advanced>>Advanced search and replace
there you will find the option to Add up to 2 leading zeros or Add up to 5 leading zeros
further down the list is the option Remove leading zeros

Awesome, thank you!
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 23, 2013, 07:14:10 PM
Just installed the additional tagging tools. Nice options.
But the first one wasn't an immediate success:
I wanted to move the content of all 'conductor' fields (plain string) to customized field 4, labeled 'edit status' (string in autoselect droplist).
When I tried to swap all 11.000 field the tool stopped after a while. Clicking the X didn't help. A popup window appeared, saying that background processes can not be terminated (? - strange, why not?) and that a restart of MB was recommended. I then tried to close MB  itself, with the X, but that didn't work. The program was not responding.
After the restart I tried the tool again, now with a limited amount of tracks of 250. Rapidly and smoothly done.
The second 250 batch failed. Same hanging problems as before.
Please check!

PS
Steven advised me to copy this post here as well, so that the developer of Swap Tags might easier see it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 23, 2013, 07:27:42 PM
Originated from this thread: http://getmusicbee.com/forum/index.php?topic=8620.0

I wonder it would be possible for your plugin's drop-down menu to use both fg and bg values of "Controls.InputControl.Default" element. I think that would easily solve the problem, and every skin will display the menu more clearly without any alterations.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 24, 2013, 04:39:22 AM
When I tried to swap all 11.000 field the tool stopped after a while. Clicking the X didn't help.
As far as I remember there is "Stop" or "Cancel" button in plugin windows. This button should stop plugin background task immediately.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 24, 2013, 04:59:22 AM
Originated from this thread: http://getmusicbee.com/forum/index.php?topic=8620.0

I wonder it would be possible for your plugin's drop-down menu to use both fg and bg values of "Controls.InputControl.Default" element. I think that would easily solve the problem, and every skin will display the menu more clearly without any alterations.
MB API uses c# enumeration for getting colors. I don't know how this enumeration is mapped to XML skin color nodes.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 24, 2013, 05:27:15 AM
@boroda74
Well, when I was (repeatedly) trying to use Swap Tags it repeatedly crashed, and then the stop button did nothing.
About the colors: you mean your cannot create visitble colors in the swap tags panel? Or still searching?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 24, 2013, 06:28:17 PM
About the colors: you mean your cannot create visitble colors in the swap tags panel?
I mean that I don't know which XML skin-file tags I'm using in plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 24, 2013, 08:48:59 PM
Don't know what that means...
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on January 24, 2013, 09:00:07 PM
@boroda74, it should be
SkinElement.SkinInputControl   (7)
ElementState.ElementStateDefault  (0)
using function:
Setting_GetSkinElementColour
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 25, 2013, 10:14:39 AM
mmm... I'm already using SkinElement.SkinInputControl for buttons and SkinElement.SkinInputPanel for other controls.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 25, 2013, 09:11:26 PM
Hello Boroda,
I understand requests regarding your plugin should be put here - not in the MB wishlist.
As a new user I am already using your plugin a LOT, when re-arranging my big library migrating it from MediaMonkey.
I hope you will continue the good work by creating more presets (and some other functionality)
Instead of presenting a long wish-list, just allow me two requests at the moment:
1. What I really miss in the presets is something like: ADD <custom text 1> at the beginning of <tag1>
2. Same, but then at the end.

I already used a workaround a few times: I used preset #1 to add 'The', then used search/replace to replace 'the' into my desired text.
But special presets (at position #2 and 3?) would be much better.
Could you do that?

Thanks in advance!

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 26, 2013, 08:33:06 AM
Hi, WimYogya. As a quick solution you can use 'Copy tag' command:
1. select <Empty value> source tag and tick 'Add source tag to the beginning of destination tag placing between them: <Custom text>'
2. the same, but tick 'Append source tag to the end of destination tag placing between them <Custom text>'
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 26, 2013, 12:20:53 PM
Thanks, Borodo.
Helpful quick solution.
But you consider to create corresponding proper presets in the future?
If I have more preset requests, can I feel free to let you know? Or are you already fully booked till 2039? ;-)
Greetings,
Wim/William
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 26, 2013, 01:19:00 PM
But you consider to create corresponding proper presets in the future?
If I have more preset requests, can I feel free to let you know?
You are welcome.

edit:
I'm going to update ASR Preset pack according to user's requests in near future.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 26, 2013, 02:59:07 PM
Would there be a way to publish your future plans (in a sticky topic?), so that users can see if their requests are already on the list or possibly want to ammend the list?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 27, 2013, 06:46:41 PM
I'm doubtful that my plugin deserves separate wishlist topic. Post you requests here: I'll give you instructions how to create appropriate presets manually and later I'll include new presets to preset pack.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 27, 2013, 08:11:08 PM
Ok. I migrated this week from MediaMonkey (what a relief!) and I am not sure if you know the RegExp S&P plugin there.
Do you know that plugin?
It has an impressive set of 100+ presets, but:
- some are still not flexible enough to customize them a little bit
- they are VERY badly and messy organized, without any proper grouping labels.
So my suggestion to you is - if you keep the good preset work going:
1. make each preset as flexible as possible, customizable per action
2. group them logically-alfabetically with proper labels or numbers - such as:
ADD spaces to tag - <n> leading spaces to <tag1>
ADD text to etc.
COPY content <tag1> to <begin> or <end> of <tag2> seperated by <text>
REMOVE spaces - remove leading and trailing spaces in selected tag(s) (including ALL or multiple!)
REMOVE spaces - remove double spaces  etc....
3, give the user the option to replace your own preset description, sometimes a user finds a better/simpler one
4. give the user the option to rearrange the preset lists. In MM i only used around 15 of the 110 presets, I could move them to the top of my own customizable list

Goodluck and thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 29, 2013, 04:04:24 AM
Ok. I migrated this week from MediaMonkey (what a relief!) and I am not sure if you know the RegExp S&P plugin there.
Do you know that plugin?
This MM plugin inspired ASR command
1. make each preset as flexible as possible, customizable per action
2. group them logically-alfabetically with proper labels or numbers - such as:
ADD spaces to tag - <n> leading spaces to <tag1>
ADD text to etc.
COPY content <tag1> to <begin> or <end> of <tag2> seperated by <text>
REMOVE spaces - remove leading and trailing spaces in selected tag(s) (including ALL or multiple!)
REMOVE spaces - remove double spaces  etc....
I hope ASR preset pack is already organized this way
3, give the user the option to replace your own preset description, sometimes a user finds a better/simpler one
Although you can't edit/rename 'official' presets, you still can copy 'official' presets and edit/rename the copy and you can delete 'official' presets.
4. give the user the option to rearrange the preset lists. In MM i only used around 15 of the 110 presets, I could move them to the top of my own customizable list
Unfortunately it lies in the very basics of ASR command to display presets alphabetically, but you can simply delete unwanted presets. And you can restore full preset pack at any moment by clicking 'Import All' button.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on January 29, 2013, 04:48:00 AM
It seems that your suggestions and options make ASR flexible enough to 'rearrange' the list by giving new descriptions to each set with the copy/paste/delete commands. Thanks for the info.
And keep the good work going! ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 30, 2013, 09:46:19 AM
Here are my two wishes:

1. It would be great if conditions such as specific tag values, filters and playlists can be set for a auto-run preset so that the preset auto-applies only to those files meeting the conditions.

2. Expand MB's current "infer and update tags from filename" function to other tags so that average users can use "search in one tag & replace in another tag" without using regex.

Thanks in advance.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 30, 2013, 12:38:06 PM
1. It would be great if conditions such as specific tag values, filters and playlists can be set for a auto-run preset so that the preset auto-applies only to those files meeting the conditions.
Actually some filtering is already possible: any ASR preset won't do anything if there is no match in search pattern (more precisely if there is no match in any of 3 available search patterns).

2. Expand MB's current "infer and update tags from filename" function to other tags so that average users can use "search in one tag & replace in another tag" without using regex.
Did you mean search patterns like <Tag1>SomeExcludedText<Tag2>? So that searched tag will be splited to several tags? I'm afraid this is too far from current functionality. What do you need this for? Some example?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 30, 2013, 04:16:58 PM
1. It would be great if conditions such as specific tag values, filters and playlists can be set for a auto-run preset so that the preset auto-applies only to those files meeting the conditions.
Actually some filtering is already possible: any ASR preset won't do anything if there is no match in search pattern (more precisely if there is no match in any of 3 available search patterns).

What I meant was that, for instance, when I tick the option of auto-running for "swap first and last name of Composer field and save n another field," I'd like the preset to auto-apply only to classical music files (Genre=Classical, or in "Classical" filter), not to other files. I don't see how that's possible with the current version.
 

2. Expand MB's current "infer and update tags from filename" function to other tags so that average users can use "search in one tag & replace in another tag" without using regex.
Did you mean search patterns like <Tag1>SomeExcludedText<Tag2>? So that searched tag will be splited to several tags? I'm afraid this is too far from current functionality. What do you need this for? Some example?

For editing and managing tags without using regex. For instance, if I'd like to remove everything before or after a certain character or a word, currently I have to use regex. But my wish would let the user do the job easily. If it's not possible, never mind. Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 31, 2013, 04:11:22 AM
What I meant was that, for instance, when I tick the option of auto-running for "swap first and last name of Composer field and save n another field," I'd like the preset to auto-apply only to classical music files (Genre=Classical, or in "Classical" filter), not to other files. I don't see how that's possible with the current version.
I think this is a good idea. Probably I'll implement this.

For editing and managing tags without using regex.
Its easier for me to prepare several customizable ASR presets for such purposes than modify ASR command this way.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 31, 2013, 05:49:53 AM
I think this is a good idea. Probably I'll implement this.

Wonderful!

Its easier for me to prepare several customizable ASR presets for such purposes than modify ASR command this way.

That sounds good, too. I hope to see some presets dedicated to merge tags and split tags that can handle multiple delimiters. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: artiedeco on February 03, 2013, 02:15:10 AM
I just installed this and I am having trouble with the "Copy To" command.  I'm trying to copy from the # tag to custom3. Everything looks right in the preview and when I click proceed it appears to work. However, when I check the tag in edit, nothing is there.  I've tried other combinations with the same results. Am I missing something?

Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2013, 02:32:44 AM
Hmm. Just tested this and found no problem.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2013, 02:34:38 AM
I think this is a good idea. Probably I'll implement this.

Wonderful!

Its easier for me to prepare several customizable ASR presets for such purposes than modify ASR command this way.

That sounds good, too. I hope to see some presets dedicated to merge tags and split tags that can handle multiple delimiters. Thanks!
redwing, two your requests are implemented now. Download beta version of plugin from the 1st post of this topic.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2013, 05:21:04 AM
redwing, two your requests are implemented now. Download beta version of plugin from the 1st post of this topic.

Thanks for implementing my requests! I downloaded it and did some tests, but it didn't work well. A preset I set up (Swap first and last name adding custom text) was applied to tracks that don't belong to the selected playlist. And the preset itself wasn't working properly. It wrote in a tag differently from what was shown at preview. At last it was writing and rewriting constantly in some tags only to freeze MB. When I restarted MB, the playlist selection box was gone. Overwriting the new dll file didn't make a difference. So I ran MB with the previous version of dll file, exited, copied the new dll file, and restarted MB, this time I was able to see the box again.

Anyway, are you gonna add some more auto-apply options in addition to playlist, or that's all?

As for the new presets (combine and split tags), they looked great although I didn't actually test them. After looking over them, I got another wish, but it might take some time to implement. So just think about it.

Currently each preset allows the user to configure up to 5 steps. That's great, but only if you're familiar with regex. Otherwise, it won't be easy to utilize those step boxes. So how about allowing the user to select (and configure) another preset as a step by offering a preset selection box for each step from 2nd step?

Anyway, I'm looking forward to a bug-free update version :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2013, 04:02:10 AM
A preset I set up (Swap first and last name adding custom text) was applied to tracks that don't belong to the selected playlist.
That's strange and I can't reproduce that. Notice that this option ('Auto apply preset only if it is contained in playlist:') applies only when preset is auto applied, i.e. when manually select a number of tracks and click 'Preview' in ASR window then preset will be applied to all selected tracks.

And the preset itself wasn't working properly. It wrote in a tag differently from what was shown at preview. At last it was writing and rewriting constantly in some tags only to freeze MB. When I restarted MB, the playlist selection box was gone. Overwriting the new dll file didn't make a difference. So I ran MB with the previous version of dll file, exited, copied the new dll file, and restarted MB, this time I was able to see the box again.
Probably I need to do more careful testing of beta version of plugin. Thanks for bug reporting.

Anyway, are you gonna add some more auto-apply options in addition to playlist, or that's all?
I think it's sufficient as you can create very complicated autoplaylists specially for ASR command.

As for the new presets (combine and split tags), they looked great although I didn't actually test them. After looking over them, I got another wish, but it might take some time to implement. So just think about it.
You are welcome.

Currently each preset allows the user to configure up to 5 steps. That's great, but only if you're familiar with regex. Otherwise, it won't be easy to utilize those step boxes. So how about allowing the user to select (and configure) another preset as a step by offering a preset selection box for each step from 2nd step?
Actually I don't mean that end users will create ASR presets by themselves (although it is possible). I'm ready to create (or give you instructions how to create) new presets if they are needed.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2013, 04:41:35 AM
That's strange and I can't reproduce that. Notice that this option ('Auto apply preset only if it is contained in playlist:') applies only when preset is auto applied, i.e. when manually select a number of tracks and click 'Preview' in ASR window then preset will be applied to all selected tracks.

Yes, I meant auto-apply. I selected "Classical" playlist, and as I edit a composer tag of a "Pop" track, the preset was auto-applied to the file.

I just tried the beta version again, but it's still doing wrong conversions and freezing MB. The box was gone again.

Actually I don't mean that end users will create ASR presets by themselves (although it is possible). I'm ready to create (or give you instructions how to create) new presets if they are needed.

What I meant was that you already provided those presets that can be used as a step for another preset. For instance, if I want to split a tag in a certain way, remove particular parts of the split part, and combine them and save in another tag, you already created three presets for such a task. What's needed is to allow users to configure a workflow using multiple presets for a single task. Currently I can only do that in separate three sessions with each of those presets. It's not that urgent right now. But I think that would make this plugin more useful for average users. Thanks for your support!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2013, 04:56:04 AM
What I meant was that you already provided those presets that can be used as a step for another preset. For instance, if I want to split a tag in a certain way, remove particular parts of the split part, and combine them and save in another tag, you already created three presets for such a task. What's needed is to allow users to configure a workflow using multiple presets for a single task. Currently I can only do that in separate three sessions with each of those presets. It's not that urgent right now. But I think that would make this plugin more useful for average users. Thanks for your support!
i.e. some kind of groups of presets. Maybe, maybe. But first I need to debug current beta version.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2013, 05:05:08 AM
i.e. some kind of groups of presets. Maybe, maybe. But first I need to debug current beta version.

Yes. And I understand it's not certain how many users would ever need a multiple-step workflow for converting tags. It might not worth it, especially if you're available for a customized preset. I'm just throwing a wish. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2013, 06:50:06 AM
At last it was writing and rewriting constantly in some tags only to freeze MB. When I restarted MB, the playlist selection box was gone. Overwriting the new dll file didn't make a difference. So I ran MB with the previous version of dll file, exited, copied the new dll file, and restarted MB, this time I was able to see the box again.
What is number of tracks in your library? Did you do some manual massive tagging operations when UI was freezed?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2013, 07:01:02 AM
What is number of tracks in your library? Did you do some manual massive tagging operations when UI was freezed?

No, it was just one track, and the freezing part had nothing to do with auto-apply (today's test was the same). I applied the swap preset to a classical track, as a test, and it wrote wrongly "Chopin, 1Frédéric" and then correctly "Chopin, Frédéric", and repeat it constantly only to finally freeze MB. I had to end the process with Windows Task Manager.

I remember it wrote "/%" instead of ", " the other day although its preview was correct.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2013, 07:16:37 AM
What is number of tracks in your library? Did you do some manual massive tagging operations when UI was freezed?
No, it was just one track, and the freezing part had nothing to do with auto-apply (today's test was the same). I applied the swap preset to a classical track, as a test, and it wrote wrongly "Chopin, 1Frédéric" and then correctly "Chopin, Frédéric", and repeat it constantly only to finally freeze MB. I had to end the process with Windows Task Manager.
Was some preset is ticked for auto applying at this moment? Probably the same preset which was applied manually?

I remember it wrote "/%" instead of ", " the other day although its preview was correct.
I think it wrote ", /" instead of ", ". Its an error in this preset. I'll check all new presets for errsors.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2013, 07:23:25 AM
Was some preset is ticked for auto applying at this moment? Probably the same preset which was applied manually?

Yes. that's the only one. But after unticking it, it froze MB again. To me the endless rewriting seemed to be a main cause.

I think it wrote ", /" instead of ", ". Its an error in this preset. I'll check all new presets for errsors.

No, I'm sure it was "/%." I tested it several times while changing the value of source tag. But today the same preset wrote ", 1". I have no clue.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2013, 08:09:38 AM
redwing, could you give me exact name of preset which causes freezing as I can't reproduce this?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2013, 08:40:41 AM
redwing, could you give me exact name of preset which causes freezing as I can't reproduce this?

It's "Swap first & last name of artist and adding <Custom text> - 2."

Search for: 

([\x01\x02\x04]?)([^\x00]*) ([^\x00]*)(\x00?)

Replace with:

$1$3\@1$2$4
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2013, 10:55:42 AM
Sill can't reproduce freezing.

If somebody else have similar issues with beta version of plugin, please report them.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 05, 2013, 05:03:09 PM
@boroda, redwing
Upon redwing's advice I installed the newest beta of the plugin.
But the TOY: copy' 'feature does not seem to work.
I try to copy the virtual field 'performer-v' (with a chain of people: multiple soloists, instrumentalists, orchestra, conductor) into a 'normal' custom field that I labeled 'performer' - hoping this custom field would split up all the chained entries into individual ones.
But nothing is being copied at all.

Even more:
Also other copy tag tasks do not seem to work.

And a related request:
In the ASR preview/result section the column width can not be changed, even if you widen the whole panel.
And the default width for old/new tag are simply to small for most (classical) tags.
Make it resizable, please?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2013, 03:21:19 AM
But the TOY: copy' 'feature does not seem to work.
I try to copy the virtual field 'performer-v' (with a chain of people: multiple soloists, instrumentalists, orchestra, conductor) into a 'normal' custom field that I labeled 'performer' - hoping this custom field would split up all the chained entries into individual ones.
But nothing is being copied at all.
Yes, I can reproduce this. I'll fix it.

Even more:
Also other copy tag tasks do not seem to work.
What do you mean by 'other copy tag tasks'?

And a related request:
In the ASR preview/result section the column width can not be changed, even if you widen the whole panel.
And the default width for old/new tag are simply to small for most (classical) tags.
Make it resizable, please?
It very easy to do, but then columns won't be autosized at all.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 06, 2013, 09:44:35 AM
Even more:
Also other copy tag tasks do not seem to work.
What do you mean by 'other copy tag tasks'?

I meant to say: NOTHING can be copied from any field to any field; it's not restricted to my virtual source tag


And a related request:
In the ASR preview/result section the column width can not be changed, even if you widen the whole panel.
And the default width for old/new tag are simply to small for most (classical) tags.
Make it resizable, please?
It very easy to do, but then columns won't be autosized at all.

I don't know how other users feel/think about it, but for me the default size is useless: in most cases I cannot see if the new/proposed change is the one I want. Because I can simply not see it in the narrow column.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2013, 11:07:33 AM
I'll upload new beta tonight. There will be free-sized columns in ASR and some bugfixes.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 06, 2013, 02:21:38 PM
Ok, thanks.... Please check the bug (?) too that makes it impossible to work with copied preset(s)... See my other post. But take your time if it is a complicated one.
And: what is your 'tonight'? I mean: your timezone?
Here (Indonesia) it als already halfway tonight, but maybe you are 12 or more hours behind ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2013, 02:52:31 PM
See my profile :) UTC+4
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 06, 2013, 04:07:39 PM
I would have guessed (based upon the 'sound' of the name/nick): one of the Eastern European countries... ;-)
Well: who knows > see you in Moscow between July 13-21 ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2013, 05:19:23 PM
Well: who knows > see you in Moscow between July 13-21 ;-)
Do you intend to visit Moscow? Well, see you ;)
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 06, 2013, 08:55:46 PM
Yes, we already booked our Aeroflot tickets: 12 July Bangkok > Moscow + 21 July Moscow > Amsterdam
I live in Indonesia and will travel with my friend via Moscow to Holland.
If you and I both have time and interest we might have a drink somewhere.
And if you have good, cheap, central, reliable hotel or b & b in Moscow to recommend: please send me in PM. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 07, 2013, 03:08:37 AM
Updated beta of plugin is released. See 1st topic for details.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 07, 2013, 03:49:36 AM
The new beta version is working excellent. Tested with the Swap preset auto-applied to "classical" playlist, and it's working perfectly. I'll try other new presets later and report back if I encounter problems. Thanks a lot!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 07, 2013, 04:35:49 AM
There's a small annoyance with your plugin, not just with the new version. I think it should suppress MB's hotkeys while the plugin's pane is active. For instance, I have assigned space key for play/pause. If I use the key while editing something on the pane, the selected track starts to play. It doesn't make sense since I can't even see what track is selected. Ctrl-C and V also function as MB's default hotkeys for copy and paste tags. It would be great if this can be fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 07, 2013, 05:30:05 AM
I think it should suppress MB's hotkeys while the plugin's pane is active.
I'll intercept common keys such as space or enter in plugin's windows, but I'm not sure if this will prevent MB from getting these events.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 07, 2013, 06:22:00 AM
The new beta did not solve the performance issue.
First I thought that (only) COPIED presets did the trouble (even without the presets themselves had been changed, just copied with a new name).
But now I know it is not that.
The problem happens at least with ONE of your own presets:
After scanning a substantial amount of files to add a zero in a single numbered track field, it is impossible to use ASR and even MG again.
The first time running is normal and ok, but a second time is slow as a handicapped snail... That goes for other, non-ASR actions as well: the edit panel opens in 30+ seconds etc.
There must be some very very very slow background process running that makes all other actions impossible, at least unacceptably slow.
Sometimes I see a slow change happening on the screen: minutes after I applied the command I see 7 change in in 07, 20 seconds later the next one: 8 becomes 08.
Stopping the process, closing the ASR window, all impossible - or sometimes possible after 30 mins or 1 hour.

At least the 'add zero' preset (checked) causes the trouble. Maybe other presets too, I have no experience with them.
Please check.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 07, 2013, 07:14:02 AM
The matter is that I don't experience any slowdowns on my PC, so let me ask some questions:  

1. What is specs of your PC?
2. What is number of tracks in your library?
3. Do you mean auto applied or manually applied 'add zero' preset?
4. What number of tracks were edited when MB had been down?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 07, 2013, 07:30:50 AM
@WimYogya:

Just make sure that when you update this plugin with the new version, delete the old ASR presets folder entirely and copy new folder. And after activating the plugin, delete all existing presets in the window and import new presets since those presets have been updated too.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 07, 2013, 08:59:52 AM
Bug report:

Having the swap preset only auto-applied, after editing a rating for a (classical) track I noticed the preset all of a sudden started to run (according to status bar) while consuming most of system resources. Since I did not edit any composer tag, I opened the plugin window and managed to stop it to auto-apply. After reviewing tracks, it turned out that it did not edit any track as opposed to the status bar info. After this, I found the playlist selection box's gone again.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 07, 2013, 09:03:43 AM
@boroda
@redwing

Seems that the instruction to remove the old folder/presets and re-import from the new folder did the trick.
So far all works as expected, smooth and fast. Will experiment more to see if behaviour remains this pleasant.

Tip:
Wouldn't it be a suggestion to add this instruction to remove old folder/presets when installing an update at the top topic?

Boroda's questions:
1. 6 months old PC with intel core i3-2100 cpu @ 3.10 ghz - 3.10 ghs - ram installed 8 gb - 64 bit OS - windows 7 home premium w SP 1
2. 113.000 tracks
3. the problem that seems solved now occurred when 'auto-apply' adding zeros was activated, but the first run was done manually and smooth. after that all went wrong.
4. I experimented with batches of 10-750 tracks. Don't know what amount exactly triggered the problem. I would say: few hundred tracks. But just now a smooth run with 2750 tracks was possible.

Requests:
1. Would it be possible to add the option 'any' to (all or some) presets, in the field selector. Then you don't have to do multiple runs of a preset to clean/change the track(s) but all fields are expected in one time.
2. Would it be possible to let some/all panels to remember their position on the screen? Especially the (normal) Search & Replace: it always pops up in the far left corner, that means: dragging tot the center of my wide screen every time.
3. Would it be possible to let S&R remember the last used settings (field, search string, replace string). Easier if you are working with thousands of tracks if you cannot keep the panel open permanently because of other tasks.
All these are just ideas, suggestions. No hurry. Take your time. And see what is possible, handy, urgent. You are the expert, not me....
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 07, 2013, 09:33:21 AM
Bug Report 2:

Just now a similar, but a little worse, thing happened again. Editing rating of a track invoked a full running of the auto-applied preset. This time it froze MB, so I had to end the process with Process Manager.
The preset edited only one track, wrongly, that already had a right tag: from "Verdi, Giuseppe" to "Verdi, 1Giuseppe".
Playlist selection box was gone again.

Edit: To be precise, it didn't freeze MB unlike the previous version. I couldn't exit the plugin's window to return to MB because all keys didn't work. But on the Process Manager MB was running all right even though I can do nothing with it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 07, 2013, 12:32:51 PM
Tip:
Wouldn't it be a suggestion to add this instruction to remove old folder/presets when installing an update at the top topic?
I've written almost this in "What's new?" section of 1st post. Probably I'll write that this step is obligatory in bold text.

1. 6 months old PC with intel core i3-2100 cpu @ 3.10 ghz - 3.10 ghs - ram installed 8 gb - 64 bit OS - windows 7 home premium w SP 1
Your machine is perfect, better than mine.

2. 113.000 tracks
This may cause some problems because I'm testing plugin with ~14.000 tracks (size of my library).

1. Would it be possible to add the option 'any' to (all or some) presets, in the field selector. Then you don't have to do multiple runs of a preset to clean/change the track(s) but all fields are expected in one time.
I can't imagine how such universal command like ASR can deal with all tags simultaneously. Where should it write changed values if there may be up to 5 different source values in every ASR preset?

2. Would it be possible to let some/all panels to remember their position on the screen? Especially the (normal) Search & Replace: it always pops up in the far left corner, that means: dragging tot the center of my wide screen every time.
Yes, I can implement this. I was already thinking about this. But plugin hardly will remember windows positions between MB sessions.

3. Would it be possible to let S&R remember the last used settings (field, search string, replace string). Easier if you are working with thousands of tracks if you cannot keep the panel open permanently because of other tasks.
Its possible too. Later.

P.S.
@redwing
@WimYogya
Thanks for bugs reports. I'll test plugin more carefully. Remember that now its just a beta.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 07, 2013, 04:01:30 PM
More experiments with the ASR beta showed that the update is significantly faster than before, but after/during mass operations it still slows down the whole behaviour if auto-apply is used in my big collection. So for the time being I will not use it in these times where I am permanently re-arranging, updating, cleaning, retagging thousands of files. Maybe later, for finetuning of smaller amounts.
The tool itself is excellent - just the auto-apply-speed is not so good (yet) in my situation.

As to the 'any' field request: I just saw that it was added (by you or Steven?) recently in various dropdownlists. Including standard S&R. So thought i would perhaps be possible in other presets as well. I have no clue about background processes, values, etc. If it is not possible, so be it.
In the meantime I found that several presets can already scan up to 5 customizable fields in one go - that is already quite convenient.

If panel positions cannot remember their positions across MB sessions, then give it a fixed startup position elsewhere, not in the far left corner. With wide screens like mine it is too much scrolling ;-)

Sometimes I feel sorry to report issues, because I cannot express enough how thankful I am, first of all. But then I realize too that bug reporting is not a matter of complaining or demanding improvements, but a contribution to your work. Nice to hear you appreciate it.
Goodluck!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 07, 2013, 04:50:39 PM
More experiments with the ASR beta showed that the update is significantly faster than before, but after/during mass operations it still slows down the whole behaviour if auto-apply is used in my big collection.
WimYogya, one more question: was auto applied preset filtered by auto- or static- playlist in your case? I mean "Auto apply preset only if track is contained in playlist:" option.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 07, 2013, 05:30:08 PM
No, I saw that filter option but did not understand (yet) why i should/could use it, so i didnt activate any filter.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 07, 2013, 08:42:41 PM
New Trouble. Maybe ASR can 'save' me!
A completely failed experiment to map the field 'conductor' with my own customized field 'conductortest' had the terrible result that all 2500 fields with names in 'conductortest' are completely gone. Lesson learned: don't apply experiments to the whole library, just experiment with backups or selected files... But that lesson came too late for NOW.

All my conductors names are still in the field 'performers', which is a copy of the field performers-virtual.
The performers-virtual are changed now, missing their last entry, the conductor(test).
But the copied field 'performers' was not automatically affected, the conductors are still there - as said: as the last of a multiple entry list.
Would ASR have a way to SPLIT OFF the last entry in a multiple entry list and COPY it to the field 'conductortest'?
I see a preset in the ASR list, like: remove the last entry from ARTIST. That is about the idea but:
- can I do it from other fields as well, i.e. PERFORMERS?
- can I not just (re)move that last entry, but copy it to another field (CONDUCTORTEST or TEMP or so?)

Help would be highly appreciated!
Sorry for the mess. Growing pains...
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 08, 2013, 01:25:45 AM
@WimYogya:

Would you give an example of your tags with the current and the desired format? It's not easy to get what each field of yours looks like.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 08, 2013, 08:36:45 AM
I already found a way to isolate the 'conductors' from the PERFORMERS field, where (if existing) it is always the last of the (many) entries.
I split the PERFORMERS field several times in several tracks, till just one entry is left in the source field. That is the conductor (if a conductor name was entered, otherwise it is the orchestra, easy to see the difference....)  ;-)
But I made a mistake.
So now I am in other trouble again.
See my newest topic about 'retrieving title information'...
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on February 09, 2013, 03:31:13 AM
Switched to new beta
deleted old ASR presets, imported new
CPU usage normal for when MB running (3-6% with Firefox and a few others open)
Edited tags on one album (10 tracks) and background 'Copy Tag' preset starts
CPU usage jumps to 65-70% and stays there.
Have let MB run for 24hrs to see if CPU usage drops again but it doesn't
Approx 25K files in library
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 09, 2013, 04:14:39 PM
Bug Report 3:

I have noticed the pattern I've reported repeats. When set, auto-applying works fine for a while, but all of sudden it starts to run when a tag value of a file is changed. It doesn't matter whether the file is on the selected playlist or the edited tag is related to the auto-applied preset. It consumes lots of system resources, and whether or not I succeed in unticking the auto-apply option, it freezes MB as I reported before. What it does seems to be the same as the previous version. It constantly rewrites the same tag for one file, ends up editing wrongly. And playlist selection box disappears from the pane.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 10, 2013, 03:08:45 PM
@WimYogya
@redwing
@Bee-liever
I still can't reproduce sudden slowdowns and freezes, but I've tweaked ASR command. Please try new beta (http://www.mediafire.com/download.php?22w07d5hd6i57cj).
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on February 10, 2013, 10:15:53 PM
@ boroda74

Updated to latest beta and CPU usage has returned to normal.
Thank you
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 11, 2013, 05:24:58 AM
It's a good news.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 11, 2013, 05:58:37 AM
Sorry, but the same error persists with the new version. This time editing a rating of classical track started and repeated the whole steps only to end up with wrong editing of "Chopin, 1Frédéric" with the same file. I'm sure you know now what preset I'm using under what settings.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 11, 2013, 06:09:19 AM
redwing, try to 'delete all' and 'import all' presets as they were upgraded after releasing beta version.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 11, 2013, 06:17:40 AM
redwing, try to 'delete all' and 'import all' presets as they were upgraded after releasing beta version.

I did.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 11, 2013, 06:25:26 AM
No luck?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 11, 2013, 07:02:15 AM
I had already done the steps you mentioned when updating, and then reported the bug. Yes, no luck, unfortunately.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 11, 2013, 07:21:49 PM
When installing a new beta of ASR, is it sufficient to delete and re-import all non-user presets?
No chance that the user-presets still have old functionality that can create problems?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 12, 2013, 03:07:39 AM
There were errors in some 'official' presets. That's why I recommend to reimport them. If user presets don't have errors then there is no need to delete them.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 12, 2013, 10:04:36 AM
I've located what caused, at least, coming-and-going of playlist selection box.
While having lots of trouble with this beta version, one of the most annoying thing was that playlist selection box was constantly coming and going, sometimes with no apparent reason. Then it occurred to me that whenever I updated the new beta version I always left the official version of mb_TagTools.dll in the same folder under the filename of mb_TagTool.dll for easy restoration of the plugin's functionality after crush (by swapping the filename of the old and new dll file). A little while ago I deleted the file, and then immediately noticed that the box was back and has stayed stable. Also the auto-applied preset has been working fine so far. I'll report back if that will really do the trick. BTW how come a dll file with different name can affect the plugin's functionality?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 12, 2013, 11:29:41 AM
I'll report back if that will really do the trick.
Thank you. Seems that I could release stable version in near future.

BTW how come a dll file with different name can affect the plugin's functionality?
This is a puzzle. :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 12, 2013, 04:03:34 PM
I set up two presets auto-applied to tracks contained in two different playlists and so far they're working perfectly with various tests. I'll report back if I encounters a problem.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 12, 2013, 06:06:00 PM
Just now I edited a tag of 500+ tracks, all of which are not contained the two auto-applied playlists. But that prompted MB to consume most of CPU resources and MB's main panel header started to tremble, which is a typical sign of background running of auto-applied presets but there was no messages on the status bar. I managed to open the plugin's pane and untick the two preset's auto-apply options. Then system resources were back to normal but MB got frozen. It seems that this version is still unstable with massive editing of tag values.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 12, 2013, 06:32:23 PM
Now filtering by playlist is not very effective. I'll ask Steven to extend API for fast filtering.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 13, 2013, 06:17:17 PM
Is there a way (in an existing preset or a planned new one) to remove one or more characters from the beginning or the end of a field?
I do not mean a specific string (then I can just replace string x with nothing), but one or more characters, based upon their positions?

Classical title strings are often surrounded by ' apostrophes or " quotation marks.
If I don't want that (which is the case) I can easily remover the "
But if I do that with the ' than I will also damage all the words like: don't, I'll, L'argent etc.
The initial ' can often be removed because it often comes after a : or -  and can be search/replaced with that sign.
But the one at the end is difficult...

From previous experiences I remember that such 'character remover' can be helpful to standardize titles that start with numbers in a wide variety of formats:
1. Bla
2 - Bla
3. - Bla
04: Bla
If you can remove 1 initial character at a time (and then resort the titles) you can clean up easier.
Title: Re: Additional Tagging and Reporting Tools
Post by: jamburglar on February 13, 2013, 10:19:35 PM
I keep getting this error (just downloaded the latest beta):

Quote
Some tag names are duplicated. Plugin is not properly initialized.

EDIT: When I open ASR, I receive this Error:
Quote
MusicBee v2.1.4770.37287 (Win6.1), 13 Feb 2013 17:21:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.ChangeCasePlugin.IsItemContainedInList(String item, String[] list)
   at MusicBeePlugin.Plugin.fillList(IList list, Boolean addReadOnlyTags, Boolean addArtwork)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.fillParameterTagList(Int32 parameterTagType, ComboBox parameterTagListParam, Label parameterTagLabelParam)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.presetList_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.CheckedListBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.CheckedListBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ListBox.WndProc(Message& m)
   at System.Windows.Forms.CheckedListBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Any help would be much appreciated.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2013, 06:59:31 PM
Is there a way (in an existing preset or a planned new one) to remove one or more characters from the beginning or the end of a field?
Create new ASR preset. Fill step 1. Search for (without quotes) "^.(.*).$" and replace with "$1". Leave steps 2-5 blank. This will remove 1st and last character in tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2013, 07:03:35 PM
I keep getting this error (just downloaded the latest beta):

Quote
Some tag names are duplicated. Plugin is not properly initialized.

Try to upgrade MB to latest version (http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip).
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 14, 2013, 07:44:02 PM
Is there a way (in an existing preset or a planned new one) to remove one or more characters from the beginning or the end of a field?
Create new ASR preset. Fill step 1. Search for (without quotes) "^.(.*).$" and replace with "$1". Leave steps 2-5 blank. This will remove 1st and last character in tag.

I am afraid I still have questions about your suggestion:
1. How can the preset you describe remove the first AND the last character in a tag? I didn't even mean to propose that.
2. At times I need to remove the LAST (or the last 2 or 3 or 5) characters. What is the formula for that?
3. At times I need to remove the FIRST (or the first 2 or 3 or 5) characters. What is the formula for that?
Thanks for additional information!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2013, 08:00:33 PM
2. At times I need to remove the LAST (or the last 2 or 3 or 5) characters. What is the formula for that?
for 2 last chars search for "^(.*)..$" and replace with "$1"
for 3 last chars search for "^(.*)...$" and replace with "$1"
for 5 last chars search for "^(.*).....$" and replace with "$1"

3. At times I need to remove the FIRST (or the first 2 or 3 or 5) characters. What is the formula for that?
for 2 first chars search for "^..(.*)$" and replace with "$1"
for 3 first chars search for "^...(.*)$" and replace with "$1"
for 5 first chars search for "^.....(.*)$" and replace with "$1"
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 14, 2013, 08:12:11 PM
Great, thanks for fast support. Created one for 'last character' and for 'first'. They work fine.

Do you consider to create such preset in the future, to include in your set?
A combined one, where you can select variables as  first, last, 1, 2, 3, 4, 5?
Greetz

PS:
One small display issue that you might be able to find solution for:
You use marroon as the font color for 'new value'. But (specially if I only want to change ONE file) I cannot read the new value.
Because my default color in Windows for highlighting a selected word/line is RED...
So there is no contrast between your font and my background.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2013, 08:33:07 PM
A combined one, where you can select variables as  first, last, 1, 2, 3, 4, 5?
It's not possible with current (beta) version of plugin. Maybe I'll extend ASR functionality in future to add support for such variables.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 14, 2013, 08:42:29 PM
Don't worry, I can live with it.
If it was just a matter of changing a color code, nice, but don't need to make major changes for this.
You already busy enough, I think...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 16, 2013, 08:32:12 PM
@redwing
Could you test speed of ASR with new version of plugin?
Title: Re: Additional Tagging and Reporting Tools
Post by: jistme on February 16, 2013, 08:44:35 PM
Thnx Boroda, much appreciated.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 16, 2013, 09:00:09 PM
@redwing
Could you test speed of ASR with new version of plugin?

Filtering with playlists feature doesn't work at all with the new version. If I untick playlist selection box, then they auto-apply.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 16, 2013, 09:22:03 PM
One small display issue that you might be able to find solution for:
You use marroon as the font color for 'new value'. But (specially if I only want to change ONE file) I cannot read the new value.
Because my default color in Windows for highlighting a selected word/line is RED...
So there is no contrast between your font and my background.
What color do you propose for 'new value'? I suggest that any color may interfere with custom windows color scheme :(
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 16, 2013, 10:14:08 PM
Filtering with playlists feature doesn't work at all with the new version. If I untick playlist selection box, then they auto-apply.
Re-download latest MB version (http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 16, 2013, 11:07:07 PM
Filtering with playlists feature doesn't work at all with the new version. If I untick playlist selection box, then they auto-apply.
Re-download latest MB version (http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip).

Filtering feature is now working fine. But I don't see much differences in massive editing with the previous version.
I set up two presets auto-applied to two different playlists and tried two sets of massive tag editing with 500+ and 1000+ tracks. As usual, after MB's editing session is done, the plugin's blinkering headers and cursor continued for several minutes. During that time I could play and navigate tracks but could not edit any tags because tag editor was constantly trembling. And opening plugin's pane during that time led to freeze MB as previously. I'm not sure this is due to filtering or new version in general.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 17, 2013, 05:30:34 AM
What color do you propose for 'new value'? I suggest that any color may interfere with custom windows color scheme :(

Yes, I do realize that any chosen color could interfere with someone's Windows settings, unless there is an 'autocontrast option': in my case white font if the background is red (or in general: if the background isnt white). Have no idea if that is simple/possible... Otherwise just forget it...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 17, 2013, 11:33:23 AM
Filtering feature is now working fine. But I don't see much differences in massive editing with the previous version.
I set up two presets auto-applied to two different playlists and tried two sets of massive tag editing with 500+ and 1000+ tracks...
Could you untick filters of ASR presets and redo massive tag changing to see if there is much difference in speed? I need to know if slowdowns are caused mainly by filetring by playlists or by ASR itself.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 17, 2013, 11:36:58 AM
in my case white font if the background is red (or in general: if the background isnt white).
I'm afraid that white font will be indistinguishable on standard unselected white background.

P.S.
I'll see if there is possibility to use windows scheme colors instead of fixed colors.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 17, 2013, 12:11:04 PM
Filtering feature is now working fine. But I don't see much differences in massive editing with the previous version.
I set up two presets auto-applied to two different playlists and tried two sets of massive tag editing with 500+ and 1000+ tracks...
Could you untick filters of ASR presets and redo massive tag changing to see if there is much difference in speed? I need to know if slowdowns are caused mainly by filetring by playlists or by ASR itself.

With two playlist-filtered auto-applied presets, entering a value in a field of 953 files took 58 sec for MB and 3 min 8 sec for plugin (to confirm with high CPU usage).
After unticking filtering option for the two presets, removing the same value took 1 min 40 sec for MB and 3 min 40 sec for plugin.
Looks like there's no differences in speed between filtering or not.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 17, 2013, 12:42:17 PM
redwing, thank you
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 17, 2013, 12:50:54 PM
@redwing
Does this version (http://www.mediafire.com/download.php?rg1i8s8ka9ey2ug) eliminates UI slowdowns?

EDIT: link is updated
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 17, 2013, 01:25:04 PM
@redwing
Does this version (http://www.mediafire.com/download.php?ciwe1w5ftl2ywx6) eliminates UI slowdowns?

With that version,

Ticking: 44 for MB, 3:38 for plugin
Unticking: 45 for MB, 3:45 for plugin

So it improved MB's speed when not filtering, but plugin's speed was almost the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 17, 2013, 01:31:39 PM
EDIT: link is updated

I'll be right back.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 17, 2013, 01:49:36 PM
@redwing
I think I cant improve the *speed* of ASR, but I intend to improve *UI responsiveness*. My test showed that current version runs fine until you reopen (and then close) ASR window. In last case UI just freezes. Its definitely some bug, not just the performance issue and I'll try to get rid of it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 17, 2013, 01:54:58 PM
With that edited version,

Ticking: 1:00 for MB, 3:36 for plugin
Unticking: 0:46 for MB, 4:33 for plugin

@redwing
I think I cant improve the *speed* of ASR, but I intend to improve *UI responsiveness*. My test showed that current version runs fine until you reopen (and then close) ASR window. In last case UI just freezes. Its definitely some bug, not just the performance issue and I'll try to get rid of it.

Sounds reasonable. Based on my (unreliable) test, the previous of the last version works best.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 17, 2013, 03:07:35 PM
in my case white font if the background is red (or in general: if the background isnt white).
I'm afraid that white font will be indistinguishable on standard unselected white background.

P.S.
I'll see if there is possibility to use windows scheme colors instead of fixed colors.

Fine, take your time and let me know. No hurry.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on February 18, 2013, 09:30:26 PM
Thank you for your work on this
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 19, 2013, 08:17:20 AM
New version of plugin is released. See 1st post for details.

Tried the new version. Now opening and closing down the plugin's pane during background running of auto-applied presets doesn't lead to freezing. But all buttons including "save all" and "save all and close" don't work except tick boxes, so I had to click on Windows' close button to close down the pane. But that's not a big deal because it's now working stable and there's no need to open the pane while it's working. Thanks for your hard work!
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 22, 2013, 01:17:16 PM
An update after a lot of tagging work, with and without ASR.
First of all: thanks for the great tool, Boroda! I save SO much time, compared to previous managers/plugins!

Having said this, allow me a few remarks/requests/issues:
1.
What I really miss most is a small feature: when doing LOTS of editing it is a pity that the Search & Replace (and other?) command can not memorize its most recent settings (looking for ... in ... and replace with ...). When cleaning up 1000+ titles of all kinds of mess, it is annoying that after every new instance I have to close S&R, and scroll down to TITLE again, and retype the search/replace values, even if there is just 1 character difference. Please store the settings (at least during one MB session) and store the location as well.
2.
With the copy tag command I sometimes have a problem. I created a 'virtual performers' field (combining vocalists + instrumentalists + choir + orchestra + conductor) and then I use 'copy tag' to copy this often long chain of people to a (non-virtual) field 'performers' where MB can split the chain in individual contributors again. Most of the time it works fine, but sometimes the copying goes wrong: most tracks are ok, but some remain empty, even after repeated attempts. There was nothing in the empty field before. What can be the problem?
3.
The performance for auto-application is a lot better than it was, but I still prefer to use them non-auto only. The column headers are sometimes still shaking a bit, performance is slow and some tasks must wait till the auto-app is done.
4.
I have experimented a bit with the 'change case' command. Even not enough, I already have the feeling that it could (should?) be made more fancy. I cannot come with a proper proposal yet, but I am thinking of 'language groups', so that a user can define by language what words he wants capilatized or not. It seems very difficult to make 'one box' that should serve all languages. Especially with short words like a, à, de, der, des, di and words with an apostrophe the rules vary per language, so it would be nice if the user has an option to select which language/rules to apply. Possible?

Keep in mind: I first of all want to express apprecation about the plugin. And in fact just my remark no 1 is about something I hope can be changed/solved soon. See if you have time for it. The rest can wait.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2013, 03:21:23 PM
@WimYogya
Thank you for good words.

1.
What I really miss most is a small feature: when doing LOTS of editing it is a pity that the Search & Replace (and other?) command can not memorize its most recent settings (looking for ... in ... and replace with ...). When cleaning up 1000+ titles of all kinds of mess, it is annoying that after every new instance I have to close S&R, and scroll down to TITLE again, and retype the search/replace values, even if there is just 1 character difference. Please store the settings (at least during one MB session) and store the location as well.
If you mean standard Search & Replace command (not ASR), then it's native MB command and have no control over it. Ask Steven to enhance this command.

2.
With the copy tag command I sometimes have a problem. I created a 'virtual performers' field (combining vocalists + instrumentalists + choir + orchestra + conductor) and then I use 'copy tag' to copy this often long chain of people to a (non-virtual) field 'performers' where MB can split the chain in individual contributors again. Most of the time it works fine, but sometimes the copying goes wrong: most tracks are ok, but some remain empty, even after repeated attempts. There was nothing in the empty field before. What can be the problem?
It very strange and I have no clue for this. I've never seen such behavior myself.

3.
The performance for auto-application is a lot better than it was, but I still prefer to use them non-auto only. The column headers are sometimes still shaking a bit, performance is slow and some tasks must wait till the auto-app is done.
I'm afraid I cannot make plugin commands more responsive when ASR is running in background.

4.
I have experimented a bit with the 'change case' command. Even not enough, I already have the feeling that it could (should?) be made more fancy. I cannot come with a proper proposal yet, but I am thinking of 'language groups', so that a user can define by language what words he wants capilatized or not. It seems very difficult to make 'one box' that should serve all languages. Especially with short words like a, à, de, der, des, di and words with an apostrophe the rules vary per language, so it would be nice if the user has an option to select which language/rules to apply. Possible?
Theoretically possible, but actually a dictionary of excluded words for every language is needed. Who will make such dictionaries? Windows and .net by themselves don't allow to retrieve list of short service words for a given language :(
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 23, 2013, 08:29:47 AM
Quote
If you mean standard Search & Replace command (not ASR), then it's native MB command and have no control over it. Ask Steven to enhance this command.
Yes, that is what I meant - will ask Steven about it. Thanks.

Quote
It very strange and I have no clue for this. I've never seen such behavior myself.
I can't find a pattern either. Normally all is normal. Sometimes one or two tracks 'refuse' to copy the v-performers to the performers, sometimes a whole cd in a pack of 10 cd's misses the performers. Re-applying the app sometimes helps, often manual copying is the only solution. Strange.

Quote
I'm afraid I cannot make plugin commands more responsive when ASR is running in background.
Personally I can live with the manual application of the presets. Just want to let you know that things improved but for me not fast/stable enough yet.

Quote
Theoretically possible, but actually a dictionary of excluded words for every language is needed. Who will make such dictionaries? Windows and .net by themselves don't allow to retrieve list of short service words for a given language
Don't understand your last remark. No one has to create dictionaries, to my opinion. As long as they can select a (customizable labeled) language and per language enter the words that they wish to exclude. For instance: as a Dutchman I wished I could set up 'casing' rules for my Dutch songs which sometimes are different from (or non-existent in) other languages. Same goes for classical music in German or Italian. But maybe there are programming limits in providing this, don't know.

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 23, 2013, 09:54:56 AM
Don't understand your last remark. No one has to create dictionaries, to my opinion. As long as they can select a (customizable labeled) language and per language enter the words that they wish to exclude. For instance: as a Dutchman I wished I could set up 'casing' rules for my Dutch songs which sometimes are different from (or non-existent in) other languages. Same goes for classical music in German or Italian. But maybe there are programming limits in providing this, don't know.
Ahhh... Seems I understood you. Do you mean implementing savable/customizable presets in 'Change case' command like in 'Library Reports' command? Yes, its possible, its not very hard to make.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 23, 2013, 03:27:25 PM
@Boroda
Don't know what you mean with the Library Reports command, I never used it and can't quickly see what it does and how it works.
But yes, I mean customizable/savable presets i 'change case'.
You may have much better ideas about configuration/layout of the preset I have in mind, but I think of adding new customizable options like this:
(with [  ] I mean to display a checkbox, but if I put an x in it, the graphic display in this forum makes it a black square...)

When changing case I want to apply the following language set(s):
[  ] [English, fixed?]      exclude the following words: [ a the if as but etc]    
[  ] [French, fixed?]                                                      [ le la les il l' etc]
[  ] [German, fixed?]                                                    [ der die das des ein du etc]
[  ] [Spanish, variable?]                                               [ el les los las un uno etc]
[  ] [Italian, variable]                                                   [il un uno una l' e i etc]
[  ] [Dutch, variable]]                                                   [de het een 'n 'm m'n z'n 't etc]
[  ] ALL OF THE ABOVE    

What you think?


PS:
About the S&R: Steven already implemented the 'remember location and search field' feature and released a new working patch.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 23, 2013, 04:49:08 PM
Not exactly what you asked for but something like it is already implemented:

(http://img339.imageshack.us/img339/4622/20130223204407greenshot.png) (http://imageshack.us/photo/my-images/339/20130223204407greenshot.png/)

Uploaded with ImageShack.us (http://imageshack.us)

If you change the list of excluded words & click 'Proceed', then previous list of excluded words will be automatically saved.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 23, 2013, 08:18:36 PM
Well, this seems it is VERY MUCH what I had in mind.
I just had missed the dropdown arrow and not seen yet that I can create multiple rows with words-to-exclude.
If I understand it well:
1. I can create as many of those 'rows' as I wish?
2. I can give each language a separate list of excluded words?
3. I could (for example) copy all the words from my English list + my Dutch list + my Italian list to the top list which should include ALL words-to-exclude?

And could you please explain the use of the button 'reapply rules to new tag'?
When and why and how to use it?

Thanks for your great assistance!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2013, 05:01:24 AM
1. I can create as many of those 'rows' as I wish?
No, as far as I remember up to 10 rows can be saved.

2. I can give each language a separate list of excluded words?
Yes.

3. I could (for example) copy all the words from my English list + my Dutch list + my Italian list to the top list which should include ALL words-to-exclude?
Yes, but you have to manually create all-words-to-exclude list.

And could you please explain the use of the button 'reapply rules to new tag'?
When and why and how to use it?
You can change casing rules & click 'Reapply rules to new tag' button to apply modified rules to already changed values without saving new values to tags, i.e this button allows you to make multiple steps without saving changes to tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 24, 2013, 07:06:17 AM
It's all clear.
Will experiment more.
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2013, 07:26:23 AM
Notice that excluded words remain unchanged, not become lowercased! That's why multiple steps ('Reapply rules' button) may be useful.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 24, 2013, 07:41:39 AM
What is "Import New" button supposed to do? "Import All" button imports 69 presets, but "Import New" imports no preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2013, 08:04:24 AM
'Import new' button doesn't import deleted 'official' presets. 'Import all' imports/reimports all 'official' presets.

Quote
...but "Import New" imports no preset.
Its because you have all presets up to date.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 24, 2013, 08:12:26 AM
Its because you have all presets up to date.

I see. I thought it would open a selection dialog of available official presets to choose what to import.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 24, 2013, 09:42:44 AM
Notice that excluded words remain unchanged, not become lowercased! That's why multiple steps ('Reapply rules' button) may be useful.

Makes sense, but I might have overlooked it. Thanks for the reminder!
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 24, 2013, 07:24:02 PM
@Boroda
Did you recently change the font color in the ASR old/new value boxes?
If so, it is not an improvement, on the contrary:
Most values now are 'white' or 'invisible' on a white background - can only be seen if a row is selected - in my case: white letters on red background.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 24, 2013, 09:09:03 PM
Most values now are 'white' or 'invisible' on a white background - can only be seen if a row is selected - in my case: white letters on red background.
Same here.  White on white unless the row is selected.  Just recently updated to the 2013-02-18 version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 25, 2013, 01:02:16 PM
@WinYogya
@phred
Try this version (http://www.mediafire.com/download.php?kc2ov6b06y3oa9c).
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 25, 2013, 02:59:07 PM
Works for me.
Thank you, Sir.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 27, 2013, 05:59:12 PM
Yes, works for me too.,
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on February 28, 2013, 06:14:04 AM
I have a strange problem with this plugin. It took me a while to figure out what it was but it is definitely this plugin that causes it.

I have just installed it.
I right click>edit on a file called "Italian Concerto in F major, BWV 971 - 2. Andante".
Add "test" to the comment tag, save.
I look at the file now and all the numbers have disappeared from the title so it appears something like "Italian Concerto in F major, BWV - . Andante"

I had this problem a few months ago and reinstalled MB and built up all my preferences from scratch in case there was something wrong and everything was ok but I just wanted to use this plugin again for something and realised that it was doing this weird thing again. I don't know if it is conflicting with something but this only happens when the plugin is enabled. As it happened a few months ago I don't think it is related to the version of MB (I used the lasted version patch posted here).

I'm using the following rule for auto organisation, in case that is related:

$Sort(<Album Artist>)\<Year (yyyy)> - <Album>\<Disc-Track#>. <Title>

Obviously this doesn't seem to be happening to anyone else so I don't expect that much can be done about it but I thought I would report it anyway, just in case anyone else if suffering the same problem without knowing what is causing it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 28, 2013, 07:01:34 AM
@beeing good:

Does it happen only with FLAC files? What happens when you edit tags of other types of files?
Title: Re: Additional Tagging and Reporting Tools
Post by: ajfudge on February 28, 2013, 08:56:20 AM
Hi there. I've only been using MusicBee for a week (in love with it already) so I'm still overwhelmed by its many functions. So if anyone could teach me how to execute this thing I want to do (I am using v2.1):
Scan tags and interpret the symbols "," (comma)" "/" (slash) or ";" (semicolon) as separator and automatically split the values (like in multiple artist or composer). I have a large music collection so I'm hoping I wouldn't have to do this manually.

(I'm also hoping that I'm posting at the right forum)
Thanks!

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2013, 09:38:11 AM
@ajfudge
Hi. 1st of all select all files you need and open standard (not Advanced) Search & Replace command and untick 'Use regular expressions' option. Select 'Artist' or 'Composer tag'. Then search for '; '  (semicolon and space) and replace with ';' (semicolon). Then search for ', ' (comma and space) and replace with ';' (semicolon). Search for ',' (comma) and replace with ';'. Search for '/' and replace with ';'.  

Now you should have only ';' as separator of multiple artists/composers.

Open 'Swap tags' command. Select the same source and destination tag (eg 'Artist'). Be sure that 'Smart swap' is ticked. Swap tags. This should convert ';'-separated list of artists to multiple artists.
Title: Re: Additional Tagging and Reporting Tools
Post by: ajfudge on February 28, 2013, 10:15:16 AM
Hi boroda74,

I can't seem to find the Swap Tags command  ???
Where do I find it?
Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: beeing good on February 28, 2013, 01:59:28 PM
@beeing good:

Does it happen only with FLAC files? What happens when you edit tags of other types of files?

I have only tried with mp3s but I can try with FLAC next time I have some.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 28, 2013, 02:14:16 PM
@beeing good:

Does it happen only with FLAC files? What happens when you edit tags of other types of files?

I have only tried with mp3s but I can try with FLAC next time I have some.

For some reason I thought it could be a cuesheet related problem with FLAC files. My mistake then.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2013, 04:46:54 PM
I can't seem to find the Swap Tags command  ???
Where do I find it?
Seems that you don't have 'Additional Tagging and Reporting Tools' installed. Download this plugin from the 1st post on this topic and install it. See 'Tools->Tagging Tools->Swap Tags' menu item.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 01, 2013, 07:30:24 AM
@beeing good:
Been doing lots of manipulations in my first month in MB, including the ASR presets.
Many of them classical movements similar to your example.
Never came across a problem like yours.
Title: Re: Additional Tagging and Reporting Tools
Post by: ajfudge on March 01, 2013, 10:51:02 AM
I can't seem to find the Swap Tags command  ???
Where do I find it?
Seems that you don't have 'Additional Tagging and Reporting Tools' installed. Download this plugin from the 1st post on this topic and install it. See 'Tools->Tagging Tools->Swap Tags' menu item.
I misread the instructions on page 1. I actually thought that v2.1 already has this plugin integrated in MusicBee.  :P
Anyway, installed and tried per your instruction, and I noticed that some, if not all (I did not check every track), tracks have artists already split after performing Search and Replace. That's nice.  :D

Anyway, here's another question: in some tracks, the name of the featured artist is on the title, now how do I copy the name of the artist to the artist tag field? Thanks again.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 01, 2013, 12:38:09 PM
Anyway, here's another question: in some tracks, the name of the featured artist is on the title, now how do I copy the name of the artist to the artist tag field?
Give some real example.
Title: Re: Additional Tagging and Reporting Tools
Post by: ajfudge on March 01, 2013, 12:48:09 PM
example:
The file has the following tags:
Title:     Song 1 (ft. Band Zero)
Artist:   Singer

I know how to add "Band Zero" to Artist manually, but in the cases of tagging many tracks, how do I search every Title that has "(ft. )" and then add the name/s after the word "ft." to Artist?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 01, 2013, 01:43:37 PM
@ajfudge:
This will require a lot of manipulating - it will only be worth it in my opinion if you have a few hundreds of these.
With the ASR plugins you will have to take several steps, but before that you should filter all titles mentioning 'contributing artists' and standardize the label for it.
It can be ft. ft feat. feat. featuring & with vs vs.  etc...
After you have found all tracks with all these variables, use general search and replace (not the ASR plugin) to replace the variables step by step by a uniform unique character (example: #).
Then use the ASR plugins to split the title tag in two separate tags, using the # as a splitter. The contributing artist could be stored in an empty field such as TEMP (you can create that yourself.
Then use the copy tag plugin to add the newly isolated contributing artist to the end of the original one, separated by ;  (see the bottom S&R features for that)

Quite some work - but possible...
Title: Re: Additional Tagging and Reporting Tools
Post by: ajfudge on March 01, 2013, 03:41:31 PM
This will require a lot of manipulating - it will only be worth it in my opinion if you have a few hundreds of these.
With the ASR plugins you will have to take several steps, but before that you should filter all titles mentioning 'contributing artists' and standardize the label for it.
It can be ft. ft feat. feat. featuring & with vs vs.  etc...
I actually have more than a couple hundred of those files.
I understand that this kind of process won't be as quick as a one-click after boroda74 taught me to formalize my separator under the same symbol which is ";" (semicolon).  so I took the initiative to Search and Replace "feat.", "featuring", etc. so they'd all be the same "ft."


After you have found all tracks with all these variables, use general search and replace (not the ASR plugin) to replace the variables step by step by a uniform unique character (example: #).
Then use the ASR plugins to split the title tag in two separate tags, using the # as a splitter. The contributing artist could be stored in an empty field such as TEMP (you can create that yourself.
Then use the copy tag plugin to add the newly isolated contributing artist to the end of the original one, separated by ;  (see the bottom S&R features for that)

Quite some work - but possible...
You got me confuse here. The format I use for tracks with a featured artist is this:
Title (ft. Featured Artist)

Note that the featured artist is enclosed in parenthesis with the word "ft." to offset it.
I want to copy the names of the featured artist in the artist tag, but I also want to retain the name  of the featured artist in the title, if it's possible.
I hope I explained clearly.
Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 01, 2013, 03:52:59 PM
Here's my suggestions using a virtual tag.

1. Copy and paste the following to label and formula box under Tags(1)> Define New Tags

FeatArtist=$Split($Split(<Title>,"(ft.",2),")",1)

Add the column to main panel and sort by it.
Select all the tracks that have a value in the field.

2. Go to Tools> Tagging Tools> Copy tag

Source: FeatArtist Target: Artist
Tick "smart copy" and "append source tag..." and put ";" in the box
Preview and Proceed.

3. Select all those tracks, open ASR preset pane, find "Generate Display Artist..." and run it.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 01, 2013, 04:24:01 PM
@redwing:
Sounds like a good suggestion although I am not expert enough to understand it. But if I would need the same I would sure test it! ;-)
@ajfudge:
In general: MB itself plus the excellent ASR plugin options make almost every manipulation possible, is my experience after 1 month.
The question often remains: is it worth the lot of work that you have to do before you have everything exactly uniformised in your desired format.
I am struggling with that question myself too.
Options are endless, time and energy are not...
Success!
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 02, 2013, 10:22:49 AM
As I noticed before: sometimes (with some presets?) ASR seems to skip certain or all fields.
As far as I can analyze it now, it is just a matter of refreshing: after a restart the values have been added to the respective fields.
I experienced it a few times today with the 'add zeros to track number' presets: after applying the preset to 15 tracks of 1 cd nothing changed.
Repeating the application didn't make a change.
The restart did: the 01, 02 etc were there...

Later the same happened when I wanted to combine two fields and append an opera title to the beginning of the title field.
No changes visible until after a restart.

Please check the refreshing issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 02, 2013, 10:54:34 AM
What's happened if you hit F5 button? Are fields refreshed?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 02, 2013, 02:00:39 PM
Seems ok after hitting F5.
Still, autorefresh would be nicer (and is sometimes automatically done)
Could you let it ALWAYS happen? ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 02, 2013, 02:22:00 PM
Seems ok after hitting F5.
Then it's a bug in plugin. I'll check auto-refreshing in it. Last question: Fields aren't updated when preset is auto or manually applied?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 02, 2013, 02:34:01 PM
I dont use autoreply (yet) coz it (still) slows down my performance.
So my experience only comes from manual application.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 02, 2013, 07:11:14 PM
@WimYogya
Please try this version (http://www.mediafire.com/download.php?kwgwlwvfdz186in)
Title: Re: Additional Tagging and Reporting Tools
Post by: superstar19 on March 05, 2013, 12:31:29 AM
I keep getting this error (just downloaded the latest beta):

Quote
Some tag names are duplicated. Plugin is not properly initialized.


I'm using MB 2.1.4770 and the latest plugin (also tried the 2013-03-02 version), and get the same message.   Is there something else I'm missing?  I've loaded the files to the Plugins folder, but I still get this error.  I'm running MB on a desktop running Windows XP.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 05, 2013, 12:43:19 PM
Did you change any field names/labels? Check if some of them are duplicates. I had that before.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 05, 2013, 12:45:17 PM
@Boroda:
Newest version solves most of the autorefresh problems. The rest is - as I think - part of an existing problem on my PC where autorefresh is sometimes not perfect. Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 05, 2013, 01:46:08 PM
@Boroda:
Newest version solves most of the autorefresh problems.
Good news
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 05, 2013, 01:47:39 PM
I'm using MB 2.1.4770 and the latest plugin (also tried the 2013-03-02 version), and get the same message.   Is there something else I'm missing?  I've loaded the files to the Plugins folder, but I still get this error.  I'm running MB on a desktop running Windows XP.
What localization of MB are you using?
Title: Re: Additional Tagging and Reporting Tools
Post by: superstar19 on March 05, 2013, 01:53:16 PM
I'm using MB 2.1.4770 and the latest plugin (also tried the 2013-03-02 version), and get the same message.   Is there something else I'm missing?  I've loaded the files to the Plugins folder, but I still get this error.  I'm running MB on a desktop running Windows XP.
What localization of MB are you using?
I'm just using the standard install (english?) without any localisation added.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 05, 2013, 02:06:18 PM
@superstar19
Try to upgrade MB to latest version (http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip).
Title: Re: Additional Tagging and Reporting Tools
Post by: superstar19 on March 05, 2013, 07:01:20 PM
Thanks for the follow-up.  I'll give it a try when I get home.
Title: Re: Additional Tagging and Reporting Tools
Post by: superstar19 on March 05, 2013, 10:53:37 PM
@superstar19
Try to upgrade MB to latest version (http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip).
Thanks.  That worked.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 13, 2013, 04:01:06 AM
Thanks a lot for implementing my request of text file to tag feature. Later I'm going to post a how-to tip for the feature.

BTW with the new version, Apply after Preview is not working for some reason with any preset and copy tag commands. Apply without Preview is working fine.   
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 13, 2013, 05:45:59 AM
@redwing
Thanks for bug report. Its fixed. Redownload plugin from 1st post.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 13, 2013, 06:04:04 AM
Now working perfect. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 13, 2013, 07:36:27 AM
Two additional bugs:

1. The ASR preset for "Split '<Tag 1>' to tags '<Tag 2>', '<Tag 3>'" does not seem to be working properly. After applying it, the ASR running message keeps being displayed on the status bar without changing tags.

2. Text file to tags feature does not read unicode text file properly.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 13, 2013, 08:41:41 AM
About 2.
For unicode text 1st 2 chars should be Byte Ordering Marker. I created UTF-8 text in Notepad and all worked fine.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 13, 2013, 08:47:20 AM
About 1.
Didn't find any problem. Is some preset ticked for autoapplying in your case?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 13, 2013, 09:18:15 AM
About 1.
Didn't find any problem. Is some preset ticked for autoapplying in your case?

Yes, that seems to be the case. It's working fine without having auto-applied preset. But not working properly with having one.

About 2.
For unicode text 1st 2 chars should be Byte Ordering Marker. I created UTF-8 text in Notepad and all worked fine.

UTF-8 is working fine. I meant UTF-16LE as "Unicode" in encoding option of Windows Notepad.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 13, 2013, 11:44:40 AM
Yes, that seems to be the case. It's working fine without having auto-applied preset. But not working properly with having one.
What preset was ticked for autoapplying?

UTF-8 is working fine. I meant UTF-16LE as "Unicode" in encoding option of Windows Notepad.
Yes, there was an error. Its fixed. See 1st post for download link.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 13, 2013, 12:20:08 PM
That's "Swap first and last name of artist and adding <Custom text> - 2" preset. Only 2 out of 8 tracks worked with the preset auto-applied.
Title: Re: Additional Tagging and Reporting Tools
Post by: TheAlfred on March 16, 2013, 10:06:41 AM
@superstar19
Try to upgrade MB to latest version (http://musicbee.niblseed.com/V2_1/MusicBee_Exe_Patched.zip).

I am having the same problem with "some tag names are duplicated...blah"... Already installed the latest version of the plugin.
What is this "latest", patched version of MB? Is it your own build? Will this patch be included in the official version?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2013, 10:44:47 AM
What is this "latest", patched version of MB? Is it your own build? Will this patch be included in the official version?
It's latest build made by Steven which is not yet officially released. Later this patch will be included in official release.
Title: Re: Additional Tagging and Reporting Tools
Post by: MeeMeeMee on March 17, 2013, 08:34:32 AM
Sorry if this has been asked and answered:
Does this plugin (and, in fact, others) respect the Save tags to the music file setting, under Tags(1)?
i.e., if I disable that option and use this plugin to make changes to tags: Will those changes be applied just to MB's data-base?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2013, 08:51:31 AM
It would be great if null can be selected for tags with ASR presets:

http://getmusicbee.com/forum/index.php?topic=9182.0 (custom fields were used instead)
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on March 18, 2013, 04:29:30 PM
I just started using it and the first task (copying info from Performer to Musician Credit List) went beautifully.  Thanks!

Now I'm starting on more complicated stuff, and may be back to ask for help if I can't figure it out...

In the meantime, I've discovered that while typing in this plug-in, hotkey combinations are transmitted to MB as though I weren't typing in any field.  I don't know if you can fix this, or if Steven would need to.

---

If anyone else would find it useful, I've come up with a formula for converting musician credits from "role; Musician" to "Musician (role)".
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2013, 12:27:05 PM
Sorry if this has been asked and answered:
Does this plugin (and, in fact, others) respect the Save tags to the music file setting, under Tags(1)?
i.e., if I disable that option and use this plugin to make changes to tags: Will those changes be applied just to MB's data-base?
I didn't test it well, but plugin should respect these settings

In the meantime, I've discovered that while typing in this plug-in, hotkey combinations are transmitted to MB as though I weren't typing in any field.  I don't know if you can fix this, or if Steven would need to.
I tried to make a hack to workaround such keys, but didn't succeed. So I need Steven's help to intercept some common keys such as space or enter assigned as hotkeys.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on March 24, 2013, 04:13:33 AM
I tried to make a hack to workaround such keys, but didn't succeed. So I need Steven's help to intercept some common keys such as space or enter assigned as hotkeys.

That's okay, I just took out that hotkey.  Didn't use it much anyway.  :)

Since then, I've made a bit of a mess and I'm not sure how to fix it.  I was trying to copy the Writer tag (from Musicbrainz) into the Composer tag.  

First, somehow I ran the copy without meaning to - I was just trying to check/uncheck specific files.  

Second (or maybe this should be first), the reason I was fiddling with which files to apply it to was because it wasn't handling the "append to" command well, even though I had "smart copy" option selected.  If I told it to append with ; as a separator, it wanted to put ; even in tags that should be blank.  If I told it not to use a separator, then when there was a value in both Writer and Composer it mushed them together.

And somehow the tags where Writer had multiple values got copied as a single value.  As soon as I go into the file and open the Composer split screen, it sorts them out correctly without my doing anything.  But until I do that, I have values showing up in Library Explorer like "Andy SelwayJules Hodgson; Sascha Konietzko; Lucia Cifarelli; Andy Selway".  Which somehow fail to make the associated tracks appear in the main window, even though they show up in Library Explorer...

Can you offer any advice in sorting this out?  I hope it can be solved without editing every single file by hand...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 24, 2013, 09:39:41 AM
If I told it to append with ; as a separator, it wanted to put ; even in tags that should be blank.  If I told it not to use a separator, then when there was a value in both Writer and Composer it mushed them together.
I have an advice, but think its too late. You should copy Writer to Composer without placing ';' and only for tracks with empty Composer. Then copy Writer to Composer placing ';' only for tracks with not empty Composer.

And somehow the tags where Writer had multiple values got copied as a single value.  As soon as I go into the file and open the Composer split screen, it sorts them out correctly without my doing anything.  But until I do that, I have values showing up in Library Explorer like "Andy SelwayJules Hodgson; Sascha Konietzko; Lucia Cifarelli; Andy Selway".  Which somehow fail to make the associated tracks appear in the main window, even though they show up in Library Explorer...
Try the following: select all tracks with single-value-composer. Use 'Swap tags' command with Composer selected as both source and destination tags. Tick 'Smart swap'. Click proceed. This should convert ;-separated value to multiple values for Composer.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 24, 2013, 09:40:58 AM
It would be great if null can be selected for tags with ASR presets:

http://getmusicbee.com/forum/index.php?topic=9182.0 (custom fields were used instead)
I'll add 'null' tag to ASR.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on March 24, 2013, 02:34:43 PM
Try the following: select all tracks with single-value-composer. Use 'Swap tags' command with Composer selected as both source and destination tags. Tick 'Smart swap'. Click proceed. This should convert ;-separated value to multiple values for Composer.

Awesome, thanks!  I'll give that a try.

Update: Actually, I think all it needed was a force rescan.  I feel silly.  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 25, 2013, 12:16:21 PM
Thanks a lot for implementing null field! :) I'll edit how to instructions later.

Edit: It's done.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 25, 2013, 08:55:29 PM
1. How about going one step further by adding <clipboard> tag to Copy Tags command pane so that the user even don't have to save tags to text file?

2. It would be great if ASR presets support <text file> or suggested <clipboard> tags.

3. Is it possible to enter or insert <tab character> in "Custom Text" box with Split ASR presets?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 26, 2013, 09:26:47 AM
1. How about going one step further by adding <clipboard> tag to Copy Tags command pane so that the user even don't have to save tags to text file?
I think its possible, I need to investigate this.

2. It would be great if ASR presets support <text file> or suggested <clipboard> tags.
Don't want to do this. Too difficult.

3. Is it possible to enter or insert <tab character> in "Custom Text" box with Split ASR presets?
Not sure, try '\t' escape char.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 26, 2013, 10:27:24 AM
3. Is it possible to enter or insert <tab character> in "Custom Text" box with Split ASR presets?
Not sure, try '\t' escape char.

That doesn't work. I found a workaround: copy and paste the invisible tab char from notepad. But can't find a way to directly enter it with MB either.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 26, 2013, 10:57:58 AM
@redwing
1. I've added <Clipboard> pseudo tag to 'Copy tag' command.
2. I'll make \t to work as tab char.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 26, 2013, 11:11:07 AM
@redwing
1. I've added <Clipboard> pseudo tag to 'Copy tag' command.
2. I'll make \t to work as tab char.

Wonderful! I just tried and it worked flawlessly, with the error message shown when the number of lines are different. Excellent work!
Let me know when tab is done. I'll write 2nd part of the how-to instructions with this new feature.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 26, 2013, 02:37:02 PM
Let me know when tab is done. I'll write 2nd part of the how-to instructions with this new feature.
Its done. See download link in the 1st post.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 26, 2013, 07:15:14 PM
Let me know when tab is done. I'll write 2nd part of the how-to instructions with this new feature.
Its done. See download link in the 1st post.

Great! It's working perfect!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 05:29:15 AM
When using Merge or Split ASR presets with more than two delimiters, if source tag is the same as one of target tags it's not working properly. I suspect it has something to do with its multiple step process. Can you fix it somehow or do users have to avoid such use?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 09:02:56 AM
This is intended behavior. Actually you can use destination tag same as source tag with split/merge presets, but destination tag should be the last customizable tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 12:57:30 PM
This is intended behavior. Actually you can use destination tag same as source tag with split/merge presets, but destination tag should be the last customizable tag.

Then, cannot use it if it's not the last tag?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 01:47:41 PM
Then, cannot use it if it's not the last tag?
No, you can use if not last tag, but then source tag will be substituted with replaced value and this substituted value will be used in subsequent steps. This is mostly likely undesirable.

P.S. Sorry for my English
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 02:08:14 PM
Then, cannot use it if it's not the last tag?
No, you can use if not last tag, but then source tag will be substituted with replaced value and this substituted value will be used in subsequent steps. This is mostly likely undesirable.

P.S. Sorry for my English

That's exactly what I understood (your English is superb). My question was if there's any way you can modify regex/steps to perform the task when it's not last tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 04:32:58 PM
My question was if there's any way you can modify regex/steps to perform the task when it's not last tag.
Lets see 2 examples: 'Comment' tag with value...

Example#1 ... 'Artist1 - Title1 - Comment1' is split to tag#1 'Artist', custom_text#1 '-', tag#2 'Title', custom_text#2 '-', tag#3 'Comment'. In this example 'Artist1' will be extracted on the 1st step ('Comment' tag remain unchanged), 'Title1' will be extracted on the 2nd step ('Comment' tag remain unchanged) and 'Comment1' will be substituted in 'Comment' tag on the last step.

Example#2 ... 'Comment1 - Artist1 - Title1' is split to tag#1 'Comment', custom_text#1 '-', tag#2 'Artist', custom_text#2 '-', tag#3 'Title'. In this example 'Comment1' will be substituted in 'Comment' tag on the 1st step, no match will be found on the 2nd step (so 2nd step will be effectively skipped) and no match will be found on the last step (so last step will be effectively skipped).

NB: Only actual order of searches and replaces is important. Actual order is defined in preset editor and by order of customizable tags.

P.S. Hope I succeeded to explain how ASR works.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 06:05:51 PM
For example #2, this modification can handle the task.


(http://i.imgur.com/6PRkUqL.png)


Then with more null fields, all split/merge presets can handle the task automatically regardless of the position?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 06:27:38 PM
This one is better. No need for more null fields, and can handle all positions.


(http://i.imgur.com/JCQaw6d.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 07:07:42 PM
For example #2, this modification can handle the task.

(http://i.imgur.com/6PRkUqL.png)
No, <Null> is not <Temporary tag>. Writing to <Null> does nothing. Reading from <Null> always returns empty string. You can use 'Custom16' tag for example as temporary tag. Alternatively I could add <Temp> pseudo-tag to ASR.

edit:
Possibly (I'm not sure) <Null> tag is cached along with other tags in ASR, then your preset should work.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 07:39:27 PM
Both presets are working fine. The only problem is that the user cannot use <null> field to discard unnecessary string since it will overwrite the field. But the suggested <temp> tag would be the solution for that. So do you mean that the user have to do all these configurations? How about modifying merge/split presets like this? Any downsides? I can configure these myself, but whenever you update the plugin they will become useless.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 08:15:37 PM
BTW split presets are not parsing properly with period "." as delimiter.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 08:32:35 PM
Both presets are working fine.
This is unintended, but useful behavior :)

The only problem is that the user cannot use <null> field to discard unnecessary string since it will overwrite the field. But the suggested <temp> tag would be the solution for that. So do you mean that the user have to do all these configurations? How about modifying merge/split presets like this?
I'll add several <Temp#> pseudo-tags and will modify split/merge presets, so users can safely use any combination of customizable tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 08:34:07 PM
BTW split presets are not parsing properly with period "." as delimiter.
This is downside of allowing escape sequences like '\t'. Use '\.' instead of '.' as delimiter.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 08:36:41 PM
Both presets are working fine.
This is unintended, but useful behavior :)

The only problem is that the user cannot use <null> field to discard unnecessary string since it will overwrite the field. But the suggested <temp> tag would be the solution for that. So do you mean that the user have to do all these configurations? How about modifying merge/split presets like this?
I'll add several <Temp#> pseudo-tags and will modify split/merge presets, so users can safely use any combination of customizable tags.

Sounds great! Thanks!

BTW split presets are not parsing properly with period "." as delimiter.
This is downside of allowing escape sequences like '\t'. Use '\.' instead of '.' as delimiter.

Then only for period or any other characters? Maybe some notes should be displayed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2013, 09:10:28 PM
Then only for period or any other characters? Maybe some notes should be displayed.
For some chars. I think I should rollback to old behavior and make some special escape sequence for tabulation only (eg. <TAB> or something else).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2013, 11:37:25 PM
Then only for period or any other characters? Maybe some notes should be displayed.
For some chars. I think I should rollback to old behavior and make some special escape sequence for tabulation only (eg. <TAB> or something else).

That sounds reasonable. And consider to put a note on the preset window.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2013, 09:04:03 AM
@redwing
4 temp tags are added to ASR preset editor. '<tab>' (lowercased) special string is now used for tabulation in custom text. See 1st post for download link. Later I'll update ASR presets which will use new temp tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 28, 2013, 09:26:55 AM
@redwing
4 temp tags are added to ASR preset editor. '<tab>' (lowercased) special string is now used for tabulation in custom text. See 1st post for download link. Later I'll update ASR presets which will use new temp tags.

Yes, it's working perfect. And period "." too. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 28, 2013, 05:55:39 PM
Thanks! Split presets are now working perfect. But I don't see any changes in Combine presets that have the exact opposite problem (not working properly if target tag is not first source tag).
This is my modification. Would you consider to modify them too?

(http://i.imgur.com/e7I9CJq.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2013, 06:53:01 PM
@redwing
Thanks. I've modified combine presets. Download link on the 1st post is updated.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 28, 2013, 07:10:54 PM
Great! It's working good. Now I am gonna post how-to instructions about clipboard tag feature.
Thanks for your hard work!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2013, 07:15:34 PM
Thank you, redwing! You did half of my work testing my plugin! :)
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on April 01, 2013, 11:15:13 AM
Hello @boroda
Would ASR have an option (or could it be created?) to make the following rather complex editing a bit easier?
It has to do with track/title numbering of mainly classical works like operas.
Let's say I have 3 cd's of the opera Rigoletto. Cd's already numbered 1-2-3. Tracks already numbered for each cd: 1-24.
The tracks already have their correct title.
But I want to change the title as in the following format:
<album/opera> - <cd>.<tracknr>. <tracktitle>

With the copy tag feature it is very easy to insert the album/opera name at the beginning of the title field.
But is there a way to add the cd number + track number as well?

An even more complicated version of this problem is the following:
The opera has 3 acts but covers only 2 cd's. So you can not use the disc number as the act number. Act 2 could already begin towards the end of cd 1, so the track numbers there will not correspond with the act-track-number. I don't see how ASR or another clever tool could create automatic numbering there... Or....?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 01, 2013, 12:23:33 PM
Let's say I have 3 cd's of the opera Rigoletto. Cd's already numbered 1-2-3. Tracks already numbered for each cd: 1-24.
The tracks already have their correct title.
But I want to change the title as in the following format:
<album/opera> - <cd>.<tracknr>. <tracktitle>

With the copy tag feature it is very easy to insert the album/opera name at the beginning of the title field.
But is there a way to add the cd number + track number as well?
Yes. 1st download latest plugin version. Then find ASR preset "Combine tags '<Tag 1>', '<Tag 2>', '<Tag 3>', '<Tag 4>' and write result in '<Tag 5>'". Set <Tag 1> to 'Album', <Custom text 1> to ' - ', <Tag 2> to 'Disk #', <Custom text 2> to '.', <Tag 3> to 'Track #', <Custom text 3> to '. ', <Tag 4> to 'Title', <Tag 5> to 'Title'.

An even more complicated version of this problem is the following:
The opera has 3 acts but covers only 2 cd's. So you can not use the disc number as the act number. Act 2 could already begin towards the end of cd 1, so the track numbers there will not correspond with the act-track-number. I don't see how ASR or another clever tool could create automatic numbering there... Or....?
Try to manually set disk# to 1,2,3 according to act#, then use native 'Renumber tracks' command.
Title: Re: Additional Tagging and Reporting Tools
Post by: ma_t14 on April 10, 2013, 10:41:17 AM
When trying to produce a library report with only the album artist field I get the following error

MusicBee v2.1.4847.37599 (Win6.2), 10 Apr 2013 10:40:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.LibraryReportsPlugin.exportTrackList()
   at MusicBeePlugin.LibraryReportsPlugin.buttonOK_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 10, 2013, 03:23:02 PM
I can reproduce this. I'll fix this bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 10, 2013, 04:08:14 PM
Its fixed. See 1st post on this topic.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2013, 05:43:32 PM
Have a look at this post: http://getmusicbee.com/forum/index.php?topic=9461.msg55880#msg55880

I was trying to auto-copy with TOY copy preset Love field to a custom filed. But the target field wasn't auto-updated unless the file is saved with an updated value. It would be great the field is auto-copied in real time without having to save files with an adjusted love value.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 14, 2013, 07:18:17 PM
Tested auto-copying rating field to a custom field.

1. POPM values are different from the original.
2. Bomb should be 0 and no rating should be no value, but currently both are auto-copied as 0 to a custom field.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 15, 2013, 10:26:37 AM
Have a look at this post: http://getmusicbee.com/forum/index.php?topic=9461.msg55880#msg55880

I was trying to auto-copy with TOY copy preset Love field to a custom filed. But the target field wasn't auto-updated unless the file is saved with an updated value. It would be great the field is auto-copied in real time without having to save files with an adjusted love value.
I asked Steven one question. Waiting for his response.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on April 22, 2013, 08:45:48 AM
Hello! I've been having trouble with this plugin. The Advanced Search and Replace doesn't import any of the presets. Also, my list of words in the Change Case doesn't save, prompting me to add them each time I open it. Been having this issue for the past couple of weeks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 22, 2013, 09:40:10 AM
Do you 'import all' or 'import new' ASR presets?

List of words is saved only if you click 'Proceed' button.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on April 22, 2013, 04:18:16 PM
If I clicked on import all, it says "69 preset(s) was/were successfully imported." But nothing shows up. And a list of words are saved when I click proceed. But when I restart MB, they disappear.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 23, 2013, 05:44:08 AM
Is there any error messages displayed when you import presets or exit MB (settings are saved to file on MB exit)?
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on April 23, 2013, 06:33:30 AM
Hmmmmm, didn't notice this until now. This keeps repeating around the time I use the plugin:

Quote
4/22/2013 8:16:57 AM - 6.1.7601.65536 - 2.1.4848.35226 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidCastException: Specified cast is not valid.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterSavedSettingsType.Write7_SavedSettingsType(Object o)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
   at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o, XmlSerializerNamespaces namespaces)
   at MusicBeePlugin.Plugin.SaveSettings()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=quLLvjgdAE_Nbqv7HRl0cvqQWB2pnoxzHVLUwc4mHJKE=.#=qzRKLcqgbtCzWHxB2sX1UDA==()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 23, 2013, 07:08:30 AM
First install latest plugin version (http://www.mediafire.com/download.php?9b6li2tx471pc94), then go to edit>prefs>plugins>additional tagging tools, click 'unistall' and restart MB immediately to clear saved plugin settings.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on April 23, 2013, 08:47:20 AM
I get this error when I try to uninstall it from the plugins section...

Quote
MusicBee v2.1.4860.34625 (Win6.1), 23 Apr 2013 0:46:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.IOException: The process cannot access the file 'C:\Users\Mark Jr\AppData\Roaming\MusicBee\mb_TagTools.Settings.xml' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.Delete(String path)
   at MusicBeePlugin.Plugin.Uninstall()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=qEZFsCbHjVDNOvCg3YjPCSEtOFBh4LLpcTeHbTs2gLs8=.#=qBET49i1uhGv7Oji4taeuBg==()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 23, 2013, 09:36:24 AM
The process cannot access the file 'C:\Users\Mark Jr\AppData\Roaming\MusicBee\mb_TagTools.Settings.xml' because it is being used by another process.
The file is plugin settings. Strange that its locked by another process. Can you delete this file manually (first exit MB)?
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on April 23, 2013, 03:16:49 PM
I can delete this manually. But when I restart MB, instead of the plugin being uninstalled, it's still there, just being shown as disabled.
So I manually deleted all traces of this plugin (even went into MB's settings and removed the dll of the plugin), reinstalled it, and it's at the same situation.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 23, 2013, 07:36:38 PM
Sorry, Maleko12. I have no idea what's happening.
Title: Re: Additional Tagging and Reporting Tools
Post by: Maleko12 on April 25, 2013, 12:12:39 AM
OK, I uninstalled and reinstalled MB and downloaded your plugin again. Now it works!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 25, 2013, 04:29:47 AM
Happy to hear that problem solved :)
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on May 04, 2013, 02:18:30 PM
There is a bug with the latest stable plugin version and ASR Preset Editor.

I've translated recently added presets into Polish. When updating I clicked 'Save' button after every translated preset. When I finished I clicked 'Save all and Close' button, and then closed MB. After MB restart I can see ASR Preset Editor asking me to click 'OK' button for every preset I've updated.
After a few clicks 'OK' button the following error occurred:

Code
MusicBee v2.1.4870.30402 (Win6.1), 4 maj 2013 15:05:

System.NullReferenceException: Odwo?anie do obiektu nie zosta?o ustawione na wyst?pienie obiektu.
   w MusicBeePlugin.ASRPresetEditor.saveSettings()
   w MusicBeePlugin.ASRPresetEditor.buttonOK_Click(Object sender, EventArgs e)
   w System.Windows.Forms.Control.OnClick(EventArgs e)
   w System.Windows.Forms.Button.OnClick(EventArgs e)
   w System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   w System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   w System.Windows.Forms.Control.WndProc(Message& m)
   w System.Windows.Forms.ButtonBase.WndProc(Message& m)
   w System.Windows.Forms.Button.WndProc(Message& m)
   w System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   w System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   w System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I'll send updated presets to you in a while (check your email and confirm please). Not all translations were saved successfully, but I've made a copy in a plain text file so I can fix this easily.

Update:
Looks like the translations were saved, only the translated presets names remained in English, but when I clicked 'Rename/edit...' button both title and the description were in Polish, so I clicked 'OK' for every preset, then 'Save' and 'Save and close' button at the end.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 04, 2013, 03:25:22 PM
Cant reproduce this. Seems to be specific for your PC. Try uninstall & reinstall plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 04, 2013, 04:12:56 PM
New version of plugin released. See 1st post for details.
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on May 05, 2013, 10:07:33 AM
I wonder if its possible to use ASR Presets for  batch "Mark as Having No Lyrics".
There are several requests for this feature on the forum:
http://getmusicbee.com/forum/index.php?topic=9207.0
http://getmusicbee.com/forum/index.php?topic=7735.0
http://getmusicbee.com/forum/index.php?topic=6026.0

It would be useful especially for:
audiobooks,
podcasts,
mp3 courses,
instrumental,
relaxation
or classical music.
What do you think  ???
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 05, 2013, 11:05:18 AM
Steven, if I its easy fix, could you provide writable tag to mark track as having no lyrics?
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on May 05, 2013, 11:35:27 AM
HasLyrics was only intended as readonly (it should have been put it under the properties section)
I will change it so if you set it to "MarkNoLyrics" it marks as having no lyrics and any other value undoes that flag
The 2.1 link has been updated
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 05, 2013, 12:33:25 PM
Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 05, 2013, 01:18:52 PM
@VX
New in 'Copy tag' command: now its possible to copy '<Null>' pseudo tag to 'Lyrics?' tag to mark track as having no lyrics. Copy '<+>' pseudo tag to clear this mark.

P.S. Use latest plugin & MB version for this.
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on May 05, 2013, 01:43:07 PM
@VX
New in 'Copy tag' command: now its possible to copy '<Null>' pseudo tag to 'Lyrics?' tag to mark track as having no lyrics. Copy '<+>' pseudo tag to clear this mark.

P.S. Use latest plugin & MB version for this.


Brilliant! Thank you both boroda and Steven for providing such a useful feature  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Iasc on May 06, 2013, 08:22:18 AM
@VX
New in 'Copy tag' command: now its possible to copy '<Null>' pseudo tag to 'Lyrics?' tag to mark track as having no lyrics. Copy '<+>' pseudo tag to clear this mark.

P.S. Use latest plugin & MB version for this.


thanks for this
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on May 09, 2013, 02:49:34 AM
New in 'Copy tag' command: now its possible to copy '<Null>' pseudo tag to 'Lyrics?' tag to mark track as having no lyrics

while <Null> is available to select in 'Tag 1', 'Lyrics?' is not available in 'Tag 2' field.
Do I have to define 'Lyrics?' as a custom tag for it to be useable?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 09, 2013, 07:57:03 PM
@Bee-liever
No, "Lyrics?" should be the last tag in destination tag list if you are using English localization.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on May 09, 2013, 09:58:52 PM
"Lyrics?" should be the last tag in destination tag list

Nope
(http://img845.imageshack.us/img845/8417/lyrics.jpg)

and I also have that Polish entry in the list of presets

Installed update like I have before; overwrote files and imported new presets.
But after posting here, and learning that "Lyrics?" should in the list, I uninstalled the plug-in and tried a complete re-install. Same result though.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 09, 2013, 10:26:26 PM
@Bee-liever:

It's not the ASR preset but Tools> Tagging Tools> Copy Tags... command dialog.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on May 10, 2013, 12:14:20 AM
@ redwing:

Thanks. No wonder I couldn't find it  ;)

I can read quite clearly now that it says 'Copy tag' command not 'Copy tag' preset

Must be my early onset Alzheimer's kicking in  :D
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 10, 2013, 08:50:03 AM
Since I setup two SoundCheck conversion presets auto-applied, I have experienced serious lags and freezes with bulk importing and editing. Even copying and pasting of tags of an album (tens of tracks) ends up freezing MB. Unticking the two presets resolves all those problems. I don't think I can recommend auto-applying of the presets in how-to any more. Do you think this is specific to those new presets or playlist-filtering auto-applying in general?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 10, 2013, 07:27:17 PM
I'm travelling now and can't check how plugin works. From my experience auto-applying works fine, but I cant tell what this depends upon. Maybe its a size of Library, maybe something else.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 10, 2013, 11:02:07 PM
Have a nice trip!

Regarding the issue, I'm not sure but it might have something to with MP3 conversion presets. Having "track gain mp3 conversion preset" auto-applied, even copying and pasting a single MP3 file sometimes freezes MB without leaving any error log. I remember I had the same freezing issues when I tried to convert RG values to SC values with that preset. So maybe it's not about auto-applying but about the preset. When you have time, have a close look at those mp3 conversion presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 11, 2013, 02:22:22 AM
I get the same hanging problems as Redwing if I have the preset 'Convert Track/Album Gain to SoundCheck mp3' selected for auto-apply. As with him, removing the auto apply instantly fixes the problems with MusicBee.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 11, 2013, 10:33:47 AM
Having "track gain mp3 conversion preset" auto-applied, even copying and pasting a single MP3 file sometimes freezes MB without leaving any error log. I remember I had the same freezing issues when I tried to convert RG values to SC values with that preset. So maybe it's not about auto-applying but about the preset. When you have time, have a close look at those mp3 conversion presets.
Does this happen only with mp3 preset? Not with m4a?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 11, 2013, 01:32:20 PM
It seems so. I didn't have any problem converting thousands of m4a tracks at once with that preset. But with mp3 preset, I had to use for a small group of tracks repeatedly, having freezing issues occasionally.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2013, 03:26:10 AM
This version (http://www.mediafire.com/download.php?k0r52fslqpc2pqr) works fine for me. I don't remember if I changed something comparing to last 'official' version.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 12, 2013, 12:00:33 PM
I don't know how you are testing. But this version is worse at least for me, hangs at almost every twenty mp3 files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2013, 12:53:51 PM
Just have tried with 590 tracks. No problem here.
Actually I don't understand how auto-applied presets could hang up UI, because they are executed in background thread, not in UI thread.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 12, 2013, 01:07:52 PM
I didn't try auto-apply. I tried converting RG to SC values, and it hanged a lot. After closing and relaunching MB, re-running for the hanged track individually worked most time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2013, 03:23:13 PM
Well, manual application works fine for me too.

(http://imageshack.us/a/img849/6431/20130512181603greenshot.png)

I'll leave it as is for now.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2013, 10:17:03 AM
You're right. It wasn't the presets but my settings file.

Later I noticed even editing a tag of some mp3 files sometimes crashed MB. So I launched MB with no settings file, and the problem was gone. Then I set both mp3 and m4a presets auto-applied and ran them, and it worked flawlessly for thousands of files without any hanging. So it seems my settings file was somehow corrupt. Hope this helps to other users who have encountered a similar problem.

Thanks for your help!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2013, 10:56:42 AM
Happy that your problem is resolved.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2013, 12:16:12 PM
I am testing with my old settings file to figure out what could be a interfering setting.
So with my old settings file, those hanging issues occur only if (1) the mp3 preset is auto-applied and (2) the problem file is in Music library. In other words, if the file is in inbox or in an unorganized folder, there's no hanging when saving after editing any tag.
What setting(s) do you think could cause this?  

Edit: It just occurred to me that #2 could mean it belongs to the filtering playlist by being in Music library. Then the only condition is auto-applying through a playlist.

Edit2: I found one more condition: it has to be main panel with Music library node selected. When I edit tags and save the file in a playlist, there's no crash.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2013, 12:59:38 PM
There is a little chance that manually applying some ASR preset when another preset is ticked for auto-applying could cause UI freezing. I cant reproduce this, but from what other people says it may be possible.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2013, 01:00:29 PM
Edit2: I found one more condition: it has to be main panel with Music library node selected. When I edit tags and save the file in a playlist, there's no crash.
This seems to be some MB bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2013, 01:07:36 PM
There is a little chance that manually applying some ASR preset when another preset is ticked for auto-applying could cause UI freezing. I cant reproduce this, but from what other people says it may be possible.

Edit2: I found one more condition: it has to be main panel with Music library node selected. When I edit tags and save the file in a playlist, there's no crash.
This seems to be some MB bug.

What I am saying is that this error occurs only with my old settings file. With no (or a new) settings file, everything works fine even with multiple presets auto-applied. Either library node or playlist doesn't matter either. This means there must be some setting(s) that interferes with proper working of playlist-filtering auto-applied presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2013, 01:53:18 PM
Understood
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 16, 2013, 09:36:21 AM
Got this error when trying to run "reencode tag" command:

5/15/2013 4:35:34 PM - 6.0.6002.131072 - 2.1.4882.33419 - System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Collections.ArrayList.get_Item(Int32 index)
   at System.Windows.Forms.DataGridViewColumnCollection.get_Item(Int32 index)
   at MusicBeePlugin.ReencodeTagPlugin.initializeForm()
   at MusicBeePlugin.ReencodeTagPlugin..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.reencodeTagEventHandler(Object sender, EventArgs e)
   at #=qqmD$0WtGEch25w4RfuQXVx8hsKlJs9MqU8CBmx0_YQvnlNTjs8ENnEX3_min9w_z.#=qKMqG1pPovQ5BGw9RR2uPNg==(Object #=qSZnlIXdCrAkndwtGEGIorw==, EventArgs #=qiE0FKERQLtrpTj7X0VhtJw==)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 16, 2013, 02:41:21 PM
Its fixed (http://www.mediafire.com/download.php?bi2j6727xfblo5n).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 16, 2013, 02:59:27 PM
Its fixed (http://www.mediafire.com/download.php?bi2j6727xfblo5n).

Working fine. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on May 30, 2013, 06:47:44 PM
Recently my Windows OS crashed, had to do a full reinstall of my pc and its programs, including MB.
Most things work fine again, but I wished I could find my 'own' (edited) ASR presets back and simply re-import or copy them.
I did backup my 'old windows' before re-installation.
In what folder or under what name should I look for my old presets?
Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on May 30, 2013, 07:13:28 PM
In what folder or under what name should I look for my old presets?


If you have Windows 7 go to: C:\Users\YOUR USER NAME\AppData\Roaming\MusicBee\ASR Presets
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on May 30, 2013, 07:25:12 PM
I find a long list of unrecognizable codes there. How can I find out which ones are those that I created/edited myself???
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on May 30, 2013, 07:54:49 PM
I find a long list of unrecognizable codes there. How can I find out which ones are those that I created/edited myself???
Just copy whole folder to the new location on reinstalled system and then use 'Import all' button in the Advanced Search and Replace plugin window.

If you have some useful presets, share them with boroda who can release them with a new version of the plugin.
Next time you'll need to download a new version of the plugin in this case.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 31, 2013, 12:40:09 PM
VX, thanks :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 18, 2013, 11:17:42 AM
Hi,
I installed the recent plugin (from  2013-05-16) and when I start musicbee I get the following 2 errors:
"Some tag names are duplicated.  Plugin is not properly initialized"
and
"Some track property names are duplicated. Plugin is not properly initialized"

I looked in musicbee at all the tags, and I don't see anything that is "duplicate".
Can you explain what this mean, and how to look for the problem?

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2013, 12:23:04 PM
Hello. First try to upgrade MB to latest version. Then report back if problem is gone.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 18, 2013, 12:35:39 PM
Of course MB is the latest:

From download page
Version:   2.0 Final
Date:   10 October 2012

From MB about:
V 2.1.4873

This error message started as soon as I installed the plugin, a few days ago. I never knew of the plugin before.

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2013, 02:47:21 PM
No, latest version is 2.1.4915 (http://musicbee.niblseed.com/Weekly/MusicBee_2_1_4915.zip). Plugin is fully compatible with final MB 2.0 or latest MB 2.1.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 18, 2013, 03:00:31 PM
OK, DL'ed and installed this latest you provided, but the error is still the same.

I think I should add that the files handled by MB are all FLAC, many with manually added tags, but only few of these are defined in MB.

Usually I work with Foobar2000 to handle tags and everything else. MB is used as catalog for organizing and finding things.

I still organize it all, so many HDD relocating may occur, as well as changes to tag values.
Each time I load MB, I perform re-scan of the relevant folders to sync the latest changes on the albums.

Does this help in anyway?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2013, 03:35:59 PM
What MB localization are you using? Default English?

edit: try this debug version of plugin (http://www.mediafire.com/download/6hkk72r7x1s3np2/mb_TagTools.dll). Copy to 'MusicBee\Plugins' and overwrite existing file.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 18, 2013, 04:11:11 PM
Yes, I use only English.

I put the dll in the plugin folder, and had to "unblock" it. (Nice touch, it hinted me at the reason it was disabled, in MB preferences.)

Then, I pressed (in preferences) on "Enable" and it gave the following error:
"Can't add 5 /format"

After that, I closed MB to see if anything changed.
Opening it I go the initial tag duplicated message and after I pressed "OK", I got this new one:
"Can't add 5 /format"
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2013, 05:15:56 PM
Try this (debug) version (http://www.mediafire.com/download/585nycly5d8lnm7/mb_TagTools.dll).
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 18, 2013, 05:34:21 PM
With this one I get:
"Can't add Format / Format" after that "duplicated tags" error from before.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2013, 07:50:27 PM
Try one more debug version (http://www.mediafire.com/download/lm7yi92u4neliwf/mb_TagTools.dll). Send me files 'C:\Windows\Temp\TagTools.PropNamesErrorLog.txt' and 'C:\Windows\Temp\TagTools.TagNamesErrorLog.txt'.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 18, 2013, 08:42:29 PM
There's no way to attach files, so I must cut & paste. Sorry:
TagTools.PropNamesErrorLog:
/*-------------   start ------------------
Adding URL / Url
Adding Format / Kind
Adding Format / Format
Cant add Format / Format
Adding Size / Size
Adding Channels / Channels
Adding Sample Rate / SampleRate
Adding Bitrate / Bitrate
Adding Date Modified / DateModified
Adding Date Added / DateAdded
Adding Last Played / LastPlayed
Adding Play Count / PlayCount
Adding Skip Count / SkipCount
Adding Time / Duration
Adding Track Gain / ReplayGainTrack
Adding Album Gain / ReplayGainAlbum
---------   end -----*/

TagTools.TagNamesErrorLog.txt
/*-------------   start ------------------
Adding Title / TrackTitle
Adding Album / Album
Adding Album Artist (displayed) / AlbumArtist
Adding Album Artist / AlbumArtistRaw
Adding Artist (displayed) / -1
Adding Artist / -2
Adding Artwork / Artwork
Adding BPM / BeatsPerMin
Adding Composer (displayed) / -3
Adding Composer / -4
Adding Comment / Comment
Adding Conductor / Conductor
Adding Disc# / DiscNo
Adding Disc Count / DiscCount
Adding Encoder / Encoder
Adding Genre / Genre
Adding Genre Category / GenreCategory
Adding Grouping / Grouping
Adding Keywords / Keywords
Adding Lyricist / Lyricist
Adding Mood / Mood
Adding Occasion / Occasion
Adding Origin / Origin
Adding Publisher / Publisher
Adding Quality / Quality
Adding Rating / Rating
Adding Album Rating / RatingAlbum
Adding Love / RatingLove
Adding Tempo / Tempo
Adding Track# / TrackNo
Adding Track Count / TrackCount
Adding Year / Year
Adding Lyrics? / HasLyrics
Adding Virtual1 / Virtual1
Adding Virtual2 / Virtual2
Adding Virtual3 / Virtual3
Adding Virtual4 / Virtua
---------   end -----*/
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on June 19, 2013, 06:34:33 AM
I think I should add that the files handled by MB are all FLAC, many with manually added tags, but only few of these are defined in MB.

Usually I work with Foobar2000 to handle tags and everything else.


1. Is this bug reproducible when MB is used for tagging  ??? (IMHO, MB is much better than Foobar in this case).
2. Which version of Foobar was used to tag the problematic FLAC files  ???
3. What external components are used with Foobar to handle FLAC files  ??? (This might be a compatibility issue that can be easily resolved by updating MB external components, but we need make sure this is the reason for the bug).
Thanks  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 19, 2013, 07:15:58 AM
The issue is not Foobar-related, and there are no "problematic FLAC files".
The errors are reported ONLY when I open MB. After that MB works properly.
It is related to this plugin, because when the plugin is disabled, there's no error.

I have no problem tagging with MB, and foobar. I use them interchangeably, according to what I need.

The plugin informs me that it didn't initialize properly, but I can't say what it means.
I tried to use the library reports, and it seemed to have worked fine.

The foobar versions varied over time from 1.2.1 to 1.2.6 to the latest beta 1.2.7.
The metaflac.exe is the same as far as  I know.  Only the FLAC was lately upgraded, and again, it's irrelevant here.
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on June 19, 2013, 08:52:07 AM
Thanks for the clarification  :)

Looking at the changelog of Foobar: http://www.foobar2000.org/changelog
there are some changes that might be related to this:

Quote
1.2.7
 Now using latest & greatest libFLAC 1.3.0
1.2.6
Fixed misbehavior when updating attached pictures in files with ID3v2.2 tags.
1.2.3
FLAC decoding improvements (beta 3):
-Work-around for certain broken files producing loud glitches.
-SSE optimizations to counter slowdown from the above work-around.
-File Integrity Verifier component now detects such files.
[/qoute]
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 19, 2013, 09:26:31 AM
I don't see the relevance to the problem discussed.
We're not dealing with the actual tagging, nor with Foobar.

Is there any constructive info you need?
What of the logs provided, can they hint at the actual problem?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2013, 02:22:23 PM
The plugin informs me that it didn't initialize properly, but I can't say what it means.
I tried to use the library reports, and it seemed to have worked fine.
Improper initialization of plugin means that you cant use (or even see) some tags in all additional tagging tools commands.

Is there any constructive info you need?
What of the logs provided, can they hint at the actual problem?
Yes. I see that file properties "Kind" and "Format" both have the displayed name "Format" (strings 2 and 3 in TagTools.PropNamesErrorLog). Displayed names should be unique in MB and for plugin correct work.

Displayed tag/property names are defined in localization file. I've tried to use default English localization and found no problem. Please check again which MB localization you are using and that there are no duplicated localizations (2 or more localizations with the name "English").
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 19, 2013, 02:56:54 PM
I renamed the format for the "kind" field to "Format-Kind"
Following at the end of the post, the two logs after the change.

I also tried to look at the localization you mentioned:
I had my MB set to English. (I never even was aware of this option)
I saw in the preferences additional locale named "English US", so "in the name of science" I removed all the files from the Localisation folder under the MB installation folder. After that the drop-down list of locales contains now only "English".
Still, the same error of duplicated.

Must be something else but I can't think of.
Any ideas?
Thanks.
So here are the logs again"
/*-----
TagTools.PropNamesErrorLog.txt:
Adding URL / Url
Adding Kind-Format / Kind
Adding Format / Format
Adding Size / Size
Adding Channels / Channels
Adding Sample Rate / SampleRate
Adding Bitrate / Bitrate
Adding Date Modified / DateModified
Adding Date Added / DateAdded
Adding Last Played / LastPlayed
Adding Play Count / PlayCount
Adding Skip Count / SkipCount
Adding Time / Duration
Adding Track Gain / ReplayGainTrack
Adding Album Gain / ReplayGainAlbum
------------------------------------------------*/

/*--------------   TagTools.TagNamesErrorLog.txt
Adding Title / TrackTitle
Adding Album / Album
Adding Album Artist (displayed) / AlbumArtist
Adding Album Artist / AlbumArtistRaw
Adding Artist (displayed) / -1
Adding Artist / -2
Adding Artwork / Artwork
Adding BPM / BeatsPerMin
Adding Composer (displayed) / -3
Adding Composer / -4
Adding Comment / Comment
Adding Conductor / Conductor
Adding Disc# / DiscNo
Adding Disc Count / DiscCount
Adding Encoder / Encoder
Adding Genre / Genre
Adding Genre Category / GenreCategory
Adding Grouping / Grouping
Adding Keywords / Keywords
Adding Lyricist / Lyricist
Adding Mood / Mood
Adding Occasion / Occasion
Adding Origin / Origin
Adding Publisher / Publisher
Adding Quality / Quality
Adding Rating / Rating
Adding Album Rating / RatingAlbum
Adding Love / RatingLove
Adding Tempo / Tempo
Adding Track# / TrackNo
Adding Track Count / TrackCount
Adding Year / Year
Adding Lyrics? / HasLyrics
Adding Virtual1 / Virtual1
Adding Virtual2 / Virtual2
Adding Virtual3 / Virtual3
Adding Virtual4 / Virtua
------------------------------------*/
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2013, 03:37:42 PM
Log for TagTools.PropNamesErrorLog.txt looks fine, no error messages. How did you rename Kind property to "Kind-Format"?

Log for TagTools.TagNamesErrorLog.txt also looks good, but its truncated - my fault, bug in debug version :) Please redownload debug version (http://www.mediafire.com/download/j8l41tu30fffjyh/mb_TagTools.zip) and post logs again.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 19, 2013, 03:59:19 PM
Rename "Kind" property:
Preferences--> Layout (1) --> in the 3rd group titled "Main Panel": -->Configure Fields button:
There's a whole list of properties with their original names and that name can be overridden.

TagTools.TagNamesErrorLog.txt
/*--------------
Adding Title / TrackTitle
Adding Album / Album
Adding Album Artist (displayed) / AlbumArtist
Adding Album Artist / AlbumArtistRaw
Adding Artist (displayed) / -1
Adding Artist / -2
Adding Artwork / Artwork
Adding BPM / BeatsPerMin
Adding Composer (displayed) / -3
Adding Composer / -4
Adding Comment / Comment
Adding Conductor / Conductor
Adding Disc# / DiscNo
Adding Disc Count / DiscCount
Adding Encoder / Encoder
Adding Genre / Genre
Adding Genre Category / GenreCategory
Adding Grouping / Grouping
Adding Keywords / Keywords
Adding Lyricist / Lyricist
Adding Mood / Mood
Adding Occasion / Occasion
Adding Origin / Origin
Adding Publisher / Publisher
Adding Quality / Quality
Adding Rating / Rating
Adding Album Rating / RatingAlbum
Adding Love / RatingLove
Adding Tempo / Tempo
Adding Track# / TrackNo
Adding Track Count / TrackCount
Adding Year / Year
Adding Lyrics? / HasLyrics
Adding Virtual1 / Virtual1
Adding Virtual2 / Virtual2
Adding Virtual3 / Virtual3
Adding Virtual4 / Virtual4
Adding Virtual5 / Virtual5
Adding Virtual6 / Virtual6
Adding Virtual7 / Virtual7
Adding Virtual8 / Virtual8
Adding Virtual9 / Virtual9
Adding Virtual10 / Virtual10
Adding Virtual11 / Virtual11
Adding Virtual12 / Virtual12
Adding Virtual13 / Virtual13
Adding Virtual14 / Virtual14
Adding Virtual15 / Virtual15
Adding Virtual16 / Virtual16
Adding Lyrics / -5
Adding Lyrics (synchronized) / -6
Adding Lyrics (unsynchronized) / -7
Adding <Null> / -20
Adding Lyrics / Custom1
Cant add Lyrics / Custom1
Adding Label / Custom2
Adding Media / Custom3
Adding Grabbed From / Custom4
Adding Ripper / Custom5
Adding Sort Artist / Custom6
Adding Sort Album Artist / Custom7
Adding Info / Custom8
Adding Custom9 / Custom9
Adding Custom10 / Custom10
Adding Custom11 / Custom11
Adding Custom12 / Custom12
Adding Custom13 / Custom13
Adding Custom14 / Custom14
Adding Custom15 / Custom15
Adding Custom16 / Custom16
--------------*/
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2013, 04:51:20 PM
Rename "Kind" property:
Preferences--> Layout (1) --> in the 3rd group titled "Main Panel": -->Configure Fields button:
There's a whole list of properties with their original names and that name can be overridden.
Never have known of it.

@Steven: could you disable duplicated field names when configured in Preferences--> Layout (1) --> in the 3rd group titled "Main Panel": -->Configure Fields button. All in all MB itself requires that all field names should be unique.

@Bhive: As for 2nd log: rename Custom1 tag name from "Lyrics" to something else because there is predefined tag "Lyrics".
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 19, 2013, 05:17:57 PM
That's it boroda74.
Renaming this last one (Lyrics-->Custom1) fixed it.
Closing and opening MB with no error!!

Many thanks and thumbs-up!
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on June 19, 2013, 07:33:41 PM
@Steven: could you disable duplicated field names when configured in Preferences--> Layout (1) --> in the 3rd group titled "Main Panel": -->Configure Fields button. All in all MB itself requires that all field names should be unique.
That validation is already being done in v2.1 (cant remember if it was in place in 2.0).
But i dont see "Lyrics" being used already as a header - what does Lyrics/ -5 mean?
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 19, 2013, 08:14:38 PM
But i dont see "Lyrics" being used already as a header - what does Lyrics/ -5 mean?
This is not a question for me, is it?
Because if it is, I don't know the answer.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2013, 08:34:30 PM
But i dont see "Lyrics" being used already as a header - what does Lyrics/ -5 mean?
Here is the code from my getFileTag() plugin function:
Code
                case LyricsId: //LyricsId is -5
                    tag = mbApiInterface.Library_GetLyrics(sourceFileUrl, LyricsType.NotSpecified);
                    break;

                case SynchronisedLyricsId: //SynchronisedLyricsId is -6
                    tag = mbApiInterface.Library_GetLyrics(sourceFileUrl, LyricsType.Synchronised);
                    break;

                case UnsynchronisedLyricsId: //UnsynchronisedLyricsIdis -7
                    tag = mbApiInterface.Library_GetLyrics(sourceFileUrl, LyricsType.UnSynchronised);
                    break;
I dont remember why I didnt use MetaDataType.Lyrics (114) id for unspecified lyrics type. You can see similar workarounds for Artist/Artist (displayed) and Composer/Composer (displayed) tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on June 19, 2013, 08:44:07 PM
as mentioned MB is already validating for duplicate header labels. As a guess it seems to me you might be adding "Lyrics" yourself which is conflicting with "Lyrics" from BHive's custom tag - but "Lyrics" is not a duplicate in MB itself so will pass the validation
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2013, 09:02:10 PM
Bhive succeeded to rename Custom1 tag to "Lyrics" (suggest he was using MB 2.0 at that time). That was the problem: predefined tag with displayed name "Lyrics" and custom tag with the same displayed name. Now problem is solved, I just wondered that MB allowed to enter duplicated filed displayed names.

P.S. To get displayed name for my LyricsId (-5) pseudo tag I'm using code: mbApiInterface.Setting_GetFieldName(MetaDataType.Lyrics);
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2013, 09:24:45 PM
as mentioned MB is already validating for duplicate header labels. As a guess it seems to me you might be adding "Lyrics" yourself which is conflicting with "Lyrics" from BHive's custom tag - but "Lyrics" is not a duplicate in MB itself so will pass the validation
Actually "Lyrics" tag is not included in "Preferences--> Layout (1) --> Configure Fields" window and MB allows to rename any displayed field name to "Lyrics". Steven, could you disable "Lyrics" displayed filed name? I'm using lyrics as usual tag in plugin, so its very not desirable to allow existence of another "Lyrics" field.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on June 19, 2013, 10:27:58 PM
i'm not sure i am comfortable putting that restriction in when its not a restriction needed by MB itself - certainly not for the 2.1 version.
I'll revisit this at a later date when i have more time to think about the impact
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 20, 2013, 05:26:31 AM
OK. Thanks anyway.
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on June 20, 2013, 09:08:55 AM
Taking into consideration that this is one of the most popular and useful plugins for MB that definitely expands its functionality so that it's much better for tagging than any other music player or manager is, IMHO the issue should be handled somehow before the 2.1 stable release.

The easiest way I could think would be to add an information window to MB that would pop up when "Preferences--> Layout (1) --> Configure Fields" is launched. I think 2 or 3 sentences with a description or warning (even if available in English only) would be enough to prevent such bugs and make users more convenient with the plugin and MB itself.

A more fundamental change could be applied if needed for the 2.2 version or newer.
I can't imagine this could be done better with the plugin update as it's a MB 'fault'.

We should take advantage of discovering the bug before the stable release.

Steven, boroda - what do you think  ???
Title: Re: Additional Tagging and Reporting Tools
Post by: Bhive on June 20, 2013, 09:18:21 AM
If I may add my 2 cents on this, I'm with Steven.

Much careful consideration should be given to possible consequences.

Restrictions to data on one section/part of a software to "brick wall" for other unrelated something, that might not even be installed on users' machines, is not a good design.

Sorry, I know it was not a call for open discussion.
Title: Re: Additional Tagging and Reporting Tools
Post by: quick_wango on June 20, 2013, 09:26:56 AM
Would you consider putting this on github?
Title: Re: Additional Tagging and Reporting Tools
Post by: VX on June 20, 2013, 09:35:52 AM
Thanks, Bhive for expressing your opinion.  :) Be sure that this forum has always been opened for the discussions  :)
I know we all have best wishes for MB. Not only I appreciate your opinion but also I share it  :)

IMHO, adding a few words of explanation when "Preferences--> Layout (1) --> Configure Fields" is launched wouldn't restrict/break anything I can think of. But it would still make users more aware of the consequences of the changes they could make. Those who don't use the plugin or have no need for this particular feature could simply ignore the info.

As you can see implementing this solution would help to prevent/fix the issue for those who use the plugin without any negative impact on MB usability and features.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 20, 2013, 10:17:44 AM
I can't imagine this could be done better with the plugin update as it's a MB 'fault'.
...
Steven, boroda - what do you think  ???
You have given me an excellent idea: instead of requesting Steven for modification of MB, just to use in plugin 'Lyrics (any)' (localized) instead of 'Lyrics' (localized) if some tag is already named 'Lyrics' (localized).

EDIT: Its done.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 20, 2013, 10:19:08 AM
Would you consider putting this on github?
No. What are advantages of github?
Title: Re: Additional Tagging and Reporting Tools
Post by: quick_wango on June 20, 2013, 11:35:41 AM
Version Control, easy collaboration, easier source code distribution.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on June 20, 2013, 01:36:03 PM
@ boroda74

just a tiny error
(http://img546.imageshack.us/img546/2694/tzcl.jpg)

'Noting done.'  =  'Nothing done.'
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 20, 2013, 02:25:04 PM
@ boroda74

just a tiny error
(http://img546.imageshack.us/img546/2694/tzcl.jpg)

'Noting done.'  =  'Nothing done.'

Thank you :) Its fixed now.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 25, 2013, 04:21:03 PM
Plugin description and download links have been moved to Plugin Wiki page (http://musicbee.wikia.com/wiki/Tagging_and_Reporting_Tools).
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on June 25, 2013, 04:24:01 PM
Nice work, thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on July 15, 2013, 02:17:29 AM
G'day boroda74

just noticed that "Remove all '(...)' or '[...]' from '<Tag 1>' isn't working as shown in the example in the plugin dialogue

Quote
Command removes all '(...)' or '[...]' from '<Tag 1>' (e.g. 'RV 548: 1. [Allegro]' becomes 'RV 548: 1. Allegro').

it's removing the brackets and everything between them, so for the included example:
'RV 548: 1. [Allegro]' becomes 'RV 548: 1.'

which is a bit of a bummer, as how it's shown in the plugin is how I needed it to work today  :(
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 15, 2013, 08:17:54 PM
just noticed that "Remove all '(...)' or '[...]' from '<Tag 1>' isn't working as shown in the example in the plugin dialogue
I think its an error in description, but I'll make both variants in future. Right now copy 'Remove all '(...)' or '[...]' from '<Tag 1>' preset and edit it:

search for
Code
[\(\[\]\)]
and replace with empty string.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on July 16, 2013, 12:29:21 AM
thank you boroda74
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on July 16, 2013, 11:56:14 AM
Hi boroda74!

Using version 4.8.4919 of the Additional Tagging and Reporting Tools and version 2.1.4924 of MusicBee.

Yesterday I encountered a strange issue using the copy tag function as follows:

1.) Marked some mp3 files to be changed (copy title to empty album tag)
2.) Setup under copy tag: Copy from Title to Album Tag
3.) After Setup I clicked on the "Preview" button. Everything was fine. I usually don't use the preview function but yesterday I did because of a fresh clean installation of the 2.1 version (I was updating from 2.0 version) of MB and reinstallation of the 4.8.4919 version of your tagging tool.
4.) As everything was fine I clicked on the "Apply" button.
5.) Next thing I expected was that the album tag of all marked mp3 files were filled with the copied title tag but that wasn't the case obviously, i. e. I couldn't see anything being filled in in the album tag on my screen.
6.) So I marked one of those mp3 files, opened the tag editor and voilà the copied value was there in the album tag.
7.) Next I clicked on "Save" and - what a surprise - the album tag appeared on my screen (being visible now).
8.) Then I repeated steps 1 to 4 except using the preview function. I directly clicked on the "Apply" button.
9.) And now the album tag was filled and I could see it on my screen without using the tag editor detour.


Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 17, 2013, 10:38:00 AM
Hello GoodWill41. I can't reproduce this behavior (at least with MB .4932).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 17, 2013, 11:05:33 AM
New version of plugin released:


See plugin Wiki page (http://musicbee.wikia.com/wiki/Tagging_and_Reporting_Tools) for download link.
Title: Re: Additional Tagging and Reporting Tools
Post by: GoodWill41 on July 17, 2013, 11:06:38 AM
Hello boroda74!

And even that is strange because I tested it today and I also can't reproduce it.

And it wouldn't have been a big deal if you could reproduce it because it was an exception (using the preview first) as I wrote in my earlier post.

The empty album tag was the result of a faulty setup of a recording software for internet radio streams. I've corrected that yesterday, so it won't happen again and that leading to not using the copy tag function.

So, I'm sorry for the false alarm I've created.

Title: Re: Additional Tagging and Reporting Tools
Post by: Pat on August 27, 2013, 06:32:55 AM
@Boroda74
Hi, 'redwing' pointed me to this reporting tool plugin and suggested mentioning my question/request from the general question list in here. Could you have a look?

Topic: Export artwork and description of album and tracks as document
http://getmusicbee.com/forum/index.php?topic=10538.msg63184#msg63184

The reason I am looking for this kind of report is that it was (and believe still is) available in iTunes. Under File there is an option "Print..." Then you can select "Print Album Listings". This produces a report with artwork on the left and next to it on the right: album name, artist, song titles and length. I used to take a printout of this report with me when visiting the public library. Especially with classical music, it was a way of checking whether I already had a performance a particular work (concerto, ...) when browsing the CD's in the library. Or making annotations on the report to look for new versions of the same works.

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 27, 2013, 11:06:08 AM
The reason I am looking for this kind of report is that it was (and believe still is) available in iTunes. Under File there is an option "Print..."
Hi, I cant promise you fancy report, but I'll do your requests later (now I'm working on another plugin and don't enough time for this).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 07, 2013, 04:13:56 AM
When a new virtual field is added, the field is not readily available from the list of both "copy tag" and ASR presets. MB has to be restarted. Would be great if it gets updated real time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 07, 2013, 09:11:11 AM
Do you mean that if you rename virtual field then new name in not displayed immediately?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 07, 2013, 10:02:31 AM
Yes, that's what I meant.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 07, 2013, 10:37:55 AM
I'll try to fix it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 09, 2013, 05:03:12 AM
New beta version of plugin (http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools) released

Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 09, 2013, 01:55:44 PM
  • Added option to resize artworks in "Library Reports" command.
  • Memory consumption by artworks is significantly reduced in "Library Reports" command.
Resized artwork doesn't show up both in preview and in the report.
Unlike the previous version, it creates a report for all tracks in the node, not just selected files.

  • Tag names are refreshed upon opening any command window (MusicBee restart is not required anymore if you changed some tag names).
Working well, thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 09, 2013, 02:30:55 PM
Resized artwork doesn't show up both in preview and in the report.
Working fine here. I'll do more careful testing.

Unlike the previous version, it creates a report for all tracks in the node, not just selected files.
"Library reports" always listed all tracks included in current (maybe filtered) view, not selected tracks. Use autoplaylist if you need to filter tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 09, 2013, 03:29:38 PM
New beta version of plugin (http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools) released


Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 09, 2013, 03:48:32 PM
Now artwork is working fine, thanks!
Would be great if the user can change the order of columns with preview.

BTW got this error with "Calculate subgroupings total" option ticked.

9/9/2013 03:41:23 PM - 6.0.6002.131072 - 2.2.4999.29982 - System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.ToolsPluginTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 09, 2013, 04:17:31 PM
Now artwork is working fine, thanks!
Would be great if the user can change the order of columns with preview.

BTW got this error with "Calculate subgroupings total" option ticked.

9/9/2013 03:41:23 PM - 6.0.6002.131072 - 2.2.4999.29982 - System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.ToolsPluginTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Seems I write very buggy code for recent time. Thank you.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 09, 2013, 04:54:56 PM
@redwing
Try this version (http://www.mediafire.com/download/ex1do2c48k1xgt1/mb_TagTools_2013-09-09-3.zip).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 09, 2013, 07:14:19 PM
Good! No longer with the error. Then, is it now working fine as long as the total size of resized artwork is under 2G?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 09, 2013, 07:36:19 PM
Yes. Total size of unique uncompressed binary images (duplicates are automatically removed) should be < 2GB.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 18, 2013, 04:50:07 PM
New beta version of plugin (http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools) released

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 21, 2013, 11:40:22 AM
New stable version of plugin (http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools) released
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on September 22, 2013, 05:04:37 AM
I'm having a problem with the Copy Tags command where it keeps switching the first tag to <Null> after I set the second tag.

For instance, I was trying to copy Track# into Title, and when I put title in for the second tag, the first one switched.  Also happened when I tried to copy Artist into Comment.  I could still re-enter the first tag and continue, it's just an minor annoyance.

(I updated the plugin today, but I'm not sure if I'm on the latest version or the one right before it.)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 22, 2013, 05:32:36 AM
Thanks. It fixed. Redownload plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on September 22, 2013, 03:39:55 PM
Done, thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: Stampie on September 30, 2013, 02:00:11 PM
I got the error below when trying to export a report containing Artwork, Album, Album Artist, Year, Genre.

MusicBee v2.1.4924.34601 (Win6.2), 30 Sep 2013 13:47:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.LibraryReportsPlugin.exportTrackList()
   at MusicBeePlugin.LibraryReportsPlugin.buttonOK_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The preview worked fine and the report contains 447 albums.

I was exporting to a local drive on my PC with plenty of free space.

Regards
Nick
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 30, 2013, 03:45:28 PM
I can reproduce this. Thanks for bug report. Will fix it as soon as possible.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 30, 2013, 04:35:18 PM
@Stampie
Redownload plugin (http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools). Fixed mentioned and several other bugs in "Library report" command.
Title: Re: Additional Tagging and Reporting Tools
Post by: Stampie on September 30, 2013, 05:56:02 PM
I can confirm that the report is now generated.

I don't know whether this is a bug, or just not possible, but I sorted the report by album artist in the preview dialog prior to exporting; however, the html report ignored the sort order and produced it in the order that the preview window originally presented me with (which appears random)

thanks for the quick fix.
Nick
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 30, 2013, 08:51:55 PM
Unfortunately exporting operations always uses initial (cached) sorting. I could only disable changing sorting in UI (UI table is stored differently than cached one) for disambiguation.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 01, 2013, 09:18:24 PM
New version of plugin (http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools) released


Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 04, 2013, 02:45:11 PM
Hey, boroda74, you know what this is about:
http://getmusicbee.com/forum/index.php?topic=10786.msg65862#msg65862

Would it be possible to create a preset that can automate this process? So when it's auto-applied, it checks whether title has "(" or "[" and lyrics tag is not present. If so, it copies title to <Tag2> and remove all (...) [...] from title. Then once it gets lyrics tag, it restores original title and remove <Tag2>. What do you think?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2013, 04:14:47 PM
I'm afraid there is no simple solution for this.

1. Select all tracks and copy "Title" to "Custom 8".

2. Create auto-playlist "Has lyrics" with condition "Lyrics?" is not equal to "" (empty value) and auto-playlist "Has no lyrics" with condition "Lyrics?" is equal to "".

3. Copy asr preset "Remove all '(...)' or '[...]' from '<Tag 1>'" and rename the copy to "Copy <Tag 1> to <Tag 2> and remove all '(...)' or '[...]' from '<Tag 1>'". Copy everything from step 1 to step 2. Change step 1 to search for "^(.*)" in tag <Tag 1> and replace with "$1" in <Tag 2>.  Save this preset.

4. Set <Tag 1> to 'Title' and <Tag 2> to "Custom 8" (for example) for this preset.

5. Tick this preset for auto-applying if it track belongs to playlist "Has no lyrics".

6. Find preset "TOY: 'Copy tag' command" . Set <Tag 1> to "Custom 8" and <Tag 2> to "Title".

7. Tick this preset for auto-applying if track belongs to playlist "Has lyrics".

P.S. Didn't test these instructions, but they should work.

P.P.S. I don't want to modify ASR preset pack because instructions for this situation anyway are too complex.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 04, 2013, 04:28:19 PM
Looks like it should be working fine.

But then all tracks will keep having a <Custom 8> value, and the process is too complex. I will think about a way to use virtual tags to simplify the process.

Thanks for your help!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 04, 2013, 06:32:17 PM
No Bracket = $IsNull(<Lyrics?>,$IsNull($If($Replace(<Title>,"(",)=<Title>,N,), $Split(<Title>,"(",1),),)

returns AAA for the title of AAA(aaa) only when the track has no lyrics. Otherwise it has no value.

Then what? Take into account that if you change title value, the virtual tag will not work properly.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2013, 08:16:38 PM
All this is needed to get lyrics for title without text in brackets? Then we have to modify 'title' tag and to store original 'title' tag value somewhere else. If lyrics plugin can't use virtual field instead of 'title' then I can't see how we could use virtual field.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 05, 2013, 07:22:13 AM
Thanks. I posted it on the wishlist board: http://getmusicbee.com/forum/index.php?topic=10863.0
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 08, 2013, 08:37:53 AM
Related to these threads:

http://getmusicbee.com/forum/index.php?topic=10883.0
http://getmusicbee.com/forum/index.php?topic=10893.0

How about supporting "All Contained Tags" preset for Library Reports command that shows all supported/unsupported fields contained by those tracks just like when looked into with tag inspector? Then the user would be able to browse all those tag values by sorting by each column.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 08, 2013, 10:37:57 PM
Sorry, MB API supports access only to tags mapped to UI. I don't want to write own id3 parser.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 09, 2013, 01:45:16 AM
No problem!
Title: Re: Additional Tagging and Reporting Tools
Post by: Arathon on October 30, 2013, 11:29:12 PM
Hi, Thanks for this great plugin, it's really usefull. I'm having a problem in tagging my files and i wanted to ask if you could help me, i want to split the artist tag while keeping the original one so it want mess last.fm scrobbling. For example i have such an artist:
ARTIST: deadmau5 feat. Chris James
I want to split it into:
ARTIST:Chris James
ARTIST: deadmau5
But in the track explorer the artist tag (or Artist displayed tag as i saw in mp3tag) should remain as the original one "deadmau5 feat. Chris James", so the scrobbling want be affected while i'll have a nice organized library.

I tried copying the artist tag to displayed artist one and splitting it, but when i scrobble it will send
ARTIST: deadmau5;Chris James
and last.fm couldn't recognize it. Is there a way to solve this?

Thanks again for this awesome plugin  and sorry if this is OT.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 31, 2013, 01:16:00 AM
Thanks again for this awesome plugin  and sorry if this is OT.
No, its not offtopic.

I can't check this right now, but try "Advanced Search & Replace" command, "Copy all artists from 'Displayed Artist' tag to 'Artist' tag" preset. First select 1 test track, then the click "Preview", "Proceed".
Title: Re: Additional Tagging and Reporting Tools
Post by: Arathon on October 31, 2013, 05:44:08 PM
Awesome, that was the right option :D Thank you very much!!!

Now i have another two request  :) :
1 - First i want to organize all the remix songs I have by adding in the artist tag the author of the remix too like this:
             Bonobo -  Pick Up (Fourtet Remix)
      So i want to add "Fourtet" to the artist tag with "Bonobo". The structure of all my remix songs are the same:
      %songtitle (%artist_who_has_done _the_remix Remix). I know that i can achieve this with regular expression but I have no clue how,
       so I'm hoping you are so kind to help me :D.

2.    After i finished organizing my "artist" tag i noticed that the sort artist tag was also messed, can i copy the first ones to the seconds? i tried using the Copy tag funtion but it seems it doesn't like multiple artist because it doesn't split them even thought the "Sort artist" tag accept multiple entries.

This is all, Thanks again for this plugin. In my opinion this should be included by default because it gives so much potential and power to the already awesome musicbee.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 01, 2013, 01:43:33 AM
Now i have another two request  :) :
1 - First i want to organize all the remix songs I have by adding in the artist tag the author of the remix too like this:
             Bonobo -  Pick Up (Fourtet Remix)
      So i want to add "Fourtet" to the artist tag with "Bonobo". The structure of all my remix songs are the same:
      %songtitle (%artist_who_has_done _the_remix Remix). I know that i can achieve this with regular expression but I have no clue how,
       so I'm hoping you are so kind to help me :D.
Create new ASR preset, name it correctly. Search title tag for
Code
(.*)\((.*)\s*Remix)\)
in title and replace artist tag by
Code
\null($2)$2
in step 1. Tick (+) checkbox to add (not to replace) new artist. Leave other steps blank. I didn't test these instructions, so try them first on 1 test track.


2.    After i finished organizing my "artist" tag i noticed that the sort artist tag was also messed, can i copy the first ones to the seconds? i tried using the Copy tag funtion but it seems it doesn't like multiple artist because it doesn't split them even thought the "Sort artist" tag accept multiple entries.
What is 'song artist' tag? Album artist? Or 'artist' is album artist and 'song artist' is artist?


This is all, Thanks again for this plugin. In my opinion this should be included by default because it gives so much potential and power to the already awesome musicbee.
Thanks for kind words :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Arathon on November 01, 2013, 02:41:51 AM
Now i have another two request  :) :
1 - First i want to organize all the remix songs I have by adding in the artist tag the author of the remix too like this:
             Bonobo -  Pick Up (Fourtet Remix)
      So i want to add "Fourtet" to the artist tag with "Bonobo". The structure of all my remix songs are the same:
      %songtitle (%artist_who_has_done _the_remix Remix). I know that i can achieve this with regular expression but I have no clue how,
       so I'm hoping you are so kind to help me :D.
Create new ASR preset, name it correctly. Search title tag for
Code
(.*)\((.*)\s*Remix)\)
in title and replace artist tag by
Code
\null($2)$2
in step 1. Tick (+) checkbox to add (not to replace) new artist. Leave other steps blank. I didn't test these instructions, so try them first on 1 test track.

Thanks i  tried setting the preset but every time i do a preview it crashes closing musicbee, here the error given every time:

MusicBee v2.2.5039.18316 (Win6.2), 1 nov 2013 2:29:

System.ArgumentException: parsing "(.*)\((.*)\s*Remix)\)" - Too many )'s.
   at System.Text.RegularExpressions.RegexParser.ScanRegex()
   at System.Text.RegularExpressions.RegexParser.Parse(String re, RegexOptions op)
   at System.Text.RegularExpressions.Regex..ctor(String pattern, RegexOptions options, TimeSpan matchTimeout, Boolean useCache)
   at System.Text.RegularExpressions.Regex.Matches(String input, String pattern, RegexOptions options)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.Replace(String value, String searchedPattern, String replacedPattern, Boolean ignoreCase, Boolean& match)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.SetReplacedTag(String currentFile, Plugin tagToolsPluginParam, Int32 searchedTagId, Int32 replacedTagId, String searchedPattern, String replacedPattern, Boolean ignoreCase, Boolean append, String& searchedTagValue, String& replacedTagValue, String& originalReplacedTagValue)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.GetReplacedTags(String currentFile, Plugin tagToolsPluginParam, Preset presetParam)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.previewChanges()
   at MusicBeePlugin.ToolsPluginTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()


What is 'song artist' tag? Album artist? Or 'artist' is album artist and 'song artist' is artist?
I thought that i could put multiple Artist in the "Artist Sort" tag but it doesn't work as i want.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 01, 2013, 03:34:19 AM
Thanks i  tried setting the preset but every time i do a preview it crashes closing musicbee, here the error given every time:
Yea, my fault. There are even more mistakes. This time I've tested my advice :) Search for:
Code
(.*)\((.*)\s*Remix\)
and replace by
Code
\@null($2)$2
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 01, 2013, 05:58:48 PM
All of sudden, I found this plugin was disabled and when trying to enable it I'm getting this error.

(http://i.imgur.com/1u3Xobg.png)

The thing is if I launch MB with "run as administrator" then the plugin can be enabled. But it had worked fine with normal running. Reinstalled the plugin, gave full permission to all user options for the dll file, but it has no effect. All other plugins are working fine except this one. MB runs as portable version and the path is E:\MB\Plugins. Any thought?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 01, 2013, 07:23:24 PM
Try this version:
http://www.mediafire.com/download/n83gdk20fgxk46n/mb_TagTools.dll
it should give more detailed error description.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 01, 2013, 07:34:48 PM
Thanks!
When I click on Enable, It says "Access to the path 'C:\Windows\Temp\TagTools.TagNamesErrorLog.txt' is denied."
Title: Re: Additional Tagging and Reporting Tools
Post by: Arathon on November 01, 2013, 08:14:44 PM
Thanks!
When I click on Enable, It says "Access to the path 'C:\Windows\Temp\TagTools.TagNamesErrorLog.txt' is denied."

Did you restore your system with Windows restore point option? Cause it happened to me and i had to uninstall every folder created by musicbee (especially the appdata one) then re install. This resolved the issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 01, 2013, 08:18:47 PM
Did you restore your system with Windows restore point option?

No, I didn't. In fact I have that option disabled. BTW was your previous setup a portable or a normal installation?
Title: Re: Additional Tagging and Reporting Tools
Post by: Arathon on November 01, 2013, 09:06:47 PM
No, I didn't. In fact I have that option disabled. BTW was your previous setup a portable or a normal installation?

It was a normal installation over windows 8.1 and I've done a reset after the update; and everything was working quite well until i had to use windows restore option and from there i had your same issue and also another one related to administrator permission. I tried the portable option, moving the program folder on another location with no success, so i decided to wipe everything related to the program backing up the preference file. At this point i redownloaded the software and choose this time to use it as portable. Now everything is working, but when i try o edit a lot of files it will start to blink and i have to wait (30s to 1 min) before i could use it again (it's quite slow in portable mode).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 01, 2013, 09:28:12 PM
Thanks for the info, but still I'm not sure what triggers this kind of problem. Regarding the blinking, that happens while this plugin is working with tags. boroda74 made a great effort to shorten the time, but still you have to wait for some time until it's done.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 02, 2013, 09:47:50 AM
I'm still getting the same error whenever launching MB. What are the files for, and should they be stored in that folder instead of Appdata folder for portable version?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 02, 2013, 10:47:58 AM
'C:\Windows\Temp\TagTools.TagNamesErrorLog.txt' and  'C:\Windows\Temp\TagTools.TagIdsErrorLog.txt' files are debug logs. Does folder  'C:\Windows\Temp\' exist on your machine? Also check if this folder is writable by your user.

On the other hand I could turn off writing these logs if they cause more problem than solve.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 02, 2013, 11:03:50 AM
@redwing
This version will write error logs to 'AppData' rather than 'C:\Windows\Temp'

http://www.mediafire.com/download/fpaj92s7ipwk252/mb_TagTools_2013-11-02.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 02, 2013, 11:11:22 AM
The problem was indeed the permission issue with the two files in C:\Windows\Temp folder. After giving all user level a full permission for the two text files, the issue was resolved.

This version will write error logs to 'AppData' rather than 'C:\Windows\Temp'

Yes, this is working great. Now I deleted the two files in C:\Windows\Temp folder, and it's working fine. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 02, 2013, 11:18:57 AM
BTW I also noticed Now Playing to Text File plugin writes its output files and error logs in the same Windows folder. You might want to consider changing that too.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 02, 2013, 11:45:15 AM
BTW I also noticed Now Playing to Text File plugin writes its output files and error logs in the same Windows folder. You might want to consider changing that too.
I did right now: Now Playing, Social Networks Status and Tag Tools plugins are updated.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 02, 2013, 12:00:12 PM
Just tested with ASR plugin & Now Playing plugin. Now they write error logs in both folders. Deleted files in Windows\Temp folder but they keep regenerating them. Is this expected behavior?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 02, 2013, 12:04:44 PM
No. Could you re-download both plugins?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 02, 2013, 12:13:02 PM
Re-downloaded, but still the same.

Take your time. There's no hurry for this.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 02, 2013, 12:24:13 PM
May be I uploaded wrong versions of plugins. I'll reupload them again.
Title: Re: Additional Tagging and Reporting Tools
Post by: martez89 on November 03, 2013, 10:40:15 AM
I'm having trouble changing the case to Title Case with exceptions.

First it won't make the words "Of" and "A" lower case. And the list of exceptions doesn't seem to be saved after closing the window.

(http://i.imgur.com/GJSbItO.png)

I've only experienced this the last few weeks. I've updated the plugin and I reinstalled MusicBee (including latest patch).

Thank you!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2013, 11:14:20 AM
First it won't make the words "Of" and "A" lower case.
Excluded words are not changed, not become lowercased! You should lowercase tags with 'exclude words' unticked, then 'sentence case' tags with 'exclude words' ticked (click 'Reapply rule to new tag' button instead of Preview/Proceed to make 2nd step without saving tags).

And the list of exceptions doesn't seem to be saved after closing the window. I've only experienced this the last few weeks. I've updated the plugin and I reinstalled MusicBee (including latest patch).
Nothing was changed for saving exceptions for ages. All settings are saved only after you click 'Proceed' button.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 03, 2013, 12:42:51 PM
- For me this works: first, <Sentence case> with "exclude words" unticked, then <Title Case> with "exclude words" ticked
- My template for "exclude words": a an and as at but by for from in into nor of off on onto or out over the to up with
- Also use Always capitalize first or last word option when you need it
- Here's previous discussion about the tool: http://getmusicbee.com/forum/index.php?topic=8518.0

@boroda74:
Upon clicking on "Clear", it sometimes deletes a template for "exclude words" when it has focus. If it's not intended, how about disabling that behavior?
Title: Re: Additional Tagging and Reporting Tools
Post by: martez89 on November 03, 2013, 01:18:24 PM
@boroda74:

I thought I used this plugin previously with my settings and that a bug caused a problem. But probably I changed the settings once, and I couldn't fix it because I misunderstood how Change Case worked. Your advice helped, thanks!

@redwing:

Thank you for your comment!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2013, 01:34:33 PM
@boroda74:
Upon clicking on "Clear", it sometimes deletes a template for "exclude words" when it has focus. If it's not intended, how about disabling that behavior?
Very strange behavior. I'll try to fix it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2013, 02:14:15 PM
New plugin version released:


http://www.mediafire.com/download/z1pecsqm79r68is/mb_TagTools_2013-11-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 03, 2013, 02:51:35 PM
Thanks for the update!

Now they write error logs in both folders. Deleted files in Windows\Temp folder but they keep regenerating them.

Just to let you know, this bug is not fixed for ASR plugin. The thing is that it updates the two text files for both paths when MB starts, but when I launch ASR plugin it updates the files in \Windows\Temp folder only. Probably that's why it keeps doing that.

Also Now Playing plugin's default folder for output files is still set to \Windows\Temp folder. It's configurable, but it would be nice if it defaults to AppData folder especially for a portable version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2013, 03:41:11 PM
Just to let you know, this bug is not fixed for ASR plugin. The thing is that it updates the two text files for both paths when MB starts, but when I launch ASR plugin it updates the files in \Windows\Temp folder only. Probably that's why it keeps doing that.
I missed several places in the code. That's fixed now. Thank you.

http://www.mediafire.com/download/5k1c0uk65pceg2f/mb_TagTools_2013-11-03.zip

Also Now Playing plugin's default folder for output files is still set to \Windows\Temp folder. It's configurable, but it would be nice if it defaults to AppData folder especially for a portable version.
I'll change defaults.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 03, 2013, 06:36:09 PM
Now they're all working great! Thank you for the update!
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on December 07, 2013, 09:20:33 AM
Something happened, probably related to changes in my screen resolution, and now when I try to run the Swap Tags command this is the box I get:

(http://i.imgur.com/CxW9oHs.png?1)

I can't resize it.  I've tried updating the plugin, disabling and enabling, etc, but it stays that size.  Any suggestions?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 08, 2013, 06:17:13 PM
Try to click 'Uninstall' in plugins prefs. This should remove plugin settings. Then restart MB.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on December 08, 2013, 06:35:06 PM
That got it, thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: timelezz on December 08, 2013, 11:47:45 PM
Hello, I try to use this plugin, but not with great success. I wish to replace snippets of text from the song title. Could someone guide me? For example: I want to remove the snippet "(Official Video)" from a song title. I've tried, but nothing happens. So obviously I do something wrong. Can someone explain what I should enter to make it work?

Ps. I did not read every single post here. Sorry when my question is already asked before.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on December 09, 2013, 12:43:37 AM
@ timelezz
using the Remove '(...)' or '[...]' from the end of '<Tag 1>' preset
change Tag 1 to Title
click Preview
if everything correct, click Apply
Title: Re: Additional Tagging and Reporting Tools
Post by: timelezz on December 09, 2013, 01:23:04 AM
Thank you, that worked!

And what can I do when I have a song title that says:  "Look Right Through (MK Remix) (Official Video) "  and I only want to remove the '(Official Video)' part?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 09, 2013, 03:51:28 AM
Copy preset 'Remove '(...) or '[...]' from <Tag 1>' and search for
Code
(.*?)\s*[\(\[][^\)\]]*?[\]\)]$
in <Tag 1>. Name new preset accordingly, click 'OK'. Apply new preset to appropriate tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: timelezz on December 09, 2013, 02:00:12 PM
Thank you. Isn't there a way to make it remove an (editable) set of given strings when they appear in the title?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 09, 2013, 02:25:48 PM
Isn't there a way to make it remove an (editable) set of given strings when they appear in the title?

MB's native Search & Replace (Under Tools> Tagging Tools) will do. Just leave empty for "replace with" part.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on December 19, 2013, 12:43:50 AM
from here (http://getmusicbee.com/forum/index.php?topic=11200.msg70074#msg70074)
Quote from: Steven
- support for the following predefined tags - see this topic
    Genres, Artists, Artists: Artist, Artists: Performer, Artists: Guest, Artists: Remixer

G'day boroda74
Just wanted to check if there will there be an update of the plugin to use these new tags?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 19, 2013, 04:55:07 AM
No, they are currently not exposed in api.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on December 20, 2013, 12:49:10 AM
No, they are currently not exposed in api.

Thanks for the info
I'll see if I can access them via a virtual tag
 :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 21, 2013, 09:54:37 AM
I'm going to add these new tags to my plugins on this weekend (thanks to Steven).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 21, 2013, 04:07:34 PM
New plugin version is released


http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools

MB latest update is required to use new tags:

http://musicbee.niblseed.com/V2_3/MusicBee_Exe_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 19, 2014, 04:08:58 PM
New plugin version is released:
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on January 23, 2014, 06:53:39 PM
Hey Boroda. This bug report (http://getmusicbee.com/forum/index.php?topic=11785.0) is related to the new version's Auto-Report command (more relevant details on my second post in that thread). In the status bar at the bottom, MB displays "Generating preview (reading): 4050 / 4098 file(s)". Incidentally, it displays this throughout the whole Auto-Report process. The rules for my Auto-Report are as follows :

<Album> (Grouping)
<Album Complete (V)> (Grouping)
<Playcount> (Sum)

Save only if <Album Complete (V)> is "Yes"
Save field <Playcount> (Sum) to <Album Playcount (Sum)>

<Album Complete (V)> is a virtual tag defined by $If($And($If($Or(<Album Complete?>="Y",<Complete Album>="Yes"),Yes,)="Yes",$If(<Release Type>="Album",Yes,)="Yes"),Yes,).

Shout if you need any other info. Auto-reports also seem to be taking a lot longer than normal reports did.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 24, 2014, 02:54:13 AM
Hi. As far as I understood your problem is solved by Steven.

Auto-reports also seem to be taking a lot longer than normal reports did.
This is maybe because background threads have lower priority in my plugin, not sure though.
Title: Re: Additional Tagging and Reporting Tools
Post by: hisuwh on February 01, 2014, 06:19:43 AM
Hey I got the following bug report when clicking "New Preset" in Auto-report
the preset list was empty

MusicBee v2.2.5069.34742 (Win6.1), 1 Feb 2014 19:12:

System.OutOfMemoryException: List box contains too many items.
   at System.Windows.Forms.ListBox.NativeAdd(Object item)
   at System.Windows.Forms.ListBox.ObjectCollection.AddInternal(Object item)
   at System.Windows.Forms.ListBox.ObjectCollection.Add(Object item)
   at MusicBeePlugin.AutoLibraryReportsPlugin.buttonAddPreset_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 01, 2014, 10:19:23 AM
Yes I can reproduce this. Thanks for bug report.

EDIT: This fixed:

http://www.mediafire.com/download/y9j9fu6dv4qdozq/mb_TagTools_2014-02-01.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: hisuwh on February 02, 2014, 12:29:33 AM
Thanks for the swift response. It is working now.
Though it is taking an awful long time to complete.
Otherwise great plugin.

I have been trying to think if there is a better way to average rate albums.
The problem with taking an average rating is that an otherwise awesome album is dragged down by one or 2 mediocre songs.

A couple of fillers doesn't make an awesome album bad in my opinion - and they often add to the character of the album, even if you wouldn't listen to them individually. 

For example Fatboy Slims - You've Come a Long Way Baby is probably one of my favourite albums.  I've rated 7 of the 11 songs 5 stars and would say it is a 5 star album but the average drags it down.

I don't know if there is a better way to do this?  Or a way to skew the average based on another factor (mode / number of 5 star tracks / number of positive tracks ).  Any thoughts from the community?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 09, 2014, 05:00:22 PM
Have a look at this issue:

http://getmusicbee.com/forum/index.php?topic=10396.msg72675#msg72675

I have "Convert Track ReplayGain to SoundCheck format for m4a" preset auto-applied to "m4a" auto-playlist, and found out that it disables loving and unloving while an m4a file is playing. But no such issue with mp3 files though I have "Convert Track ReplayGain to SoundCheck format for mp3" preset auto-applied to "mp3" auto-playlist as well. Maybe something with the m4a preset code?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 09, 2014, 05:26:25 PM
On further tests, it happens with mp3 as well. Such an issue doesn't occur if I do not auto-apply those presets. Could be something about filtering thru playlists.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on February 12, 2014, 01:15:45 AM
Having some problems with the plugin Boroda. I thought it might be something that was happening without the plugin, but I disabled it for a week as a test. Didn't experience it once, but re-enabling it today gave me the problem again.

What is essentially happening is that when I hibernate the computer with MB open, then load the computer up again, MB becomes unresponsive and can't be closed without task manager. I haven't managed to isolate the exact reason as to why it doesn't happen every time. I think it's probably something to do with my auto-report though. I have the following auto-report set up, although it's currently disabled as waiting for it to finish slowed down tag editing too much.

<Album> (Grouping)
<Album Complete (V)> (Grouping)
<Playcount> (Sum)

Save only if <Album Complete (V)> is "Yes"
Save field <Playcount> (Sum) to <Album Playcount (Sum)>

<Album Complete (V)> is a virtual tag defined by $If($And($If($Or(<Album Complete?>="Y",<Complete Album>="Yes"),Yes,)="Yes",$If(<Release Type>="Album",Yes,)="Yes"),Yes,).

Also, feature request/question - what's the reason behind the summation reports being applied to all files in an auto-report, regardless of the Save only condition? This is one of the reasons that the auto-report takes too long for me to have it permanently applied.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 12, 2014, 09:08:14 AM
Having some problems with the plugin Boroda. I thought it might be something that was happening without the plugin, but I disabled it for a week as a test. Didn't experience it once, but re-enabling it today gave me the problem again.

What is essentially happening is that when I hibernate the computer with MB open, then load the computer up again, MB becomes unresponsive and can't be closed without task manager. I haven't managed to isolate the exact reason as to why it doesn't happen every time. I think it's probably something to do with my auto-report though. I have the following auto-report set up, although it's currently disabled as waiting for it to finish slowed down tag editing too much.

<Album> (Grouping)
<Album Complete (V)> (Grouping)
<Playcount> (Sum)

Save only if <Album Complete (V)> is "Yes"
Save field <Playcount> (Sum) to <Album Playcount (Sum)>

<Album Complete (V)> is a virtual tag defined by $If($And($If($Or(<Album Complete?>="Y",<Complete Album>="Yes"),Yes,)="Yes",$If(<Release Type>="Album",Yes,)="Yes"),Yes,).
At the moment I'm very busy at my work. I'll try to test plugin with hibernating (never tried this) when I can.

Also, feature request/question - what's the reason behind the summation reports being applied to all files in an auto-report, regardless of the Save only condition? This is one of the reasons that the auto-report takes too long for me to have it permanently applied.
As I understand you mean that 'Save only...' option does nothing for you? It's strange and this is a bug if it's so. I'll check this later.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on February 13, 2014, 09:06:26 PM
Also, feature request/question - what's the reason behind the summation reports being applied to all files in an auto-report, regardless of the Save only condition? This is one of the reasons that the auto-report takes too long for me to have it permanently applied.
As I understand you mean that 'Save only...' option does nothing for you? It's strange and this is a bug if it's so. I'll check this later.

These are the settings for my Auto-Report

 (https://dl.dropboxusercontent.com/u/50123406/Auto-Library%20Report.png)
(https://dl.dropboxusercontent.com/u/50123406/Auto-Library%20Report.png)
[/url]

The calculated field is being saved to every file. When I first read the message I've ringed in red, I thought that it meant that any fields that were calculated would be saved to every file. However, re-reading it, it sounds like it is a bug I'm experiencing, as it's ignoring the 'Save Only...' option. This doesn't happen with the normal library report.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 20, 2014, 01:34:03 PM
New plugin version is released


http://www.mediafire.com/download/y95jhv7sh2hv2lo/mb_TagTools_2014-02-20.zip

@Pingaware
Please check that problems you experienced are solved.

@redwing
UI refreshing is rewritten again. Maybe loving tracks issue is also solved now. Please check it.  
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on February 20, 2014, 10:01:47 PM
  • Fixed checking condition in 'Auto library reports' command.
This one's now working fine. Haven't had a chance to test out the other one yet. I'll get back to you in a week after some proper testing. Cheers for the fix boroda!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 20, 2014, 11:35:01 PM
Maybe loving tracks issue is also solved now. Please check it.  

No differences.
As I said, it's working fine when a track is not playing, but doesn't work while a track is playing for all m4a files and some mp3 files. 
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 21, 2014, 08:12:36 AM
I did some more tests, and it looks like the bug occurs only when SoundCheck presets are auto-applied (happens even when filtering through a playlist is not enabled). I have two track gain presets auto-applied.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 21, 2014, 10:39:33 AM
Thanks, redwing. I'll take a look at this issue tonight.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 12:08:46 PM
@redwing
What I can reproduce: trying to change 'love' status of playing track twice usually invokes infinite loop of applying asr preset(s) after playback of track is finished. Also sometimes status is not changed second time in this case. Is this what you meant?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 22, 2014, 12:18:16 PM
Not sure about the first part, but what I can't do is changing love status while a track is playing, yes, from second time. But first time change is not saved in file either most time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 12:28:21 PM
ok
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 01:46:30 PM
@redwing
This version is working for me, please try it:

http://www.mediafire.com/download/cqb5ebd7opk95z6/mb_TagTools_2014-02-22.zip

There is one issue though: if you love/unlove/ban playing track in player controls panel then there may be some delay (1-3 sec.) in changing track 'love' status. And no delay if you love/ban track in the column of main panel. I think its something on MB side.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 22, 2014, 01:55:58 PM
Thanks! It's working with a delay as you described but for some tracks still not working at all. Main panel is just working fine. Why does this happen only with those presets?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 02:07:17 PM
Why does this happen only with those presets?
I think it happens with any ticked for auto applying preset.

It's working with a delay as you described but for some tracks still not working at all. Main panel is just working fine.
How do you think, should we ask Steven to fix it?

BTW it seems that refreshing multiple tag editor is working now (with delay up to 5 sec.)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 22, 2014, 02:11:57 PM
No, I think it's SoundCheck preset specific problem. I have swap preset auto-applied to classical playlist, and have no problem loving and unloving while any classical track is playing, if I disable those SoundCheck presets. There's no delay at all.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 02:20:06 PM
I have delay with 'swap' preset only applied. Delay may vary though and may be almost unnoticeable sometimes.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 22, 2014, 02:30:00 PM
BTW it seems that refreshing multiple tag editor is working now (with delay up to 5 sec.)

I just tested this, and it's working much worse. When trying to edit multiple files at once, it pops up confirmation dialog several times, and often fails to locate files saying unable to find files. Sometimes swap preset doesn't rewrite tags. All of these did not happen before.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 22, 2014, 02:40:18 PM
For the love status problem, if you can't fix it, that's ok. I can disable those presets while playing tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 03:02:39 PM
I'll revert recent changes back and try another approach to fix loving problem.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 03:39:52 PM
Behavior is reverted back, loving from main panel works, from player control doesn't:

http://www.mediafire.com/download/oub0bh67676zm7j/mb_TagTools_2014-02-22-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 22, 2014, 05:04:51 PM
@redwing
Try this version of plugin:

http://www.mediafire.com/download/oub0bh67676zm7j/mb_TagTools_2014-02-22-2.zip

with MB latest patch:

http://musicbee.niblseed.com/V2_3/MusicBee_Exe_Patched.zip

It seems that all asr bugs are fixed now (except for multiple-files tag editor is not refreshing on changes made by asr).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 22, 2014, 10:10:41 PM
Now no more love status bug. Working perfect with no delay while a track is playing. Thanks!

Regarding multiple tag editing, are there any differences between the two 2-22-2 dll files? They look just the same in their file size and modified date. Yet, previous version is working without issue (except refreshing the changed tag value) while current version sometimes does not work properly: file gets missing, auto-applied preset fails rewriting tags, etc.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 23, 2014, 08:58:50 AM
Regarding multiple tag editing, are there any differences between the two 2-22-2 dll files? They look just the same in their file size and modified date.
No, they are the same. I just reposted the link .

Yet, previous version is working without issue (except refreshing the changed tag value) while current version sometimes does not work properly: file gets missing, auto-applied preset fails rewriting tags, etc.
Could you be more specific?
Title: Re: Additional Tagging and Reporting Tools
Post by: Moss on February 25, 2014, 06:41:51 AM
Hi,

by every start from MusicBee I got this error message.



Can you tell me whats wrong. What can I do?

Moss
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 25, 2014, 03:50:40 PM
Hi. Post the content of mentioned .txt file.
Title: Re: Additional Tagging and Reporting Tools
Post by: Moss on February 25, 2014, 05:06:12 PM
Adding Titel / TrackTitle
Adding Album / Album
Adding Album-Künstler (displayed) / AlbumArtist
Adding Album-Künstler / AlbumArtistRaw
Adding Künstler (displayed) / -1
Adding Künstler / -2
Adding Cover / Artwork
Adding BPM / BeatsPerMin
Adding Komponist (displayed) / -3
Adding Komponist / -4
Adding Kommentar / Comment
Adding Dirigent / Conductor
Adding Disk-Nr. / DiscNo
Adding Disk-Anzahl / DiscCount
Adding Encoder / Encoder
Adding Genre / Genre
Adding Genrekategorie / GenreCategory
Adding Gruppierung / Grouping
Adding Schlüsselwörter / Keywords
Adding Texter / Lyricist
Adding Stimmung / Mood
Adding Anlass / Occasion
Adding Herkunft / Origin
Adding Verlag / Publisher
Adding Qualität / Quality
Adding Bewertung / Rating
Adding Album-Bewertung / RatingAlbum
Adding Lieben / RatingLove
Adding Tempo / Tempo
Adding Titelnr. / TrackNo
Adding Titel-Anzahl / TrackCount
Adding Jahr / Year
Adding Liedtext? / HasLyrics
Adding Virtual1 / Virtual1
Adding Virtual2 / Virtual2
Adding Virtual3 / Virtual3
Adding Virtual4 / Virtual4
Adding Virtual5 / Virtual5
Adding Virtual6 / Virtual6
Adding Virtual7 / Virtual7
Adding Virtual8 / Virtual8
Adding Virtual9 / Virtual9
Adding Virtual10 / Virtual10
Adding Virtual11 / Virtual11
Adding Virtual12 / Virtual12
Adding Virtual13 / Virtual13
Adding Virtual14 / Virtual14
Adding Virtual15 / Virtual15
Adding Virtual16 / Virtual16
Adding Liedtext / -5
Adding Liedtext (synchronized) / -6
Adding Liedtext (unsynchronized) / -7
Adding <Null> / -20
Adding Sort Artist / Custom1
Adding Sort Album Artist / Custom2
Adding Custom3 / Custom3
Adding Custom4 / Custom4
Adding Custom5 / Custom5
Adding Custom6 / Custom6
Adding Custom7 / Custom7
Adding Custom8 / Custom8
Adding Custom9 / Custom9
Adding Custom10 / Custom10
Adding Custom11 / Custom11
Adding Custom12 / Custom12
Adding Custom13 / Custom13
Adding Custom14 / Custom14
Adding Custom15 / Custom15
Adding Custom16 / Custom16
Adding Genres / Genres
Adding Künstler / Artists
Cant add Künstler / Artists
Adding Künstler: Künstler / ArtistsWithArtistRole
Adding Künstler: Performer / ArtistsWithPerformerRole
Adding Künstler: Gast / ArtistsWithGuestRole
Adding Künstler: Remixer / ArtistsWithRemixerRole
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 26, 2014, 04:08:28 AM
Its strange that German translation of 'Artist' and 'Artists' tags are the same for your MB (tag names are duplicated). Go to Edit> Prefs> Layout (1)> Configure fields and rename Artists field from 'Künstler' to German multiple form of word or to something else other than 'Künstler'.
Title: Re: Additional Tagging and Reporting Tools
Post by: Moss on February 26, 2014, 01:33:24 PM
now it's ok, thanks...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2014, 03:17:36 AM
New plugin version released


http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2014, 04:21:55 AM
New plugin version released


http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 03, 2014, 05:01:31 AM
Working great! This saved me two hotkeys, which I can now assign to other commands.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2014, 09:09:30 AM
Do you mean 'Show commands in context menu' option? Thanks to Steven :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 08, 2014, 06:02:37 AM
Came from here: http://getmusicbee.com/forum/index.php?topic=12221.0

There's a problem writing MB's 5 point scale rating values (when sent to clipboard with <rating> in Tags(2) setting) back to files. Tried with both clipboard and text file options, but "No rating" does not overwrite the file's existing rating value. Preview shows correctly, though.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 08, 2014, 07:15:34 AM
BTW when I tried to run copy command with text file option without choosing a text file, it gave me a long error message. Maybe it could just return focus to the text file selection box instead since it's most likely the user simply overlooked to do so.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 08, 2014, 10:55:23 AM
There's a problem writing MB's 5 point scale rating values (when sent to clipboard with <rating> in Tags(2) setting) back to files. Tried with both clipboard and text file options, but "No rating" does not overwrite the file's existing rating value. Preview shows correctly, though.
Can't reproduce what you said, but there was a bug with ratings. Ratings in text file/clipboard must be in 0-5 range.

BTW when I tried to run copy command with text file option without choosing a text file, it gave me a long error message. Maybe it could just return focus to the text file selection box instead since it's most likely the user simply overlooked to do so.
I've added simple error message "File not found!" if source files doesn't exist or file name is empty.

http://www.mediafire.com/download/3dc1c74725ss85f/mb_TagTools_2014-03-08.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 08, 2014, 11:21:24 AM
The bug wasn't fixed. It's working fine with all other ratings including bomb. It doesn't work properly only when overwriting an existing value with "No Rating". It doesn't clear it, and the file keeps the old rating value. You can't reproduce this?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 08, 2014, 11:47:57 AM
Working fine for me overwriting bomb, empty or any other rating. I don't understand how initial value of rating might affect 'copy tag' command behavior if you don't tick "Append source tag to the end of destination tag placing between them:" or "Add source tag to the beginning of destination tag placing between them:" options.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 08, 2014, 12:53:28 PM
As I said, it doesn't work properly only when overwriting an existing value with "No Rating". I never said existing values somehow affects the plugin.  Even though preview shows correctly "No Rating" as new values in red, it fails to clear existing values. If you can't reproduce it, never mind.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 08, 2014, 08:08:20 PM
Excuse me if you take my previous post offensive and/or you tired of testing my plugin, but i really can't reproduce issues you experience. I'm ready to prepare debug version of plugin, but I'm not sure what must be logged,. For ratings ''copy tag" command just uses standard Library_SetFileTag/Library_CommitTagsToFile functions without any workarounds. And copying ratings from text file works fine for me.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 09, 2014, 03:34:54 PM
Perhaps you misunderstood what I meant by "No Rating", by which I virtually meant such a character string, not a "null" value.

There's a problem writing MB's 5 point scale rating values (when sent to clipboard with <rating> in Tags(2) setting) back to files. Tried with both clipboard and text file options, but "No rating" does not overwrite the file's existing rating value. Preview shows correctly, though.

Those are what I got from MB's send to-clipboard feature. MB puts "No Rating"(without quote) for not-rated tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 10, 2014, 10:37:28 AM
Hope this time I understood you correctly. This this version:

http://www.mediafire.com/download/3o54oi4aum6lpns/mb_TagTools_2014-03-10.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 10, 2014, 10:56:22 AM
Works like a charm! Tried both with the string and with no value, and all worked fine. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 14, 2014, 05:48:34 PM
There's another panel where auto-application of ASR plugins interferes with changing ratings of playing track.
It's track info panel with "playing track" selected. When a track is playing I cannot change ratings from second time for some tracks. Changing love status is working fine. If I disable SoundCheck conversion presets, then I can change ratings on that panel for any files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2014, 09:14:39 AM
@redwing
It seems to be an MB issues. I've reported it to Steven, but don't know his reaction.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on March 18, 2014, 11:03:49 AM
Need a bit of help please.
I'm trying to duplicate all my Mp3tag actions with the AT&R Tools plugin.
I've got almost all done, but my limited knowledge of regex has got me stumped with this one:
Custom tag - Release Date Sort - numerical in the form YYYYmmdd.
Mp3tag action checks to see if dd is in range 01 to 31 then saves dd/mm/YYYY in Year tag otherwise only saves YYYY.
Anybody know how to do this in Tagging Tools?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2014, 01:43:58 PM
Need a bit of help please.
I'm trying to duplicate all my Mp3tag actions with the AT&R Tools plugin.
I've got almost all done, but my limited knowledge of regex has got me stumped with this one:
Custom tag - Release Date Sort - numerical in the form YYYYmmdd.
Mp3tag action checks to see if dd is in range 01 to 31 then saves dd/mm/YYYY in Year tag otherwise only saves YYYY.
Anybody know how to do this in Tagging Tools?

This would work for that.

(http://i.imgur.com/RtY2CE5.png)


For easy copy & paste,

(\d\d\d\d)([1][0-2]|[0]\d)([3][0,1]|[0-2]\d)

$3/$2/$1

(\d\d\d\d)(\d\d\d\d)

$1
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2014, 06:57:44 PM
Thanks, redwing! You are my best friend :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2014, 07:54:07 PM
New plugin version:


http://www.mediafire.com/download/gz4jjaava1wt38c/mb_TagTools_2014-03-18.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2014, 08:58:26 PM
Looks good! Just tested and it can write all different text into up to 3 tags at the same time with the following setting.


(http://i.imgur.com/0NN4Fk0.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on March 18, 2014, 09:03:06 PM
There's another panel where auto-application of ASR plugins interferes with changing ratings of playing track.
It's track info panel with "playing track" selected. When a track is playing I cannot change ratings from second time for some tracks. Changing love status is working fine. If I disable SoundCheck conversion presets, then I can change ratings on that panel for any files.
i dont have your set up so i am doing some guesswork, but i think this should resolve the issue:
http://musicbee.niblseed.com/V2_4/MusicBee_Exe_Patched.zip

If it doesnt work, could you reply to a new bug topic
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2014, 09:09:22 PM
There's another panel where auto-application of ASR plugins interferes with changing ratings of playing track.
It's track info panel with "playing track" selected. When a track is playing I cannot change ratings from second time for some tracks. Changing love status is working fine. If I disable SoundCheck conversion presets, then I can change ratings on that panel for any files.
i dont have your set up so i am doing some guesswork, but i think this should resolve the issue:
http://musicbee.niblseed.com/V2_4/MusicBee_Exe_Patched.zip

If it doesnt work, could you reply to a new bug topic

Yes, it's fixed. Thanks a lot!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2014, 09:27:58 PM
Another preset request:

Can you create a preset that checks cases in <Title> and <Album> field and change cases like this if anything is wrong?

(http://i.imgur.com/tcIPlku.png)


I can do this manually using Change Cases command, but the problem is I have to apply this to all files once in a while.
If there's such preset, then I could just auto-apply it and forget about it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2014, 10:49:37 PM
Its possible to create any function for ASR (currently there are only \@null($1) and \@rg2sc($1) functions). Do you need only 'title case' function or all functions of 'change case' command?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2014, 11:07:48 PM
What I need is the following three:

- Title case
- Exception word list
- "Always capitalize first word in tag" option

Then the preset checks (1) if first word is uppercase or not, (2) if all exception words are lowercase or not, and (3) if all words other than exception words are uppercase or not for the specified tags.

Probably this is sufficient for the standard format, but of course others might need other functions and options as well.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on March 19, 2014, 12:23:20 AM
Thanks heaps redwing

Made a slight change to the second part:

(\d\d\d\d)(\d\d\d\d)

$1

to

Code
(\d\d\d\d)([1][0-2]|[0]\d)([00]\d)

$1

so it didn't write 00/00/YYYY when dates weren't valid.

I could even try to like yellow more for your help with this  :)

(Nahhh.  That's not gonna happen  :D  )
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2014, 04:35:04 AM
I could even try to like yellow more for your help with this  :)
:)
Title: Re: Additional Tagging and Reporting Tools
Post by: June on March 19, 2014, 09:09:01 AM
Hi, I'm currently using 4ASR - one of them for date created (thanks again for that) and 3 'Copy-tags' to remove unwanted tag fields.
The problem is that Musicbee stops after around 4~10songs -The process seems to be running in task manager, just the window is unresponsive and no report is given. I can manage it fine by enable the plugin only when adding new songs but would you have any idea what might cause this problem?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2014, 09:13:58 AM
Thanks heaps redwing

Made a slight change to the second part:

(\d\d\d\d)(\d\d\d\d)

$1

to

Code
(\d\d\d\d)([1][0-2]|[0]\d)([00]\d)

$1

so it didn't write 00/00/YYYY when dates weren't valid.

I could even try to like yellow more for your help with this  :)

(Nahhh.  That's not gonna happen  :D  )

This one should work better in validating dates.

^((19|20)\d\d)(0[1-9]|1[012])(0[1-9]|[12][0-9]|3[01])$

$4/$3/$1

And there's no point editing second part as it's just capturing first four digits.

(\d\d\d\d)(\d\d\d\d)

$1

I saw some regex that take into account even leap year, but it must be an overkill for this use.


If this works, you should try Citrine for a week to investigate why your hate yellow so much.

Of course, I'm kidding.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on March 19, 2014, 09:30:19 AM
Hi, I'm currently using 4ASR - one of them for date created (thanks again for that) and 3 'Copy-tags' to remove unwanted tag fields.
The problem is that Musicbee stops after around 4~10songs -The process seems to be running in task manager, just the window is unresponsive and no report is given. I can manage it fine by enable the plugin only when adding new songs but would you have any idea what might cause this problem?
I'm not very familar with how the ASR works - in your case is it reacting to when you save a file in the tag editor or if not, can you explain what is triggering the ASR to perform an action?
Title: Re: Additional Tagging and Reporting Tools
Post by: June on March 19, 2014, 09:51:12 AM
I'm not very familar with how the ASR works - in your case is it reacting to when you save a file in the tag editor or if not, can you explain what is triggering the ASR to perform an action?

Editing tag invokes the presets as far as I know. So it left me blank because MB plays the song till the end for when the error occurs and the next song is kinda stuck at buffering (minilyrics showing the lyrics trembling)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2014, 10:03:50 AM
I would test each preset one by one, and then combining them gradually to narrow down what preset causes the problem. Also pay attention to what specific action with MB, and with what kind of files, leads to the crash.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on March 19, 2014, 01:36:53 PM
Editing tag invokes the presets as far as I know. So it left me blank because MB plays the song till the end for when the error occurs and the next song is kinda stuck at buffering (minilyrics showing the lyrics trembling)
is your library auto-organised and if so, do you think one of the fields that affects file naming might have been changed (by yourself or by the ASR)?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2014, 01:52:43 PM
New plugin version released:


http://www.mediafire.com/download/nog19x1azdqjy7y/mb_TagTools_2014-03-19.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2014, 01:55:21 PM
Hi, I'm currently using 4ASR - one of them for date created (thanks again for that) and 3 'Copy-tags' to remove unwanted tag fields.
The problem is that Musicbee stops after around 4~10songs -The process seems to be running in task manager, just the window is unresponsive and no report is given. I can manage it fine by enable the plugin only when adding new songs but would you have any idea what might cause this problem?
The similar problem was in past when plugin started to update UI periodically instead of on every track update. I'll try to check this.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2014, 05:08:07 PM
New plugin version released:
  • New ASR preset 'TOY: Change case'. Don't forget to import presets after upgrading plugin.


http://www.mediafire.com/download/nog19x1azdqjy7y/mb_TagTools_2014-03-19.zip

Working excellent! Thanks a lot!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2014, 06:33:02 PM
I did some more research on title case, and hope the following two features could be added. Then it would be nearly perfect.

- Always capitalize last word, too:
I didn't pay much attention to this, but it's the rule most styles require for title case however awkward they might look sometimes.

- User input text that will be respected over any other rules:
This is for handing phrasal verbs that should be always uppercase and some special cases where mixed cases are required. Custom Text 2 box could be used for this with the following format:

Beat Up; Blow Out; Break Down; The Bad Seeds

Of course, the user should manually input "Blew Out" and "Blown Out" too if they are in his collection since the preset can't take care of tenses.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2014, 06:38:45 AM
- Always capitalize last word, too:
I didn't pay much attention to this, but it's the rule most styles require for title case however awkward they might look sometimes.
Its done.

- User input text that will be respected over any other rules:
This is for handing phrasal verbs that should be always uppercase and some special cases where mixed cases are required. Custom Text 2 box could be used for this with the following format:

Beat Up; Blow Out; Break Down; The Bad Seeds
Too difficult to do.

http://www.mediafire.com/download/eno6zpcqaaicf4v/mb_TagTools_2014-03-20.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 20, 2014, 01:03:06 PM
Works like a charm! Now I can forget about managing title case manually. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 20, 2014, 06:15:00 PM
Did some more tests with the new preset, and found that it doesn't change exception words to lowercase when they are uppercase.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2014, 10:50:56 AM
This was intensional, but I agree this was a bad idea. Its fixed now:

http://www.mediafire.com/download/qgrlxcdpxnp50ep/mb_TagTools_2014-03-21.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2014, 12:12:51 PM
Thanks, now it's working fine.

I also thought that was intentional and liked it at first because it allowed manual change of case for those exception words. But in the end, there's no way to tell auto-fixed titles from manually edited titles.

I'm working on a how-to guide on this preset and will post it later.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2014, 12:48:47 PM
I'm working on a how-to guide on this preset and will post it later.
Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2014, 01:15:44 PM
The preset is not working properly when applied multiple times. Apply it to a track multiple times. It sort of toggles to a correct and a wrong result.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2014, 02:44:17 PM
Very strange bug. Not sure what was the matter, but new version works correctly

http://www.mediafire.com/download/ekand3m2m09gi2s/mb_TagTools_2014-03-21-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2014, 03:37:35 PM
It seems the linked file is identical to the previous version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2014, 06:32:10 PM
It seems the linked file is identical to the previous version.
Yes, but preset 'Change case' is modified.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2014, 06:42:20 PM
I'm not sure what you mean. Every file is identical, and there's no change when applied.

This is the preset's modified date. Is this latest one?

<modified>2014-03-21T09:44:56.1340713Z</modified>
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2014, 06:53:08 PM
My fault. I've reuploaded plugin zip:

http://www.mediafire.com/download/xkigtw1g44a648c/mb_TagTools_2014-03-21-3.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2014, 07:07:49 PM
Now it's working perfect! Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 26, 2014, 08:44:31 PM
Opening the plugin either closes MB or shows the following error.

MusicBee v2.4.5197.34757 (Win6.1)

System.ObjectDisposedException: Cannot access a disposed object.
Object name: '#=qjFxC$WZQtDA7lOl4V2LcEju4grbRfUm4HxVxS3RjiKo='.
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Form.UpdateHandleWithOwner()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
   at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
   at MusicBeePlugin.PluginWindowTemplate.display()
   at MusicBeePlugin.Plugin.asrEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 26, 2014, 09:11:32 PM
The previous error was resolved by updating the plugin to the latest version. BTW you didn't post the latest version. I got it from your source files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2014, 08:29:30 AM
Yes, I'm waiting resolving Pingaware's bug, then I'll post new binary.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2014, 12:51:18 AM
Could you add one more function to the Change case preset? It's about handling acronyms like "U.F.O." and "L.A. Woman". Currently it converts them to "U.f.o." and "L.a. Woman". Can you add a rule that any single letter coming before a period gets converted to uppercase? If it's multiple letters before a period like "Ver." or "Mr.", then they should be left as is.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2014, 05:59:33 AM
Thanks for pointing to one important thing I completely ignored when wrote 'Change Case' command.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2014, 06:54:10 AM
http://www.mediafire.com/download/rzbkeimfr9l38nk/mb_TagTools_2014-03-29.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2014, 07:17:16 AM
Thanks for the quick update! But it doesn't seem to work. I noticed only dll file got updated and no update with the preset file. Is that correct?

Or this update is not about the preset?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2014, 07:20:07 AM
Yes, this is correct. Works for me. Are using 'Change case' command or ASR preset? For 'Change case' command you should tick 'Words splitters' option and add period to word splitters.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2014, 07:26:21 AM
Yes, this is correct. Works for me. Are using 'Change case' command or ASR preset? For 'Change case' command you should tick 'Words splitters' option and add period to word splitters.

Actually I meant the ASR preset. I now see the option added to the command, though.

Can you add it to the preset, not as an option but as part of its function?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2014, 07:29:06 AM
I've found a bug. Will post update later.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2014, 07:36:03 AM
Haven't tested very well. New version should work for both 'Change case' command and 'Change case' ASR preset:

http://www.mediafire.com/download/zdrudwff76a961i/mb_TagTools_2014-03-29-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2014, 07:51:28 AM
Yes, it's working great! Thanks!

But there's one problem. It now converts "feat." to "Feat." even though I included it in the exception word list. So my guess is the rule overrides the exception words list just like the first and last word capitalization rules. But can you, if possible, change this rule to respect the exception word list since it doesn't have to be applied absolutely unlike the first and last word rules?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2014, 08:10:14 AM
Add "feat" (without period) to excepted words
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2014, 08:15:30 AM
Add "feat" (without period) to excepted words

That works! The only problem would be when "feat" is used as a noun in title, but those rare cases could be handled as an exception track. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on March 29, 2014, 09:31:50 PM
I've got space as a hotkey for pause/play. It's not a global hotkey, but regardless, I can't type a space in any of the text boxes in the plugin without disabling my hotkey briefly. Bug?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 30, 2014, 07:40:37 AM
Its a known bug, but can't resolve it without Steven's help.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 03, 2014, 02:25:48 AM
I was trying to copy a virtual tag to <Artists: Guest> field using Copy tag command, but it didn't work. It properly shows new values for preview, but does not update anything after clicking on proceed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 03, 2014, 08:01:28 AM
Working fine here. Check options, especially "Copy only if destination tag is empty"
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 03, 2014, 08:16:42 AM
No option is ticked. Not working at all regardless of file format. Are you sure it creates TXXX/Guest Artist field with the value when copied to the field?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 03, 2014, 09:05:05 AM
Sorry, probably I misunderstood you. Are copying *to* or *from* Artists (Guest) tag? 1st option is not tested at all.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 03, 2014, 09:28:57 AM
This is my first time trying a sub-artist field. A little surprising to hear no one has ever used this plugin for tagging those fields. Yes, I'm trying to copy to the field, not from.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 03, 2014, 03:12:49 PM
I think its not supported by MB, but I could create ASR preset to copy any tag to guest artists.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 04, 2014, 01:27:05 AM
I could create ASR preset to copy any tag to guest artists.

That'd be great!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 04, 2014, 06:25:14 AM
Could you also create a new preset that removes all duplicate entries from a multi-value field like genre and artist?
That'd be useful for various cases including the request in this thread: http://getmusicbee.com/forum/index.php?topic=12441.0
Would be great if the preset could remove multiple kinds of duplicate entries at once regardless of their places (consecutive or not).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 04, 2014, 06:31:51 AM
http://www.mediafire.com/download/s87uco67sc2l5i7/mb_TagTools_2014-04-04.zip

See new ASR preset 'Copy guest artists from <Tag 1>'
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 04, 2014, 06:49:56 AM
http://www.mediafire.com/download/s87uco67sc2l5i7/mb_TagTools_2014-04-04.zip

See new ASR preset 'Copy guest artists from <Tag 1>'

Working great! Thanks!

- There's a typo in the preset name
- How about using MB default delimiter "; " instead of ","?
- Can you show in the dialog just guest artist tag values? Currently it shows them along with artist values that could be confusing.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 04, 2014, 08:10:18 AM
- There's a typo in the preset name
- How about using MB default delimiter "; " instead of ","?
That's fixed for the net update

- Can you show in the dialog just guest artist tag values? Currently it shows them along with artist values that could be confusing.
This would require rewriting the entire ASR command. Don't want to do this.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 04, 2014, 08:36:48 AM
Could you also create a new preset that removes all duplicate entries from a multi-value field like genre and artist?
That'd be useful for various cases including the request in this thread: http://getmusicbee.com/forum/index.php?topic=12441.0
Would be great if the preset could remove multiple kinds of duplicate entries at once regardless of their places (consecutive or not).
See ASR preset 'Remove duplicated entries from <Tag 1>'

http://www.mediafire.com/download/88pjrri86eyto6r/mb_TagTools_2014-04-04-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 04, 2014, 09:05:42 AM
See ASR preset 'Remove duplicated entries from <Tag 1>'

http://www.mediafire.com/download/88pjrri86eyto6r/mb_TagTools_2014-04-04-2.zip

Thanks! It works, but with some limitations.

- For genre tag, it removes one duplicate entry at a time. So for the given string "Funk; Funk; Funk; Pop; Pop", it needs to be applied 4 times to make it "Funk; Pop".
- For some reason, artist tag doesn't show a semicolon between multiple artists on the plugin dialog. Because of this, I can't make the preset work for artist field.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 04, 2014, 09:54:03 AM
It works, but with some limitations.

- For genre tag, it removes one duplicate entry at a time. So for the given string "Funk; Funk; Funk; Pop; Pop", it needs to be applied 4 times to make it "Funk; Pop".
Its a known limitation, but I'm afraid I can't avoid it.

- For some reason, artist tag doesn't show a semicolon between multiple artists on the plugin dialog. Because of this, I can't make the preset work for artist field.
See new ASR presets "Remove duplicated entries from tag 'Artist'"

http://www.mediafire.com/download/1k8cr39mmkdzada/mb_TagTools_2014-04-04-4.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 04, 2014, 10:14:17 AM
Working great! Thanks a lot!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2014, 01:31:37 PM
How about naming ASR preset xml files with their preset title, if that doesn't affect any functionality? That would make it a lot easier to handle those files along with custom preset files in AppData folder. Currently I have to open each file with notepad to figure out what preset it is.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2014, 02:00:24 PM
Initial idea was to abstract from preset names because every preset can have several localized names (usually only Russian and English, but there may be German, French and Polish names also). Its too hard to change this now.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2014, 02:04:32 PM
Understood. Then can I change their names in my plugin folder and AppData folder? Does that have any effect on functionality?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2014, 02:20:51 PM
Yes, you can as long as you don't edit them (to edit 'standard' presets just create empty file 'devmode.txt' in 'Plugins' folder). Also importing may be incorrect if you rename presets (suggest that presets will be duplicated on importing).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2014, 02:39:14 PM
I changed all of my custom preset xml file names in AppData folder. Now the plugin dialog lists none of those custom presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2014, 02:41:55 PM
I'll see source code.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2014, 02:53:07 PM
As far as I can see from source code you can rename presets as long as you keep double extension ".ASR Preset.xml"
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2014, 02:58:28 PM
It worked! Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2014, 03:14:27 PM
After re-launching MB, all edited names are gone. I guess I have to stick with the default file names.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 05, 2014, 11:42:38 PM
As far as I can see from source code you can rename presets as long as you keep double extension ".ASR Preset.xml"

Wouldn't you also have to change the GUID reference in the preset .xml to match the new custom preset name?
Or would "guid.CustomName.ASR Preset.xml" work?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 06, 2014, 04:00:22 AM
As far as I can see from source code you can rename presets as long as you keep double extension ".ASR Preset.xml"

Wouldn't you also have to change the GUID reference in the preset .xml to match the new custom preset name?
Or would "guid.CustomName.ASR Preset.xml" work?

Tried both, but nothing worked.
Also tried importing a standard preset after edited its name, but the plugin dialog is not listing the preset even though it's imported to AppData folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: blau on April 09, 2014, 02:53:49 PM
Hello,

I would like te be able to get the last word of the path where a mp3 reside and copy the result into a custom tag.
An example would be:
Path: D:\Music\Pop\Adele\Adele_Live-1980-CD\

Is this possible to achieve with ASR? I have tried editing some of the profiles but my skills don't allow me get anywhere.

Note: The path varies because the files are scattered in various drives.
In this case i think the value would be copied toe TXXX/MEDIA or TMED

Thank you very much
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 09, 2014, 04:10:49 PM


http://www.mediafire.com/download/ipkba7tg2o8pyyp/mb_TagTools_2014-04-09.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: blau on April 09, 2014, 05:21:01 PM
Awesome!

If i may abuse you a little more, which regex we would use to "capture" the last last word.
So we can get CD (this media can be different) from Path: D:\Music\Pop\Adele\Adele_Live-1980-CD\

Thanks boroda
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 09, 2014, 05:30:35 PM
Search for
Code
.*\\(.*)\\.*\..*
replace with
Code
$1
Title: Re: Additional Tagging and Reporting Tools
Post by: blau on April 09, 2014, 05:39:54 PM
Perhaps i'm doing something wrong but i have the same result.

This is what i did:
I have made a copy of the original preset in order to modify it, opened with "Rename/Edit", erased the old regex in the "search for" field and copypasted the new one from your post.
The result was the same, i think the regex you posted is the same as in the original preset.
Does this make sense?

Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 09, 2014, 06:07:39 PM
Sorry, I misunderstood you. Search for

.*\\.*-.*-(.*)\\.*\..*

replace with

$1

Hope this time I understood you correctly :)
Title: Re: Additional Tagging and Reporting Tools
Post by: blau on April 09, 2014, 06:15:22 PM
Perfect!!!

Thank you very much boroda   :D
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 12, 2014, 12:12:02 PM


http://www.mediafire.com/download/9ctqn5pgb8nr0ui/mb_TagTools_2014-04-14.zip

You need MB 2.4 latest patch to use new plugin version:

http://musicbee.niblseed.com/V2_4/MusicBee_Exe_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 12, 2014, 12:57:23 PM
Thanks for the improvement! It took more than a year since I asked for the fix, but I'm really glad I can now type any characters and copy and paste parts of regex freely.

I think it should suppress MB's hotkeys while the plugin's pane is active. For instance, I have assigned space key for play/pause. If I use the key while editing something on the pane, the selected track starts to play. It doesn't make sense since I can't even see what track is selected. Ctrl-C and V also function as MB's default hotkeys for copy and paste tags. It would be great if this can be fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 02, 2014, 12:13:25 AM
Hi Boroda, long(ish) time, no bug report from me.

When the plugin is activated in MB, and a second monitor is connected (or disconnected) from the computer while MB is open, MB freezes and has to be manually closed by killing the process in Task Manager. This doesn't happen when the plugin is disabled. Haven't been able to test whether it happens if there isn't an auto-report enabled (my auto-report is always enabled and I don't have much time for bug-tracing currently).

Also, a minor one. If an auto-report is cancelled using the cross which appears in the status bar, you can't then access the auto-report menu as the message "Background auto-report is still running!" pops up.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on May 02, 2014, 06:10:34 AM
Haven't been able to test whether it happens if there isn't an auto-report enabled

I don't have auto-anything enabled, and it happens for me, too.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 04, 2014, 09:24:59 AM
When the plugin is activated in MB, and a second monitor is connected (or disconnected) from the computer while MB is open, MB freezes and has to be manually closed by killing the process in Task Manager. This doesn't happen when the plugin is disabled. Haven't been able to test whether it happens if there isn't an auto-report enabled (my auto-report is always enabled and I don't have much time for bug-tracing currently).
I think I need Steven's help to resove this, but I'm not sure if he has enough time/willing to help me fix it ((

Also, a minor one. If an auto-report is cancelled using the cross which appears in the status bar, you can't then access the auto-report menu as the message "Background auto-report is still running!" pops up.
Thanks for this bug report. I'll fix this.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on May 04, 2014, 09:42:03 AM
I think I need Steven's help to resove this, but I'm not sure if he has enough time/willing to help me fix it ((
not now but maybe in a couple of weeks - although it seems bizzare the plugin or musicbee would react this way. Perhaps you could debug what the plugin is doing at the time so it helps identify what MB is doing?
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 04, 2014, 12:41:17 PM
When the plugin is activated in MB, and a second monitor is connected (or disconnected) from the computer while MB is open, MB freezes and has to be manually closed by killing the process in Task Manager. This doesn't happen when the plugin is disabled. Haven't been able to test whether it happens if there isn't an auto-report enabled (my auto-report is always enabled and I don't have much time for bug-tracing currently).
I think I need Steven's help to resolve this, but I'm not sure if he has enough time/willing to help me fix it ((

That's fine boroda. There's an easy work around at the moment anyway, so take as long as you need. Thanks for looking into it and the other report!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 04, 2014, 06:56:37 PM
If an auto-report is cancelled using the cross which appears in the status bar, you can't then access the auto-report menu as the message "Background auto-report is still running!" pops up.
Please try this version:
http://www.mediafire.com/download/1ou85ombhcbkllm/mb_TagTools_2014-05-04.zip

Also please let me know if bug is fixed now.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 04, 2014, 11:23:00 PM
Nope, sorry boroda. Neither bug is fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 05, 2014, 03:53:06 PM
@Pingaware
Check presence of both bugs in this version:
http://www.mediafire.com/download/85v8xgd9v8ldvbf/mb_TagTools_2014-05-05.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 05, 2014, 05:05:23 PM
Getting there! The auto-report not finishing properly is fixed now, so thanks very much for that.  :) Other one is still reproducible though. Something to note, though I don't know if this is due to the bug or not - when the second screen is connected or disconnected, MB does a visible slight resizing where the very edges of the screen below can be seen when MB is full-screened. MB also can't just be killed by ending the task in Task Manager. It ends fine, but you then have to go and kill the process as well and you can't reload MB until you have.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 08, 2014, 12:33:15 AM
I've got another question/bug report. Where does the number of files used in the status bar come from? My auto-report always says 4333 files, but that's not the number of files that fulfil the conditions (for the record, currently 5085). It's not in anyway a problem, as all the correct files get modified appropriately, it's just slightly strange for the number never to change.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 08, 2014, 06:34:05 AM
Its actually showing the number of processed rows in preview table, not the number of files. I've added this statusbar text only to animate the progress. I've changed this to show the percentage for the next update.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on May 14, 2014, 02:23:30 PM
G'day, boroda74  :)

Just wondering if you can improve the "Use skin colors" view.
I believe the API is limited in getting the colors from MB, but I've worked out you get the background from
Code
<element id="InputPanel.Default" bg="x,x,x" />

but the foreground comes from
Code
<element id="Controls.InputControl.Default" fg="x,x,x" />

With some skins, these elements are very similar.

Can the bg and fg come from the same item, like the do in TheatreMode?

It's probably not a big deal, as I don't think most users change their MB skins as often as I do  ;)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2014, 03:56:57 PM
I've made the change you requested:
http://www.mediafire.com/download/pj21kskdukd52cl/mb_TagTools_2014-05-14.zip

but as far as I remember it looks worse than previous version. Could you try new version with different skins and say me if it looks appropriate?
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on May 14, 2014, 04:00:34 PM
<removed>
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2014, 04:11:10 PM
@scampbll
This is very old post and there was no such command at the time of posting
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on May 14, 2014, 04:24:05 PM
Oh, oops! I must have ended up on some page other than the last one without realizing it.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on May 14, 2014, 11:27:09 PM
Could you try new version with different skins and say me if it looks appropriate?

Thanks for the quick update  :)
new colors work great with light / neutral skins but with dark skins.... not so good.

(http://i.cubeupload.com/EFKUUo.jpg)

zone 1 is fine, but zone 2, where the shadow / overlay is happening, it's not as clear.

on my Bee78 skin, the text even turns greenish  ???

(http://i.cubeupload.com/ddfxAS.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 15, 2014, 04:55:15 AM
Which version would you prefer?
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on May 15, 2014, 05:53:01 AM
The new one.
I think it's better to be able to clearly see the ASR presets in the top pane, then the headings in the next section.
While they are still legible, with some skins and the older version, the presets were virtually impossible to see.
Thanks very much for doing this.  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on May 27, 2014, 11:04:39 PM
Hi boroda. Two things.

First, was anything done about the dual screen bug I reported earlier? It's not a major problem, I just wanted to know.

And secondly, another bug report. (Sorry I keep finding them!) With the plugin activated, if you go to the mini player and then choose to dock the mini player at the top or bottom of the screen, MB freezes and needs to be closed using Task Manager (although it says it's still running and the Now Playing List is preserved, so it seems like it's just the GUI which is jamming up). This doesn't happen with the plugin disabled. See a little more info here (http://getmusicbee.com/forum/index.php?topic=12924.msg77943#msg77943).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 28, 2014, 07:10:48 AM
@Pingaware
Steven probably already hates me, but I again need his help. I don't know why my plugin causes permanent problems with UI freezing. What' special with it ?)))

@Steven
If you are reading this - uploaded sources and binaries are the latest ones. I'm ready to answer any question.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on May 28, 2014, 10:29:44 PM
i cant reproduce any problems as described. I would only expect MB to potentially be the source of the issue if doing this action were to result in an API call being made but i really doubt that would be the case. My only suggestion is to put in some logging to help narrow down where its freezing and if it turns it is because MB is freezing in an API call then i can look into it further
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on June 01, 2014, 04:58:24 PM
Realised I never thanked you for implementing the % in the status bar. Cheers very much for that boroda!

Regarding the bug I reported, I can provide my settings files if needed. Just say the word.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 02, 2014, 01:06:48 AM
@Steven and Pingaware
I wasn't at home for a few days, now I'm going to look at these 2 issues with freezing UI.

@Pingaware
Yes. PM me or post your settings (TagTools.Settings.xml from AppData). Also as far as I understand you don't use ASR, please confirm it.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on June 02, 2014, 03:07:40 AM
I use the auto-reports and ASR. However, I apply all the ASR presets manually (i.e. none of them are auto-applied).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 02, 2014, 06:11:14 AM
However, all I apply all the ASR presets manually (i.e. none of them are auto-applied).
Thats what wanted to hear.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 03, 2014, 08:56:53 AM
@Pingaware

This has the fix of bug with docked mini-player:
http://www.mediafire.com/download/hyq2wabn25l2q0m/mb_TagTools_2014-06-03-2.zip

Can't check if 1st bug reported by you is fixed now because I don't have 2 monitors.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on June 03, 2014, 12:30:16 PM
Fantastic boroda! Both bugs are now fixed! Thanks so much for all your hard work on squashing them.  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on June 08, 2014, 12:01:45 AM
FYI, the "Move everything after..." preset has $1 and $2 backwards (or maybe Tag 1 and Tag 2, not sure which is more accurate)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 12, 2014, 03:46:49 AM
When running Track Previewer plugin in any view, MB flickers whenever playing track changes. Also the status bar says "ASR preset is auto applied", but there's no reason any preset should be applied.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 13, 2014, 10:23:31 AM
When listening to tracks in artwork view, sometimes MB flickers with the status bar saying "ASR preset is auto applied". The file modification date got updated with it. But if I compare the two files (before and after), there's no differences in content. So it updates file modification date only with no reason.
Title: Re: Additional Tagging and Reporting Tools
Post by: elefantino on June 17, 2014, 02:43:40 PM
Realy nice Plugin, but when I make an report with title no. greater then 10, the list start with 10 not with 1 !!!
Is it possible to chance the layout from the htm export?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2014, 02:55:15 PM
@redwing
I've made a guesswork, try this version:
http://www.mediafire.com/download/33mb5u0e1mm55sm/mb_TagTools_2014-06-18.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2014, 02:57:16 PM
@elefantino
Plugin sorts fields as numbers only if field value can be converted to number. I would recommend to add sorting column(s) (disk #, track #, etc.) before 'Title column'.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 18, 2014, 03:08:49 PM
@redwing
I've made a guesswork, try this version:
http://www.mediafire.com/download/33mb5u0e1mm55sm/mb_TagTools_2014-06-18.zip

Thanks, but it still updates file modification date of playing tracks with the same message "ASR preset is auto applied" on the status bar when enabling Track Preview mode.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2014, 03:14:23 PM
The only reason for this I can see is that Track Preview plugin updates play counts and ASR is responding to this. In this case I could only disable ASR for play count changes.

Also is flickering gone now?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 18, 2014, 03:27:23 PM
No, it's not about play count. The value remains the same after playing just a portion of a track.

I just tested each of those presets with others disabled. And it narrowed down to two Soundcheck conversion presets: mp3 and m4a track gain to soundcheck presets. With other presets auto-applied, it's working fine. As for the flickering, it continues when the message shows up.  
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2014, 05:06:00 AM
Some tag should be changed to invoke ASR. If its not play count then it may be *skip* count.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 19, 2014, 09:56:41 AM
OK, I'll ask Steven to address skip count issue. But still I don't understand the following:

- Even if play/skip count changes, it only updates MB database file, not music files. Then why does ASR plugin update the files' modification date when there's no changes in files?
- Why only soundcheck conversion presets do that? Any other auto-applied presets don't respond to the skip count changes.  
- For a long time I have played lots of songs with many presets auto-applied. But the changes in play count of those tracks never updated modification date of music files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2014, 11:19:22 AM
I don't know. ASR updates tags using standard api functions and cant enforce changing file modification dates. Also all presets are equivalent in responding to the same tag changes.  Its a mystery for me.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on June 19, 2014, 07:37:18 PM
these are the fields that dont update the actual file:
PlayCount, SkipCount, LastPlayed, RatingLoveBan, FilePersistentId and any custom tags configured to save to the MB cache

If needed i can give you a debug version that says which fields are being updated, but as a guess from what redwing said, wouldnt it be updating the comment with a soundcheck value, perhaps when not needed?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2014, 08:27:10 PM
redwing, please send me all your asr presets from 'AppData\ASR Presets'.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 19, 2014, 09:04:11 PM
As I said only mp3 & m4a track gain to soundcheck conversion presets matter. You should be able to reproduce it with those two.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 19, 2014, 09:10:32 PM
Hmm, and SoundCheck custom tag is stored in database only? Or is mapped to 'COMM/iTunNORM'?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 19, 2014, 09:15:30 PM
Of course it's mapped to COMM/iTunNORM field through an auto-playlist. Basically they are configured the same as the guide I wrote: http://getmusicbee.com/forum/index.php?topic=9600.0
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 20, 2014, 09:40:07 AM
I really wish you could fix this bug before Steven updates Track Previewer plugin. As you may remember, this is an old issue that made me stop using your iPod & iPhone plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 10:52:14 AM
@redwing
I can't reproduce the issue. Please run debug version of plugin:
http://www.mediafire.com/download/1sw49c31rd26yws/mb_TagTools.dll

Post a links to files AppData\TtErrorLog1.txt and AppData\TtErrorLog2.txt
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 21, 2014, 11:09:54 AM
Just PMed you. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 12:06:20 PM
Try this version:
http://www.mediafire.com/download/5eblt8vc64jcyno/mb_TagTools_2014-06-21.zip

Don't forget to import asr presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 21, 2014, 12:18:10 PM
The new presets write SoundCheck values like "\@rg2sc4mp3(-7.2 dB)". Is this correct?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 12:21:30 PM
No. Min.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 12:30:08 PM
http://www.mediafire.com/download/u70mf8hlukc64dl/mb_TagTools_2014-06-21.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 21, 2014, 12:37:26 PM
The new presets still update file modification date responding to skip count changes.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 12:53:53 PM
This?
http://www.mediafire.com/download/c6fq3vtwf8j1cqb/mb_TagTools_2014-06-21.zip

Notice that both plugin dll AND asr presets are modified. Also combined track/album presets will modify files anyway (unfortunately).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 21, 2014, 01:05:35 PM
No differences. And I only use track gain conversion presets.

One thing I noticed is that they don't update tracks played at least once with these new presets. So do I need to rewrite SoundCheck values for all my tracks?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 21, 2014, 01:14:20 PM
Again they write SoundCheck values like "\@rg2sc4mp3(-7.2 dB)".
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 01:15:23 PM
Yes. But subsequent applying of preset shouldn't modify files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 01:16:05 PM
Again they write SoundCheck values like "\@rg2sc4mp3(-7.2 dB)".
Do you use new plugin dll?

edit: I'm a fool. Will correct it soon.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2014, 01:49:23 PM
This version should work:
http://www.mediafire.com/download/8dtj5fnfhmuzqc3/mb_TagTools.dll
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 21, 2014, 02:23:13 PM
Working great so far. I'll report back if that happens again. Thanks for the fix!
Title: Re: Additional Tagging and Reporting Tools
Post by: so_la_la on July 10, 2014, 10:33:40 PM
Hi
I have tags called USERCUSTOM1 in .ogg-files and CUSTOM! in .wma-files. Is there a way to have them displayed in the dialogue pane of this great plugin. There seems to be a limited number only of displayed tags when you want to copy or swap tags...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 11, 2014, 09:43:35 AM
Yes, you should map USERCUSTOM1 and CUSTOM! to MB UI. Go to edit > preferences > Tags (1) > define new tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: so_la_la on July 11, 2014, 01:29:43 PM
Thanks for the answer. I just had the appropriate fields make appear in the mapping section, they were all set to the Mp3-syntax. Now it is doing some massive rescanning.
Well, this issue led me into carrying out some inquiries into the tag and tagging alchemy. How fascinating what kind of different tags I have and what a mess it all is despite my continuing effort to sort it out. But the tag inspector and mp3tag have been quite a revelation. So many tags i didn't even know that existed...
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on July 11, 2014, 05:47:20 PM
Well, this issue led me into carrying out some inquiries into the tag and tagging alchemy. How fascinating what kind of different tags I have and what a mess it all is despite my continuing effort to sort it out. But the tag inspector and mp3tag have been quite a revelation. So many tags i didn't even know that existed...

This is why I use Picard and have it clear all the previous tags when I update a file.  :) 
Title: Re: Additional Tagging and Reporting Tools
Post by: so_la_la on July 11, 2014, 06:52:39 PM
Thanks for the answer. I just had the appropriate fields make appear in the mapping section, they were all set to the Mp3-syntax. Now it is doing some massive rescanning.

Well, as a matter of fact I think it rescanned my whole library and gave me this mistake after several hours:

MusicBee v2.4.5269.30921 (Win6.2), 11 Jul 2014 19:49:

System.ObjectDisposedException: Auf das verworfene Objekt kann nicht zugegriffen werden.
Objektname: "#=qZcOoNq1DImCHhjWS4wILwg==".
   bei System.Windows.Forms.Control.CreateHandle()
   bei System.Windows.Forms.ListView.CreateHandle()
   bei System.Windows.Forms.Control.get_Handle()
   bei #=qq1CSXB9XcKvGpSEk$$FvZHF9vT4jzHeeLkxN51zhNTE=.#=qjUul2rXffhiJyXNsWkYfUBC7SnFbiOIQSflvjOKCwOM=(Control #=qpjCGJ0KVhm7LTwjMUXePuQ==)
   bei #=qXHs8DrqylTrO5DFcIp8SJpiCIP8I5vodPfGiuYmLbT6Lqc2AQ_bLXv7zjiD5FK_I.#=qXqBR0Es1XLl6yApfKPXNuJsQmdLFDA$GCb99MfRF4qM=()
   bei #=qrBrSPhqcgPCVwICmqlF859Z_oHyjuHie1Qrvl13$tXAMkK05d_NsTFNLk$o5yjaV.#=qTgnrl14xw62I76lvI$Y4Ew==(Int32 #=q0WaB1P1E4jlTNNA_ug5h3g==, Int32 #=qqaLbKISX7XlpQZAyehFEEg==)
   bei #=qrBrSPhqcgPCVwICmqlF859Z_oHyjuHie1Qrvl13$tXAMkK05d_NsTFNLk$o5yjaV.#=q4NmnxNOsyq2DqcUca_JgCg==(Int32 #=qy4Jxf9_YaokRnhBGbRF9uA==)
   bei #=q31hb2ndEbcfTut1kIWWGJUarcFBzV42_HvsaIYiLB44=.#=q7rSkvjCt9QPyf4FL9dWQJeInjxu$9dr4nI826OFKXss=(#=qbSU12pVww9e0YOyjAZeuSA== #=qmT0hvBDBB31JYNPqpnNU3w==, Boolean #=qfn43u7jEOA6ozQ1ddACMZHBDC8Q8prZoJk$aCk30BRU=)
   bei #=q7zOaljZ$XUmBStoexi1xEmnHSfVJfpgaNCPYOQcan2I=.#=qbSU12pVww9e0YOyjAZeuSA==.#=qIMMDzOq68lKN5fI4NH7pSNJqSmrjD0l1wnbpza5dF28=()

I don't know what it means but anyway here is the mistake.
Title: Re: Additional Tagging and Reporting Tools
Post by: so_la_la on July 11, 2014, 07:05:13 PM
This is why I use Picard and have it clear all the previous tags when I update a file.  :) 

Are the mood, keywords and occasion tags in Picard taken from Last.fm as well? In this case then it would be identical to MusicBee... How do you set up these things, have you created some kind of white list. And can you recommend populating these three tags in one massive update?

Picard looks interesting but I just can't afford to get into yet another programme (besides MusicBee, MP3Tag, EAC and MusicIPMixer).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 12, 2014, 10:19:30 AM
Thanks for the answer. I just had the appropriate fields make appear in the mapping section, they were all set to the Mp3-syntax. Now it is doing some massive rescanning.

Well, as a matter of fact I think it rescanned my whole library and gave me this mistake after several hours:

MusicBee v2.4.5269.30921 (Win6.2), 11 Jul 2014 19:49:

System.ObjectDisposedException: Auf das verworfene Objekt kann nicht zugegriffen werden.
Objektname: "#=qZcOoNq1DImCHhjWS4wILwg==".
   bei System.Windows.Forms.Control.CreateHandle()
   bei System.Windows.Forms.ListView.CreateHandle()
   bei System.Windows.Forms.Control.get_Handle()
   bei #=qq1CSXB9XcKvGpSEk$$FvZHF9vT4jzHeeLkxN51zhNTE=.#=qjUul2rXffhiJyXNsWkYfUBC7SnFbiOIQSflvjOKCwOM=(Control #=qpjCGJ0KVhm7LTwjMUXePuQ==)
   bei #=qXHs8DrqylTrO5DFcIp8SJpiCIP8I5vodPfGiuYmLbT6Lqc2AQ_bLXv7zjiD5FK_I.#=qXqBR0Es1XLl6yApfKPXNuJsQmdLFDA$GCb99MfRF4qM=()
   bei #=qrBrSPhqcgPCVwICmqlF859Z_oHyjuHie1Qrvl13$tXAMkK05d_NsTFNLk$o5yjaV.#=qTgnrl14xw62I76lvI$Y4Ew==(Int32 #=q0WaB1P1E4jlTNNA_ug5h3g==, Int32 #=qqaLbKISX7XlpQZAyehFEEg==)
   bei #=qrBrSPhqcgPCVwICmqlF859Z_oHyjuHie1Qrvl13$tXAMkK05d_NsTFNLk$o5yjaV.#=q4NmnxNOsyq2DqcUca_JgCg==(Int32 #=qy4Jxf9_YaokRnhBGbRF9uA==)
   bei #=q31hb2ndEbcfTut1kIWWGJUarcFBzV42_HvsaIYiLB44=.#=q7rSkvjCt9QPyf4FL9dWQJeInjxu$9dr4nI826OFKXss=(#=qbSU12pVww9e0YOyjAZeuSA== #=qmT0hvBDBB31JYNPqpnNU3w==, Boolean #=qfn43u7jEOA6ozQ1ddACMZHBDC8Q8prZoJk$aCk30BRU=)
   bei #=q7zOaljZ$XUmBStoexi1xEmnHSfVJfpgaNCPYOQcan2I=.#=qbSU12pVww9e0YOyjAZeuSA==.#=qIMMDzOq68lKN5fI4NH7pSNJqSmrjD0l1wnbpza5dF28=()

I don't know what it means but anyway here is the mistake.
This is not a plugin error, report it on 'bug reports' board of the forum.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on July 20, 2014, 06:48:50 AM
Can you add the ability to edit Artist: Performer, Artist: Guest, etc tags?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 20, 2014, 08:11:45 AM
These tags are read-only. However there are possible workarounds for ASR. What do you mean exactly by "ability to edit"?
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on July 20, 2014, 02:35:57 PM
These tags are read-only. However there are possible workarounds for ASR. What do you mean exactly by "ability to edit"?

Currently, I want to copy performer to guest artist.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 21, 2014, 09:52:47 AM
Create new ASR preset, search for
Code
(^|\x00)\x02([^\x00]*)
in Artist tag and replace with
Code
$1\@char(1)$2
in Artist tag
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 04, 2014, 07:08:19 PM
Copied this from my bug report thread as Steven says it's yours to solve (lucky you :P ).

"I was generating the preview for a library report using boroda74's plugin, a song was playing as part of the queue in the now playing list (which may just have been about to load a playlist mixer) and I got the below bug report. The report was at 90%. When I then copied the error and hit OK, MB closed. The report was resizing the artwork to 300x300 pixels and was using a virtual tag. EDIT - Same again when not resizing artwork. Got to 38% this time."

MusicBee v2.4.5328.30888 (Win6.1), 4 Aug 2014 14:53:

System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
   at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
   at System.Drawing.Image.Save(MemoryStream stream)
   at System.Drawing.ImageConverter.ConvertTo(ITypeDescriptorContext context, CultureInfo culture, Object value, Type destinationType)
   at System.ComponentModel.TypeConverter.ConvertTo(Object value, Type destinationType)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

MusicBee v2.4.5328.30888 (Win6.1), 4 Aug 2014 15:47:

System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
   at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
   at System.Drawing.Image.Save(MemoryStream stream)
   at System.Drawing.ImageConverter.ConvertTo(ITypeDescriptorContext context, CultureInfo culture, Object value, Type destinationType)
   at System.ComponentModel.TypeConverter.ConvertTo(Object value, Type destinationType)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()


Exact report was Album Artist (Displayed), Album, Artwork, Release Type (a custom tag), Track Count, Album Track Count (a virtual tag which just allows the plugin to access the Album Track Count field generated by MB).

I did a retry of the report and it fails at the same two places (dependent on artwork resizing) each time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 06, 2014, 06:22:43 AM
Try this version
http://www.mediafire.com/download/9o6b0re869b234b/mb_TagTools.dll
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 06, 2014, 11:51:30 AM
Sorry boroda, got what I assume is the same report again -

MusicBee v2.4.5330.22939 (Win6.1), 6 Aug 2014 11:47:

System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
   at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
   at System.Drawing.Image.Save(MemoryStream stream)
   at System.Drawing.ImageConverter.ConvertTo(ITypeDescriptorContext context, CultureInfo culture, Object value, Type destinationType)
   at System.ComponentModel.TypeConverter.ConvertTo(Object value, Type destinationType)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 07, 2014, 10:58:22 AM
And this?
http://www.mediafire.com/download/9o6b0re869b234b/mb_TagTools.dll
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 07, 2014, 02:09:00 PM
Sorry boroda! This is the error report from the one without artwork resizing:

MusicBee v2.4.5331.30657 (Win6.1), 7 Aug 2014 13:57:

System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
   at System.Drawing.Image.Save(Stream stream, ImageCodecInfo encoder, EncoderParameters encoderParams)
   at System.Drawing.Image.Save(MemoryStream stream)
   at System.Drawing.ImageConverter.ConvertTo(ITypeDescriptorContext context, CultureInfo culture, Object value, Type destinationType)
   at System.ComponentModel.TypeConverter.ConvertTo(Object value, Type destinationType)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

and with the artwork being resized:

MusicBee v2.4.5331.30657 (Win6.1), 7 Aug 2014 14:08:

System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart().

If it's any help, the reports are crashing slightly earlier now - 37% for the no resize and 94% for the one with resizing.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 09, 2014, 03:41:51 PM
One more attempt:
http://www.mediafire.com/download/va8j6zr4nfaqz7o/mb_TagTools.dll
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 09, 2014, 04:05:44 PM
Failure's changed place - it now occurs at 83% without resizing with this error:

MusicBee v2.4.5332.32253 (Win6.1), 9 Aug 2014 15:58:

System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   at System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height)
   at System.Drawing.Bitmap..ctor(Image original)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

and 95% with resizing producing this error:

MusicBee v2.4.5332.32253 (Win6.1), 9 Aug 2014 16:05:

System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Thanks for the effort you're putting into this boroda!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 09, 2014, 06:28:41 PM
http://www.mediafire.com/download/0jvahurvcc09ihh/mb_TagTools.dll
???
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 09, 2014, 10:22:22 PM
Same again by the looks of it. Without resizing:

MusicBee v2.4.5332.32253 (Win6.1), 9 Aug 2014 22:15:

System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   at System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height)
   at System.Drawing.Bitmap..ctor(Image original)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

and with resizing:

MusicBee v2.4.5332.32253 (Win6.1), 9 Aug 2014 22:21:

System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 14, 2014, 08:44:29 PM
Pingaware, sorry for delay, I was very busy at my work.

Try this version:
http://www.mediafire.com/download/eaoq0at7907l7ni/mb_TagTools.dll
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 14, 2014, 10:08:29 PM
Pingaware, sorry for delay, I was very busy at my work.

Oh don't ever worry about apologising for taking a while to post! I'm grateful enough as it is that you keep spending all this time trying to (and succeeding in) solving all the bugs I keep digging up for you. Thanks for the effort you always put in - I don't mind about a little wait.

Unfortunately still crashing - 82% without artwork resizing

MusicBee v2.4.5339.22204 (Win6.1), 14 Aug 2014 22:02:

System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   at System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height)
   at System.Drawing.Bitmap..ctor(Image original)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

and 95% with resizing:

MusicBee v2.4.5339.22204 (Win6.1), 14 Aug 2014 22:08:

System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   at MusicBeePlugin.LibraryReportsPlugin.previewTrackList()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 15, 2014, 07:57:42 AM
Hmm. Seems to be the same error. I should prepare a debug version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 15, 2014, 10:55:05 AM
@Pingaware
Create folder C:\Temp, install debug version:
http://www.mediafire.com/download/99qpe0ij991lkds/mb_TagTools.dll

, run LibraryReports and send me Log.txt from C:\Temp.

making report will be slower than usual. Its normal.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 24, 2014, 05:49:29 AM
Hey boroda74, you look busy lately. When you have time, would you have a look at this request?

With the current functionality, it's possible to copy & paste a single tag between multiple files (http://getmusicbee.com/forum/index.php?topic=13643.msg82206#msg82206). But no way for multiple tags.

So it would be great if the plugin could read and split clipboard data with a user-defined delimiter and then write each of them into multiple fields. For instance, the user enters "<Title>*<Artist>*<Album>" in the 'send to clipboard settings' box. Then runs copy tag command, and selects something like "<Clipboard-multiple>" for the source , "<Multiple>" for the target, and "*" for custom text. Then the plugin splits the data and writes each value in the corresponding field. What do you think?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 10:25:40 AM
... What do you think?
It would be very complicated for copy tag command, but probably I could do this for ASR. I'll look at this later.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 10:41:03 AM
Then would it be possible to select multiple tags from the preset instead of entering into the clipboard setting box?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 01:23:39 PM
Didn't understand. First try new version (see 'Paste tags from clipboard' preset):
http://www.mediafire.com/download/xtk27amjt45r265/mb_TagTools_2014-08-28.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 01:45:57 PM
It's working fine. But the workflow is too complicated. Could be useful in some special cases where some tags need to be switched, though.

How about creating another preset with the same look, but this time each source tag is the same as target tag? So this would be a multiple tag version of "TOY: Copy Tag" preset. No need to use clipboard setting. Just copies multiple tags of source files to the corresponding tag of target files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 01:48:44 PM
I cant imagine UI for this. Could you make a mockup?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 01:53:21 PM
But do you think this would work for ASR? They are not the same files. After selecting source files, the user then needs to select target files during the process.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 02:03:30 PM
Actually I don't think that process is too complicated now. Preset (and Tags(2) preferences) must be adjusted only once, then you can simply select destination files and click 'Proceed'.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 02:14:38 PM
You mean the paste tags preset? The complicating part is you need to arrange target tags correctly, each time you make an adjustment to clipboard template. Then can you add a setting that copies to the same tags as the source tags?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 02:17:58 PM
Yes, its possible, but it will require to co-adjust copy tags/paste tags presets anyway.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 02:21:03 PM
What do you mean? Why copy tags preset?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 02:27:59 PM
I see, do you mean "copy tags" command? That would work better.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 05:05:36 PM
I meant possible "copy tags to clipboard" preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 06:14:55 PM
Then would it work something like "select source files> copy to clipboard preset> select target files> paste tags preset"?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 28, 2014, 08:39:49 PM
http://www.mediafire.com/download/cdat25658rybkfj/mb_TagTools_2014-08-28-2.zip

see 'CLIPBOARD: Copy tags to clipboard' preset
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 28, 2014, 09:08:04 PM
Thanks, but 'CLIPBOARD: Copy tags to clipboard' preset doesn't work properly. Try with three tags. The third tag gets copied to the fourth, null tag.
Also it would be great if this preset too could show each value that will be copied to each tag in preview mode, just to make sure.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2014, 01:56:06 AM
Just some thought about this.

- Fix the copy to clipboard preset. That would be useful anyway as an alternative way of using clipboard setting box.

- But the problem is that still source tags and target tags are separated, and each of them needs to be rearranged manually. This is for copy and paste multiple tags between multiple files. Hence switching between tags would be rarely needed, and target tags can be safely the same as source tags in most cases. Then how to automate it? Can the plugin access and read the clipboard setting template? If that's possible, the plugin should be able to write down each value to the same tag as the source tag just with one click.

- Even if that's possible, still something's missing. In more cases, people want to copy and paste "all (including artwork) but one to two" tags between multiple files like all tags except title or all tags except artist & album artist. It's like when you press Ctrl-C to copy tags between multiple files, you want to exclude one or two tags. Probably the current ASR and copy tag command can't handle this, and a new command with its own UI will be needed. Or should this be added to wishlist for MB?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 29, 2014, 09:22:55 AM
I think I'll make 2 new commands for copying/pasting tags. Probably on this weekend.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2014, 10:37:11 AM
That'd be great!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 29, 2014, 03:56:10 PM
http://www.mediafire.com/download/5t1mf956enl53xf/mb_TagTools_2014-08-29.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2014, 04:27:57 PM
Excellent! Did some tests and it's working flawlessly so far.
Can you add artwork and lyrics field too?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 29, 2014, 04:38:39 PM
No. At the moment artworks and lyrics tags are read-only. May be Steven could make them writable.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2014, 04:53:28 PM
OK.

There are some problems with handling artist and album artist fields.
- It doesn't write multiple artists correctly. Only display artist are copied correctly with existing multiple artist values unchanged.
- It doesn't handle well when album artist/sort artist/sort album artist fields are empty as it just writes down artist value to sort artist and sort album artist field. Shouldn't it do so only when those fields have distinct values?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2014, 05:02:38 PM
Also, sub-artist fields (guest artist, performer, remixer) are copied to artist field instead of its own sub field.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2014, 06:23:31 PM
How about adding a setting that allows single to multiple copy & paste tags? The use case would be you got a whole album and want to copy "all but title" fields from a single track you already had and tagged completely to the rest of album.

Maybe, instead of adding the setting, it could pop up a confirmation dialog only for single to multiple cases.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 30, 2014, 02:32:37 AM
Another suggestion. Probably each user has his/her own tagging scheme, using only specific fields for all collection. Then separating ticked fields and unticked fields could ease managing the command like the following mockup:

(http://i.imgur.com/1xv3o5E.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 30, 2014, 09:15:41 AM
I'm sure you know this but just to make sure: composer/display composer fields have the same issue as artist field when it has multiple values, and sort composer field has the same issue as other sort- fields in that it fills with composer value when it's blank.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 30, 2014, 03:21:54 PM
All is fixed and done except for:

- It doesn't handle well when album artist/sort artist/sort album artist fields are empty as it just writes down artist value to sort artist and sort album artist field. Shouldn't it do so only when those fields have distinct values?
1. For Album Artist: its an MB bug, I've reported it to Steven ans is waiting for his answer.
2. For Sort Artist, Sort Album, etc.:  these tags are just custom tags and may be actually any of custom tags or may not exist at all. So I'm afraid I cant make special handling for them (though MB internally recognizes these tags and handles them in a special way).


http://www.mediafire.com/download/p5bzxxvxia6fckf/mb_TagTools_2014-08-30.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 30, 2014, 03:56:07 PM
Thanks, but I keep getting this error when trying to paste and it can't paste.

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at MusicBeePlugin.PasteTagsFromClipboardPlugin.pasteTagsFromClipboard()
   at MusicBeePlugin.PasteTagsFromClipboardPlugin.PasteTagsFromClipboardPlugin_Shown(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnShown(EventArgs e)
   at System.Windows.Forms.Form.CallShownEvent()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

Also can you make the two field lists always sorted alphabetically? Currently it does only when relaunched. I would prefer the two lists to be in a single window with one scroll bar like the previous version, but this is just personal opinion.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 30, 2014, 04:01:26 PM
2. For Sort Artist, Sort Album, etc.:  these tags are just custom tags and may be actually any of custom tags or may not exist at all. So I'm afraid I cant make special handling for them (though MB internally recognizes these tags and handles them in a special way).

If this issue can't be addressed, then consider disabling those fields as no one would want to have artist and album artist values copied to those sort fields.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 30, 2014, 05:13:22 PM
http://www.mediafire.com/download/t8lt496i6dht6qk/mb_TagTools_2014-08-30-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 30, 2014, 05:21:11 PM
1. For Album Artist: its an MB bug, I've reported it to Steven ans is waiting for his answer.
Actually it was a plugin bug and its fixed in the version above.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 30, 2014, 05:52:13 PM
Now it's working fine. I can confirm that album artist, multi-artist/composer, display artist/composer, sub-artist issues were all sorted out. And single to multiple cases are handled well. Great job!

Now some remaining issues:
- Often newly pasted files don't seem to have changed at all in their tag values, when seen from the main panel and tag editor. But if I rescan them, MB says it can't locate the files. After removing them, the pasted files show up correctly. This never happens with MB's internal Ctrl-C/Ctrl-V.
- If you can't fix the sorting issue for the two field lists, probably the previous version would work better. Currently it's really confusing to configure the setting because the fields are not sorted alphabetically, hiding somewhere in two windows.
- Would be nice if sort-fields could be handled properly just like MB's internal Ctrl-C/Ctrl-V.
- Would be nice if artwork and lyrics could be copied as well just like MB's internal Ctrl-C/Ctrl-V.

Anyway, thanks so much for implementing this useful tool! I'm sure people will appreciate this great addition.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 30, 2014, 06:22:44 PM
- Often newly pasted files don't seem to have changed at all in their tag values, when seen from the main panel and tag editor. But if I rescan them, MB says it can't locate the files. After removing them, the pasted files show up correctly. This never happens with MB's internal Ctrl-C/Ctrl-V.
Probably this was my fault. Try new version.
- If you can't fix the sorting issue for the two field lists, probably the previous version would work better. Currently it's really confusing to configure the setting because the fields are not sorted alphabetically, hiding somewhere in two windows.
Sorting is not a problem.

http://www.mediafire.com/download/1hug6d98n2f86t0/mb_TagTools_2014-08-30-4.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 30, 2014, 06:55:04 PM
Great! Sorting issue is now resolved. But the first one still happens. Try to paste to a just pasted file.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 31, 2014, 03:18:11 PM
It's great the current ASR pane is resizable, but the preset list pane and track list pane inside it are not. Now the pane lists more than 80 presets, but the preset list pane is too short to browse them adequately. The same goes for track list pane at the bottom. So how about making the two panes resizable inside the pane? Maybe "Description" pane can be shorter as it has three lines at longest.

Also it would be great if copy tags to clipboard pane is resizable.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 31, 2014, 09:19:15 PM
http://www.mediafire.com/download/4t23q67m7inr6la/mb_TagTools_2014-09-01.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 01, 2014, 06:05:27 AM
Thanks for the update!

- Now in most cases the tag values for the pasted files are immediately changed without having to rescan.
- But still it happens often with single to multiple cases. Rarely, entire tags are getting removed from target files.
- The pane is now resizable, but it doesn't remember the adjusted size, always returning to the default size when relaunched.
- How about taking one more step, enabling it to be listed in two columns when it has sufficient width? Then it could show entire fields without the scroll bars from the both lists.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 01, 2014, 08:37:18 AM
http://www.mediafire.com/download/n46dw1qj3dat6bc/mb_TagTools_2014-09-01-3.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 01, 2014, 09:03:30 AM
Excellent! Now it's handling tag update better than MB's internal Ctrl-C/Ctrl-V as the MB's updates not entire tags in real time. Also no more flickering.
And great improvement of the copy tags to clipboard pane. Only two glitches:
- When minimized, the top border of Copy and Close button gets removed.
- More width is needed for each column as some field names (display composer & sort album artist) are truncated
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 01, 2014, 09:40:44 AM
- When minimized, the top border of Copy and Close button gets removed.
Cant reproduce and didn't understand clearly what you are meaning. Screenshot could help.

- More width is needed for each column as some field names (display composer & sort album artist) are truncated
Yes, I know this, but its out of my control.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 01, 2014, 10:00:28 AM
I meant this:

(http://i.imgur.com/wlMXTxG.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 01, 2014, 10:05:59 AM
What do you minimize? MB itself?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 01, 2014, 10:08:59 AM
No, the pane to its shortest height.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 01, 2014, 10:30:34 AM
Still cant reproduce, but hope new version will be better.

http://www.mediafire.com/download/tihs7g9no777dsq/mb_TagTools_2014-09-01-6.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 01, 2014, 10:45:41 AM
Yes, it's fixed. Thanks!
And I noticed you fixed ASR pane too. Looks much better except this glitch:

(http://i.imgur.com/4qloXBD.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 01, 2014, 10:59:50 AM
http://www.mediafire.com/download/uds3tx9ou2nqu4h/mb_TagTools_2014-09-01-7.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 01, 2014, 11:21:21 AM
Yes, it's fixed. All seems to be sorted out for now. Thanks!
I'm gonna post a how-to guide about the new commands soon.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 01, 2014, 11:35:10 AM
I'm gonna post a how-to guide about the new commands soon.
Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 03, 2014, 07:46:46 PM
This version should work:
http://www.mediafire.com/download/8dtj5fnfhmuzqc3/mb_TagTools.dll

Looks like something went wrong since this version with regard to writing SoundCheck values.
iTunes no longer recognizes MB SoundCheck values for some m4a files, doing its own volume analysis while importing. Though mp3 files look fine so far I'm not 100% sure.
First suspected a possible field format change from iTunes, but after testing with my 6 month-old backup without any problem, it seems it's due to some changes made onto the way this plugin writes the field. Any ideas?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 03, 2014, 08:43:22 PM
For now, let's concentrate on <track gain m4a> preset as it's making most of the problem. I just tested with the old version of the preset (<modified>2013-05-04T10:02:09.6700279Z <guid>a6059a62-d1f4-4d6e-a609-c01593709553), overwriting SoundCheck values with it. iTunes does not recognize them either. So it's not just caused by the preset change but by the plugin change and possibly plus the preset change.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 03, 2014, 09:58:08 PM
OK, this is really interesting. The version released two month ago had a bug that prevents iTunes from recognizing SoundCheck values for some m4a files. But the latest version seems to work fine, which means the bug was fixed at some point during the last two months. So I'm in the middle of updating SoundCheck values with the latest version, and so far the values are correctly recognized by iTunes without its own volume analysis. I'll report back after a full test.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 03, 2014, 11:33:56 PM
I can confirm the latest version of this plugin and SoundCheck presets are working correctly so that iTunes has no problem recognizing MB SoundCheck values (no volume analysis on its own). I don't know what the bug was and when it was fixed, but I'd recommend other users who are using this feature to update your SoundCheck values with the latest plugin and presets. In doing so, you need empty SoundCheck values for all files first, and then apply the presets to update the values properly. Simply re-applying presets without emptying the tag first won't update files if the values are same. This could result in preventing some files' SoundCheck values from being recognized by iTunes.  
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 13, 2014, 08:28:37 AM
(http://i.imgur.com/0HXR6uv.png)

The number of "tags" should be "tracks" as they could be confusing now with multiple tags and tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 13, 2014, 11:22:44 AM
http://www.mediafire.com/download/x2swprd6vwhwpxs/mb_TagTools_2014-09-13.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 13, 2014, 11:27:42 AM
Yes, it's fixed. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on September 20, 2014, 10:33:39 AM
Just wanted to thank you for this plugin.
All the work you have done has enhanced it to the point I've not used Mp3tag for at least two months now.  :o
Kudos to you, boroda74.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 20, 2014, 06:54:48 PM
:)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 03, 2014, 11:07:28 AM
One of the old bugs came back. With ASR presets auto-applied, a play count update by playing a track updates the file's modification date. It doesn't seem to be confined to any specific presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on November 03, 2014, 06:33:02 PM
if its updating just the playcount then i see no reason for the file to be updated, and  nothing has been changed in this regard on the musicbee side.
It sounds to me like other fields are being updated.
@boroda74, if you dont think it is a plugin issue then i would need to know what fields are being updated - is that possible?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 11, 2014, 12:22:08 PM
As far as I understand from redwings post any field may be updated.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 27, 2014, 06:16:30 PM
New version released:


http://www.mediafire.com/download/73cuewyrc1p2xfu/mb_TagTools_2014-11-27.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 30, 2014, 06:04:48 PM
New version released:


http://www.mediafire.com/download/em1g6lbh5o6i8x2/mb_TagTools_2014-12-30.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: burns274 on January 08, 2015, 11:22:27 PM
Hi,
I'm trying to get this plugin working, but Musicbee always crashes, as long as it's in the plugin folder.
Musicbee 2.5.5469
mb_TagTool_2014-12-30

I'm running it on an maybe unusual System. WinXP SP2 in a VirtualBox on a Macbook.
Any advise on this? Tried is also with a fresh install of Musicbee, but that didn't help...

Without the plugin, everything works fine. Other plugins too.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 09, 2015, 03:14:30 PM
Unfortunately I cant test plugin on Macbook, could you provide more info about plugin crashes?
Title: Re: Additional Tagging and Reporting Tools
Post by: burns274 on January 09, 2015, 03:23:06 PM
Musicbee crashes immediately when I go to
->Edit/Preferences/Plugins
or
->Tools/Tagging Tools

probably when Musicbee is trying to load it.

I would need a debug Version of Musicbee or an error log, to see what is happening.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 10, 2015, 09:43:23 AM
Musicbee crashes immediately when I go to
->Edit/Preferences/Plugins
or
->Tools/Tagging Tools

probably when Musicbee is trying to load it.
No, plugin is started/invoked at MB startup/clicking on plugin menu item, not on opening all plugin prefs or just openening Tagging Tools menu. I'm not sure what could I log in this situation.

@burns274, could you post here text of error message?

@Steven, if you are reading this, could you please provide debug version of MB?
Title: Re: Additional Tagging and Reporting Tools
Post by: burns274 on January 10, 2015, 10:58:07 AM
No, plugin is started/invoked at MB startup/clicking on plugin menu item, not on opening all plugin prefs or just openening Tagging Tools menu. I'm not sure what could I log in this situation.
Ah, you are right. Now it's even crashing a few seconds after the Musicbee start,
without me doing a thing.

This is the header of the Microsoft error message that pops up.

problem signature
AppName: musicbee.exe      AppVer: 2.5.5469.14126     AppStamp:5497cdb8
ModName: clr.dll      ModVer: 4.0.30319.2045      ModStamp:53b5055f
fDebug: 0       Offset: 0017464b

I googled that clr.dll and it could be a problem with my .net framework installation.
I don't know if this is the case, since everything else works normally.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 10, 2015, 11:52:58 AM
Yes. clr.dll is common language runtime. Its a part of .net framework. Try reinstall .net first.
Title: Re: Additional Tagging and Reporting Tools
Post by: burns274 on January 10, 2015, 01:02:59 PM
Yes. clr.dll is common language runtime. Its a part of .net framework. Try reinstall .net first.

Now I got it working. My Net Framework obviously was the problem.
Sorry for bothering you with this.

great plugin. thank you!
Title: Re: Additional Tagging and Reporting Tools
Post by: daver88 on February 03, 2015, 03:48:37 AM
I don't have Reg Exp knowledge but am hoping someone could give me the Reg Exp code which would allow me to - " Add an ordinal number to the beginning of Title, increased by specified value" - This is mostly for Classical tagging.
eg : Original -
Preludios Americanos - Evocacion
Preludios Americanos - Scherzino
Preludios Americanos - Campo
Preludios Americanos - Ronda

New -
Preludios Americanos - 1. Evocacion
Preludios Americanos - 2. Scherzino
Preludios Americanos - 3. Campo
Preludios Americanos - 4. Ronda

Thanks - David
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2015, 08:30:12 AM
I don't have Reg Exp knowledge but am hoping someone could give me the Reg Exp code which would allow me to - " Add an ordinal number to the beginning of Title, increased by specified value" - This is mostly for Classical tagging.
eg : Original -
Preludios Americanos - Evocacion
Preludios Americanos - Scherzino
Preludios Americanos - Campo
Preludios Americanos - Ronda

New -
Preludios Americanos - 1. Evocacion
Preludios Americanos - 2. Scherzino
Preludios Americanos - 3. Campo
Preludios Americanos - 4. Ronda

Thanks - David

This tool won't work that way.

Here's a simple workaround using notepad++ & this plugin's Copy tags to clipboard & Paste tags from clipboard commands.

1. Create a text file with notepad like the following.

1.
2.
3.
...

2. Select files you want to edit title field and run "copy to clipboard" command. Tick title field only in the selection setting.

3. Paste it to a new blank text file. Then you will have a list of titles of those files. Now copy the counters you created at step #1 while pressing alt key. Then paste it to the beginning of the title or any place you want to insert. Note that they are inserted in column. Now you have a list of titles prepended with a counter.

4. Select all and copy them, return to MB and run "paste from clipboard" command. Now those files will have a counter at the beginning (or another place you chose) of title.
Title: Re: Additional Tagging and Reporting Tools
Post by: daver88 on February 03, 2015, 07:45:33 PM
Thanks Redwing - I've ben a long time user of MediaMonkey which had  a Reg Exp addon with 250 presets. the code for the function i was looking for was :
Find What = ^.*
Replace with = IIf(Len("$&") > 0, (lSongIndex + <Number Caption="Start numbers with"  Value="0">) & ". $&", "")
There was also a dialog:
----------------------------------------------------------------------------
@ Add ordinal number of current track to the begin of Title incre...   ,,
Start nunbers with: <value>
Description: If speci?ed value = 100, 6 (#) _Let ItBe (T?e) —> 106. Let ItBe (li?e) (ony if1'|t
Don't show this dialog anymore
--------------------------------------------------------------------
My example was not quite correct, should have been -
Original -
Evocacion
Scherzino
Campo
Ronda

New -
1. Evocacion
2. Scherzino
3. Campo
4. Ronda

I guess from your response RegExp works a bit differently with MB. In any case thanks again for the suggested workaround

David
Title: Re: Additional Tagging and Reporting Tools
Post by: daver88 on February 15, 2015, 07:23:10 AM
I'm using Advanced Search & Replace - (Preset "Split Tags to ......) for an album which has a number of split values for (Artist).
The original artist format is :
Bix Beiderbecke / Paul Whiteman & his Orchestra
Bix Beiderbecke / Frank Trumbauer & His Orchestra

i would like this to be:
Artist 1 = Bix Beiderbecke
Artist 2 = Paul Whiteman & his Orchestra
Artist 2 = Frank Trumbauer & His Orchestra

Cannot get this to work. Some help would be appreciated

David
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 15, 2015, 05:21:21 PM
I'm using Advanced Search & Replace - (Preset "Split Tags to ......) for an album which has a number of split values for (Artist).
The original artist format is :
Bix Beiderbecke / Paul Whiteman & his Orchestra
Bix Beiderbecke / Frank Trumbauer & His Orchestra

i would like this to be:
Artist 1 = Bix Beiderbecke
Artist 2 = Paul Whiteman & his Orchestra
Artist 2 = Frank Trumbauer & His Orchestra

Cannot get this to work. Some help would be appreciated

David

This is a two-step approach for that task:

1. Tools> Tagging Tools> Search & Replace (not Advanced...)

Search " / " from Artist field and Replace it with ";"
Then it will split them to two artist values.

2. Tools> Tagging Tools> Advanced Search & Replace

Find a preset named "Generate 'displayed artist'...."
Enter " / " in the <Custom text> setting.
Preview and Apply.

Then it will change ";" back to " / " in display artist field.
Title: Re: Additional Tagging and Reporting Tools
Post by: daver88 on February 15, 2015, 10:53:53 PM
Thanks redwing - exactly what i wanted.
I notice that if i edit the tags in Foobar using ";" as the split character MusicBee changes this to " / " then i have to go through the split process you described.
Given that MusicBee also uses ";" for splitting do you know why it changes it to " / "  ?

David
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 16, 2015, 10:07:02 AM
Thanks, redwing :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 16, 2015, 04:00:13 PM
I notice that if i edit the tags in Foobar using ";" as the split character MusicBee changes this to " / " then i have to go through the split process you described.
Given that MusicBee also uses ";" for splitting do you know why it changes it to " / "  ?

I can't replicate that by using foobar's native metadata editor. MB just displays ";" with multiple artist values.
Title: Re: Additional Tagging and Reporting Tools
Post by: daver88 on February 17, 2015, 04:51:06 AM
I was also using the native Foobar Properties editor & I can definitely replicate the problem i described. BTW in that case the Album Artist was Various.

I tested another album where Artist was split but Album Artist wasn't
eg
Artist = Ahmad Jamal; Yusef Lateef
Album Artist = Ahmad Jamal/Yusef Lateef

MB Split the Artist correctly but the Artist 'displayed name' was -  Ahmad Jamal / Yusef Lateef. Album Artist was correct (Ahmad Jamal/Yusef Lateef)
--------------------------------------
I also tested an album where both the Artist & Album Artist were split in Foobar
eg:
Artist = Ahmad Jamal; Yusef Lateef
Album Artist = Ahmad Jamal; Yusef Lateef

In MB, Artist was split correctly but Artist 'displayed name' was -  Ahmad Jamal / Yusef Lateef as in previous example.
The Album Artist = Ahmad Jamal; Yusef Lateef; Ahmad Jamal / Yusef Lateef

Something odd going on here!

As before, your help is much appreciated

David

Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 17, 2015, 08:50:06 AM
I tried m4a files before, and their tags were read and split the same as foobar.
This time tried mp3 files and found MB changing ";" into " /". Also MB failed to split artist values as it read it as "/".

Upon searching in the forum, it seems MB imports MediaMonkey multiple artist values the same way, changing "; " into " /" without splitting them. If this matters to you, you could post a wishlist item.
Title: Re: Additional Tagging and Reporting Tools
Post by: daver88 on February 18, 2015, 03:07:59 AM
I'll work on it a bit more before I submit a wish request. In the meantime it seems to work in Foobar & MB if i seperate the artists with a 'comma' & then split them using the MB editor. Foobar then reads the split values correctly.
Title: Re: Additional Tagging and Reporting Tools
Post by: Rambostyne on February 18, 2015, 07:57:06 AM
I keep getting the following error when I try to use the auto rate function.

Quote
MusicBee v2.5.5524.39432 (Win6.2), 18 Feb 2015 1:51:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AutoRatePlugin.InitializeComponent()
   at MusicBeePlugin.AutoRatePlugin..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.autoRateEventHandler(Object sender, EventArgs e)
   at #=qOQLu0JmgzQo$2ZdDrQQe12OrwXflzNjHEoSdrrSwLsPsSNmq$_gZyqD7qVQ4rQww.#=qFqKrvY1c320y93RWz_d7Pg==(Object #=qRzfhR_ZoP4ghNlUG9SvRag==, EventArgs #=qPphfixBs9dCqakgxrq5Oeg==)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: Arathon on February 18, 2015, 04:35:39 PM
Hi I have some tracks were in the title it is listed the featured artist and i want to add him to the artist field, my problem is a complete ignorance of the regex syntax and i noticed a can't modify the similar action meant for the displayed artist tag in order to put the input to title. Hope you can help me and thanks for the great plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: MJMike on February 28, 2015, 11:35:00 AM
Hi Boroda,

got flwg.error msg. when try 2 create library report of my db...

Got this error msg. when try to create library report:

MusicBee v2.5.5524.39432 (Win6.0), 27 feb 2015 15:34:

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.SplitInternal(Char[] separator, Int32 count, StringSplitOptions options)
   at MusicBeePlugin.LibraryReportsPlugin.prepareBackgroundPreview()
   at MusicBeePlugin.PluginWindowTemplate.clickOnPreviewButton(DataGridView previewList, PrepareOperation prepareOperation, ThreadStart operation, Button clickedButtonParam, Button closeButtonParam)
   at MusicBeePlugin.LibraryReportsPlugin.buttonPreview_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

i am using yr latest update fron dec.'14

help?

Mike
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 28, 2015, 12:33:23 PM
New version released:
  • Added support for wring 'Lyrics' tag (requires latest version of MusicBee 2.5, on 2.4 writing to 'Lyrics' tag will be ignored).


http://www.mediafire.com/download/73cuewyrc1p2xfu/mb_TagTools_2014-11-27.zip

This feature never worked. It copies but can't paste, saying the number of tags are different. Apparently it takes the line of lyrics as the number of tags.

New version released:
  • Added support for wring 'Artwork' tag (only primary artwork is written, requires latest version of MusicBee 2.5, on 2.4 writing to 'Artwork' tag will raise exception).


http://www.mediafire.com/download/em1g6lbh5o6i8x2/mb_TagTools_2014-12-30.zip

This works only when artwork field alone is selected. With any other fields, it doesn't work.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 06, 2015, 04:46:25 AM
I keep getting the following error when I try to use the auto rate function.

Quote
MusicBee v2.5.5524.39432 (Win6.2), 18 Feb 2015 1:51:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AutoRatePlugin.InitializeComponent()
   at MusicBeePlugin.AutoRatePlugin..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.autoRateEventHandler(Object sender, EventArgs e)
   at #=qOQLu0JmgzQo$2ZdDrQQe12OrwXflzNjHEoSdrrSwLsPsSNmq$_gZyqD7qVQ4rQww.#=qFqKrvY1c320y93RWz_d7Pg==(Object #=qRzfhR_ZoP4ghNlUG9SvRag==, EventArgs #=qPphfixBs9dCqakgxrq5Oeg==)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
it seems that your .net framework is corrupted. try to reinstall .net
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 06, 2015, 04:54:26 AM
... and i noticed a can't modify the similar action meant for the displayed artist tag in order to put the input to title.
you can copy preset and edit the copy
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 06, 2015, 04:55:19 AM
Hi Boroda,

got flwg.error msg. when try 2 create library report of my db...

Got this error msg. when try to create library report:

MusicBee v2.5.5524.39432 (Win6.0), 27 feb 2015 15:34:

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.SplitInternal(Char[] separator, Int32 count, StringSplitOptions options)
   at MusicBeePlugin.LibraryReportsPlugin.prepareBackgroundPreview()
   at MusicBeePlugin.PluginWindowTemplate.clickOnPreviewButton(DataGridView previewList, PrepareOperation prepareOperation, ThreadStart operation, Button clickedButtonParam, Button closeButtonParam)
   at MusicBeePlugin.LibraryReportsPlugin.buttonPreview_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

i am using yr latest update fron dec.'14

help?

Mike
seems that your library is too large
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 06, 2015, 04:56:03 AM
New version released:
  • Added support for wring 'Lyrics' tag (requires latest version of MusicBee 2.5, on 2.4 writing to 'Lyrics' tag will be ignored).


http://www.mediafire.com/download/73cuewyrc1p2xfu/mb_TagTools_2014-11-27.zip

This feature never worked. It copies but can't paste, saying the number of tags are different. Apparently it takes the line of lyrics as the number of tags.

New version released:
  • Added support for wring 'Artwork' tag (only primary artwork is written, requires latest version of MusicBee 2.5, on 2.4 writing to 'Artwork' tag will raise exception).


http://www.mediafire.com/download/em1g6lbh5o6i8x2/mb_TagTools_2014-12-30.zip

This works only when artwork field alone is selected. With any other fields, it doesn't work.
thanks redwing for reporting these 2 issues, i'll look at them
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 06, 2015, 05:40:40 AM
Regarding this:

One of the old bugs came back. With ASR presets auto-applied, a play count update by playing a track updates the file's modification date. It doesn't seem to be confined to any specific presets.

I have identified what preset causes the issue. It's mp3 track gain to soundcheck preset (m4a track gain preset is working fine). With that preset not auto-applied, playing a track doesn't change file modification date. Hope you can fix it again.
Title: Re: Additional Tagging and Reporting Tools
Post by: MJMike on March 07, 2015, 09:51:38 AM
Hi Boroda!

U r right, it is a large library, but Musicbee program has no problems at all processing it, editing, sorting..it all runs smooth.

So, how can I work with your plugin, to give me an overview of all my albums in the library? not in detail, just album, album artist, genre and grouping...something like that.

Is it possible for u to make your plugin work at large libraries? After all, it is one of THE features of Musicbee?

Tks.

Mike
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 08, 2015, 04:34:54 AM
@boroda74:

Regarding this request:

Hi I have some tracks were in the title it is listed the featured artist and i want to add him to the artist field, my problem is a complete ignorance of the regex syntax and i noticed a can't modify the similar action meant for the displayed artist tag in order to put the input to title. Hope you can help me and thanks for the great plugin.

it would be useful if there's a preset "Extract featuring artists from title and add to (Guest) Artist tag" just like the existing "Extract remixer..." preset. The usual format would look something like "FourFiveSeconds (feat. Kanye West & Paul McCartney)". For custom text, the user could enter "ft." or "feat." but the preset should treat a comma and "&" as a delimiter between multiple featuring artists.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 08, 2015, 10:18:05 AM
@boroda74

In the most recent ASR version some bug might have entered. Please check.
In the preset Add up to 2 leading zeros in track numbers I tried to change (example)
1 2 3 4 5 6 7 8 9 10 11 12 13 14
The result shown in the preview is correct (only added an extra zero from 1-9)
But the final result included:
010 011 012 013 014

In earlier versions this was not the case, I used the preset 100's of times.
Please inform when an update is available. Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 08, 2015, 11:05:22 AM
@boroda74

Since I use the new release of both MB and ASR the ASR performance is sooooo muuuuuuch sloooooower....
Often it takes 4 seconds per track update, so 50 tracks take more than 3 minutes.
Do others have this experience too?
Or should I change any setting?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 08, 2015, 11:09:28 AM
@boroda74

Would you please consider to add 2 more presets:
1. Remove # characters from the beginning/end of field x
2. Add text xxxxxxxxxx to the beginning/end of field y, separated by z
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 08, 2015, 01:37:03 PM
Since I use the new release of both MB and ASR the ASR performance is sooooo muuuuuuch sloooooower....
Often it takes 4 seconds per track update, so 50 tracks take more than 3 minutes.
i think this is because plugin now updates ui every 5 sec. instead of just at the end of operation. i dont want to change this behavior.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on March 08, 2015, 05:11:57 PM

[/quote]
i think this is because plugin now updates ui every 5 sec. instead of just at the end of operation. i dont want to change this behavior.
[/quote]

I am not sure if I understand the change. Why not change back if it slows down so much? Update of 1000 tracks = 4000 seconds = more than 1 hour...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 09, 2015, 11:05:40 AM
@boroda74

In the most recent ASR version some bug might have entered. Please check.
In the preset Add up to 2 leading zeros in track numbers I tried to change (example)
1 2 3 4 5 6 7 8 9 10 11 12 13 14
The result shown in the preview is correct (only added an extra zero from 1-9)
But the final result included:
010 011 012 013 014

In earlier versions this was not the case, I used the preset 100's of times.
Please inform when an update is available. Thanks.
cant confirm this. try to reimport all presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 09, 2015, 11:29:22 AM
New plugin version  released:


http://www.mediafire.com/download/a1rub2vt7btow9w/mb_TagTools_2015-03-09.zip

redwing, an issue with file timestamp is still unresolved, but i'm going to take a look at this.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 09, 2015, 12:46:27 PM
Thanks for the update!

- Copy/paste selected tags commands are now working great with lyrics & artwork fields. I'm going to update the guide about this feature.
- "Extract featuring artists from title..." preset is working fine, but what I meant by "(Guest) Artist" was that it could copy to either Guest Artist or Artist tag. Can you add one more preset that copies to Artist tag? A note to other users: this preset works fine for a single featuring artist as well, and if a track has more than two featuring artists, use the same "custom text 2"( a comma or &) between them in title field before running this preset to the track.
- As you said, mp3 replaygain preset issue remains unresolved.
- Now included presets are almost 90. How about adding a search box to the dialog so that people could easily locate presets they are looking for?
 
  
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 10, 2015, 06:35:51 AM
- "Extract featuring artists from title..." preset is working fine, but what I meant by "(Guest) Artist" was that it could copy to either Guest Artist or Artist tag. Can you add one more preset that copies to Artist tag?
its done

http://www.mediafire.com/download/7wq4fff8bkc0riv/mb_TagTools_2015-03-10.zip

- As you said, mp3 replaygain preset issue remains unresolved.
- Now included presets are almost 90. How about adding a search box to the dialog so that people could easily locate presets they are looking for?
still to do
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 10, 2015, 08:29:02 AM
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: nirolf on March 19, 2015, 04:35:37 PM
@boroda74

I'm having a problem with auto-rating. After I change some presets (see screenshot) it works OK (though the ratings don't change, only Custom9), but after I restart MB I get this error:

Quote
MusicBee v2.4.5404.16303 (Win6.1), 19 Mar 2015 17:34:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AutoRatePlugin.InitializeComponent()
   at MusicBeePlugin.AutoRatePlugin..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.autoRateEventHandler(Object sender, EventArgs e)
   at #=q9DbaPkf98Bwnsb8WzYcjp0RNJK2ABsR7K3qLJHpRAZU=.#=qZZJUsWw6tR8pvhvDIsy$2g==(ApplicationCommand #=q4OrOPUtIo9ZMXVwHmwTogw==, Object #=qKixOGksuZIqNarZ4TufoBw==)

(https://farm9.staticflickr.com/8604/16864264895_329c5fc1ac_c.jpg) (https://flic.kr/p/rGeLpR)

Could you please have a look?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2015, 08:53:41 AM
plugin cant create auto-rate class. looks like your .net is corrupted. try reinstall .net
Title: Re: Additional Tagging and Reporting Tools
Post by: nirolf on March 21, 2015, 12:32:57 PM
I have reintalled the framework and even tried on another computer, still the same. It seems to trigger when I check "Auto calculate thresholds on startup".

Quote
MusicBee v2.4.5404.16303 (Win6.1), 21 Mar 2015 13:28:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AutoRatePlugin.InitializeComponent()
   at MusicBeePlugin.AutoRatePlugin..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.autoRateEventHandler(Object sender, EventArgs e)
   at #=qkqD_24K_jqNNsY4ytXfL8gdU4AeJG50yEcwQQ82gVnW0tjNMKqAPXQTcHSTEGGUx.#=q_BllApB1jquyAgblsRWAGQ==(Object #=qHIgSGJS$_ycrUlpxd6kRrg==, EventArgs #=qdjAGRgNuykZe8nBxToZIxg==)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2015, 06:48:57 PM
yes, i can reproduce this. thanks for bug report.

http://www.mediafire.com/download/ece49y264z0ipz7/mb_TagTools_2015-03-21.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2015, 01:23:28 PM


http://www.mediafire.com/download/jgv1m6amb9dumzy/mb_TagTools_2015-03-22.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2015, 02:31:43 PM
Working good! But it doesn't allow to resize the window.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2015, 04:14:35 PM
my bad. will fix it soon

http://www.mediafire.com/download/x03bqbdob7afdv9/mb_TagTools_2015-03-22-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2015, 04:36:24 PM
Working great now. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 24, 2015, 09:13:14 PM
I've been spending a lot of time with this plugin over the past few days as I'm cleaning up some debris in my tags.  It's really a great tool, but unless I'm missing something, I can't figure out how to replace specific text in the middle of a tag.  For instance, I want to change all occurrences of "Feat." in the title or artist tag with "Ft."  Is there any way to accomplish this search and replace?  Needless to say, I can find and select the tracks that need the change, but I can't, with just a couple of clicks, change all of them at once.  Does a preset for this already exist?  

BTW, the search feature is a really nice added feature.

Thanks.

EDIT:  If this is a preset that you have to add, I request that it not be limited to "feat" but that it could be used to replace -any- text in the tag.  I just came across some tracks that had "Alt Take" and "Alternate Take."  I'd like to make them consistent - one way or the other.

EDIT 2:  Never mind.  I figured out that one can create one's own presets!!!  Very nice feature to this versatile plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 25, 2015, 10:34:32 AM
glad you sorted it out :)
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 26, 2015, 08:22:42 PM
Am I overlooking Episode Date (TDRL) in the Copy Tag fields, or can I ask for it to be added?  Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 30, 2015, 06:27:07 AM
@Steven, could you add to api podcast tags (eg episode date)?
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on May 10, 2015, 04:05:16 AM
Why do I get this when I export html from the Library report? Am I supposed to have some css stylesheet in the same directory?

Geoff

MusicBee v2.5.5524.39432 (Win6.1), 10 May 2015 12:33:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\Geoff\Desktop\Exported Track List.files\stylesheet.css'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode)
   at MusicBeePlugin.HtmlDocument.writeHeader()
   at MusicBeePlugin.LibraryReportsPlugin.exportTrackList()
   at MusicBeePlugin.LibraryReportsPlugin.buttonOK_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2015, 02:49:58 PM
css file will created automatically. error means that either 'C:\Users\Geoff\Desktop\' path doesn't exist or plugin cant create 'Exported Track List.files' folder for some reason. also you can try to export report as simple html table.
Title: Re: Additional Tagging and Reporting Tools
Post by: BeeBeeKing on May 12, 2015, 03:01:25 PM
simple html table report works ok. I've never been able to get the html report to work though.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 05, 2015, 06:23:32 PM
"Set tags" ASR preset is not working properly when asked to write "0" into a tag if some of the selected files already have "0" for the tag value. In that case, Preview shows the correct result, but Apply doesn't do anything to the files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 05, 2015, 08:18:11 PM
strange. will look into it. thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: sbt on July 25, 2015, 12:28:05 PM
Having problems with Auto Rate. A new, clean, install of the Plugin has no problems but as soon as I set up Auto Rate the player starts failing to update 'Last Played' and 'Play Count'. Its intermittent, only 1 in 5 tracks are updated correctly. Obviously this completely fscks the Auto Rate system.

Latest built of MusicBee and client.

I have tried to work out which settings trigger this but I'm at a loss.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 26, 2015, 04:09:40 PM
post screenshot of autorate command window
Title: Re: Additional Tagging and Reporting Tools
Post by: sbt on July 27, 2015, 10:54:08 AM

(http://i.imgur.com/Tcn77SW.png)

Have now determined that this seems linked to the 'Autorate songs if they are played' setting, which is turned off, for obvious reasons, in this screenshot.

With it turned OFF I get proper updating of Last Played plus Played and Skipped counts. With it turned ON I get unpredictable behaviour, with most updates of these missed.

PS: 'Autorate if played or skipped' would be a better behaviour, IMHO.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 01, 2015, 07:37:29 PM
@sbt, i cant reproduce described issue, auto-rate works fine for me with any settings. try to temporary disable all other plugins to see if there is some interference between them.
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on August 16, 2015, 01:18:45 PM
Hey boroda74,
In the settings panel I have set: Show commands in 'Tools/Tagging tools/Advanced' menu.
Yet I still find all the commands combined under the standard 'Tagging Tools', and not under a separate 'Advanced' tagging tools menu?

(MB portable 2.5.5699, plugin v.2015-03-22-2)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2015, 07:57:46 PM
hmm... it seems that predefined 'advanced' menu was moved from 'tools/tagging tools' to 'tools'. now i can't neither place plugin commands to 'Tools/Tagging tools/Advanced' nor to 'Tools/Advanced'. i could ask Steven to fix it, but want to know where do you want to place commands? to 'Tools/Tagging tools/Advanced' or to 'Tools/Advanced'?
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on August 16, 2015, 09:23:16 PM
Personally I feel it would be good to be able to see the difference between the default tagging tools, and the additional options that became available when your advanced plugin is installed.

Therefore I think I would prefer it like this, adding your 'Advanced Tagging Tools' below the default 'Tagging Tools':

(http://i.imgur.com/NkYFtLml.jpg) (http://i.imgur.com/NkYFtLm.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on August 17, 2015, 03:10:54 AM
Personally I feel it would be good to be able to see the difference between the default tagging tools, and the additional options that became available when your advanced plugin is installed.

Therefore I think I would prefer it like this, adding your 'Advanced Tagging Tools' below the default 'Tagging Tools':
Yes!!  +1
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 18, 2015, 07:12:18 PM
http://www.mediafire.com/download/ph89ybgpop1qst7/mb_TagTools_2015-08-18.zip

you need mb latest patch:
http://musicbee.niblseed.com/V2_5/MusicBee_Exe_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on August 18, 2015, 07:46:47 PM
Wow, that's great, and fast. Thnx!
Can I also order pizza?  ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on August 18, 2015, 08:23:28 PM
Thanks boroda74!!  Nicely done.
I'll take a pizza also, but help yourself to an adult beverage on me.
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on September 20, 2015, 07:48:50 PM
I assume this is not possible, but let's just ask to be sure:

Suppose I have an album (mp3), with all tags nicely filled in, including the performing musicians per track.
Now I acquire a lossless version of the exact same album, but with a better sound quality.

I there a way to copy all tags from all the tracks from the old mp3 album, to the tracks of the new flac version?
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on September 20, 2015, 10:28:27 PM
@ hiccup

You can use the Copy and Paste Tags to/from Clipboard functions to do this
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on September 20, 2015, 10:42:30 PM
You can use the Copy and Paste Tags to/from Clipboard functions to do this

Wow!
Unbelievable. I never assumed that function would be so sophisticated.

Thnx Bee-liever, thnx Boroda!
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on September 21, 2015, 01:32:56 AM
You can also use send to > replace.  Just beware that in either method, any tag not configured in MB (ie not displayed in the tag editor) will not be copied.
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on September 21, 2015, 08:54:26 AM
You can also use send to > replace.  Just beware that in either method, any tag not configured in MB (ie not displayed in the tag editor) will not be copied.

Thnx, I am going to try out that method too.
The advantage of the second part of your advice is that in that way you could use this feature to clean up tags that you are not aware of and don't care about.
Great.
Title: Re: Additional Tagging and Reporting Tools
Post by: moophat on January 06, 2016, 07:27:04 PM
I'm getting a lot of error on MB 2.5, seem like some object that this plugin need was removed?
MusicBee v2.5.5804.26036 (Win6.3), 7 Jan 2016 2:26:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ObjectDisposedException: Cannot access a disposed object.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on January 06, 2016, 08:05:30 PM
I'm getting a lot of error on MB 2.5, seem like some object that this plugin need was removed?
MusicBee v2.5.5804.26036 (Win6.3), 7 Jan 2016 2:26:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ObjectDisposedException: Cannot access a disposed object.
Make sure the file(s) you're trying to tag are not Read-Only.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 08, 2016, 08:59:57 PM
@moophat, what are you doing when you get this error?
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on January 22, 2016, 12:56:06 AM
Hmmm, a number of GUI elements with this plugin are non-responsive.  I unpacked the contents of the latest build <MB>\Plugins.  Even though I'm using MB as a standard user in Windows 7, I granted myself full access rights to the MusicBee directory and its subdirectories.

For example, the scroll bar in "Auto Library Reports" doesn't respond to any left click-and-hold, thus I cannot scroll through the tag fields.  The advance search and replace doesn't respond to any input.

EDIT: Nevermind.  NB: Uncheck "Use skin colors" under Appearance in its Settings menu.  Skin used: DarkRED Flat.
Title: Re: Additional Tagging and Reporting Tools
Post by: evil_mani-mani on February 14, 2016, 08:21:38 PM
@boroda74

In the most recent ASR version some bug might have entered. Please check.
In the preset Add up to 2 leading zeros in track numbers I tried to change (example)
1 2 3 4 5 6 7 8 9 10 11 12 13 14
The result shown in the preview is correct (only added an extra zero from 1-9)
But the final result included:
010 011 012 013 014

In earlier versions this was not the case, I used the preset 100's of times.
Please inform when an update is available. Thanks.

I'm still running into this issue with the latest version, is there any fix for this?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 18, 2016, 03:04:11 PM
i cant reproduce this and nothing was changed with this asr preset for ages. the only suggestion is that tags are NOT really 1 2 3 4 5 6 7 8 9 10 11 12 13 14, i mean that there may be some hidden special characters. try to reenter manually 12 or 13 (etc) for 1 track and check if something changed.
Title: Re: Additional Tagging and Reporting Tools
Post by: evil_mani-mani on February 19, 2016, 12:13:33 AM
Yeah, It's odd, so I had the 'Add two leading zeros...' preset enabled, and if I try to manually change a double digit track, say 12, the preset will automatically change it to 012. I don't currently have any other presets enabled. This also occurs if I use the 'Auto-tag by Album' option, tracks 1-9 will properly have the leading zero added, but 10+ will have a 3rd digit added (010, 011, etc.)

Also I tried applying the manual search and replace filter to a list of tracks that already had double digit track numbers (01 to 13), the preview shows that it wouldn't make any changes to the track numbers, but when I applied it, all the tracks gained an additional leading zero (001, 002, 003, .... 013). Cheers.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 20, 2016, 04:32:00 PM
@boroda74-

Are you able to make the ATRT plugin window persistent?  It always opens towards the upper left and I drag it do the right.  I'd like it to stay where I put it.  Or is this something Steven has to do?

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2016, 02:11:49 PM
all plugin command windows very long time remembers their sixes and positions (i've just checked this and all is working fine here). may be plugin setting file is read-only? also try to close plugin windows by clicking 'close' button (not 'X' button in window caption).
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 24, 2016, 02:57:50 PM
all plugin command windows very long time remembers their sixes and positions (i've just checked this and all is working fine here). may be plugin setting file is read-only? also try to close plugin windows by clicking 'close' button (not 'X' button in window caption).
I'm not finding that to be the case.  The DLL is not read-only and I click Save and Close to exit.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2016, 07:25:31 PM
no, not dll, 'mb_TagTools.Settings.xml' in AppData folder. have just rechecked this issue by clicking 'Save & Close' button (suggest that you mean asr window), for me all is fine. i could give you a debug version later, but first check read-only status of settings file.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 24, 2016, 07:58:48 PM
no, not dll, 'mb_TagTools.Settings.xml' in AppData folder. have just rechecked this issue by clicking 'Save & Close' button (suggest that you mean asr window), for me all is fine. i could give you a debug version later, but first check read-only status of settings file.
Sorry about that.  No, the .xml is not read-only either.

 I tried to post an animated GIF showing that Advanced Search & Replace always opens in the same place despite being dragged to another part of the MB window, but while the GIF got posted, it's not animated.  If you'd like to see it let me know and I'll PM you a link to it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 25, 2016, 05:03:42 AM
yes, pm me the gif.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 25, 2016, 12:56:32 PM
PM sent
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 25, 2016, 08:08:43 PM
i'll try to prepare a debug plugin version tomorrow. 1st step of debugging is very easy, but now its too late in moscow.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 25, 2016, 08:14:57 PM
i'll try to prepare a debug plugin version tomorrow. 1st step of debugging is very easy, but now its too late in moscow.
No hurry on my side.  Get to it when you have the time available.  And thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 26, 2016, 02:54:09 PM
i've made minor change in plugin, which may help or may not. also in debug version log dialogs will be popped up every time you open/close any plugin window. install debug version, open asr window, ignore log dialog this time. move asr window, then close asr window, write down 3 numbers from log dialog. open asr again, write down 3 numbers. repeat opening/moving/closing asr window again. post these numbers here if asr window doesn't remember its position.

http://www.mediafire.com/download/cddfse2fu218qad/mb_TagTools_2016-02-26.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 26, 2016, 03:13:39 PM
i've made minor change in plugin, which may help or may not.
It certainly did help.  The ASR window is now behaving as expected and staying in its assigned position.  :-)

Quote
also in debug version log dialogs will be popped up every time you open/close any plugin window. install debug version, open asr window, ignore log dialog this time. move asr window, then close asr window, write down 3 numbers from log dialog. open asr again, write down 3 numbers. repeat opening/moving/closing asr window again. post these numbers here if asr window doesn't remember its position.
The three numbers were the same when opening or closing multiple times.  991:231:768.  The only time the numbers differed was when I tried closing with the exit X (upper right corner) instead of the Save/Close button.  These were 616:403:768.  But even exiting that way the window position stayed persistent.

Thanks for taking care of this so quickly.  Will there be a non-debug version coming soon so I don't have to see the debug numbers any more?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 26, 2016, 04:58:35 PM
this is the same version as previous, but there is no log dialogs any more. its now new public release. i'll update download link on the wiki.

http://www.mediafire.com/download/c23hp2z92l94uop/mb_TagTools_2016-02-26-1.zip
 
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 26, 2016, 05:21:33 PM
Thank you kindly.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 26, 2016, 05:30:18 PM
@Steven, could you add to api podcast tags (eg episode date)?

Just thought I'd bump this, because I recall it happened at a time that Steven was up to his ears in something else...
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on March 30, 2016, 10:09:24 PM
The issue is explained here: http://getmusicbee.com/forum/index.php?topic=17949.0

TL; DR version: Editing tracks in MB automatically saves track# as #/total# whenever editing other fields despite my <track#> being only ## (leading zeroes for tracks 1-9).

The result of this behavior is seen in other players where the album now displays two different <track#> arrangements # or #/# (basically, non-edited and MB-edited tracks).  This gets even more annoying where <track#> for multi-CD albums are tagged in the following manner (first digit is the disc # and the latter two the disc's track number) : 101, 102... 201, 201... etc.  After editing just a few of them in MB (adding keywords to track I enjoy), they turn into 101/10, 201/13, etc.

Opening mp3tag every time I need to correct the <track#> MB screwed up gets tiresome real fast.  As a workaround (see thread above), I noticed that Advanced Search and Replace has a preset "Replace '#/#' with '#' in 'Track #'".  I tried it but it didn't work.  The plugin didn't see the '/#' portion.
 
I made a custom preset with the regexp: (\d+)(\/\d+).  It is very simple and works to correct #/# in notepad++ and mp3tag.  However, when saved in Advanced Search and Replace, the preset (like the one provided by ASR) doesn't work.  It only sees '#' rather than '#/#' as seen in mp3tag and tag inspector.

EDIT: Nevermind, I think it this is due to the information being stored in <Track Count>.  Blanking that field and making a new preset to replace everything in that field (^.*$) with a blank and keeping it active might work.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 30, 2016, 10:26:26 PM
let me know if you get it sorted
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on March 31, 2016, 05:15:02 AM
let me know if you get it sorted
Thanks for taking interest in this.  So far, my "Remove Track Count" preset removes <Track Count> fine, but having it checked doesn't seem to prevent MB from automatically filling in the field after editing the album.  Before doing this I decided to start with a clean slate, so I had mp3tag remove ##/## from <Track> since this format was seen in both mp3tag and MB's tag inspector but not within MB's tag editor (strange).  Again, it was a simple regexp search (d+)(\/\d+) and replacing it with \1. 

After 19,000 edits later, I edited a few albums to see what happens with my preset checked.  So far, MB still fills <Track Count>, but <Track> is not expressed as ##/## (a truce?).  The funny thing is that <Track Count> does not appear in either mp3tag or tag inspector, but still in MB's tag editor.  It must be stored/generated in MB's db.  Again, running my preset clears <Track Count>, but any idea how to get it to automatically clear <Track Count> from MB's db?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 31, 2016, 05:48:46 AM
suggest that mb generates track count *after* it calls plugin. though plugin call is asynchronous. i could implement some delay in plugin, but not sure if it helps, because mb can react to tag modification by plugin and regenerate track count again. maybe Steven can comment this?
Title: Re: Additional Tagging and Reporting Tools
Post by: tmprojection on April 16, 2016, 01:37:44 PM
Hey, i want to make use of your "TOY: 'Copy tag' command" command to copy "play count" into a custom field, ie "www radio", but im having a problem, in case of emergencies say i remove a file, or rename it, the musicbee library will reset its playcount and will copy the new tag of 0, which would delete all the previous play counts, is there anyway to use this TOY: 'Copy tag' command with an IF statement? so for example, say i delete an audio file from the library, rename it, import it back in, the www radio tag has say 53, play count in musicbee library has 0, but if the www radio tag value is higher, it copies it back to the play count tag, and continues updating the musicbee library tag, when a track is played 50% it increases by 1, and also updates the www radio tag as well
Title: Re: Additional Tagging and Reporting Tools
Post by: GeekyFreakyEddy on April 24, 2016, 07:49:39 PM
Hey people, I need help. I have some problems with the "Advanced Research and Replace" Function because there are no presets and I don't know how to import them. Also the window don't look really complete. I hope someone can help me.

Sorry for my probably not perfect english^^

PS: Why is there no function to upload pictures? Or is it my fault?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 24, 2016, 07:56:35 PM
To post screenshots:  http://getmusicbee.com/forum/index.php?topic=16499.0
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on April 25, 2016, 01:58:06 AM
Hey people, I need help. I have some problems with the "Advanced Research and Replace" Function because there are no presets and I don't know how to import them. Also the window don't look really complete. I hope someone can help me.

Sorry for my probably not perfect english^^

PS: Why is there no function to upload pictures? Or is it my fault?
I had this issue too when first running ASR.  First things first, check to make sure the preset directory is populated with preset files (*.xml): C:\Users\<username>\AppData\Roaming\MusicBee\ASR Presets.  If the directory is populated with files but the presets are not showing, as it did with me, make sure that "use skin colors" is unchecked under ASR's settings (preferences > Plugins > Additional Tagging Tools > configure > Appearance).  When I unchecked this option, the presets finally came into view after restarting Musicbee.

Updated wiki: http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools#Advanced_Search_and_Replace_presets_are_not_displayed
Title: Re: Additional Tagging and Reporting Tools
Post by: GeekyFreakyEddy on April 25, 2016, 06:18:11 PM
Thank you, ssri! It worked perfectly. But the window still isn't complete...
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on April 25, 2016, 07:25:23 PM
Thank you, ssri! It worked perfectly. But the window still isn't complete...
Please try to describe the window issue and post a screenshot.  Also, post a screenshot of your configuration window (settings) for Additional Tagging and Reporting Tools.  For screenshots, I go to imgbox.com.  Upload the pic as family safe and 350x350 resized (not box!).  After uploading the screenshot on imgbox, copy and paste the contents from the BB-Code box here.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 26, 2016, 05:02:34 AM
@boroda74:

I was trying to make a new preset and botched the regex by putting a { instead of a (.  When I tried to preview it, it crashed MusicBee complete, with this error:

Code
4/25/16 10:58:56 PM - 10.0.10586.0 - 3.0.5959.35156 - System.ArgumentException: parsing "phc_(\d{4})(\d{2}){\d{2})_.*" - Too many )'s.
   at System.Text.RegularExpressions.RegexParser.ScanRegex()
   at System.Text.RegularExpressions.RegexParser.Parse(String re, RegexOptions op)
   at System.Text.RegularExpressions.Regex..ctor(String pattern, RegexOptions options, TimeSpan matchTimeout, Boolean useCache)
   at System.Text.RegularExpressions.Regex.Matches(String input, String pattern, RegexOptions options)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.Replace(String value, String searchedPattern, String replacedPattern, Boolean ignoreCase, Boolean& match)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.SetReplacedTag(String currentFile, Plugin tagToolsPluginParam, AdvancedSearchAndReplacePlugin plugin, Int32 searchedTagId, Int32 replacedTagId, String searchedPattern, String replacedPattern, Boolean ignoreCase, Boolean append, String& searchedTagValue, String& replacedTagValue, String& originalReplacedTagValue)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.GetReplacedTags(String currentFile, Plugin tagToolsPluginParam, AdvancedSearchAndReplacePlugin plugin, Preset presetParam)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.previewChanges()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 26, 2016, 04:19:38 PM
@psychoadept, yes its known issue that regex syntax should be perfectly correct. i haven't fixed this because it seems that almost nobody creates asr presets by himself (and my presets are well  tested). if its important for you i could fix this.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 26, 2016, 04:34:17 PM
I tend to create my own presets but I usually test them first with regexr.  Probably not going to be an issue often enough to bother with.
Title: Re: Additional Tagging and Reporting Tools
Post by: seabeam on April 27, 2016, 05:42:31 PM
Hy,

after updating to the latest Version from 26.02.2016 the window appears like this: (look at the sreenshot): http://imgur.com/blQjjNh

Musicbee Version: 3.0.5960

Thank you for help.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on April 27, 2016, 06:12:39 PM
are you using a high DPI resolution screen?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 29, 2016, 06:31:21 PM
i have no ideas about what is happening. try to answer Steven.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 29, 2016, 06:51:22 PM
@boroda74...

As I'm clearing not-need files/apps from my hard drive, I noticed two ASR Preset sub-directories.  One is under AppData and the other is under Plugins.  I'd be surprised if ASR needed both, but which is the one that is used?  I'd like to delete the other one.

Also, is there a way to send someone  a custom preset?  I'm specifically thinking about earlier this week where I created a step-by-step for a forum user who was having trouble removing track numbers from the artist tag.  It would've been nice if I could've created the preset and sent it to him via PM, email, or even posting in the forum so others could use it.  If this doesn't 'feature' doesn't exist, it would be nice if you could add it at some point in the future.

Thanks for all the time you've put into this plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: GeekyFreakyEddy on April 29, 2016, 07:17:51 PM
@ssri

The text on the right side ends abruptly. It seems there are a lot of buttons missing. Here is the screenshot:

(http://3.t.imgbox.com/IhAwUwVt.jpg) (http://imgbox.com/IhAwUwVt)
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on April 30, 2016, 06:42:38 AM
@ssri

The text on the right side ends abruptly. It seems there are a lot of buttons missing. Here is the screenshot:
Sorry, but I don't see it on my end.  I do admit that I see a little bit of the rightside slightly truncated.

OS: Win7
Screen resolution: 1920x1080
DPI setting:  125%, 120 pixels per inch

(http://0.t.imgbox.com/JlGqrPBk.jpg) (http://imgbox.com/JlGqrPBk)
Title: Re: Additional Tagging and Reporting Tools
Post by: seabeam on April 30, 2016, 11:33:07 AM
Sorry for the late Reply

Windows 10
Screen Resolution: 1680x1050
DPI 100%
Title: Re: Additional Tagging and Reporting Tools
Post by: GeekyFreakyEddy on April 30, 2016, 02:48:04 PM
@ssri

Yes and there were no buttons, but I have solved the problem. It was the german localization. I deleted all localization folders and now I have the english localization - now the window is complete and all buttons are visible.

Title: Re: Additional Tagging and Reporting Tools
Post by: seabeam on April 30, 2016, 05:39:30 PM
i do the same, no effect. The window apperars wihout the Buttons on the right side.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 05, 2016, 12:59:30 PM
@boroda74...

As I'm clearing not-need files/apps from my hard drive, I noticed two ASR Preset sub-directories.  One is under AppData and the other is under Plugins.  I'd be surprised if ASR needed both, but which is the one that is used?  I'd like to delete the other one.

Also, is there a way to send someone  a custom preset?  I'm specifically thinking about earlier this week where I created a step-by-step for a forum user who was having trouble removing track numbers from the artist tag.  It would've been nice if I could've created the preset and sent it to him via PM, email, or even posting in the forum so others could use it.  If this 'feature' doesn't exist, it would be nice if you could add it at some point in the future.

Thanks for all the time you've put into this plugin.
1. 'asr presets' folder in 'plugins' folder exist only because 'plugins' folder is usually read-only without rights elevation, so it wouldn't be possible for plugin to write new presets to this folder. it is used only for importing new presets and not needed for plugin functionality.

2. you can find asr preset in 'appdata\asr presets' folder, but presets names are guids, not descriptive names. you can see preset guid if click 'edit' button in the asr window.

3. there is already sending functionality in asr, but i have disabled it, because it requires setting up smtp server (i think its too difficult for many users). if you are ready to set up smtp server, i can reenable it.
Title: Re: Additional Tagging and Reporting Tools
Post by: seabeam on May 08, 2016, 11:07:36 AM
I solved the Problem for me.

The issue with the window without the Buttons on the right side, is caused by mb_TagTools.resources (C:\Program Files (x86)\MusicBee\Plugins\de).
I have replaced the dll with the Version before the acutal Version and it looks like before and works like before.
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on May 08, 2016, 05:34:25 PM
I solved the Problem for me.

The issue with the window without the Buttons on the right side, is caused by mb_TagTools.resources (C:\Program Files (x86)\MusicBee\Plugins\de).
I have replaced the dll with the Version before the acutal Version and it looks like before and works like before.
hmmm,  good to know.   I haven't updated mine for a few months.  The version I have installed works fine.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 11, 2016, 02:20:12 PM
i'll recheck german localization, but i suggest its something specific to your machine.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 12, 2016, 09:47:58 AM
Thanks boroda74 for showing your interest in PM in developing a new plugin. Actually I have two ideas. Maybe one can be integrated into Additional Tagging Tools plugin, but it's your decision. Here are my ideas.

Template Manager

MB's problem with templates is the number of templates that can be used is limited and changing templates and storing unused templates are either quite cumbersome or not supported. This plugin will provide a way to store unused templates and effectively manage various templates used in MB.

1. Open the plugin under Tools menu or via a hotkey.

2. Select a section among three: virtual tags, external tools commands, custom web links.

3. Each section will show two tables (current and stored) with the same column sets.

<Virtual Tags>
Current
No. | Label | Formula | Descriptions

Stored
No. | Label | Formula | Descriptions

<External Tools Commands>
Current
No. | Label | Path | Parameters | Wait | Descriptions

Stored
No. | Label | Path | Parameters | Wait | Descriptions

<Custom Web Links>
Current
No. | Label | Web Link | Descriptions

Stored
No. | Label | Web Link | Descriptions

4. The user can move each line to anywhere he wants (either on the same table or to the other). Upon saving, the plugin updates both MB's settings file to reflect the changes made onto the current tables and the plugin's data file to save all.

Though the user could edit any cell on the plugin window tables, no need to support writing functions and fields like MB as it's assumed wrting formula is done on MB.


Backup and Restore Tool

It would be useful if a plugin can auto-save MB's xml database file regularly, and when something goes wrong it can assist the user in restoring lost tags. This would allow to import only specific tags from the xml file and thus give more choices to users migrating from other music players. Also it can work as a "tag time machine" since it stores all history of the tag changes made. Then users can keep tag history without having to store multiple versions of music files.

1. Open the plugin under Tools menu or via a hotkey.

2. On Backup section, the user sets how often it will save the xml file and how long it will keep each saved file. Also sets a path to backup. So this section displays the current settings and how many files have been stored since when.

3. On Restore section, the user could select one of the saved xml files to import. This will open a window where the user could select/deselect what tags to be imported. Upon applying it, the plugin will have MB rewrite database file via Library/Import command.

4. Each track shows a context menu command "Tag History". This will open a window where all tag changes made onto the track will display based on the saved xml files (probably the plugin needs to keep a master data file to handle this when each xml file is backed up). Then the user could select an old value to update the current tag value.

5. It could also support backup & restore of MB settings file.
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on May 12, 2016, 04:11:35 PM
Hey boroda74,

With some skins, the colouring of your main panel doesn't work very well.
Especially the readability of text on buttons can be problematic sometimes.
Is it something you can address, or should I throw this in the general direction of Steven?

(and I notice the caption bar doesn't adhere to the skin, but that's not really a big issue)

(http://i.imgur.com/6WJPGYEl.jpg) (http://i.imgur.com/6WJPGYE.png)




Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2016, 05:22:34 PM
"The user can move each line to anywhere he wants (either on the same table or to the other)." i havent gotten this: all 3 tables have different sets of columns.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 12, 2016, 05:29:26 PM
Only between "Current" and "Stored" table on the same section. No need to move to different sections.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2016, 05:48:32 PM
got it. should 'current' table contain just 1 line or you mean by 'current' all stored templates, but stored in native mb configuration file?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 12, 2016, 05:54:06 PM
Yes, all currently stored templates in MB's settings file. 16 for virtual tags, 8 for external tool commands, 6 for custom web links (Steven said he increased custom web links for 3.1, but that can be addressed later).
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on May 12, 2016, 06:04:53 PM
Is it going to be possible to manage organization templates this way, too?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 12, 2016, 06:09:11 PM
and auto-organization ones. i hope, yes. probably i'll start to develop this tomorrow. i intend to extend tag tools plugin, because to develop new plugin afresh is a bit harder, then to reuse existing plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 12, 2016, 06:14:42 PM
I like the idea to extend the current plugin. Thanks for doing this!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 05:08:13 AM
mb coloring api is *very* limited (thats why 'use skin colors' option is unchecked by default), so if its important for you request Steven to extend api or just dont use 'use skin colors' option.
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on May 13, 2016, 07:46:43 AM
No problem, I'll just uncheck 'use skin colors'.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 10:27:29 AM
@redwing
could you make a mockup(s) of tag(s) history dialog(s) and context menu(s)? nothing fancy is needed, just ideas. i cant think something elegant. of course no need for mockups of backup/restore settings dialogs.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 12:18:31 PM
- If there has been no changes in any tags for a track, then "Tag History" context menu command for that track should be disabled. That disabled state itself is a useful information to the user.

- If there were changes, show those tags and values only on the popup window upon clicking on the command. Something like this would suffice, really no need for fancy visual clutters.

(http://i.imgur.com/Afutxl3.png)

The example shows previous values of Title and Album Artist along with when each value was updated.
If the user right-click on one of the previous values, context menu shows "Copy" and "Restore" command. With copy, the user could paste it on a notepad and edit the value (and then could copy and paste it using MB's tag editor). With restore, the plugin overwrites the current value with the selected value.

- Some tag values can be very lengthy (e.g. classical music) and multiple selection of cells needs to be supported. Maybe clicking on a column header could select all tag values on that day like Excel.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 12:48:24 PM
"Copy" "Edit" "Restore"

"Edit" would be also useful when the user wants to edit the current value while browsing previous values.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 01:19:02 PM
thanks. i guess its 'elegant' enough.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 02:00:30 PM
@redwing
It would be useful if a plugin can auto-save MB's xml database file regularly, and when something goes wrong it can assist the user in restoring lost tags. This would allow to import only specific tags from the xml file and thus give more choices to users migrating from other music players
do you mean that backup file format should be itunes xml format rather than my own format? 'time machine' is a simple task for me, but creating itunes xml parser/writer is not that trivial task. are you sure that its important (not (only) for you, but in general)?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 02:04:07 PM
So you're not gonna use MB-created iTunes xml file?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 02:18:03 PM
I thought it would be useful for importing data from backed up MB-created xml files or iTunes/MM-exported xml files. But I guess that can be handled by MB as now.
Yes, use your own format as long as it can backup and restore tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 02:30:41 PM
the problem is that mb api doesn't provide any way to work with importing/exporting any files. there is no way to force mb to write itunes xml file or read it. and i dont want to ask Steven too much, i today sent him a wish for giving me access to all mb templates already.

but (auto)backup/restore tags and 'tag history' written in my own format (more precisely in .net class serialization format) is not a problem at all.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 02:35:36 PM
I understand. Managing iTunes xml files is not a must-have feature. This tool can be useful enough on its own.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 02:39:54 PM
yes, i got your position. just for the record, there is one big problem with itunes xml: i'm pretty sure that this format doesn't support for custom tags at all. no need to answer this my post, it was just a note.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 02:43:11 PM
MB-created xml file saves custom tags too.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 13, 2016, 03:33:40 PM
i'm really surprised.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 13, 2016, 03:57:59 PM
What happens if music files are moved to a new drive?
Would it suffice to run remap music files with MB, or the user has to edit backed up xml files?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 09:55:13 AM
saving/reading backups is not implemented yet (now only ui is ready). i was going to use track file paths as track identifiers. another possible solution is using some guids generated by plugin, but its a harder to implement solution. do you think its important issue? i want to decide this question before i start to write saving/reading functionality.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 10:19:26 AM
If it uses file path as a track identifier, it won't recognize existing files even with a slight change in auto-organization rule. Some more advanced method is needed. The best way would be using MB's own track id (if accessible) then people would only need to run remap music files command with MB when music files are moved to a new drive and the plugin will keep recognizing them as existing files. If it's not accessible, the plugin needs its own remap command in addition to more advanced track identifiers.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 10:35:58 AM
If it uses file path as a track identifier, it won't recognize existing files even with a slight change in auto-organization rule.
you are quite right. thank you that you asked this question early. mb supports for hidden custom tag which can store multiple custom ids for various plugins. this tag is used by ipod driver and google play music plugins. this approach reacquires very many workarounds to make sure that ids are generated for all tracks (ids should be somehow generated on 1st run of plugin, plugin can be temporary disabled, so library should be scanned for empty ids on every start, track moved from inbox to library must be intercepted to generate id, etc.), but file paths as ids are unacceptable.

there is another important question concerning 'tag history': should plugin cache (load to memory) all backups on startup or only information for this track should be loaded on right-clicking on track? its a 'speed vs consumed memory' question. considering that 'tag history' menu item must be disabled if there are no backups for this track, there may be temporary freeze just on right-clicking on track. tags might not to occupy much memory by themselves except for artworks. but what if there are 100's of backups?  the problem is that there is a limit on available memory: only 2gb for 32-bit apps. what do you think about this?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 10:55:18 AM
should plugin cache (load to memory) all backups on startup

I don't think this would be necessary.

or only information for this track should be loaded on right-clicking on track?

Yes, I'd expect it would work this way. Also selecting multiple tracks won't show the command.


but what if there are 100's of backups?

I don't think in general people change tags that quite often. If the plugin keeps a master data file, it only needs to record new changes when a back up is made, then there won't be much new data to save each time. So the number of backups itself won't matter much.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 11:14:06 AM
Also consider not supporting inbox files for tag history feature as they would increase data to store tremendously but most of those data would be useless because that's what inbox is for. But each back up file should include those.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 12:18:20 PM
Also consider not supporting inbox files for tag history feature as they would increase data to store tremendously but most of those data would be useless because that's what inbox is for. But each back up file should include those.
yes, of course. i was planning to make things this way from beginning.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 12:23:44 PM
I don't think in general people change tags that quite often.
no, the problem is that context menu will contain 'tag history' command and this command must be enabled or disabled depending on is there backup data for this track or not. i.e. even if user uses context menu for other purposes than 'time machine', there can temp ui freezing anyway. though i may not disable 'tag history' command even if there is no data.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 01:15:51 PM
Then always enabling the tag history context menu command solves the problem? If so, do it that way. It won't be an issue as it would only require one more click to pop up "No backup data for tag changes" message when there's no changes.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 01:28:38 PM
ok
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 01:35:25 PM
@redwing
i want to know your opinion:
is it better to restore selected tags for the whole library or for selected tracks only? ofc if one of selected tracks was never backed up, nothing will be changed for this track.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 01:51:23 PM
Can you support both? Restoring for selected tracks would be useful when you saved wrong tag values to the whole tracks in a filter. If you restore for the whole library in this case then you will lost tag changes made onto other unaffected tracks. On the other hand, restoring the whole library would be useful when all tracks got wrong or outdated values (e.g. when you have to use backup music files that were backed up long time ago).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 02:48:14 PM
restoring to selected tracks also allows to restore the whole library, just select all files, but it can require a few more clicks. do you still think that its better to make 2 restore commands?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 03:08:41 PM
Yes, selecting all library files and inbox files would require creating a new playlist/filter but auto-playlists exclude banned tracks. And what about hidden duplicates? It's not straight forward. Restoring an entire library shouldn't be that hassle.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 14, 2016, 03:16:13 PM
I forgot to mention but you probably figured that some people might prefer manual backup only, so auto-backup should be an option.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2016, 08:52:32 PM
I forgot to mention but you probably figured that some people might prefer manual backup only, so auto-backup should be an option.
yes, its already an option.
Title: Re: Additional Tagging and Reporting Tools
Post by: Don_Leon_87 on May 18, 2016, 03:32:15 PM
Hello,

Can someone please explain how i can use this plugin to sort my music as "Date Created"?
I finally switched from Winamp to Musicbee and i really like it, but i really miss this option. And i can't figure out how to do this.

Thank you

Edit: I got it! Thank you for making this plugin
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 18, 2016, 05:04:18 PM
just want to give you some details: you can use the dedicated 'copy tag' command to copy '<date created>' pseudo-tag to custom tag or you might want to tick 'toy: copy tag' asr preset to automatically do the same when you add new track to the library.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 11, 2016, 10:28:07 AM
Hello Boroda,

Around a year ago I reported what I think is a bug in the preset to add a leading zero.
It adds zeros in all cases (with results as 013, 021 and also 001, 008) whereas I expect it to add the zero ONLY before ONE single digit: 1 > 01, 2 > 02 etc.
I got the reply that there was no problem.
But whatever I tried since then, I could not get the result I expected.
Any solution?

Thanks!
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: Ravoblex on June 13, 2016, 06:30:38 PM
I installed "Additional Tagging and Reporting Tools" with the hopes of exporting my 5-Star albums to external file for cataloging. I created the subfolder ASR Presets. It still doesn't show up in Preferences/Plugins.

I installed the plugin directly into the plugins folder without creating the plugin's own folder as per the instructions. This seemed odd, but I did it. Then I created the ASR sub-folder.

Any ideas as to what I may be doing wrong?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 13, 2016, 10:02:14 PM
Hello Boroda,

Around a year ago I reported what I think is a bug in the preset to add a leading zero.
It adds zeros in all cases (with results as 013, 021 and also 001, 008) whereas I expect it to add the zero ONLY before ONE single digit: 1 > 01, 2 > 02 etc.
I got the reply that there was no problem.
But whatever I tried since then, I could not get the result I expected.
Any solution?

Thanks!
Wim
the only suggestion i have is you have changed version of preset. try to re-import all presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 13, 2016, 10:03:53 PM
I installed "Additional Tagging and Reporting Tools" with the hopes of exporting my 5-Star albums to external file for cataloging. I created the subfolder ASR Presets. It still doesn't show up in Preferences/Plugins.

I installed the plugin directly into the plugins folder without creating the plugin's own folder as per the instructions. This seemed odd, but I did it. Then I created the ASR sub-folder.

Any ideas as to what I may be doing wrong?
no ideas except for plugin dll may be corrupted. try to re-download plugin zip again.

p.s. what mb version you are using?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 14, 2016, 04:56:43 PM
@boroda
Did what you suggested, even more: downloaded the newest plugin version > closed MB > deleted the old plugin parts in my MB folder > extracted the newest version there > restarted MB > activated ASR > imported all presets > did a new test > same result.
As the attached .jpg shows: the ASR screen PROMISES to leave 10, 11, 12, 13 unchanged, but as the results show it DOES CHANGE them into 010, 011, 012, 013.
(And if you repeat the same test the result is even stranger: 07, 08, 09, 010, 011, 012 change into 007, 008, 009, 10, 11, 12).

http://imgur.com/YrhG5IO



Long time ago I personalized a number of the default presets and put them on the top of my ASR-screen, but for this test I used 'your' unchanged default preset that promises to add zeros.
What is wrong?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 14, 2016, 05:36:14 PM
i never was able to reproduce this, but sometimes there may be very strange errors on some pcs. suggest its specific to your .net installation. the code for writing preview results is very straightforward (and always was working fine for me). not sure what i could make in this case.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 14, 2016, 06:10:06 PM
But for me it has been working FINE for several years, all of a sudden it changed, on the same pc.
No idea if other software was disturbing, no idea about .net.

Can I myself make a change in the setting of the script - although I have no clue how to do it...
For instance: add 1 zero to a number with 1 digit, add nothing to numbers with 2 digits?
(Only VERY VERY exceptionally I have track numbers >100)

If such change is possible, can you tell me how. Or could you change 'your own' preset this way?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 14, 2016, 06:28:24 PM
Also: after the NEW installation of the NEWEST plugin version, I still see my own personalized ASR screen when I startup MB again, including the presets that I copied/renamed in the past.
Could that be part of the problem?
If it is, then how to I make a completely FRESH plugin installation?
I don't know what else to delete to make a fresh start...
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 14, 2016, 06:41:11 PM
Looks like regex used in that preset won't work properly for track numbers.

Instead of
^(\d+)

try
^([1-9])$
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 14, 2016, 06:57:15 PM
Also: after the NEW installation of the NEWEST plugin version, I still see my own personalized ASR screen when I startup MB again, including the presets that I copied/renamed in the past.
Could that be part of the problem?
If it is, then how to I make a completely FRESH plugin installation?
I don't know what else to delete to make a fresh start...
Wim

They are stored under AppData\ASR Presets folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 14, 2016, 06:57:58 PM
First test result: WORKS!
No time for more experiments now, will inform you in a few days if all is ok now.
In that case please implement the change in your 'own' preset too.
Thanks!
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 14, 2016, 07:12:09 PM
Also: after the NEW installation of the NEWEST plugin version, I still see my own personalized ASR screen when I startup MB again, including the presets that I copied/renamed in the past.
Could that be part of the problem?
If it is, then how to I make a completely FRESH plugin installation?
I don't know what else to delete to make a fresh start...
Wim
no, this cant be the problem because every asr preset is completely independent xml file. you can delete 'appdata\asr presets' folder as redwing said or you can delete any (your or standard) preset in asr dialog by selecting (NOT ticking!) preset and clicking on 'delete' button.

p.s. try to copy my preset and edit the copy as redwing suggested. if you succeed post results here and i'll add new preset for track numbers (though my preset is working fine on my pc).


edit: i can vaguely recall that there is an option in mb prefs (not in *plugin* prefs) to add leading zeros to track numbers. try to disable this option to see if this helps.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 15, 2016, 07:22:50 AM
@boroda74;

I'm not sure what the preset is intended to do. Its title says "Add up to 2 leading zeros to first digits of <Tag 1>", but its description says "e.g. '1 text' will be replaced with '01 text', '1' is replaced with '01' and 'text' remains unchanged". Was your original intention to convert "1" to "001"?

Anyway I don't think a new preset for track numbers is needed as MB already has Renumber Tracks command that can handle multiple digits.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 15, 2016, 03:55:53 PM
I'm not sure what the preset is intended to do. Its title says "Add up to 2 leading zeros to first digits of <Tag 1>", but its description says "e.g. '1 text' will be replaced with '01 text', '1' is replaced with '01' and 'text' remains unchanged". Was your original intention to convert "1" to "001"?

its a mistake in preset name (and the same mistake for second 'add leading zeros...' preset). i've corrected these 2 mistakes in names and have changed preset reg exes so now these 2 presets should work always correctly, but still allows to have some (preserved) text after digits. also i've added 3d similar preset to make tags 3 digits.

@WimYogya
could you try these 3 new presets on your machine? just unrar the content of archive to 'plugins' folder and overwrite all files, then 'import all' asr presets in mb.

http://www.mediafire.com/download/1dumoxp4g5vpi38/ASR_Presets.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 17, 2016, 06:12:59 PM
@boroda
Came across your previous reply by coincidende. Downloaded, extracted and installed the presets, will explore more (no time now) and inform you.

I came here to ask if you or 'normal users' have problems with the split-presets. I do. In the past they worked fine, but now not.
I cannot detect the problem.
But if I want to split tag1 into tag2 and tag3, there are often (not always!) problems when there is a 'separator' sign or text. Often - or / or ; but even if I replace them with ### or so, they are not recognized as splitters.
Do I do anything wrong?
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 17, 2016, 06:46:41 PM
As to the leading zero's: first 2 tests result: works OK but does not LOOK ok > just a minor detail: you promise FIVE zeros in stead of three... ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 18, 2016, 09:28:24 AM
As to the leading zero's: first 2 tests result: works OK but does not LOOK ok > just a minor detail: you promise FIVE zeros in stead of three... ;-)
actually instead of 4 (up to 5 total digits) :-) its corrected for the next plugin update.

split presets are working fine for me.
try this split preset, its just a minor minor modification of original preset, its named "Split '<Tag 1>' to tags '<Tag 2>', '<Tag 3>' *" (note asterisk!):

http://www.mediafire.com/download/56b1hsbtg8yyupo/2acc97f0-bd50-476a-8f2a-680eedca8985.ASR_Preset.xml

place this preset to "<appdata>\asr presets" folder and restart mb.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 19, 2016, 11:27:04 AM
The new split preset does not change anything.
PERHAPS the cause of the trouble is the following: the beginning of the splitter text box is invisible (in my view at least) because the preceding label is a bit too long: it covers the first 1 or 2 spaces of the text box.
Please check if this makes sense...
Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 20, 2016, 06:19:25 AM
could you post a screenshot? seems to be ui bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 20, 2016, 01:03:03 PM
http://imgur.com/y1SIu7D

This is the newly modified * version. It has a strange unknown character as default. What is it and why?
But (similar to the other versions) that 'first character' is not in the first position, because 'custom text 1 >' is a bit too long. Goes for the other text boxes as well..
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 20, 2016, 01:05:54 PM
Does ASR have a preset to remove a desired number of characters from a field, e.g. 'remove the first x characters from the beginning of field 1'?
If not, is there a way to do that?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2016, 11:30:45 AM
The new split preset does not change anything.
PERHAPS the cause of the trouble is the following: the beginning of the splitter text box is invisible (in my view at least) because the preceding label is a bit too long: it covers the first 1 or 2 spaces of the text box.
Please check if this makes sense...
Thanks,
Wim
place it to 'musicbee\plugins' folder and retype needed custom text from scratch. but i'm doubtful that this will help.

http://www.mediafire.com/download/ehgjhi4c8jtdwm9/mb_TagTools.dll
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2016, 11:37:06 AM
This is the newly modified * version. It has a strange unknown character as default. What is it and why?
its just a slash (partially obscured). i had a computer crash and loosed half of tag tools project (i mean current plugin version which is not released yet). i need to rewrite all missing code, after that i could adjust ui (though i don't have this glitch on my pc).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2016, 11:45:19 AM
Does ASR have a preset to remove a desired number of characters from a field, e.g. 'remove the first x characters from the beginning of field 1'?
If not, is there a way to do that?
there are 2 'remove leading zeros...' presets, but that's not exactly what you asked. do you want to remove given number of digits or leave given number of digits (removing all before these digits)? digits or zeros?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 21, 2016, 11:57:41 AM

its just a slash (partially obscured). i had a computer crash and loosed half of tag tools project (i mean current plugin version which is not released yet). i need to rewrite all missing code, after that i could adjust ui (though i don't have this glitch on my pc).
[/quote]

Sorry to hear you lost so much work. No backup available?? Take your time with UI adjustments, I just keep reporting/asking - it is up to you to see if things are urgent/essential and if/when you have time to change/update features.
See for instance my next reply...
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 21, 2016, 12:00:30 PM
there are 2 'remove leading zeros...' presets, but that's not exactly what you asked. do you want to remove given number of digits or leave given number of digits (removing all before these digits)? digits or zeros?
[/quote]

No, I am not referring to the specific removal of zeros, not even of digits, but of ANY type of character in a field. Sometimes people spread music files with ridiculous and confusing tags - then it can be useful if you just can remove 7 or 15 or 31 characters from the beginning or the end of a field, to keep the 'correct info'.
Although I did not mean it, the option to 'keep a certain number of characters' or a specific text string could perhaps be useful for others.

PS
Sorry for not using the /quote format correctly - don't really know how I have to start and finish the /quote...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2016, 02:01:26 PM
http://www.mediafire.com/download/khv0t42am7d2k22/ASR_Presets.rar

unrar to 'musicbee\plugins' folder, then 'import all' presets. you need preset 'remove given number of characters...'.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on June 21, 2016, 06:45:48 PM
@boroda
Have to thank you LOTS for your speedy and effective cooperation:
1. The split problem seems to be solved. As I already assumed the custom text LABEL made the first space (with the default character - ) invisible, so every new character in the box created a mismatch. Now OK., after replacing the .dll there is more space between the label and the text box.
2. The 'remove a given number of characters' works!

A (new?) thing for the long term, when you improve the UI:
In the list of presets the text lines are too tight above one another. The result is that the letters like p q h 'loose' their 'stick' which makes reading a little more difficult. Add some space.

Again: thanks!
Success with your restoration ;-)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 21, 2016, 07:28:34 PM
In the list of presets the text lines are too tight above one another. The result is that the letters like p q h 'loose' their 'stick' which makes reading a little more difficult. Add some space.
this list is a native .net control. i'll check its possible configuration, but hardly its possible to extend space between lines. don't want to write my own control for this.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on July 01, 2016, 09:15:32 AM
In the Change Case drop down list I have a multitude of 'smaller' or 'special' words that I want to include or exclude in my options.
My default case format is the Toggle View, but with exceptions.
Since I want to specify those exceptions per language or per 'special category' I made several lines.
Example:
ENGLISH: at am on of for from in it etc...
FRENCH: un une unes le la les etc...
(similar for GERMAN, SPANISH, ITALIAN, DUTCH)
ABBREVIATIONS: 10CC UB40 OMD O.M.D. U.S.A. USA etc.

And now my problem:
(example)
If I add a new word to the ENGLISH list, I suddenly have TWO English lists, with only 1 word as a difference.
How can I avoid that?
I like to have just ONE list/line per language/category.

Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 01, 2016, 01:17:43 PM
i guess ui will be very cluttered if i add some sophisticated 'organizing' capabilities. only 10 (as far as i remember) last exceptions are stored, so old exceptions will be off the list over time. alternatively i can sort that list in most recently used order (if its not the case right now, don't remember).
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on July 02, 2016, 05:57:54 PM
@boroda:
If it's not possible: pity but no problem.
Is there no way to manually remove the unnecessary word lists, and just keep the updated versions?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 03, 2016, 07:35:10 AM
i think i'll just add 'remove' button next to exception field, which will remove currently entered in the field word list from exception history (if there is any match in the history), so you can just select not needed exception in the history and immediately remove it.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on July 03, 2016, 05:27:52 PM
I think that would be a GREAT solution and improvement for me. Thanks for doing it, but don't hurry, take your time. Nothing urgent.
And when done, please let me know. Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: dylstew on July 10, 2016, 04:03:27 PM
It works with a simple html and text file, but if I export it as an html document, I get this error (sorry, it's dutch):

''MusicBee v3.0.5995.40050 (Win6.1), 10 jul 2016 17:02:

System.IO.DirectoryNotFoundException: Kan een gedeelte van het pad F:\Program Files (x86)\MusicBee\Plugins\Artists.files\t.files\stylesheet.css niet vinden.
   bij System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bij System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bij System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   bij System.IO.FileStream..ctor(String path, FileMode mode)
   bij MusicBeePlugin.HtmlDocument.writeHeader()
   bij MusicBeePlugin.LibraryReportsPlugin.exportTrackList()
   bij MusicBeePlugin.LibraryReportsPlugin.buttonOK_Click(Object sender, EventArgs e)
   bij System.Windows.Forms.Control.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bij System.Windows.Forms.Control.WndProc(Message& m)
   bij System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bij System.Windows.Forms.Button.WndProc(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)''

The main error means ''Can't find part of path'', and then it can't find stylesheet.css.
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on August 03, 2016, 12:48:38 AM
Hmm, it appears that "Replace '#/#' with '#' in Track#" does not work.  Under preview, Track# and "New Tag Value" appears the same although the latter is in red (I guess to signify changed tags).  However, after hitting apply and save all and close, Track# appears to still be in the format "##/##" in the id3 tag frame <TRCK> under mp3tag and tag inspector.
Title: Re: Additional Tagging and Reporting Tools
Post by: seabeam on August 04, 2016, 10:26:21 AM
hy
thank you for this great plugin, ic have one question:

Is it possible to modify the MB-Database Field "DateAdd" with the Tools?
Title: Re: Additional Tagging and Reporting Tools
Post by: Ravoblex on August 11, 2016, 07:18:01 PM
I've searched and cannot find a solution for this. But how do I create a Preset to search and replace a single word (among many) in the Comment field of an ID3 tag? For example, to replace the word "Fun" with "Happy" but leave the rest of the comments the same?
Title: Re: Additional Tagging and Reporting Tools
Post by: Ravoblex on August 11, 2016, 07:24:47 PM
Figured it out. The regular search and replace function accomplished this just fine. Thanks. :/
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 23, 2016, 11:58:53 AM
@boroda74;

Just wondering how this is going. Are you still working on it?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 24, 2016, 12:24:20 PM
(edit: almost) all had been completely done for backup/restore, but i had computer crash and had lost about half of tag tools project (hadn't uploaded project for backup purposes). i've restored part of new code combining uploaded old and corrupted new project, but unfortunately much code is lost now anyway. don't know when i have a time to rewrite lost code. also i've stopped writing code before crash when i needed Steven support on mb side and this support is not implemented yet anyway (suggest that it won't be implemented until 3.1).

as for template organizer i even hasn't started to write it yet (and i need Steven support for this also, so waiting for 3.1 again).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 24, 2016, 01:12:54 PM
Sorry to hear your trouble. Never mind this request then for now.

About the lost project, isn't the uploaded old source file (2015-03-22) good enough? Actually I haven't updated the plugin since then, but had no problem so far.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 24, 2016, 04:28:54 PM
About the lost project, isn't the uploaded old source file (2015-03-22) good enough? Actually I haven't updated the plugin since then, but had no problem so far.
uploaded project is the last version before i've started to write backup/restore. but most backup/restore code i've lost.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 02, 2016, 08:28:25 AM
here is the latest source code of plugin. most part of backup/restore code is rewritten. its just for backup purposes, this project is not intended for end users.

http://www.mediafire.com/download/26259gywkcaknpb/TagTools_2016-09-02.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 03, 2016, 01:03:09 PM
It works with a simple html and text file, but if I export it as an html document, I get this error (sorry, it's dutch):

''MusicBee v3.0.5995.40050 (Win6.1), 10 jul 2016 17:02:

System.IO.DirectoryNotFoundException: Kan een gedeelte van het pad F:\Program Files (x86)\MusicBee\Plugins\Artists.files\t.files\stylesheet.css niet vinden.
   bij System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bij System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bij System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   bij System.IO.FileStream..ctor(String path, FileMode mode)
   bij MusicBeePlugin.HtmlDocument.writeHeader()
   bij MusicBeePlugin.LibraryReportsPlugin.exportTrackList()
   bij MusicBeePlugin.LibraryReportsPlugin.buttonOK_Click(Object sender, EventArgs e)
   bij System.Windows.Forms.Control.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnClick(EventArgs e)
   bij System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bij System.Windows.Forms.Control.WndProc(Message& m)
   bij System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bij System.Windows.Forms.Button.WndProc(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)''

The main error means ''Can't find part of path'', and then it can't find stylesheet.css.
somewhat old answer, but try to export html document to writable folder, eg. desktop instead of 'program files'.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 03, 2016, 01:10:13 PM
Hmm, it appears that "Replace '#/#' with '#' in Track#" does not work.  Under preview, Track# and "New Tag Value" appears the same although the latter is in red (I guess to signify changed tags).  However, after hitting apply and save all and close, Track# appears to still be in the format "##/##" in the id3 tag frame <TRCK> under mp3tag and tag inspector.
download latest presets:

http://www.mediafire.com/download/khv0t42am7d2k22/ASR_Presets.rar

unrar them to 'musicbee\plugins' folder and reimport all presets in asr window. also make sure that existing 'track number' values are in '#/#' format (they may be for example in '#-#') format.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 03, 2016, 01:11:23 PM
hy
thank you for this great plugin, ic have one question:

Is it possible to modify the MB-Database Field "DateAdd" with the Tools?
no, this field is read-only for any plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 03, 2016, 01:14:59 PM
In the Change Case drop down list I have a multitude of 'smaller' or 'special' words that I want to include or exclude in my options.
My default case format is the Toggle View, but with exceptions.
Since I want to specify those exceptions per language or per 'special category' I made several lines.
Example:
ENGLISH: at am on of for from in it etc...
FRENCH: un une unes le la les etc...
(similar for GERMAN, SPANISH, ITALIAN, DUTCH)
ABBREVIATIONS: 10CC UB40 OMD O.M.D. U.S.A. USA etc.

And now my problem:
(example)
If I add a new word to the ENGLISH list, I suddenly have TWO English lists, with only 1 word as a difference.
How can I avoid that?
I like to have just ONE list/line per language/category.

Thanks,
Wim

i think i'll just add 'remove' button next to exception field, which will remove currently entered in the field word list from exception history (if there is any match in the history), so you can just select not needed exception in the history and immediately remove it.


download latest plugin version:

http://www.mediafire.com/download/ehgjhi4c8jtdwm9/mb_TagTools.dll

copy this dll to 'plugins' folder and overwrite existing file. its a beta, but just ignore backup/restore section of plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on September 04, 2016, 03:36:01 AM
test presets:

http://www.mediafire.com/download/khv0t42am7d2k22/ASR_Presets.rar

unrar them to 'musicbee\plugins' folder and reimport all presets in asr window. also make sure that existing 'track number' values are in '#/#' format (they may be for example in '#-#') format.
Thanks for the presets boroda.  Yeas, the track number values are in #/# format.  Sadly, it doesn't appear that the updated preset worked where hitting "apply" and then "save all & close" doesn't change the TRCK value like it did before:

(http://4.t.imgbox.com/dr1TNP51.jpg) (http://imgbox.com/dr1TNP51)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 04, 2016, 05:21:25 PM
hmm... unfortunately i don't have direct access to id3v2 tags in my plugin, i can use only mb tagging system instead. i see in your screenshot that mb *tag editor* displays correct track number. i recommend you write a post in 'general' section of the forum and ask Steven why this happens.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steve Duncan on September 10, 2016, 12:11:35 AM
Hi there,
Psychoadept told me that I might be able to get some help if I post here.
I always seem to post in the wrong area of the forum.
What the problem is is with Additional tagging & reporting tools.
Yesterday, I used the "Swap Tag" function and then minimized it and it went into the left hand corner of my screen.
Today, when I went into the function, it showed up, but only a tiny box in the left side corner.
Furthermore, the "Maximize" button is blacked out and isn't active even when I press the little wrench icon to the left of it.
So basically, I can't use this function.
I have done a system restore and have downloaded the latest patch, bu it still doesn't work.
Anyone who could help, I would be really appreciative to!

(P.S. - I went to the thread under the same name that I used, but there was no box for me to leave a new comment.  So I had no choice but to go this route.)
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on September 10, 2016, 12:55:37 AM
(P.S. - I went to the thread under the same name that I used, but there was no box for me to leave a new comment.  So I had no choice but to go this route.)

I merged your post into the original thread.  Do you see the Reply button under the last post?
Title: Re: Additional Tagging and Reporting Tools
Post by: Steve Duncan on September 10, 2016, 12:57:46 AM
Yes, thank you very much psychoadept.  It is there now, but wasn't when I first looked.
Appreciate it!
Title: Re: Additional Tagging and Reporting Tools
Post by: Steve Duncan on September 10, 2016, 07:08:23 AM
Hi psychoadept?
I managed to fix that problem I had with the "Swapping" function, but guess what?
It seems as soon as I did, something else happened.
I went to the "Advanced Search & Replace" box, and you know where there is the button which asks you if you want to import presets?  Well, now IT doesn't work.
I press "Yes" and then get a message that "No presets were imported."
Again, this never happened to me before.  It used to load about 82 presets, but now - nothing.
Any ideas at all?
Thank you.  :/
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 11, 2016, 07:08:01 AM
Steve, it seems that you removed 'asr presets' folder from 'plugins' folder. maybe its easier for you just to reinstall plugin?
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on September 11, 2016, 08:08:00 AM
Hi psychoadept?
I managed to fix that problem I had with the "Swapping" function, but guess what?
It seems as soon as I did, something else happened.
I went to the "Advanced Search & Replace" box, and you know where there is the button which asks you if you want to import presets?  Well, now IT doesn't work.
I press "Yes" and then get a message that "No presets were imported."
Again, this never happened to me before.  It used to load about 82 presets, but now - nothing.
Any ideas at all?
Thank you.  :/
You did something.  Like Boroda said reinstall the plugin and if it still fails, try this: http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools#Advanced_Search_and_Replace_presets_are_not_displayed
Title: Re: Additional Tagging and Reporting Tools
Post by: Steve Duncan on September 11, 2016, 09:10:03 PM
Thank you boroda 74 & ssri.
I did as you suggested, and now it is working normally as usual!  YAY!
Let's keep our fingers crossed that it stays that way!
Thank you both and you, psychoadept, for helping me with this problem!
Cheers!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 20, 2016, 01:14:51 AM
latest plugin source code (again mostly for backup purposes):

http://www.mediafire.com/download/6j5i5o705jcb6uc/TagTools_2016-09-20_02-38-06.rar

backup/restore code is completed except for 3 lines of code (now i need to wait when persistent track ids are supported by mb).

its compiled plugin beta, just if some curious how it looks now. beta seems to be stable, but DON'T use it on a real library. also backup/restore supports libraries with one track only at the moment:

http://www.mediafire.com/download/c139z836cud2c4u/mb_TagTools_2016-09-20-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: euanek on September 21, 2016, 07:39:31 PM
Hey all:

I've searched this thread and didn't find an answer to this question, but if I missed something and this question is redundant, please let me know.

My question is: is there a way to append a text phrase to the "comments" field? It seems like the "copy tag" tool can append data, but I don't want to copy a tag. I want to, for example, append the text "Mix 1" to all the files I have selected, and I'd like to do so without having to first tag them somewhere as "Mix 1".

Thanks!

x
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 21, 2016, 10:58:07 PM
i never intended to make this feature, but might try 'copy' to the same tag. if its not possible try to search appropriate asr preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on September 22, 2016, 03:49:39 AM
Hey all:

I've searched this thread and didn't find an answer to this question, but if I missed something and this question is redundant, please let me know.

My question is: is there a way to append a text phrase to the "comments" field? It seems like the "copy tag" tool can append data, but I don't want to copy a tag. I want to, for example, append the text "Mix 1" to all the files I have selected, and I'd like to do so without having to first tag them somewhere as "Mix 1".

Thanks!

x
Try the following below.  It will result in <Comment> foo > <Comment> foo Mix 1

It will even work in <Comment> with multiple lines, i.e.

foo 1                        foo 1

foo 2           >           foo 2

foo 3                        foo 3 Mix 1

1) Create new Preset (add name and description)
2) Under the preset editor, for "Step 1"
    Search for:
Code
\Z
   Replace with:
Code: "notice the space at the beginning"
 Mix 1
3) Set the tags to <Comment>
4) Press OK
5) Go back to MB and select a few files you want to edit
6) Select the new present
7) Preview
8) Apply and check tags
9) If happy, save all & close
NOTA BENE: Do not check the preset because if you do, it will run the preset on every file you select.  So, leave it unchecked.

(http://6.t.imgbox.com/cegHRMX6.jpg) (http://imgbox.com/cegHRMX6)
^EDIT NOTE: In the screenshot, " foo" under Replace with: should be " Mix 1" (w/o quotes) to coincide with the above instructions
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on September 22, 2016, 04:04:59 AM
Hey Boroda,

Is it possible to assign a preset to a hotkey?

I miss that ability in Mediamonkey's add-on "RegExp Find and Replace"

For example, I have it in Mediamonkey where if I want to label a track from the 80s by adding\appending "80s" to a custom tag field, I press CTRL+ALT+8 (a hotkey I assigned to that particular preset).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 22, 2016, 09:17:59 AM
Hey Boroda,

Is it possible to assign a preset to a hotkey?
its not very straightforward, but i think, yes, its possible. i'll try to experiment first.
Title: Re: Additional Tagging and Reporting Tools
Post by: euanek on September 23, 2016, 08:45:40 PM
Hey all:

I've searched this thread and didn't find an answer to this question, but if I missed something and this question is redundant, please let me know.

My question is: is there a way to append a text phrase to the "comments" field? It seems like the "copy tag" tool can append data, but I don't want to copy a tag. I want to, for example, append the text "Mix 1" to all the files I have selected, and I'd like to do so without having to first tag them somewhere as "Mix 1".

Thanks!

x
Try the following below.  It will result in <Comment> foo > <Comment> foo Mix 1

It will even work in <Comment> with multiple lines, i.e.

foo 1                        foo 1

foo 2           >           foo 2

foo 3                        foo 3 Mix 1

1) Create new Preset (add name and description)
2) Under the preset editor, for "Step 1"
    Search for:
Code
\Z
    Replace with:
Code: "notice the space at the beginning"
 Mix 1
3) Set the tags to <Comment>
4) Press OK
5) Go back to MB and select a few files you want to edit
6) Select the new present
7) Preview
8) Apply and check tags
9) If happy, save all & close
NOTA BENE: Do not check the preset because if you do, it will run the preset on every file you select.  So, leave it unchecked.

(http://6.t.imgbox.com/cegHRMX6.jpg) (http://imgbox.com/cegHRMX6)

THANKS!!! ssri -- that works perfectly!
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on September 24, 2016, 02:59:04 AM
Try the following below.  It will result in <Comment> foo > <Comment> foo Mix 1

It will even work in <Comment> with multiple lines

THANKS!!! ssri -- that works perfectly!
I'm glad to hear that it works.  Sorry about the screenshot.  I just realized that the entry " foo" under Replace with: should have been " Mix 1".  I'm glad that it didn't throw you off.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on September 28, 2016, 05:09:12 PM
@boroda74-

I haven't used this plugin for about a month and now that I'm using it almost daily I'm finding that the plugin window always opens towards the upper left corner of my monitor. I then have to drag it more towards the center so I can work comfortably with it. And then I close it. But each time I reopen it, with or without closing MB, it reappears towards the upper left.

I'm not sure if this is a Steven thing or if you can do it, but can the plugin window please be made persistent? Please let me know if it's out of your control and I'll post it where Steven is more likely to see it. I can't really remember if the window was persistent when I was using it a while ago.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 29, 2016, 09:19:10 AM
you are using some beta version. its temporary intentional behavior (visual studio doesn't allow to use visual form editor if i turn on remembering window sizes/positions). redownload plugin from official link or try this beta:

http://www.mediafire.com/file/c139z836cud2c4u/mb_TagTools_2016-09-20-beta.zip

don't try to use backup/restore part of beta, its not completed yet!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 29, 2016, 07:19:24 PM
new version. it seems to be stable. at least working fine for me.

http://www.mediafire.com/file/6k7o89xkbvmu5ae/mb_TagTools_2016-09-29-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on September 29, 2016, 07:19:57 PM
Hey Boroda,

Is it possible to assign a preset to a hotkey?

I miss that ability in Mediamonkey's add-on "RegExp Find and Replace"

For example, I have it in Mediamonkey where if I want to label a track from the 80s by adding\appending "80s" to a custom tag field, I press CTRL+ALT+8 (a hotkey I assigned to that particular preset).

http://www.mediafire.com/file/6k7o89xkbvmu5ae/mb_TagTools_2016-09-29-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on September 29, 2016, 08:15:01 PM
you are using some beta version. its temporary intentional behavior (visual studio doesn't allow to use visual form editor if i turn on remembering window sizes/positions). redownload plugin from official link or try this beta:

http://www.mediafire.com/file/c139z836cud2c4u/mb_TagTools_2016-09-20-beta.zip

don't try to use backup/restore part of beta, its not completed yet!
Thanks. Tried this beta, and the one from today 2016-09-29. While both do what I wanted - persistent window location - they both also throw this error when I right-click on a track and select Additional Tagging Tools > Change Case > Close. All of the other Additional Tagging Tools in that dialog close properly. And all but 'change case' close properly if I open it from the Tools menu. It's only the 'change case' option that throws the error.
Code
MusicBee v3.0.6114.37635 (Win6.1), 29 Sep 2016 15:14:

System.ArgumentNullException: Value cannot be null.
Parameter name: dest
   at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
   at System.Collections.ArrayList.CopyTo(Array array, Int32 arrayIndex)
   at MusicBeePlugin.ChangeCasePlugin.buttonCancel_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on September 30, 2016, 11:47:23 AM
new version. it seems to be stable. at least working fine for me.

http://www.mediafire.com/file/6k7o89xkbvmu5ae/mb_TagTools_2016-09-29-beta.zip

Does this version support backup and restore commands?

I just tried but can't figure out how to use it.
BTW track tag history command throws the following error:

10.0.14393.0 - 3.0.6116.38898 - System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.TagHistoryPlugin.initializeForm()
   at MusicBeePlugin.TagHistoryPlugin..ctor(Plugin tagToolsPluginParam, String[] trackUrlsParam, String[] trackIdsParam)
   at MusicBeePlugin.Plugin.tagHistoryEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 01, 2016, 09:03:53 AM
this bug is fixed, but you probably will need to delete mb_tagtools.settings.xml in <appdata> folder anyway.

http://www.mediafire.com/file/7nidu1z81crt8so/mb_TagTools_2016-09-30.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 01, 2016, 10:12:14 AM
yes, ofc this version surpports backup/restore commands. as for the bug, try this version, but you probably will need to delete mb_tagtools.settings.xml in <appdata> folder:

http://www.mediafire.com/file/7nidu1z81crt8so/mb_TagTools_2016-09-30.zip

NOTE: you will need to use mb latest patch to use this plugin version.

PS: please report back even if your experience with backup/restore is successful. i want to get some feedback, before i mark this version as stable.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2016, 10:55:51 AM
The bug's fixed.

But as I said I still don't get how to use this.

I ran "Backup tags for all tracks" command but when I look inside the file it created, there's no tag values except track ids.
I edited a tag of one file, and ran the command again, and it increased the size of the existing mbi file almost one and a half times (why?).

But still no tag values in there. Can you tell me how this works?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 01, 2016, 11:49:11 AM
the ".Master Tag Index.mbi" is just a master index file, it must not be very big anyway. are you using latest mb patch?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 01, 2016, 02:12:18 PM
this bug is fixed, but you probably will need to delete mb_tagtools.settings.xml in <appdata> folder anyway.
http://www.mediafire.com/file/7nidu1z81crt8so/mb_TagTools_2016-09-30.zip
Confirmed as fixed. Thanks very much.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2016, 05:39:43 PM
- When running "Backup tags for all tracks" command, why is it trying to create backup files in playlists folder with a strange filename starting with the first playlist in there instead of in AppData\Tag Backups folder?

- Can you display progress status while creating a backup?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 01, 2016, 06:18:17 PM
- When running "Backup tags for all tracks" command, why is it trying to create backup files in playlists folder with a strange filename starting with the first playlist in there instead of in AppData\Tag Backups folder?
probably you are using not standard playlist folder hierarchy, mb api doesn't allow to get current library name (which is a prefix for backup name) and plugin tries to get that name by enumerating all playlists and by discovering common path (plugin assumes the following playlist paths: <beginning of path>\MusicBee\<library name>\Playlists\<the rest of path>). maybe i should make this optional.

could you give me an example of this strange backup path?

- Can you display progress status while creating a backup?
i think, yes, but not sure if its easy to implement.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2016, 06:32:03 PM
<beginning of path>\MusicBee\<library name>\Playlists\<the rest of path>

The problem was "\MusicBee\". When I change the folder name for my portable MB, it saves it properly.
People use all kinds of different folder name. How about just taking a parent folder of "\Playlists\"?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 01, 2016, 06:43:15 PM
<beginning of path>\MusicBee\<library name>\Playlists\<the rest of path>

The problem was "\MusicBee\". When I change the folder name for my portable MB, it saves it properly.
People use all kinds of different folder name. How about just taking a parent folder of "\Playlists\"?
yes, i think this behavior should be optional and less "aggressive". also reread my previous post, i've edited it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2016, 06:50:19 PM
could you give me an example of this strange backup path?

"C:\Portable\MB\Library\Playlists\Recently Added.xautopf - Tag Backup 2016-10-01 20.18.15"
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2016, 08:12:31 PM
I've installed another portable MB for test, but it gives the following error for "Track Tag history" command. Strangely the command is working fine in another MB. Both are with the latest patch and plugin.

Code
10.0.14393.0 - 3.0.6118.33091 - System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at MusicBeePlugin.TagHistoryPlugin..ctor(Plugin tagToolsPluginParam, String[] trackUrlsParam, String[] trackIdsParam)
   at MusicBeePlugin.Plugin.tagHistoryEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 08:25:58 AM
I've installed another portable MB for test, but it gives the following error for "Track Tag history" command. Strangely the command is working fine in another MB. Both are with the latest patch and plugin.
it seems that there is no 'missing artwork.png' file in 'plugins' folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 08:41:45 AM
it seems that there is no 'missing artwork.png' file in 'plugins' folder.

Thanks! That fixed it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 08:45:12 AM
- If there were changes, show those tags and values only on the popup window upon clicking on the command.

(http://i.imgur.com/Afutxl3.png)


This is what I suggested. But currently it shows all tags, not just changed tags. Then the user has to read all tags to find out what's changed.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 08:58:13 AM
the ".Master Tag Index.mbi" is just a master index file, it must not be very big anyway.

I am still concerned about the file's size which keeps growing whenever a backup is made even without any changes from the previous backup. Why does it keep growing without any changes in the library?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 11:42:35 AM
- If there were changes, show those tags and values only on the popup window upon clicking on the command.

(http://i.imgur.com/Afutxl3.png)


This is what I suggested. But currently it shows all tags, not just changed tags. Then the user has to read all tags to find out what's changed.
changed tags are highlighted by blue-grey color (except for artworks).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 11:45:36 AM
the ".Master Tag Index.mbi" is just a master index file, it must not be very big anyway.

I am still concerned about the file's size which keeps growing whenever a backup is made even without any changes from the previous backup. Why does it keep growing without any changes in the library?
master index contains all track ids for every backup, so plugin can quickly find all backups witch have some data for given track. master index is used only by 'tag history' command. its safe to delete this file if you are not going to use this command.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 11:46:39 AM
new version (some bugfixes and enhancements):

http://www.mediafire.com/file/61lk6be8a7ck25k/mb_TagTools_2016-10-02.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 11:59:21 AM
btw, master index (and backup files also) can be perfectly compressed by ntfs. also master index will be reduced if you (auto)delete old backups.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 03:36:22 PM
new plugin version is available:

http://www.mediafire.com/file/61lk6be8a7ck25k/mb_TagTools_2016-10-02.zip


you will need MB latest patch:

http://musicbee.niblseed.com/V3_0/MusicBee3_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 02, 2016, 04:20:35 PM
i've never been able to reproduce all these bugs/visual glitches when using skin coloring, but i assume all these bugs are fixed now.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 04:39:29 PM
Does "Restore tags for all tracks" or "Restore tags for selected tracks" work for you? I always get this error:

Code
10.0.14393.0 - 3.0.6118.39208 - System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.BackupIndexDictionary.loadBackupAsync(Object parameters)
   at MusicBee.Plugin.#=qq8unhGCJB9SClRVZR5gNmygFqueSbCHuuBEa3Z$$56c=(Object #=q3lUtIUSd9g6WUEwABBRV_w==)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 04:44:29 PM
Preferences/Plugin/configure setting doesn't change menu location. It always revert back to the first option.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 04:50:03 PM
- If there were changes, show those tags and values only on the popup window upon clicking on the command.

(http://i.imgur.com/Afutxl3.png)


This is what I suggested. But currently it shows all tags, not just changed tags. Then the user has to read all tags to find out what's changed.
changed tags are highlighted by blue-grey color (except for artworks).

OK. Then how about showing backup files from newer to older order since "library" (current) is placed leftmost?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 04:54:25 PM
master index will be reduced if you (auto)delete old backups.

It just stays with the same (biggest) size even if all backups are deleted.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 02, 2016, 05:57:38 PM
"Copy tags to clipboard" command window now contains virtual tags and file properties as well. Can you remove them?

Edit: Never mind. I can see that could be useful just for exporting those values without pasting to another file. Even if they are selected, they won't be pasted to other files, right?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 02, 2016, 11:52:44 PM
new plugin version is available:
http://www.mediafire.com/file/61lk6be8a7ck25k/mb_TagTools_2016-10-02.zip
  • New "Backup & Restore" functionality is added.
Maybe I'm using the new 'backup & restore' function incorrectly but it doesn't do what I'm expecting it to.
Using today's plugin .dll and MB 3.0.6118 I performed a backup of all tracks. I then went to one track and deleted the comments. Then I used the 'restore tags for selected tracks' option and an error was thrown. I manually restored the comments and deleted the album name and again tried to restore. And again an error was thrown.
[/list]
Code
10/2/2016 6:38:09 PM - 6.1.7601.65536 - 3.0.6118.39208 - System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.BackupIndexDictionary.loadBackupAsync(Object parameters)
   at MusicBee.Plugin.#=qq8unhGCJB9SClRVZR5gNmygFqueSbCHuuBEa3Z$$56c=(Object #=q3lUtIUSd9g6WUEwABBRV_w==)

10/2/2016 6:40:28 PM - 6.1.7601.65536 - 3.0.6118.39208 - System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.BackupIndexDictionary.loadBackupAsync(Object parameters)
   at MusicBee.Plugin.#=qq8unhGCJB9SClRVZR5gNmygFqueSbCHuuBEa3Z$$56c=(Object #=q3lUtIUSd9g6WUEwABBRV_w==)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 03, 2016, 06:06:25 AM
Does "Restore tags for all tracks" or "Restore tags for selected tracks" work for you? I always get this error:
its fixed.

OK. Then how about showing backup files from newer to older order since "library" (current) is placed leftmost?
i'm really surprised that it doesn't work this way already. its fixed also.

It just stays with the same (biggest) size even if all backups are deleted.
i'll recheck this.

--------------

new version:

http://www.mediafire.com/file/1vofq1g4whvjatc/mb_TagTools_2016-10-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 03, 2016, 06:43:35 AM
Thanks! Working much better.

- What's the purpose of "Rename or move backups" command? Would it be a good idea to allow the user to move "some" backup files to different folders? Then master index file stays in the same location? Also there's "Move backups" command which overlaps with the previous command.

- Noticed "Restore tags for all tracks" command rewrites every file in the library, taking lots of time. Would it be possible for it to rewrite only files with changed tags?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 03, 2016, 07:10:33 AM
Preferences/Plugin/configure setting doesn't change menu location. It always revert back to the first option.
its fixed.

"Copy tags to clipboard" command window now contains virtual tags and file properties as well. Can you remove them?

Edit: Never mind. I can see that could be useful just for exporting those values without pasting to another file. Even if they are selected, they won't be pasted to other files, right?
yes, that's why i've added read-only (in mb) tags to this command.

Maybe I'm using the new 'backup & restore' function incorrectly but it doesn't do what I'm expecting it to.
Using today's plugin .dll and MB 3.0.6118 I performed a backup of all tracks. I then went to one track and deleted the comments. Then I used the 'restore tags for selected tracks' option and an error was thrown. I manually restored the comments and deleted the album name and again tried to restore. And again an error was thrown.
its fixed.

---------------------

http://www.mediafire.com/file/roh9s4o64kb03rq/mb_TagTools_2016-10-03-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 03, 2016, 07:17:04 AM
- What's the purpose of "Rename or move backups" command? Would it be a good idea to allow the user to move "some" backup files to different folders? Then master index file stays in the same location? Also there's "Move backups" command which overlaps with the previous command.
1st command allows to -rename- (or move) single backup, 2nd allows to -move- multiple backups. yes, there is some overlapping, but i can't find better solution. master index file is always stored in autobackup directory.

- Noticed "Restore tags for all tracks" command rewrites every file in the library, taking lots of time. Would it be possible for it to rewrite only files with changed tags?
i'm not sure if reading existing tags and comparing them to backuped tags will be faster than just overwriting all tags, i need to experiment first.

----------------

new plugin version:

http://www.mediafire.com/file/roh9s4o64kb03rq/mb_TagTools_2016-10-03-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 03, 2016, 07:26:28 AM
- Noticed "Restore tags for all tracks" command rewrites every file in the library, taking lots of time. Would it be possible for it to rewrite only files with changed tags?
i'm not sure if reading existing tags and comparing them to backuped tags will be faster than just overwriting all tags, i need to experiment first.

Not just time. Many people don't like their music files rewritten unless they have to.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 03, 2016, 07:34:45 AM
"Copy tags to clipboard" command window now contains virtual tags and file properties as well. Can you remove them?

Edit: Never mind. I can see that could be useful just for exporting those values without pasting to another file. Even if they are selected, they won't be pasted to other files, right?
yes, that's why i've added read-only (in mb) tags to this command.

But the tag selection window now looks too complicated. How about sorting tags grouped by its kind?

<Standard tags>
Album
Artist
...
<Custom tags>
Custom1
Custom2
...
<Virtual tags>
Virtual1
Virtual2
...
<File properties>
Bitrate
...

Also allow to tick not just each tag but each kind to multi-select all tags belonging to the ticked kind.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 03, 2016, 03:26:13 PM
master index will be reduced if you (auto)delete old backups.

It just stays with the same (biggest) size even if all backups are deleted.
yes, you are right. its fixed now.

- Noticed "Restore tags for all tracks" command rewrites every file in the library, taking lots of time. Would it be possible for it to rewrite only files with changed tags?
its done.

also some speed enhancements for 'tag history' command.

http://www.mediafire.com/file/53cgkru10l9y8q4/mb_TagTools_2016-10-03-3.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 03, 2016, 05:36:02 PM
Thanks, both issues are fixed!

- Which files are covered by tag backup feature? Of course all files in the music library. What about files in other nodes (audiobooks, videos, podcasts, inbox)?

- I'm gonna test auto-organization rule changes and "remap music folder" to a different drive to see if it can restore previous backups before re-organization. Any things I should know before?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 03, 2016, 09:52:15 PM
@boroda74-
I've still experiencing trouble with the tag backup option. This is with the 2016-10-03-3 version.

First thing is that after creating a backup and attempting to restore the tags of one track, I get a "Tag Backup 2016-10-03 x.x.x is corrupted or is not a valid MusicBee backup" error. I have created the backup three times today and each resulted in the same error when I try to restore.

Second is when I select a track and right-click > Advanced Tagging Tools > Track tag history, this  error gets thrown:
Code
MusicBee v3.0.6119.39237 (Win6.1), 3 Oct 2016 16:48:

System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at MusicBeePlugin.TagHistoryPlugin..ctor(Plugin tagToolsPluginParam, String[] trackUrlsParam, String[] trackIdsParam)
   at MusicBeePlugin.Plugin.tagHistoryEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging and Reporting Tools
Post by: Sofocl on October 04, 2016, 12:41:04 AM
boroda74 I greet!
"Backup & Restore" does not work with ".cue" files!(?)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2016, 12:51:00 PM
- Which files are covered by tag backup feature? Of course all files in the music library. What about files in other nodes (audiobooks, videos, podcasts, inbox)?
all files except for those in inbox.

- I'm gonna test auto-organization rule changes and "remap music folder" to a different drive to see if it can restore previous backups before re-organization. Any things I should know before?
i think, nothing special.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2016, 12:52:33 PM
boroda74 I greet!
"Backup & Restore" does not work with ".cue" files!(?)
plugin is using generic api call to read/write tags. i don't have any cue file. can you edit its tags in mb tag editor?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2016, 12:56:29 PM
new version:

http://www.mediafire.com/file/u54dezp824bv8bq/mb_TagTools_2016-10-04.zip

- now autobackups will be skipped if no changes in tags and/or library content were made since last manual or auto backup.
- now both 'autodelete' options will delete only autobackups of current library.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2016, 12:59:38 PM
But the tag selection window now looks too complicated. How about sorting tags grouped by its kind?

<Standard tags>
Album
Artist
...
<Custom tags>
Custom1
Custom2
...
<Virtual tags>
Virtual1
Virtual2
...
<File properties>
Bitrate
...

Also allow to tick not just each tag but each kind to multi-select all tags belonging to the ticked kind.
though not what you have asked, but i've added 10 tag sets to this command. hope it can be used more easily now:

http://www.mediafire.com/file/u54dezp824bv8bq/mb_TagTools_2016-10-04.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2016, 01:01:33 PM
Second is when I select a track and right-click > Advanced Tagging Tools > Track tag history, this  error gets thrown:
Code
MusicBee v3.0.6119.39237 (Win6.1), 3 Oct 2016 16:48:

System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at MusicBeePlugin.TagHistoryPlugin..ctor(Plugin tagToolsPluginParam, String[] trackUrlsParam, String[] trackIdsParam)
   at MusicBeePlugin.Plugin.tagHistoryEventHandler(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
suggest that you haven't unzipped 'missing artwork.png' to 'plugins' folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 04, 2016, 01:04:16 PM
@boroda74-
I've still experiencing trouble with the tag backup option. This is with the 2016-10-03-3 version.

First thing is that after creating a backup and attempting to restore the tags of one track, I get a "Tag Backup 2016-10-03 x.x.x is corrupted or is not a valid MusicBee backup" error. I have created the backup three times today and each resulted in the same error when I try to restore.
i don't have any problems with restoring. try to close mb, the delete 'mb_tagtools.settings.xml' file and 'tag backups' folder in <appdata> folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: Sofocl on October 04, 2016, 05:30:29 PM
can you edit its tags in mb tag editor?
Yes, it's ratings, and they are stored in the database only MB. Tags  "Play count" also do not work.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 04, 2016, 05:46:08 PM
- I'm gonna test auto-organization rule changes and "remap music folder" to a different drive to see if it can restore previous backups before re-organization. Any things I should know before?
i think, nothing special.

All worked fine during tests.

- now autobackups will be skipped if no changes in tags and/or library content were made since last manual or auto backup.

Working fine. How about showing "Tag autobackup skipped" message briefly on the status bar when it's skipped?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 04, 2016, 06:00:36 PM
Backup and restore tag feature is working great so far, but one aspect is different from what I expected.

I thought when it runs backup first time it would create a master db file with all tag values and then create each backup file only with changed tag values.

But currently it creates a complete tag db every time. For my test I used only 400 tracks, but each backup file amounts to 1.2 MB. This would make people with a huge library hesitate to use this feature frequently, not to mention auto-backup feature.

If it worked as I suggested the only downside would be a restore needs a backup file plus the master db file, but the advantages in sizes could be much greater. What do you think?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 04, 2016, 06:09:28 PM
But the tag selection window now looks too complicated. How about sorting tags grouped by its kind?

<Standard tags>
Album
Artist
...
<Custom tags>
Custom1
Custom2
...
<Virtual tags>
Virtual1
Virtual2
...
<File properties>
Bitrate
...

Also allow to tick not just each tag but each kind to multi-select all tags belonging to the ticked kind.
though not what you have asked, but i've added 10 tag sets to this command. hope it can be used more easily now:

Thanks! That's a useful addition!

But I'd still insist on grouping tags per kind since many users won't know which ones are tags or properties and I am confused too at which tag is standard, custom or virtual tag with all customized names. Also please make virtual tags and file properties unselected by default for copy tags to clipboard window.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 05, 2016, 02:26:21 AM
@boroda74-
I've still experiencing trouble with the tag backup option. This is with the 2016-10-03-3 version.

First thing is that after creating a backup and attempting to restore the tags of one track, I get a "Tag Backup 2016-10-03 x.x.x is corrupted or is not a valid MusicBee backup" error. I have created the backup three times today and each resulted in the same error when I try to restore.
i don't have any problems with restoring. try to close mb, the delete 'mb_tagtools.settings.xml' file and 'tag backups' folder in <appdata> folder.
I have removed mb_tagtools.setting.xml along wtih the tag backups folder. I then installed TagTools 2016-10-04 and ran 'backup tags for all tracks.' When I try to restore tags to one track either via the ToolBar drop-down or a right-click on track tag history, I still get the corrupted xml error message.
(http://i.imgur.com/CC8D6Li.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 05, 2016, 08:03:14 AM
phred, can you post the link to this backup (note that backup consists of 2 files: .xml and .mbc)?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 05, 2016, 09:49:13 AM
But I'd still insist on grouping tags per kind since many users won't know which ones are tags or properties and I am confused too at which tag is standard, custom or virtual tag with all customized names. Also please make virtual tags and file properties unselected by default for copy tags to clipboard window.
i think this approach is sufficient:

http://www.mediafire.com/file/q3vnfme659snkk4/mb_TagTools_2016-10-05.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 05, 2016, 01:12:42 PM
phred, can you post the link to this backup (note that backup consists of 2 files: .xml and .mbc)?
boroda74 -PM sent with link.
Great minds think alike. I was going to suggest that you take a look at the files, but you beat me to it. Note that the backup I sent is not the one in the screenshot. In an attempt to solve the issue I changed settings, moved the backup directory, and did some other things. But the backup is still throwing the same error.
Thanks for trying to get this going.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 05, 2016, 04:48:32 PM
one baseline backup for every library and further incremental backups:

http://www.mediafire.com/file/hmiaozzv3q6csn9/mb_TagTools_2016-10-05-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 05, 2016, 05:05:00 PM
unfortunately baseline backup files (*.bbl) always are stored in autobackup folder. but incremental backups can saved/moved to any folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: Sofocl on October 05, 2016, 05:08:14 PM
mb_TagTools_2016-10-05-2.zip
Unable to initialise this plugin:
Адресат вызова создал исключение.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 05, 2016, 05:36:00 PM
its because you have very strange characters (which are not allowed for xml) in some tags. try this plugin version, it will display some additional info about xml parsing errors (line number and problem char position in line):

http://www.mediafire.com/file/ekct1t8ss36fp29/mb_TagTools_2016-10-05-3.zip

you will need some powerful text editor (eg. notepad++) to find these problem chars because your backup file is very large. you can delete these strange chars in text editor, then import tags back to mb.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 05, 2016, 07:16:14 PM
There's a newer version available. Check the Additional Tagging Tools thread in the Plugins forum
Title: Re: Additional Tagging and Reporting Tools
Post by: Sofocl on October 05, 2016, 07:30:21 PM
There's a newer version available. Check the Additional Tagging Tools thread in the Plugins forum
mb_TagTools_2016-10-05-3.zip
The same thing
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 05, 2016, 11:44:20 PM
its because you have very strange characters (which are not allowed for xml) in some tags. try this plugin version, it will display some additional info about xml parsing errors (line number and problem char position in line):

http://www.mediafire.com/file/ekct1t8ss36fp29/mb_TagTools_2016-10-05-3.zip

you will need some powerful text editor (eg. notepad++) to find these problem chars because your backup file is very large. you can delete these strange chars in text editor, then import tags back to mb.
I think it's time for me to stop trying to use the Tag Backup feature of the Advanced Tagging Tools plugin.

Using the updated dll I ran a backup and it created a 60mb file called phred=Baseline.bbl. I opened in in Notepad++ and found lots of characters that look like little rectangles but when copied and pasted into a next text doc show as question marks. I certainly haven't looked at every track, but it appears that this character is in every set of lyrics I've looked at.  From what you've said, I'm assuming this is the character that's corrupting the backup file. There's just no way I'm going to edit the lyrics of 15,000+ tracks.

Here's a screenshot of one set of lyrics...
(http://i.imgur.com/wzQ3Lsu.jpg)

I do have one other question regarding the ASR Presets - I extracted the zip file to my Plugins folder. The result was the four language folders and the ASR Presets folder, along with the png and dll. But after enabling and configuring the plugin, there's now a second ASR Presents folder in my AppData folder. Should there be two? And if not, which one should be deleted?

Thanks for all your help on this. At least the Additional Tagging Tools (still) work fine for me.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 06, 2016, 09:46:23 AM
nothing was changed significantly. try to close mb and delete <appdata>\mb_tagtools.settings.xml
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 06, 2016, 11:52:40 AM
Doesn't work for me either. When trying to enable it, keep getting this message:

(http://i.imgur.com/aJ5p6fo.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 06, 2016, 04:57:49 PM
I think it's time for me to stop trying to use the Tag Backup feature of the Advanced Tagging Tools plugin.
its up to you, but could you try this version (this version tries to escape all illegal xml chars, its very funny that standard .net xml serializer/deserializer can write files, which it cant read)?

http://www.mediafire.com/file/lwm2u2b6ldum6nq/mb_TagTools_2016-10-06.zip

I do have one other question regarding the ASR Presets - I extracted the zip file to my Plugins folder. The result was the four language folders and the ASR Presets folder, along with the png and dll. But after enabling and configuring the plugin, there's now a second ASR Presents folder in my AppData folder. Should there be two? And if not, which one should be deleted?
its because installation instructions to copy 'asr presets' folder to <appdata> folder would be too complicated. 'asr presets' folder in 'plugins' folder is used only for importing presets and is not needed for plugin functionality.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 06, 2016, 06:48:16 PM
I think it's time for me to stop trying to use the Tag Backup feature of the Advanced Tagging Tools plugin.
its up to you, but could you try this version (this version tries to escape all illegal xml chars, its very funny that standard .net xml serializer/deserializer can write files, which it cant read)?
To be honest, I'd rather have it working, but not at the expense of trying to edit that character out of all my tracks. As for .net writing but not reading I consider that Microsoft being Microsoft. :-)

Quote
http://www.mediafire.com/file/lwm2u2b6ldum6nq/mb_TagTools_2016-10-06.zip
I'll test today's version in a couple of hours and report back.

Quote from: phred date=1475707460 link=topic=3833.msg
118527#msg118527
I do have one other question regarding the ASR Presets - I extracted the zip file to my Plugins folder. The result was the four language folders and the ASR Presets folder, along with the png and dll. But after enabling and configuring the plugin, there's now a second ASR Presents folder in my AppData folder. Should there be two? And if not, which one should be deleted?
its because installation instructions to copy 'asr presets' folder to <appdata> folder would be too complicated. 'asr presets' folder in 'plugins' folder is used only for importing presets and is not needed for plugin functionality.
[/quote]
Ahhh - very clever.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 06, 2016, 07:18:56 PM
Found a workaround to avoid the error.

- Install the last working version (mb_TagTools_2016-10-04.zip) and enable it to create <AppData>\mb_TagTools.Settings.xml file.
- Without deleting the settings file, overwrite the dll file only with the latest version.

nothing was changed significantly. try to close mb and delete <appdata>\mb_tagtools.settings.xml

Must have been some changes in the code since the 10-05 version that interferes with the initializing process. It creates a zero-byte settings file.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 06, 2016, 07:33:50 PM
one baseline backup for every library and further incremental backups

Tried this (with 10-06 version) and indeed it now creates incremental backups, saving space considerably. Here are some issues.

- Track tag history is not working. It shows current tags only without showing any tags from the backup files.
- When creating a backup, it always pause at "99%" for a long time. First I thought it crashed but it finally worked. So probably it was comparing tags to write changed tags only. How about changing the message not to give a false impression?
- Restoring worked fine. But it was much slower than before. Hope you could speed up the backup and restore process.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 06, 2016, 11:11:33 PM
I think it's time for me to stop trying to use the Tag Backup feature of the Advanced Tagging Tools plugin.
its up to you, but could you try this version (this version tries to escape all illegal xml chars, its very funny that standard .net xml serializer/deserializer can write files, which it cant read)?

http://www.mediafire.com/file/lwm2u2b6ldum6nq/mb_TagTools_2016-10-06.zip
PROGRESS!!!  But still not working as I expected it to.  Full backup of all track tags was completed. And I can restore without getting the 'corrupted xml' error message. The size of yesterday's baseline was about 60mb and today's is about 90mb. I looked at the baseline file with Notepad++ and see why the increase in file size. Lots of data between each word in the lyrics and in other places. But I assume this is due to the change you made to have it ignore the characters previously written that caused it to be corrupt.
(http://i.imgur.com/mVuFkBM.jpg)

After the manual (full) backup was complete I set the auto-backup to run every thirty minutes. It runs, and the status bar shows that it completed, but I can't find the new backup even though it's set to go in the same directory as the first one. I believe this is what redwing is referring to in his first item in this thread: http://getmusicbee.com/forum/index.php?topic=18426.msg118558#msg118558
I also experienced the second item he mentioned - seemingly stuck at 99% during the auto-backup. But not during the initial one. I also confirm redwing's third item, but I attribute that to the 18,000+ tracks I have.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 08, 2016, 05:51:05 PM
But still not working as I expected it to.  Full backup of all track tags was completed. And I can restore without getting the 'corrupted xml' error message. The size of yesterday's baseline was about 60mb and today's is about 90mb. I looked at the baseline file with Notepad++ and see why the increase in file size. Lots of data between each word in the lyrics and in other places. But I assume this is due to the change you made to have it ignore the characters previously written that caused it to be corrupt.
i'm not sure what i can do with it. trying to escape all illegal xml chars manually would be too complicated and using standard "escaper" produces very long strings,
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 08, 2016, 06:28:42 PM
i'm not sure what i can do with it. trying to escape all illegal xml chars manually would be too complicated and using standard "escaper" produces very long strings,
That's fine. I can live with the file that way it's being generated now. Hell, drive space is fairly cheap these days. :-)

After the manual (full) backup was complete I set the auto-backup to run every thirty minutes. It runs, and the status bar shows that it completed, but I can't find the new backup even though it's set to go in the same directory as the first one. I believe this is what redwing is referring to in his first item in this thread: http://getmusicbee.com/forum/index.php?topic=18426.msg118558#msg118558
I also experienced the second item he mentioned - seemingly stuck at 99% during the auto-backup. But not during the initial one. I also confirm redwing's third item, but I attribute that to the 18,000+ tracks I have.
It's these items I'm still concerned about. Especially the auto-backup seemingly running, but not being saved anyplace.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on October 08, 2016, 06:32:46 PM
@boroda74, have you considered using a binary stream writer rather than xml?
i expect it would be faster as well
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 09, 2016, 02:13:22 AM
@boroda74- a couple of weeks ago I asked if you could make the windows persistent in their location and you did. But over the past few versions, it stopped. The behavior now is that all Additional Tagging Tools windows open towards the top left of the screen. I have to drag them to where I want each time I open one. Please make them persistent again. Many thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 09, 2016, 08:50:10 AM
I set the auto-backup to run every thirty minutes. It runs, and the status bar shows that it completed, but I can't find the new backup even though it's set to go in the same directory as the first one.

Did you make any tag changes after the initial backup? If not, it cancels writing a backup after comparing tags.

18,000+ tracks I have.

For my test with 400 tracks, it takes 40 secs (mostly for comparing tags at 99%) to create a backup. Does it take 30 minutes for you as you have 45 times more tracks than my test library?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 09, 2016, 01:40:31 PM
I set the auto-backup to run every thirty minutes. It runs, and the status bar shows that it completed, but I can't find the new backup even though it's set to go in the same directory as the first one.

Did you make any tag changes after the initial backup? If not, it cancels writing a backup after comparing tags.

Ahhh! Good info. At this point I can't remember if I changed any tracks, but I certainly have now since the last full manual backup. So I have turned auto-backup on again

18,000+ tracks I have.

For my test with 400 tracks, it takes 40 secs (mostly for comparing tags at 99%) to create a backup. Does it take 30 minutes for you as you have 45 times more tracks than my test library?
Yes, it takes between 30-45 minutes, so that's within your parameter.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 09, 2016, 04:04:16 PM
I set the auto-backup to run every thirty minutes. It runs, and the status bar shows that it completed, but I can't find the new backup even though it's set to go in the same directory as the first one.

Did you make any tag changes after the initial backup? If not, it cancels writing a backup after comparing tags.
Well, I'm not so sure about this. I enabled the auto-backup to run every 30 minutes. I deleted the comments from one track. More than two hours later and there is no new file in the Tag Backups directory. So I'm not convinced the auto-backup is working.

So even with only one backup set, I selected 'restore tags for selected tracks' and while the comments were indeed restored to the track, MB threw this error:
Code
10/9/2016 11:06:21 AM - 6.1.7601.65536 - 3.0.6125.34367 - System.ArgumentException: Controls created on one thread cannot be parented to a control on a different thread.
   at System.Windows.Forms.Control.ControlCollection.Add(Control value)
   at System.Windows.Forms.Form.ControlCollection.Add(Control value)
   at #=qBOEK$ER4a7TnOPwZ103epIzRNWPxfx0GK6J4iWlfi98=.#=qzSaq0kRSdQoKZJeJKYt_4CFft_Wob2CaK3xacXyUjUI=(Int32 #=q3Xw_NdCitgt0Mge4rCimGw==, Boolean #=q33kiPxCuE4eiZw3OtQR74iEulWCC72rpIZ5b$$ub$qI=)
   at #=qBOEK$ER4a7TnOPwZ103epIzRNWPxfx0GK6J4iWlfi98=.#=qjZG6tKHp0Ergv$9dL8N5zmrzQWmurqaC2Fp6i3JThS0=(Size #=qgIKj3zaEwqigJfU01kP2QQ==)
   at #=qBOEK$ER4a7TnOPwZ103epIzRNWPxfx0GK6J4iWlfi98=.#=qBBBaYGkNZHZSzFClXkskJQ1xw0gJNfe7YhU$t29uFjg=(Int32 #=qCs5O3$8qTUQyfQeo0ZPCcQ==)
   at #=qT9pBK1lHIOFwzvZ5WIEjd9FphSqYiTCOzj5Tun6CFtg=.#=qqoXcZu8U7GAyGFW2H4rMWS36zA1HuUvszzSxHJ2cf$s=()
   at #=qT9pBK1lHIOFwzvZ5WIEjd9FphSqYiTCOzj5Tun6CFtg=.#=qkbLE$1YlMTNfoiT9dWv1sg==(IList`1 #=qQ_6ajPRqisg15ZNLLI0COg==, TagCode #=qcnvAr5ZTXGdrdgtHoEy4DQ==)
   at MusicBee.MusicBeeMain.#=qnlPP3KiEfK9IuUYasSISEw==(IList`1 #=qiFPjpRe6xxZcV58gGBquYg==, TagCode #=q6sl_tjMRXPQnHMN0bssjnw==, Boolean #=qfuwQc8Toe6LqIbmt9vul413FpyaMoZkCddLrgthbAMY=)
   at MusicBee.MusicBeeApplication.#=qGBsEqXZfXCfWdJei8AXviKOHHEpsD6sL7gMx3TVQFro=(IList`1 #=q4TxsSZ6J31JybnmsqeJrIA==, TagCode #=qrsTQtuU8N_zRSyC6FmAuYQ==, Boolean #=qdVzured5vCIVI5jgnZoB4JI2gwLlRUFOXKlaV_4algk=)
   at MusicBee.Plugin.#=qQrlAaJdWaDx8TDwyNIBvsrqg0iixll$vwMSgOWiPas8=()
   at MusicBeePlugin.Plugin.RefreshPanels(Boolean immediateRefresh)
   at MusicBeePlugin.Plugin.CommitTagsToFile(String sourceFileUrl, Boolean ignoreTagsChanged, Boolean updateOnlyChangedTags)
   at MusicBeePlugin.BackupIndexDictionary.loadBackup(String backupName, String statusbarText, Boolean restoreForEntireLibrary)
   at MusicBeePlugin.BackupIndexDictionary.loadBackupAsync(Object parameters)
   at MusicBee.Plugin.#=q5UOfiqI70ZvTPMz0$OWc_84YhXktRdorwAG5039v1G8=(Object #=qLChswvFgx8WMuu4zMIToWg==)