getmusicbee.com

MusicBee & Add-Ons => Customizations => 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
NOTE

If you are familiar with plugin quick update process, you can always download latest plugin version here (https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file) (NOTE: this latest version can require the latest version of MusicBee which sometimes may be available as a beta). Copy the file "mb_TagTools.dll" from the archive "mb_TagTools_latest.zip" to MusicBee "Plugins" folder, and overwrite the existing file.

NOTE

Pay attention to tool tips over buttons/fields in plugin windows.

-------------------------------------------------------------------------------------------------------------------------------

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 a music file from another computer with different regional settings).

7. Reencode Tags

Command to re-encode all tags of selected tracks at ones. Cuesheets are supported.

8. Advanced search and replace
9. Calculate average album ratings

Command averages all the ratings of the individual tracks on the album, writing the 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.

10. Plugin has the option to store "last skipped date/time" in any writable tag (e.g. some custom tag)

Go to MusicBee menu> Edit> Preferences> Plugins> Additional Tagging Tools> Configure. Click the button "Save last skipped date..." at the bottom of plugin settings window.

Plugin strictly follows MusicBee convention of what is "skipped track".

To define date type of custom tag, open MusicBee menu> Edit> Preferences> Tags (1)> Define New Tags> Configure Fields. Find "Custom1" tag (or some other custom tag), change type to "Date".

See here screenshot of this setting (https://i.imgur.com/C1gPwaK.png)

11. Backup & Restore

Backup & restore commands allow to (auto)backup tags of all tracks in your library and restore them. First create full backup manually. You can do manual or auto incremental backups after this.


And much more

Full description and download link (https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/)

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==)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 09, 2016, 05:04:11 PM
I just tested auto-backup feature, and it's working fine for me.

Yes, it takes between 30-45 minutes, so that's within your parameter.

I enabled the auto-backup to run every 30 minutes.

Maybe that's the problem. Try increasing the interval to 1 hour.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on October 09, 2016, 05:05:04 PM
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:
thats something i will need to fix on the MB side

edit:
the usual v3 link is updated with the fix
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 13, 2016, 03:38:52 PM
Doesn't work for me either. When trying to enable it, keep getting this message:

(http://i.imgur.com/aJ5p6fo.png)
its fixed for the next update.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 13, 2016, 04:33:47 PM
- Track tag history is not working. It shows current tags only without showing any tags from the backup files.
its fixed also for next update

- 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?
yes, its comparing tags. i'll try to write some text about this in statusbar.

- Restoring worked fine. But it was much slower than before. Hope you could speed up the backup and restore process.
cant think how to speed up saving, but restoring might work faster for large libraries (> 100-200 tracks) now.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 13, 2016, 05:13:20 PM
http://www.mediafire.com/file/7412sqnmmiz7g81/mb_TagTools_2016-10-13.zip

also incremental backups are more compact now (now only changed tags are actually saved).

still to do: add new command "delete all backups of current library and create new baseline".

-------

edit:

new version is incompatible with previous backups, so just delete "<appdata\tag backups>" folder before upgrading.

also auto-backups will be skipped now if there are no changes comparing to baseline (even if you changed some tags (to baseline tags) since last incremental backup).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 13, 2016, 05:17:17 PM
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
autobackups will be skipped if there are no changes in library tags or content since last auto- or manual-backup.

some bugfixes:

http://www.mediafire.com/file/7412sqnmmiz7g81/mb_TagTools_2016-10-13.zip

new version is incompatible with previous backups, so just delete "<appdata\tag backups>" folder before upgrading.


Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 13, 2016, 06:45:47 PM
Thanks! The bugs are fixed.

But after testing incremental backups I think this is almost unusable for me. It takes too much time and consumes lots of system resources (mostly CPU) while comparing tags. Now tag history command too takes some time and uses up CPU for loading backup files and comparing tags. It repeats it for each track. I am testing this only with 400 tracks and I don't think I can bear this long and huge usage of CPU with a much bigger library.

I just tested 10-04 version again, which does a full backup each time, and it felt much usable though it can use up more spaces.

Maybe the plugin could offer two options so that users could test and choose one that's working better for them.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 14, 2016, 06:23:56 AM
Maybe the plugin could offer two options so that users could test and choose one that's working better for them.
its possible, but 1st i'll try to optimize performance. unfortunately i can test on large library only saving backups and restoring only on small test library. i hope performance can enhanced. as for cpu usage, background task should be launched at lowest priority (so use only free resources), so could you confirm that high cpu usage is the real problem for you?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 14, 2016, 07:34:25 AM
With 400 tracks, one backup takes about 40-50 secs and uses about 30% of CPU. phred said it takes 30-45 mins to backup his 18000 tracks. Probably he gets the similar CPU usage during that time. This means if he sets up to auto-backup every hour, this plugin alone consumes 30% of CPU all the time.

Track tag history command too takes lots of resources for comparing tags out of multiple backup files. Sometimes I get "Not Responding" error message while it's loading. But that happened only with 4 backup files. What would happen with 40 or 400 backups?

I don't think managing background priority can resolve this issue. It needs to use far less CPU with much more efficient algorithm, but I'm not sure it's possible.
Title: Re: Additional Tagging and Reporting Tools
Post by: Duke9700 on October 14, 2016, 04:49:46 PM
Hoping I'm just overlooking something simple but I recently went to use AT&RT and it wasn't anywhere to be found. None of the options show up in the Tagging menu and the settings do not appear in the Plugins area of Preferences. I did reinstall both MB and AT&RT but it still does not appear. I'm not sure when it disappeared so it may have been gone for a while.

I'm using the latest versions of each (MB v3.0.6129 and AT&RT 2016-10-13).

Any thoughts? Are there perhaps some tagging settings I could strip out of one of the ini files that might be interfering? I didn't see others mentioning this (except for a similar problem one user had on the 1st page of this thread but that was years ago) so I won't take offense of this was caused by a defective user (I have a thick enough skin!).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 14, 2016, 05:06:15 PM
None of the options show up in the Tagging menu and the settings do not appear in the Plugins area of Preferences.

Make sure you have copied mb_TagTools.dll file under Plugins folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 14, 2016, 05:30:27 PM
None of the options show up in the Tagging menu and the settings do not appear in the Plugins area of Preferences.

Make sure you have copied mb_TagTools.dll file under Plugins folder.
And once you've confirmed the dll is in the Plugins folder, exit MB and restart it. Then go to Plugins preferences and enable the ATRT plugin. (You may have to exit and restart after enabling also - I can't remember.)  Only then will it show up under Tools > Additional Tagging Tools
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 14, 2016, 05:37:04 PM
I haven't checked CPU usage, but with the latest version, starting over from scratch per boroda74's instructions, it's now taking about 45 minutes to backup 18,000 tracks. I then deleted some tags from three tracks and attempted a restore. That took about 20-25 minutes.
My auto-backup is now set for 90 minutes and since I just launched MB for the first time since the change, I'll report back later today about the auto-backup. There are about 50 new tracks added to the library since the new, full backup yesterday.

@boroda74- what about Steven's suggestion for a possible speed up? http://getmusicbee.com/forum/index.php?topic=3833.msg118611#msg118611
Title: Re: Additional Tagging and Reporting Tools
Post by: Duke9700 on October 14, 2016, 05:44:10 PM
Make sure you have copied mb_TagTools.dll file under Plugins folder.

Yep - the problem was my not being able to follow instructions. You'd think after decades in IT I'd figure it out! I was happily dumping everything into the MusicBee folder and not the Plugins subfolder.

I'll go stand in the corner for my timeout...
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on October 14, 2016, 06:13:13 PM
@boroda74- what about Steven's suggestion for a possible speed up? http://getmusicbee.com/forum/index.php?topic=3833.msg118611#msg118611
that comment was mostly for the issues around saving and retrieving non-xml compliant tag data. The speed improvement wouldnt be much.
I have PM'ed boroda74 with a suggestion for an API enhancement that might help but that wouldnt be until v3.1
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 14, 2016, 11:38:50 PM
@boroda74 - can we get persistent windows in the latest ATRT please?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 15, 2016, 11:34:24 AM
Steven, answering your pm here, yes, probably it would be great enhancement to bulk save/read all tags of multiple tracks at once.

redwing, what do you think about this version?:

http://www.mediafire.com/file/611of07fk25fk5z/mb_TagTools_2016-10-15.zip

of course, its not compatible with previous backups again.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 15, 2016, 11:39:55 AM
phred, i'm just forgetting to uncomment this part of code (which remembers window sizes/positions). this definitely will be fixed in final version. 
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 15, 2016, 01:27:07 PM
phred, i'm just forgetting to uncomment this part of code (which remembers window sizes/positions). this definitely will be fixed in final version.
Great - thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 15, 2016, 01:37:49 PM
redwing, what do you think about this version?:

Great improvement!
Now creating a backup of 400 tracks takes about 7-8 secs. And tag history command works very fast. Restoring tags is a lot faster than backing up.
What's changed? Any downsides compared to the previous versions?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 15, 2016, 03:37:24 PM
Great improvement!
Now creating a backup of 400 tracks takes about 7-8 secs. And tag history command works very fast. Restoring tags is a lot faster than backing up.
What's changed? Any downsides compared to the previous versions?
Hmmm ... I guess this is a case of 'different strokes for different folks.' Testing a full backup on my 18,000+ tracks took almost one hour and 15 minutes. About 30 minutes longer than the previous version.

Tag history command is indeed faster. As is restoring tags for selected tracks is much much faster.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 15, 2016, 03:46:25 PM
redwing, what do you think about this version?:

Great improvement!
Now creating a backup of 400 tracks takes about 7-8 secs. And tag history command works very fast. Restoring tags is a lot faster than backing up.
What's changed? Any downsides compared to the previous versions?
no, i just haven't been sure if new solution is acceptable. actually i was going to write backup/restore this way initially, but had thought that source code would be too complicated. in fact new code is more compact, more efficient and more readable than previous one.

------

phred, could you post timings for backup/restore with new version (you have very large library and plugin speed is not linear respective the size of library).

-------

edit:
sorry, phred, you already answered my question.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 15, 2016, 04:02:01 PM
Hmmm ... I guess this is a case of 'different strokes for different folks.' Testing a full backup on my 18,000+ tracks took almost one hour and 15 minutes. About 30 minutes longer than the previous version.
phred, i think you write about initial (first, baseline) backup. what about further (incremental) backups?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 15, 2016, 05:29:00 PM
Just tested with a 12,000 tracks library.
The initial backup took 5 mins and each incremental backup took 12 mins (5 mins for writing + 7 mins for comparing).
But tag history command is not working properly. First time it worked with a brief "Not Responding" message but then the right click menu for the command disappeared. After relaunching MB, now it throws the following error:

Code
10.0.14393.0 - 3.0.6130.40302 - System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.TagHistoryPlugin.fillTable(String folder, Boolean includeSubfolders, Int32 maxBackupCount, Int32 trackIndex, Boolean reuseCache)
   at MusicBeePlugin.TagHistoryPlugin.rereadButton_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)

It worked fine when testing with 400 tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 15, 2016, 05:33:38 PM
Testing a full backup on my 18,000+ tracks took almost one hour and 15 minutes. About 30 minutes longer than the previous version.

Try again after completely deleting tag backups folder and the plugin's settings file in appdata folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 15, 2016, 05:41:42 PM
When creating an incremental backup, can't it do comparing first and then write only changed tags? Then it could save about a half of the time.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 15, 2016, 07:24:11 PM
Testing a full backup on my 18,000+ tracks took almost one hour and 15 minutes. About 30 minutes longer than the previous version.

Try again after completely deleting tag backups folder and the plugin's settings file in appdata folder.
I had deleted the backups folder before trying a full backup today, but not the settings file. So now I've deleted them both and started another full tag backup. Will report back later today.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 15, 2016, 08:13:39 PM
Testing a full backup on my 18,000+ tracks took almost one hour and 15 minutes. About 30 minutes longer than the previous version.

Try again after completely deleting tag backups folder and the plugin's settings file in appdata folder.
I had deleted the backups folder before trying a full backup today, but not the settings file. So now I've deleted them both and started another full tag backup. Will report back later today.
Full tag backup took just under 50 minutes. So that's much better than earlier today. Only thing that I changed was the deletion of the settings file.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 16, 2016, 11:40:34 PM
I have autobackup set for 90 minutes. I have changed some tags after the full back and before the autobackup. This error is being thrown
Code
10/16/2016 6:03:56 PM - 6.1.7601.65536 - 3.0.6130.40302 - System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.Plugin.regularAutobackup(Object state)
   at System.Threading.TimerQueueTimer.CallCallbackInContext(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.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()
   at System.Threading.TimerQueue.AppDomainTimerCallback()
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 19, 2016, 02:38:15 AM
I have autobackup set for 90 minutes. I have changed some tags after the full back and before the autobackup. This error is being thrown
Code
10/16/2016 6:03:56 PM - 6.1.7601.65536 - 3.0.6130.40302 - System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.Plugin.regularAutobackup(Object state)
   at System.Threading.TimerQueueTimer.CallCallbackInContext(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.TimerQueueTimer.CallCallback()
   at System.Threading.TimerQueueTimer.Fire()
   at System.Threading.TimerQueue.FireNextTimers()
   at System.Threading.TimerQueue.AppDomainTimerCallback()
New tracks and new tags have been added since the last (only) full backup. Auto-backups do not run. Or if they do, nothing has changed in the Tag Backups folder. The error above seems to happen when the plugin is attempting to run the auto-backup.

Now, when I right-click on a new track that wasn't in the original, full backup, and then select 'tag history' this error is thrown. Perhaps it's because the track doesn't exist in the full backup. However, I am also getting this error when trying to see the tag history for a track that was part of the original backup.
Code
MusicBee v3.0.6135.34867 (Win6.1), 18 Oct 2016 21:35:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.TagHistoryPlugin.fillTable(String folder, Boolean includeSubfolders, Int32 maxBackupCount, Int32 trackIndex, Boolean reuseCache)
   at MusicBeePlugin.TagHistoryPlugin.TagHistoryPlugin_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()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 19, 2016, 11:40:02 AM
phred, redwing, i'll try to experiment myself first, because right now i'm not sure what to log in debug version. null reference exception can't depend on library size, its something else.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 19, 2016, 12:06:56 PM
phred, auto- or manual-backup won't be actually started until any previous backup is completed, but should see some info in statusbar about backup in progress.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 19, 2016, 01:19:24 PM
phred, auto- or manual-backup won't be actually started until any previous backup is completed, but should see some info in statusbar about backup in progress.
Yes, I understand that. If a full backup takes about 60 minutes, and I have auto-backup set for 90, there shouldn't be an issue, correct? And if I change tags, or add new tagged tracks, and leave MB open, auto-backup should run. I have seen an indication of auto-backup running in the statusbar, but when complete there's no new file and checking the error log shows the first of the two errors I posted yesterday.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 19, 2016, 04:13:48 PM
hope this error with null reference is fixed now. also 1 new option for backup settings and backups must be smaller now (maybe even faster, not sure).

http://www.mediafire.com/file/darerwuapbiwbfm/mb_TagTools_2016-10-19.zip

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 19, 2016, 04:19:07 PM
forgot to mention: new version is not compatible with old backups.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 19, 2016, 04:34:20 PM
hope this error with null reference is fixed now. also 1 new option for backup settings and backups must be smaller now (maybe even faster, not sure).

http://www.mediafire.com/file/darerwuapbiwbfm/mb_TagTools_2016-10-19.zip
Great! Downloaded and installed. Will be starting backup shortly and will report back later today.

forgot to mention: new version is not compatible with old backups.
Good to know, but I always remove previous backups (and settings) with each new version you issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 19, 2016, 05:30:19 PM
hope this error with null reference is fixed now. also 1 new option for backup settings and backups must be smaller now (maybe even faster, not sure).
Encouraging results! Previously just over 18,000 tracks took just over 60 minutes for the initial backup. Now, with just over 19,000 tracks the initial backup took just under 50 minutes. IIRC, the previous full backup (18k+ tracks) was over 200mb in size which this new one is 128mb. Also, selecting a track and evoking the 'tag history' not only doesn't throw an error, but it completes very quickly.

I've added some new tracks and am now waiting 90 minutes for the auto-backup. I noticed the new option to not skip auto-backup and have enabled it.

I'll keep an eye out for the 'null reference error.'

EDIT: Also no error thrown when looking for 'tag history' of a newly-added (not yet backed up) track. All-in-all this latest version is looking much better.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 19, 2016, 06:50:15 PM
phred, just a note: all backup files can be very efficiently compressed by ntfs (up to 4 times in my case), but i'm not sure about cpu usage and backup/restore speed for large libraries.

-----------------

new plugin version 4.18 (2016-10-19-2). i've added new command 'create new baseline of current library'. there will be info/warning window displayed. also window sizes/positions remembering is turned on now again.

this version will be new stable release if (edit: NO) new bugs are found:

http://www.mediafire.com/file/3wnrs9g14agy26w/mb_TagTools_2016-10-19-2.zip

and latest source code:

http://www.mediafire.com/file/rqhjf2em3qmewt7/TagTools_2016-10-19_20.40.39.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 19, 2016, 06:59:32 PM
phred, just a note: all backup files can be very efficiently compressed by ntfs (up to 4 times in my case), but i'm not sure about cpu usage and backup/restore speed for large libraries.
I'm not really concerned with file size as I've got many TBs of space. I brought it up because you stated file sizes will be smaller, so I was confirming.  :-)

Quote
new plugin version 4.18 (2016-10-19-2). i've added new command 'create new baseline of current library'. there will be info/warning window displayed. also window sizes/positions remembering is turned on now again.
All sounds good. Thanks for adding this feature to what I think is the most downloaded plugin for MB.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 19, 2016, 07:47:47 PM
Just tested the first version with a 12,000 tracks library again. Backup time and CPU usage were almost the same as the previous version - the initial backup took 5 mins and each incremental backup (either manual or auto) took 12 mins (5 mins for writing + 7 mins for comparing). CPU usage was always 7 to 8%, never exceeding 9%.
The problem is tag history command. It no longer throws the error, but it doesn't work smoothly. It takes noticeably longer time to load whenever a backup is added, and consumes CPU over 30% percent. Only with three backups, it takes 6-7 secs to load and the app window looks almost not responding during that time. Not sure it could handle more than 10 backups reliably.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 20, 2016, 01:41:39 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).

Still I think it would be much useful if the tag history table shows only backups with any changed tags (instead of all backups) and changed tags only (instead of all tags). The more backups you have, the harder it gets to browse what tags have changed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 21, 2016, 04:26:42 PM
Just tested the first version with a 12,000 tracks library again. Backup time and CPU usage were almost the same as the previous version - the initial backup took 5 mins and each incremental backup (either manual or auto) took 12 mins (5 mins for writing + 7 mins for comparing). CPU usage was always 7 to 8%, never exceeding 9%.
The problem is tag history command. It no longer throws the error, but it doesn't work smoothly. It takes noticeably longer time to load whenever a backup is added, and consumes CPU over 30% percent. Only with three backups, it takes 6-7 secs to load and the app window looks almost not responding during that time. Not sure it could handle more than 10 backups reliably.
i'm afraid i can't optimize speed more.

Still I think it would be much useful if the tag history table shows only backups with any changed tags (instead of all backups) and changed tags only (instead of all tags). The more backups you have, the harder it gets to browse what tags have changed.
i think its not too difficult. maybe in a couple of days.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 21, 2016, 08:32:40 PM
I'm not sure I understand why the tag history command uses so much CPU. Now each backup saves changed tags only and thus in a very small size. Then loading those backups and listing those changed tags shouldn't require much operations even though there's a difference in that backup checks against a baseline file and tag history against current tags. At least the scope of changed tags and changed files to handle should be very small because they had to be recorded in one of incremental backups.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on October 27, 2016, 01:19:31 PM
you are right. maybe 'tag history' can significantly optimized now. at the moment baseline is restored for *every* backup included in command window. thanks for the tip.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on October 27, 2016, 09:48:16 PM
anyone using v3.1, should redownload as i forgot to update one thing that would affect the tag backup plugin
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2016, 09:21:46 AM
new version:

http://www.mediafire.com/file/5rx4f21zcp1wk7n/mb_NowPlayingToExternalFiles_2015-09-06.zip

* overall performance is better, but i'm not sure if the difference is noticeable.
* tag history command loads baseline backup only once now.

source code:

http://www.mediafire.com/file/890wv21zk9myzd6/TagTools_2016-11-03_11.03.28.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 03, 2016, 09:22:43 AM
new version:

http://www.mediafire.com/file/5rx4f21zcp1wk7n/mb_NowPlayingToExternalFiles_2015-09-06.zip

* overall performance is better, but i'm not sure if the difference is noticeable.
* tag history command loads baseline backup only once now.

source code:

http://www.mediafire.com/file/890wv21zk9myzd6/TagTools_2016-11-03_11.03.28.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 03, 2016, 12:29:38 PM
new version:

http://www.mediafire.com/file/5rx4f21zcp1wk7n/mb_NowPlayingToExternalFiles_2015-09-06.zip
@boroda74- you're linking to one of your other plugins.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 03, 2016, 02:11:10 PM
Tested the new version included in the source code archive file.
For backing up, there's not much differences compared with previous versions. But I noticed while comparing tags with baseline it uses 20 to 30% of CPU and about 1.4 GB of memory. MB is almost unusable during the task - mouse and keyboard lag and visual glitches in UI.
Tag history command too shows not much improvement in terms of CPU usage. Still I get "Not Responding" message while it's loading just two backups.
Thanks for making layout changes so that it now shows changed backups and changed tags only. But there are some bugs.

(http://i.imgur.com/8ry1GL0.png)

- The name of each backup is displayed incorrectly as the timestamp of the first backup file for every backup. Tooltip shows a different (correct) timestamp for each.

- It draws three lines for the same field (play count) maybe because three backups have a different value from that of library. But just one line can deliver the same information. If a cell has the same value as library, it can be left blank.

Also, tag history command sometimes didn't work with the following error. Restarting MB sorted out.

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.BackupType.Load(String fileName, String backupFileExtension)
   at MusicBeePlugin.TagHistoryPlugin.fillTable(String folder, Boolean includeSubfolders, Int32 maxBackupCount, Int32 trackIndex, Boolean reuseCache)
   at MusicBeePlugin.TagHistoryPlugin.TagHistoryPlugin_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()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 04, 2016, 10:34:50 AM
redwing, thanks for bug reports, will look into it. as for cpu usage, only tag history can be affected, because all other functionality is very slightly improved and definitely improved (there are only couple of lines changed outside tag history), so maybe its some other reasons?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 04, 2016, 10:38:11 AM
you are right, sorry for that. correct link:

http://www.mediafire.com/file/3juwddn1bp5ybmt/mb_TagTools_2016-11-03.zip

edit: mediafire uses flash and flash works very strangely in my browser (cyberfox for 64-bit intel).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 04, 2016, 10:39:58 AM
redwing, if you haven't recompiled plugin, then i'm not sure what binaries are contained in source project. correct link to compiled plugin:

http://www.mediafire.com/file/3juwddn1bp5ybmt/mb_TagTools_2016-11-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 04, 2016, 10:55:49 AM
Yeah, that's the one I tested. You have included it in the source project file (\obj\release\).

The high CPU usage while comparing tags with baseline might be an existing behavior that I happened to notice this time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 05, 2016, 11:54:36 AM
various bugfixes:

http://www.mediafire.com/file/rc6lyaay185dc05/mb_TagTools_2016-11-05.zip

source:

http://www.mediafire.com/file/rmsj1arbxa7vnnx/TagTools_2016-11-05_13.49.53.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 05, 2016, 01:11:25 PM
various bugfixes:

http://www.mediafire.com/file/rc6lyaay185dc05/mb_TagTools_2016-11-05.zip
Does this new version take care of this error?
Code
MusicBee v3.1.6152.39912 (Win6.1), 5 Nov 2016 8:13:

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.DataGridViewRowCollection.SharedRow(Int32 rowIndex)
   at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
   at MusicBeePlugin.TagHistoryPlugin.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)
This error was thrown with the previous version (2016-11-03) when trying to do 'tag history.' Which wouldn't even show the library tags for the track in question. I also couldn't create a new baseline.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 05, 2016, 03:52:43 PM
Great job! Working much better. Now the whole backup process no longer uses excessive resources, and MB can be used during the task.

Tag history too is working better with those reported bugs fixed. The only wish is tag history command too won't use too much CPU (still it uses over 30% of CPU briefly).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 08, 2016, 01:09:17 PM
Does this new version take care of this error?
suggest, yes.

I also couldn't create a new baseline.
i need more info: is there some error dialog box?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 08, 2016, 07:14:31 PM
I also couldn't create a new baseline.
i need more info: is there some error dialog box?
I can't give you any dialog from when I originally posted that since I've removed all backups, along with the settings file while waiting for a possible fix. I've now started a full backup and when that's done, will try to create a new baseline.
Title: Re: Additional Tagging and Reporting Tools
Post by: klint on November 09, 2016, 08:40:11 AM
Hi
This has probably already been reported, but just in case :)
The plugin page on the main Musicbee site still points to an old version of ATRT (the one for 2.5), although it says 4.18 and requiring MB 3.0 or above

See http://getmusicbee.com/addons/plugins/49/additional-tagging-and-reporting-tools/
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 09, 2016, 09:35:36 AM
phred, thanks, don't forget to report bug if it reappears.

klint, have forgotten that mb main site has own download links and having the link to the wiki is insufficient. thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 09, 2016, 05:15:46 PM
phred, thanks, don't forget to report bug if it reappears.
@boroda74- I'm very encouraged by the latest build! The initial full backup took -much- less time than any full backup previous to this build. 19,000+ tracks in about 30 minutes. Maybe less because I wasn't expecting it to be so much faster I left it and came back 30 minutes later and it was done. Also the restore tags for selected tracks is also much faster. The only thing left for me to test is to create a new baseline. Which I'll get to sometime today and only report back if there's any error. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 10, 2016, 01:12:23 PM
thanks for testing, phred.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 10, 2016, 06:29:07 PM
thanks for testing, phred.
Thanks for developing! And by the way, I ran a new baseline last night and no issues.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 11, 2016, 02:18:47 AM
As a test, I deleted the comment tag from a track which had been backed up. I right-clicked on the track and selected "Tag History." It then showed the Library as black (correct) and the dates/times of the backups that had the tag (also correct.) I then selected on of the previous dates and clicked 'restore selected. The library column now shows the comment. I click apply and I get this error and the tag is not restored.

Code
MusicBee v3.1.6158.36927 (Win6.1), 10 Nov 2016 21:17:

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.DataGridViewRowCollection.SharedRow(Int32 rowIndex)
   at System.Windows.Forms.DataGridViewRowCollection.get_Item(Int32 index)
   at MusicBeePlugin.TagHistoryPlugin.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 November 11, 2016, 11:41:26 AM
thanks. i know why this happens. very silly that i hadn't checked 'apply' button after all optimizations.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 11, 2016, 01:37:02 PM
Fixed! You're getting as fast as Steven with your patches. :-)
Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 13, 2016, 04:39:35 AM
Just tested it, but it doesn't seem to create the initial backup properly. The backup files have no content about tag values. If you make tag changes and run an incremental backup, tag history says no differences for all tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 13, 2016, 09:10:34 AM
Yes, I can see now comparing tags runs almost instantly. For a library with 12,500 tracks, it takes about 6 minutes either for an initial or an incremental backup. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 13, 2016, 01:32:05 PM
No differences in incremental backup, but initial backup takes longer time (from 6 min to 10 min).
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 13, 2016, 02:37:11 PM
No differences in incremental backup, but initial backup takes longer time (from 6 min to 10 min).
I agree - the initial backup using 2016-11-13-4 is substantially slower than 2016-11-11. I'm now at 54% of my 19,000+ tracks and it has taken 35 minutes. That projects out to almost an hour. With the 11-11 build the entire backup took no more than half an hour.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 13, 2016, 02:41:06 PM
what about this version?

http://www.mediafire.com/file/nb4j4fs381mm5ir/mb_TagTools_2016-11-13-5.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 13, 2016, 04:58:13 PM
what about this version?

http://www.mediafire.com/file/nb4j4fs381mm5ir/mb_TagTools_2016-11-13-5.zip
Better. 19k+ took just under 40 minutes. I can live with that.

@boroda74- Since this thread is mostly dealing with the Add'l Tagging & Reporting Tools plugin, would you like me to attempt to merge this thread into the ATRT thread? Might make it easier for users and yourself to keep current.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 13, 2016, 08:08:44 PM
yes, phred, please.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 13, 2016, 08:45:55 PM
yes, phred, please.
Done.   :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 13, 2016, 11:58:07 PM
phred, please compare timings of baseline backup and 2 subsequent incremental backups of 11-13-5 version and these 2 versions for your library (for inc. backups the number of changed tracks should be large enough (~500-1000), i want to choose more fast version:

http://www.mediafire.com/file/mujcqei9936qmpf/mb_TagTools_2016-11-14-1.zip

http://www.mediafire.com/file/uej6c5a5fv7yqry/mb_TagTools_2016-11-14-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 14, 2016, 01:12:52 AM
phred, please compare timings of baseline backup and 2 subsequent incremental backups of 11-13-5 version and these 2 versions for your library (for inc. backups the number of changed tracks should be large enough (~500-1000), i want to choose more fast version:
Happy to help out, boroda74. I should have some info for you around the middle of the week.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 14, 2016, 04:51:06 AM
Why was the Plugin Discussion thread merged into this? And why didn't you ask my opinion before merging this?

What's the hurry? Did I violate any forum rules? Or my opinion doesn't matter?

I am really upset about this.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 14, 2016, 05:10:54 AM
Nobody violated any rules. I sent you a PM right after it was merged so you'd be aware of it.

The 'discussion' thread had boroda74 fielding and posting Add'l Tagging & Reporting plugin questions/updates in two places. I asked him if he thought it was a good idea to merge and he agreed. It made sense to me and it made sense to him.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 14, 2016, 05:28:06 AM
It makes no sense to me as the topic starter, but it doesn't matter to you, does it? Otherwise, you must have asked me too about it.

Also, why did he start posting on the two threads? That's because you posted your responses in the both threads. You're the only one who followed this feature on the other thread. And now you think this topic has no reason to stand alone and merge with the other without asking me?

The Plugin Discussion topic had the proposals of two plugins and the discussion about the other one didn't even start. Also now I have to go through more than 80 pages of the merged thread to find out previous discussion of these features.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 14, 2016, 07:30:21 AM
redwing, i've agreed with phred without asking you first just because didn't consider merging threads very important question. but if you don't think so maybe its not too difficult and too late to separate thread back?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 14, 2016, 07:47:49 AM
phred, forgot to mention: of course you can recopy only 1 file from 3 zip's - mb_TagTools.dll, no need to extract all files from zip.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 14, 2016, 01:13:21 PM
The Plugin Discussion topic had the proposals of two plugins and the discussion about the other one didn't even start. Also now I have to go through more than 80 pages of the merged thread to find out previous discussion of these features.
If the the discussion of the other proposal hasn't even started, then it's simply a matter of copying and pasting it into a new thread. It took me about three minutes to find your initial post on page 72 http://getmusicbee.com/forum/index.php?topic=3833.msg111090#msg111090

Again - the reason for the merge was that 99% of the posts were dealt with an enhancement to the ATRT plugin. I posted my questions and bugs in the ATRT thread because that's where the discussion should've been to being with.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 14, 2016, 01:14:03 PM
phred, forgot to mention: of course you can recopy only 1 file from 3 zip's - mb_TagTools.dll, no need to extract all files from zip.
No problem. That's what I've been doing.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 14, 2016, 03:17:45 PM
I posted my questions and bugs in the ATRT thread because that's where the discussion should've been to being with.

That statement tells me a lot about your mentality and now I can kind of see why you didn't (and probably will not) care my opinion before your action. So you don't care where actual discussion has been going on because you think you know the right place. And you don't care why it started from a new thread to begin with (when the discussion started it wasn't decided whether it would be a new plugin or part of the existing plugin). And you don't care the inconveniences the merge of threads could cause upon me because you think you did a right action. Now I feel like I must thank you for not having merged the wrong topic until yesterday with your great patience.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 14, 2016, 03:41:04 PM
Now I feel like I must thank you for not having merged the wrong topic until yesterday with your great patience.
You yourself admitted that you proposed -two- suggestions in your initial post and that the other suggestion hadn't even started being discussed. That being the case, just start a new thread, as I suggested earlier, by copying the other suggestion into the new initial post. But rather than doing that simple task, you'd rather rant about my "mentality" and not "caring."

No, redwing, you don't have to thank me at all. AAMOF, it's probably better if we just stop communicating with each other.

Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 14, 2016, 04:15:34 PM
OK. I hope you won't take any actions (merging, deleting) on my topics without my consent unless I'm violating any forum rules.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 16, 2016, 03:28:07 AM
phred, please compare timings of baseline backup and 2 subsequent incremental backups of 11-13-5 version and these 2 versions for your library (for inc. backups the number of changed tracks should be large enough (~500-1000), i want to choose more fast version:
Here are the results of my testing...

2016-11-13-5
Initial backup of my 19,000+ track library took about 40 minutes
Auto backup after comments tag was changed in 762 tracks took about 50 minutes

2016-11-14-1
Auto backup took about 45 minutes with 762 tracks changed
New baseline took about 50 minutes

2016-11-14-2
Auto backup took 37 minutes with 762 tracks changed
New baseline took about 15 minutes
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 16, 2016, 10:25:26 AM
ok, phred, thanks. you can keep any version you want because all 3 versions have compatible backups, but new 'official' stable version is 14-2 now.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 16, 2016, 12:18:08 PM
14-2 is what I've kept.
Title: Re: Additional Tagging and Reporting Tools
Post by: dgbx on November 22, 2016, 04:47:47 PM
Hello - I've had Additional Tagging and Reporting Tools installed for some time now and I keep it updated. Last update was maybe a week ago.

I decided I would try the tag backup feature but that ended with the following error:

"Backup ' C:\Users\Dave\AppData\Roaming\Musicbee\Tag Backups\Musicbee Library - Baseline' is corrupted or is not valid MusicBee backup!

There is an error in XML document (11,6)."

Now whenever MusicBee starts up after this I get this error message:

"Master tag backup index is corrupted! All existing at the moment backups are not available any more in 'Tag history' command."

I am running MusicBee 3.1.6169 and have over 100,000 mp3 files in my library.

Any help would be appreciated. I do regular whole computer backups so in any case I would like to get rid of the MB startup error message.

Thanks
dgbx
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 25, 2016, 02:51:15 PM
probably its because i was changing backup format during several weeks. try close mb and delete folder 'C:\Users\Dave\AppData\Roaming\Musicbee\Tag Backups'. then start mb and create fresh backup.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on November 25, 2016, 02:53:34 PM
also you can try to disable guessing library name in '(auto)backup settings' if you are using only 1 library.
Title: Re: Additional Tagging and Reporting Tools
Post by: dgbx on November 27, 2016, 02:57:25 AM
After doing the two suggested actions, the problem has disappeared. Thank you very much. 
Title: Re: Additional Tagging and Reporting Tools
Post by: PolkSDA on November 30, 2016, 07:19:49 PM
Just did an update to the most current version of MusicBee and this plugin, but still cannot configure the plugin. Edit Preferences > Plugins > Configure results in the following:

MusicBee v3.0.6172.33966 (Win6.1), 30 Nov 2016 13:17:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: value
   at System.ComponentModel.ComponentResourceManager.ApplyResources(Object value, String objectName, CultureInfo culture)
   at System.ComponentModel.ComponentResourceManager.ApplyResources(Object value, String objectName)
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at MusicBee.Plugin.#=q_Byn7p7uYnH$D8rPWGVtvw==(IntPtr #=qjFWSK9rKZJ64QvPKm23YbA==)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 01, 2016, 05:18:06 PM
i suggest all other plugin windows are displayed in english (are not localized)?
Title: Re: Additional Tagging and Reporting Tools
Post by: PolkSDA on December 01, 2016, 05:25:39 PM
Correct. Yours is the only plugin I have installed myself. The other ones that are listed are part of the Music Bee install. The list of plugins on that screen are as follows:

last.fm (disabled)
cd art display (disabled)
xbox music
additional tagging tools
theater mode

I went ahead and disabled "xbox music" and "theater mode" and exited and restarted Music Bee, just in case there was some conflict, but that did not fix the error.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 01, 2016, 07:39:36 PM
no, it cant be due to other plugins. some plugin resource (which is stored in one of plugin dll's) is corrupted. i'd recommend to delete all plugin files from 'plugins' folder, redownload plugin and install it again. at least 'configure' window works fine for english localization on my pc.
Title: Re: Additional Tagging and Reporting Tools
Post by: PolkSDA on December 01, 2016, 08:01:24 PM
Deleted all plugin files. Did a fresh download. No change. Still same error.

MusicBee v3.0.6172.33966 (Win6.1), 1 Dec 2016 14:00:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: value
   at System.ComponentModel.ComponentResourceManager.ApplyResources(Object value, String objectName, CultureInfo culture)
   at System.ComponentModel.ComponentResourceManager.ApplyResources(Object value, String objectName)
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at MusicBee.Plugin.#=q_Byn7p7uYnH$D8rPWGVtvw==(IntPtr #=qjFWSK9rKZJ64QvPKm23YbA==)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 05, 2016, 05:03:00 AM
Coming from this thread: http://getmusicbee.com/forum/index.php?topic=20379.0

It would be useful if this plugin supports a command that can convert any Unicode punctuation characters in selected tags to their ASCII equivalents. As the topic suggests, this can always happen whenever the user auto-tags tracks from Musicbrainz in addition to already existing tags.

Picard seems to have such a feature, but when looking at the code, it's trying to do a bit too much beyond punctuation: https://github.com/metabrainz/picard/blob/cb9b6294e2502b637c93a93a54d96f46570f2407/picard/util/textencoding.py

I think it only needs to convert just punctuation characters to be useful. Other characters are rarely used and if they are used it could be intended.

The tags where this can happen most often includes title, album, lyrics, comments and filename. It would be great if the user could keep a set of tags selected at once for this command. But changing folder name in path should be warned before execution as that is likely to affect finding other tracks under those folders.

What do you think?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 05, 2016, 08:37:18 AM
On second thought, probably it would be better for this new command or preset not to support changing filename and path at all as it might break mapping of the files with MB database (which could end up losing all metadata saved only in MB db).
I think the best place for that would be a new option in "Remap Music Files" command dialog as it needs to be executed for entire database, not just for a subset of files which could break the mapping for other affected files.
Not sure this plugin can do such a remapping as well. If not, I'll post such a wish from MB side.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 17, 2016, 07:11:36 PM
@redwing, mb api doesn't allow such kind of things, thought i really can do some characters substitutions only in tags. also unicode can contain above 1,000,000 characters and i even don't know the number of punctuation chars in the latest version of unicode. i don't think this can usefully implemented in plugin.

@PolkSDA, i think i cant help you.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 18, 2016, 05:43:19 AM
@redwing, mb api doesn't allow such kind of things, thought i really can do some characters substitutions only in tags. also unicode can contain above 1,000,000 characters and i even don't know the number of punctuation chars in the latest version of unicode. i don't think this can usefully implemented in plugin.

Converting only 68 characters would be more than enough. Look at the linked Picard code from line 107 to 175.

    u"\u013F": u"L",  # LATIN CAPITAL LETTER L WITH MIDDLE DOT (compat)
    u"\u0140": u"l",  # LATIN SMALL LETTER L WITH MIDDLE DOT (compat)
    u"\u2018": u"'",  # LEFT SINGLE QUOTATION MARK (from ‹character-fallback›)
    u"\u2019": u"'",  # RIGHT SINGLE QUOTATION MARK (from ‹character-fallback›)
    u"\u201A": u"'",  # SINGLE LOW-9 QUOTATION MARK (from ‹character-fallback›)
    u"\u201B": u"'",  # SINGLE HIGH-REVERSED-9 QUOTATION MARK (from ‹character-fallback›)
    u"\u201C": u"\"",  # LEFT DOUBLE QUOTATION MARK (from ‹character-fallback›)
    u"\u201D": u"\"",  # RIGHT DOUBLE QUOTATION MARK (from ‹character-fallback›)
    u"\u201E": u"\"",  # DOUBLE LOW-9 QUOTATION MARK (from ‹character-fallback›)
    u"\u201F": u"\"",  # DOUBLE HIGH-REVERSED-9 QUOTATION MARK (from ‹character-fallback›)
    u"\u2032": u"'",  # PRIME
    u"\u2033": u"\"",  # DOUBLE PRIME
    u"\u301D": u"\"",  # REVERSED DOUBLE PRIME QUOTATION MARK
    u"\u301E": u"\"",  # DOUBLE PRIME QUOTATION MARK
    u"\u00AB": u"<<",  # LEFT-POINTING DOUBLE ANGLE QUOTATION MARK (from ‹character-fallback›)
    u"\u00BB": u">>",  # RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK (from ‹character-fallback›)
    u"\u2039": u"<",  # SINGLE LEFT-POINTING ANGLE QUOTATION MARK
    u"\u203A": u">",  # SINGLE RIGHT-POINTING ANGLE QUOTATION MARK
    u"\u00AD": u"",  # SOFT HYPHEN (from ‹character-fallback›)
    u"\u2010": u"-",  # HYPHEN (from ‹character-fallback›)
    u"\u2011": u"-",  # NON-BREAKING HYPHEN (from ‹character-fallback›)
    u"\u2012": u"-",  # FIGURE DASH (from ‹character-fallback›)
    u"\u2013": u"-",  # EN DASH (from ‹character-fallback›)
    u"\u2014": u"-",  # EM DASH (from ‹character-fallback›)
    u"\u2015": u"-",  # HORIZONTAL BAR (from ‹character-fallback›)
    u"\uFE31": u"|",  # PRESENTATION FORM FOR VERTICAL EM DASH (compat)
    u"\uFE32": u"|",  # PRESENTATION FORM FOR VERTICAL EN DASH (compat)
    u"\uFE58": u"-",  # SMALL EM DASH (compat)
    u"\u2016": u"||",  # DOUBLE VERTICAL LINE
    u"\u2044": u"/",  # FRACTION SLASH (from ‹character-fallback›)
    u"\u2045": u"[",  # LEFT SQUARE BRACKET WITH QUILL
    u"\u2046": u"]",  # RIGHT SQUARE BRACKET WITH QUILL
    u"\u204E": u"*",  # LOW ASTERISK
    u"\u3008": u"<",  # LEFT ANGLE BRACKET
    u"\u3009": u">",  # RIGHT ANGLE BRACKET
    u"\u300A": u"<<",  # LEFT DOUBLE ANGLE BRACKET
    u"\u300B": u">>",  # RIGHT DOUBLE ANGLE BRACKET
    u"\u3014": u"[",  # LEFT TORTOISE SHELL BRACKET
    u"\u3015": u"]",  # RIGHT TORTOISE SHELL BRACKET
    u"\u3018": u"[",  # LEFT WHITE TORTOISE SHELL BRACKET
    u"\u3019": u"]",  # RIGHT WHITE TORTOISE SHELL BRACKET
    u"\u301A": u"[",  # LEFT WHITE SQUARE BRACKET
    u"\u301B": u"]",  # RIGHT WHITE SQUARE BRACKET
    u"\uFE11": u",",  # PRESENTATION FORM FOR VERTICAL IDEOGRAPHIC COMMA (compat)
    u"\uFE12": u".",  # PRESENTATION FORM FOR VERTICAL IDEOGRAPHIC FULL STOP (compat)
    u"\uFE39": u"[",  # PRESENTATION FORM FOR VERTICAL LEFT TORTOISE SHELL BRACKET (compat)
    u"\uFE3A": u"]",  # PRESENTATION FORM FOR VERTICAL RIGHT TORTOISE SHELL BRACKET (compat)
    u"\uFE3D": u"<<",  # PRESENTATION FORM FOR VERTICAL LEFT DOUBLE ANGLE BRACKET (compat)
    u"\uFE3E": u">>",  # PRESENTATION FORM FOR VERTICAL RIGHT DOUBLE ANGLE BRACKET (compat)
    u"\uFE3F": u"<",  # PRESENTATION FORM FOR VERTICAL LEFT ANGLE BRACKET (compat)
    u"\uFE40": u">",  # PRESENTATION FORM FOR VERTICAL RIGHT ANGLE BRACKET (compat)
    u"\uFE51": u",",  # SMALL IDEOGRAPHIC COMMA (compat)
    u"\uFE5D": u"[",  # SMALL LEFT TORTOISE SHELL BRACKET (compat)
    u"\uFE5E": u"]",  # SMALL RIGHT TORTOISE SHELL BRACKET (compat)
    u"\uFF5F": u"((",  # FULLWIDTH LEFT WHITE PARENTHESIS (compat)(from ‹character-fallback›)
    u"\uFF60": u"))",  # FULLWIDTH RIGHT WHITE PARENTHESIS (compat)(from ‹character-fallback›)
    u"\uFF61": u".",  # HALFWIDTH IDEOGRAPHIC FULL STOP (compat)
    u"\uFF64": u",",  # HALFWIDTH IDEOGRAPHIC COMMA (compat)
    u"\u2212": u"-",  # MINUS SIGN (from ‹character-fallback›)
    u"\u2215": u"/",  # DIVISION SLASH (from ‹character-fallback›)
    u"\u2216": u"\\",  # SET MINUS (from ‹character-fallback›)
    u"\u2223": u"|",  # DIVIDES (from ‹character-fallback›)
    u"\u2225": u"||",  # PARALLEL TO (from ‹character-fallback›)
    u"\u226A": u"<<",  # MUCH LESS-THAN
    u"\u226B": u">>",  # MUCH GREATER-THAN
    u"\u2985": u"((",  # LEFT WHITE PARENTHESIS
    u"\u2986": u"))",  # RIGHT WHITE PARENTHESIS
    u"\u200B": u"", # Zero Width Space

Some special ASR preset could do the job that detects those characters and converts to ascii code just like the apostrophe preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: bosseric on January 05, 2017, 03:21:30 AM
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: frankcreed on January 24, 2017, 08:50:00 PM
Wishlist request: to support the additional tags Steven has added for classical music tagging (see this thread: http://getmusicbee.com/forum/index.php?topic=20209.60 (http://getmusicbee.com/forum/index.php?topic=20209.60))

MOVEMENT
MOVEMENTNAME
MOVEMENTTOTAL
SHOWMOVEMENT
WORK

Thanks in advance.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 30, 2017, 04:02:19 PM
redwing, frankcreed, i will look at  your ideas later, i'm ill now and wont to spent tool much time on programming.

bosseric, suggest you can copy 'toy: set tag' to multiplr presets and say each of them to set emty value for every unnededd  tag (you have to have every preset for every unneeded tag. .if you  tick  checkbox next yo these 'tay: ...' presets, then all these tags wil be auto erased, if you change any tag of track or just move track from inbox to library.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 31, 2017, 05:34:11 AM
redwing, frankcreed, i will look at  your ideas later, i'm ill now and wont to spent tool much time on programming.

Hope you get better soon. Don't worry about my suggestion. It's not that important.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 04, 2017, 04:38:26 AM
No rush, but when you feel up to it... I find it WAY too easy to accidentally apply presets on a permanent basis.  Could there maybe be a confirmation, or even a complete separate screen for applying presets that should be "always on" instead of just loaded for single use/editing?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 04, 2017, 01:28:43 PM
No rush, but when you feel up to it... I find it WAY too easy to accidentally apply presets on a permanent basis.  Could there maybe be a confirmation, or even a complete separate screen for applying presets that should be "always on" instead of just loaded for single use/editing?
+1
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 10:48:54 AM
No rush, but when you feel up to it... I find it WAY too easy to accidentally apply presets on a permanent basis.  Could there maybe be a confirmation, or even a complete separate screen for applying presets that should be "always on" instead of just loaded for single use/editing?
do you mean confirmation before auto-applying presets? if so its very easy to do, but for all auto-applying presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 10:50:25 AM
Converting only 68 characters would be more than enough. Look at the linked Picard code from line 107 to 175.
redwing, probably i'll publish new asr preset pack later this evening.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 10:51:42 AM
Wishlist request: to support the additional tags Steven has added for classical music tagging (see this thread: http://getmusicbee.com/forum/index.php?topic=20209.60 (http://getmusicbee.com/forum/index.php?topic=20209.60))

MOVEMENT
MOVEMENTNAME
MOVEMENTTOTAL
SHOWMOVEMENT
WORK

Thanks in advance.
i've asked Steven about details about these new tags. waiting for his answer.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 03:56:15 PM
redwing, please test new asr preset 'replace unicode punctuation marks...'

phred, psychoadept, please test new option 'ask confirmation before auto-applying this preset' in main asr window.

frankcreed, i've received Stevens comments on new tags, but its not implemented yet.






http://www.mediafire.com/file/9i97ha7peugjsrx/mb_TagTools_2017-02-09.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 09, 2017, 05:48:39 PM
redwing, please test new asr preset 'replace unicode punctuation marks...'

Thanks for implementing this!
I tested with some unicode characters and it works well. However it for some reason multiplies the converted value. For instance, if you convert "abc" in title tag, it writes "abcabcabc".
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 08:08:05 PM
redwing, please test new asr preset 'replace unicode punctuation marks...'

Thanks for implementing this!
I tested with some unicode characters and it works well. However it for some reason multiplies the converted value. For instance, if you convert "abc" in title tag, it writes "abcabcabc".
i knew that there are some errors.:)  could you post one example tag with unicode punctuation mark(s), so i can test this myself.

edit: i think i know whats the problem. try this preset pack:

http://www.mediafire.com/file/pc5wmt02zdbc3zp/ASR_Presets.rar

don't forget to 'import all' presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 08:57:30 PM
@frankcreed, please try this plugin version, new tags should be available now:

http://www.mediafire.com/file/7a8rb12mz257wk4/mb_TagTools_2017-02-09-2.zip

you will need latest mb 3.1 patch:

http://musicbee.niblseed.com/V3_1/MusicBee31_Patched.zip

Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 09, 2017, 10:03:24 PM
@boroda74-

I have unzipped ARS Presents along with the dll and placed them in their respective directories, letting new overwrite old. Trying to start MB I'm now getting the following error when launching MB:
(http://i.imgur.com/fD1loov.jpg)
After clicking OK, -sometimes- the Advanced Search and Replace window opens and sometimes it doesn't. In either case, MB opens.
Checking TagNamesErrorLog revels this:
Code
Adding  / SortAlbumArtist
Cant add  / SortAlbumArtist
Adding  / SortArtist
Cant add  / SortArtist
Adding  / SortComposer
Cant add  / SortComposer
Adding  / Work
Cant add  / Work
Adding  / MovementName
Cant add  / MovementName
Adding  / MovementNo
Cant add  / MovementNo
Adding  / MovementCount
Cant add  / MovementCount
Adding  / ShowMovement
Cant add  / ShowMovement
Adding  / Language
Cant add  / Language
Adding  / OriginalArtist
Cant add  / OriginalArtist
Adding  / OriginalYear
Cant add  / OriginalYear
Adding  / MusicianCredits
Cant add  / MusicianCredits
Adding  / OriginalTitle
Cant add  / OriginalTitle
Is this something I can fix, or is there a bug you need to work on?
Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2017, 10:50:09 PM
@phred, its because you've downloaded 02-09-2 plugin version instead of 02-09. to use 02-09-2 version (the only difference between these 2 versions is that 02-09-2 supports for new tags, recently added to mb by Steven) you need mb 3.1 latest patch:

http://musicbee.niblseed.com/V3_1/MusicBee31_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 09, 2017, 11:22:10 PM
@phred, its because you've downloaded 02-09-2 plugin version instead of 02-09. to use 02-09-2 version (the only difference between these 2 versions is that 02-09-2 supports for new tags, recently added to mb by Steven) you need mb 3.1 latest patch:
Yes, my bad. I thought I was using the latest patch, but apparently not. Thanks boroda74.

Also, I like the new confirmation on auto-applying presets! I have found one thing that doesn't work as I believe it should. I'm using it on the preset 'remove leading zeros in '<Tag 1>' -2. It works as expected when I edit a track number that is 01. But when I remove the track number completely, the confirmation window also pops up. I don't think it should be asking for confirmation in a case like this.

But thanks for adding that feature.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 10, 2017, 12:14:58 AM
The bug's fixed. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 10, 2017, 12:58:58 AM
@phred

http://www.mediafire.com/file/bzdr7aqxya3bvok/mb_TagTools_2017-02-10.zip

it seems that there are some bugs with confirmation checkbox on manual applying presets, but now is deep night, i'm sleepy and edit: cant reproduce these bags.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 10, 2017, 02:07:26 AM
There's still an issue ... I deleted a track number and did not get the confirmation, which is good.
But when I added track number 013 and clicked 'save' I got this
(http://i.imgur.com/CsOmpVB.jpg)
After clicking 'ok' the expected confirmation popped up. And now, if I manually edit a track number to 013, there's no confirmation nor does the leading '0' get removed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 10, 2017, 07:06:01 AM
@phred
i've forgotten to remove debugging popup window, but i'm sure there is still some real bug. here is plugin with debugging widow removed:

http://www.mediafire.com/file/xcarqxt9pw69xjd/mb_TagTools_2017-02-10-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: frankcreed on February 14, 2017, 09:33:26 PM
redwing, please test new asr preset 'replace unicode punctuation marks...'

phred, psychoadept, please test new option 'ask confirmation before auto-applying this preset' in main asr window.

frankcreed, i've received Stevens comments on new tags, but its not implemented yet.






http://www.mediafire.com/file/9i97ha7peugjsrx/mb_TagTools_2017-02-09.zip

Hi Boroda,

Thanks for implementing the changes!
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 19, 2017, 04:22:20 AM
Sorry, I've been behind!  I just tested out the new confirmation setting.  I'm not sure how it's supposed to work.  When a setting is ticked for auto-apply, you have to also tick the confirmation setting?  Otherwise it behaves as before, and goes straight to auto-apply?
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on February 19, 2017, 03:00:28 PM
Been a hell of a long time since I've been on the board, so of course I return with a bug report.

14/01/2017 16:52:59 - 10.0.14393.0 - 3.0.6190.36802 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: String
   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at MusicBeePlugin.Plugin.ReceiveNotification(String sourceFileUrl, NotificationType type)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at MusicBee.Plugin.#=qGVXp5ZoITKKwGWjTtr1As43kOnRgnp$zA2OSSytwaBE=()

I think this has been happening since sometime after the 05/02 (that's the last time my auto-report seems to have run) - I only noticed that the plugin was disabled when I couldn't access the S&R screen yesterday. I'm on the latest MB patch and the latest version of the plugin (from 10/02). Now every time I try to enable the plugin from within the preferences screen, I just get the message: Unable to initialise this plugin. Exception has been thrown by the target of an invocation.

Any ideas?

EDIT: Just had a look through my recycle bin. Based on the versions of MB I've recently downloaded, I'd say it's probably some sort of conflict that's occurred due to a change between the MB version on 04/02 and the current version.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 19, 2017, 05:24:52 PM
Try patching to 3.1
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on February 19, 2017, 10:23:32 PM
Just checked - I'm on 3.1.6256
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 20, 2017, 04:55:17 AM
The plugin is working for me, but I'm getting the same error message as above, about 2500 times just in the last day.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 21, 2017, 07:34:02 AM
@all

can't reproduce this bug.

try this plugin version:

http://www.mediafire.com/file/333ora4bh7s1p2m/mb_TagTools.dll

i need to know if error window (not confirmation dialog) with text "null!" will pop up for you.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 21, 2017, 07:36:34 AM
Sorry, I've been behind!  I just tested out the new confirmation setting.  I'm not sure how it's supposed to work.  When a setting is ticked for auto-apply, you have to also tick the confirmation setting?  Otherwise it behaves as before, and goes straight to auto-apply?
if preset is not ticked for auto-applying then it it doesn't matter if confirmation option is ticked or not. also confirmation option does nothing when you manually apply preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 21, 2017, 02:28:01 PM
Sorry, I've been behind!  I just tested out the new confirmation setting.  I'm not sure how it's supposed to work.  When a setting is ticked for auto-apply, you have to also tick the confirmation setting?  Otherwise it behaves as before, and goes straight to auto-apply?
if preset is not ticked for auto-applying then it it doesn't matter if confirmation option is ticked or not. also confirmation option does nothing when you manually apply preset.

That's all fine, but I don't think it has solved the problem. The change needed is the ability to make a preset NOT automatically applied with one click.  It still only takes one click to mark the box next to a preset.  There needs to be an opt OUT for confirmation of applying a preset, not an opt IN.  Ideally this would be a global setting, maybe in the configuration panel.  Something to the effect of "Do not require confirmation when applying tag changes automatically"  (my preference would be to receive a confirmation when you tick the box fur the preset, but receiving it when tag changes are triggered could work, too.)
Title: Re: Additional Tagging and Reporting Tools
Post by: Piwilelapin on February 21, 2017, 02:57:34 PM
Hi !

Since I've used the TOY change case command with advanced tagging tool, the numbers in my titles appear this way: "Ii, Iii, Iv, V, Vi"

(http://img11.hostingpics.net/pics/421302Capture.png) (http://www.hostingpics.net/viewer.php?id=421302Capture.png)

The exceptions is about putting words in lowercase, so I'm not sure what to use.

Does anyone of you know ? :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2017, 08:00:30 AM
That's all fine, but I don't think it has solved the problem. The change needed is the ability to make a preset NOT automatically applied with one click.  It still only takes one click to mark the box next to a preset.  There needs to be an opt OUT for confirmation of applying a preset, not an opt IN.  Ideally this would be a global setting, maybe in the configuration panel.  Something to the effect of "Do not require confirmation when applying tag changes automatically"  (my preference would be to receive a confirmation when you tick the box fur the preset, but receiving it when tag changes are triggered could work, too.)
actually i don't understand you. just tick confirmation checkboxes for all presets and you will get confirmation dialog before AUTO-applying these presets. its not the global option, but i don't think you have dozens auto-applied presets. and here you are right:

When a setting is ticked for auto-apply, you have to also tick the confirmation setting?  Otherwise it behaves as before, and goes straight to auto-apply?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 24, 2017, 08:41:58 AM
Hi !

Since I've used the TOY change case command with advanced tagging tool, the numbers in my titles appear this way: "Ii, Iii, Iv, V, Vi"

(http://img11.hostingpics.net/pics/421302Capture.png) (http://www.hostingpics.net/viewer.php?id=421302Capture.png)

The exceptions is about putting words in lowercase, so I'm not sure what to use.

Does anyone of you know ? :)
try dedicated 'change case' command instead of 'toy' asr preset.this command has much more options.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 26, 2017, 06:13:04 PM
@all

can't reproduce this bug.

try this plugin version:

http://www.mediafire.com/file/333ora4bh7s1p2m/mb_TagTools.dll

i need to know if error window (not confirmation dialog) with text "null!" will pop up for you.

Yes, I am seeing "null!" pop up frequently.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 27, 2017, 07:41:14 AM
could you try to upgrade to the very latest mb 3.1 patch? it seems that some mb functionality is broken now.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on February 27, 2017, 08:32:08 AM
could you try to upgrade to the very latest mb 3.1 patch? it seems that some mb functionality is broken now.
I am pretty sure psychoadept is using the latest version. You need to let me know what api function specifically is not doing the expected thing. The only thing I can recall being changed is to allow the new tags to be retrieved, so is it possible one of the tag numbers you are calling is returning null and if so is the number < 175 ? Also if you are looking at the data type, don't assume that numeric fields are guaranteed to be valid numbers

edit:
looking at the code the Library_GetFileTag(url,field) function will return null if the url is blank or if field > 180
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2017, 01:19:20 AM
Steven, thanks for your interest.

plugin now frequently (it seems that not always) gets null when it request mb native persistent track id if tag backup is turned on. more specifically (though i don't think it matters) plugin is failing to get track id in call of 'mbApiInterface.Library_GetDevicePersistentId(currentFile, (DeviceIdType)0)' in 'ReceiveNotification()' method.
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on February 28, 2017, 07:25:40 AM
Steven, thanks for your interest.

plugin now frequently (it seems that not always) gets null when it request mb native persistent track id if tag backup is turned on. more specifically (though i don't think it matters) plugin is failing to get track id in call of 'mbApiInterface.Library_GetDevicePersistentId(currentFile, (DeviceIdType)0)' in 'ReceiveNotification()' method.


For what it's worth, I do not have tag backup turned on.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2017, 11:13:02 AM
i don't mean *autobackup*, try to exit mb, delete plugin settings file and restart mb.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2017, 12:23:42 PM
@psychoadept

could you try this plugin version?

http://www.mediafire.com/file/6wptsnr2ead8wzz/mb_TagTools_2017-02-28.zip

only 'mb_tagtools.dll' is changed.



------------------------------------------------
edit:

and probably mb latest patch:

http://musicbee.niblseed.com/V3_1/MusicBee31_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on March 02, 2017, 06:47:48 AM
Running a debug version of MB that Steven sent me in PM, and this version of your plugin, I got exactly one error message all evening.  I think it was from the debug, not the plugin, but here it is.

Code
3/1/2017 11:48:59 PM -    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at #=qpv2JUQuAHhMDCbXp2bxKog==.#=qmJpdlj3DFxVhg70jvgXYiA==.#=qGmwv8cv_Tv0jdbpgTZNffw==(String #=q8C57lWBhZw6z_r4NjT$pmw==, Int32 #=qSxE6bRWCJ8l76sY99lGchQ==)
   at #=qpv2JUQuAHhMDCbXp2bxKog==.#=qmJpdlj3DFxVhg70jvgXYiA==.#=q0cvPR40BT0zPtrVBnfPA$g==.#=qb_clzpoONlj9rF5mkOzgRyZYLlBtWAtvlgYMd2$xir0=(#=qh1isaBINOwFMhU544dHDfQ== #=qXipF23a6P49RVfcCYqgiiQ==, FileMode #=qHvVL8yiI4fW$kSle9$SezA==, FileAccess #=qYhyrkpYyKnUpK6tjVpyhtA==, FileShare #=q7mhLOYHM9R5NeTb2sGhWcQ==, Int32 #=qDyZVQw_jLxMuR1vP7DpENw==, Boolean #=qKBsW0n7re$XITg7MqX5OoQ==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=qEdosXhXh2y8fSd7ddq3P4Sbt$a6crTBkPtJcZS866q8=(#=qh1isaBINOwFMhU544dHDfQ== #=qG5ASwGfwdd$M9RC$1GRV2Q==, FileMode #=qHM_N46ZBWR3Wl7dclLrKEQ==, FileAccess #=q7jQa0WvvJIYfoeVdK09LSA==, Int32 #=q6DdKOkNMw72AvpmLvB7_fA==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=qazl6k$oWBk60YbdoMhmCOA5ysptXBWFm6TzgmOJPiO0=(#=qh1isaBINOwFMhU544dHDfQ== #=q7DI20uOZY60PuClLfRxB6A==)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qv2C__rOSWo$qPqIDcTb2dDkZsYBJqJ0IvAEN9b6N4jw=(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qqdJV3O5ldBcIivh2W49cBQ==, #=q7jWLST0vzQWExCXh58jTUP2bAnF3yEPx$O9Vq_e9q_Q= #=q3kB56$D05U1Xspzf6YwpBQ==, Int32 #=qDtx9o$EfgxzCJbKFEzyFDroFhTD3kwuoOIE_aPvNM90=, Stream #=q4kUlu3F8340IqFdNWJiOXA==, List`1 #=q5GNPyKNyWU6Ji0RqDqvwDg==, Boolean #=qllJS2uBYbLvTEk0B6r786W8IksRp1Ok52t9$0oD6EFg=)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qLezpjErWU0Y2Y1tP74RQvIN$VYxinb_PIM9hqc5tiE0=(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qfrqndb4sEqfIeaidxU7SUw==, List`1 #=qUvaKN72ccwmOqp_biGvqPg==, Boolean #=qFdzdQXeROYVJvQuDQCmTtg==, List`1 #=q2sNy$fBiuycHnAeK2iljvQ==, #=qCiuJIBZrhEzfgLnfBgkgqKPhMe5$ttArFNtNAuKhNAs= #=qxN_55WA0xEJsPIO8of3Z6g==, Boolean #=q67iz9AlsFZ505$e7YePuQQ==)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qhb9aklekV6xQhV1ick7$Dw==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qLxLcgsr8KF94flqOu6sQyw==, List`1 #=q0M4fHt542oQdPJVy_nSyTQ==)
   at MusicBee.Media.File.#=qa8WmNY2$7GsCTtYY7eeQuA==.#=q8x75j4LQqG8qpkM4DNmZug==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=q04Wsr3WgchflYoq4M9KI7w==, List`1 #=q_thh$uzd6Shz$KthF5mS$g==)
   at MusicBee.Media.File.#=qhNiwMrUbo8UntzdYkSopnA==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qEXzWXCy4Drv9sqaAZzrjKQ==, List`1 #=qAQBysU4r74GjD7$DWcwovw==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=q9gRMxMvkd39i5Ez9XBtCOw==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qb3$PnyUCsGjMq1I1dBtjvQ==, List`1 #=ql47ghZho6uQrs3HXON6Xbw==)
   at #=qqOhFRUOH0GvU5$xoGffr3RI87kwpuh5xhTCQWfGBkv4=.#=qjxxVw5wgEJN1Wr95D4fR3wTvY92v$htlhnlpfMsFjGs=.#=qR_IC74Mk1ID3k7kWLXXDBw==(#=qIvMEl5$IzxmNl4zmdjBD2yzvkvVNkeg8PTvLCCp2XX3bPvrnGHWTz09rrNvsOUtF #=qvZC4tlg4Lk$wZLVgci8bZA==, Boolean #=qIjsRvLoI$Xt3Ruzf$vNAbw==, List`1 #=qNa0Ax8cQV03R_McQE6BqwA==, List`1 #=qI9xflfNH3X4vMRYqgrArKo7TuSO1qT5StbMmhQ_LxMk=)
   at #=qqOhFRUOH0GvU5$xoGffr3RI87kwpuh5xhTCQWfGBkv4=.#=qjxxVw5wgEJN1Wr95D4fR3wTvY92v$htlhnlpfMsFjGs=.#=q1lKj2b760DLQBdeTNlH_5MEBf8_5TnCeoaH02DMoCew=()
   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()
3/1/2017 11:48:59 PM -    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at #=qpv2JUQuAHhMDCbXp2bxKog==.#=qmJpdlj3DFxVhg70jvgXYiA==.#=qGmwv8cv_Tv0jdbpgTZNffw==(String #=q8C57lWBhZw6z_r4NjT$pmw==, Int32 #=qSxE6bRWCJ8l76sY99lGchQ==)
   at #=qpv2JUQuAHhMDCbXp2bxKog==.#=qmJpdlj3DFxVhg70jvgXYiA==.#=q0cvPR40BT0zPtrVBnfPA$g==.#=qb_clzpoONlj9rF5mkOzgRyZYLlBtWAtvlgYMd2$xir0=(#=qh1isaBINOwFMhU544dHDfQ== #=qXipF23a6P49RVfcCYqgiiQ==, FileMode #=qHvVL8yiI4fW$kSle9$SezA==, FileAccess #=qYhyrkpYyKnUpK6tjVpyhtA==, FileShare #=q7mhLOYHM9R5NeTb2sGhWcQ==, Int32 #=qDyZVQw_jLxMuR1vP7DpENw==, Boolean #=qKBsW0n7re$XITg7MqX5OoQ==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=qEdosXhXh2y8fSd7ddq3P4Sbt$a6crTBkPtJcZS866q8=(#=qh1isaBINOwFMhU544dHDfQ== #=qG5ASwGfwdd$M9RC$1GRV2Q==, FileMode #=qHM_N46ZBWR3Wl7dclLrKEQ==, FileAccess #=q7jQa0WvvJIYfoeVdK09LSA==, Int32 #=q6DdKOkNMw72AvpmLvB7_fA==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=qazl6k$oWBk60YbdoMhmCOA5ysptXBWFm6TzgmOJPiO0=(#=qh1isaBINOwFMhU544dHDfQ== #=q7DI20uOZY60PuClLfRxB6A==)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qv2C__rOSWo$qPqIDcTb2dDkZsYBJqJ0IvAEN9b6N4jw=(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qqdJV3O5ldBcIivh2W49cBQ==, #=q7jWLST0vzQWExCXh58jTUP2bAnF3yEPx$O9Vq_e9q_Q= #=q3kB56$D05U1Xspzf6YwpBQ==, Int32 #=qDtx9o$EfgxzCJbKFEzyFDroFhTD3kwuoOIE_aPvNM90=, Stream #=q4kUlu3F8340IqFdNWJiOXA==, List`1 #=q5GNPyKNyWU6Ji0RqDqvwDg==, Boolean #=qllJS2uBYbLvTEk0B6r786W8IksRp1Ok52t9$0oD6EFg=)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qLezpjErWU0Y2Y1tP74RQvIN$VYxinb_PIM9hqc5tiE0=(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qfrqndb4sEqfIeaidxU7SUw==, List`1 #=qUvaKN72ccwmOqp_biGvqPg==, Boolean #=qFdzdQXeROYVJvQuDQCmTtg==, List`1 #=q2sNy$fBiuycHnAeK2iljvQ==, #=qCiuJIBZrhEzfgLnfBgkgqKPhMe5$ttArFNtNAuKhNAs= #=qxN_55WA0xEJsPIO8of3Z6g==, Boolean #=q67iz9AlsFZ505$e7YePuQQ==)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qhb9aklekV6xQhV1ick7$Dw==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qLxLcgsr8KF94flqOu6sQyw==, List`1 #=q0M4fHt542oQdPJVy_nSyTQ==)
   at MusicBee.Media.File.#=qa8WmNY2$7GsCTtYY7eeQuA==.#=q8x75j4LQqG8qpkM4DNmZug==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=q04Wsr3WgchflYoq4M9KI7w==, List`1 #=q_thh$uzd6Shz$KthF5mS$g==)
   at MusicBee.Media.File.#=qhNiwMrUbo8UntzdYkSopnA==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qEXzWXCy4Drv9sqaAZzrjKQ==, List`1 #=qAQBysU4r74GjD7$DWcwovw==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=q9gRMxMvkd39i5Ez9XBtCOw==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qb3$PnyUCsGjMq1I1dBtjvQ==, List`1 #=ql47ghZho6uQrs3HXON6Xbw==)
   at #=qqOhFRUOH0GvU5$xoGffr3RI87kwpuh5xhTCQWfGBkv4=.#=qjxxVw5wgEJN1Wr95D4fR3wTvY92v$htlhnlpfMsFjGs=.#=qR_IC74Mk1ID3k7kWLXXDBw==(#=qIvMEl5$IzxmNl4zmdjBD2yzvkvVNkeg8PTvLCCp2XX3bPvrnGHWTz09rrNvsOUtF #=qvZC4tlg4Lk$wZLVgci8bZA==, Boolean #=qIjsRvLoI$Xt3Ruzf$vNAbw==, List`1 #=qNa0Ax8cQV03R_McQE6BqwA==, List`1 #=qI9xflfNH3X4vMRYqgrArKo7TuSO1qT5StbMmhQ_LxMk=)
   at #=qqOhFRUOH0GvU5$xoGffr3RI87kwpuh5xhTCQWfGBkv4=.#=qjxxVw5wgEJN1Wr95D4fR3wTvY92v$htlhnlpfMsFjGs=.#=q1lKj2b760DLQBdeTNlH_5MEBf8_5TnCeoaH02DMoCew=()
   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()
3/1/2017 11:48:59 PM -    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at #=qpv2JUQuAHhMDCbXp2bxKog==.#=qmJpdlj3DFxVhg70jvgXYiA==.#=qGmwv8cv_Tv0jdbpgTZNffw==(String #=q8C57lWBhZw6z_r4NjT$pmw==, Int32 #=qSxE6bRWCJ8l76sY99lGchQ==)
   at #=qpv2JUQuAHhMDCbXp2bxKog==.#=qmJpdlj3DFxVhg70jvgXYiA==.#=q0cvPR40BT0zPtrVBnfPA$g==.#=qb_clzpoONlj9rF5mkOzgRyZYLlBtWAtvlgYMd2$xir0=(#=qh1isaBINOwFMhU544dHDfQ== #=qXipF23a6P49RVfcCYqgiiQ==, FileMode #=qHvVL8yiI4fW$kSle9$SezA==, FileAccess #=qYhyrkpYyKnUpK6tjVpyhtA==, FileShare #=q7mhLOYHM9R5NeTb2sGhWcQ==, Int32 #=qDyZVQw_jLxMuR1vP7DpENw==, Boolean #=qKBsW0n7re$XITg7MqX5OoQ==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=qEdosXhXh2y8fSd7ddq3P4Sbt$a6crTBkPtJcZS866q8=(#=qh1isaBINOwFMhU544dHDfQ== #=qG5ASwGfwdd$M9RC$1GRV2Q==, FileMode #=qHM_N46ZBWR3Wl7dclLrKEQ==, FileAccess #=q7jQa0WvvJIYfoeVdK09LSA==, Int32 #=q6DdKOkNMw72AvpmLvB7_fA==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=qazl6k$oWBk60YbdoMhmCOA5ysptXBWFm6TzgmOJPiO0=(#=qh1isaBINOwFMhU544dHDfQ== #=q7DI20uOZY60PuClLfRxB6A==)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qv2C__rOSWo$qPqIDcTb2dDkZsYBJqJ0IvAEN9b6N4jw=(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qqdJV3O5ldBcIivh2W49cBQ==, #=q7jWLST0vzQWExCXh58jTUP2bAnF3yEPx$O9Vq_e9q_Q= #=q3kB56$D05U1Xspzf6YwpBQ==, Int32 #=qDtx9o$EfgxzCJbKFEzyFDroFhTD3kwuoOIE_aPvNM90=, Stream #=q4kUlu3F8340IqFdNWJiOXA==, List`1 #=q5GNPyKNyWU6Ji0RqDqvwDg==, Boolean #=qllJS2uBYbLvTEk0B6r786W8IksRp1Ok52t9$0oD6EFg=)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qLezpjErWU0Y2Y1tP74RQvIN$VYxinb_PIM9hqc5tiE0=(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qfrqndb4sEqfIeaidxU7SUw==, List`1 #=qUvaKN72ccwmOqp_biGvqPg==, Boolean #=qFdzdQXeROYVJvQuDQCmTtg==, List`1 #=q2sNy$fBiuycHnAeK2iljvQ==, #=qCiuJIBZrhEzfgLnfBgkgqKPhMe5$ttArFNtNAuKhNAs= #=qxN_55WA0xEJsPIO8of3Z6g==, Boolean #=q67iz9AlsFZ505$e7YePuQQ==)
   at MusicBee.Media.File.Tagging.#=q3Cu9SrnMaI30zN9cdj$7bg==.#=qhb9aklekV6xQhV1ick7$Dw==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qLxLcgsr8KF94flqOu6sQyw==, List`1 #=q0M4fHt542oQdPJVy_nSyTQ==)
   at MusicBee.Media.File.#=qa8WmNY2$7GsCTtYY7eeQuA==.#=q8x75j4LQqG8qpkM4DNmZug==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=q04Wsr3WgchflYoq4M9KI7w==, List`1 #=q_thh$uzd6Shz$KthF5mS$g==)
   at MusicBee.Media.File.#=qhNiwMrUbo8UntzdYkSopnA==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qEXzWXCy4Drv9sqaAZzrjKQ==, List`1 #=qAQBysU4r74GjD7$DWcwovw==)
   at #=qWeF$mQrEqw9hRKKgLzejpNChsGdtcNK9pr1q0g5FeJs=.#=q9gRMxMvkd39i5Ez9XBtCOw==(#=qkTasL8dsZ6JWDx2NytSqxyAuRQ5LiYnVdeLLEMf4fXA= #=qb3$PnyUCsGjMq1I1dBtjvQ==, List`1 #=ql47ghZho6uQrs3HXON6Xbw==)
   at #=qqOhFRUOH0GvU5$xoGffr3RI87kwpuh5xhTCQWfGBkv4=.#=qjxxVw5wgEJN1Wr95D4fR3wTvY92v$htlhnlpfMsFjGs=.#=qR_IC74Mk1ID3k7kWLXXDBw==(#=qIvMEl5$IzxmNl4zmdjBD2yzvkvVNkeg8PTvLCCp2XX3bPvrnGHWTz09rrNvsOUtF #=qvZC4tlg4Lk$wZLVgci8bZA==, Boolean #=qIjsRvLoI$Xt3Ruzf$vNAbw==, List`1 #=qNa0Ax8cQV03R_McQE6BqwA==, List`1 #=qI9xflfNH3X4vMRYqgrArKo7TuSO1qT5StbMmhQ_LxMk=)
   at #=qqOhFRUOH0GvU5$xoGffr3RI87kwpuh5xhTCQWfGBkv4=.#=qjxxVw5wgEJN1Wr95D4fR3wTvY92v$htlhnlpfMsFjGs=.#=q1lKj2b760DLQBdeTNlH_5MEBf8_5TnCeoaH02DMoCew=()
   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 March 03, 2017, 05:14:00 AM
i think its not plugin. this plugin version will skip tracks in the inbox when it makes backup. i think its new stable version (don't run it with debug version of mb otherwise you will continue to receive errors):

http://www.mediafire.com/file/jh415jnt9hqiuin/mb_TagTools_2017-03-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 16, 2017, 08:17:46 PM
I copied the preset "TOY: 'Change case' command - Title Case" and created two new presets based on the original. One is for Title and the other is for Album. Both are auto-applied and both ask for confirmation.

As I edit each one I'm getting the following error, but not 100% of the time, but maybe half the time. It doesn't seem to cause any problem with the new presets, but I'm wondering what's going on.
Code
MusicBee v3.1.6283.38016 (Win10.0), 16 Mar 2017 15:08:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.askConfirmationCheckBox_CheckedChanged(Object sender, EventArgs e)
   at System.Windows.Forms.CheckBox.OnCheckedChanged(EventArgs e)
   at System.Windows.Forms.CheckBox.set_CheckState(CheckState value)
   at System.Windows.Forms.CheckBox.set_Checked(Boolean value)
   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.NativeRemoveAt(Int32 index)
   at System.Windows.Forms.ListBox.ObjectCollection.SetItemInternal(Int32 index, Object value)
   at System.Windows.Forms.ListBox.ObjectCollection.set_Item(Int32 index, Object value)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.editPreset(Preset tempPreset, Preset originalPreset)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.buttonEdit_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)
Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 17, 2017, 03:57:00 AM
In addition to the error being thrown (reported just above) those newly created presets are being triggered just about every time I edit a tag or add lyrics even when the Title or Album tag already has the proper case. Is that the way it's supposed to work? I would expect it would check the case and only ask for confirmation if/when the case needed to be updated. If this is as expected, then I guess I can just turn off confirmation.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2017, 05:19:17 AM
In addition to the error being thrown (reported just above) those newly created presets are being triggered just about every time I edit a tag or add lyrics even when the Title or Album tag already has the proper case. Is that the way it's supposed to work? I would expect it would check the case and only ask for confirmation if/when the case needed to be updated. If this is as expected, then I guess I can just turn off confirmation.
there is no way in mb api to determine which tags were changed. if its *very* important for you i can add check before confirmation if preset is actually changing anything. as for error i will look into it.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 17, 2017, 01:40:58 PM
there is no way in mb api to determine which tags were changed. if its *very* important for you i can add check before confirmation if preset is actually changing anything. as for error i will look into it.
Not necessary as it's not that important. It's much easier to simply disable the request for confirmation. Then whatever needs to get changed gets changed and I don't even have to think about it. But thanks for offering.
Title: Re: Additional Tagging and Reporting Tools
Post by: M.O.Z.G on March 21, 2017, 06:46:52 PM
Some bugs with TagTool plugin when MB start minimized to Mini/Compact Player. After it the configuration window, creating presets, and may be something else that I didn't check, doesn't work. Each module had launched with errors also. I place some logs from different versions below:

Code: "AT&RT 4.18.6162.4867 on MusicBee 3.0.X.X"
3/21/2017 8:55:08 AM - 6.1.7601.65536 - 3.0.6132.15853 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
   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 System.Windows.Forms.Control.Invoke(Delegate method)
   at MusicBeePlugin.Plugin.ReceiveNotification(String sourceFileUrl, NotificationType type)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at MusicBee.Plugin.#=q8RoorlQ8HIg85T6khe4eDptctZs9uZqlk1FqeoNVSVs=()


Code: "AT&RT 4.18.6270.19414 on MusicBee 3.1.X.X"
3/21/2017 7:19:27 PM - 6.1.7601.65536 - 3.1.6287.39764 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ObjectDisposedException: Cannot access a disposed object.
Object name: '#=qd3gb_2djDMcwA57Pndq3gxbiMU3kKCarJlFTyaaZXsY='.
   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.Form.ShowDialog(IWin32Window owner)
   at System.Windows.Forms.Form.ShowDialog()
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at MusicBee.Plugin.#=qyt0FUH9HPXzxojc6MBE8Jw==(IntPtr #=qepWpJlE8RxvBAk$uFMD8oQ==)

When MB start in Normal view or minimized to Tray/TaskBar - no errors. After manual minimization to Mini/Compact Player - too.
Title: Re: Additional Tagging and Reporting Tools
Post by: cublikefoot on March 21, 2017, 08:25:12 PM
I'm getting an error when trying to paste tags from clipboard. I'm trying to copy tags from MP3 files and paste them onto FLAC files (just tested FLAC to FLAC and same issue). It only manages to paste the tags of the first file before giving this error:

Code
MusicBee v3.1.6275.38881 (Win10.0), 21 Mar 2017 15:19:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBee.Plugin.#=qjKWbvhPGx5RULOcCYsjzzEuaNdPK_prWLbOIScrjDgI=(String #=qRgLyhqFOcd1lxTyMriCq$A==, Int32 #=qAzAgFwi$uZV1l0Hr_0$Luw==, String #=qLXYFnmDm856gHOeOJD6u3Q==)
   at MusicBeePlugin.Plugin.SetFileTag(String sourceFileUrl, MetaDataType tagId, String value, Boolean updateOnlyChangedTags)
   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()

I'm using the default fields for "tag set 1" when copying the tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2017, 07:19:51 AM
sorry for being late. will look at new issues during couple of days.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 24, 2017, 06:02:51 PM
some bug fixes:

http://www.mediafire.com/file/43gqu2dgqgfo3b5/mb_TagTools_2017-03-24.zip

@cublikefoot
its mb bug. unselect all new sort-tags and "original year", "original artist" tags until its fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 25, 2017, 12:07:22 PM
@cublikefoot

its fixed now:

http://musicbee.niblseed.com/V3_1/MusicBee31_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: M.O.Z.G on March 26, 2017, 07:45:25 AM
some bug fixes:

http://www.mediafire.com/file/43gqu2dgqgfo3b5/mb_TagTools_2017-03-24.zip

The issue with minimization on startup is still there.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2017, 01:28:50 PM
try this version:

http://www.mediafire.com/file/y4738budi6rtgax/mb_TagTools_2017-03-28.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: M.O.Z.G on March 28, 2017, 02:19:34 PM
try this version:

http://www.mediafire.com/file/y4738budi6rtgax/mb_TagTools_2017-03-28.zip


Thank you for the reply! It works after minimized start now. But tagTool works only when MB is maximized. When we try to run some module (or open config window) from context menu in Compact/Minimized view - it still shows the error.

Code
MusicBee v3.1.6293.19583 (Win6.1), 28 Mar 2017 15:37:

System.ArgumentNullException: Value cannot be null.
Parameter name: value
   at System.ComponentModel.ComponentResourceManager.ApplyResources(Object value, String objectName, CultureInfo culture)
   at System.ComponentModel.ComponentResourceManager.ApplyResources(Object value, String objectName)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.InitializeComponent()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin..ctor(Plugin tagToolsPluginParam)
   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: boroda on April 03, 2017, 03:17:24 AM
its fixed:

http://musicbee.niblseed.com/V3_1/MusicBee31_Patched.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 03, 2017, 04:51:23 PM
new plugin beta version:

http://www.mediafire.com/file/pjwa895r2rnuke7/mb_TagTools_2017-04-03.zip

now any asr preset can be used as virtual tag function (also as a function in file organization templates, etc.).

go to main asr window, select preset and define virtual tag function id (any string containing a-z chars, numbers and symbols . : - _ ).

then use function

Code
$ASR(<URL>,preset_id)

where preset id is the id entered in asr window. asr preset function will return last written tag in preset. to see last written tag click 'edit/rename' button in asr window or (if 'edit/rename' is disabled) click 'copy' button and view the content of preset copy. most preset functions will return exactly what you expect.

still to do: add support for auto library report presets.

p.s. you need mb latest patch.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 05, 2017, 12:02:33 PM
I've never been sure if this is a bug or not, so I finally decided to just post this  :-\
When you 'Preview' an ASR on selected files
(http://i.cubeupload.com/s0zYi9.jpg)
The checkboxes on the LH side can't be un-ticked for individual tracks.
It's either all ticked or all un-ticked
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2017, 12:28:43 PM
Bee-liever, i already don't remember this, but i would say its a bug. will look into it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2017, 03:15:23 PM
http://www.mediafire.com/file/cn581l75mxq3neo/mb_TagTools_2017-04-05.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 06, 2017, 12:06:53 AM
Thank you boroda74
Title: Re: Additional Tagging and Reporting Tools
Post by: sashi79 on April 22, 2017, 03:44:55 PM
Today I tried to download the tagging tool of the above named and everytime I clicked on download a new advertising page oben in the end I had 5 ad pages for each click. Hence I gave up.
I find this not to be very professional and as a negative touch to it. I therefore advice to change the download options in a way that is acceptable. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on April 22, 2017, 04:10:50 PM
Today I tried to download the tagging tool of the above named and everytime I clicked on download a new advertising page oben in the end I had 5 ad pages for each click. Hence I gave up.
I find this not to be very professional and as a negative touch to it. I therefore advice to change the download options in a way that is acceptable. Thanks!
Its up to boroda74 if he wants to take your advice, but a number of the plugin developers and musicbee itself use mediafire.com because its free to host files for the developer without restrictions other hosting sites have. Personally i have never had a problem with mediafire but i guess you were unlucky.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 22, 2017, 06:08:23 PM
mediafire.com never failed me. maybe some temporary bugs on the site. have tried to download 2017-04-05 version right now and have had no problems.
Title: Re: Additional Tagging and Reporting Tools
Post by: alec.tron on April 23, 2017, 01:04:15 AM
Uneducated guess - boroda74 & Steven use a PupUpBlocker in their browser, sashi79 is not maybe - hence the different perceptions...?
Just a thought.
c.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 23, 2017, 09:04:10 AM
i've disabled adblock when i was testing download.

n.b. i do accept voluntary donations via paypal from the links on main mb site, but i dont earn money on mediafire.com. just have never seen free file hosting site without ads.


edit:

i think i'll make a backups of all my plugins on google drive for similar cases.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 24, 2017, 10:34:52 AM
new version. seems to be stable.

http://www.mediafire.com/file/w778d772lle3uy4/mb_TagTools_2017-04-24.zip

source:

http://www.mediafire.com/file/0t502gd61f7fwv4/TagTools_2017-04-24.rar

i have added new virtual tag function: $ALR(<URL>,function_id)

open auto-library reports window, create one or several presets, each with one or several aggregate functions and assign a function id for functions. probably you will want to write all aggregate functions to <null> tag (i.e. do not write them to custom tags).

example: how to display the number or tracks per artist of every track.

create new alr preset, add 'artist' grouping field, then add 'count(url)' aggregate function. assign some_function_id to the preset. save preset.
create virtual tag with formula: $ALR(<URL>,some_function_id), add this virtual tag to the main view. done.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 25, 2017, 05:08:11 PM
new beta version:

http://www.mediafire.com/file/gjrd3cq6deroq7o/mb_TagTools_2017-04-25-beta.zip



i've replaced obsolete mb api functions by new more efficient and quick api functions. not sure though how much overall performance is increased.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on April 25, 2017, 06:01:12 PM
It seems you may have created something very powerful with the $ALR function. I think it would benefit people if you or someone created some more detailed examples and also provided the steps needed to do them. I am sure you would get much more appreciation for what you have done - for myself i didnt realise its potential until saw the brief example of an aggregate artist track count.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 25, 2017, 06:19:10 PM
yes, i agree. maybe somebody could request some statistic info and i'll prepare more examples. all i can do without this is pre-create alr presets based on the (not auto) 'library reports' 2 existing predefined presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 25, 2017, 06:27:55 PM
i've copied 'library reports' command description from the wiki. alr (and alr virtual tag functions) has exactly the same functionality, only ui is slightly different, but these instructions and examples are totally applicable to alr.

edit:

i've slightly adopted instructions for alr. will adopt them more later.

------------------------------------------------------------------------

ALR virtual tag functions allow to gather and display in the main panel some library statistics for currently displayed tracks.

NOTE 1:

Main ALR window supports for two types of fields: grouping tags and aggregated functions. Every aggregated function is calculated for every unique combination of grouping tags. 'Count' function counts the number of different values of a given (function parameter, not grouping) tag. Other functions are obvious and should be applied only to numeric or duration (parameter) tags (e.g. 'Time', 'File size', etc.).

NOTE 2:

All ALR virtual tag function are calculated, updated and displayed dynamically.

NOTE 3:

For all aggregated functions except for 'Count' function please make sure that all (parameter) tag values used by function have the same measurement units (KB, MB, etc.) or adjust units in 'Edit/Preferences/Plugins' window (not required if both MusicBee and Windows localizations are English or Russian).

EXAMPLE 1

If you want to get the number of albums of artist of displayed track, i.e. the number of albums (function 'Count' of (parameter) tag 'Album') per artist (tag 'Album Artist'), you should add grouping tag 'Album Artist' in the table and required function 'Count(Album)'. Assign some_function_id to this aggregated function. Create virtual tag with formula $ALR(<URL>,some_function_id). Add this virtual tag to the main panel.

EXAMPLE 2

If you want to get the number of releases of artist (of displayed track) per year (of displayed track), i.e. the number of albums (function 'Count' of (parameter) tag 'Album') per year (tag 'Year') per artist (tag 'Album Artist'), you should add grouping tags (in order) 'Album Artist' and 'Year' in the table and required function 'Count(Album)'. Assign some_function_id to this aggregated function. Create virtual tag with formula $ALR(<URL>,some_function_id). Add this virtual tag to the main panel.

EXAMPLE 3

If you want to get the total duration of all tracks of artist of displayed track, i.e. the sum of track durations (function 'Sum' of tag 'Time') per artist (tag 'Album Artist'), you should add grouping tag 'Album Artist' and function 'Sum(Time)'. Assign some_function_id to this aggregated function. Create virtual tag with formula $ALR(<URL>,some_function_id). Add this virtual tag to the main panel.

See two predefined presets 'LIBRARY TOTALS' and 'LIBRARY AVERAGES' of (not auto) 'Library Reports' command for more examples.

ALR virtual tag functions are even more useful if they are used in grouping header in 'Albums and Track' view:

(https://www.mediafire.com/convkey/db1e/x536dw67abu9txj7g.jpg) (https://www.mediafire.com/view/?x536dw67abu9txj)
Title: Re: Additional Tagging and Reporting Tools
Post by: noose6767 on May 10, 2017, 04:41:03 PM
Please can anyone help me with a problem I am having exporting track rating ?. For some of my albums when I preview/export them from Library report the Rating column for all tracks is showing as the same value (e.g 2) but Musicbee shows the rating as a combination of 2,3,4 stars etc. I have the "Store rating in music file" property enabled but disabling that, re-tagging the ratings to different values etc. makes no different, the rating in Library Report stubbornly stays set to 2 for all tracks. Any ideas what's going on and how I get Library Report to reflect what I am seeing in Muscbee ? Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: Havokdan on May 10, 2017, 10:11:34 PM
Does MusicBee show in the application what version of the plugin that user is using?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 11, 2017, 03:26:11 AM
Does MusicBee show in the application what version of the plugin that user is using?
Preferences > Plugins > Additional Tagging Tools > Configure.
Version is at the bottom.
Title: Re: Additional Tagging and Reporting Tools
Post by: Havokdan on May 11, 2017, 10:29:51 AM
Does MusicBee show in the application what version of the plugin that user is using?
Preferences > Plugins > Additional Tagging Tools > Configure.
Version is at the bottom.

Thanks, I think it should have also in the plugins section of the player as well.
Title: Re: Additional Tagging and Reporting Tools
Post by: Cormac1902 on May 11, 2017, 08:13:58 PM
Hey, does this work with v3.0.6335 of MusicBee? When I try to load it it says "Unable to load this plugin: Exception has been thrown by the target of an invocation."

Great work on it btw! Never had any issues before.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2017, 07:06:26 AM
Please can anyone help me with a problem I am having exporting track rating ?. For some of my albums when I preview/export them from Library report the Rating column for all tracks is showing as the same value (e.g 2) but Musicbee shows the rating as a combination of 2,3,4 stars etc. I have the "Store rating in music file" property enabled but disabling that, re-tagging the ratings to different values etc. makes no different, the rating in Library Report stubbornly stays set to 2 for all tracks. Any ideas what's going on and how I get Library Report to reflect what I am seeing in Muscbee ? Thanks
can you pm me the link to one of problematic files (*not* 2-stared and rated with 'store ratings in music files' enabled)?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 14, 2017, 07:11:52 AM
Hey, does this work with v3.0.6335 of MusicBee? When I try to load it it says "Unable to load this plugin: Exception has been thrown by the target of an invocation."

Great work on it btw! Never had any issues before.
not the latest version of plugin (which requires latest mb 3.1 patch). if you prefer to use mb 3.0 go to plugin download page and redownload plugin from there.
Title: Re: Additional Tagging and Reporting Tools
Post by: Rambostyne on May 15, 2017, 04:37:27 PM
Hey, does this work with v3.0.6335 of MusicBee? When I try to load it it says "Unable to load this plugin: Exception has been thrown by the target of an invocation."

Great work on it btw! Never had any issues before.
not the latest version of plugin (which requires latest mb 3.1 patch). if you prefer to use mb 3.0 go to plugin download page and redownload plugin from there.
Second edit: Disregard this post. Just a case of confusion on my end.

I have this same issue. I use the pugin for its autorate features and noticed it stopped working after the latest MB update. Just now, I updated the plugin and MB gave me the same message as above. Well, what am I to do? Revert to an earlier version of MB? If so, how? On their download page I only see the latest version. Or are you planning on updating the plugin so its compatible with MB again? The autorate feature saved me a considerable amount of time, especially since most of my playlists rely on ratings. I can't go back to doing it manually.

Edit: I did find where to download earlier versions of MB, however, after downloading and installing it says its still using version 3.0.6335. So I suppose I'd have to uninstall my current version first in order to downgrade. I suppose I'll just wait for the plugin to catch up to the newest version of MB.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 15, 2017, 04:56:55 PM
What boroda74 is saying is that in order to use the current version of the plugin, you have to have MB 3.1, which you can get from my sig. You don't have to uninstall anything.

He is also saying that if you want to stay on 3.0, you have to go to the -plugin- download page and redownload from there.
Title: Re: Additional Tagging and Reporting Tools
Post by: Rambostyne on May 15, 2017, 05:01:36 PM
What boroda74 is saying is that in order to use the current version of the plugin, you have to have MB 3.1, which you can get from my sig. You don't have to uninstall anything.

He is also saying that if you want to stay on 3.0, you have to go to the -plugin- download page and redownload from there.

I just figured this out. Everything is fine now. I didn't realize that he was saying all we needed was the 3.1 patch. I'm used to the program automatically updating and never having to worry about it.

My apologies for the confusion and thank you for the awesome plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 19, 2017, 04:37:26 PM
new command is added: compare tracks. this command provides easy way to compare tags of 2 (or more) tracks.

http://www.mediafire.com/file/ly0fxnvdnf3aq3a/mb_TagTools_2017-05-19.zip

source:

http://www.mediafire.com/file/ihmlyqyjb8y77g7/TagTools_2017-05-19.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 19, 2017, 09:09:50 PM
new command is added: compare tracks. this command provides easy way to compare tags of 2 (or more) tracks.
Great idea!! Thanks for implementing this.
However (you just knew there would be a however, didn't you?)

In a few tests tag data is not populating the correct tags. Note that the following tags are incorrect:
BPM, Composer, Genre, Sort Album Artist, Work.  (Composer in these two tracks is blank; info in "Work" is from Comments; Sort Album Artist shows BPM; Genre shows Artist
(http://i.imgur.com/Jsj7dvyl.jpg) (http://i.imgur.com/Jsj7dvy.jpg)
In some further testing, BPM is -never- in the correct place, and not always in the same place. But it's most everything else that's not correct either.
Let me know if there's anything I can do to help you troubleshoot this.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 19, 2017, 10:12:30 PM
However (you just knew there would be a however, didn't you?)
i was sure :) and its very pity that i have marked this version as stable too early. will look at the issues.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 19, 2017, 11:00:49 PM
i was sure :) and its very pity that i have marked this version as stable too early. will look at the issues.
Thanks for looking into it.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 23, 2017, 02:09:49 AM
Persistent windows have disappeared in the latest version (2017-05-19)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 23, 2017, 07:54:02 AM
thanks, forgot to reenable them.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 24, 2017, 01:45:44 PM
new command is added: compare tracks. this command provides easy way to compare tags of 2 (or more) tracks.
Great idea!! Thanks for implementing this.
However (you just knew there would be a however, didn't you?)

In a few tests tag data is not populating the correct tags. Note that the following tags are incorrect:
BPM, Composer, Genre, Sort Album Artist, Work.  (Composer in these two tracks is blank; info in "Work" is from Comments; Sort Album Artist shows BPM; Genre shows Artist
(http://i.imgur.com/Jsj7dvyl.jpg) (http://i.imgur.com/Jsj7dvy.jpg)
In some further testing, BPM is -never- in the correct place, and not always in the same place. But it's most everything else that's not correct either.
Let me know if there's anything I can do to help you troubleshoot this.

(with caution :)) new version seems to be a bit less buggy. persistent windows are also fixed:

http://www.mediafire.com/file/6g8oo2wkxfn88dc/mb_TagTools_2017-05-24.zip

source:

http://www.mediafire.com/file/ofjw9ba7750ovy6/TagTools_2017-05-24.rar
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 24, 2017, 07:57:43 PM
(with caution :)) new version seems to be a bit less buggy. persistent windows are also fixed:
Working well. I like the addition of artwork. Tags now seem to be placed where they belong. And the window is indeed persistent.

Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: Rambostyne on June 03, 2017, 10:41:31 PM
Is anyone aware of there being any issue with the "last played" and "play count" data not updating? I only just noticed this today as I was playing any tracks with an "unknown" last played date. After playing through a few dozen songs, I noticed that about 10% hadn't updated in those two columns. A quick search led me back to this thread where somebody once brought this up in the past, but borada74 was unable to reproduce the results. I have not observed any similarities in the situations in which a file does not update, nor do I utilize any other plugins. When I've replayed the tracks to see if they will update, they usually do, but still not every time.

Update: I spent the rest of the day trying to figure out why it's randomly choosing not to update approximately every 1 out of 5 tracks. I'm also now wondering how long this has been going on. The only reason I noticed today was because I was exclusively playing tracks with an "unknown" last played time. But it does seem to only happen when I'm not watching the program. I'll have it open, not minimized, but behind other programs and I'll come back to it and see that several songs in a row didn't update. But if I keep the program in front of others, this still happens, but less frequently.

That's all I've come up with.

Second Update: Today I tried it with the "auto rate songs automatically if they are played" option turned off. Problem solved.
Title: Re: Additional Tagging and Reporting Tools
Post by: alec.tron on June 05, 2017, 11:55:14 PM
There's a potential bug report about ASR & hotkey assingment here:
https://getmusicbee.com/forum/index.php?topic=22031.0
c.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 12, 2017, 04:59:30 AM
Virtual 22 tag is not available for copy tag command.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 12, 2017, 06:12:47 AM
thanks, redwing:

http://www.mediafire.com/file/7qletb9v2d4erym/mb_TagTools_2017-06-12.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 12, 2017, 06:29:34 AM
Thanks for the fix!
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on June 12, 2017, 06:07:59 PM
<Artist: Guest> is not showing up among the selectable fields within the "Replace with:" box (red arrow) whereas it is selectable in the "Search for:" box.

In Musicbrainz, featuring artists were included in the title in the past (as displayed on the CD tray for example).  However, they recently changed their policy to move that info in <Artist>, as seen in the following (<Artist> - <Title> format):

Before Musicbrainz change: Artist - Title (feat. Guest Artist)
After Musicbrainz change: Artist feat. Guest Artist - Title

The change is necessary for Musicbrainz's db purposes but it leads to sorting issues if one sorts by <Artist>.  I've been trying to do the following with "Foo feat. Bar - Title"

Example (<Artist> - <Title>): Foo feat. Bar - Title
From Musicbrainz:
<Artist> = Foo feat. Bar
<Title> = Title

Replacement:
<Artist> = Foo
<Artist: Guest> = Bar
<Title> = Title (feat. Bar)

This is shown below.  I cannot complete the Replacement because <Artist: Guest> is not selectable among the fields available within the "Replace with:" box.

(http://i.imgur.com/bhdPGOF.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on June 13, 2017, 10:44:21 AM
its the limitation of mb api, but there is a workaround: try to write all involved people to 'artist' tag, split them by '\@char(0)' function and add function '\@char(1)' *before* the name of guest artist.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on July 28, 2017, 02:20:22 PM
I noticed this plugin makes all album covers flickering on MB's startup (in all views). If I disable it, it doesn't happen.
I have not enabled any presets for auto-applying. Simply enabling/disabling the plugin makes the difference. Open the plugin tab in preferences and try enabling it, then you will see that enabling makes covers flickering.
Title: Error report after change of custom tags
Post by: WimYogya on August 12, 2017, 08:14:04 AM
I got this error message:

MusicBee v3.1.6420.28372 (Win6.1), 12 Aug 2017 14:00:

System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalDelete(String path, Boolean checkHost)
   at System.IO.File.Delete(String path)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.saveSettings()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.buttonSave_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)


Don't know what it means.
It happened after I renamed a number of my custom tags. That was necessary due to the new layout of the tag (2) screen.
There seems something wrong with custom tage 9.

When performing an ASR command the popup says:
Some tage names are duplicated. See (...)tagtools.tagnameserrorlog.txt for details. The plugin is not properly initialized.
The message there says: Cant add Custom 9 / Custom9


What does it mean? What should I do?
Or is a bug fix necessary first?

Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on September 03, 2017, 05:08:39 AM
i have added new virtual tag function: $ALR(<URL>,function_id)

This is absolutely awesome, thanks!  :D

(http://i.imgur.com/z0HAKRD.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on September 03, 2017, 05:13:57 PM
Hi Boroda,
Since a few months (after updating MB to version 3.1.5900 or so, I have problems with ONE of your ASR commands.
I created one to copy my virtual file PERFORMERS-VIRTUAL to PERFORMERS.
The virtual file itself is the sum of categories like vocalist-main, vocalist-other, instrumentalist, choir, orchestra, director (for classical works).
Once I have filled them in all, I want to put them in the PERFORMERS field which in the column viewer displayes all 'involved people'.

It still works as before - with ONE annoying exception:
The target field for the merging result of fields PERFORMERS-VIRTUAL + MOOD is always set to VOCALS-MORE - not by me, I don't use it for that purpose. MANUALLY i can enter the correct target field: PERFORMERS and then execute the command properly.

But if I want to SAVE the new settings, I get an MB error message - and the target field can NOT be changed.
This is the error message:

System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.

What to do?
Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on September 09, 2017, 04:18:14 PM
@Boroda74...

Maybe this is an oversight, or perhaps it's me, but in the "Remove # characters from the beginning/end of <Tag 1>" preset, there doesn't appear to be a place to indicate the number of characters to remove. Nor does there appear to be a place to indicate if the removal is to be from the beginning or the end.

Hmmm ... on further inspection, I found preset "Remove given number of characters from beginning/end of <Tag 1>" which does what I expect. Perhaps this preset replaced the one I mentioned above? And the first one should be removed.

Thanks for clarifying.
Title: Re: Additional Tagging and Reporting Tools
Post by: evankap on September 17, 2017, 08:05:22 PM
Hi all

fyi1: Great add-in!

fyi2: I was not able to find a related post, hence this topical post.

I noticed when using the Additional Tagging add-in, specifically the Copy and/or Swap Tags features, not all tag fields are available.

For example, I'd like to copy all of my "YEAR (YYYY)" tags to the tag "Original Year" but "Original Year" is not in the list of "swappable" tags. It seems like perhaps this is an omission.

Is this something that can be added?

Thanks
evan
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on September 20, 2017, 11:30:17 AM
Hi Boroda,
Since a few months (after updating MB to version 3.1.5900 or so, I have problems with ONE of your ASR commands.
I created one to copy my virtual file PERFORMERS-VIRTUAL to PERFORMERS.
The virtual file itself is the sum of categories like vocalist-main, vocalist-other, instrumentalist, choir, orchestra, director (for classical works).
Once I have filled them in all, I want to put them in the PERFORMERS field which in the column viewer displayes all 'involved people'.

It still works as before - with ONE annoying exception:
The target field for the merging result of fields PERFORMERS-VIRTUAL + MOOD is always set to VOCALS-MORE - not by me, I don't use it for that purpose. MANUALLY i can enter the correct target field: PERFORMERS and then execute the command properly.

But if I want to SAVE the new settings, I get an MB error message - and the target field can NOT be changed.
This is the error message:

System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.


Hello Boroda,

My post above did not get any reply yet.
In the meantime I noticed the issue is NOT restricted to my specific pair of column settings that can not be saved. It happened in a few other cases as well.
Please have a look.
Why can settings not be changed AND saved??

Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on October 02, 2017, 02:26:08 PM
Hi @boroda

My repeated support request did not get any reply.
See below.
Is there any problem with it?

Please inform, thank you.
Greetz,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on October 02, 2017, 07:24:26 PM
ATTN: All who are waiting for replies from boroda74...

Note that boroda74 hasn't logged on to the forum since mid-July 2017.

Please don't repeat messages that you posted which haven't been replied to as that just clutters up things.
Title: Re: Additional Tagging and Reporting Tools
Post by: Camzo on October 14, 2017, 10:30:44 PM
Is anyone else having issues with advanced search & replace not working on 3.1? I can click it but nothing opens. Most of the other tools seem to work fine except the one I use the most funnily enough...  :(
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on October 15, 2017, 12:54:37 AM
@ Camzo
Have you tried updating to the 3.1 version of the plugin?
Title: Re: Additional Tagging and Reporting Tools
Post by: Camzo on October 15, 2017, 01:36:01 AM
@ Camzo
Have you tried updating to the 3.1 version of the plugin?

I believe so. The version I have is 2017-06-12. I think it's the latest?
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on October 15, 2017, 10:57:12 AM
The version I have is 2017-06-12. I think it's the latest?
I think it's the latest too.  At the very least, it's the same one I'm using  ;D

Try disabling the plugin from Preferences
Re-start MB and then re-enable the plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: Camzo on October 15, 2017, 11:37:29 AM
The version I have is 2017-06-12. I think it's the latest?
I think it's the latest too.  At the very least, it's the same one I'm using  ;D

Try disabling the plugin from Preferences
Re-start MB and then re-enable the plugin.
Managed to figure out a a solution along the same vein as what you suggested. I uninstalled it through musicbee then went and removed any traces of files it had left behind in both programfiles(x86) and %APPDATA%. It seems to be working now.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 23, 2017, 08:39:43 PM
Tried $ALR function for album size: selecting Album and Sum(Size). It works and the virtual field shows the value correctly for each track. But the problem is it almost freezes the UI with high CPU usage. At MB's start, I see it finishes the ALR update 100% from the status bar, but why it gets sluggish right after that with nothing to compute? Looks like a bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 21, 2017, 08:50:16 AM
Tried $ALR function for album size: selecting Album and Sum(Size). It works and the virtual field shows the value correctly for each track. But the problem is it almost freezes the UI with high CPU usage. At MB's start, I see it finishes the ALR update 100% from the status bar, but why it gets sluggish right after that with nothing to compute? Looks like a bug.

Update on this. The freezing comes from ticking either auto-calculate setting or auto-apply tickbox for a preset. If I do not tick both tickboxes I don't get such freezing, but still it can't show the tag values stably. I get a completely empty main panel for a tab with that column added.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on November 25, 2017, 06:59:49 AM
Hello,

Since Boroda74 has not logged in for a long time, would anybody else be able and willing to help me with the MB error message that I get when I try to change a setting that I can USE but not CHANGE PERMANENTLY?

This is the message:
System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.

I use this feature very often - and every time I have to change the existing setting 'vocals' into 'performers'.
Any trick to 'stick' it?

Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 25, 2017, 10:22:05 AM
System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.

You don't have permission to access the file. Google how to change permissions on files/folders.
BTW if you encounter such issues often, I'd recommend using a portable installation.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on November 25, 2017, 12:38:46 PM

You don't have permission to access the file. Google how to change permissions on files/folders.

I checked the permissions. I have all possible permissions, I think - including ownership...
Not very familiar with these matters, but that is what I see...

Could the problem perhaps be a corrupt file?
This is what happened:
I checked for the file with my program Everything. At the given location I found TWO files with that name but could NOT access them.
Deleting one of them did not help. And once one of the two were deleted, the given file could not be found inside the appdata folder.

Then I found the same file in one of my backup files. It could be accessed without a problem.
So I copy/pasted it to the appdata folder. Ran the preset again. Same error message: no access...

Any other solution?
Thanks...
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 25, 2017, 02:17:15 PM
Do you have the issue for only that preset or other presets as well (that are in your AppData folder)?
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on November 25, 2017, 03:31:57 PM
Found it - I think!
But do NOT understand how it could happen.
Problem was not the preset's permissions, but the fact that it had been set as READ ONLY.
For sure NOT by me: I didn't even know that such file existed.

After your question I experimented with other presets, found out that from within the AppData folder THOSE could be changed/saved.
Only 2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml could NOT be saved and the reason was given: READ ONLY.
So I removed the checkmark, tried new changes, and now it seems all ok.

It was a bit of a detour, but thanks to your suggestions and question I found the cause of the trouble.
Thanks a LOT!

Ciao!
Wim

PS:
If I may bother you with a new (recent) issue, can you tell me if you have the sorting problem as me:
The result of a click on the column header DATE ADDED does not give the expected result. It is confusing and messy. If I add 4 cd's of the same opera album ONE BY ONE in the order 1-2-3-4 the DATE ADDED result downwards should be 4-3-2-1, but it is not. Can be 2-4-3-1 or 3-1-4-2 or anything. Looks as if the sort order feature looks at the DATE only, not (correctly) at the TIME.
And one or more of the 4 cd's can even be displayed BELOW tracks that were added earlier in time...
Is that the same with you?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 25, 2017, 04:23:27 PM
The result of a click on the column header DATE ADDED does not give the expected result. It is confusing and messy. If I add 4 cd's of the same opera album ONE BY ONE in the order 1-2-3-4 the DATE ADDED result downwards should be 4-3-2-1, but it is not. Can be 2-4-3-1 or 3-1-4-2 or anything. Looks as if the sort order feature looks at the DATE only, not (correctly) at the TIME.
And one or more of the 4 cd's can even be displayed BELOW tracks that were added earlier in time...

If you just click on the Date Added column header, that will still take care of sorting tracks within each album, also affected by your view settings. To sort solely by date added, create a custom sorting with that field and select that as sort by setting in Tracks view.
Title: Message when invoking plugin in portable version
Post by: barlet on November 26, 2017, 04:03:56 PM
I am getting the message " Unable to initialise the plugin. Exception has been thrown by the target of an invocation." when trying to enable the additional tools in the portable version of MB version 3.1.6529. This message does not appear on the desktop version of the MB and the plugin works correctly. Can anyone please direct me to the file which may be creating this error message in the portable version?

Thanks a lot
Title: Re: Additional Tagging and Reporting Tools
Post by: cynflux on December 02, 2017, 04:15:41 AM
Getting the following error when attempting to add the plugin:

-----------------------------------------------

Unable to save due to the following error:
Found invalid data while decoding.

------------------------------------------------
Title: Re: Additional Tagging and Reporting Tools
Post by: gdog on December 08, 2017, 05:56:25 PM
New to the forum, and I apologize if I'm asking something that has already been answered. I read thru the thread and search all the forums and can't seem to find the same issue described.

I'm in the process of importing music into MB, and when I have some music sitting in the INBOX I use the "Auto-Tag by Track" - "Identify and Update Tags". That's fine, but now I want to add/append a new genre to all the music in the INBOX.  Note: I want to retain the auto-tagged genres - do not want to replace what is already there.

for Example
STARTING POINT
file name      -  Artist   -  Title   -  Genre
123.mp3      -  Alpha   -  123    -  Vocal
Shout.mp3   -  Bravo   -  Shout -  Rock
ABD.mp3     -  Charlie  -  ABD   -  R&B
xyz.mp3      -  Delta     - Xyz     -  Pop; R&B

DESIRED STATE, where I want to add a new genre called NEW GENRE
file name      -  Artist   -  Title   -  Genre
123.mp3      -  Alpha   -  123    -  NEW GENRE; Vocal
Shout.mp3   -  Bravo   -  Shout -  NEW GENRE; Rock
ABD.mp3     -  Charlie  -  ABD   -  NEW GENRE; R&B
xyz.mp3      -  Delta     - Xyz     -  NEW GENRE; Pop; R&B

I've tried using the "Copy Tag" feature of the ADDITIONAL TAGGING AND REPORTING TOOLS plugin, configurations:
- using "Append source tag to the end..." -  I end up with ->  Vocal; NEW GENRE; Vocal    <--  Note that now there are 2 entries of original  Genre in the Genre field
- using "Add source Tag to the beginning..." -- same issue of duped genre entries

Let me know if I'm missing something.
I'll also try to post a picture so people can see what I'm trying to do with my specific example and configuration settings.

Thx
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 10, 2017, 06:49:50 AM
I've tried using the "Copy Tag" feature of the ADDITIONAL TAGGING AND REPORTING TOOLS plugin, configurations:
- using "Append source tag to the end..." -  I end up with ->  Vocal; NEW GENRE; Vocal    <--  Note that now there are 2 entries of original  Genre in the Genre field
- using "Add source Tag to the beginning..." -- same issue of duped genre entries

The reason it gets duplicated is it copies the new value to each of the existing genre tag. It would be easily resolved if the command supported "<Genres>" field (rather than <Genre> tag) as a target tag, but it's not available currently.

As a workaround you can use a virtual tag.

Suppose you have new genre value in <Custom5> tag, then create a virtual as follows:

Code
$IsNull(<Custom5>,,<Custom5>"; ")<Genres>

Then add the virtual field to the main panel and verify if the tag value is what you want.

Now use Copy tag command from the virtual tag to genre tag after selecting files.
Title: Re: Additional Tagging and Reporting Tools
Post by: tangotonyb on December 12, 2017, 11:11:51 AM
I'm running the latest copy of plugin and musicbee, but there's a problem.

I used one of the functions in Adv Srch & Repl to modify the Title,adding (ex) to the end of the title for selected tracks.

Then later I noticed that whenever I edited a track's metadata using the STANDARD editor, the Title was also modified with (ex).

I used Adv Srch & Repl again to clean up the mess made and remove the excess (ex)'s.

Now when i try to add (ex) back for certain tracks in the Standard editor, I can't!

Only when I went back into Adv Srch & repl and unselected the template And clicked APPLY, was I able to edit my tracks without interference.

My guess is that whatever means you are using to inject the editing code into MusicBee is being left switched on when the Adv Srch & Replace window is closed.

Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on December 12, 2017, 11:44:24 AM
If you have the template ticked
(http://i.cubeupload.com/0qZdwC.jpg)
this means the template will be auto applied whenever tags change
Title: Re: Additional Tagging and Reporting Tools
Post by: tangotonyb on December 12, 2017, 02:50:54 PM
Well - yes I've figured that out, but that's surely a bug.

If intentional it's totally dumb as it's totally counter-intuitive. I cannot think of a use case in which such operation was desirable, yet there are lots of cases where it's undesirable!

It's fortunate I discovered this "feature" early on - I hate to think what would have happened if I'd done a radical operation in there intending it to operate on one file, and then done a bulk edit to add a new field.


If it's intended that the operation remain like this, then you NEED a warning on that GUI to state this is the case.







Title: Re: Additional Tagging and Reporting Tools
Post by: phred on December 12, 2017, 07:14:19 PM
Right at the very top of the window it states "Tick presets which should be automatically applied." It's pretty clear to me, and to almost all the other users of this plug-in since this is the first anyone has complained about it.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on December 12, 2017, 08:06:15 PM
And the fact that when you tick the preset, the two options
Auto apply preset only if track is contained in playlist
and
Ask confirmation before autoapplying this preset
are suddenly available to select, should have been a deadset giveaway that the preset was going to be auto applied.
Title: Re: Additional Tagging and Reporting Tools
Post by: tangotonyb on December 13, 2017, 02:11:48 PM
I see now that you do not need to tick an item in the list in order for the lower dialog to work - the screen in effect does two jobs.

The author has differentiated the two behaviours by referring to highlighting and ticking, however he uses "Select" to mean highlight - for many users confronted with a list of tick boxes and the instruction (select), they would tick the item.

The second sentence: "TICK PRESETS..." then makes no sense at all - mainly because the idea that an advanced tag edit screen would continue to operate behind the scenes when the dialog is closed is VERY unusual. I would suspect UNIQUE. Normally a user expects that when a dialog (except for those labelled settings/preferences/options) is closed, it ceases to operate. A "Search and Replace" dialog certainly falls into this category. It doesn't help that it's hard to imagine WHY someone would want it to behave in the way it does.

I should point out, I'm an experienced Software Tester - I've worked for Financial Organisations & Ecommerce developing desktop and web applications. I'm not clueless.
I approached this screen cautiously, to see what it did and how - operating on a playlist of a handful of tracks that I could easily replace if things went wrong.


SO at the very least, change the layout/wording on that screen to make it clear.

"HIGHLIGHT preset below to edit or apply to selected tracks. (In red) TICK presets you want to ALWAYS AUTOMATICALLY invoke whenever tags change in MusicBee."


On closing the dialog, if any remain ticked, a warning window should pop up to say (presets ticked -these will continue to be applied OK?)


These are simple changes to make and could save another user a lot of grief.




Title: Re: Additional Tagging and Reporting Tools
Post by: tangotonyb on December 13, 2017, 02:14:21 PM
And the fact that when you tick the preset, the two options
Auto apply preset only if track is contained in playlist
and
Ask confirmation before autoapplying this preset
are suddenly available to select, should have been a deadset giveaway that the preset was going to be auto applied.

"Ask confirmation before autoapplying this preset" - I don't see that option

Title: Re: Additional Tagging and Reporting Tools
Post by: tangotonyb on December 13, 2017, 02:19:13 PM
OK - I'm using the version linked to from https://getmusicbee.com/addons/plugins/49/additional-tagging-and-reporting-tools/ which I would have thought was the latest, but I can see now it isn't.

Suggest the download button on that page redirect to http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools with #Download if anchor exists.

Title: Re: Additional Tagging and Reporting Tools
Post by: tangotonyb on December 13, 2017, 02:35:18 PM
An error I get with both versions of the plugin:

Code
MusicBee v3.1.6546.37911 (Win6.1), 13 Dec 2017 14:22:

System.IO.FileNotFoundException: Could not find file 'C:\Users\Tony\AppData\Roaming\MusicBee\Tag Backups\DJ Music - Baseline.bbl'.
File name: 'C:\Users\Tony\AppData\Roaming\MusicBee\Tag Backups\DJ Music - Baseline.bbl'
   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)
   at MusicBeePlugin.BackupType.Load(String fileName, String backupFileExtension)
   at MusicBeePlugin.TagHistoryPlugin.fillTable(String folder, Boolean includeSubfolders, Int32 maxBackupCount, Int32 trackIndex, Boolean reuseCache)
   at MusicBeePlugin.TagHistoryPlugin.TagHistoryPlugin_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()
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 04:46:33 AM
I got this error message:

MusicBee v3.1.6420.28372 (Win6.1), 12 Aug 2017 14:00:

System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.InternalDelete(String path, Boolean checkHost)
   at System.IO.File.Delete(String path)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.saveSettings()
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.buttonSave_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)


Don't know what it means.
It happened after I renamed a number of my custom tags. That was necessary due to the new layout of the tag (2) screen.
There seems something wrong with custom tage 9.

When performing an ASR command the popup says:
Some tage names are duplicated. See (...)tagtools.tagnameserrorlog.txt for details. The plugin is not properly initialized.
The message there says: Cant add Custom 9 / Custom9


What does it mean? What should I do?
Or is a bug fix necessary first?

Thanks!

sorry for being late. this error means that you have 2 (mostly probably custom) tags with name 'custom9'
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 04:57:31 AM
Hi Boroda,
Since a few months (after updating MB to version 3.1.5900 or so, I have problems with ONE of your ASR commands.
I created one to copy my virtual file PERFORMERS-VIRTUAL to PERFORMERS.
The virtual file itself is the sum of categories like vocalist-main, vocalist-other, instrumentalist, choir, orchestra, director (for classical works).
Once I have filled them in all, I want to put them in the PERFORMERS field which in the column viewer displayes all 'involved people'.

It still works as before - with ONE annoying exception:
The target field for the merging result of fields PERFORMERS-VIRTUAL + MOOD is always set to VOCALS-MORE - not by me, I don't use it for that purpose. MANUALLY i can enter the correct target field: PERFORMERS and then execute the command properly.

But if I want to SAVE the new settings, I get an MB error message - and the target field can NOT be changed.
This is the error message:

System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.

What to do?
Thanks,
Wim
check write access for this file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 05:45:38 AM
@Boroda74...

Maybe this is an oversight, or perhaps it's me, but in the "Remove # characters from the beginning/end of <Tag 1>" preset, there doesn't appear to be a place to indicate the number of characters to remove. Nor does there appear to be a place to indicate if the removal is to be from the beginning or the end.

Hmmm ... on further inspection, I found preset "Remove given number of characters from beginning/end of <Tag 1>" which does what I expect. Perhaps this preset replaced the one I mentioned above? And the first one should be removed.

Thanks for clarifying.
working fine here. its 'custom text 1' which defines how many chars to remove. try to 'import all' presets again.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 05:48:31 AM
Hi all

fyi1: Great add-in!

fyi2: I was not able to find a related post, hence this topical post.

I noticed when using the Additional Tagging add-in, specifically the Copy and/or Swap Tags features, not all tag fields are available.

For example, I'd like to copy all of my "YEAR (YYYY)" tags to the tag "Original Year" but "Original Year" is not in the list of "swappable" tags. It seems like perhaps this is an omission.

Is this something that can be added?

Thanks
evan

'original year' has been added to mb very recently, so try to upgrade both mb and plugin to latest version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:00:33 AM
Tried $ALR function for album size: selecting Album and Sum(Size). It works and the virtual field shows the value correctly for each track. But the problem is it almost freezes the UI with high CPU usage. At MB's start, I see it finishes the ALR update 100% from the status bar, but why it gets sluggish right after that with nothing to compute? Looks like a bug.

Update on this. The freezing comes from ticking either auto-calculate setting or auto-apply tickbox for a preset. If I do not tick both tickboxes I don't get such freezing, but still it can't show the tag values stably. I get a completely empty main panel for a tab with that column added.
no freezing for me, but it takes abot 5 sec to alr column be filled (14000 files in my library).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:01:20 AM
System.UnauthorizedAccessException: Access to the path 'C:\Users\Wim\AppData\Roaming\MusicBee\ASR Presets\2acc97f0-bd50-476a-8f2a-680eedca8985.ASR Preset.xml' is denied.

You don't have permission to access the file. Google how to change permissions on files/folders.
BTW if you encounter such issues often, I'd recommend using a portable installation.
+1
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:03:17 AM

You don't have permission to access the file. Google how to change permissions on files/folders.

I checked the permissions. I have all possible permissions, I think - including ownership...
Not very familiar with these matters, but that is what I see...

Could the problem perhaps be a corrupt file?
This is what happened:
I checked for the file with my program Everything. At the given location I found TWO files with that name but could NOT access them.
Deleting one of them did not help. And once one of the two were deleted, the given file could not be found inside the appdata folder.

Then I found the same file in one of my backup files. It could be accessed without a problem.
So I copy/pasted it to the appdata folder. Ran the preset again. Same error message: no access...

Any other solution?
Thanks...

delete all presets, then try re'import all' presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:35:47 AM
Getting the following error when attempting to add the plugin:

-----------------------------------------------

Unable to save due to the following error:
Found invalid data while decoding.

------------------------------------------------

not sure when you are getting this error, but maybe zip is corrupted.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:38:36 AM
I am getting the message " Unable to initialise the plugin. Exception has been thrown by the target of an invocation." when trying to enable the additional tools in the portable version of MB version 3.1.6529. This message does not appear on the desktop version of the MB and the plugin works correctly. Can anyone please direct me to the file which may be creating this error message in the portable version?

Thanks a lot
actually there is no difference for plugin between portable and desktop version of mb. make sure you are using latest mb version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:47:59 AM
An error I get with both versions of the plugin:

Code
MusicBee v3.1.6546.37911 (Win6.1), 13 Dec 2017 14:22:

System.IO.FileNotFoundException: Could not find file 'C:\Users\Tony\AppData\Roaming\MusicBee\Tag Backups\DJ Music - Baseline.bbl'.
File name: 'C:\Users\Tony\AppData\Roaming\MusicBee\Tag Backups\DJ Music - Baseline.bbl'
   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)
   at MusicBeePlugin.BackupType.Load(String fileName, String backupFileExtension)
   at MusicBeePlugin.TagHistoryPlugin.fillTable(String folder, Boolean includeSubfolders, Int32 maxBackupCount, Int32 trackIndex, Boolean reuseCache)
   at MusicBeePlugin.TagHistoryPlugin.TagHistoryPlugin_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()
if you are trying to use autobackup feature then 1st create baseline backup manually.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 14, 2017, 06:49:43 AM
@redwing, phred, Bee-leiver, thank you for your assistance!
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on December 14, 2017, 06:12:50 PM
No problem at all. Great to see you back here!
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on December 15, 2017, 11:15:42 AM
@redwing, phred, Bee-leiver, thank you for your assistance!
Glad to help  :)

Great to see you back here!
Yes.  With the long absence, I was beginning to get worried...
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 16, 2017, 05:31:47 AM
I think you need to update the link on the add-on page. It doesn't support new fields introduced in v3.1.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 16, 2017, 07:03:36 AM
thanks, redwing. will have a look at this issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 16, 2017, 07:09:41 AM
done
Title: Re: Additional Tagging and Reporting Tools
Post by: barlet on December 16, 2017, 05:05:13 PM
I am getting the message " Unable to initialise the plugin. Exception has been thrown by the target of an invocation." when trying to enable the additional tools in the portable version of MB version 3.1.6529. This message does not appear on the desktop version of the MB and the plugin works correctly. Can anyone please direct me to the file which may be creating this error message in the portable version?

Thanks a lot
actually there is no difference for plugin between portable and desktop version of mb. make sure you are using latest mb version.

Hi I know there is no difference but somehow the one I installed on the external hdd is producing the error, while the one installed on the computer system hdd is not. I have tried to uninstall the plugin and install again but with no success. I think that one of the files on the external hdd is somehow corrupted but I cannot find which one. I use two versions since I have two distinct libraries and find it easier to keep them separated. Can you please help? I can send you screenshots if they help.

Btw the plugin is excellent and very useful.

Thank you for your time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 18, 2017, 04:52:36 AM
i'm afraid screenshots wont help in this case. have you tried to reinstall mb and plugins completely?
Title: Re: Additional Tagging and Reporting Tools
Post by: alec.tron on December 18, 2017, 10:03:56 PM
Great to see you back here!
Yes.  With the long absence, I was beginning to get worried...
+1
Welcome back boroda74!
c.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 21, 2017, 05:21:04 AM
Can you consider adding support for external cuesheet files with re-encode tag command? Then people won't have to rely on third-party apps for converting encoding of cuesheet. Would be great if it could convert multiple cuesheets at once. The user could check whether encoding will be all correct with preview screen.

Also it would be useful if the current source tag option had "All fields" because it's common encoding is getting wrong for all fields rather than a single field. Of course no need to include number tags to that.

One more thing. The current code page list makes no sense in its order and language. Have a look at this app's list:
https://sourceforge.net/projects/cp-converter/
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 21, 2017, 07:05:07 PM
i think that all tags are read-only for cuesheets.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 21, 2017, 07:26:42 PM
Of course it won't work without Steven's support.
Tag editor's Edit Cuesheet button can load the entire cuesheet. So load the entire cuesheet into the command's dialog thru it and convert the encoding for the whole text and save it.
Do you think that can work?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 21, 2017, 09:43:16 PM
yes, it can work, but as you said it won't work without Steven's help.

@Steven, what do you think about this?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 22, 2017, 07:14:18 AM
I am not sure it would be possible to convert multiple cuesheets at once even if the API allowed the access to it.
But if you support "All fields" option for the command, the user could bypass the issue by splitting the cuesheet file to individual files fist and then convert the encoding of all tags for the split files. This would allow to convert encoding for multiple albums in one go since what matters is only a few tags with garbled text. How about supporting that first while waiting for Steven's support?

Also another useful feature would be to allow changing selected code page (for both) on preview screen and show the converted text dynamically and also allow deselecting certain files on preview screen that don't show a good result. Then the user won't have to try different code page and change selected files every time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 22, 2017, 09:08:40 AM
i'll look into your ideas.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on December 22, 2017, 10:05:48 AM
I just looked into how foobar handles this: it can convert either cuesheets or tags very easily if you install a component called foo_chacon. There may be something to learn from it, especially its UI:
http://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components_0.9/Chacon_(foo_chacon)
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on December 23, 2017, 09:56:39 AM
@Steven, what do you think about this?
When i get time after a couple of other things i can enhance the cuesheet tag (18) to also write to the external cuesheet file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on December 23, 2017, 12:50:50 PM
thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on December 31, 2017, 04:23:23 PM
@boroda74-

I'm cleaning up my hard drive and noticed that I have two ASR Preset folders. One is under AppData and the other is under Plugins. Looking at the modified date stamp, I'm guessing that the one under AppData is the one that the plugin uses. But before I delete one, I'd like confirmation as to which one is the correct one to keep.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 09, 2018, 09:18:51 PM
yes, mb actually uses asr preset folder that is located in app folder. the only reason for existence of asr preset folder in plugins folder is because installation instructions for appdata folder may be too complex for many users.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on January 09, 2018, 09:38:42 PM
Good info. Thank you.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 10, 2018, 05:03:35 PM
@all, just for the record, all recent requests are almost done, including new virtual tag functions for arithmetic and boolean operations. unfortunately my visual studio suddenly have stopped to work. reinstallation don't help.  :(
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 11, 2018, 04:34:13 PM
Hopefully you could get your Visual Studio working again soon.

BTW can I request a special ASR preset that can re-sort Artists:Performer tag in a custom role order?
People are importing those tags via various means/sources, but the problem is most of the time we have no control over the tag's sort order.
Currently we have to resort to re-ordering the tags manually but it takes a considerable amount of time and effort especially when there are a lot of performers are involved and when each track has different set of performers which is common in compilations.
So what I'm suggesting is the user puts a custom role order in "Custom Text" box and run the preset, then it re-orders performer tags following the custom order.

e.g.

Performer tag before:
Göteborgs Symfoniker (orchestra); Vladimir Chernov (baritone vocals); Sergej Larin (tenor vocals)

Custom Text:
soprano vocals; mezzo-soprano vocals; alto vocals; tenor vocals; baritone vocals; bass vocals; choir vocals; orchestra

Performer tag after:
Sergej Larin (tenor vocals); Vladimir Chernov (baritone vocals); Göteborgs Symfoniker (orchestra)

- if there are multiple performers for the same role, then sort them alphabetically.
- if there are performers with no assigned/specified role, put them at the end of the list.

Also I noticed Artists:Performer tag is not listed as writable tags. There are some other unsupported special tags too like "genres". Can you make them writable? Thanks in advance!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 12, 2018, 12:23:44 AM
@redwing, all tags which are writable in mb api are writable in plugin. but for artist:performer tag there IS a workaround: add prefix \@char(1) to a performer, when you write he to artist tag.

as for required preset it looks very sophisticated and probably impossible, but i'll try to make it later.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 12, 2018, 12:49:52 AM
@redwing, all tags which are writable in mb api are writable in plugin. but for artist:performer tag there IS a workaround: add prefix \@char(1) to a performer, when you write he to artist tag.

Thanks for the tip! I can see "\@char(2)" adds performer tag (1 for guest artist).

as for required preset it looks very sophisticated and probably impossible, but i'll try to make it later.

Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 12, 2018, 01:29:49 AM
Probably there are better ways of doing this, but I could suggest the following workflow with the given example:

Performer tag before:
Göteborgs Symfoniker (orchestra); Vladimir Chernov (baritone vocals); Sergej Larin (tenor vocals)

Custom Text:
soprano vocals; mezzo-soprano vocals; alto vocals; tenor vocals; baritone vocals; bass vocals; choir vocals; orchestra

Performer tag after:
Sergej Larin (tenor vocals); Vladimir Chernov (baritone vocals); Göteborgs Symfoniker (orchestra)

- assign a number to each role in custom list from 1: tenor gets 4, baritone 5, orchestra 8.
- substitute the role with the assigned number: Sergej Larin (4), etc.
- sort values by the numbered role in ascending order: Sergej Larin (4) will come first.
- substitute each number with its original role: Sergej Larin (4) becomes Sergej Larin (tenor vocals), etc.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2018, 05:35:09 PM
http://www.mediafire.com/file/4e198toyx9rmsyo/mb_TagTools_2018-01-15-beta.zip

------------------------

new virtual tag functions:

$Random(range)

$Add(number1,number2)

$Sub(number1,number2)

$Mul(number1,number2)

$Div(number1,number2)

$AddDuration(duration1,duration2)

$SubDate(date1,date2)

$IfElse(condition,result1,result2)

$And(parameter1,parameter2)

$Or(parameter1,parameter2)

$Xor(parameter1,parameter2)

$Not(parameter)

-------------------------------

'Reencode tag' command is replaced by 'Reencode tags' command. cuesheets are supported.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2018, 05:45:36 PM
@Steven, am i correct that mb native comparisons (=, <, >, etc.) return "T" for true and "F" for false?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2018, 08:28:45 PM
http://www.mediafire.com/file/n3b670vkwmoxfud/mb_TagTools_2018-01-15-3-beta.zip

function $IfElse is removed, use native mb function $If instead.

new function $NumberOfDays(date) is added. it returns number of days between 'date' and current date.

some bug fixes.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 15, 2018, 09:01:34 PM
'Reencode tag' command is replaced by 'Reencode tags' command. cuesheets are supported.

Thanks for the update! I'll report back after testing it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 15, 2018, 09:41:04 PM
It doesn't seems to read external cuesheet file. The re-encode tags command preview dialog shows filename (same for all tracks) rather than tags in the cuesheet.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2018, 11:10:44 PM
hmm. preview works as it was earlier. if preview showed tags previously then i don't understand why it shows filenames now. Steven?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 15, 2018, 11:19:01 PM
It always showed filename for files with external cuesheet. So no differences.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 15, 2018, 11:52:18 PM
Steven, could you make mb to read cuesheet tags by api call GetFileTag() as it displays tags in main view?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 16, 2018, 10:14:29 AM
Probably there are better ways of doing this, but I could suggest the following workflow with the given example:

Performer tag before:
Göteborgs Symfoniker (orchestra); Vladimir Chernov (baritone vocals); Sergej Larin (tenor vocals)

Custom Text:
soprano vocals; mezzo-soprano vocals; alto vocals; tenor vocals; baritone vocals; bass vocals; choir vocals; orchestra

Performer tag after:
Sergej Larin (tenor vocals); Vladimir Chernov (baritone vocals); Göteborgs Symfoniker (orchestra)

- assign a number to each role in custom list from 1: tenor gets 4, baritone 5, orchestra 8.
- substitute the role with the assigned number: Sergej Larin (4), etc.
- sort values by the numbered role in ascending order: Sergej Larin (4) will come first.
- substitute each number with its original role: Sergej Larin (4) becomes Sergej Larin (tenor vocals), etc.

redwing, try new asr preset 'sort artists by role':

http://www.mediafire.com/file/cty3tnqgc7mtt2q/mb_TagTools_2018-01-16-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 16, 2018, 11:29:41 AM
Thanks! I just tried it but that's not what I wanted. Maybe I should have been clearer.
- No need to touch display artist value. It's up to the user whether to change it or not or how to change it afterwards.
- The request is only about changing Performer tag's order following a custom list.
- The performer tag has special implementation with its role/instrument even though the role is part of tag value.

(https://i.imgur.com/vyJj3be.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 16, 2018, 02:12:24 PM
could you pm me one of tracks with role/instrument as i don't understand how all these are formatted?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 16, 2018, 02:47:24 PM
PMed it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 19, 2018, 05:30:14 PM
redwing, try new version. don't forget to reimport presets.

http://www.mediafire.com/file/y9aaecgxnb6eib0/mb_TagTools_2018-01-19-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 01:42:14 AM
Now it's working as expected. Thanks a lot!

One thing I noticed is it doesn't seem to compare new values and old values and overwrites everything even when the values are the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 02:49:50 AM
'Reencode tag' command is replaced by 'Reencode tags' command. cuesheets are supported.

Aside from the cuesheet issue, I don't really see much progress with this tool. It now supports only three tags: album artist, album, and title. Previously it was possible to fix other tags as well. Also no support for changing code page in preview mode, which makes really hard to figure out what combination of code pages needs to be chosen for proper encoding.

The foobar component shows only tags with garbled text (both for file tags and cuesheet fields). If no such text, it shows nothing in the dialog. But it works only for displayed tags. This tool could work better by inspecting all tags regardless of displayed tags and only showing tags with garbled text, if none then show nothing.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 20, 2018, 03:40:11 AM
'Reencode tag' command is replaced by 'Reencode tags' command. cuesheets are supported.

Aside from the cuesheet issue, I don't really see much progress with this tool. It now supports only three tags: album artist, album, and title. Previously it was possible to fix other tags as well.
its preview tags only. the whole cuesheet is reencoded. but it seems that there is some bug with displaying cuesheet tags in mb, waiting for Steven's response.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 03:45:44 AM
What about file tags with files without cuesheet? For instance, how to fix comments tag?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 20, 2018, 04:58:30 AM
if there is no cuesheet at all, then all tags must be reencoded one by one. isn't that the case for you?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 05:24:46 AM
You mean just execute it without seeing the preview? What if only comments tag has garbled text and other tags are clean?
The user should be able to see if the selected code pages will fix it properly before running it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 20, 2018, 05:40:57 AM
do you have some suggestions? i don't see how i can display all tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 05:56:56 AM
As I already suggested, why not only show tags with garbled text just as the foobar component does?
Or it could show only tags that will get new values in preview screen. Then the user could expand each column in preview screen to verify tag values.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 20, 2018, 12:35:27 PM
i dont know how to detect garbled text without syntax analyzer for every possible language. as for only changed tags, what should i display if *every* tag is changed?

i can add 1 arbitrary selectable tag to display in the table. do you think its acceptable?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 01:16:01 PM
i can add 1 arbitrary selectable tag to display in the table. do you think its acceptable?

No, I'd rather not run the command if I can't see the result for each tag beforehand since file tags can be not uniform in encoding unlike cuesheet.
Then how about restoring the "select tag" dialog of the previous version?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 20, 2018, 04:11:59 PM
i think i can make 2 commands: 'reencode tag' (for reencoding separate tags) and 'reencode tags' (for reencoding all tags at ones). but i'd want to find some acceptable solution for latter one. just want to listen to your opinion. ofc. its possible to display all changed tags, but table may become with multi multi line rows. not sweat.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 20, 2018, 04:28:59 PM
I like the idea of having two commands. How about showing them in condensed columns rather than in multi-rows? Also show the value in tooltip with the mouse over, then the user could expand each column or read tooltip.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on January 21, 2018, 06:51:29 PM
With the most recent release (mb_TagTools_2018-01-19-beta) windows are not persistent. No matter where I move them, once closed and reopened, they always appear towards the upper left. Please reinstate persistent window locations.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 12:58:42 AM
phred, i always disable persistent windows when i'm editing ui. its just a beta and it will fixed for stable release.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on January 22, 2018, 02:42:12 AM
phred, i always disable persistent windows when i'm editing ui. its just a beta and it will fixed for stable release.
Ooops... you're right. I apologize. I now remember you telling me this the last time I used a beta.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 05:24:32 AM
redwing, i've made 2 commands for reencoding tags:

http://www.mediafire.com/file/c8535ijz5d49g4c/mb_TagTools_2018-01-22-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 05:38:45 AM
Thanks!

But what's changed with 'reencode tags' command? It still shows only three fields for preview.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 05:57:02 AM
3 fields AND all changed tags (if any) in parenthesis.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 06:13:31 AM
3 fields AND all changed tags (if any) in parenthesis.

Right. I can see now how it works.
How about showing just those in parenthesis without parenthesis? Why does it have to show the three fields all the time even when their values will remain the same?
Also I'd like to see field name as well. How about this?

Title: title value (blue color); Artist: artist value (blue color)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 06:39:31 AM
3 fields are for just identifying tracks. i'm afraid that tooltips would be too wide if i include tag names along with tag values. parenthesis can be removed, but i want to separate track representation (title - album - artist) and all other tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 06:46:16 AM
Just got this error when previewing one album with the command, which crashed MB:

10.0.16299.0 - 3.2.6595.18565 - System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.Concat(String str0, String str1, String str2)
   at MusicBeePlugin.Plugin.GetTrackRepresentation(String[] tags, String[] tags2)
   at MusicBeePlugin.ReencodeTagsPlugin.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: redwing on January 22, 2018, 06:49:54 AM
3 fields are for just identifying tracks. i'm afraid that tooltips would be too wide if i include tag names along with tag values. parenthesis can be removed, but i want to separate track representation (title - album - artist) and all other tags.

Because of the three fields, the values are unnecessarily too lengthy. When they have garbled text, it has to show each field twice. How about using Disc-Track# for identifying tracks?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 07:25:32 AM
When they have garbled text, it has to show each field twice. How about using Disc-Track# for identifying tracks?
no, artist, album and title are always shown just ones. disk-track# is always displayed as 1st tag in track representation. but using disk-track# only may be insufficient if they are blank.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 07:50:08 AM
They show up twice: once outside of parentheses, second within the parentheses. Still I think they are too much just for identifying purpose.
How about showing Disc-Track# only and if that's null, then show title?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 08:24:24 AM
Just got this error when previewing one album with the command, which crashed MB:

10.0.16299.0 - 3.2.6595.18565 - System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.Concat(String str0, String str1, String str2)
   at MusicBeePlugin.Plugin.GetTrackRepresentation(String[] tags, String[] tags2)
   at MusicBeePlugin.ReencodeTagsPlugin.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()
i think it was happening because i was trying to reencode artworks also :)
its fixed:

http://www.mediafire.com/file/ob598w9cckl59g0/mb_TagTools_2018-01-22.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 08:51:37 AM
They show up twice: once outside of parentheses, second within the parentheses. Still I think they are too much just for identifying purpose.
How about showing Disc-Track# only and if that's null, then show title?
http://www.mediafire.com/file/x34w9b63wu2mv8c/mb_TagTools_2018-01-22-2.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 09:24:30 AM
They show up twice: once outside of parentheses, second within the parentheses.
its because there are duplicated performer names in 'displayed artist' tag and in 'artist' tag.

tooltip is insufficient, so now you can double-click on any cell to view full tag value:

http://www.mediafire.com/file/5bbj1zkyq8c80ll/mb_TagTools_2018-01-22-3.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 10:01:40 AM
This is how it displays. Why does it show each tag multiple times (except comments tag)?

(https://i.imgur.com/Z0OTghS.png)


And why not show field name as I suggested since the three fields are not the default value any more?

Title: title value; Artist: artist value
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 02:02:40 PM
try this version:

http://www.mediafire.com/file/sps8vtj7plpmio5/mb_TagTools_2018-01-22-4.zip

unfortunately i cant change the color of part of text in the cell.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 02:31:05 PM
So the repeated tags are all sort tags. Is it possible not to show them when it's not set explicitly?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 02:57:20 PM
yes, of course

http://www.mediafire.com/file/arbc2a0jchbatq3/mb_TagTools_2018-01-22-5.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 03:12:56 PM
But this version neither shows explicitly set sort tags in preview nor converts those sort tags.
What I mean is when you have entered a specific value to one of the sort tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 03:17:52 PM
I think this needs to be added to the command dialog, otherwise users will never know.

you can double-click on any cell to view full tag value
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 03:18:19 PM
i just cant place check box with label on command window fancily, so look at check box without label. there is a tooltip instead of label.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 03:28:52 PM
http://www.mediafire.com/file/zm7g2aagqcyelm4/mb_TagTools_2018-01-22-6.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 03:33:30 PM
Great! That solves every issue.

Thanks a lot!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 03:52:27 PM
persistent windows are restored:

http://www.mediafire.com/file/oph0rifvdifpu1d/mb_TagTools_2018-01-22-7.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 04:01:33 PM
Getting this error and it doesn't write values as shown in preview.

10.0.16299.0 - 3.2.6595.18565 - System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.ReencodeTagsPlugin.applyChanges()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at #=zlzGadM3B9bXeaXFUig==.#=z5TDdNmu87foz(Object #=z7JHDu6k=)

Is this due to adding the sort tag option?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on January 22, 2018, 04:02:30 PM
persistent windows are restored:
Thanks for the notification
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 22, 2018, 04:29:33 PM
Getting this error and it doesn't write values as shown in preview.

10.0.16299.0 - 3.2.6595.18565 - System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.ReencodeTagsPlugin.applyChanges()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at #=zlzGadM3B9bXeaXFUig==.#=z5TDdNmu87foz(Object #=z7JHDu6k=)

Is this due to adding the sort tag option?

redwing, i cant reproduce this error, but i've found some bug (again with artwork) and have fixed it. try this version:

http://www.mediafire.com/file/afnk9ern1ydyp3a/mb_TagTools_2018-01-22-8.zip

if new version doen't fix your error then pm the problem track.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on January 22, 2018, 04:41:44 PM
It's working now. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 23, 2018, 02:29:13 AM
fixed russian localization issues:

http://www.mediafire.com/file/6969qa0eb77cyt7/mb_TagTools_2018-01-23.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: Smudger on January 25, 2018, 10:44:43 AM
Hiya

New to MB, but a small issue has arisen how can I export a selection of tracks instead of my whole database please


Regards

Steve
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 25, 2018, 05:43:57 PM
hello.

i've answered you here:

https://getmusicbee.com/forum/index.php?topic=23986.0
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 01, 2018, 10:23:04 AM
Can you show me an example of how to use the new virtual functions with ASR presets?
Say you want to have a virtual tag that shows the sum of play count and skip count. How do you go about it?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 01, 2018, 02:01:03 PM
no, its not asr. plugin just adds several new functions independently of other commands (alr and asr functions is different thing). use these functions just like native functions without any setup:

$Add(<Play count>,<Skip count>)

p.s. for me it would be more meaningful $Sub(<Play count>,<Skip count>) :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 01, 2018, 02:37:09 PM
Thanks for the instructions!
So it really works like native functions. The only difference I noticed is it requires this plugin enabled, otherwise it shows null for those tags.

Can you support logarithm function?
It's for calculating clipping dB with ReplayGain tag values.
Something like "$Log(number1,number2)" where number2 "base" is optional defaulting to 10.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 01, 2018, 07:25:32 PM
If a tag value is decimal numeral (e.g. 1.03476), $Mul function gives an error: "$Mul failed: Exception has been thrown by the target of an invocation".
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 02, 2018, 09:13:08 AM
its very easy, but i'm afraid i cant make *optional* parameters. i think i'll add 3 log functions: $lg(float), $ln(float), $log(float, base).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 02, 2018, 09:18:44 AM
If a tag value is decimal numeral (e.g. 1.03476), $Mul function gives an error: "$Mul failed: Exception has been thrown by the target of an invocation".
i don't want to support floating point numbers to standard functions as they will always return a float. but i can make dedicated float arithmetic functions: $AddFloat(), $MulFloat(), etc.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 02, 2018, 09:43:10 AM
All sounds good. Then how about supporting $Round function too for formatting float numbers?

$Round(15.2768,2) would return 15.28 and $Round(7.12,0) would be 7.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 02, 2018, 12:57:05 PM
ok
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 02, 2018, 01:58:43 PM
http://www.mediafire.com/file/6g4caflcv0f6bq5/mb_TagTools_2018-02-02.zip

--------------------------------

new functions:

$AddFloat(number1,number2)

$SubFloat(number1,number2)

$MulFloat(number1,number2)

$DivFloat(number1,number2)

$Round(number,number_of_digits)

$Log(number,base)

$Lg(number) //log10

$Ln(number) //log e
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 02, 2018, 03:19:07 PM
Thanks!

All are working great except sorting issue with float numbers:

(https://i.imgur.com/P5edQrU.png)

It completely ignores decimal point and minus sign.
Tried changing the virtual field's format to number, but it makes no differences.
Not sure this is something you can handle or Steven has to look.

Another issue is when rounded it drops all trailing zeros like the screenshot. Why not keep those zeros like 3.00 instead of 3?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 02, 2018, 04:52:21 PM
for correct sorting of negative numbers (note that integers and floats are completely different): ask Steven to support this as i cant control mb behavior from plugin.

for trailing zeros: no problem, i'll make this.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 02, 2018, 06:23:40 PM
@Steven,

Can you support sorting float numbers in virtual fields?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 05:21:10 AM
It's not easy to find the link for the latest version of this plugin. The link on the first page of this plugin thread directs to the deleted wiki page (documentation is not up to date as well).
I'd suggest putting the link for the latest stable version along with, if any, beta version both on the add-on page and the first page of this thread.

Also it would be nice if MB could list virtual functions enabled by this plugin as well. Otherwise users will always have to look up the function list scattered here and there.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 08:37:17 AM
not sure how plugin (or even mb itself) can list any functions. all plugin functions are enumerated on add-on page of main site near the bottom of page.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 08:49:22 AM
Template editor has function selector that lists all supported functions.
If Steven won't support this, maybe the plugin menu could have a command that shows the list (and example) of functions.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on February 03, 2018, 09:11:33 AM
Can you support sorting float numbers in virtual fields?
if you define the virtual tag as numeric in the field definitions dialog, the next v3.2 update should sort it correctly
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 09:22:34 AM
Can you support sorting float numbers in virtual fields?
if you define the virtual tag as numeric in the field definitions dialog, the next v3.2 update should sort it correctly

Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 09:31:31 AM
Template editor has function selector that lists all supported functions.
yes, you are quite right, haven't noticed that i can switch from tag list to function list. but i suppose i cant show list of plugin functions in any convenient way by the means of plugin.

@Steven, maybe its not very important right now, but i think the number of custom functions will increase over time, so could you enumerate custom functions for all enabled plugins in mb standard function list?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 09:36:27 AM
$And(parameter1,parameter2)

$Or(parameter1,parameter2)

MB already supports those. If it does something different, it should use a different function name.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 02:07:29 PM
no, they are generic boolean functions. strange that these functions are not listed in mb and there was request on the forum to add them to mb without Steven's response.

i'll remove these 2 functions from plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 02:18:55 PM
See: http://musicbee.wikia.com/wiki/Functions#And_.2F_Or

Currently it can be used only with $If function.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 02:32:32 PM
I think people have often requested listing more than two conditions for $And and $Or. If you can implement that with different function names, that would be useful since users could easily construct a template without having to use complex nested $If conditions.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 03:17:28 PM
i'm not sure if its easy or not (as its not very important) for Steven to add support for custom functions with variable number of parameters, eg.:

Code
public string CustomFunc_MultiAnd(params string[] parameters)

currently such custom functions are just ignored by mb.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 03:24:45 PM
Thanks!

All are working great except sorting issue with float numbers:

(https://i.imgur.com/P5edQrU.png)

It completely ignores decimal point and minus sign.
Tried changing the virtual field's format to number, but it makes no differences.
Not sure this is something you can handle or Steven has to look.

Another issue is when rounded it drops all trailing zeros like the screenshot. Why not keep those zeros like 3.00 instead of 3?

its done:

http://www.mediafire.com/file/aylmg5xonsyioc1/mb_TagTools_2018-02-03.zip

also i've removed all $*Float functions, instead use $Add, $Sub, $Mul, $Div functions for both integers and floats. $Or/$And are removed.

@rewing, please change your 2 recent guides for using arithmetic operation.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 03:47:46 PM
Yep, thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 04:03:47 PM
Can you look into this issue?

$Sub(7.5,7) returns 0.5 but
$Sub(7.6,7) returns 0.5999999

Why?

Also there's the same issue as dropping trailing zeros with $Sub function.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 04:14:05 PM
its very old computer problem connected to binary calculations, but decimal representation of numbers on a screen (probably you will be surprised, but 1/10 is not 0.1). sometimes there decimal calculations are used to avoid this, but this approach is very slow. most easy way to avoid this is to slightly round end result.

only $Round function preserves trailing zeros. dont want to add additional parameter (number of trailing zeros to preserve) to other functions.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 04:24:22 PM
Then no way to predict when that occurs? Should I add $Round to all calculation result?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 04:25:15 PM
just tried visual studio interpretator and, yes:

7.6-7=0.59999999999999964

i.e. its how .net works. i think i will auto-round all arithmetic function results to 14 digits after decimal point.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 04:33:36 PM
try this version:

http://www.mediafire.com/file/aylmg5xonsyioc1/mb_TagTools_2018-02-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 04:37:50 PM
OK. I'll now add $Round to all arithmetic result.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on February 03, 2018, 04:40:31 PM
@boroda74
perhaps the Decimal data type will work better?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 05:13:26 PM
not sure how good this version works in general, but my particular tests were successful. at least $Sub(7.6,7)=0.6 now.

also i've fixed a bug for languages which use comma as decimal point: it was impossible to type fractional number as parameter because $Sub(7,6,7) cant be correctly parsed by mb. now always use dot as decimal point for explicit fractional numbers (there are not and weren't any problems with tag values).

http://www.mediafire.com/file/aylmg5xonsyioc1/mb_TagTools_2018-02-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 05:23:52 PM
Thanks! I'll try and report back.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 05:27:07 PM
@boroda74
perhaps the Decimal data type will work better?
Steven, thanks for advice, i'll try decimal type if the problem reoccurs.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 05:34:12 PM
I don't see any differences. For me $Sub(7.6,7) returns 0.5999999046
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2018, 05:54:10 PM
i've switched from float type to decimal type for arithmetic functions. log functions are still using float type.

http://www.mediafire.com/file/aylmg5xonsyioc1/mb_TagTools_2018-02-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 03, 2018, 06:10:44 PM
Thanks! Now it no longer needs $Round function for every arithmetic. I'll edit again the guide posts.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2018, 11:30:26 AM
just have found that number_of_digits in $Round(number,number_of_digits) may be negative to round a number to dozens, hundreds, thousands, etc. :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2018, 12:13:59 PM
It doesn't work for me that way. I'm getting an error with a negative number for the number of digits.

Or did you mean you could implement that? It would be nice for formatting large numbers, but $Div could be used for that along with the current $Round.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 04, 2018, 03:09:07 PM
hmm... i've supposed this because second parameter in .net Math.Round() function is *signed* integer. \:

as for implementing this by myself its possible and easy, but i dont think there are real use cases.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 04, 2018, 07:42:38 PM
How about supporting $Len function that returns the number of characters in the given string?
It can be used for checking file URL length, for instance.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 05, 2018, 03:01:21 AM
http://www.mediafire.com/file/nnna7b6l97y8jtk/mb_TagTools_2018-02-05.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 05, 2018, 06:12:15 AM
Thanks! It's working great!
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 06, 2018, 02:11:44 AM
@boroda74-

While syncing a few thousand tracks to my portable, I noticed that a lot of Albums, Album Artists, and Artists came across as "Name, The" and I had specifically changed that in MB's Sorting Tab. But obviously I missed a lot of them.

Using AT&RT, I was able to get rid of ", The" on thousands of tracks in just a few minutes. But I had to run it three times - once for each tag.

I copied the default preset and tried to add two other tags for a total of three: Sort Album, Sort Album Artist, Sort Artist. But this new preset is only looking at one tag. How can I get it to look at all three tags and if found, remove ", The" from the end of the tag.

Thanks once again for your great time saver. And for any help you can provide in making it look at three tags at the same time.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2018, 10:47:20 AM
phred, strange, but this is working fine for me:

Code
step 1:

search for: ^(.*), The
replace with: $1

step 2:

the same as above, but for another tag

step3:

the same
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 06, 2018, 11:10:23 AM
A few more function requests. No need to hurry:

$Name(abc.def.gh.mp3) returns abc.def.gh

$CutLeft(abcde,2) returns cde (while $Left(abcde,2) returns ab)

$CutRight(abcde,2) returns abc (while $Right(abcde,2) returns de)

$RoundDown(4.28,1) returns 4.2

$RoundUp(5.2,0) returns 6

$Mod(8,3) returns 2

Some of those are only possible using regex or complex formula (to work in all cases), so it will help people to create a template they need right away. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2018, 11:30:26 AM
phred, i've included this preset to plugin package:

http://www.mediafire.com/file/188i0mxfoq4o9bz/mb_TagTools_2018-02-06.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 06, 2018, 12:22:03 PM
phred, i've included this preset to plugin package:
WOW! Thanks very much. I haven't had time to test it yet, but will later today.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2018, 01:18:43 PM
A few more function requests. No need to hurry:

$Name(abc.def.gh.mp3) returns abc.def.gh

$CutLeft(abcde,2) returns cde (while $Left(abcde,2) returns ab)

$CutRight(abcde,2) returns abc (while $Right(abcde,2) returns de)

$RoundDown(4.28,1) returns 4.2

$RoundUp(5.2,0) returns 6

$Mod(8,3) returns 2

Some of those are only possible using regex or complex formula (to work in all cases), so it will help people to create a template they need right away. Thanks!

http://www.mediafire.com/file/188i0mxfoq4o9bz/mb_TagTools_2018-02-06.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 06, 2018, 01:38:20 PM
Thanks! I didn't expect you'd implement it that quickly.

Two issues:
$Name should return only filename without last dot and extension. Currently it's no different than <Filename>.
$Mod should return a remainder not a quotient.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 06, 2018, 02:32:05 PM
$Mod is fixed:

http://www.mediafire.com/file/188i0mxfoq4o9bz/mb_TagTools_2018-02-06.zip

$Name returns only filename without extension and (if any) path to file for me. check filenames in far or total commander.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 06, 2018, 03:08:21 PM
Both issues are fixed now (if I try with the previous version, $Name still shows full filename). Thanks!

Maybe I should rewrite the whole useful formula guide with these new functions. I'll think about that.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 07, 2018, 08:16:14 PM
@boroda74-

While syncing a few thousand tracks to my portable, I noticed that a lot of Albums, Album Artists, and Artists came across as "Name, The" and I had specifically changed that in MB's Sorting Tab. But obviously I missed a lot of them.

Using AT&RT, I was able to get rid of ", The" on thousands of tracks in just a few minutes. But I had to run it three times - once for each tag.

I copied the default preset and tried to add two other tags for a total of three: Sort Album, Sort Album Artist, Sort Artist. But this new preset is only looking at one tag. How can I get it to look at all three tags and if found, remove ", The" from the end of the tag.

phred, i've included this preset to plugin package

Thanks again boroda74!! I'm reporting that this works as expected and better than what I was struggling to create. It's much appreciated.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 08, 2018, 11:49:51 AM
$NumberOfDays function returns floats. Can you make it return integers (just rounding down the rest)?

And I'm not sure $SubDate needs to return mm:ss part too. Why not just return days as integer?
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on February 08, 2018, 12:44:48 PM
$NumberOfDays function returns floats. Can you make it return integers (just rounding down the rest)?

And I'm not sure $SubDate needs to return mm:ss part too. Why not just return days as integer?

Thanks for info, will have a play and see what I can come up with - if anything, as not used the plugin before!

Best regards:  Freddy
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2018, 09:53:42 AM
$NumberOfDays function returns floats. Can you make it return integers (just rounding down the rest)?

And I'm not sure $SubDate needs to return mm:ss part too. Why not just return days as integer?
i'm surprised that it doesn't return integers. i'll fix it.

for $SubDate, what will be the difference with $NumberOfDays, if i make $NumberOfDays to work correctly?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 09, 2018, 01:30:38 PM
for $SubDate, what will be the difference with $NumberOfDays, if i make $NumberOfDays to work correctly?

What do you mean? $NumberOfDays returns days from the current date and $SubDate returns days between two given dates?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 09, 2018, 03:27:36 PM
$Abs(number) would be also useful that returns absolute value of given number.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 09, 2018, 04:17:47 PM
I'm looking for a way to have AS&R search -any- field. When doing a custom search MB allows the use of "Any Field." Using that I can find any field that has Unicode characters (') and replace them with ASCII ('). Using AS&R I have to do it field by field. Being able to set AS&R to look at any field would really simply the process and set it to be automatically applied whenever it comes across a '.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2018, 05:45:45 PM
for $SubDate, what will be the difference with $NumberOfDays, if i make $NumberOfDays to work correctly?

What do you mean? $NumberOfDays returns days from the current date and $SubDate returns days between two given dates?
i'll remake all date functions as i'm not satisfied with current set of functions.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 09, 2018, 05:47:00 PM
I'm looking for a way to have AS&R search -any- field. When doing a custom search MB allows the use of "Any Field." Using that I can find any field that has Unicode characters (') and replace them with ASCII ('). Using AS&R I have to do it field by field. Being able to set AS&R to look at any field would really simply the process and set it to be automatically applied whenever it comes across a '.

Thanks.
unfortunately its now too late (too hard) to do this.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 09, 2018, 08:30:28 PM
unfortunately its now too late (too hard) to do this.
Understandable. Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 11, 2018, 01:45:52 PM
Can you add Date Added as writable field so that the field can be updated without updating files?
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on February 11, 2018, 02:31:25 PM
Can you add Date Added as writable field so that the field can be updated without updating files?
i will include "date added" as a field that doesnt update the music file
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 11, 2018, 02:40:17 PM
i will include "date added" as a field that doesnt update the music file

That'd be great. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 11, 2018, 05:49:11 PM
Can you add Date Added as writable field so that the field can be updated without updating files?
of course. its already on my todo list.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2018, 02:57:32 PM
new functions:

$Abs(number)

$Now(): returns current local date/time. date/time format depends on your windows regional settings, eg. 12/31/2018 12:59:59 pm. it seems that there is a bug in mb for functions without parameters mb now adds ")" to returned value. hope Steven will fix it soon.

$AddDuration(duration1,duration2): duration format is similar to date/time format without "am/pm" suffix, but allowed values are different, eg. 00/01/0000 00:00:00 is valid duration, but not valid date/time. either date part or time part can be omitted, it will be defaulted to zero value.

$SubDuration(duration1,duration2)

$SubDateTime(datetime1,datetime2): returns duration between datetime1 and datetime2. for datetime1 and datetime2 either date part or time part can be ommited, it will be defaulted to current date or time 00:00:00 am.

$NumberOfDays(datetime1,datetime2): returns number of days between datetime1 and datetime2 rounded down to nearest integer value.

$AddDurationToDateTime(datetime,duration)

$SubDurationFromDateTime(datetime,duration)

--------------------

still to do: make date added tag writable.

--------------------

http://www.mediafire.com/file/zvdnpbsrky8dg7a/mb_TagTools_2018-02-14.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2018, 04:22:42 PM
'date added' is now writable

http://www.mediafire.com/file/zvdnpbsrky8dg7a/mb_TagTools_2018-02-14.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 14, 2018, 10:07:16 PM
Can you support $NumberOfDays use current date as default datetime1 (1 rather than 2 because current date would be greater than most of other date tags) when it's not set so that $NumberOfDays(<Date Added>) would return days between current date and date added?

And if you make other functions work the same way, maybe $Now() won't need to be supported as a separate function that is not working correctly having no parameters.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 15, 2018, 04:46:08 AM
optional parameters in custom functions are not supported by mb, but i've made a simple workaround.
its now possible to use word 'Now' in 1st parameter of these functions:

$SubDateTime(Now,datetime)
$NumberOfDays(Now,datetime)
$AddDurationToDateTime(Now,duration)
$SubDurationFromDateTime(Now,duration)


http://www.mediafire.com/file/n96615hjv5ucfx2/mb_TagTools_2018-02-15.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 15, 2018, 05:52:32 AM
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 21, 2018, 03:51:26 AM
a new function is added: $Now(). returns current date/time. is working fine with mb 3.2 latest patch.

http://www.mediafire.com/file/8hmvlyvn39l85rp/mb_TagTools_2018-02-21.zip

use

$SubDateTime($Now(),datetime)
$NumberOfDays($Now(),datetime)
$AddDurationToDateTime($Now(),duration)
$SubDurationFromDateTime($Now(),duration)

instead of

$SubDateTime(Now,datetime)
$NumberOfDays(Now,datetime)
$AddDurationToDateTime(Now,duration)
$SubDurationFromDateTime(Now,duration)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 27, 2018, 09:47:34 AM
Like this request (https://getmusicbee.com/forum/index.php?topic=24547.0) it would be great if search & replace can convert multiple values at once for a given tag. How about adding a new "Multiple Search & Replace" command to the plugin that allows people to list a great number of paired search and replace values and converts them one shot? Also allow to list multiple values for search for a single replace value, when entering paired values.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 27, 2018, 02:51:19 PM
this is already supported, but there are only a few steps available. i dont think i can make something better. not to speak about somethng universal. as hiccup has written its aready possible to use virtual tags for these purposses.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 27, 2018, 03:43:55 PM
Of course every conversion is possible if you add $Replace function hundreds of times to the virtual tag formula. For instance, look at these examples (https://getmusicbee.com/forum/index.php?topic=9317.msg106131#msg106131). The problem is such an approach is not practical at all. Also it's very hard to create and modify such complex formula.

If you want to use the current ASR functionality for that, that's fine. Simply change its layout for this special command to support a large number of steps. No need to add tag selection box for each step. Then each line can offer two boxes for a paired search & replace values. If you add a scrollbar, tens of lines can be offered to enter values. What do you think?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on February 28, 2018, 11:07:52 AM
Another approach would be to implement a new virtual function that makes it easy to search and replace multiple values.

$MReplace(<Title>,(aaa)(bbb)(ccc),(AAA)(BBB)(CCC))

I got the idea from how Notepad++ supports the feature:

Find: (aaa)|(bbb)|(ccc)
Replace: (?1AAA)(?2BBB)(?3CCC)

If you support the function for ASR presets as well, current five steps could convert a lot of values at once without implementing a new command.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 28, 2018, 04:31:45 PM
yes, after some thinkig my idea is very like to your ideas. also new asr preset is more preferable than new virtual tag function, just because any preset can be used as function, but i cant use function in preset. i think i'll add support for new preset tomorow.
Title: Re: Additional Tagging and Reporting Tools
Post by: cynflux on March 01, 2018, 05:39:30 PM
Is there a way to run multiple presets at once?
I can select multiple presets but have to run each one individually.

Can someone also tell me what the 2 buttons to the right of the long text field are for?

Thank you in advance.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 01, 2018, 06:02:44 PM
Like this request (https://getmusicbee.com/forum/index.php?topic=24547.0) it would be great if search & replace can convert multiple values at once for a given tag. How about adding a new "Multiple Search & Replace" command to the plugin that allows people to list a great number of paired search and replace values and converts them one shot? Also allow to list multiple values for search for a single replace value, when entering paired values.
its done as new asr preset:

http://www.mediafire.com/file/1wwufnm9dj27wc0/mb_TagTools_2018-03-01.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 01, 2018, 06:10:19 PM
Is there a way to run multiple presets at once?
I can select multiple presets but have to run each one individually.
no, because asr wont be able to know the order of presets.

Can someone also tell me what the 2 buttons to the right of the long text field are for?
its for filtering the list of presets. presets with assigned hotkeys are marked by star.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 01, 2018, 06:27:05 PM
Like this request (https://getmusicbee.com/forum/index.php?topic=24547.0) it would be great if search & replace can convert multiple values at once for a given tag. How about adding a new "Multiple Search & Replace" command to the plugin that allows people to list a great number of paired search and replace values and converts them one shot? Also allow to list multiple values for search for a single replace value, when entering paired values.
its done as new asr preset:

http://www.mediafire.com/file/1wwufnm9dj27wc0/mb_TagTools_2018-03-01.zip

Thanks a lot!
I just tested it and it's working great. How many pairs do you think it can handle entered in the custom text box?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 01, 2018, 06:37:50 PM
i dont think there is any practically important limitation.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 01, 2018, 06:41:48 PM
OK. I'll try it for some time and let you know if there's any issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 01, 2018, 07:03:26 PM
It just crashes MB if there's any syntax error (for instance if a slash is used instead of a backslash).
I also noticed this when entering a wrong regex pattern in other presets. Can you make it not to crash in such a case?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 01, 2018, 07:17:26 PM
I noticed the preset works case sensitive when finding a word, which requires listing a lot of variations for each word. How about making it work case insensitive when finding a word and requires surrounding with \" for case sensitive search?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 01, 2018, 07:18:59 PM
It just crashes MB if there's any syntax error (for instance if a slash is used instead of a backslash).
I also noticed this when entering a wrong regex pattern in other presets. Can you make it not to crash in such a case?
Title: Re: Additional Tagging and Reporting Tools
Post by: cynflux on March 01, 2018, 09:07:19 PM
It just crashes MB if there's any syntax error (for instance if a slash is used instead of a backslash).
I also noticed this when entering a wrong regex pattern in other presets. Can you make it not to crash in such a case?

I am experiencing the same thing.
It will keep popping up an error until MusicBee is restarted.
Title: Re: Additional Tagging and Reporting Tools
Post by: cynflux on March 01, 2018, 09:16:54 PM
Like this request (https://getmusicbee.com/forum/index.php?topic=24547.0) it would be great if search & replace can convert multiple values at once for a given tag. How about adding a new "Multiple Search & Replace" command to the plugin that allows people to list a great number of paired search and replace values and converts them one shot? Also allow to list multiple values for search for a single replace value, when entering paired values.
its done as new asr preset:

http://www.mediafire.com/file/1wwufnm9dj27wc0/mb_TagTools_2018-03-01.zip

Thanks a lot!
I just tested it and it's working great. How many pairs do you think it can handle entered in the custom text box?

If you don't mind me asking, what were the parameters of your test?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 02, 2018, 05:29:46 AM
If you don't mind me asking, what were the parameters of your test?

Not sure what you're asking, but I'm testing "Multiple search & replace" preset with various examples.

@boroda74;

Also support an escape character for \ and | to search and replace those characters as well.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 02, 2018, 09:02:40 AM
It just crashes MB if there's any syntax error (for instance if a slash is used instead of a backslash).
I also noticed this when entering a wrong regex pattern in other presets. Can you make it not to crash in such a case?

sorry:
http://www.mediafire.com/file/1wwufnm9dj27wc0/mb_TagTools_2018-03-01.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 02, 2018, 09:21:46 AM
Thanks! It's working better.

One problem is once it shows "syntax error" the virtual tag for the preset in the main panel keeps showing "syntax error" for every track even after the preset error is fixed. A restart is required to fix it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2018, 11:34:24 AM
i'll add escape sequences and case insensitive search today.

@redwing, F5?

more exactly: 'save all', F5
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 03, 2018, 11:46:18 AM
more exactly: 'save all', F5

No differences. Even re-adding the virtual tag to the main panel has no effect. Restarting MB is the only way to fix it.

What I mean is the virtual tag's content in the main panel, not the preset's functionality which is working fine after fixing the error.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 03, 2018, 11:56:14 AM
I just tried simply editing text in the custom box without syntax error. Hitting F5 updates the virtual tag's content correctly. Then changed the text again. Now F5 has no effect and the content no longer gets updated.
So it updates only once if there's no syntax error. With syntax error, it doesn't update at all.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2018, 12:43:15 PM
String <Custom text 1> must contain substring pairs delimitered by symbol | First part of every pair (before symbol \) will be replaced by second part of the pair. Use symbol # at the beginning of search part of any pair for case-sensitive search. Use ##, \\, || sequences for symbols #, \, |.

http://www.mediafire.com/file/b5gh707ffv8dzvj/mb_TagTools_2018-03-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 03, 2018, 01:22:54 PM
Use ##, \\, || sequences for symbols #, \, |.

Escape sequences are not working at all.

Say you're changing a tag value "# \ |" to "a b c", then this should work "##\a|\\\b|||\c" but it's not working along with this error.

System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'AdvancedSearchAndReplacePlugin'.
   at System.Windows.Forms.Control.CreateHandle()
   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(Boolean modalForm)
   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: boroda on March 03, 2018, 01:38:42 PM
@Steven, its very strange, but F5 doesn't update custom virtual tag functions for me at all. could this be due to their caching on mb side?

@redwing, i'll look at this bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2018, 02:03:36 PM
Use ##, \\, || sequences for symbols #, \, |.

Escape sequences are not working at all.

Say you're changing a tag value "# \ |" to "a b c", then this should work "##\a|\\\b|||\c" but it's not working along with this error.
i haven't foreseen special sequences \\\ and ||| which can be treated ambiguously. i think i'll change all service symbols and escape sequences to avoid this situation.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2018, 02:44:42 PM
String <Custom text 1> must contain substring pairs delimitered by symbol | First part of every pair (before symbol /) will be replaced by second part of the pair. Use symbol # at the beginning of search part of any pair for case-sensitive search. Use \#, \b, \v, \s sequences for symbols #, \, |, /.

http://www.mediafire.com/file/b5gh707ffv8dzvj/mb_TagTools_2018-03-03.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 03, 2018, 03:12:53 PM
It's working now. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 03, 2018, 04:00:15 PM
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'AdvancedSearchAndReplacePlugin'.
   at System.Windows.Forms.Control.CreateHandle()
   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(Boolean modalForm)
   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)
redwing, is this reproducable? you are the second person reporting it and it looks very strange.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 03, 2018, 04:24:01 PM
redwing, is this reproducable? you are the second person reporting it and it looks very strange.

No, not yet with this version. I think that happened with serious syntax error. And if I restart MB and open ASR preset, the plugin window is always placed at the bottom of the screen only showing its top caption bar. Then I have to drag it to the center.

BTW the preset doesn't handle a space correctly. If I add a space to the replace string, it writes it as a backslash.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 04, 2018, 07:57:03 AM
I overdid it a bit with escaping characters.

String <Custom text 1> must contain substring pairs delimitered by symbol | First part of every pair (before symbol /) will be replaced by second part of the pair. Use symbol # at the beginning of search part of any pair for case-sensitive search. Use symbol * at the beginning of search part of any pair for regular expression search or #* for case-sensitive regular expression search. Use \#, \b, \v, \s, \* sequences for symbols #, \, |, /, *.

http://www.mediafire.com/file/7n4fbr6pts4l97p/mb_TagTools_2018-03-04.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 04, 2018, 09:14:39 AM
Thanks! The space issue is fixed and the regex support is working great. Now it's really powerful. I'll report back if there's any issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 04, 2018, 03:36:53 PM
Regex word boundary "\b" in search string doesn't work following *. Does this have something to do with it's used as escape sequence for "\"? If so, can you make regex search string not to be affected by any of those escape sequences?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 04, 2018, 04:28:48 PM
yes, its conflicted escape sequences. i've changed my own escape sequences to remove conflicts with standard regex escapes.

String <Custom text 1> must contain substring pairs delimitered by symbol | First part of every pair (before symbol /) will be replaced by second part of the pair. Use symbol # at the beginning of search part of any pair for case-sensitive search. Use symbol * at the beginning of search part of any pair for regular expression search or #* for case-sensitive regular expression search. Use \#, \\, \|, \l (its L, not vertical bar), \* sequences for symbols #, \, |, /, *.

http://www.mediafire.com/file/7n4fbr6pts4l97p/mb_TagTools_2018-03-04.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 04, 2018, 05:06:53 PM
Thanks a lot! Working great now.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on March 04, 2018, 05:12:45 PM
This code for DAYS SINCE LAST PLAYED -

$If(<Last Played>="Unknown",,$If($Div($NumberOfDays(Now,<Last Played>),1000)<1,$Right(00$NumberOfDays(Now,<Last Played>),3),999))

Using Tagging tools v5.0.6637 - Now not working  :'(

Regards: Freddy

Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 04, 2018, 06:27:03 PM
See this: https://getmusicbee.com/forum/index.php?topic=3833.msg141287#msg141287

You need to change "Now" in the formula.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on March 04, 2018, 06:31:16 PM
See this: https://getmusicbee.com/forum/index.php?topic=3833.msg141287#msg141287

You need to change "Now" in the formula.

Thanks redwing - i'll give it a go  ;D
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on March 04, 2018, 07:09:23 PM
See this: https://getmusicbee.com/forum/index.php?topic=3833.msg141287#msg141287

You need to change "Now" in the formula.
Thanks redwing - i'll give it a go  ;D

Getting too bogged down with commas and parenthesis and made a pigs ear out of it....Any help would be most welcome please  ;D

1) - Last Played was NNN days ago - by 'redwing' was working ok
$If(<Last Played>="Unknown",,$If($Div($NumberOfDays(Now,<Last Played>),1000)<1,$Right(00$NumberOfDays(Now,<Last Played>),3),999))

2) - Years Since Release Date - by 'boroda74' was working ok
$If(<Year>="Unknown",,$Round($Div($NumberOfDays($Now(),<Year>),365),0))

Both formulae now kaput since updating to the latest Tagging Tools v5.0.6637

Kind regards: Freddy
Title: Re: Additional Tagging and Reporting Tools
Post by: cynflux on March 04, 2018, 09:48:33 PM
Any version of mb_TagTools that is beyond 2018-03-01, breaks my search query (SYNTAX ERROR) which is as follows:

11\C|12\D|1A\A♭ Minor|2A\E♭ Minor|3A\B♭ Minor|4A\F Minor|5A\C Minor|6A\G Minor|7A\D Minor|8A\A Minor|9A\E Minor|10A\B Minor|CA\F♯ Minor|DA\D♭ Minor|1B\B Major|2B\F♯ Major|3B\D♭ Major|4B\A♭ Major|5B\E♭ Major|6B\B♭ Major|7B\F Major|8B\C Major|9B\G Major|10B\D Major|CB\A Major|DB\E Major


I will stay with version 2018-03-01 until I can figure out the correct syntax for the newer versions.
Thank you again for this incredible tool.
Title: Re: Additional Tagging and Reporting Tools
Post by: hiccup on March 04, 2018, 10:04:39 PM
I haven't looked at solving your issue by means of using this plugin, but I do notice that for your search query, you have copied 'CA', 'DA' 'CB' 'DB' from the virtual tag formula I had offered you earlier.
You should probably change that back to '11A' '12A' '11B' '12B' and use regex boundaries?
Title: Re: Additional Tagging and Reporting Tools
Post by: cynflux on March 05, 2018, 12:33:49 AM
I haven't looked at solving your issue by means of using this plugin, but I do notice that for your search query, you have copied 'CA', 'DA' 'CB' 'DB' from the virtual tag formula I had offered you earlier.
You should probably change that back to '11A' '12A' '11B' '12B' and use regex boundaries?

Thank you for the suggestion, hiccup. Actually boroda74 provided me with that search query that copied 'CA', 'DA' 'CB' 'DB' from your formula.
As I don't have much regex experience, I am using https://regex101.com/ to learn, build, and test regex.

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 05, 2018, 05:07:06 AM
i have changed \l escape to \L

http://www.mediafire.com/file/v5gzntbah4wt4mc/mb_TagTools_2018-03-05.zip

-----------------------------------------

folks, sorry, its just a beta, i'm constantly changing the syntax for 'multiple search & replace' preset :\
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 05, 2018, 05:07:36 AM
Any version of mb_TagTools that is beyond 2018-03-01, breaks my search query (SYNTAX ERROR) which is as follows:

11\C|12\D|1A\A♭ Minor|2A\E♭ Minor|3A\B♭ Minor|4A\F Minor|5A\C Minor|6A\G Minor|7A\D Minor|8A\A Minor|9A\E Minor|10A\B Minor|CA\F♯ Minor|DA\D♭ Minor|1B\B Major|2B\F♯ Major|3B\D♭ Major|4B\A♭ Major|5B\E♭ Major|6B\B♭ Major|7B\F Major|8B\C Major|9B\G Major|10B\D Major|CB\A Major|DB\E Major


I will stay with version 2018-03-01 until I can figure out the correct syntax for the newer versions.
Thank you again for this incredible tool.

replace \ by /
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 05, 2018, 05:10:40 AM
See this: https://getmusicbee.com/forum/index.php?topic=3833.msg141287#msg141287

You need to change "Now" in the formula.
Thanks redwing - i'll give it a go  ;D

Getting too bogged down with commas and parenthesis and made a pigs ear out of it....Any help would be most welcome please  ;D

1) - Last Played was NNN days ago - by 'redwing' was working ok
$If(<Last Played>="Unknown",,$If($Div($NumberOfDays(Now,<Last Played>),1000)<1,$Right(00$NumberOfDays(Now,<Last Played>),3),999))

2) - Years Since Release Date - by 'boroda74' was working ok
$If(<Year>="Unknown",,$Round($Div($NumberOfDays($Now(),<Year>),365),0))

Both formulae now kaput since updating to the latest Tagging Tools v5.0.6637

Kind regards: Freddy
try:

1) - Last Played was NNN days ago - by 'redwing' was working ok
$If(<Last Played>="Unknown",,$If($Div($NumberOfDays($Now(),<Last Played>),1000)<1,$Right(00$NumberOfDays($Now(),<Last Played>),3),999))

for:

2) - Years Since Release Date - by 'boroda74' was working ok
$If(<Year>="Unknown",,$Round($Div($NumberOfDays($Now(),<Year>),365),0))

i've placed a workaround if tag 'year' is just year (not full date).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 05, 2018, 07:13:42 AM
When lots of files are selected with a big library, the plugin window disappears after reading 100% (status bar says that). "Show hidden window" command doesn't help. If I reopen the ASR command, it's a new one.
How about listing only files that will be updated in the table? That's how MB's native search & replace command does. Even with a big library, most of the time the files that need to be updated are not that many and no need to list all selected files in the plugin window table.
Also it would be useful if it shows the count of selected files and to-be-updated files after reading is done.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on March 05, 2018, 11:34:26 AM
Quote
Boroda74 (https://getmusicbee.com/forum/index.php?action=profile;u=728) Said: try......

1) - Last Played was NNN days ago - credit to 'redwing' was working ok
$If(<Last Played>="Unknown",,$If($Div($NumberOfDays($Now(),<Last Played>),1000)<1,$Right(00$NumberOfDays($Now(),<Last Played>),3),999))

2) - Years Since Release Date - credit to 'boroda74' was working ok
$If(<Year>="Unknown",,$Round($Div($NumberOfDays($Now(),<Year>),365),0))

i've placed a workaround if tag 'year' is just year (not full date).

Yes! - with Tagging Tools v 5.0.6638 -  
Thanks very much, that's sorted it out  :)
Best regards: Freddy
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 06, 2018, 03:59:32 PM
When lots of files are selected with a big library, the plugin window disappears after reading 100% (status bar says that). "Show hidden window" command doesn't help. If I reopen the ASR command, it's a new one.
How about listing only files that will be updated in the table? That's how MB's native search & replace command does. Even with a big library, most of the time the files that need to be updated are not that many and no need to list all selected files in the plugin window table.
Also it would be useful if it shows the count of selected files and to-be-updated files after reading is done.
not sure if bug is fixed, but now only changed files are displayed in preview table:

http://www.mediafire.com/file/71klkm7ozkqc3t7/mb_TagTools_2018-03-06.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 06, 2018, 04:07:15 PM
Thanks a lot! I'll test and report back tomorrow (it takes several hours just for reading lots of files).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 06, 2018, 04:35:58 PM
It's working much better. The window no longer disappears after reading is done and reading is much faster.
The problem is the scrollbar of the table doesn't work properly. Looks like it can't reach at the bottom row. If you grab the thumb and drag it down, the thumb disappears. Also it would be great if the count is added either to the plugin window or the status bar.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 06, 2018, 04:41:03 PM
its standard .net controls, i'm not sure what can i do. don't end, ctrl+end or ctrl+pg down work? counter is possible, will make it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 06, 2018, 05:02:18 PM
Ctrl-end works. But the bottom part of the scrollbar gets broken when the number of listed files exceeds some limit.

BTW it looks like continuous monitoring interrupts this plugin's working. The plugin was writing tags for many files but then stopped. The status bar says monitored files added because while it's working some new files were added to one of monitored folders. Can you reproduce this?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 06, 2018, 05:16:28 PM
No, the scrollbar issue is not about the number of files. It's not drawn correctly in ASR preset window. Compare it with copy tag command window's scrollbar which is working fine.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 07, 2018, 06:06:54 AM
for continues monitoring: even axe shoots ones for a life. its some obscure things. i need Steven's help to resolve this (if its not something else).

for scrollbars: will have a look at it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 12, 2018, 03:31:08 PM
redwing, thanks for bug report, i haven't noticed it because it concerned only english localization.

http://www.mediafire.com/file/psopdcja3m77gjc/mb_TagTools_2018-03-12.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 12, 2018, 04:01:42 PM
@boroda74-

Maybe I'm missing something, but every time there's an update, I have to re-tick my presets. Is there any way to prevent that? I suspect not since most of the presets are being over-written when updating, but figured it's worth asking.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 12, 2018, 04:32:14 PM
just dont import presets after update. or import only new presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 12, 2018, 07:08:58 PM
redwing, thanks for bug report, i haven't noticed it because it concerned only english localization.

That fixed it. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 12, 2018, 07:55:32 PM
just dont import presets after update. or import only new presets.
Of course! Now why didn't I think of that? Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: cjoprey on March 12, 2018, 11:28:14 PM
I've been seeing something odd with the latest update - I can enable the plugin on my laptop, but my portable install on a USB stick (which has exactly the same setup using 3.2.6645) won't let me enable the plugin:

(https://i.imgur.com/zXdAKSG.jpg)

Any thoughts?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 13, 2018, 09:01:23 AM
check <appdata>\TagTools.TagNamesErrorLog.txt for any errors.

also try to delete <appdata>\mb_tagtools.settings.xml
Title: Re: Additional Tagging and Reporting Tools
Post by: cjoprey on March 13, 2018, 03:14:40 PM
Thanks boroda74! Deleting the settings file resolved the issue.

Much appreciated!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 15, 2018, 03:21:01 PM
new function is added: $Path(filename_with_path)

http://www.mediafire.com/file/g7bpm0djxh4c06g/mb_TagTools_2018-03-15.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 15, 2018, 04:11:56 PM
new function is added: $Path(filename_with_path)

It already supports $Name function, then you could make $Name(<URL>) returning path with filename instead of adding the new $Path function. I also think it's not a good idea to use an existing field name as a new function name which could confuse users.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 15, 2018, 04:27:13 PM
It already supports $Name function, then you could make $Name(<URL>) returning path with filename instead of adding the new $Path function.
bad idea because combining strings is much easier than removing substring. actually we already are able for a long time to get any part of url using $RxReplace function.

i've changed function name to $FilePath

http://www.mediafire.com/file/g7bpm0djxh4c06g/mb_TagTools_2018-03-15.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 15, 2018, 05:20:57 PM
Can you support a new preset that converts a string to performer tag?

For instance, a track has the two artist value (so in this case a string would be display artist tag with artists delimited by ; role by ,)

Elly Ameling, soprano vocals
Dalton Baldwin, piano

and I'd like to convert them to performer tags

Elly Ameling (soprano vocals)
Dalton Baldwin (piano)

and display artist value

Elly Ameling; Dalton Baldwin

I tried editing copy guest artists from Tag 1 preset, but it wasn't easy to convert the role part.

-----

Another issue with performer tag: if you copy performer tag with copy/paste tags to clipboard command, it pastes the value as artist tag rather than performer tag. You have to tick artist tag too to make it work. Is it a bug or an expected behavior?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 15, 2018, 08:40:46 PM
i don't understand how mb works with instruments/roles through api. all my assumptions are wrong. maybe Steven will help us later.

p.s. i have forgotten it and haven't realized from your previous post the pseudo-tag <Path> is just path to file without filename, so i'll remove $Path() from plugin.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 15, 2018, 08:59:04 PM
i don't understand how mb works with instruments/roles through api.

If you copy "Artist name (role)" to artist tag with \@char(2), it writes to performer tag with the role.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 15, 2018, 09:46:00 PM
http://www.mediafire.com/file/g7bpm0djxh4c06g/mb_TagTools_2018-03-15.zip

'Convert all artists with their roles after comma to performers' preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 15, 2018, 09:59:39 PM
Thanks! It's working great except one issue. The tooltip for new value in preview window shows only first performer tag.

And if the string has another delimiter for role, just change comma to that character in step 1 & 2, right?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 15, 2018, 10:26:00 PM
1st is predefined table control behavior (its because there are null chars, and only value before null is shown in tooltip).

2nd, yes, but escape sequence may be required for some chars used instead of comma.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 15, 2018, 10:37:18 PM
OK, one more question. If the role has title case like Piano, how can I change it to lowercase?

I tried changing "($2)" part in step 1 to "\@lc($2)", but it doesn't work.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 04:46:50 PM
http://www.mediafire.com/file/mazq8051trfqq98/mb_TagTools_2018-03-16-beta.zip

asr code is rewritten, preset list is changed, you will find 2 duplicated presets after importing all/new, find them, delete and reimport new. or just delete all, import all.

redwing, i've changed that my preset, now it will lowercase roles.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 05:04:21 PM
The new version doesn't rewrite display artist value.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 05:14:31 PM
Also it would be useful if multiple search & replace preset supports commands that change a string to either lowercase or title case.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 05:40:51 PM
note: in theory in case of syntax error an appropriate error text must be shown in cell now instead of crashing mb, but cant recall which regexes crashed mb previously.

redwing, will have a look at these issues.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 05:49:19 PM
http://www.mediafire.com/file/gbxicvbkghoe0k6/mb_TagTools_2018-03-16.zip

redwing, that preset is fixed.

for multiple search and replace its not so easy, but maybe there is a workaround.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 06:03:53 PM
Thanks! It's working now. But maybe it would be better if it writes display artist from performer tag rather than from original artist tag. That will allow to rewrite display artist value based on performer tag for any files regardless of their current artist tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 06:10:18 PM
for multiple search and replace its not so easy, but maybe there is a workaround.

I wouldn't mind if those command are supported in different steps as long as they allow to enter multiple search string.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 07:01:37 PM
http://www.mediafire.com/file/gbxicvbkghoe0k6/mb_TagTools_2018-03-16.zip

use functions like in this example: A/b|C/d|*e/\\@tc(f)

'Ace' becomes 'bdF'

as its too difficult to get exception words from parameter, \@lc() and \@tc() will get them from the history of Change Case command.

actually haven't tested very thoroughly.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 07:03:46 PM
this works for me: A/b|C/d|*(e)/\\@tc($1)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 07:21:23 PM
Thanks! It's working now. But maybe it would be better if it writes display artist from performer tag rather than from original artist tag. That will allow to rewrite display artist value based on performer tag for any files regardless of their current artist tag.
http://www.mediafire.com/file/gbxicvbkghoe0k6/mb_TagTools_2018-03-16.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 07:28:33 PM
one minor bug is fixed

http://www.mediafire.com/file/gbxicvbkghoe0k6/mb_TagTools_2018-03-16.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 07:59:04 PM
Thanks! I am testing it now.

By the way I found when this error occurs that you asked before:

System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'AdvancedSearchAndReplacePlugin'.
   at System.Windows.Forms.Control.CreateHandle()
   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(Boolean modalForm)
   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)

The plugin window is minimized, but the user forgets it and runs ASR command again to launch the window, then this error shows up and a restart of MB is required to use this plugin. 
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 08:20:10 PM
this works for me: A/b|C/d|*(e)/\\@tc($1)

No, it doesn't handle correctly some punctuation characters.

Try

abcde, (ABCDE)

Then you get

bbddE,@1)


Maybe supporting exception words too in this preset is too much. Converting all to either lowercase or titlecase would be enough.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 09:53:48 PM
both bug are fixed

http://www.mediafire.com/file/gbxicvbkghoe0k6/mb_TagTools_2018-03-16.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 10:26:22 PM
I'm not sure how the case conversion code works.

For instance, I have these two titles.

PIANO SONATA In G Major
symphony no. 1 in b minor

and want to convert them to

Piano Sonata in G major
Symphony No. 1 in B minor

Can you show me an example code that can convert both titles?

Regarding the bug, are you gonna allow multiple instances of the ASR command? I don't think it's a good idea because each window might have different template and it could end up losing the template the user wanted to use. Why not just restore the hidden window if the user runs the command again?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 11:23:48 PM
Regarding the bug, are you gonna allow multiple instances of the ASR command? I don't think it's a good idea because each window might have different template and it could end up losing the template the user wanted to use. Why not just restore the hidden window if the user runs the command again?
just because i'm failed to determine when and where existing hidden windows become disposed (still existing, but unusable anymore).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 16, 2018, 11:36:09 PM
I'm not sure how the case conversion code works.

For instance, I have these two titles.

PIANO SONATA In G Major
symphony no. 1 in b minor

and want to convert them to

Piano Sonata in G major
Symphony No. 1 in B minor

Can you show me an example code that can convert both titles?
what command or preset do you meant?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 11:38:38 PM
what command or preset do you meant?

multiple search & replace preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 16, 2018, 11:58:20 PM
Regarding the bug, are you gonna allow multiple instances of the ASR command? I don't think it's a good idea because each window might have different template and it could end up losing the template the user wanted to use. Why not just restore the hidden window if the user runs the command again?
just because i'm failed to determine when and where existing hidden windows become disposed (still existing, but unusable anymore).

I don't know but the hidden window is always usable for me. How about restoring it anyway even if it's unusable? Then the user will close it down and run the command again. I think that would be better than possibly having multiple hidden windows without knowing it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 12:03:11 AM
I don't know but the hidden window is always usable for me. How about restoring it anyway even if it's unusable? Then the user will close it down and run the command again. I think that would be better than possibly having multiple hidden windows without knowing it.
then this exception arises. but i think i've found the problem, it seems that i've accidentally changed couple lines of code at some time. now its working fine for me as previously.

http://www.mediafire.com/file/gbxicvbkghoe0k6/mb_TagTools_2018-03-16.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 12:06:09 AM
Great! That fixed it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 12:08:17 AM
what command or preset do you meant?

multiple search & replace preset.
i'm not sure what do you need this preset for this purposes for at all. use 'change case' command or preset. 'multiple search and replace' preset is not to change *rules* for one search/replace pattern, its for applying several (unlimited) steps of search/replace at once with the same rules.

edit: the examples we both tried were just for testing, not for some practical reasons.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 12:14:13 AM
Of course I can use the change case command for that.
I just thought you meant it's possible when you show the example code "A/b|C/d|*(e)/\\@tc($1)" for case conversion.
If it's not supported, it's fine. Thanks for your support!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 12:24:13 AM
its possible, not very inconvenient: *(^.*)/\\@sc($1)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 01:00:57 AM
I'm not sure how to use vertical bar as "or" with multiple search and replace preset.

either
*cat|dog/rabbit
or
*cat\|dog/rabbit

doesn't work.

also try using it inside parenthesis

*(cat|dog)/red-$1
*(cat\|dog)/red-$1

doesn't work either.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 01:39:24 AM
| as 'or' has priority (its not 'or' for searching, its 'or' for both searching and replacement), then / as delimiter for search/replace. escapes are used only for designating appropriate symbols. i dont understand your examples, there must be even number of search/replace items. eg:

cat/dog|the/a     cat->dog  and  the->a

if you want to use 'or' just for searching, its just generic regex (a|b), but it will require escape because | is reserved by preset:

*(cat\|dog)/red-$1    must work, will check tomorrow.

p.s. it was a good experiment, but its not usable. even you don't fully understand how to use this preset. i think 99% users wont be able to use it even with someones help.

p.p.s i'll write dedicated 'multiple search and replace' command (frontend for this preset).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 01:54:49 AM
The problem is it's not clear whether \| means the vertical line character or "or" when it's used in regex.
I think this should work in this case.

*cat|dog/rabbit

because it starts with * then all following string before / should be read as regex pattern regardless of its use in this preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 02:02:57 AM
anyway syntax is very complex and can be suited only for examples. try to replace using preset:

1. ^(.*?)\sand\sDog   -  > $1
2. (.*)[^ab^c]\s*or\s+Cat  - > \@tc($1)

i even these regexes read with very much efforts. i can imagine how all this will look in preset :\
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 02:15:05 AM
A separate command would be nice with search/replace boxes and tickbox for case sensitive and regex for each line. That would eliminate the need for all meta-characters.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 02:31:30 AM
yes, its what i'm thinking of. also i think it will be good to make regexes optional for every line (step).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 17, 2018, 06:44:31 AM
I'm not sure how to use vertical bar as "or" with multiple search and replace preset.

either
*cat|dog/rabbit
or
*cat\|dog/rabbit

doesn't work.

also try using it inside parenthesis

*(cat|dog)/red-$1
*(cat\|dog)/red-$1

doesn't work either.

bugs, bugs, bugs...

from tests all is working fine now. its required for dedicated command because preset and command will share code base.

use: *(cat\|dog)/red-$1


http://www.mediafire.com/file/lwlwpj80h8m8ayz/mb_TagTools_2018-03-17.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 11:22:27 AM
That works. Thanks!
And I found \\| works for matching the character in regex.

BTW when you create the separate command, it would be great if each step has a tickbox to enable/disable it. Then users could save all of frequently used templates in the preset, and just tick some of them to apply.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 17, 2018, 05:33:54 PM
I was testing case conversion command and found it doesn't work properly when the search pattern contains a vertical bar.

For a string "cat dog rabbit"

*(cat\|dog\|rabbit)/$1

returns the same so it's working fine.

Now if you try

*(cat\|dog\|rabbit)/\\@tc($1)

it returns

Rabbit Rabbit Rabbit

instead of

Cat Dog Rabbit
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 06:03:51 AM
That works. Thanks!
And I found \\| works for matching the character in regex.

BTW when you create the separate command, it would be great if each step has a tickbox to enable/disable it. Then users could save all of frequently used templates in the preset, and just tick some of them to apply.
command wont touch exactly this preset, instead you will able to save custom copies of this preset. its only for auto applying purposes, no other sense to save presets.here is what i have at the moment (still buggy):

(https://www.mediafire.com/convkey/e60d/sni95i4lz0v84c97g.jpg) (http://www.mediafire.com/view/?sni95i4lz0v84c9)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 06:15:25 AM
Can you add one more tickbox to each line(step) that will include/exclude the step when applying?
Then users could save some complex templates to those steps and tick only some of them to apply depending on the given string.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 06:34:24 AM
no, all steps wont be saved upon window close, command will act like mb native search and replace, but it with multiple steps and possibility to save presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 06:42:46 AM
I was testing case conversion command and found it doesn't work properly when the search pattern contains a vertical bar.

For a string "cat dog rabbit"

*(cat\|dog\|rabbit)/$1

returns the same so it's working fine.

Now if you try

*(cat\|dog\|rabbit)/\\@tc($1)

it returns

Rabbit Rabbit Rabbit

instead of

Cat Dog Rabbit
its because its equivalent to: \\@tc(cat) \\@tc(dog) \\@tc(rabbit)

and unfortunately the same asr function (eg \\tc()) is supported only once per expression. it would be *very* difficult to fix this. this issue is not the problem for other presets (considering support for 5 steps), but not for this preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 06:55:36 AM
OK. Thanks!

BTW if it's not possible to save templates to each step box, it could be saved as comments since it's an xml file, right?
Then the user could copy and paste if there's a comments box to save templates.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 07:55:09 AM

its because its equivalent to: \\@tc(cat) \\@tc(dog) \\@tc(rabbit)

and unfortunately the same asr function (eg \\tc()) is supported only once per expression. it would be *very* difficult to fix this. this issue is not the problem for other presets (considering support for 5 steps), but not for this preset.
actually not so difficult:

http://www.mediafire.com/file/mzo90szju0j364w/mb_TagTools_2018-03-18-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 08:14:34 AM
Great! It's fixed.
Now I can do this case conversion using multiple search & replace preset:

For instance, I have these two titles.

PIANO SONATA In G Major
symphony no. 1 in b minor

and want to convert them to

Piano Sonata in G major
Symphony No. 1 in B minor

Can you show me an example code that can convert both titles?

Code
*^(.*)/\\@tc($1)|*\b(in\|major\|minor)\b/\\@lc($1)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 08:35:29 AM
you were able to do this earlier:

open Change Case command, edit exception word list, close this window, open asr, use: ^(.*)/\\@tc(\\@lc($1))

much simpler, but you have less control, i mean you might change exception word list for change case command and forget it, then try to use asr.

i can add support for second argument (excepted words) to all casing functions, but it will look too cluttered in regexes: \\@tc($1,a an the in on at with by)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 08:37:54 AM
I just tried the new command, but it doesn't seem working.
Preview shows nothing and if I save a preset, where can I find and open it?
Also now no need to use those meta-characters in search pattern, or still they are required?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 08:44:36 AM
you were able to do this earlier:

open Change Case command, edit exception word list, close this window, open asr, use: ^(.*)/\\@tc(\\@lc($1))

much simpler, but you have less control, i mean you might change exception word list for change case command and forget it, then try to use asr.

Yes, I know I can do that with that preset. But the reason I prefer this preset is it can also convert other things at the same time in addition to the case.

i can add support for second argument (excepted words) to all casing functions, but it will look too cluttered in regexes: \\@tc($1,a an the in on at with by)

For me this works better since I have more control over what to find using regex (like using word boundary or not).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 08:58:27 AM
i've discovered that its already supported :)

*(cat dog rabbit)/\\@tc($1,dog)

but its buggy if use \|

*(cat\|dog|rabbit)/\\@tc($1,dog) wont work

dont want to fix this issue, too hard
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 08:59:22 AM
I just tried the new command, but it doesn't seem working.
Preview shows nothing and if I save a preset, where can I find and open it?
Also now no need to use those meta-characters in search pattern, or still they are required?
its alpha
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 09:38:46 AM
MSR works, maybe still buggy, saving presets is not supported yet

http://www.mediafire.com/file/mzo90szju0j364w/mb_TagTools_2018-03-18-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 10:48:49 AM
If there's an empty line, it crashes MB:

System.ArgumentNullException: Value cannot be null.
Parameter name: str
   at System.Text.RegularExpressions.Regex.Escape(String str)
   at MusicBeePlugin.MultipleSearchReplaceCommand.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()

- How about highlighting borders only rather than coloring entire line in blue? It's cumbersome to have to click a box every time to enter something. Also replace box could use the same color as red text is hard to read. 
- Allow to drag the horizontal border between template input window and preview window.
- In preview window, why not place track column first like ASR presets?
- Can you support case conversion command too in replace box?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 18, 2018, 11:19:54 AM
-yes, i'm aware of this bug. ofc will have a more close look at it.

-i'm very limited in coloring of standard .net controls and dont want to write my own. you can just to start typing when cell is selected or press f2, use tab to go to next cell. yes, i agree, its legacy coloring to highlight lines with changes, but now lines without changes are not displayed anyway, so will change colors.
-i haven't found a way to do this using standard controls.
-will do
-this MUST work. maybe in search box?

Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 18, 2018, 12:27:29 PM
- In template input box, one line should be already added when the command window is open.
- Can you make the plugin remember the column width of preview window? When I use ASR command too, I always have to expand new value column because track column (it's useless for me) takes more than a half of the window. If you can't, then give more width to original and new value columns.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2018, 11:24:25 AM
-+1
-+1, but for ASR its impossible because number of columns varies depending on preset selected
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 01:20:38 PM
 Can't you make each preset (for instance those saved in user's appdata folder) remember last adjusted column width?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2018, 03:34:57 PM
good idea
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2018, 06:53:35 PM
seems that MSR is completed.

http://www.mediafire.com/file/whl9921x4i7pcie/mb_TagTools_2018-03-19-beta.zip

redwing, if there is no bugs i'll make some code cleanup (enable persistent windows, window columns, etc.).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 07:58:22 PM
Still cannot make case conversion code working.

Cannot save a preset with this error:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.Preset..ctor(Preset originalPreset, String presetNameSuffix, Boolean copyGuidIfsuffixAbsent)
   at MusicBeePlugin.MultipleSearchReplaceCommand.saveButton_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 March 19, 2018, 08:27:45 PM
hmmm... case conversion is not working properly for me, but is working.

could you post a screenshot of MSR before saving preset?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 08:32:38 PM
Sure.

(https://i.imgur.com/M4hrYXq.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2018, 09:41:03 PM
working fine here. i'm not sure if you are using latest plugin version. here is the latest one (no changes in functionality, but some ui enhancements, mostly for russian localization):

http://www.mediafire.com/file/whl9921x4i7pcie/mb_TagTools_2018-03-19-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 09:59:51 PM
No, still getting the same error when trying to save a preset.
Also I noticed from tag and to tag needs to be switched.
Case conversion code is not working, either. If that works for you, give me an example code.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 10:05:30 PM
Also it fails to update the tag with this error if I hit proceed:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.MultipleSearchReplaceCommand.applyChanges()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at #=zW4PfeoQdgAPApw9RSg==.#=zZTXnloQoZcrh(Object #=z0vgHEbE=)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2018, 10:08:17 PM
it is working for me for cases i've tried. could you detect the condition when it stops to work (maybe the number of lines in MSR window)? Or it doesn't save presets at all?

p.s. also for ASR functions use them directly, without escaping, i.e. use \@tc($1) instead of \\@tc($1)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 10:14:38 PM
It doesn't save a preset in any conditions nor update tags at all. Case code doesn't work with either code.
Are you sure the current dll file is 1,644,544 byte?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 19, 2018, 10:31:31 PM
yes. its very strange situation.

i've reuploaded plugin with latest asr presets. i mean mostly latest 'multiple search & replace' preset (which is the base for all MSR presets). import new presets after installing it and try again.

http://www.mediafire.com/file/whl9921x4i7pcie/mb_TagTools_2018-03-19-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 19, 2018, 10:54:32 PM
Now I can save a preset. But it still fails to update tags. Probably the problem is it doesn't respect the source tag and the destination tag setting when applying. If I open a saved preset, it's always set to from genre tag to genre tag. Probably that's why case code doesn't work either with MSR window but works with the saved preset if I change from tag and to tag setting correctly.

I have expected it would be possible to load a saved preset from MSR window and then re-edit, run and save it. Can you support this? Also maybe they could be stored in a separate sub-folder and be loaded only from MSR window because currently the user would end up having too many presets for ASR command. That would be more consistent and efficient to manage them.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2018, 12:16:36 AM
Quote
Probably the problem is it doesn't respect the source tag and the destination tag setting when applying.
yes, at least this is the case. i'll fix it.

Quote
I have expected it would be possible to load a saved preset from MSR window and then re-edit, run and save it. Can you support this?
maybe later. parsing is not very easy and i want to have at least basic functionality first.

Quote
Also maybe they could be stored in a separate sub-folder and be loaded only from MSR window because currently the user would end up having too many presets for ASR command. That would be more consistent and efficient to manage them.
i dont want to duplicate ASR functionality and ASR doesn't support folders.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2018, 11:12:41 AM
Quote
Probably the problem is it doesn't respect the source tag and the destination tag setting when applying.
yes, at least this is the case. i'll fix it.

http://www.mediafire.com/file/4fdapqnbxfu2lha/mb_TagTools_2018-03-20-beta.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 20, 2018, 02:20:07 PM
Still fails to update tags when running on MSR window with the same error though saved presets now show correct tags and work right away:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.MultipleSearchReplaceCommand.applyChanges()
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation()
   at #=zW4PfeoQdgAPApw9RSg==.#=zZTXnloQoZcrh(Object #=z0vgHEbE=)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2018, 04:51:57 PM
post full error message (not a screenshot!) for this version, it will be auto-copied to clipboard.

http://www.mediafire.com/file/44uc7fvo914ox0m/mb_TagTools_2018-03-20-rc.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 20, 2018, 05:20:42 PM
Great! It's now working. Also I see it can now load existing presets.

- Tried case conversion code, not working. The saved preset shows ^(.\*) instead of ^(.*)
- Since the previous version, "delete all" button in ASR window deletes all presets. I lost all my custom presets. Also the saved MSR presets shouldn't be deleted and need to be treated as custom presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2018, 05:38:32 PM
- will check the issue. all this escaping is too complex. i'm afraid we wont succeed to find all possible bugs.
- 'delete all' always worked this way. i think i'll add 'delete preinstalled' button.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 20, 2018, 05:47:04 PM
For me, "delete all" always deleted non-custom presets and only left custom presets in AppData folder. Very useful.
If I want to delete a custom preset, used "delete" button. As I said this has changed since you updated all presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 20, 2018, 05:58:14 PM
now its evening at moscow, dont want to inspect the code, had a quick look at it and, yes, 'delete all' wont just delete all presets, there are something more sophisticated, but haven't changed this code for ages. there are some comparison of various dates/times, i think i'll change it to just delete non-custom presets (every preset has a flag if its custom, which cannot be changed by users).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 20, 2018, 06:03:58 PM
Yes, take your time!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 10:39:25 AM
- Tried case conversion code, not working. The saved preset shows ^(.\*) instead of ^(.*)
- Since the previous version, "delete all" button in ASR window deletes all presets. I lost all my custom presets. Also the saved MSR presets shouldn't be deleted and need to be treated as custom presets.

http://www.mediafire.com/file/5t156t19ttpzzqz/mb_TagTools_2018-03-21-rc.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 12:18:04 PM
- If you have not imported any ASR presets and try to save a MSR preset, then you get this error:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.Preset..ctor(Preset originalPreset, String presetNameSuffix, Boolean copyGuidIfsuffixAbsent)
   at MusicBeePlugin.MultipleSearchReplaceCommand.saveButton_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)

But once it starts working after you have imported presets, then it keeps working even if you have no imported presets.

- Case code still doesn't work.

If I use \@tc($1)
the saved preset also has \@tc($1)

So I have to use \\@tc($1)
then saved preset is working but MSR window still doesn't work (even preview is wrong).

- Checked escape sequences for meta-characters and all are working fine. Delete all button now doesn't delete custom presets plus MSR presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 12:33:48 PM
i'll make more meaningful error message if base msr preset is missing.

its strange, but both *^(.*)/\@tc($1) and *^(.*)/\\@tc($1) is working fine for me (i mean ASR).

msr window doesn't support asr functions. its intended, but probably should be fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 12:42:13 PM
You mean the user should import MSR preset first to make the command save a preset?
Can't it just use the preset in plugin folder even if it's not imported?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 12:59:07 PM
Also I noticed remove leading zeros presets (both of them) have a bug.
If a file has no target tag (track#), it writes "SYNTAX ERROR" to the tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 01:21:26 PM
You mean the user should import MSR preset first to make the command save a preset?
yes. don't want to change this behavior.

its strange, but both *^(.*)/\@tc($1) and *^(.*)/\\@tc($1) is working fine for me (i mean ASR).
i'll leave it as is, but MSR now saves escaped ASR functions.

Also I noticed remove leading zeros presets (both of them) have a bug.
If a file has no target tag (track#), it writes "SYNTAX ERROR" to the tag.
will check it.

msr window doesn't support asr functions. its intended, but probably should be fixed.
its fixed.

http://www.mediafire.com/file/vu7nfex1vbq9t4e/mb_TagTools_2018-03-21.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 02:10:12 PM
Also I noticed remove leading zeros presets (both of them) have a bug.
If a file has no target tag (track#), it writes "SYNTAX ERROR" to the tag.
actually its very serious bug, which concerns almost all presets, especially its risky for auto-applied presets. thanks for this finding! now asr wont write SYNTAX ERROR! to tags (though it still will display this message in preview table).

http://www.mediafire.com/file/vu7nfex1vbq9t4e/mb_TagTools_2018-03-21.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 02:10:47 PM
Case code is working, but noticed a very strange bug.

Try this with MSR preset

*(in\|of\|on)/\\@lc($1)

Those words are not working. If you use other words, or with @tc, it's working.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 02:28:25 PM
yes, i see the same  :-\
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 02:33:56 PM
It worked fine before you started working on MSR command. Must be an introduced bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 02:39:04 PM
now asr wont write SYNTAX ERROR! to tags (though it still will display this message in preview table).

Yep, it's fixed. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 02:48:40 PM
Case code is working, but noticed a very strange bug.

Try this with MSR preset

*(in\|of\|on)/\\@lc($1)

Those words are not working. If you use other words, or with @tc, it's working.
its expected behavior  :)  i've just forgotten that i've made a change for asr recently. open change case command, edit excepted words and click 'asr' button to save these words for all asr casing functions. \\@tc($1) works because this function always capitalizes 1st and last words in a sentence.

i've forgotten to reenable persistent windows:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 03:02:51 PM
Is it possible to override the setting from MSR window or preset?
What's the point of supporting case code for MSR command if that has to be adjusted from another command every time you want to change exception words?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 03:13:34 PM
no, not every time. i suggest that its one time permanent action. you can override excepted words in second parameter of casing functions: \@lc($1,a the an) \@lc($1,) etc.

i'll try to fix the bug with \| when second parameter is used.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 03:28:41 PM
hmmm... \| is working fine now. don't remember that i've fixed it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 03:42:21 PM
I don't understand why it's so complicated and there are things that has to be done first to make other things work. I wonder how other users would figure all this out.
Then can you tell me what I need to do to make that code working?
What do I have to do with the change case command? I never used the command as I only used the change case preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 04:08:05 PM
I don't understand why it's so complicated and there are things that has to be done first to make other things work. I wonder how other users would figure all this out.
i don't understand what is complicated and i don't expect that most users even know something about asr casing functions.

Then can you tell me what I need to do to make that code working?
What do I have to do with the change case command? I never used the command as I only used the change case preset.
open change case command, edit text (excepted words) after 'except for words' label or just clear the text, click 'ASR' button to the right of this text, do not make preview, do not click 'proceed', close command window. you have made default excepted words for ASR/MSR. if you want to override excepted words for particular situation just use second (optional) parameter, i.e.

\@tc($1) will use asr defaults
\@tc($1,) wont except any words
\@tc($1,a the an) will ignore asr defaults and will except only words 'a', 'the', 'an'
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 04:17:48 PM
i've changed behavior of \@tc() and \@sc() functions: now they will lowercase excepted words (previously excepted words weren't changed).
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 21, 2018, 07:11:09 PM
i've forgotten to reenable persistent windows:
Not a problem. I would've reminded you.  :-)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 21, 2018, 07:19:52 PM
 :)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 21, 2018, 10:05:34 PM
So if I clear the word list in change case command and click ASR button, would any presets work as it used to?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2018, 02:19:45 AM
I see it now shows warning message to import presets when trying to save a preset without importing them. That will help.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2018, 09:52:36 AM
"Sort performers by their roles" preset is no longer working. It gives syntax error. I wonder if you may have changed something when you're working on another performer preset later.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2018, 12:12:54 PM
So if I clear the word list in change case command and click ASR button, would any presets work as it used to?

it will just clear the list of excepted words for asr, i.e. asr wont except any words by default and functions \@tc($1) and \@tc($1,) will do the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: jmperazzo on March 22, 2018, 12:54:32 PM
embarrassingly basic question here (i don't see a question tree and perhaps this is not the place to ask either). I don't know how to run your plugin. I thought it would "appear" on musicbee but perhaps it should be moved to a folder where it can be "seen"? thanks in advance for your patience...
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2018, 02:33:09 PM
I don't know how to run your plugin. I thought it would "appear" on musicbee but perhaps it should be moved to a folder where it can be "seen"? thanks in advance for your patience...

See: http://musicbee.wikia.com/wiki/Additional_Tagging_and_Reporting_Tools#Installation_and_Usage
Also go to Preferences> Plugins and click configure button for the plugin. Then you can also make it show in context menu.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2018, 02:45:17 PM
So if I clear the word list in change case command and click ASR button, would any presets work as it used to?
it will just clear the list of excepted words for asr, i.e. asr wont except any words by default and functions \@tc($1) and \@tc($1,) will do the same.

So far it's working fine for me as it used to. But \@tc($1,a the an) function can't be used for classical music title formatting as it always capitalizes last word. So I have to use \@lc in a separate step.

BTW I noticed ASR preset folder includes one Russian named MSR test preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2018, 02:51:37 PM
"Sort performers by their roles" preset is no longer working. It gives syntax error. I wonder if you may have changed something when you're working on another performer preset later.
its not only this preset, almost half of presets were affected by this bug. update plugin and reimport all presets. also now use '\(' and '\)' instead of explicit (not service) '(' and ')' in both search (this was required previously) and *replace* patterns of ASR/MSR.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2018, 02:56:31 PM

So far it's working fine for me as it used to. But \@tc($1,a the an) function can't be used for classical music title formatting as it always capitalizes last word. So I have to use \@lc in a separate step.
what is the common practice of capitalizing in english? must the last word be capitalized always, sometimes of never?

BTW I noticed ASR preset folder includes one Russian named MSR test preset.
i'll delete it.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2018, 03:18:20 PM
its not only this preset, almost half of presets were affected by this bug. update plugin and reimport all presets.

Thanks! it's now working.

what is the common practice of capitalizing in english? must the last word be capitalized always, sometimes of never?

Never. It's only capitalized in titles (books, movies, albums, songs, etc).
But that rule doesn't apply to classical music title since its format is too diverse partly depending on its sub-genre. I'm not asking you any new feature about this. Just saying the support for excepted words in that format isn't of much help.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 22, 2018, 03:27:26 PM
also now use '\(' and '\)' instead of explicit (not service) '(' and ')' in both search (this was required previously) and *replace* patterns of ASR/MSR.

- It's only required in regex mode, right?
- For search \( works. For replace, ( works in my test (both in MSR window and MSR preset)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2018, 04:54:31 PM
more exactly its required if you use asr functions (they can be used in non-regex mode, though they are useless without regexes).

a minor bug is fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 22, 2018, 05:24:52 PM
what is the common practice of capitalizing in english? must the last word be capitalized always, sometimes of never?

Never. It's only capitalized in titles (books, movies, albums, songs, etc).
ofc i meant titles, not generic text.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 23, 2018, 07:16:31 AM
Getting this error message if you minimize copy tag command window and run the command again:

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 System.Windows.Forms.DataGridView.FlushDisplayedChanged()
   at System.Windows.Forms.DataGridView.PerformLayoutPrivate(Boolean useRowShortcut, Boolean computeVisibleRows, Boolean invalidInAdjustFillingColumns, Boolean repositionEditingControl)
   at System.Windows.Forms.DataGridView.OnColumnCollectionChanged_PreNotification(CollectionChangeEventArgs ccea)
   at System.Windows.Forms.DataGridViewColumnCollection.Clear()
   at System.Windows.Forms.DataGridView.Dispose(Boolean disposing)
   at System.ComponentModel.Component.Dispose()
   at System.Windows.Forms.Control.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Dispose(Boolean disposing)
   at MusicBeePlugin.CopyTagCommand.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Close()
   at MusicBeePlugin.PluginWindowTemplate.display(Boolean modalForm)
   at MusicBeePlugin.Plugin.copyTagEventHandler(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)

You may want to check all other commands about the same error.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 23, 2018, 01:45:53 PM
i cant reproduce this bug, redownload plugin from permanent link as i've changed something related recently:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip

if the bug persists i'll make debug version.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 23, 2018, 02:02:01 PM
That fixed it. Now re-running the command restores the hidden window. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 24, 2018, 08:52:18 AM
"Convert all artists with their roles after comma to performers" preset is no longer working with syntax error. I think it's about () to be replaced by \( \) in the code, but I can't fix it myself.
Title: Re: Additional Tagging and Reporting Tools
Post by: Alina on March 26, 2018, 03:22:34 PM
I have no experience with regex, and probably no talent for it :-(
Still i made an effort to accomplish this:

Many of my music files contain dates such as 1-1-1970 or 1980-11-12
But i do not care about days and months, and would like to permanently change these tags so they only contain the year (1970, 1980 etc.)

I found that to isolate the year, this regex should work:
[0-9]{4}
And it indeed works when i tried it on an online regex tester.

But, i can't figure out how to setup this plugin to make this work.
I tried if i could start with some 'extract' presets to perhaps tweak those, but failed miserably.

It would be great if somebody would be willing to show what i need to enter where exactly.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 26, 2018, 04:37:49 PM
Many of my music files contain dates such as 1-1-1970 or 1980-11-12
But i do not care about days and months, and would like to permanently change these tags so they only contain the year (1970, 1980 etc.)

I found that to isolate the year, this regex should work:
[0-9]{4}
And it indeed works when i tried it on an online regex tester.

But, i can't figure out how to setup this plugin to make this work.
I tried if i could start with some 'extract' presets to perhaps tweak those, but failed miserably.

It would be great if somebody would be willing to show what i need to enter where exactly.

It's much easier to tweak an existing code than to create a new one from scratch. Also the chances are such code already exists if it's for a common task.
Run advanced search & replace command and import all presets.
Type "year" in the filter bar at the top.
Then you will fined "Replace full date with year in Tag 1" preset.
Select tracks and click preview to see if it shows a correct result and proceed.

Now if you want to edit the code, click copy button, then it will create a copy of the preset.
Select that preset, click edit button, then edit the code.  That's how you create a custom preset with your own code.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 26, 2018, 04:39:13 PM
No need for regex. Or for modifying an existing preset.
I see two presets which might help you. Search for 'date' and you'll come up with:
- Remove month and day from release date
- Replace full date with year in '<Tag 1>'

I think the second one will do what you want. But I suggest you test on one or two tracks before you run everything through it.
Title: Re: Additional Tagging and Reporting Tools
Post by: Alina on March 26, 2018, 04:59:39 PM
No need for regex. Or for modifying an existing preset.
I see two presets which might help you. Search for 'date' and you'll come up with:
- Remove month and day from release date
- Replace full date with year in '<Tag 1>'

I think the second one will do what you want. But I suggest you test on one or two tracks before you run everything through it.

Thank you Phred!

That's working great indeed. (the first one)
And a bit silly of me that i had overlooked that existing preset.

(the one that redwing proposed did not work for yyyy/mm/dd)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2018, 01:55:45 PM
"Convert all artists with their roles after comma to performers" preset is no longer working with syntax error. I think it's about () to be replaced by \( \) in the code, but I can't fix it myself.
i cant reproduce this bug. 1st download latest version, if bug persists let me know exact performer names and roles:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2018, 03:43:02 PM
It's very strange. As you said the preset is working. But in some cases, it doesn't work.

Try this. Enter this value to display artist tag:

AAA, violin; BBB, piano

And save tag editor. If you open multiple artist splitter dialog, it will show the two artists properly.
Now run the preset, then you will get syntax error.
If you edit any of those values in artist splitter and save it again, then it works.
I can't make sense of this.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 27, 2018, 06:25:24 PM
i think i know why this happens, reimport all presets:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 27, 2018, 06:46:15 PM
Now the preset removes roles and write them as artists rather than as performers.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2018, 12:36:45 AM
it seems that preset doesn't work with latest mb version.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 28, 2018, 04:12:03 AM
Are you sure it's not about the plugin?

If I use the previous version of the plugin, this still works with the latest version of MB:

If you edit any of those values in artist splitter and save it again, then it works.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2018, 04:26:46 AM
hmm, i dont understand whats the difference. replaced strings are identical in both cases when i inspect them in debugger. will have a more close look at this issue.
Title: Re: Additional Tagging and Reporting Tools
Post by: Tybot on March 28, 2018, 10:02:21 AM
I'm trying to move one specific tag to another and could really use some assistance. I have guest artists formatted like this:

Tag: <performer>
Value: Name (Guest Artist)

I would like to move that value to the tag <guest artist> without deleting other values in the <performer> tag (like other names and their instrument, formatted the same way).

I need help on which preset to use and how to use it. I would also like to ask boroda74 to add the tag <guest artist> to the drop-down menu of tags to chose from as it's currently not available.

Thanks in advance!


Edit: @boroda74

Are you sure this plugin is working correctly with the latest version of MB? I just royally fucked up and was forced to restore a lot of tags different backups from the past few days and it's not going very well to say the least.

Edit2:

So I downgraded to 3.1 and tried to restore the tags again with the same result as before. It restores the <artist> tag but I'm not getting the <performer> back. Unless anyone has a better idea I'm manually restoring the 176 files I messed up, could have been worse... Not sure why restoring the backup for the selected tracks isn't working as I vaguely recall using the tool successfully before.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2018, 01:36:30 PM
tag <guest artist> is read-only in mb api, but there is a workaround. i'll search for similar preset written for redwing and will adopt it for your needs. also ALWAYS experiment with a few test tracks before bulk editing tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2018, 01:44:16 PM
what happens if just use 'toy: copy tag' asr preset to artist tag to artist tag (you need to mb 3.2). latest plugin version wont work correctly with mb 3.1, its strange if it works somehow at all with 3.1.
Title: Re: Additional Tagging and Reporting Tools
Post by: Tybot on March 28, 2018, 04:32:28 PM
tag <guest artist> is read-only in mb api, but there is a workaround. i'll search for similar preset written for redwing and will adopt it for your needs. also ALWAYS experiment with a few test tracks before bulk editing tags.

I'd appreciate that! I went through the files in question manually so right now every guest artist is in the tag <guest artist>. However, next time I add new files that's been tagged with Musicbrainz Picard, I will face the same issue as those files will automatically be tagged "Performer: Name (guest artist) because that's how Picard does it. A script to automate this process (move those tags to <guest artist> would be really nice.

The screw-up had nothing to do with you plugin. That was just me being stupid which cost me a couple of hours...

what happens if just use 'toy: copy tag' asr preset to artist tag to artist tag (you need to mb 3.2). latest plugin version wont work correctly with mb 3.1, its strange if it works somehow at all with 3.1.

Using 'toy: copy tag' does display <artist: guest> tag in the drop-down menu. But without the option to insert custom text it's going to move all my performers to the guest artist tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 28, 2018, 04:45:17 PM
i meant to copy from 'artist' tag to 'artist' tag, not to 'artist: guest'. mb 3.2 might reformat 'artist' tag. if mb doesn't i'll create new preset.

p.s. i simply cant create tags from your example to check anything myself, mb reformats 'artist' tag to correct value.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 28, 2018, 05:32:56 PM
However, next time I add new files that's been tagged with Musicbrainz Picard, I will face the same issue as those files will automatically be tagged "Performer: Name (guest artist) because that's how Picard does it.

Why not use a script in Picard in the first place to tag it the way you want?
Title: Re: Additional Tagging and Reporting Tools
Post by: Tybot on March 28, 2018, 07:21:08 PM
However, next time I add new files that's been tagged with Musicbrainz Picard, I will face the same issue as those files will automatically be tagged "Performer: Name (guest artist) because that's how Picard does it.

Why not use a script in Picard in the first place to tag it the way you want?

I asked myself the same thing just as I posted. I'll probably look into that as it would be the optimal solution to the problem. Not sure how to format such as an expression though but it shouldn't be that difficult.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2018, 08:48:17 AM
Two performer presets are not working.
- "Sort performers by their roles" preset gives syntax error. I can't fix it myself.
- "Convert all artists with their roles after comma to performers" preset still removes roles and writes artist tag. If I remove step 4 & 5, it works. Also you can merge step 1 & 2 using this code:
Code
\@char(2)$1 (\@lc($2))\@null()
Some suggestions about handling auto-applied presets. It's not easy to spot which presets are auto-applied when you have lots of presets imported. Also double-clicking a preset ticks the box and enables auto-applying which I often notice later after some tags were messed up.
- Remove the double-click-to-auto-apply functionality. The change in the tickbox is not easy to notice.
- Show auto-applied presets always at the top of the list (regardless of sort option) and use bold font for them to easily notice the change.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2018, 02:47:45 PM
both presets are fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip

its not so easy to override behavior of this control (ListView).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2018, 03:48:04 PM
Both presets still have some issues.
"Convert all artists with their roles after comma to performers" preset now writes performer tag with role properly. But it doesn't update display artist value. If you can't fix it, just remove the latter steps. I can use two separate presets myself.
"Sort performers by their roles" preset is now working. But it shows weird behavior for any performer with "mezzo-soprano vocals" role. It writes only that performer to artist tag with a value "008 performer name (mezzo-soprano vocals)". If I change the role to something else, it works.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2018, 06:40:24 PM
seems that i've fixed these 2 presets finally. also i've made some minor ui bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2018, 07:00:35 PM
Thanks!
First one is fixed now.
Second one still has an issue in handling a role with a hyphen. Try with any made-up roles with a hyphen between words. Then it writes some number before performer name and writes it as artist tag.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2018, 07:35:39 PM
second preset is working fine for me and i dont understand how hyphens can affect something (there indeed was a bug, but different bug, not related to hyphens).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2018, 07:43:47 PM
So is it working fine for you with a role having a hyphen between words?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 29, 2018, 08:35:38 PM
yes, you either haven't remported this preset for some reason or there are different set of conditions that triggers bug.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 29, 2018, 08:53:44 PM
There's one more condition.

If you use for the custom text
mezzo-soprano vocals; orchestra
it's fine.

But if you use
mezzo-soprano vocals; soprano vocals
or
mezzo-soprano vocals; soprano
or
mezzo-soprano vocals; vocals
it gives the error.

The difference is the error occurs when a word after the hyphen is used as another role.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 30, 2018, 03:44:56 PM
maybe some more conditions?

(https://www.mediafire.com/convkey/1f97/7f69mgbny9f44db7g.jpg) (http://www.mediafire.com/view/?7f69mgbny9f44db)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 30, 2018, 05:53:20 PM
redwing, though i cant reproduce 'SYNTAX ERROR!' message, i've found (and fixed) a bug for situation you described:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on March 30, 2018, 09:37:10 PM
Yes, it's fixed now. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 01, 2018, 03:54:20 PM
MSR preset is no longer working. And MSR command window doesn't work for multiple files. Can you reproduce this?
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on April 03, 2018, 07:43:08 AM
redwing, though i cant reproduce 'SYNTAX ERROR!' message, i've found (and fixed) a bug for situation you described:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
I'm getting a thrown exception error when trying to enable it.

OS: Win10 Home
MB Version: 3.1.6590 (Portable version)

I have to admit that I migrated my config files and library from a non-portable version to the portable version.

(https://i.imgur.com/CSjzpac.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 03, 2018, 07:56:19 AM
I'm getting a thrown exception error when trying to enable it.

Trying deleting the plugin settings file in AppData folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: theta_wave on April 03, 2018, 03:48:02 PM
I'm getting a thrown exception error when trying to enable it.

Trying deleting the plugin settings file in AppData folder.

Thanks Redwing.  Deleting the settings file in the AppData folder of MusicBee's portable install (initially transferred over from %AppData%) did the trick.  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 06, 2018, 06:54:58 PM
MSR preset is no longer working. And MSR command window doesn't work for multiple files. Can you reproduce this?
i've found several bugs. cant reproduce that MSR doesn't work for multiple files, but it wont display tracks without changes.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 06, 2018, 09:09:35 PM
MSR preset adds "@restoreparenthesis" to any new values.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 07, 2018, 04:21:27 AM
It seems most of the recent bugs are about the parentheses handling and it keeps occurring one after another.
I am not even sure how many presets might have similar issues since I'm using only a few of them.
If it's about you're using parentheses as a meta-character in your inner code, can't you change it to more rarely used ones like [[ ]] instead of ( )?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 07, 2018, 08:52:14 PM
it was my initial mistake trying to foresee any char combinations in tags, though its obvious that something like [[ or ]] or ;; hardly will be used in tags. for now i leaved syntax as is, but i'll follow your advice if there are still bugs.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 08, 2018, 03:24:54 AM
MSR command and presets are now working.
But if you hide MSR window and rerun the command, you get this error:

MusicBee v3.2.6671.32617 (Win10.0)
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 System.Windows.Forms.DataGridView.FlushDisplayedChanged()
   at System.Windows.Forms.DataGridView.PerformLayoutPrivate(Boolean useRowShortcut, Boolean computeVisibleRows, Boolean invalidInAdjustFillingColumns, Boolean repositionEditingControl)
   at System.Windows.Forms.DataGridView.OnColumnCollectionChanged_PreNotification(CollectionChangeEventArgs ccea)
   at System.Windows.Forms.DataGridViewColumnCollection.Clear()
   at System.Windows.Forms.DataGridView.Dispose(Boolean disposing)
   at System.ComponentModel.Component.Dispose()
   at System.Windows.Forms.Control.Dispose(Boolean disposing)
   at System.ComponentModel.Component.Dispose()
   at System.Windows.Forms.Control.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Dispose(Boolean disposing)
   at MusicBeePlugin.MultipleSearchReplaceCommand.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Close()
   at MusicBeePlugin.PluginWindowTemplate.display(Boolean modalForm)
   at MusicBeePlugin.Plugin.multipleSearchReplaceEventHandler(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 April 08, 2018, 03:29:33 AM
BTW I have lots of custom presets, and it's really pain to recreate all of them whenever you update ASR presets.
I think something is wrong here. Updating dll file alone should address the issue, or there should be a support to re-import custom presets to new format without having to re-create all of them manually.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 08, 2018, 08:09:15 AM
i dont understand, reimporting 'official' presets will delete custom presets? if so, its a bug. as for error message i'll check this.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 08, 2018, 08:14:18 AM
No, that's not what I meant. You said old presets shouldn't be used when presets get updated.
So I am re-creating custom presets using new presets whenever presets get updated.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 10, 2018, 05:01:33 PM
"Split <Tag 1> to tags <Tag 2>, <Tag 3>, <Tag 4>" preset doesn't work.
I have to use "Split <Tag 1> to tags <Tag 2>, <Tag 3>" preset twice.
If that's also about the parentheses handling, will you fix the issue by changing the meta-character?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 11, 2018, 03:03:12 AM
MSR command and presets are now working.
But if you hide MSR window and rerun the command, you get this error:

MusicBee v3.2.6671.32617 (Win10.0)
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 System.Windows.Forms.DataGridView.FlushDisplayedChanged()
   at System.Windows.Forms.DataGridView.PerformLayoutPrivate(Boolean useRowShortcut, Boolean computeVisibleRows, Boolean invalidInAdjustFillingColumns, Boolean repositionEditingControl)
   at System.Windows.Forms.DataGridView.OnColumnCollectionChanged_PreNotification(CollectionChangeEventArgs ccea)
   at System.Windows.Forms.DataGridViewColumnCollection.Clear()
   at System.Windows.Forms.DataGridView.Dispose(Boolean disposing)
   at System.ComponentModel.Component.Dispose()
   at System.Windows.Forms.Control.Dispose(Boolean disposing)
   at System.ComponentModel.Component.Dispose()
   at System.Windows.Forms.Control.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Dispose(Boolean disposing)
   at MusicBeePlugin.MultipleSearchReplaceCommand.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Close()
   at MusicBeePlugin.PluginWindowTemplate.display(Boolean modalForm)
   at MusicBeePlugin.Plugin.multipleSearchReplaceEventHandler(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)

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 11, 2018, 03:50:53 AM
Thanks! It now restores the hidden window.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2018, 10:36:18 AM
"Split <Tag 1> to tags <Tag 2>, <Tag 3>, <Tag 4>" preset doesn't work.
I have to use "Split <Tag 1> to tags <Tag 2>, <Tag 3>" preset twice.
If that's also about the parentheses handling, will you fix the issue by changing the meta-character?

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2018, 05:13:57 PM
Thanks! that preset is now working properly.
But there are more issues. The two performer presets have not been working for some time. Don't know when it worked last time.
Also msr command and preset were broken but now start working again. Still there's some issue when parentheses are used.

Try this:
*^(.*?)b/$1c

It works with msr command, but not with msr preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2018, 05:27:03 PM
Now MB supports 32 virtual tags. Can you support those additional tags with copy tag & ASR coammnd?

Also "Folder name" and "Path" are missing from read-only tag list. Can you add them as part of that value can be used for other tags?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2018, 07:42:01 PM
i'll have a look at all 3 issues tomorrow.
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 20, 2018, 12:32:57 PM
Found the following entries in my error log this morning.  I'm pretty sure these occurred upon opening MB as I don't think I was yet playing anything at the time they were thrown.


4/19/2018 12:30:20 AM - 10.0.16299.0 - 3.2.6665.34905 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
   at System.Collections.Generic.List`1.Enumerator.MoveNext()
   at #=zfVOWnuz6Wh$HaskOtzmfiedeH9NK.#=ztizM69awK7T3(Boolean #=z1ch4PUrz3iUf, SortOrder #=zeks4fPAvS$yoHmsdNA==)
   at #=zfVOWnuz6Wh$HaskOtzmfiedeH9NK.#=zhnpL8w8=(#=zpnkmxwY4IX__pZjMupoooME= #=z9P49bjQ=)
   at #=z4$90odPQW5q9S2kLFw==.#=zIxnsWjiZbPJh(String #=zhNzA16PTIpIO, String #=z_x8_vbgH6Yw8)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.AutoApply(Object currentFileObj, Object tagToolsPluginObj)
   at MusicBeePlugin.Plugin.ReceiveNotification(String sourceFileUrl, NotificationType type)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=z4$90odPQW5q9S2kLFw==.#=zIQ$i_ckXhk3p()

4/19/2018 12:30:21 AM - 10.0.16299.0 - 3.2.6665.34905 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
   at System.Collections.Generic.List`1.Enumerator.MoveNext()
   at #=zfVOWnuz6Wh$HaskOtzmfiedeH9NK.#=ztizM69awK7T3(Boolean #=z1ch4PUrz3iUf, SortOrder #=zeks4fPAvS$yoHmsdNA==)
   at #=zfVOWnuz6Wh$HaskOtzmfiedeH9NK.#=zhnpL8w8=(#=zpnkmxwY4IX__pZjMupoooME= #=z9P49bjQ=)
   at #=z4$90odPQW5q9S2kLFw==.#=zIxnsWjiZbPJh(String #=zhNzA16PTIpIO, String #=z_x8_vbgH6Yw8)
   at MusicBeePlugin.AdvancedSearchAndReplacePlugin.AutoApply(Object currentFileObj, Object tagToolsPluginObj)
   at MusicBeePlugin.Plugin.ReceiveNotification(String sourceFileUrl, NotificationType type)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=z4$90odPQW5q9S2kLFw==.#=zIQ$i_ckXhk3p()

Don't know if it's related, but when I opened MB this morning it immediately locked up without loading the library or anything else (last.fm icon at the bottom was "!" for example). I had to "End Task" it in the Task Manager and then it worked fine when I reopened it.

EDIT: Looking back, I see this error kind of frequently in my error log going back to January 2018 when I was using MB version 3.1.6596.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 20, 2018, 02:27:20 PM
Thanks! that preset is now working properly.
But there are more issues. The two performer presets have not been working for some time. Don't know when it worked last time.
Also msr command and preset were broken but now start working again. Still there's some issue when parentheses are used.

Try this:
*^(.*?)b/$1c

It works with msr command, but not with msr preset.
redwing, use now double brackets for asr functions, eg. \@tc[[$1]]

i'm afraid i haven't tested new version thoroughly enough though.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip

EDIT: i've made some bugfixes. link is the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 20, 2018, 03:01:12 PM
Found the following entries in my error log this morning.  I'm pretty sure these occurred upon opening MB as I don't think I was yet playing anything at the time they were thrown.

Don't know if it's related, but when I opened MB this morning it immediately locked up without loading the library or anything else (last.fm icon at the bottom was "!" for example). I had to "End Task" it in the Task Manager and then it worked fine when I reopened it.

EDIT: Looking back, I see this error kind of frequently in my error log going back to January 2018 when I was using MB version 3.1.6596.
can you reproduce this error with latest version of plugin?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 20, 2018, 03:04:09 PM
Also "Folder name" and "Path" are missing from read-only tag list. Can you add them as part of that value can be used for other tags?
no, because these pseudo tags are not a tags (even virtual tags), they are virtual tag functions represented as tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 20, 2018, 03:41:34 PM
Found the following entries in my error log this morning.  I'm pretty sure these occurred upon opening MB as I don't think I was yet playing anything at the time they were thrown.

Don't know if it's related, but when I opened MB this morning it immediately locked up without loading the library or anything else (last.fm icon at the bottom was "!" for example). I had to "End Task" it in the Task Manager and then it worked fine when I reopened it.

EDIT: Looking back, I see this error kind of frequently in my error log going back to January 2018 when I was using MB version 3.1.6596.
can you reproduce this error with latest version of plugin?
I've just updated.  Since I'm not sure what produced it, I'm not sure how to know whether I can reproduce it, but I'll keep an eye in the error log and let you know.  This month I've gotten it on the 2nd, twice within a second on the 5th, and twice within a second last night - all of them seem to have been at a time when I would initially open MB.  May be a couple of weeks before I'll know whether it's solved or not since it's so random.
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 20, 2018, 03:48:13 PM
Also, while I'm here and all, this has been the way the plug-in's "Setting" dialog has looked to me for as long as I can remember.  

(http://i.thinimg.com/img/34il.png)

If the picture goes away for some reason in the future, a portion of the bottom of the box is cut-off.  It's not expandable in any direction.  My screen's at 1920X1080 and I don't have any scaling applied that I'm aware of.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 20, 2018, 05:36:04 PM
Thanks! that preset is now working properly.
But there are more issues. The two performer presets have not been working for some time. Don't know when it worked last time.
Also msr command and preset were broken but now start working again. Still there's some issue when parentheses are used.

Try this:
*^(.*?)b/$1c

It works with msr command, but not with msr preset.
redwing, use now double brackets for asr functions, eg. \@tc[[$1]]

i'm afraid i haven't tested new version thoroughly enough though.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip

EDIT: i've made some bugfixes. link is the same.

None of the reported issues are fixed.
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 25, 2018, 05:44:47 AM
I've got a Search and Replace preset that clears "Last Played" and sets Play Count to 0.  Well, it used to.  Now (version 5.0.6683? I can't really see the version number per my previous post), the blank "Replace" field that previously worked shows "SYNTAX ERROR!" in the "New tag value" field when I preview.

I can get around this by making it replace "Last Played" with "Unknown" (or anything else, I guess) but I'd prefer not to do this since Last Played is defined as a date field and, I think, is blank by default.  Blanking it out has been working fine for me forever.

Any ideas on how to get around this?  What can I put in Last Played to make MB think the file has never been played?
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on April 25, 2018, 10:04:22 AM
I've got a Search and Replace preset that clears "Last Played" and sets Play Count to 0.  Well, it used to.  Now (version 5.0.6683? I can't really see the version number per my previous post), the blank "Replace" field that previously worked shows "SYNTAX ERROR!" in the "New tag value" field when I preview.

I can get around this by making it replace "Last Played" with "Unknown" (or anything else, I guess) but I'd prefer not to do this since Last Played is defined as a date field and, I think, is blank by default.  Blanking it out has been working fine for me forever.

Any ideas on how to get around this?  What can I put in Last Played to make MB think the file has never been played?

I was just thinking quite the opposite, how could I consign "Last Played date and time" to a tag - as that is one important detail that I would like to be able to preserve within the music file - (in case of a complete re-ruild of the MB library from scratch, as was recently required)..
Freddy :-)
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 25, 2018, 12:26:03 PM
I've got a Search and Replace preset that clears "Last Played" and sets Play Count to 0.  Well, it used to.  Now (version 5.0.6683? I can't really see the version number per my previous post), the blank "Replace" field that previously worked shows "SYNTAX ERROR!" in the "New tag value" field when I preview.

I can get around this by making it replace "Last Played" with "Unknown" (or anything else, I guess) but I'd prefer not to do this since Last Played is defined as a date field and, I think, is blank by default.  Blanking it out has been working fine for me forever.

Any ideas on how to get around this?  What can I put in Last Played to make MB think the file has never been played?

I was just thinking quite the opposite, how could I consign "Last Played date and time" to a tag - as that is one important detail that I would like to be able to preserve within the music file - (in case of a complete re-ruild of the MB library from scratch, as was recently required)..
Freddy :-)
I use it for very specific cases.  After I add an album to the inbox and preview it to see which tracks I want to add to my playlist, I clear the playdata so that the preview play "doesn't count." 

I also clear it for the first two weeks after a song is added to my library so that it'll come up in my playdata related autoplaylists more often. Once a song is played, it isn't eligible for play again in these playlists for 6 months.

Having this data in a tag would be helpful. Having a full playdata history for a song would be even better.
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 25, 2018, 12:27:01 PM
I've got a Search and Replace preset that clears "Last Played" and sets Play Count to 0.  Well, it used to.  Now (version 5.0.6683? I can't really see the version number per my previous post), the blank "Replace" field that previously worked shows "SYNTAX ERROR!" in the "New tag value" field when I preview.

I can get around this by making it replace "Last Played" with "Unknown" (or anything else, I guess) but I'd prefer not to do this since Last Played is defined as a date field and, I think, is blank by default.  Blanking it out has been working fine for me forever.

Any ideas on how to get around this?  What can I put in Last Played to make MB think the file has never been played?

I was just thinking quite the opposite, how could I consign "Last Played date and time" to a tag - as that is one important detail that I would like to be able to preserve within the music file - (in case of a complete re-ruild of the MB library from scratch, as was recently required)..
Freddy :-)
I use it for very specific cases.  After I add an album to the inbox and preview it to see which tracks I want to add to my playlist, I clear the playdata so that the preview play "doesn't count."  

I also clear it for the first two weeks after a song is added to my library so that it'll come up in my playdata related autoplaylists more often. This is done automatically by the plugin. I do this because, once a song is played, it isn't eligible for play again in these playlists for 6 months.

Having this data in a tag would be helpful. Having a full playdata history for a song would be even better.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on April 25, 2018, 03:12:46 PM
1) I also clear it for the first two weeks after a song is added to my library so that it'll come up in my playdata related autoplaylists more often. Once a song is played, it isn't eligible for play again in these playlists for 6 months.

2) Having this data in a tag would be helpful. Having a full playdata history for a song would be even better.

1) For very similar results, you may want to try something like:-
     Match: All of the following rules
     Date Added is in the last 30 days (or whatever works for you)
     Last Played is not in the last 30 days
     Limit to NN items selected by: Least recently played

2) I can appreciate how full 'playdata history' would benefit many MB users, but not sure it would be something I could utilise, and probably be a pain to implement!

If anyone knows of a method of using "Additional Tagging Tools" etc. to add the "Last Played Date and Time" to a TAG, I would be most interested to hear it! I have seen that there is a way to update Play Count into a tag somewhere in the Forums...

Best regards: Freddy :-)
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 25, 2018, 03:46:57 PM
1) For very similar results, you may want to try something like:-
     Match: All of the following rules
     Date Added is in the last 30 days (or whatever works for you)
     Last Played is not in the last 30 days
     Limit to NN items selected by: Least recently played
That's actually not similar at all.  Thanks, though.  I want new tracks (3 months, actually) in my playlist no matter how many times they've been played. I want new music in constant rotation. For the first two weeks, I automatically clear the play data so that none of it counts toward any quota. From the 92nd day of age on, I only want to hear a song every 6 months at the most, even if the play was from within day 15 to 91. 

I've got it working fine.  It's just this "SYNTAX ERROR!" that's got me down right now.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on April 25, 2018, 04:03:56 PM
I want new tracks (3 months, actually) in my playlist no matter how many times they've been played. I want new music in constant rotation. For the first two weeks, I automatically clear the play data so that none of it counts toward any quota. From the 92nd day of age on, I only want to hear a song every 6 months at the most, even if the play was from within day 15 to 91.

I've got it working fine.  It's just this "SYNTAX ERROR!" that's got me down right now.

I'm sure there's a way to automate all of that good stuff with auto-playlists... probably!  ???
Regards: Freddy
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on April 25, 2018, 04:13:30 PM
I'm sure there's a way to automate all of that good stuff with auto-playlists... probably!  ???
Regards: Freddy
Yes, I already do as I said earlier.  Thanks for the advice, though.

It's really just the "SYNTAX ERROR!" where there wasn't one before that I'm asking about.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on April 25, 2018, 04:38:55 PM
Yes, I already do as I said earlier.  Thanks for the advice, though.

It's really just the "SYNTAX ERROR!" where there wasn't one before that I'm asking about.

Always ready to help if I can, alas not with Syntax Errors, I had a play with the Tagging Tool but failed miserably, but got help with a fix, which worked like a charm, 'code' still made little sense to me!!
Hope you get sorted! Freddy  ;) 
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 01, 2018, 12:39:49 PM
Recently I noticed some tracks' song info doesn't scroll properly on the player bar. Turned out they had a carriage return character at the end of title tag value. That came from "Paste tags from clipboard" command when copying multiple tags from Notepad++.
Can you make the command ignore that character at the end of each tag value while doing copy & paste?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 06, 2018, 07:49:54 PM
some bugfixes (not the latest ones :/)

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 07, 2018, 12:42:54 PM
Also, while I'm here and all, this has been the way the plug-in's "Setting" dialog has looked to me for as long as I can remember.  

(http://i.thinimg.com/img/34il.png)

If the picture goes away for some reason in the future, a portion of the bottom of the box is cut-off.  It's not expandable in any direction.  My screen's at 1920X1080 and I don't have any scaling applied that I'm aware of.
its fixed for the next update
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 07, 2018, 12:55:18 PM
Thanks! that preset is now working properly.
But there are more issues. The two performer presets have not been working for some time. Don't know when it worked last time.
Also msr command and preset were broken but now start working again. Still there's some issue when parentheses are used.

Try this:
*^(.*?)b/$1c

It works with msr command, but not with msr preset.
is working fine for me for all cases: msr preset or msr command.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 07, 2018, 01:03:34 PM
very long thread, so maybe i've missed some issues.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 08, 2018, 07:17:21 PM
also i've added support for up to 32 virtual tags. the same link.
Title: Re: Additional Tagging and Reporting Tools
Post by: Franklin on May 10, 2018, 01:40:02 AM
Been getting this error whenever I run the library reports, recently started happening after I'd copy the tag from Artist to Album Artist

MusicBee v3.1.6590.32668 (Win10.0), 9 May 2018 17:35:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.LibraryReportsPlugin.AggregatedTags.GetField(KeyValuePair`2 keyValue, Int32 fieldNumber, List`1 groupingNames)
   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: redwing on May 10, 2018, 04:11:23 PM
Thanks! that preset is now working properly.
But there are more issues. The two performer presets have not been working for some time. Don't know when it worked last time.
Also msr command and preset were broken but now start working again. Still there's some issue when parentheses are used.

Try this:
*^(.*?)b/$1c

It works with msr command, but not with msr preset.
is working fine for me for all cases: msr preset or msr command.

The two performer presets are now working. Thanks!

For the msr issue,
try the code to a string with a comma (for instance "a,bc"), then msr preset isn't working while msr command works.

also i've added support for up to 32 virtual tags. the same link.

It supports up to Virtual25 tag. It doesn't support Virtual26 - 32 tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 11, 2018, 10:37:42 PM
Another bug with both msr preset and command:
Try " bc/ cc" for the string "a bc". Both don't work properly. I think it has problem handling a space. Sometimes it works only for first track when multiple tracks are selected.

Also, currently copy tag command and msr command use the same source/target tag setting. Can you make each command use its own setting so that each command remembers its own last used tag set?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 15, 2018, 01:27:16 PM
Recently I noticed some tracks' song info doesn't scroll properly on the player bar. Turned out they had a carriage return character at the end of title tag value. That came from "Paste tags from clipboard" command when copying multiple tags from Notepad++.
Can you make the command ignore that character at the end of each tag value while doing copy & paste?
redwing, carriage returns are used to split tags of different tracks (and tabs are used to split tags of single tracks). there must be something else.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 15, 2018, 01:30:51 PM
Been getting this error whenever I run the library reports, recently started happening after I'd copy the tag from Artist to Album Artist

MusicBee v3.1.6590.32668 (Win10.0), 9 May 2018 17:35:

System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at MusicBeePlugin.LibraryReportsPlugin.AggregatedTags.GetField(KeyValuePair`2 keyValue, Int32 fieldNumber, List`1 groupingNames)
   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()
lib reports is working fine foe me. try to delete all groupings/aggregated functions and recreate them from scratch.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 15, 2018, 01:35:37 PM
also i've added support for up to 32 virtual tags. the same link.

It supports up to Virtual25 tag. It doesn't support Virtual26 - 32 tags.
i've reuploaded plugin (because i see all 32 virtual tags).
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 15, 2018, 02:51:07 PM
For the msr issue,
try the code to a string with a comma (for instance "a,bc"), then msr preset isn't working while msr command works.
use \, for search pattern of msr preset. msr command will auto-escape commas.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 15, 2018, 02:56:17 PM
i've reuploaded plugin (because i see all 32 virtual tags).

It's fixed now.

carriage returns are used to split tags of different tracks

Yep, that's what I meant. Try it yourself. If you copy tags from tracks and paste it, it works fine. But if you copy tags from notepad++, it adds carriage return at the end of the tag (if you copy three lines of values for three tracks and paste it, only the first two tracks get carriage return).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 15, 2018, 02:58:54 PM
use \, for search pattern of msr preset. msr command will auto-escape commas.

Are there any other characters behave that way that I should know of?
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on May 16, 2018, 06:41:06 AM
One minor thing I noticed - when you copy "Last Played" or "Date Added" to clipboard and then paste them to files, the pasted version does not respect local time (i.e., if I copy tags from file that was last played at 10PM local time, it will paste as what I'm assuming is GMT into the file - 6 hours offset). Not a big deal, but unexpected.

Still seeing "SYNTAX ERROR!" when trying to "blank out" (erase the value of by replacing with empty values) Last Played and Play Count as reported earlier.  Not sure how to "properly" handle these.  It worked in earlier versions to just put nothing in the replace with field. 
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 16, 2018, 05:44:26 PM
Yep, that's what I meant. Try it yourself. If you copy tags from tracks and paste it, it works fine. But if you copy tags from notepad++, it adds carriage return at the end of the tag (if you copy three lines of values for three tracks and paste it, only the first two tracks get carriage return).
why not just add additional carriage return after last line in notepad++?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 16, 2018, 05:46:02 PM
use \, for search pattern of msr preset. msr command will auto-escape commas.

Are there any other characters behave that way that I should know of?
all other chars are enumerated in msr preset description.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 16, 2018, 05:54:06 PM
Yep, that's what I meant. Try it yourself. If you copy tags from tracks and paste it, it works fine. But if you copy tags from notepad++, it adds carriage return at the end of the tag (if you copy three lines of values for three tracks and paste it, only the first two tracks get carriage return).
why not just add additional carriage return after last line in notepad++?

My request is not add it to any tags.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 16, 2018, 05:57:06 PM
Another bug with both msr preset and command:
Try " bc/ cc" for the string "a bc". Both don't work properly. I think it has problem handling a space. Sometimes it works only for first track when multiple tracks are selected.

It's not fixed for msr command. Try it with multiple files and only first track changes.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 16, 2018, 06:46:48 PM
Still seeing "SYNTAX ERROR!" when trying to "blank out" (erase the value of by replacing with empty values) Last Played and Play Count as reported earlier.  Not sure how to "properly" handle these.  It worked in earlier versions to just put nothing in the replace with field.  

its fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 16, 2018, 06:49:32 PM
Yep, that's what I meant. Try it yourself. If you copy tags from tracks and paste it, it works fine. But if you copy tags from notepad++, it adds carriage return at the end of the tag (if you copy three lines of values for three tracks and paste it, only the first two tracks get carriage return).
why not just add additional carriage return after last line in notepad++?

My request is not add it to any tags.
could you post a screenshot of notepad++ with service chars shown 'couse i dont understand what do you want?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 16, 2018, 06:51:32 PM
Another bug with both msr preset and command:
Try " bc/ cc" for the string "a bc". Both don't work properly. I think it has problem handling a space. Sometimes it works only for first track when multiple tracks are selected.

It's not fixed for msr command. Try it with multiple files and only first track changes.
have completely forgotten about your bug report related to spaces. will have a look at it today.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 16, 2018, 07:02:26 PM
could you post a screenshot of notepad++ with service chars shown 'couse i dont understand what do you want?

Never mind. If Steven fixes the scroll issue, it's OK.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 24, 2018, 05:35:25 PM
Another bug with both msr preset and command:
Try " bc/ cc" for the string "a bc". Both don't work properly. I think it has problem handling a space. Sometimes it works only for first track when multiple tracks are selected.

It's not fixed for msr command. Try it with multiple files and only first track changes.
its fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 25, 2018, 09:19:29 AM
It's fixed. Thanks!

Can you consider this request? Every time using either command I have to keep changing selected tag option.

currently copy tag command and msr command use the same source/target tag setting. Can you make each command use its own setting so that each command remembers its own last used tag set?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 29, 2018, 02:50:57 PM
yes, of course.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on May 29, 2018, 03:02:29 PM
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 29, 2018, 04:10:29 PM
Thanks a lot!
Title: Re: Additional Tagging and Reporting Tools
Post by: rotong on June 06, 2018, 07:52:34 AM
This wonderful plug-in keeps unloading itself lately. At MB startup I must manually add the plug-in again and again. Now  I'm doing this by modifying the Musicbee3Settings.ini:

<Id>C:\Users\Robert\AppData\Roaming\MusicBee\Plugins\mb_TagTools.dll</Id>
  <Name>Additional Tagging Tools</Name>
  <Description>Adds some tagging tools to MusicBee</Description>
  <Enabled>false</Enabled>

and set false to true.

I have the latest version of both MB and MB_tagtools installed!
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on June 06, 2018, 11:26:37 AM
Try white-listing the dll in your security software. Or perhaps white-listing the entire MB folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: rotong on June 07, 2018, 02:21:00 PM
Try white-listing the dll in your security software. Or perhaps white-listing the entire MB folder.

Good Tip..
Thank you!
Title: Re: Additional Tagging and Reporting Tools
Post by: rotong on June 08, 2018, 07:12:17 AM
Sorry but white listing the .dll does not work. It still disables itself. I must manually modify the musicbee3settings.ini to make it work again.
Perhaps another solution?
Title: Re: Additional Tagging and Reporting Tools
Post by: rotong on June 11, 2018, 02:04:58 PM
Still having problems that the mb_tagtools.dll won't load after the computer has been properly shutdown. Every time I have to manually add the plugin again in the preferences. When an user has been logged off and logged on again there is nothing the matter and the .dll normally loads! I haven't a clue whats going on here. The mb_tagTools.dll has been white listed. I never had this problem before....
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on June 11, 2018, 04:35:03 PM
Still having problems that the mb_tagtools.dll won't load after the computer has been properly shutdown. Every time I have to manually add the plugin again in the preferences. When an user has been logged off and logged on again there is nothing the matter and the .dll normally loads! I haven't a clue whats going on here. The mb_tagTools.dll has been white listed. I never had this problem before....

Then it could be related to one of startup processes of your machine. Check MB's error log when it gets disabled. Also try deleting the plugin's settings file in MusicBee\AppData\ folder.
Title: Re: Additional Tagging and Reporting Tools
Post by: rotong on June 11, 2018, 05:23:46 PM
Well I guess I've found the culprit. MusicBee.exe and the MB_TagTools.dll do not have a digital signature! Kaspersky Internet Security prohibits loading the MB_TagTools.dll into MusicBee. I 've  setup Kaspersky not to watch over other processes initiated by MusicBee! Now it's loading without any problems.
Title: Plug in not populating
Post by: OwnDog on June 15, 2018, 02:19:09 PM
Running MB 3.2
Windows 10
trying to use additional tagging tools but presets are not loading
Dopwnloaded latest version of plug for MB 3.2 in from wiki

I know I am doing something wrong but damned if I can see it.
Title: Re: Additional Tagging and Reporting Tools
Post by: Tybot on June 23, 2018, 03:13:19 AM
I'm trying to set up a couple of "copy" presets. Is there a way to choose to only apply those if the destination is empty?

Let's say I have an album with ten tracks. Two of those tracks already have a "display artist" tag, how would I go about copying the artist tag to the display artist tag for the remaining eight tracks?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 06, 2018, 01:04:14 AM
I'm trying to set up a couple of "copy" presets. Is there a way to choose to only apply those if the destination is empty?

Let's say I have an album with ten tracks. Two of those tracks already have a "display artist" tag, how would I go about copying the artist tag to the display artist tag for the remaining eight tracks?
i can create additional 'copy' preset for this purpose.
Title: Re: Additional Tagging and Reporting Tools
Post by: Tybot on July 11, 2018, 02:58:00 AM
I'm trying to set up a couple of "copy" presets. Is there a way to choose to only apply those if the destination is empty?

Let's say I have an album with ten tracks. Two of those tracks already have a "display artist" tag, how would I go about copying the artist tag to the display artist tag for the remaining eight tracks?
i can create additional 'copy' preset for this purpose.

Thanks for the offer but there's no need to do it if it's just for the case I described above. Turns out MB itself didn't really jive with the way I was doing things so I no longer have any use for such a preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on July 12, 2018, 01:23:22 AM
I'm trying to set up a couple of "copy" presets. Is there a way to choose to only apply those if the destination is empty?

Let's say I have an album with ten tracks. Two of those tracks already have a "display artist" tag, how would I go about copying the artist tag to the display artist tag for the remaining eight tracks?
i can create additional 'copy' preset for this purpose.

Thanks for the offer but there's no need to do it if it's just for the case I described above. Turns out MB itself didn't really jive with the way I was doing things so I no longer have any use for such a preset.

@boroda74
I would love to have a 'copy' preset that would only copy if the 'from' tag wasn't null value.

eg. copying "Display Artist" to a custom tag "Artist: Display", but only if "Display Artist" has a value.

I currently do this for both "Display Artist" and "Display Composer" by using a virtual tag in my regex, but having the preset handle it would free up 2 virtual tags!
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on July 12, 2018, 07:56:06 AM
Running "Replace Unicode punctuation marks by ASCII punctuation marks" preset deletes the entire value if it contains a comma.
Title: Re: Additional Tagging and Reporting Tools
Post by: FrisBäh on July 16, 2018, 12:14:16 AM
(https://i.imgur.com/l2crx0C.gif)

Something like this in the track listing window would be nice. It would speed up the process massively:

(https://i.imgur.com/4XdFj34.gif)
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on August 02, 2018, 12:36:09 AM
On one of my periodic drops back in to the forum and the plugin isn't loading for me currently. Running the latest MB patch and the 29-05-18 version of the plugin. MB loads with it disabled and then, when I try to enable it, MB pops up with the error message "Unable to initialise this plugin: Exception has been thrown by the target of an invocation.". Any ideas on the problem?
Title: Re: Additional Tagging and Reporting Tools
Post by: calderino on August 08, 2018, 03:09:05 AM
Hi,
is it possible to support "user-defined" tags?
I use some personal tags in my files, and I want to automatically copy them into a custom Musicbee tag.

For example,
I have a tag "SOURCE" that does not correspond to any existing tag, I would like to do
Copy Tags... > SOURCE to Custom6 for example.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on August 08, 2018, 09:46:54 AM
Hi,
is it possible to support "user-defined" tags?
I use some personal tags in my files, and I want to automatically copy them into a custom Musicbee tag.

For example,
I have a tag "SOURCE" that does not correspond to any existing tag, I would like to do
Copy Tags... > SOURCE to Custom6 for example.

This method by @Redwing explains how to copy Play count,  but can be adapted, as my posts later in the thread will show..

https://getmusicbee.com/forum/index.php?topic=12987.msg78287#msg78287

Freddy
Title: Re: Additional Tagging and Reporting Tools
Post by: parky105 on August 15, 2018, 07:02:39 PM
Hi,

I dont know if anyone can help, but when I open Advanced search and replace, I have no pre-sets at all, I am using the windows store version but I did try uninstalling and downloading Musicbee off the website, but still the same no pre-sets when I open the setting, any help at all would be most welcome
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on August 16, 2018, 04:21:03 AM
Hi,

I dont know if anyone can help, but when I open Advanced search and replace, I have no pre-sets at all, I am using the windows store version but I did try uninstalling and downloading Musicbee off the website, but still the same no pre-sets when I open the setting, any help at all would be most welcome
You have to do either "Import" (to choose specific ones of interest) or "Import All" to bring them all in (which can be a little overwhelming as a list).
Title: Re: Additional Tagging and Reporting Tools
Post by: parky105 on August 16, 2018, 02:57:05 PM
Hi,

I dont know if anyone can help, but when I open Advanced search and replace, I have no pre-sets at all, I am using the windows store version but I did try uninstalling and downloading Musicbee off the website, but still the same no pre-sets when I open the setting, any help at all would be most welcome
You have to do either "Import" (to choose specific ones of interest) or "Import All" to bring them all in (which can be a little overwhelming as a list).
Thanks for your help but I cant get it to work unless I am doing something stupid, I click Import All, and it says no presets where imported.

(https://i.imgur.com/RODuT6N.gif)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2018, 04:48:30 PM
Hi,

I dont know if anyone can help, but when I open Advanced search and replace, I have no pre-sets at all, I am using the windows store version but I did try uninstalling and downloading Musicbee off the website, but still the same no pre-sets when I open the setting, any help at all would be most welcome
check 'Musicbee\Plugins\ASR Presets' folder. it must contain ~100 .xml files.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2018, 04:52:03 PM
Running "Replace Unicode punctuation marks by ASCII punctuation marks" preset deletes the entire value if it contains a comma.
i see this bug, will try to fix it.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2018, 04:55:18 PM
@boroda74
I would love to have a 'copy' preset that would only copy if the 'from' tag wasn't null value.

eg. copying "Display Artist" to a custom tag "Artist: Display", but only if "Display Artist" has a value.

I currently do this for both "Display Artist" and "Display Composer" by using a virtual tag in my regex, but having the preset handle it would free up 2 virtual tags!
i'll try to do this tomorrow.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2018, 04:57:46 PM
(https://i.imgur.com/l2crx0C.gif)

Something like this in the track listing window would be nice. It would speed up the process massively:

(https://i.imgur.com/4XdFj34.gif)
1st bug will be definitely fixed today, second request is too hard.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 16, 2018, 04:59:06 PM
On one of my periodic drops back in to the forum and the plugin isn't loading for me currently. Running the latest MB patch and the 29-05-18 version of the plugin. MB loads with it disabled and then, when I try to enable it, MB pops up with the error message "Unable to initialise this plugin: Exception has been thrown by the target of an invocation.". Any ideas on the problem?
try to delete <AppData>\mb_tagtools.settings.xml file.
Title: Re: Additional Tagging and Reporting Tools
Post by: parky105 on August 16, 2018, 06:02:20 PM
Hi,

I dont know if anyone can help, but when I open Advanced search and replace, I have no pre-sets at all, I am using the windows store version but I did try uninstalling and downloading Musicbee off the website, but still the same no pre-sets when I open the setting, any help at all would be most welcome
check 'Musicbee\Plugins\ASR Presets' folder. it must contain ~100 .xml files.
Hi thanks for getting back to me, sorry I cant find that folder, I am using Musicbee  from the windows store, I believe the Musicbee app is inside a hidden windows app folder, would it be anywhere else.
Title: Re: Additional Tagging and Reporting Tools
Post by: Steven on August 16, 2018, 09:26:58 PM
the windows store folder will be something like:
C:\Users\<your id>\AppData\Local\Packages\50072StevenMayall.MusicBee_kcr266et74avj\LocalCache\Roaming\MusicBee
Title: Re: Additional Tagging and Reporting Tools
Post by: parky105 on August 16, 2018, 10:30:05 PM
the windows store folder will be something like:
C:\Users\<your id>\AppData\Local\Packages\50072StevenMayall.MusicBee_kcr266et74avj\LocalCache\Roaming\MusicBee
Many thanks for that, inside that folder was a ASR presets folder but it was empty, there was also a plugin folder and inside that was another ASR presets folder with 103 files in, which I copied over to the empty folder and now all the presets show when I open the setting, many thanks to everyone who helped me sort this out.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 17, 2018, 11:25:39 AM
known bugs are fixed (don't forget to reimport new asr presets):

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

@redwing: now use ;; instead of comma as asr function parameter separator (eg. \@tc[[$1;;a the an]]).

@Bee-liever: your requset is not done yet, but will be.



edit: minor MSR bug is fixed. download link is the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 17, 2018, 11:40:56 AM
What presets have changed? Are there any except the unicode preset?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 17, 2018, 11:42:32 AM
What presets have changed? Are there any except the unicode preset?

unicode preset and all presets with 2 parameter asr functions (i've replaced , by ;; ).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 17, 2018, 11:58:44 AM
I'm still having the carriage return issue and have to keep removing it every time after using the paste selected tags command.

Let me explain what the issue is:

Select 5 tracks> run copy selected tags command for title> paste it to other tracks.
It works fine and the pasted tags have no carriage return in their tag values.

Now paste it to notepad++> copy those five lines> paste it to some tracks.
Now the first four tracks have carriage return character in their values.

Do you see the differences? My request is when pasting selected tags, if the tag has the carriage return character at the end of the value, then remove it when writing the tag.

The reason is I am frequently copying selected tags from notepad++ rather than other tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 17, 2018, 01:38:44 PM
not sure why this happens, but try this version:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 17, 2018, 01:59:40 PM
Great! Now it no longer writes the character at the end of the tag when pasting tags.
Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 17, 2018, 03:06:11 PM
Bee-leiver, find second 'copy tag' preset:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 17, 2018, 03:12:01 PM
@redwing, i've reenabled persistent windows. link is the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 18, 2018, 02:42:32 PM
The add-on page of this plugin links to an outdated version. Why not change the link to mb_TagTools_latest.zip file?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 19, 2018, 01:47:01 PM
What presets have changed? Are there any except the unicode preset?

unicode preset and all presets with 2 parameter asr functions (i've replaced , by ;; ).

The new multiple search & replace preset has a bug:
Try
*(b)/$1aa
It works fine with MSR command, but not with ASR command. So it can't be used via a hotkey.

Also, it doesn't add a proper escape sequences to special characters when they are entered via MSR command (previous versions had the same bug).
For instance enter "#" or "*" to the first box.
Then if you open the ASR preset it's saved as either "#/abc" or "*/abc" rather than "\#/abc" or "\*/abc".
Title: Re: Additional Tagging and Reporting Tools
Post by: zkhcohen on August 22, 2018, 10:50:10 PM
How would you copy a single part of a tag from one file to another? I'm trying to copy artist pictures from one to another.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on August 26, 2018, 06:56:39 AM
Bee-leiver, find second 'copy tag' preset:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Thank you!
Title: Re: Additional Tagging and Reporting Tools
Post by: SpirosG on August 28, 2018, 03:30:39 PM
If we have the "date created" tag in this Form ex. "28-8-2018" is there any way to convert it to "2018-08-28"
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on August 29, 2018, 05:58:08 PM
If we have the "date created" tag in this Form ex. "28-8-2018" is there any way to convert it to "2018-08-28"

Date display format

Date display format in MB follows your Windows short date format. It applies to various "year" tags and "date" tags. Thus editing year tag format with tag editor won't change its displayed format within MB.
You could also use virtual tags with $Date function if you want to keep your Windows setting in a different way.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on September 04, 2018, 03:04:04 PM
On one of my periodic drops back in to the forum and the plugin isn't loading for me currently. Running the latest MB patch and the 29-05-18 version of the plugin. MB loads with it disabled and then, when I try to enable it, MB pops up with the error message "Unable to initialise this plugin: Exception has been thrown by the target of an invocation.". Any ideas on the problem?
try to delete <AppData>\mb_tagtools.settings.xml file.

Thanks boroda, that worked.

Has the formula for converting ReplayGain to Soundcheck changed? It used to produce something like this "00000943 00000943 00001728 00001728 00024CA8 00024CA8 00007AAD 00007AAD 00024CA8 00024CA8" but now it explicitly writes out what the changes are (like ReplayGain does).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2018, 04:04:18 PM
If you copy any date time tag to last played, it doesn't write a correct hour. Can you take a look?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 01, 2018, 04:07:43 PM
Another bug with MSR command: you can't deselect individual tracks from the preview screen.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on October 04, 2018, 12:35:53 AM
Has the formula for converting ReplayGain to Soundcheck changed? It used to produce something like this "00000943 00000943 00001728 00001728 00024CA8 00024CA8 00007AAD 00007AAD 00024CA8 00024CA8" but now it explicitly writes out what the changes are (like ReplayGain does).

FYI, I fixed this. Turns out I was missing a few presets from AppData but not from the main plugin folder. Copying them all over fixed it. No idea how it happened.
Title: Re: Additional Tagging and Reporting Tools
Post by: Freddy Barker on October 08, 2018, 04:45:29 PM
If you copy any date time tag to last played, it doesn't write a correct hour. Can you take a look?

Makes interesting reading when looking at the current track Scrobbling on Last FM, in a 'time shift' sort of 'back to the future' mode  :-X
(copy tag 'Now' to 'Last Played') - Freddy
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on October 15, 2018, 04:33:01 PM
The context menu for the plugin often disappears when using from the expanded panel of album covers view. If switching to another view, the menu shows up again.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 01, 2018, 08:09:58 PM
Boroda74 hasn't been on the forum since August, but I'm hoping someone can help me with this.

Using the AS&R preset "Remove # characters from the beginning/end of <Tag 1>" I'm trying to remove 5 characters from the end of the track title. I use the drop-down to select 'Title' for Tag 1, but I don't see where there's a field to specify 5 characters. Nor do I see where to specify to remove from the end of the title.

Anyone?

Thanks.
(http://i.imgur.com/PZJPsvZl.jpg) (https://i.imgur.com/PZJPsvZ.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on November 02, 2018, 01:44:23 AM
Using the AS&R preset "Remove # characters from the beginning/end of <Tag 1>" I'm trying to remove 5 characters from the end of the track title. I use the drop-down to select 'Title' for Tag 1, but I don't see where there's a field to specify 5 characters. Nor do I see where to specify to remove from the end of the title.

That preset literally removes "#" characters from both beginning and end of a tag. Use "Remove given number of characters from beginning/end of <Tag 1>" preset instead. Enter "0" and "5" in both custom boxes for your purpose.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on November 02, 2018, 02:17:19 AM
That preset literally removes "#" characters from both beginning and end of a tag. Use "Remove given number of characters from beginning/end of <Tag 1>" preset instead. Enter "0" and "5" in both custom boxes for your purpose.
Ahhh ... The preset I was using removes the -number- sign (#) not a -number- of characters.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: jazzhands on November 27, 2018, 12:08:56 AM
I like to convert ReplayGain values to Itunes soundcheck for legacy purposes. I had that working nicely with this plugin, then had a hard drive failure.

I decided to try using the Windows Store version of MB (currently 3.2.6827) and installed the plugin, but am getting soundcheck values like so:

\@rg2sc4mp3(-1.43 dB)

I saw it earlier in this thread, and wonder if it's because I'm using the "app" versus the standard Win10 installer. Please advise.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on December 09, 2018, 05:49:22 PM
I like to convert ReplayGain values to Itunes soundcheck for legacy purposes. I had that working nicely with this plugin, then had a hard drive failure.

I decided to try using the Windows Store version of MB (currently 3.2.6827) and installed the plugin, but am getting soundcheck values like so:

\@rg2sc4mp3(-1.43 dB)

I saw it earlier in this thread, and wonder if it's because I'm using the "app" versus the standard Win10 installer. Please advise.

Yeah I had this problem. What I did to fix it was delete everything under MusicBee>Plugins>ASR Presets and copy everything from MusicBee>AppData>ASR Presets in instead.
Title: Re: Additional Tagging and Reporting Tools
Post by: whoozwah on January 06, 2019, 06:17:06 PM
I'm trying to set up an ASR preset to auto apply at startup and I'm having some issue. What I want it to do is

If Love tag = L AND rating tag = 3
then replace rating value with 3.5

I already have set up presets to auto Love tracks with ratings of 3.5, 4, 4.5 or 5 so I'm trying to make sure the inverse is true. This allows me to build out smart playlists of music I like based on cloud ratings as I tend to just love a song on last fm and use that as the rating.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on January 10, 2019, 12:39:07 PM
@all, I don't have access to my home pc now, will check all bug/issue reports during month or two.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 03, 2019, 03:48:25 AM
@boroda-

Is there any way to allow an exception to a ticked preset in AS&R?

For example, I have both "Remove the track number from Track title" and "Remove the track number followed by a dash or dot from Track Title" ticked. This has been immensely helpful until today when I added a track with the title of "25 or 6 to 4" and it kept showing up with the title tag of "or 6 to 4". I see why it's happening, but it would be nice if I could exceptions on a per track basis. For the time being I've had to untick both presets.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 03, 2019, 04:26:19 AM
hmm. will be sufficient to have user defined exception value (or maybe value list) for track title (for any input tag in general) in this case?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 03, 2019, 01:19:13 PM
hmm. will be sufficient to have user defined exception value (or maybe value list) for track title (for any input tag in general) in this case?
Yes, I think a list for exceptions would be better than one value.

What I found odd while digging into this later was that I have about 150 tracks that begin with numbers and it was only this one track that had this behavior. I don't understand why (or how) the auto-preset would only affect one but not the others.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 12, 2019, 05:11:30 PM
various bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file



@phred, enter tag exclusions separated by ;; in the list at the bottom of asr.



if somebody wants to tick 'copy tag' preset for auto-applying, but so that it wont copy empty values, just enter ;; in the exception list.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 12, 2019, 08:13:11 PM
@phred, enter tag exclusions separated by ;; in the list at the bottom of asr.
Thanks boroda. I'll have some time to dig into this in the next few days.

And can you please make the window location persistent when you have the change? Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 13, 2019, 03:51:00 AM
@phred, enter tag exclusions separated by ;; in the list at the bottom of asr.
And can you please make the window location persistent when you have the change? Thanks.
of course, its some kind of beta at the moment. :)
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 13, 2019, 08:08:51 PM
of course, its some kind of beta at the moment. :)
Ahhh yes. You've mentioned that before - you don't make the window persistent until you're out of beta. Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: Darwin4Ever on February 14, 2019, 02:13:49 PM
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Is it not possible to offer this file in a location accessible without having to create a (mediafire) account ?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 14, 2019, 02:25:00 PM
Is it not possible to offer this file in a location accessible without having to create a (mediafire) account ?
It is not necessary to register on MediaFire. I clicked on the plugin link and it took me direct to the MediaFire page with a window to download. Click it and it downloads. I did it yesterday, and I just tried it again today.
Title: Re: Additional Tagging and Reporting Tools
Post by: Darwin4Ever on February 14, 2019, 02:40:56 PM

It is not necessary to register on MediaFire. I clicked on the plugin link and it took me direct to the MediaFire page with a window to download. Click it and it downloads. I did it yesterday, and I just tried it again today.
Weird, tried it again and now it works without credentials. The first I tried it I had to enter a Username/PW
Thanks
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 14, 2019, 06:38:37 PM
minor bugfixes. persistent windows are reenabled:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

------------

latest source code:

http://www.mediafire.com/file/s7uwb5y39x3a82y/TagTools_2018-04-19.rar/file
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 14, 2019, 07:35:32 PM
persistent windows are reenabled
8)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 15, 2019, 12:13:09 PM
source code refactored (must work a bit faster):

-plugin:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


-source code:

http://www.mediafire.com/file/mnimta5f8kn1cz3/TagTools_2019-02-15.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 15, 2019, 07:24:27 PM
@boroda...

Perhaps I'm mistaken, but I seem to recall that when using the "Change Case" module, the "New Tag Value" column showed tracks to be changed in blue. That doesn't happen in the version release today. Perhaps in the version released yesterday also, but I hadn't checked it. Nor is the color showing in AS&R proposed changed tracks. I apologize in advance if I'm only imagining it used to do this.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on February 16, 2019, 07:51:29 AM
@boroda
 I think I found a bug in the new version  :o

When you try to access a <Temp #> tag more than once, the regex is applied but all values from the source tag are copied over (see step 2)
(https://i.imgur.com/MxP3KE0.jpg)

all the values of Lyrics? have been appended to the tag:
(https://i.imgur.com/EGIMPKO.jpg)

If I change the output of step 2 to another tag:
(https://i.imgur.com/4FyEf01.jpg)

only the correct regex output is appended to the tag:
(https://i.imgur.com/Fy1aFjn.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on February 16, 2019, 09:41:38 AM
@boroda...

Perhaps I'm mistaken, but I seem to recall that when using the "Change Case" module, the "New Tag Value" column showed tracks to be changed in blue. That doesn't happen in the version release today. Perhaps in the version released yesterday also, but I hadn't checked it. Nor is the color showing in AS&R proposed changed tracks. I apologize in advance if I'm only imagining it used to do this.
no, you are not mistaken. its intentional change, but i'm not sure what is better. I think i'll revert it back.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 16, 2019, 01:25:50 PM
no, you are not mistaken. its intentional change, but i'm not sure what is better. I think i'll revert it back.
Of course -I- think having the coloring is better as it calls attention to the fields that are going to be changed. Which helps me untick tracks that I don't want to change.

Unless you removed it due to some functionality issue, I'd really like to see it restored.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 20, 2019, 05:13:06 PM
Hi all,

Allow me a typical Dummy's Question: Almost 10 yrs (?) a MusicBee user, including ATRTools.
Been inactive for a couple of months due to sight problems - but all ok now after 2 operations!
Had 2x a pc crash too in the meantime.

So now...
I reinstalled MB again, but cannot find how to install the ASR plugin again.
Absolutely not even an idea where to search.
Once I have it back I am sure I will re-teach myself again how to use my favorite features.
But how to begin?
UPDATE: I did find and downloaded the newest ASR-zipfile, unzipped it in a special folder.
But then? No idea anymore...
Also: there is still an ASR button in my toolbar. Totally blank about how to link ASR to that button.


An informative installation/startup link will already be helpful!

Thanks - and sorry...
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: frankz on February 20, 2019, 05:45:26 PM
I reinstalled MB again, but cannot find how to install the ASR plugin again.
Absolutely not even an idea where to search.
Once I have it back I am sure I will re-teach myself again how to use my favorite features.
But how to begin?
From the add-on page, click the download link and download the ZIP. (Your post update shows you did this)
In MB: Edit->Edit Preferences...Plugins...Add Plugin (upper right) and find the ZIP you downloaded
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on February 22, 2019, 03:03:05 AM
Using MB 3.3.6987 wtih ATRT version released Feb 15 2019...

I'm finding that the width of the columns in 'preview' do not remain persistent. When I open ASR they're bunched together and I spread them apart, run a preset, close ASR, reopen it and the columns are bunched together again.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 23, 2019, 09:23:18 AM
@Frankz:

[/quote]From the add-on page, click the download link and download the ZIP. (Your post update shows you did this)
In MB: Edit->Edit Preferences...Plugins...Add Plugin (upper right) and find the ZIP you downloaded
[/quote]

Thanks, Frankz, I am on my way. Manage to install the .dll and even link it to my toolbar under ASR.
But... the presets box is totally empty.
Two questions:
1. How to fill it with the (perhaps updated) default preset list
2. In the past I configured a number of my old presets. I still have a folder 'presets old'. Can I add 'mine' to the default set - without deleting updated default presets?
Thanks!
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: WimYogya on February 24, 2019, 04:49:11 PM
Hello all,

I managed to copy/import a list of presets in my newly attached plugin.
But...

In the past I had added/created a limited number of my own presets.
I thought they were lost, but I searched my pc for ALL ASR-presets and copied them to my appdata MBplugin folder.
Now they appear in the presets list again.

But still not reached the finish.
Seems none of the presets can be activated.
After I select one, I can change a selected element (e.g. Title > Track) but the rest is greyed out.

Cannot find till now what I do wrong.
Any idea?


Thanks,
Wim
Title: Re: Additional Tagging and Reporting Tools
Post by: Tybot on March 09, 2019, 05:00:52 PM
I have a question regarding the backup/restore function. Does it include every tag field that's present in a FLAC file, including custom tags created by mp3tag or musicbee? I used it today to try to restore the value of the tag <lyrics> but it didn't do anything.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 23, 2019, 12:04:07 PM
sorry for being late. i'll try to answer all questions.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 23, 2019, 12:06:42 PM
@boroda
 I think I found a bug in the new version  :o

When you try to access a <Temp #> tag more than once, the regex is applied but all values from the source tag are copied over (see step 2)
(https://i.imgur.com/MxP3KE0.jpg)

all the values of Lyrics? have been appended to the tag:
(https://i.imgur.com/EGIMPKO.jpg)

If I change the output of step 2 to another tag:
(https://i.imgur.com/4FyEf01.jpg)

only the correct regex output is appended to the tag:
(https://i.imgur.com/Fy1aFjn.jpg)
just have tried to create a simple test preset and found no problems. so its not about reusing temp1 tag, its something else. try to check/experiment with your regexes.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 23, 2019, 12:09:26 PM
Using MB 3.3.6987 wtih ATRT version released Feb 15 2019...

I'm finding that the width of the columns in 'preview' do not remain persistent. When I open ASR they're bunched together and I spread them apart, run a preset, close ASR, reopen it and the columns are bunched together again.

Thanks.
ill revert coloring back (the reason for the change was that previous coloring didn't look good with some skins).

you are right, there is some bugs with remembering column widths.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 23, 2019, 12:13:34 PM
Hello all,

I managed to copy/import a list of presets in my newly attached plugin.
But...

In the past I had added/created a limited number of my own presets.
I thought they were lost, but I searched my pc for ALL ASR-presets and copied them to my appdata MBplugin folder.
Now they appear in the presets list again.

But still not reached the finish.
Seems none of the presets can be activated.
After I select one, I can change a selected element (e.g. Title > Track) but the rest is greyed out.

Cannot find till now what I do wrong.
Any idea?


Thanks,
Wim
don't understand. could you post a screenshot?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 23, 2019, 12:15:05 PM
I have a question regarding the backup/restore function. Does it include every tag field that's present in a FLAC file, including custom tags created by mp3tag or musicbee? I used it today to try to restore the value of the tag <lyrics> but it didn't do anything.
all tags, which are mapped to mb tags (including custom tags). but I indeed see a bug with lyrics tags (and maybe some other tags).
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on March 23, 2019, 01:30:26 PM
ill revert coloring back (the reason for the change was that previous coloring didn't look good with some skins).

you are right, there is some bugs with remembering column widths.
Thanks - looking forward to the changes.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on March 24, 2019, 06:06:46 AM
just have tried to create a simple test preset and found no problems. so its not about reusing temp1 tag, its something else. try to check/experiment with your regexes.
OK.  Will try a few different ideas.

Also, I noticed the Lyrics? psudeo-tag is read/write in MSR, but is 'read only' in ASR.
Could you make it writeable in ASR as well , please?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 26, 2019, 09:54:05 AM
backup/restore bugfixes:

https://www.mediafire.com/file/midj69aq1qagfv1/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on March 26, 2019, 11:06:17 AM
bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

and source:

http://www.mediafire.com/file/790wksi25fct52v/TagTools_2019-03-26.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on March 31, 2019, 05:41:50 AM
Thanks for fixing the Lyrics? tag  :)
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 04, 2019, 04:04:22 AM
I'm using the latest MB and the 3-27 update of this plugin. Trying to copy and paste tags from about 250 tracks (using "copy tags to clipboard" and "paste tags from clipboard", I'm getting this kind of error a lot (sometimes on copy, this one was on paste):

Code
MusicBee v3.3.7032.40028 (Win10.0), 3 Apr 2019 22:01:

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.Split(String[] separator, Int32 count, StringSplitOptions options)
   at MusicBeePlugin.PasteTagsFromClipboardCommand.pasteTagsFromClipboard()
   at MusicBeePlugin.PasteTagsFromClipboardCommand.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()

Maybe related, it also doesn't seem to be actually copying all the info. I'll see if I can get more info on that.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 04, 2019, 03:57:45 PM
suggest a corrupted artwork. i'll prepare a debug version.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 04, 2019, 04:26:51 PM
this version must display slightly more detailed message:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 04, 2019, 05:54:20 PM
Thanks, I'll see what i come up with.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 05, 2019, 03:45:27 AM
Also, I noticed the Lyrics? psudeo-tag is read/write in MSR, but is 'read only' in ASR.
Could you make it writeable in ASR as well , please?
Thanks for fixing the Lyrics? tag  :)

Actually in either one, it says it's being written too but no data is actually saved.
Would this be a limitation within MB as it's a database-only pseudo tag?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2019, 09:07:00 AM
actually it doesnt work for msr and 'copy tag' either. maybe its recent change in mb api.

try to write 'lyrics' tag instead of 'lyrics?'.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2019, 03:55:12 PM
Just started testing the new version.

- MSR preset doesn't handle escape sequences for special characters properly. Also they don't work via ASR command.

- Why is the target tag of the MSR preset "Temp 1" rather than "Tag 2"? It works via MSR command but not via ASR command, so they can't be used for hotkeys.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 05, 2019, 04:16:20 PM
for 1: will check this, but could you give me some example?

for 2: msr preset is just a service template for msr command. unfortunately the way i've implemented asr doesnt allow to hide it in asr, but i'll write a comment in it that its a service preset. use msr command to create meaningful msr presets, then tick them for autoapplying and/or assign hotkeys to them in asr. its not very intuitive, but its so for historical reasons (msr has been created as asr extension after several years of asr existance).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2019, 04:21:39 PM
for 1: will check this, but could you give me some example?

Replace # and * with certain numbers with or without regex enabled.

for 2: msr preset is just a service template for msr command. unfortunately the way i've implemented asr doesnt allow to hide it in asr, but i'll write a comment in it that its a service preset. use msr command to create meaningful msr presets, then tick them for autoapplying and/or assign hotkeys to them in asr. its not very intuitive, but its so for historical reasons (msr has been created as asr extension after several years of asr existance).

Yes, I know. What I'm saying is the target tag needs to be changed to "Tag 2" for those msr preset to be used as an ASR hotkey command.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 05, 2019, 04:26:01 PM
The tag backup feature works up to about 100,000 tracks. If the library is larger than that, it doesn't work. Is it possible to support more tracks?
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 06, 2019, 05:21:46 AM
this version must display slightly more detailed message:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

I was doing smaller batches and everything went fine for a while. Then tried about 150 files and got an error on the copy command. But I keep getting a message that I can't copy the error. So here are screenshots:

https://imgur.com/a/ZTV3t6t


Update: I just had it happen with only 14 tracks. I think you're on to something with the artwork, because when I looked they had a 16MB artwork attached. Seems excessively large, lol. At the same time I don't know why even that size would overload my computer.
Title: Re: Additional Tagging and Reporting Tools
Post by: barlet on April 06, 2019, 07:15:44 PM
Recently, additional Tagging and Reporting Tools has been reporting an error in invocation when enabled in Preferences. I uninstalled the plugin and tried to download again, perhaps the latest version, from the plugin page, only to be faced with a Malicious Site, usually by ad.fly. Can anyone fix this please?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 06, 2019, 08:49:52 PM
Are you certain you've installed the plugin correctly? The dll goes in MusicBee\Plugins while the ARS Presets goes in MusicBee\AppData.

Where/when are you seeing the 'malicious site' warning? The plugin should be downloaded from MediaFire and I've never see a warning such as that. I just did it now and saw no warning.
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 06, 2019, 08:55:13 PM
@boroda-

Using 5.0.7025 I just had an instance of the columns not opening to size correctly in ASR preview. I closed ASR and opened it again and it was fine.
(http://i.imgur.com/Oe9c9avl.jpg) (https://i.imgur.com/Oe9c9av.jpg)

Title: Re: Additional Tagging and Reporting Tools
Post by: barlet on April 07, 2019, 12:28:55 PM
Are you certain you've installed the plugin correctly? The dll goes in MusicBee\Plugins while the ARS Presets goes in MusicBee\AppData.

Where/when are you seeing the 'malicious site' warning? The plugin should be downloaded from MediaFire and I've never see a warning such as that. I just did it now and saw no warning.
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

I just clicked on the appropriate entry in the plugins section and then on the mediafire link to download. This is the only plugin directing me to ad.fly.  I tried some others and they do not direct me to any other site.

Thanks for your help anyway.

Albert
Title: Re: Additional Tagging and Reporting Tools
Post by: psychoadept on April 07, 2019, 05:23:23 PM
I just clicked on the appropriate entry in the plugins section and then on the mediafire link to download. This is the only plugin directing me to ad.fly.  I tried some others and they do not direct me to any other site.

I've also had problem with that specific link sending me to a spammy page. The ones in this thread do not, not sure why the difference.

(I don't have access to see all the details, but on mouseover the download button shows something with "fainbory.com", which google shows a bunch of porn links for. O_O)


Update: it turns out the link on the wiki had the same problem. I've removed that one and pm'd boroda about the add-ons page.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 08, 2019, 03:24:03 PM
The tag backup feature works up to about 100,000 tracks. If the library is larger than that, it doesn't work. Is it possible to support more tracks?

I was just asking. If the support requires lots of efforts, feel free to disregard the request.

Another issue: Copy/paste selected tags command doesn't work for any file properties. And can you add <Path> & <Filename> too? Currently it only supports <URL> (though it's not working now), so the user has to use virtual tags for those.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 10, 2019, 05:59:54 PM
Recently, additional Tagging and Reporting Tools has been reporting an error in invocation when enabled in Preferences. I uninstalled the plugin and tried to download again, perhaps the latest version, from the plugin page, only to be faced with a Malicious Site, usually by ad.fly. Can anyone fix this please?
try to close mb, delete file <appdata>\mb_tagtools.settings.xml and start mb again.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 11, 2019, 05:24:59 AM
The tag backup feature works up to about 100,000 tracks. If the library is larger than that, it doesn't work. Is it possible to support more tracks?
what do you mean by "it doesn't work"? what does exactly happen? there is no artificial limit and i cant test it by myself because my library has only 16000 tracks. 
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 11, 2019, 01:01:22 PM
The tag backup feature works up to about 100,000 tracks. If the library is larger than that, it doesn't work. Is it possible to support more tracks?
what do you mean by "it doesn't work"? what does exactly happen? there is no artificial limit and i cant test it by myself because my library has only 16000 tracks.  

Actually it works. I just tried it which took several hours and it stopped at "99%" for a long time, and probably that's why I thought it's not working properly before, but if you keep waiting it eventually works. So never mind.

Copy/paste selected tags command doesn't work for any file properties. And can you add <Path> & <Filename> too? Currently it only supports <URL> (though it's not working now), so the user has to use virtual tags for those.

Regarding this, please add <Folder Name> too. Also it would be great if you can make those three fields (path, folder name, filename that all MB supports) available in other commands as well (copy tag, asr, etc.). I know I can easily construct those using virtual tags, but I'm really short of virtual tag slots.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 11, 2019, 07:56:26 PM
various bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 11, 2019, 07:59:08 PM
- MSR preset doesn't handle escape sequences for special characters properly. Also they don't work via ASR command.
i cant reproduce this. * is replaced by \X and # by \# for me.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 12, 2019, 01:35:25 PM
bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 12, 2019, 03:06:01 PM
Regarding this, please add <Folder Name> too. Also it would be great if you can make those three fields (path, folder name, filename that all MB supports) available in other commands as well (copy tag, asr, etc.). I know I can easily construct those using virtual tags, but I'm really short of virtual tag slots.

its done:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: Bizy on April 12, 2019, 03:10:45 PM
Hé Boroda,

Thanks (again) for the update.

I don't know if you've seen my response in 'Questions'.
Just to make sure. For feedback:

I noticed that everything works fine (selecting multiple tags and copy/paste them in 'compare tracks') unless I include Artwork.
In that case, it only pastes the Artwork and the tags that are positioned above it.

You might want to look into that (too) ;-)

b.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 12, 2019, 03:19:59 PM
thanks for feedback. i'll test this.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 12, 2019, 03:41:09 PM
very stupid mistake. this bug is fixed. download link is the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bizy on April 12, 2019, 03:52:31 PM
The word 'stupid' never crossed my mind.
Please, be kind to yourself ;-)

b.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 12:53:19 AM
Another issue: Copy/paste selected tags command doesn't work for any file properties. And can you add <Path> & <Filename> too? Currently it only supports <URL> (though it's not working now), so the user has to use virtual tags for those.
file properties are read-only. what do you mean by <URL> is not working? that its read-only? could you give me an example of what you are trying to do?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 01:32:49 AM
Regarding this, please add <Folder Name> too. Also it would be great if you can make those three fields (path, folder name, filename that all MB supports) available in other commands as well (copy tag, asr, etc.). I know I can easily construct those using virtual tags, but I'm really short of virtual tag slots.
its done

Thanks, but you added <filename> and <folder>. <folder> seems <path> that MB supports and still there's no <folder name>. Different field names could confuse users. Can you support the same three fields just as MB does?

So for a file E:\Music\Pop\abc.mp3

Path: E:\Music\Pop
Folder Name: Pop
Filename: abc.mp3

Another issue: Copy/paste selected tags command doesn't work for any file properties. And can you add <Path> & <Filename> too? Currently it only supports <URL> (though it's not working now), so the user has to use virtual tags for those.
file properties are read-only. what do you mean by <URL> is not working? that its read-only? could you give me an example of what you are trying to do?

Try selecting all file property tags using copy selected tags command and paste it to a text file. It copies nothing.
Also, tag sets don't remember any file property tags. Include some property tags to a set, and if you open the set next time, file property tags are all excluded. Looks like the command doesn't support copying file property tags at all.

Of course they are read-only. I'm using this to get information of tracks or to compare a large number of tracks by pasting it to a text file.
But is it not possible to write Album Gain and Track Gain tags to files?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 01:42:07 AM
for 'folder': i misunderstood you first. of couse it can be done.

for copying tags to clipboard: sounds like a bug. will check this.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 01:45:15 AM
Thanks!
For now I've been using MB's send to clipboard command for file properties. You might want to check that to compare the results.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 01:51:18 AM
also msr preset is now hidden in asr (i mean uploaded version).
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 01:56:40 AM
Something's wrong with tag name. <Tag 1> and <Temp 1> are all shown as <1> in Preset Editor.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 02:08:27 AM
also msr preset is now hidden in asr (i mean uploaded version).

msr presets are not hidden in asr with the latest version. And why are you trying to hide them?
It's very useful to quickly edit the custom text using asr command window. Also if they are hidden, they can't be auto-applied or hotkeyed.
BTW hotkey still doesn't work for msr presets. If I press the hotkey, nothing happens unlike other asr presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 02:25:20 AM
Regarding this, please add <Folder Name> too. Also it would be great if you can make those three fields (path, folder name, filename that all MB supports) available in other commands as well (copy tag, asr, etc.). I know I can easily construct those using virtual tags, but I'm really short of virtual tag slots.
its done

Thanks, but you added <filename> and <folder>. <folder> seems <path> that MB supports and still there's no <folder name>. Different field names could confuse users. Can you support the same three fields just as MB does?

So for a file E:\Music\Pop\abc.mp3

Path: E:\Music\Pop
Folder Name: Pop
Filename: abc.mp3

Another issue: Copy/paste selected tags command doesn't work for any file properties. And can you add <Path> & <Filename> too? Currently it only supports <URL> (though it's not working now), so the user has to use virtual tags for those.
file properties are read-only. what do you mean by <URL> is not working? that its read-only? could you give me an example of what you are trying to do?

Try selecting all file property tags using copy selected tags command and paste it to a text file. It copies nothing.
Also, tag sets don't remember any file property tags. Include some property tags to a set, and if you open the set next time, file property tags are all excluded. Looks like the command doesn't support copying file property tags at all.

Of course they are read-only. I'm using this to get information of tracks or to compare a large number of tracks by pasting it to a text file.
But is it not possible to write Album Gain and Track Gain tags to files?

all these seem to be fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 02:27:49 AM
also msr preset is now hidden in asr (i mean uploaded version).

msr presets are not hidden in asr with the latest version. And why are you trying to hide them?
It's very useful to quickly edit the custom text using asr command window. Also if they are hidden, they can't be auto-applied or hotkeyed.
BTW hotkey still doesn't work for msr presets. If I press the hotkey, nothing happens unlike other asr presets.
i mean msr template preset only, not custom msr presets. template preset must be hidden to user doesn't change it accidently.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 02:51:19 AM
Now I can copy file property tags and RG tags can be copied to files as well. Thanks!

This is not fixed yet:

Something's wrong with tag name. <Tag 1> and <Temp 1> are all shown as <1> in Preset Editor.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 03:34:43 AM
its fixed. suggest that have forgotten to 'import new' presets.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 13, 2019, 03:36:37 AM
msr hotkeys are fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 03:40:31 AM
After installing the new version, running asr command first time shows this error. Next time it works. Started from a few versions ago.

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.InitializeComponent()
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand..ctor(Plugin tagToolsPluginParam)
   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)

This is when you run msr command first:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.MultipleSearchReplaceCommand.InitializeComponent()
   at MusicBeePlugin.MultipleSearchReplaceCommand..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.multipleSearchReplaceEventHandler(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 April 13, 2019, 03:50:59 AM
<1> in preset editor bug persists with the new version. Delete/Import all doesn't make any differences.

(https://i.imgur.com/QhbKDjf.png)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 04:30:41 AM
msr hotkeys are fixed

Found a bug when running an msr custom preset through asr hotkey command.

Try this

*^(.)b(.)$/$1$2

for

abc

The result should be "ac" and msr works properly but asr outputs "abcc"
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 13, 2019, 01:40:30 PM
The carriage return issue seems to have been reintroduced with copy/paste selected tags command. But for some reason, notepad++ shows it as a BEL character rather than a carriage return. Can you take a look?

I'm still having the carriage return issue and have to keep removing it every time after using the paste selected tags command.

Let me explain what the issue is:

Select 5 tracks> run copy selected tags command for title> paste it to other tracks.
It works fine and the pasted tags have no carriage return in their tag values.

Now paste it to notepad++> copy those five lines> paste it to some tracks.
Now the first four tracks have carriage return character in their values.

Do you see the differences? My request is when pasting selected tags, if the tag has the carriage return character at the end of the value, then remove it when writing the tag.

The reason is I am frequently copying selected tags from notepad++ rather than other tracks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 18, 2019, 03:31:00 PM
<1> in preset editor bug persists with the new version. Delete/Import all doesn't make any differences.

(https://i.imgur.com/QhbKDjf.png)
its fixed.

msr hotkeys are fixed

Found a bug when running an msr custom preset through asr hotkey command.

Try this

*^(.)b(.)$/$1$2

for

abc

The result should be "ac" and msr works properly but asr outputs "abcc"
its fixed also.

The carriage return issue seems to have been reintroduced with copy/paste selected tags command. But for some reason, notepad++ shows it as a BEL character rather than a carriage return. Can you take a look?

I'm still having the carriage return issue and have to keep removing it every time after using the paste selected tags command.

Let me explain what the issue is:

Select 5 tracks> run copy selected tags command for title> paste it to other tracks.
It works fine and the pasted tags have no carriage return in their tag values.

Now paste it to notepad++> copy those five lines> paste it to some tracks.
Now the first four tracks have carriage return character in their values.

Do you see the differences? My request is when pasting selected tags, if the tag has the carriage return character at the end of the value, then remove it when writing the tag.

The reason is I am frequently copying selected tags from notepad++ rather than other tracks.
there is a bell char, because i change carriage returns to bell on copying to clipboard, then on pasting i remove cr's (if any) on pasting, then change bells to crs. its so to preserve crs in lyrics. for me its working fine.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 18, 2019, 03:32:26 PM
for null reference bug: sometimes i it also, but i cant reproduce it by will.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 18, 2019, 03:57:03 PM
Thanks! It seems all reported issues are addressed except the carriage return issue.

If you copy multiple lines from notepad++ and paste it to a tag of multiple files, it adds a carriage return at the end of each tag value.
For instance, if you copy the following from notepad++ and paste it to title tag of three files, the first two files get a carriage return at the end of title tag.

Song 1 Title
Song 2 Title
Song 3 Title
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 18, 2019, 04:10:59 PM
How about always removing a carriage return at the end of value when pasting? Then it will work for lyrics tag as well.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 18, 2019, 04:27:08 PM
try this version:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 18, 2019, 04:31:24 PM
No differences from the previous version as it keeps adding a carriage return.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 18, 2019, 04:47:37 PM
this one?

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 18, 2019, 04:56:59 PM
Great! It no longer adds it when pasting. Thanks!

BTW copying lyrics field (using copy/paste selected tags command) doesn't seem to work. It copies nothing. Does it work for you?
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 18, 2019, 11:07:28 PM
yes, its working fine here.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2019, 06:21:19 AM
Does it copy from MB's database rather than from the file?
I tried with a file in the library, then it copies lyrics. But for a file not imported to the library it copies nothing.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 19, 2019, 06:53:08 AM
Does it copy from MB's database rather than from the file?
I tried with a file in the library, then it copies lyrics. But for a file not imported to the library it copies nothing.
boroda recently made some changes to the <Lyrics?> tag for me. These also weren't successful.
Could there be some confusion regarding the <Lyrics> tag (embedded or in an external .txt/ .lrc file) and the <Lyrics?> tag in the database (really only a flag to show if tracks are marked as no lyrics, unsynched lyrics or synched lyrics)?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2019, 08:11:07 AM
boroda recently made some changes to the <Lyrics?> tag for me. These also weren't successful.

Just tested with couple of albums copying <Lyrics?> tag and it's working fine for me. What's your problem exactly?
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 19, 2019, 08:24:26 AM
boroda tried to make <Lyrics?> writable in ASR and MSR.
It didn't work.
Lyrics? is now no longer selectable for writing in either panel.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2019, 08:44:27 AM
Was it ever possible to write something on <Lyrics?> tag?
I thought it's a read-only tag and "mark having no lyrics" can be enabled only via tag editor or track info panel.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on April 19, 2019, 08:48:47 AM
It was writable in MSR, when tried to extend to ASR it wouldn't work in either.

boroda thought that Steven may have made a change to the API
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2019, 12:04:00 PM
Does it copy from MB's database rather than from the file?
I tried with a file in the library, then it copies lyrics. But for a file not imported to the library it copies nothing.
what do you mean by "file not imported to the library"? file in the inbox? or file, which is in a playlist only, but not in mb database?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2019, 01:40:06 PM
A file not belonging to any of those.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2019, 03:09:30 PM
i.e. you are coping lyrics to clipboard in another program? 'paste tags from clipboard' will expect tag set in clipboard, which was last time used by 'copy tags clipboard'.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2019, 03:14:47 PM
I don't think that's an issue here. If I copy lyrics from a file in the library, it sends it to the clipboard. But for a file not belonging to the library, it sends nothing to the clipboard.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2019, 03:36:24 PM
but how do you select file in mb (to copy lyrics to clipboard), if its not the library?
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 19, 2019, 03:40:42 PM
Using computer folder in left navigator.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2019, 03:55:42 PM
Ahhh...
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 19, 2019, 04:14:28 PM
you are right. i guess its a bug in mb api. Steven, have you read several last posts?
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 20, 2019, 04:16:21 AM
@boroda...

Using the latest version of the plugin (posted in Reply #2058) nothing is persistent. Not the location of the window. Not the column sizes. Not the ticks for auto-apply presets. Not the tags selected for any ASR function.

Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on April 20, 2019, 05:25:18 AM
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 20, 2019, 01:42:21 PM
Thanks boroda - all is well expect for the column width. It still does not remain persistent.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on April 20, 2019, 02:27:56 PM
Thanks boroda - all is well expect for the column width. It still does not remain persistent.

I've had this issue for some months now too, but haven't reported it as I don't use many features other than the Soundcheck preset.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on April 20, 2019, 02:56:36 PM
I've had this issue for some months now too, but haven't reported it as I don't use many features other than the Soundcheck preset.
Typically when boroda issues a 'testing' version it doesn't have the persistent windows, etc enabled. When he's satisfied with the test results, he 're-releases' a version that has persistence. Perhaps that's the case this time, but I didn't notice that he was 'testing.' Hence my call-out.
Title: Re: Additional Tagging and Reporting Tools
Post by: Pingaware on April 22, 2019, 12:32:30 PM
I've had this issue for some months now too, but haven't reported it as I don't use many features other than the Soundcheck preset.
Typically when boroda issues a 'testing' version it doesn't have the persistent windows, etc enabled. When he's satisfied with the test results, he 're-releases' a version that has persistence. Perhaps that's the case this time, but I didn't notice that he was 'testing.' Hence my call-out.

Didn't know that but thought I was on a more stable version as (I think) I was on a version that was for some time the most recent update. It's really not an issue either way. Just good info to know.
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on April 23, 2019, 07:09:53 AM
Another bug when running an msr custom preset via asr command.
When both tag 1 & tag 2 are "Lyrics", it doesn't work via asr command with any template. It doesn't change anything while msr command works just fine.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 06, 2019, 01:28:07 AM
I created an ASR preset to change the case of prepositions found in the middle of a title (The, To, From, In, Of.) Many a year ago I started using the built-in change case so that the first letter of all words in the title were changed to an upper case letter. Now I regret that decision and want to change the first letter of those words to lower case. Unfortunately there is only room for five words in the template. Is there any way to get ten (or more) words in the template? Or is there a more efficient way to do this? A work-around would be to create a second (or third) preset, but that would require me running it two (or three) times on about 30k tracks.
(http://i.imgur.com/Tl0w5CYl.jpg) (https://i.imgur.com/Tl0w5CY.jpg)

Also, a while back the preview of an ASR would show the 'new tag value' in a blue color, which makes it easier to spot what is going to change. It was removed for a short while but then boroda brought it back. However I've now noticed that not all changes are shown in blue. Here are 9 tracks about to be changed, but only 1 is in blue.
(http://i.imgur.com/uHMyl3Dl.jpg) (https://i.imgur.com/uHMyl3D.jpg)
Title: Re: Additional Tagging and Reporting Tools
Post by: redwing on May 06, 2019, 01:40:04 AM
You could use Multiple search & replace command instead which doesn't have such restrictions.
But for that case, why not use "Change case" command? Just list all words in the box.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on May 06, 2019, 02:46:08 AM
You could use Multiple search & replace command instead which doesn't have such restrictions.
But for that case, why not use "Change case" command? Just list all words in the box.
Thank you.

I'm playing with Multiple Search & Replace rather than Change Case because I don't seem to be able to surround the word with space characters due to the space character being the separator.  Using " The " prevents the first word in the title from changing to lower case. MSR does appear do what I want. Added benefit is that I didn't realize when I saved it, it would create an ASR Preset. Good ol' boroda - he thought of everything.
Title: Additional Tagging Tools -> Paste Tags from Clipboard
Post by: ryanemerson on July 15, 2019, 11:06:00 PM
Hello. New MB user. Hoping to get some help

Looking to paste tags I created in excel back into MB library

One of 2 error messages always occurs when use "Paste Tags from Clipboard" either pasting copied columns from excel, or when pasting from a .txt file. My library has 22,583 tracks, and I am selecting all tracks in MB, then "Paste Tags from Clipboard"


1) From .txt. file: The number of tags in clipboard (1) does not correspond to the number of selected tracks (63)

2) From excel spreadsheet: The number of tags in clipboard (22,584) does not correspond to the number of selected tracks (22,583)

I am not pasting headers from Excel.

When I add in an extra "fake" track in MB when pasting from Excel, I am back to error message #1

I have tried smaller chunks of the library, receiving the same results

Where I am going wrong?

Any help/advice I would be most grateful.

Thank you!

Title: Re: Additional Tagging and Reporting Tools
Post by: Jirachi on July 25, 2019, 10:37:27 PM
Hi everybody,

Is there any way to make MusicBee work like in iTunes, in that whenever the play count is changed, it doesn't keep having to modify the file? I have the Additonal Tagging Tools plug-in, which is supposed to update the playcount, but it never syncs up. It just adds the playcount under Tags (2) and modifies the file every single time I listen to it. And is there any simple way to sync play count between iTunes and MusicBee, besides converting the library to an iTunes one and keep importing it? Hope that makes sense.. Thanks!
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on July 26, 2019, 06:33:31 AM
Thanks boroda - all is well expect for the column width. It still does not remain persistent.
working fine here. but column widths are remembered only when you click 'proceed' button. of course click 'save & close' button after that.
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on July 26, 2019, 11:41:05 AM
working fine here. but column widths are remembered only when you click 'proceed' button. of course click 'save & close' button after that.
I'm pretty sure I've done that, but will certainly do it again today. Thanks.
Title: Re: Additional Tagging and Reporting Tools
Post by: Zafar Iqbal on August 01, 2019, 04:45:57 AM
How is auto rating supposed to work? It writes to the costum fields, but I can't get it to rate.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 02, 2019, 06:21:08 AM
How is auto rating supposed to work? It writes to the costum fields, but I can't get it to rate.
select all files in your library (ctrl+a), define what percentage of your library must have desired rating, setup tag to store autorating (it may be 'rating' tag or custom tag) , then click 'set ratings of selected files' button.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 02, 2019, 03:45:16 PM
Another bug when running an msr custom preset via asr command.
When both tag 1 & tag 2 are "Lyrics", it doesn't work via asr command with any template. It doesn't change anything while msr command works just fine.
working fine for me:

(https://www.mediafire.com/convkey/63ea/gl8e39fvhy4ip8d6g.jpg) (http://www.mediafire.com/view/?gl8e39fvhy4ip8d)
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 04, 2019, 04:17:11 AM
Thanks boroda - all is well expect for the column width. It still does not remain persistent.
working fine here. but column widths are remembered only when you click 'proceed' button. of course click 'save & close' button after that.
now you don't need to click 'apply' button to remember column widths:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: phred on August 04, 2019, 04:24:48 AM
now you don't need to click 'apply' button to remember column widths:
Thanks -VERY- much.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 07, 2019, 05:17:17 PM
a few bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 07, 2019, 08:14:12 PM
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

i've added to all plugin commands new pseudo-tag: <File path>. it's path to file without filename itself and without ending backslash.
Title: Re: Additional Tagging and Reporting Tools
Post by: Zafar Iqbal on August 07, 2019, 09:26:01 PM
How is auto rating supposed to work? It writes to the costum fields, but I can't get it to rate.
select all files in your library (ctrl+a), define what percentage of your library must have desired rating, setup tag to store autorating (it may be 'rating' tag or custom tag) , then click 'set ratings of selected files' button.

It's working now. Thanks!

The problem was auto ratings being set to be stored in Custom9. I must have changed it early on and not realizing rating wouldn't show up normally.
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 08, 2019, 12:09:17 PM
i've added new virtual tag function $Sqrt(number). it returns square root of input parameter. may be useful for gathering some library statics (in conjunction with ALR functions).

download link is the same.
Title: Re: Additional Tagging and Reporting Tools
Post by: Bee-liever on August 08, 2019, 12:17:09 PM
may be useful for gathering some library statics (in conjunction with ALR functions).

I know I'll find it useful  :)
Thank you boroda
Title: Re: Additional Tagging and Reporting Tools
Post by: boroda on August 15, 2019, 01:31:31 AM
minor bugfixes and improvements:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 15, 2019, 02:52:48 PM
some bugfixes. also, support for skin colors is enhanced:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 15, 2019, 10:33:18 PM
@boroda-

At this point I can't say with 100% certainty, but it appears the last two updates (today and yesterday) to ATRT is causing MB to lock up on my Windows 10 machine.

I've been using MB 3.3.7154 P with no issues since it was released. Today I patched to 3.3.7165 P and MB would launch as normal but within five minutes (often less) it would lock up. Totally unresponsive. Had to kill the process to exit. I had also updated ATRT to today's version, so I rolled that back to yesterday's. MB still locked up. I rolled MB back to 7154 and still got lock ups. I rolled ATRT back to the update issued August 3 2019 and MB hasn't locked up (so far) after 15 minutes of use. So right now, ATRT from Aug 3 seems to be playing nice with MB 3.3.54.

I took a chance and patched MB to 7165 and I haven't had any lock ups for about thirty minutes. So I'm fairly certain there's an issue with the last one or two updates to ATRT.

There is nothing in the error log.

Let me know if there's anything I can do to help you troubleshoot this. Or to disprove it's ATRT.

Also, while I have your attention, could you go back to having version numbers, or dates, as part of the filename for your releases instead of using "latest."? This would/should make it more clear for me (and others) to tell you which version they're using instead of saying, like I did, the version released today. My 'today' is more likely your 'tomorrow'. Or visa versa.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 16, 2019, 07:21:31 AM
i'll take a look at possible issues. have you any auto library report's presets? all recent changes have been connected to alr.

for plugin versions: open plugin settings, you'll see plugin version at left bottom corner of the settings panel.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 16, 2019, 11:51:41 AM
@phred, try this version:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 16, 2019, 01:05:16 PM
i'll take a look at possible issues. have you any auto library report's presets? all recent changes have been connected to alr.
No, I don't have any auto-library report presets.

Quote
for plugin versions: open plugin settings, you'll see plugin version at left bottom corner of the settings panel.
Ahhh --- good to know. Thanks for pointing that out.

@phred, try this version:
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
So far, so good. MB has been running with the updated version for about 15 minutes. I'll report back if there's a lock up later in the day, but as of right now, it looks like you squashed it.

Thanks for the quick work.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 16, 2019, 07:44:28 PM
It took a while, but MB is locking up again. This time it happened when I started playing a CD. After a number of times of killing the process followed by a relaunch and immediate freeze, I restored ATTR 5.1.7154, which was the version I was using successfully until today's update (5.2.7167.)

Relaunching MB and the CD, all is working well. At this point I can say utmost certainty, that something changed after 5.1.7154 that is causing this issue.

I'm content to keep running this slightly older version. Let me know if there's something I can do on my side as you try to find this pesky little bugger.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 18, 2019, 07:13:24 PM
some bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Nixander on September 08, 2019, 07:06:40 PM
//Edit: okay I solved it myself. I deactivated autobackup and restarted the computer. I guess the baseline file was being used by the autobackup. :)




Hey Boroda,
I just deleted 4000 genre-tags by accident. Luckily I made a tag backup before. But When I click on "open", after selcting the backup, nothing happens... Does it work in the background and needs a lot of time?

After a long wait I just got this error:


Quote
MusicBee v3.3.7016.32512 (Win10.0), 8 Sep 2019 22:42:

System.IO.IOException: Der Prozess kann nicht auf die Datei "D:\Dokumente\Backups\Musicbee Tag Backup\MusicBee - Baseline.bbl" zugreifen, da sie von einem anderen Prozess verwendet wird.
   bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei 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)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   bei MusicBeePlugin.BackupType.Load(String fileName, String backupFileExtension)
   bei MusicBeePlugin.BackupType.save(String fileName)
   bei MusicBeePlugin.BackupIndex.saveBackup(String backupName, String statusbarText, Boolean isAutocreatedParam)
   bei MusicBeePlugin.Plugin.regularAutobackup(Object state)
   bei System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)
   bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   bei System.Threading.TimerQueueTimer.CallCallback()
   bei System.Threading.TimerQueueTimer.Fire()
   bei System.Threading.TimerQueue.FireNextTimers()
   bei System.Threading.TimerQueue.AppDomainTimerCallback(Int32 id)
Title: Re: Additional Tagging & Reporting Tools
Post by: The Freezing Chicken on September 11, 2019, 05:33:58 PM
Hi Boroda. First of all, what a wonderful plugin. Very useful.

Anyway, I tried to use the $Random function and I noticed that it generates a lot of duplicate numbers, so I took the liberty to look at your source code and found how you implemented that.
Your code looks like this
Code
public string CustomFunc_Random(string max_number)
{
    return (new Random()).Next(int.Parse(max_number) - 1).ToString("D" + (int)Math.Log10(float.Parse(max_number) + 0.5));
}

The problem with this is that a Random instance probably works by generating a seed from the current system tick counts or something like that, so if you do a "new Random()" you end up restarting the sequence until the tick count changes.

What I suggest is to store the Random instance in a static field and calling Next on it, like this
Code
static readonly Random randomGen = new Random();



public string CustomFunc_Random(string max_number)
{
     return randomGen.Next(int.Parse(max_number) - 1).ToString("D" + (int)Math.Log10(float.Parse(max_number) + 0.5));
}
This way the seed gets generated only once and the sequence behaves randomly.

Also I'm not sure why you do "-1" on the max number, because that makes the generator generate numbers between 0 and max_number-1, so if I put "10" in the function it goes from 0 to 8. Not sure that's what you want but maybe there's a reason I don't know.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on September 16, 2019, 07:47:10 PM
Thanks for a fantastic plugin @boroda! I was looking for a preset that would move featured artist from artist to title but couldn't find one. Is this possible to create via the preset editor?
Cheers!
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on September 18, 2019, 11:56:47 AM
I'm probably blind, but how would I easily copy just a part of a tag to another tag? For example, in the <album> "Hôtel Costes, volume 8", I'd like to copy volume 8, or at least 8, to another tag.
Thanks in advance!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 20, 2019, 09:27:44 AM
Hi Boroda. First of all, what a wonderful plugin. Very useful.

Anyway, I tried to use the $Random function and I noticed that it generates a lot of duplicate numbers, so I took the liberty to look at your source code and found how you implemented that.
Your code looks like this
Code
public string CustomFunc_Random(string max_number)
{
    return (new Random()).Next(int.Parse(max_number) - 1).ToString("D" + (int)Math.Log10(float.Parse(max_number) + 0.5));
}

The problem with this is that a Random instance probably works by generating a seed from the current system tick counts or something like that, so if you do a "new Random()" you end up restarting the sequence until the tick count changes.

What I suggest is to store the Random instance in a static field and calling Next on it, like this
Code
static readonly Random randomGen = new Random();



public string CustomFunc_Random(string max_number)
{
     return randomGen.Next(int.Parse(max_number) - 1).ToString("D" + (int)Math.Log10(float.Parse(max_number) + 0.5));
}
This way the seed gets generated only once and the sequence behaves randomly.

Also I'm not sure why you do "-1" on the max number, because that makes the generator generate numbers between 0 and max_number-1, so if I put "10" in the function it goes from 0 to 8. Not sure that's what you want but maybe there's a reason I don't know.

you are quite right and i will rewrite random function.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 20, 2019, 09:38:22 AM
I'm probably blind, but how would I easily copy just a part of a tag to another tag? For example, in the <album> "Hôtel Costes, volume 8", I'd like to copy volume 8, or at least 8, to another tag.
Thanks in advance!
create own preset, search for:

Code
^(.*?),\s*(.*)$|^.*$

replace with:

$2

in step 1.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 20, 2019, 10:18:00 AM
new implementation is

Code
        public string CustomFunc_Random(string max_number)
        {
            return RandomGenerator.Next(int.Parse(max_number) + 1).ToString("D" + (int)Math.Round(Math.Log10(float.Parse(max_number) + 1)) + 0.5);
        }



http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 20, 2019, 04:28:07 PM
//Edit: okay I solved it myself. I deactivated autobackup and restarted the computer. I guess the baseline file was being used by the autobackup. :)




Hey Boroda,
I just deleted 4000 genre-tags by accident. Luckily I made a tag backup before. But When I click on "open", after selcting the backup, nothing happens... Does it work in the background and needs a lot of time?

After a long wait I just got this error:
...


i've overlooked this situation. this must be fixed now. download link is the same.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 26, 2019, 08:14:48 PM
minor bugfixes:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on September 27, 2019, 08:48:03 AM
Hi @boroda!

I had some problems with ASR freezing after/while applying the Remove month and day from release date-preset. According to the status bar, 100% of the files are read, but then nothing happens, and MB becomes unresponsive. Anyway, I thought I should re-install ATRT but when I uninstall it from the plugin menu in Edit I get this error msg:

Code
MusicBee v3.3.7199.32952D  (Win10.0), 27 Sep 2019 9:26:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.IOException: The directory is not empty.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean throwOnTopLevelDirectoryNotFound, WIN32_FIND_DATA& data)
   at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
   at MusicBeePlugin.Plugin.Uninstall()
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zNb5JX7ZJ08AFj0dTBw==.#=zXvQGTro=()

Do you have any idea as of how to move on? I could of course delete all files manually, but maybe this error msg gives some clue as to what's not working?

Very best
J
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 27, 2019, 01:13:33 PM
exception is fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

for asr i don't know why freezing is happened, but i'll to fix this if you can reliably reproduce it.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on September 27, 2019, 04:00:48 PM
exception is fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

for asr i don't know why freezing is happened, but i'll to fix this if you can reliably reproduce it.

Great boroda, thanks! Please let me know what I need to do to reproduce it. As it is now, I select an album (I have tried a couple of different, on 2 different hard drives), and select the Remove month...preset. On preview, everything looks fine, with the yyyy-mm-dd being exchanged to yyyy. Then on apply, all files are listed appropriately, and buttons change to Stop/Save all/Hide, but I can't see that anything is happening. None of the files' switches from checkmark to the filled black square, and the ATRT window becomes unresponsive. I can see the status bar in MB and it says Advanced searching and replacing (reading):100%. Nothing happens for now 20 minutes and I have to end MB task in task manager. Note though that Windows Task Manager does not report MB as Not responding.

Please let me know if there's anything else I can provide. Nothing is noted in the MB error log.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 27, 2019, 04:21:59 PM
can you pm me one of music files, which can't be processed?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 30, 2019, 02:39:17 PM
@Johan_A_M, rename mb_tagtools.dll to something like mb_tagtools.dll.bak for backup purposes, then unzip this archive to "Plugins" folder and overwrite all files:

https://www.mediafire.com/file/ufh99qf34u441n2/mb_TagTools_ASR_debug.zip/file

run the preset in question for 1 test music file. you'll see a series of message boxes with numbers 1, 2, 3, etc. post last number you will see.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 01, 2019, 10:23:51 AM
run the preset in question for 1 test music file. you'll see a series of message boxes with numbers 1, 2, 3, etc. post last number you will see.

It's a 6.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 01, 2019, 10:49:29 AM
and for this version?

http://www.mediafire.com/file/ufh99qf34u441n2/mb_TagTools_ASR_debug.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 01, 2019, 06:46:48 PM
Bef
and for this version?

http://www.mediafire.com/file/ufh99qf34u441n2/mb_TagTools_ASR_debug.zip/file

Before doing this, can I just ask if this should be done in nthe plugin folder or the appdata folder? Haven't realized that there are two folders with the presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 01, 2019, 06:58:14 PM
<appdata>\asr presets
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 01, 2019, 07:02:45 PM
i suspect that almost any plugin commands will freeze for you (eg. copy tag, change case, etc.). if this is the case, then its worst situation because it means that something went wrong with your windows environment (especially with .net framework).
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 01, 2019, 07:23:04 PM
i suspect that almost any plugin commands will freeze for you (eg. copy tag, change case, etc.). if this is the case, then its worst situation because it means that something went wrong with your windows environment (especially with .net framework).

Still 6. Yes, you're right, it has frozen on other presets too. I think I've tried 3-4 different ones and had the same problem. Could I maybe simply reinstall .net? My version seems to be 4.7.2 which apparently is not the latest.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 01, 2019, 07:40:23 PM
you have used some other version of plugin. now the displayed number can't be greater than 3.

for reinstalling .net, i would suggest upgrading to latest .net version, just to reinstall current .net version during upgrade.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 01, 2019, 07:44:26 PM
Ah yes, I forgot to .bak ... Will install latest .net and try again afterward.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 01, 2019, 09:54:27 PM
Could it really be that I get none of the message boxes? Most probably I'm doinng something wrong, but just wanted to check. Also, updated to latest .net but to no luck.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 02, 2019, 12:33:10 AM
delete plugins\mb_tagtools.dll, rename backed up mb_tagtools.dll.bak to original mb_tagtools.dll name. or (if you deleted original file) redownload non-debug version from here:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

unzip mb_tagtools.dll to 'plugins' folder and overwrite existing file.
Title: Re: Additional Tagging & Reporting Tools
Post by: Arkada on October 02, 2019, 04:46:33 AM
I downloaded the latest build but for some reason it will not initialize correctly, and I get these pop ups (https://imgur.com/a/ilWZWFx). Any ideas? It installed correctly on my other machine.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 02, 2019, 07:45:33 AM
1st exception can be easily fixed: close mb, then delete <appdata>\mb_tagtools.settings.xml file.

second error means that you have 2 (maybe custom or virtual, but maybe generic) tags with the tag names. plugin won't work in this situation. go to edit> prefs> tags(2) and click 'configure fields' button. find 2 tags with the same name and rename 1 of them.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 02, 2019, 08:04:28 AM
delete plugins\mb_tagtools.dll, rename backed up mb_tagtools.dll.bak to original mb_tagtools.dll name. or (if you deleted original file) redownload non-debug version from here:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

unzip mb_tagtools.dll to 'plugins' folder and overwrite existing file.

Hmm, strange, that is precisely what I'm doing. Still, no numbered msg boxes with that new debug version.
Title: Re: Additional Tagging & Reporting Tools
Post by: Arkada on October 02, 2019, 08:08:54 AM
1st exception can be easily fixed: close mb, then delete <appdata>\mb_tagtools.settings.xml file.

second error means that you have 2 (maybe custom or virtual, but maybe generic) tags with the tag names. plugin won't work in this situation. go to edit> prefs> tags(2) and click 'configure fields' button. find 2 tags with the same name and rename 1 of them.

Found and deleted the xml file, but can't find duplicates in the configuations menu. here is a snippet from the error log though

Adding Artist (displayed) / -1
Adding Artist / -2
Adding Artwork / Artwork
Adding BPM / BeatsPerMin
Adding Composer (displayed) / -3
Adding Composer / -4

I take it the negative numbers shouldn't be there?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 02, 2019, 09:18:24 AM
yes, negative values are normal. post here full log, which is mentioned in error message. there is must be at least 1 entry saying "Can't add...".
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 02, 2019, 09:22:35 AM
delete plugins\mb_tagtools.dll, rename backed up mb_tagtools.dll.bak to original mb_tagtools.dll name. or (if you deleted original file) redownload non-debug version from here:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

unzip mb_tagtools.dll to 'plugins' folder and overwrite existing file.

Hmm, strange, that is precisely what I'm doing. Still, no numbered msg boxes with that new debug version.

excuse me, hasn't been sleeping for 2 days. here is the right one:

http://www.mediafire.com/file/ufh99qf34u441n2/mb_TagTools_ASR_debug.zip/file

archive and .dll names are the same as the 1st time, but its different debug version.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on October 02, 2019, 11:45:22 AM
delete plugins\mb_tagtools.dll, rename backed up mb_tagtools.dll.bak to original mb_tagtools.dll name. or (if you deleted original file) redownload non-debug version from here:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

unzip mb_tagtools.dll to 'plugins' folder and overwrite existing file.

Hmm, strange, that is precisely what I'm doing. Still, no numbered msg boxes with that new debug version.


excuse me, hasn't been sleeping for 2 days. here is the right one:

http://www.mediafire.com/file/ufh99qf34u441n2/mb_TagTools_ASR_debug.zip/file

archive and .dll names are the same as the 1st time, but its different debug version.

Sorry but no matter what I do, I don't get the numbered boxes, only the freeze. Anyway, you should go to sleep!!  :)  :o
Title: Re: Additional Tagging & Reporting Tools
Post by: Arkada on October 02, 2019, 02:53:12 PM
yes, negative values are normal. post here full log, which is mentioned in error message. there is must be at least 1 entry saying "Can't add...".

Yeah, virtual26 - virtual32, which aren't visible in the config menu, and don't seem to be present at all in the machine I'm having trouble with. The machine that works has those virtual tags though

Edit: I fixed it. Despite having check for updates checked, I was two versions behind. I've since updated it and the plugin works fine. Thank you for the support!
Title: Need Instructions for "Additional Tagging & Reporting Tools" plugins
Post by: Shepherd Jim on October 11, 2019, 04:27:23 PM
Hello All:  I have downloaded and installed/enabled the plugin "Additional Tagging & Reporting Tools". I find a lot of information (it comes with a "Read Me") about what the plugin can do. But, maybe it's me. I cannot figure out how to accomplish what I want to do -- I'm about 98% sure the plugin IS capable of the task.

My immediate problem: I have the Beatles' Abbey Road in MusciBee as downloaded MP3's, I have extensively modified the tracks' tags/metatdata. I have now ripped the Abbey Road CD into my Inbox as flac's. I am going to import the "flac album" into my Library and will retain the MP3 album. I want to copy the tags from the MP3 files to the incoming flac's.

How do I find instructions on how to use the plugin?

Thanks for all comments and assistance!
Jim in Maine
Title: Re: Additional Tagging & Reporting Tools
Post by: psychoadept on October 11, 2019, 05:15:28 PM
If you need help with a plugin, you should post in the plugin's thread. I merged your post for you.

You're looking for the copy tags and paste tags command, which are easiest to use if you have the plugin configured to show up in the context menu. If not, it's in the Tools menu somewhere.

Although in this case you can get it done almost as easily with MusicBee's built in copy tags command (probably the more complete version), configured to a hot key.

Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 12, 2019, 08:18:56 AM
just make sure that mp3 tracks and flac tracks of the album are sorted the same way, because 'paste tags' command wont search for appropriate track, it will use appropriate track sequence number in current view.
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on October 24, 2019, 10:11:36 PM
Hello

I am trying to get Episode date into my tags before the title on my podcasts so they will be sorted correctly on my Garmin watch.

"Episode date" as shown under podcasts is not available (why not?) so I want to use Date (which turns out to be added date and time: "24-10-2019 13:35").

So for the match of only the date part I have put in ^.{10} in the part that should read the date. I have kept the $1 that was in the Replace with field - my preset is based on "Combine tags '<Tag 1>', '<Tag 2>' placing between them <Custom text 1> and write result in '<Tag 3>'."

However when I preview the result I get:
$1 13:35 <content of the title field>

What am I doing wrong?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 25, 2019, 05:49:57 AM
try to search for: ^(.{10}).*
Title: Re: Additional Tagging & Reporting Tools
Post by: PWN3D_ on October 28, 2019, 11:08:14 PM
Hello,

I decided to update my version of this plugin,from 4.xxx  (I don't remember honestly) version to the latest one.

I have a problem with musicbee getting slower than before and not responding program when I update tags normaly (without the use of the plugin)... Like updating the title of an album result in musicbee not responding for few seconds.

I also noticed that when I update tags from an album, as soon I as press apply, I can see all the tracks getting remove one by one, then replace with the updated tags and I guess this is what causing slow down.

If I dissable the plugin, everything works as intended, and this problem never happened with my previous version so I don't know what to do.
Title: Re: Additional Tagging & Reporting Tools
Post by: PWN3D_ on October 28, 2019, 11:48:34 PM
Well some thing was wrong here:

Musicbee was till showing the previous version in the plugins windows,there were some files from the previous version in the directory "users\<USERNAME>\AppData\Roaming\MusicBee\Plugins" that I had to delete.

At least that's out of the way...

But it still slow down Musicbee as a whole for few seconds after I press apply, it looks like the plugin is doing something  where it's not supose to be active before Musicbee proceed to tagging the files.
Title: Re: Additional Tagging & Reporting Tools
Post by: PWN3D_ on November 01, 2019, 10:17:49 PM
While I'm at it, here is some little bugs I encountered too:

When I change a cover from an album, the cover of that album on the primary panel doesn't change, I need to go to edit and save change again for it to update.

(https://i.imgur.com/uTo3PM3.jpg)

Here I just change the album cover to a white one.

Also the "use skin colors" work well, but with my skin, some words stays in black and are hard to read, with no way to twek this:

(https://i.imgur.com/KJnufvk.jpg)

(https://i.imgur.com/atSL4sm.jpg)

I use a stock skin (Dark : Duophonic)

Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2019, 11:31:49 AM
recently i've had several complaints about ui freezing when using the latest plugin version. could somebody confirm that this (older) version is still stable?

http://www.mediafire.com/file/7m62hq58ekph12k/mb_TagTools_stable.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 12, 2019, 12:28:16 PM
I'm finding anything from the 5.2.0.0 version gives me problems

Always aborts my AutoLibrary report at 88% with this error.
Code
12/11/2019 11:02:48 PM - 10.0.18362.0 - 3.3.7251.37421P - System.NullReferenceException: Object reference not set to an instance of an object.
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zhW5rhVLmgA5t(Int32 #=zlGZMpsA=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zvesHNF197Ki_(TagCode #=zpXMe84c=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zThGs_SKDXjKl(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, Int32 #=zzn0Oaqw=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zuCWZmkrNFqCNSvZbsA==(String #=zesgHATI=, Int32 #=zzn0Oaqw=)
   at MusicBeePlugin.Plugin.GetFileTag(String sourceFileUrl, MetaDataType tagId, Boolean autoAlbumArtist, Boolean normalizeTrackRatingTo0_100Range)
   at MusicBeePlugin.AutoLibraryReportsCommand.previewTrackList(Boolean interactive)
   at MusicBeePlugin.AutoLibraryReportsCommand.autoCalculate()
   at #=z78OeXVV6zcbJKhXa4Q==.#=z_OvZgZCh_RA0(Object #=zxJOcuTQ=)

currently still using a Version 5.1.0.0 from 8/08/2019 8:58 PM as it's the last one that was able to complete the report
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2019, 01:30:50 PM
it's 5.1 with some tiny improvements/bugfixes (new 5.2):

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 13, 2019, 12:21:07 AM
Still kills MB at 88% of report

Code
13/11/2019 11:15:54 AM - 10.0.18362.0 - 3.3.7251.37421P - System.NullReferenceException: Object reference not set to an instance of an object.
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zhW5rhVLmgA5t(Int32 #=zlGZMpsA=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zvesHNF197Ki_(TagCode #=zpXMe84c=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zThGs_SKDXjKl(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, Int32 #=zzn0Oaqw=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zuCWZmkrNFqCNSvZbsA==(String #=zesgHATI=, Int32 #=zzn0Oaqw=)
   at MusicBeePlugin.Plugin.GetFileTag(String sourceFileUrl, MetaDataType tagId, Boolean autoAlbumArtist, Boolean normalizeTrackRatingTo0_100Range)
   at MusicBeePlugin.AutoLibraryReportsCommand.previewTrackList(Boolean interactive)
   at MusicBeePlugin.AutoLibraryReportsCommand.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 & Reporting Tools
Post by: phred on November 13, 2019, 02:41:58 AM
In addition to what Bee-liever stated, 5.2.7214 is causing other problems also.

When I tried to use an ASR preset, it hung before changing anything.
When I tried to add lyrics to some tracks (using Lyrics Reloaded plugin) MB hung after the first track. I disabled AT&RT and after a MB restart I was able to get lyrics.

After the restart I noticed an album I moved from the Inbox to the Library was missing. I searched for it (File > Add files to library) and was able to recover them.

I rolled back AT&RT plugin to 5.2.7167 which was working yesterday and got the same results. Again I had to disable the plugin in order to get MB to work again without hanging.

Everything seems to be working as expected when I rolled back even further to 5.0.7049.

There is nothing in the Error Log.

The built in Search and Replace tool works without any issues.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 13, 2019, 01:19:13 PM
@Bee-liever, could you try this version?

https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file

post error message here.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 13, 2019, 07:47:34 PM
@Bee-liever, could you try this version?
https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
@boroda- I know this update was directed to Bee-liever's issues, but I figured I'd try it for mine. Even worse lockup than with 5.2.7214. MB launched and froze. Didn't have the opportunity to click on anything. Back to 5.0.7046 and working well.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 13, 2019, 09:22:44 PM
Version 5.2.7214 error log
Code
14/11/2019 8:15:03 AM - 10.0.18362.0 - 3.3.7251.37421P - System.NullReferenceException: Object reference not set to an instance of an object.
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zhW5rhVLmgA5t(Int32 #=zlGZMpsA=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zvesHNF197Ki_(TagCode #=zpXMe84c=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zThGs_SKDXjKl(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, Int32 #=zzn0Oaqw=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zuCWZmkrNFqCNSvZbsA==(String #=zesgHATI=, Int32 #=zzn0Oaqw=)
   at MusicBeePlugin.Plugin.GetFileTag(String sourceFileUrl, MetaDataType tagId, Boolean autoAlbumArtist, Boolean normalizeTrackRatingTo0_100Range)
   at MusicBeePlugin.AutoLibraryReportsCommand.previewTrackList(Boolean interactive)
   at MusicBeePlugin.AutoLibraryReportsCommand.autoCalculate()
   at #=z78OeXVV6zcbJKhXa4Q==.#=z_OvZgZCh_RA0(Object #=zxJOcuTQ=)

Version 5.1.7159 is the one I'm still using
Title: Re: Additional Tagging & Reporting Tools
Post by: Steven on November 13, 2019, 09:41:33 PM
The musicbee side of this error relates to a null value being returned by the custom function. I guess MB should convert the null to a blank value but its too late now for older MB versions, so really needs to be addressed by the custom function
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 14, 2019, 02:43:12 AM
@Bee-liever, what about this version?

https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file

@phred
Quote
When I tried to use an ASR preset, it hung before changing anything.
i can reproduce this, but only right after mb start. if i wait for several seconds then all is fine.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 14, 2019, 02:49:41 AM
@phred
Quote
When I tried to use an ASR preset, it hung before changing anything.
i can reproduce this, but only right after mb start. if i wait for several seconds then all is fine.
Okay, I'll try with 5.2.7167 tomorrow. Unless you think I should try the version you just posted for Bee-liever. Unless that's a debug.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 14, 2019, 02:54:54 AM
I had a little time so I installed 5.2.7167, launched MB, waited one minute and MB was hung. Totally unresponsive. Had to use task manager to kill it. Back to 7154 and it works with no delay.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 14, 2019, 03:01:00 AM
try with latest posted version (5.2.7214).
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 14, 2019, 04:18:59 AM
Version: 5.2.7214

Stops at 87% of second ALR preset.
Error Log:
Code
MusicBee v3.3.7251.37421P  (Win10.0), 14 Nov 2019 15:14:

System.NullReferenceException: Object reference not set to an instance of an object.
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zhW5rhVLmgA5t(Int32 #=zlGZMpsA=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zvesHNF197Ki_(TagCode #=zpXMe84c=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zThGs_SKDXjKl(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, Int32 #=zzn0Oaqw=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zuCWZmkrNFqCNSvZbsA==(String #=zesgHATI=, Int32 #=zzn0Oaqw=)
   at MusicBeePlugin.Plugin.GetFileTag(String sourceFileUrl, MetaDataType tagId, Boolean autoAlbumArtist, Boolean normalizeTrackRatingTo0_100Range)
   at MusicBeePlugin.AutoLibraryReportsCommand.previewTrackList(Boolean interactive)
   at MusicBeePlugin.AutoLibraryReportsCommand.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 & Reporting Tools
Post by: boroda on November 14, 2019, 04:48:37 AM
do you see any pop-up window with this version?

https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 14, 2019, 05:05:50 AM
Only the MusicBee Error window.
MB closes when you click 'OK'
(http://i.imgur.com/rzVKRmt.jpg) (https://imgur.com/rzVKRmt)


Think the error log is exactly the same as before:
Code
14/11/2019 3:57:14 PM - 10.0.18362.0 - 3.3.7251.37421P - System.NullReferenceException: Object reference not set to an instance of an object.
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=z7R5fQlEWA_zekNPRaAFassm4KT6Y.#=zBvjBMt1tQgDq(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zsuw89B8ux0wjALoQ8679GTVJvpgI.#=zM0iWbZHZOpjh(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, #=zb4zx58KH1jMbCbsRe1KWcezvMuc0[] #=zbAKnYPE=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=, StringBuilder #=zKsoWZAs=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zhW5rhVLmgA5t(Int32 #=zlGZMpsA=, #=zT_UiO12$HceYzJV4w2wndYU= #=zUt3Af3Y=)
   at #=zfPN9N9ucNejpFsmGK7Yoz5A=.#=zvesHNF197Ki_(TagCode #=zpXMe84c=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zThGs_SKDXjKl(#=zfPN9N9ucNejpFsmGK7Yoz5A= #=zh$Cto0o=, Int32 #=zzn0Oaqw=)
   at #=z78OeXVV6zcbJKhXa4Q==.#=zuCWZmkrNFqCNSvZbsA==(String #=zesgHATI=, Int32 #=zzn0Oaqw=)
   at MusicBeePlugin.Plugin.GetFileTag(String sourceFileUrl, MetaDataType tagId, Boolean autoAlbumArtist, Boolean normalizeTrackRatingTo0_100Range)
   at MusicBeePlugin.AutoLibraryReportsCommand.previewTrackList(Boolean interactive)
   at MusicBeePlugin.AutoLibraryReportsCommand.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 & Reporting Tools
Post by: PWN3D_ on November 14, 2019, 02:25:30 PM
Just tested version in post #2161 and did a few edits on some albums, it seems to works better for me, no more UI freezes for now. Need more testing.

Edit:Mmmh, still some freezes but they last smaller than before. The Albumart not updating in main window is still there but I guess this is minor for now.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 14, 2019, 06:19:49 PM
@Bee-liever, try any not working plugin version with mb 3.3 latest patch:

https://getmusicbee.com/patches/MusicBee33_Patched.zip
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 14, 2019, 06:49:45 PM
MB 3.3.7257 P and TagTools 5.2.7214 work great!

Sorry if I wasted your time, I didn't notice that Steven had posted a newer patch than the one I was using. :-[
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 14, 2019, 06:56:48 PM
MB 3.3.7257 P and TagTools 5.2.7214 work great!
Just tried this combination and it locked up. Killed it, restarted, waited one minute, hard freeze. Killed it, restarted, locked up within five seconds.

It seems that 5.1.7154 is the last version that works for me without locking up MB. Anything more recent than that presents a hard freeze.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 14, 2019, 07:15:49 PM
phred, i'll take a more close look at your issue tomorrow.

It seems that 5.1.7154 is the last version that works for me without locking up MB. Anything more recent than that presents a hard freeze.
no, its special mb patch to solve issues when using the plugin. i don't think this patch was initially planned :)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 14, 2019, 07:19:10 PM
phred, i'll take a more close look at your issue tomorrow.
Great - thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 15, 2019, 01:00:54 PM
phred, do you have any alr presets? do you have asr presets ticked for auto-applying? what happens if you disable all plugins except for at&rt?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 15, 2019, 02:58:33 PM
phred, do you have any alr presets? do you have asr presets ticked for auto-applying? what happens if you disable all plugins except for at&rt?
Using AT&RT 5.2.7214 with MB 3.3.7257 P

I have no presets for library reports, nor have I used reports in quite some time.

I thought I had three or four ASR presets ticked, but only found one, which I disabled. Closed MB and restarted and MB froze.

I have disabled all plugins except AT&RT, shut down and restarted MB, performed a preset (change case) and ASR showed the changes, but never displayed 'close' or 'save' and only changed one of the left side boxes changed from a tick to a solid box and promptly froze. MB's status bar shows "Changing case: 100% (2 file(s)) read" when it hangs.

Please let me know what other information I can provide in order to help get this resolved.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: Tpyo on November 18, 2019, 07:28:50 PM
Newie here - 1st post

I'm here today searching for more Tagging Tools.

I'm finally moving my Playlist to a Smartphone, and I see lots of editing on the Desktop in my future. I tried a few other programs (am I suppose to say Apps now? - lol)

The final decisions to chose MB was
1) Android path too
2) Tagging Tools with a memory of existing Tags


This program appears a growth stage, seeing lots of small errors popping up

? - should I wait?

thanks
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 19, 2019, 06:18:04 AM
what errors do you mean? post a screenshot.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 19, 2019, 05:42:51 PM
I have disabled all plugins except AT&RT, shut down and restarted MB, performed a preset (change case) and ASR showed the changes, but never displayed 'close' or 'save' and only changed one of the left side boxes changed from a tick to a solid box and promptly froze. MB's status bar shows "Changing case: 100% (2 file(s)) read" when it hangs.
cant reproduce this and dont have any ideas why this would happen. sorry.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 19, 2019, 08:24:46 PM
cant reproduce this and dont have any ideas why this would happen. sorry.
Thanks for taking a look at it. Since it is working with an older version, I'll keep using that until your next release and see what happens then.
Title: Re: Additional Tagging & Reporting Tools
Post by: dr0mo on November 22, 2019, 03:51:56 PM
cant reproduce this and dont have any ideas why this would happen. sorry.
Thanks for taking a look at it. Since it is working with an older version, I'll keep using that until your next release and see what happens then.

 I'm also having problems with the latest version of the plugin and can't seem to find a link to older versions. Can you upload the version you have?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 22, 2019, 04:49:35 PM
i'm afraid i have only very old version designed for musicbee 2.5:

https://drive.google.com/file/d/0B-D1MoIY406HbUllM1VzMlhrVXc/view?usp=sharing

maybe phred can upload the version he has (which is working for him without problems).
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 22, 2019, 09:26:10 PM
maybe phred can upload the version he has (which is working for him without problems).
Happy to help out. Here's the last version that works for me...
https://www.mediafire.com/file/noxrurht2m3zpeb/mb_TagTools_5.1.7154_2019-08-03.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: dr0mo on November 23, 2019, 04:09:15 AM
maybe phred can upload the version he has (which is working for him without problems).
Happy to help out. Here's the last version that works for me...
https://www.mediafire.com/file/noxrurht2m3zpeb/mb_TagTools_5.1.7154_2019-08-03.zip/file

Thanks for the answers & links. No more freezes, it's working fine now.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 23, 2019, 04:21:10 AM
Thanks for the answers & links. No more freezes, it's working fine now.
Great to hear it worked. For two reasons - one, your problem is solved. Two, because boroda couldn't reproduce the freezing issue I was having. The fact that you experienced it also, confirms that I'm not as crazy as I thought.

Perhaps boroda can dig into this a little more when he has the time.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 23, 2019, 04:21:46 AM
@phred, could you try this version?

http://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 23, 2019, 01:57:03 PM
@phred, could you try this version?
http://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
A test of 5.2.7214 shows no progress in resolving the issue.
I selected six tracks and selected the preset to change title to lower case.
The preview window shows what the new tag value would be, as expected.
Clicked on apply and MB went into a deep freeze requiring a CTRL-ALT-DEL to get to the task manager and kill the process.
Replaced the dll with 5.1.7154 performed the same action and no problem whatsoever.

I just noticed a couple of odd things in the available presets. Entries which I had not noticed previously. At the very end of the list are two 'presets' that make no sense. Perhaps the name is in Russian. The first has a description and the second does not...
(http://i.imgur.com/gwN0ipGl.jpg) (https://i.imgur.com/gwN0ipG.jpg)

There is also a preset named 'test' and the description is the same as the one in the screenshot.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 26, 2019, 01:11:32 PM
'delete' these 3 presets, manually delete all files from 'plugins\asr presets' folder, then unzip asr presets from any recent plugin zip and 'import all' presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 26, 2019, 08:02:19 PM
'delete' these 3 presets, manually delete all files from 'plugins\asr presets' folder, then unzip asr presets from any recent plugin zip and 'import all' presets.
@boroda...

Still not working. First off,my ASR Presets folder was under AppData not Plugins. Since it works there, I left it there.
Using the 'working' version of ASR I launched MB and deleted the three funky presets.
I closed and restarted MB  and using ASR I deleted all remaining presets and closed MB.
I checked the Presets folder and they were gone, and then copied them in from a recent zip.
Launched MB and ASR (older, working version) and imported the presets and ASR worked as it always has.
Closed MB, overwrote the working dll with the most recent dll, launched MB and as soon as I tried to apply a preset, MB locked up.
Closed MB, moved the presets folder to under Plugins and it still locked up.

So 5.2.7167 still not working for me. But know I'm wondering under what folder should the presets folder be? For the time being, I have it under the plugins folder. And 5.1.7154 is working as expected. Not so good with the latest version.

I appreciate you looking at this again. Let me know if you think of anything else that might be the cause.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 27, 2019, 04:34:40 PM
@phred, try this version:

http://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 27, 2019, 07:47:32 PM
@phred, try this version:
I'm sorry to report that this is even worse than before. I just about always launch MB in Album View. With the new dll, MB hangs before the artwork even loads.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 28, 2019, 04:49:08 AM
and this?

http://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 28, 2019, 06:29:59 PM
and this?
Sadly no.

But I did notice something that may help in figuring out what's going on...

I selected the preset "Remove the track number followed by a dah or dot from Track title."
Clicked 'preview' and saw the the proposed changes were correct and clicked 'apply'. In the 'new tag value' column all the changes were made, but as soon as it was done, MB locked up. And the changes were not applied to the actual tags. The first thing I checked was the file properties to see if they were Read Only. They were not.

Here's a screenshot of when the plugin was finished applying the changes. Note that the 'apply' button is showing 'stop' and has not returned to 'apply' as is usually the case when the changes are completed.
(http://i.imgur.com/voWd5sil.jpg) (https://i.imgur.com/voWd5si.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 29, 2019, 01:45:56 PM
Some new information.

Since I run the portable edition, I created a new MB install, left everything as default, then installed the plugin and presets. Relaunched MB and the plugin worked just fine on the one test I did.

I then imported my settings file to MB, which I had exported from the install I had been using up until today. Launched MB and it hung immediately. Closed MB, overwrote the dll with the one that had been working, and MB didn't hang. And the plugin worked as expected.

My conclusion is that there's a conflict between the AT&RT dll and -something- in my settings. But I have no idea how to proceed from here with any troubleshooting.

I know there is at least one other user who is experiencing this issue, so perhaps Steven can jump in and offer some advice.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 02, 2019, 10:12:25 AM
I was able to reproduce the MB freeze!

Still using 5.2.7214

I have an ASR preset that is auto-applied. Normally works fine.

If I use the tag editor and make changes to the tag that triggers the ASR, then use the arrows to move to the next track,
(https://i.imgur.com/SFyKPJr.png)
MB will lock up and I have to kill via Task Manager.

If I save and then move to the next track, no lock up.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 02, 2019, 01:53:27 PM
Good info Bee-liever. I have two (three?) auto-presets. I will disable them all and see what happens.

It seems like you were able to trigger the freeze once you were using the tag editor. My freezes have come not when editing, but simply using ASR. Or sometimes just launching MB.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 02, 2019, 02:47:21 PM
Using the working ASR I disabled the two auto-presets I had. Closed MB, copied over the latest plugin and launched MB. Used ASR to do a simple 'change case' and it locked up. Closed with Task Manager and tried again. Same thing. Replaced the new dll with the old and it now works as expected.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 03, 2019, 10:11:48 AM
phred, could you pm me your settings file?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 03, 2019, 12:56:09 PM
PM sent - thanks
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 03, 2019, 02:16:42 PM
yes! i can reproduce ui freezing. will look deeper now.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 03, 2019, 03:07:25 PM
yes! i can reproduce ui freezing. will look deeper now.
GREAT!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 04, 2019, 03:51:45 AM
https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 04, 2019, 08:30:36 PM
Did a quick two track test and the latest dll seems to be working without any lock-ups. I will have some time later today to test it further, but it's looking good.

I'm going to look back in this thread to see if I can find the other user who was having lock-ups and point him to this release and ask him to post here if it works for him or not.

Thanks for your time in tracking down this issue.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 04, 2019, 08:33:46 PM
I'm also having problems with the latest version of the plugin and can't seem to find a link to older versions. Can you upload the version you have?
@dr0mo-
Take a look at this new version of the dll that boroda posted. No more freezes. Please give it a try and post the results here.

https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 05, 2019, 09:04:06 AM
minor visual improvements (changed colors of all tables). also its full package of plugin, not just dll:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 06, 2019, 11:18:48 AM
new virtual tag function added:

$AddLeadingZeros(number,number_of_didgits_including_leading_zeros): adds leading zeros to number

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 06, 2019, 12:44:31 PM
Did a quick two track test and the latest dll seems to be working without any lock-ups. I will have some time later today to test it further, but it's looking good.
Follow-up... I used ASR quite a bit yesterday and had no issues whatsoever. Very glad you were able to fix it. Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 06, 2019, 10:17:41 PM
new virtual tag function added:

$AddLeadingZeros(number,number_of_didgits_including_leading_zeros): adds leading zeros to number

Uhmm.  Isn't that what $Pad(<field>,number) already does?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 10, 2019, 08:10:53 AM
yes, you are right. i've removed this function from plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: dr0mo on December 14, 2019, 06:31:31 PM
I'm also having problems with the latest version of the plugin and can't seem to find a link to older versions. Can you upload the version you have?
@dr0mo-
Take a look at this new version of the dll that boroda posted. No more freezes. Please give it a try and post the results here.

https://www.mediafire.com/file/lx6lk42gdeci018/mb_TagTools.dll/file

The last version is working fine too, thanks for the help guys
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 15, 2019, 02:35:51 AM
I'm having a problem with Advanced Search and replace. I have set up a rule to automatically rate any song 3.5 when Love=L and another one that does the reverse, Love a song if it's rated 3.5. This works generally when I'm using it but I have a script set to launch Musicbee, wait 60 seconds and close at night so that it syncs my playcounts and loves (from the day when using my phone) so that those stats are accurate. My phone doesn't use Loves so I'm trying to get musicbee to automatically rate songs 3.5 once the love sync happens but it's not doing it. I have an everything playlist that encompasses my entire library and I have the ASR presets I built set to run automatically if the song is in my everything playlist and I've tested it and it doesn't run. Help please.

If there is no way to automatically run ASR presets at startup would it be possible to add the "if Loved" criteria to the auto-rate tracks functionality so that it could be run at startup? All I'm after is some sort of automatic way for Musicbee to rate my loved tracks so that I can keep my Loves synced between Last.fm, my flac server and my phone.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 15, 2019, 09:21:17 AM
If there is no way to automatically run ASR presets at startup would it be possible to add the "if Loved" criteria to the auto-rate tracks functionality so that it could be run at startup? All I'm after is some sort of automatic way for Musicbee to rate my loved tracks so that I can keep my Loves synced between Last.fm, my flac server and my phone.
asr presets can't be run automatically on mb startup. they are run if any tag is changed (or if new track(s) is added to the library). but you tick preset to set Loved status if you change rating.
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 15, 2019, 04:50:21 PM
If there is no way to automatically run ASR presets at startup would it be possible to add the "if Loved" criteria to the auto-rate tracks functionality so that it could be run at startup? All I'm after is some sort of automatic way for Musicbee to rate my loved tracks so that I can keep my Loves synced between Last.fm, my flac server and my phone.
asr presets can't be run automatically on mb startup. they are run if any tag is changed (or if new track(s) is added to the library). but you tick preset to set Loved status if you change rating.

I have all the presets I created ticked to run automatically. Also, functionally, the last.fm love sync DOES update the tags when it runs but the ASR presets don't reflect this (and run accordingly) when that sync is done. Is there anything that can be done to fix this?

EDIT: Love is not a tag. It's a virtual tag in the musicbee database. That's why it's not running. No actual tag is being updated at startup. I'm going to create custom tag (not virtual) called Loved and another ASR preset that says if Love = L, make Loved = L also. Then run my rating preset against the Loved field since it's an actual tag and see if that works.

EDIT 2: That didn't work. I am formally requesting that running ASR presets at startup OR Auto-rate tracks based on Love status be added as a feature to the plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 16, 2019, 05:41:47 AM
Loved *is* a tag, though it's stored in mb database only. virtual tags are not stored anywhere at all, they are calculated dynamically.

I have all the presets I created ticked to run automatically. Also, functionally, the last.fm love sync DOES update the tags when it runs but the ASR presets don't reflect this (and run accordingly) when that sync is done. Is there anything that can be done to fix this?
this must work. what happens if you run preset manually?
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 16, 2019, 03:34:19 PM
Loved *is* a tag, though it's stored in mb database only. virtual tags are not stored anywhere at all, they are calculated dynamically.

I have all the presets I created ticked to run automatically. Also, functionally, the last.fm love sync DOES update the tags when it runs but the ASR presets don't reflect this (and run accordingly) when that sync is done. Is there anything that can be done to fix this?
this must work. what happens if you run preset manually?
If I select a Loved track and run the ASR preset manually it will work. If I Love a track within Musicbee then the rating will update automatically. But when I love a track outside of musicbee the ASR preset doesn't run automatically after the love sync happens at startup.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 17, 2019, 06:46:01 PM
but how do you love track outside mb? 'love' is mb database tag, you can't update it outside mb.
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 17, 2019, 07:07:29 PM
but how do you love track outside mb? 'love' is mb database tag, you can't update it outside mb.

"Love" is a last.fm rating method. You can love tracks on last.fm by going to the site and clicking the heart icon there provided you're logged into your account. I usually do it with the scrobbling app on my phone. This updates the love status in my account. Then when you open musicbee the last.fm playcount, love status and last played date are synced with the musicbee database if you have it set up to do this (which I do, I'm very invested in last.fm playback stats), updating those tags. If I love a song outside of musicbee then the next time musicbee opens, those songs are flagged as loved in the mb database due to this sync operation. But even though these tags are updated in the sync, the ASR presets don't run as a result of the last.fm sync. It only seems to run if I either manually run the ASR or if I manually love the song within musicbee. I do listen to a lot of music on my phone outside of musicbee and I do love songs on last.fm from my phone so I'm trying to get ASR to play nice with this workflow and run automatically as a result of the last.fm sync. Hope that clears up what I do and what I'm trying to accomplish. I really do appreciate your help :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 17, 2019, 07:17:10 PM
asr preset *must* be run if any tag is changed by any means (eg. due to syncing with last.fm). the only reason why this wouldn't happen is if plugin is started after last.fm syncing (last.fm plugin is built-in into mb and starts before any other plugin). i think i'll add 'apply on startup' option to asr.
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 17, 2019, 11:42:45 PM
that's great to hear! looking forward to testing it out once you finish the patch. Thank you so much.  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 18, 2019, 03:04:30 PM
https://www.mediafire.com/file/null/mb_TagTools_latest.zip/file

(https://www.mediafire.com/convkey/5310/uj6kfafc9cxs67k6g.jpg) (http://www.mediafire.com/view/uj6kfafc9cxs67k)
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 18, 2019, 03:32:46 PM
the download link is broken. Can you please update? Thanks for turning that around so fast  8)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 18, 2019, 03:58:42 PM
http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 18, 2019, 04:05:24 PM
right on. that works. I just made it to work. I'll be home in 9 hours and I can test it against my use case and see what happens. Thanks again.
Title: Re: Additional Tagging & Reporting Tools
Post by: whoozwah on December 19, 2019, 01:26:37 AM
the app just crashes. I continually get this error:

MusicBee v3.3.7261.33657D  (Win10.0), 18 Dec 2019 17:25:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.InitializeComponent()
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.asrEventHandler(Object sender, EventArgs e)
   at #=zUvgbLIsM5RlUtBS5uFvcgMr53IcC.#=z39UB1WA=(Object #=zRDI$Mj4=, EventArgs #=zRiDv2sk=)
   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 & Reporting Tools
Post by: boroda on December 26, 2019, 07:31:44 PM
i cant reproduce this. try to reinstall plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: foxj on January 15, 2020, 06:37:06 PM
I have also been getting an error with this plugin. MusicBee will disable it when it starts.
If I try to manually start it I will get this  ERROR (https://drive.google.com/open?id=10yWbMR9q1tZ_hiy_f5NNO9MBbJkhEzWW)
Both portable and installed versions 3.3. and 3.4 on win 10. (3.3.7310 & 3.3.7261)

Where does it put its log in the portable version?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 15, 2020, 08:18:21 PM
This might be a security issue. Whitelist your entire MB directory and try again.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 16, 2020, 06:35:06 AM
I have also been getting an error with this plugin. MusicBee will disable it when it starts.
If I try to manually start it I will get this  ERROR (https://drive.google.com/open?id=10yWbMR9q1tZ_hiy_f5NNO9MBbJkhEzWW)
Both portable and installed versions 3.3. and 3.4 on win 10. (3.3.7310 & 3.3.7261)

Where does it put its log in the portable version?
close mb, then delete file <mb appdata>\mb_tagtools.settings.xml
Title: Re: Additional Tagging & Reporting Tools
Post by: foxj on January 23, 2020, 04:46:22 PM
That worked thank you

Possibly because I copied it from the MusicBee installed version to the portable version?
Title: Re: Additional Tagging & Reporting Tools
Post by: asdasdasd223 on January 27, 2020, 04:45:38 AM
For some reason, it randomly stopped showing up in the drop-down menu. I reinstalled and saw that all the files were still there... I replaced everything and now I'm getting this error every time I open MusicBee: "Some tag names are duplicated"

When I try to use one of the advanced tagging tools, I get this error (https://pastebin.com/HBWTtBk5).
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 27, 2020, 01:01:23 PM
What version of MB are you using?

Completely uninstall the plugin, completely exit out of MB. The relaunch MB and reinstall the plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on January 28, 2020, 09:55:41 PM
Hello

I believe there used to be a help page for advanced search and replace but I can no longer find it.

Anyway I would really like to automatically add episode date (not time!) to the start of the existing podcast title. I understand I can use something like this:
$Date(<Episode Date>,MM-dd) <Title> in organizing podcasts, but I cannot seem to be able to use $Date(<Episode Date>,MM-dd) in the ASR.

In addition, I have been unable to get some RegExp to work that fetches the first 5 characters file name (that due to the organization above does have the month and date).

Could anyone point me in the right direction?

(I understand that creating a dynamic playlist I can get the tag updates to run automatically on only my podcasts - and I have created an auto playlist that only finds relevant podcasts)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2020, 04:05:05 PM
For some reason, it randomly stopped showing up in the drop-down menu. I reinstalled and saw that all the files were still there... I replaced everything and now I'm getting this error every time I open MusicBee: "Some tag names are duplicated"
this means that plugin requires that all tag names must be unique. go to edit> prefs> tags(2)> configure fields. make all tag names unique.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2020, 04:22:35 PM
Hello

I believe there used to be a help page for advanced search and replace but I can no longer find it.

Anyway I would really like to automatically add episode date (not time!) to the start of the existing podcast title. I understand I can use something like this:
$Date(<Episode Date>,MM-dd) <Title> in organizing podcasts, but I cannot seem to be able to use $Date(<Episode Date>,MM-dd) in the ASR.
create virtual tag with formula $Date(<Episode Date>,MM-dd) and use it in ASR.
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on January 30, 2020, 06:33:14 PM
Thank you!

Works well now. I actually had a virtual tag before but I could not get it to work in ASR.

Which settings in ASR do I need to make sure that this is applied to new podcasts as they are downloaded? Do I just need to tick it (I have already made an auto playlist for podcasts less than 30 days - but that also included those that are already updated)?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2020, 07:01:03 PM
asr can auto-apply presets to new tracks *and* existing tracks if any tag is changed. but you can assign virtual tag function id for any preset and use that preset function in a *virtual* tag (which is not stored at all).
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 02, 2020, 11:02:21 AM
I set it to auto-apply, but it keeps looping (each time ASR has added the episode to the start of the tag, (the tag is updated),it re-applies, and again, and again, ...)

How do I prevent this?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 03, 2020, 12:54:43 PM
can you post a screenshot?
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 03, 2020, 04:35:07 PM
ftp://hjem.fjelsten.dk/Public/MusicbeeEpisodeDate.png and ftp://hjem.fjelsten.dk/Public/MusicbeeEpisodeDateOverview.png
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 03, 2020, 05:48:32 PM
I set it to auto-apply, but it keeps looping (each time ASR has added the episode to the start of the tag, (the tag is updated),it re-applies, and again, and again, ...)

How do I prevent this?

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 03, 2020, 06:48:08 PM
Hello

Thank you.

I copied the file and ticked the preset. Unfortunately, a new podcast had come in so I manually ran it and then it started looping again. Ideally ASR would know that I have changed the tag from the actual ASR window.

I will check to see if this also happens on a fresh podcast update and report back.
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 05, 2020, 03:47:08 PM
Sorry, it does not work.

I got a new podcast today and it was automatically tagged:
"02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 02-04 Phil Ball on Martin Odegaard + Copa Preview; Loan Tracker; Castilla Corner"
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 05, 2020, 03:56:04 PM
i've tried your preset with generic track and it worked fine for me. i guess i need to try it with a real podcast.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 05, 2020, 04:08:52 PM
i cant reproduce this issue. could you pm me zipped folder "<mb appdata>\asr presets" and take give  ;D  me url of podcast in question?
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 05, 2020, 10:41:50 PM
Private message sent
Title: Re: Additional Tagging & Reporting Tools
Post by: Darwin4Ever on February 07, 2020, 04:42:56 PM
I'm trying to use the Tools -> Advanced Tagging Tools -> Library Reports  -> Export and as save as "HTML-Document" but always get this error :

Code
MusicBee v3.3.7261.33657P  (Win10.0), 7 Feb 2020 17:31:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'E:\MusicBeePortable\Library\Exported Track Lists\TEST.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.LibraryReportsCommand.exportTrackList()
   at MusicBeePlugin.LibraryReportsCommand.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)

There is no existing stylesheet at "TEST.files\stylesheet.css" !
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 08, 2020, 12:42:15 AM
what happens if you save report to other location, e.g. to desktop?
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 08, 2020, 08:24:53 AM
Any update on the auto update tagging loop?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 08, 2020, 08:41:39 AM
Any update on the auto update tagging loop?
the asr presets which you sent me didn't contain your custom preset. your preset uses <tag 1>, <tag 2> and <tag 3> customizable tags. what do you assign them to? i suspect that <tag 1> and <tag 3> are the same in your case. if this is the case, then this error is obvious.
Title: Re: Additional Tagging & Reporting Tools
Post by: Darwin4Ever on February 08, 2020, 10:46:38 AM
what happens if you save report to other location, e.g. to desktop?
Makes no difference, same error
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 08, 2020, 03:43:30 PM
Please find it here: ftp://hjem.fjelsten.dk/Public/Episodetitle.ASRPreset.xml
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 09, 2020, 10:52:35 AM
what happens if you save report to other location, e.g. to desktop?
Makes no difference, same error
yes, i can reproduce this. it's strange that nobody has reported this error earlier. will check this.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 10, 2020, 06:34:54 AM
Any update on the auto update tagging loop?

i cant reproduce this.

(https://www.mediafire.com/convkey/e8b6/fa8zqvhd2wr0pgk6g.jpg) (http://www.mediafire.com/view/fa8zqvhd2wr0pgk)

also, i cant understand how this could happen. if 2 source tags are different from destination tag, then reapplying preset wont repeat anything (if (+) checkbox next to tag 3 is unticked).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 10, 2020, 07:09:35 AM
I'm trying to use the Tools -> Advanced Tagging Tools -> Library Reports  -> Export and as save as "HTML-Document" but always get this error :

Code
MusicBee v3.3.7261.33657P  (Win10.0), 7 Feb 2020 17:31:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'E:\MusicBeePortable\Library\Exported Track Lists\TEST.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.LibraryReportsCommand.exportTrackList()
   at MusicBeePlugin.LibraryReportsCommand.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)

There is no existing stylesheet at "TEST.files\stylesheet.css" !

it's fixed:

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 10, 2020, 11:34:01 PM
Any update on the auto update tagging loop?

i cant reproduce this.

(https://www.mediafire.com/convkey/e8b6/fa8zqvhd2wr0pgk6g.jpg) (http://www.mediafire.com/view/fa8zqvhd2wr0pgk)

also, i cant understand how this could happen. if 2 source tags are different from destination tag, then reapplying preset wont repeat anything (if (+) checkbox next to tag 3 is unticked).

Have you downloaded my preset I linked to:

Please find it here: ftp://hjem.fjelsten.dk/Public/Episodetitle.ASRPreset.xml


I think the issue may be related to it first reads the title, and then adds to the title again.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 11, 2020, 01:16:52 AM
Have you downloaded my preset I linked to:

Please find it here: ftp://hjem.fjelsten.dk/Public/Episodetitle.ASRPreset.xml
yes.

I think the issue may be related to it first reads the title, and then adds to the title again.
but preset you sent me doesn't use title tag. if it reads title and then writes title, then i don't think i can do something about this. try to write to a custom tag instead of title.
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 12, 2020, 04:34:29 PM
Hmm.


So you're saying that if you need to add something to the beginning of the title tag (first read current title and then write new element to the beginning of the title and write it>), this is impossible?

It does include 2 titles: ftp://hjem.fjelsten.dk/Public/MusicbeeEpisodeDate.png
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 13, 2020, 04:19:57 AM
plugin CAN detect tag changes made by plugin itself and ignore them. but when downloading new episode, it is written by several dozens tags, and every tag writing triggers your preset. just make a custom tag named like 'my title', add it to main view instead of 'title' and write preset result to the custom tag.
Title: Re: Additional Tagging & Reporting Tools
Post by: fjelsten on February 13, 2020, 06:00:53 PM
Everything seems to work. Maybe the issue was related to having two versions of ASR installed. I have disabled one on there and it seems to be running fine now. Thanks for the plugin and all your help.
Title: Feature Request: more export options
Post by: fabiorfreitas on February 16, 2020, 02:46:13 AM
First of all, I'd like to say that this plugin is amazing and I'm so thankful for your work!

However, I feel there could be a few more export options, such as CSV and XML!

CSV is actually pretty easy to do myself with a little search and replace, but it would be a cool feature to have :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 16, 2020, 03:53:25 AM
what do need xml support for? you are the second person who requests this, but it's for several years.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 17, 2020, 07:25:29 AM
First of all, I'd like to say that this plugin is amazing and I'm so thankful for your work!

However, I feel there could be a few more export options, such as CSV and XML!

CSV is actually pretty easy to do myself with a little search and replace, but it would be a cool feature to have :)
i've added support for csv files.

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 21, 2020, 08:47:52 PM
I read in another thread (https://getmusicbee.com/forum/index.php?topic=30864.msg171125#msg171125 (http://Adios (feat. Aaron Neville))) that I shouldn't be adding a featured artist as part of the track title, as in "Adios (feat. Aaron Neville)". So I checked out Advanced Search and Replace and was very happy to see a preset "Extract featuring artist from track title and add them to the (Guest) Artist tag..."

However it's not working as I expected it to. It does indeed extract the featured artist, but doesn't put in the guest artist tag.
Originally I had this:
(http://i.imgur.com/2sl4fztl.jpg) (https://i.imgur.com/2sl4fzt.jpg)

After running AS&R I get this:
(http://i.imgur.com/TRfrF8el.jpg) (https://i.imgur.com/TRfrF8e.jpg)

While I expected this:
(http://i.imgur.com/8Ial3Vjl.jpg) (https://i.imgur.com/8Ial3Vj.jpg)

Here's the AS&R window:
(http://i.imgur.com/4r4zQ2ql.jpg) (https://i.imgur.com/4r4zQ2q.jpg)

Apparently the featured artist in the title is extracted but not removed. And it is not placed as guest artist in the artist splitter.
Am I not entering the criteria correctly? Is there a bug? Or does it just not work the way I expected?

EDIT: At this point I don't need nor want the featured artist removed from the title. But I would like to figure out why it's not being copied to the guest artist tag.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on February 21, 2020, 11:40:28 PM
@ phred
Just in regards to your above post and its mate in 'Cleaning up Sorting (Last Name, First Name) for Album Artists and Artists', Aaron Neville is only a featured artist on tracks 3, 4, 5, and 11 of that album.
With you going to all the trouble of changing the tags I thought, you know, that you might want to put the correct info in the tags while your doing it?  :o
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 22, 2020, 01:22:25 AM
...Aaron Neville is only a featured artist on tracks 3, 4, 5, and 11 of that album.
Hmmm ... And I'm showing him as the featured artist on eleven of the twelve tracks. I guess I'm off to do some research...
[five minutes later] Ok, here's what I found:
Wikipedia confirms what you said - 3, 4, 5, 11. As does Discogs and MusicBrainz.
AllMusic shows him as featured on all twelve tracks.

Quote
With you going to all the trouble of changing the tags I thought, you know, that you might want to put the correct info in the tags while your doing it?  :o
I have corrected the tags. Thanks Bee-liever. Much appreciated.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 22, 2020, 06:10:06 AM
@phred, both "Extract featuring artists..." presets must *not* remove featured artists from title, so it's normal. will investigate further.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 22, 2020, 06:16:25 AM
both (and maybe some other) presets don't work now. i think mb api has been changed in mb 3.3. i'll rewrite these presets or contact Steven for returning old api style (in addition to new (and better) api style).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 22, 2020, 12:53:50 PM
i've fixed this error (and couple other minor errors):

http://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

reimport new (or all) asr presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 22, 2020, 02:13:01 PM
i've fixed this error (and couple other minor errors):
I understand your comment that 'extract' won't remove and I'm fine with that.
Does the 'error' that you fixed address the 'guest artist' issue?

I'll have time to test it later today, but what to get clarification.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 22, 2020, 04:06:40 PM
Does the 'error' that you fixed address the 'guest artist' issue?
I'll have time to test it later today, but what to get clarification.
I have now had the time to test the new release and it addresses the Guest Artist tag. This will make copying the featured artist from the title to the guest artist tag a quick and easy task. I've got a little more that 400 tracks that will be fixed in a jiffy.

Thanks boroda!

Note to anyone who plans to use this new update: Be sure you import -all- your presents again.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 23, 2020, 02:03:22 PM
@boroda...

I'm seeing some unexpected behavior related to the latest fix (guest artist.)

I have this title
Johnny B. Goode - Take 2 (feat. Orianthi; Lindsay Ell; Cam; Troi Irons)
I run the extract featured artists preset and all four featured artists appear on one line in the artist splitter. It doesn't matter if I use commas or semi-colons to separate as the result is the same. I can PM a link to one of the tracks if that will be helpful.
(http://i.imgur.com/qkpo08Vl.jpg) (https://i.imgur.com/qkpo08V.jpg)

EDIT: Tried with MB versions 3.3.7357P and 3.3.7354 P. Same result.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 24, 2020, 06:36:45 AM
@phred, i  can't reproduce this, so could you pm me one of problem tracks?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 24, 2020, 12:52:41 PM
PM sent
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 24, 2020, 01:44:33 PM
i can't reproduce this with sent file:

(https://www.mediafire.com/convkey/6c97/qtjxq19cb73e8cf6g.jpg) (http://www.mediafire.com/view/qtjxq19cb73e8cf)

make sure that you've reimported all asr presets. if bug won't be fixed after reimporting, select asr preset you are using, click 'copy' button and post a screenshot of preset edit dialog (don't save preset copy).
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 24, 2020, 02:01:50 PM
make sure that you've reimported all asr presets. if bug won't be fixed after reimporting, select asr preset you are using, click 'copy' button and post a screenshot of preset edit dialog (don't save preset copy).
Reimporting the presets didn't fix the issue. Here's the preset:
(http://i.imgur.com/KfWyUlYl.jpg) (https://i.imgur.com/KfWyUlY.jpg)
I hope this helps.
Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 24, 2020, 02:31:20 PM
hmm. this preset should work, but it's not the latest version. redownload plugin and reimport all presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 24, 2020, 04:51:31 PM
hmm. this preset should work, but it's not the latest version. redownload plugin and reimport all presets.
My file worked for you?

Prior to this reply I was showing v5.2.7357, which I thought was the latest. I downloaded and installed from the link you have in reply #2262 and it shows the same version. I have imported all presets and still the same issue.

This is only happening with multiple artists after the word "feat." Single featured artists appear as 'guest artist' as expected. I did notice in the preview an ASCII character before the -first- guest artist, but not before the other guest artists. I don't know if that's a clue or not.
(http://i.imgur.com/1Nx5QqZl.jpg) (https://i.imgur.com/1Nx5QqZ.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 25, 2020, 01:56:42 AM
you have entered '&' in <custom text 2> instead of ';'
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 25, 2020, 02:28:41 AM
you have entered '&' in <custom text 2> instead of ';'
GRRRR! Thanks so much for finding that. I'm glad I attached that screenshot.
I don't recall ever using that preset before, so I must've accidentally changed it during this 'project.' All is now well.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 25, 2020, 02:38:34 AM
no, '&' is default delimiter, but maybe i must change it.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 25, 2020, 02:50:27 AM
no, '&' is default delimiter, but maybe i must change it.
Ahhh! I feel much better now. I did notice on the other 'featuring' presets that they also had "&" for Custom 2.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 25, 2020, 07:00:15 PM
@boroda...

Totally unrelated to the recent (now fixed) issue. If I tick a preset so that it is automatically applied, does it only apply to tracks in the library? Or does it also change tracks in the inbox?

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 25, 2020, 07:29:13 PM
it doesn't matter if track is in the inbox or in the library. also, ticked asr presets are auto-applied if new track is added to inbox or to library.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 25, 2020, 07:50:36 PM
it doesn't matter if track is in the inbox or in the library. also, ticked asr presets are auto-applied if new track is added to inbox or to library.
Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: Corliss Rain on February 25, 2020, 09:11:55 PM
Okay, maybe I'm missing something. I downloaded the latest update and installed it. How do I get the presets to populate? I typed in "feat" and nothing shows up.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 25, 2020, 09:31:27 PM
Okay, maybe I'm missing something. I downloaded the latest update and installed it. How do I get the presets to populate? I typed in "feat" and nothing shows up.
Make sure you've installed the plugin properly. The .dll goes in the plugin directory under the MB directory. And the -entire- ASR Presets directory goes under the Plugins directory.

Do you see any presets at all? If not, you probably haven't imported them. Make sure the presets and dll are placed as above. Launch Additional Tagging Tools from the Tools menu or by right-clicking a track/album > Additional Tagging Tools > Advanced Search & Replace > click on 'Import all' and that should take care of it.

Type "feat" in the search window and the presets containing 'feat' will appear. The most recent version has four presets that meet this criteria.

(http://i.imgur.com/6TSVa79l.jpg) (https://i.imgur.com/6TSVa79.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: Corliss Rain on February 25, 2020, 09:42:47 PM
Okay, I'm an idiot. Instead of having the folder directing in the plugins folder, I had moved the entire folder I extracted the file to into the plugin folder. Working now. Thanks!
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 26, 2020, 02:33:01 AM
Working now. Thanks!
Glad to hear it was something simple.
Title: Re: Additional Tagging & Reporting Tools
Post by: noose6767 on March 17, 2020, 03:51:28 PM
Hi, I can't seem to get the dialogue to show when I choose the "Copy tags to clipboard" option, it normally
appears and asks me which tags I wish to copy. I think it is because I was running Musicbee on a multiple monitor
set up and am now on a single monitor setup. Hope someone can help, thanks in advance.
Title: Re: Additional Tagging & Reporting Tools
Post by: noose6767 on March 18, 2020, 12:38:15 PM
I've fixed it by resetting the x and y values in the mb_TagTools.Settings.xml file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 27, 2020, 04:21:56 PM
just for future reference: you can clear plugin settings by clicking 'uninstall' button next to plugin name in mb prefs and restarting mb.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on April 12, 2020, 01:25:08 AM
Refer to bug report: https://getmusicbee.com/forum/index.php?topic=31196.0 (https://getmusicbee.com/forum/index.php?topic=31196.0)

Not sure if it's the plugin or MB.  :-\
Title: Re: Additional Tagging & Reporting Tools
Post by: Charpmen on April 15, 2020, 07:05:14 PM
Hi guys, I've looked all over this forum before posting my question. I'm having a hard time to figure out how to modify a script and save in the Advance search & replace tool.

I would like to extract the artists from these song titles in this playlist and place them in the appropriate artist tag https://imgur.com/PuW4i7J

The best preset I've found in the ASR tab is this one that would do the job is thos one https://imgur.com/Nolg4s1 but it's not doing anything.
Title: Re: Additional Tagging & Reporting Tools
Post by: frankz on April 15, 2020, 10:31:38 PM
I think you're using the wrong preset. You don't have any featured artists in the titles.

I think you need Split '<Tag 1>' to tags '<Tag 2>', '<Tag 3>'.

Tag 1 Title Tag 2 Title Tag 3 Artist Custom Text <space>-<space>

Don't type the word space, use however many spaces are before and after the "-" in your current title.

Try it on one or two at first and preview, preview, preview to make sure you're getting the results you want.  Specifically, I don't know if you need an interim tag for "Tag 2" or you can read and write Title in the same operation.

This plugin is a powerful tool and you can screw up your files pretty easily if you don't know what you're doing and/or do things without really thinking about it.
Title: Re: Additional Tagging & Reporting Tools
Post by: Charpmen on April 15, 2020, 10:53:00 PM
WOW :)  Thank you verry much
Title: Additional Plugins Tools and MusicBee Error
Post by: wirtual82 on April 25, 2020, 03:43:58 PM
How to get rid of this annoying error? I searched the forum, but I understand nothing of what I found about it.

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

Sorry, I have no clue.

I had to turn off that plugin because of this error.

Hopefully, I can find the answer because this is a really helpful and great plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: wonderdog on April 30, 2020, 09:34:25 PM
https://i.imgur.com/mbMCrct.jpg

Is there a way to print exactly the way the Library Report shows album artist, album, artwork when I run "preview"? See image attached.

If I try to do any or the exports HTML, CSV, M3U, TXT I don't get the same results. Under CSV, M3U, TXT i lose the album thumbnail. If I save under any of the HTML I get the Album thumbnails but no album artist or album, just the JPG info under the thumbnail.

The way the "Library Reports" generates the list before any export is what I am hoping to be able to print. It's alphabetized and simple, just album, artist and thumbnail.  



Thank you
Title: Re: Additional Tagging & Reporting Tools
Post by: kakkun on May 07, 2020, 08:33:14 PM
I'm trying to create an advanced search and replace preset that will increment play count and set the "last played" tag as the current time. I've been able to update the play count, but not the last played tag. Is this not possible because the last played tag is not user editable? I would appreciate any help with this.
Title: Re: Additional Tagging & Reporting Tools
Post by: ariesps on May 13, 2020, 01:38:08 AM
Hi all,

I 'm looking to implement some way to copy MusicBee ratings, mainly in FLAC Files, to Traktor compatible rating tag. Half based ratings are disabled on MusicBee

On Mp3Tag I create a RATING WMP tag, which value is replaced based on RATING tag set on MusicBee. This works ok and Traktor reads correctly ratings.

(https://i.imgur.com/dHHi916.jpg)

Is there anyway to get this to work within Advanced Search & Replace and regular expressions?

In MusicBee I've created a custom Tag, named RATING WMP, as a number.

Thanks in advance.
Title: Re: Additional Tagging & Reporting Tools
Post by: ariesps on May 13, 2020, 07:33:02 PM
Hi all,

I 'm looking to implement some way to copy MusicBee ratings, mainly in FLAC Files, to Traktor compatible rating tag. Half based ratings are disabled on MusicBee

On Mp3Tag I create a RATING WMP tag, which value is replaced based on RATING tag set on MusicBee. This works ok and Traktor reads correctly ratings.

(https://i.imgur.com/dHHi916.jpg)

Is there anyway to get this to work within Advanced Search & Replace and regular expressions?

In MusicBee I've created a custom Tag, named RATING WMP, as a number.

Thanks in advance.

Done!

Although RATING values in Musicbee flac files are 20,40,60,80,100, ASR must read them as (1), (2), (3), (4) or (5). Now RATING WMP custom tag is populated correctly and I can finally have tags in sync between Musicbee & Traktor. Same ratings on both softwares.

Title: Re: Additional Tagging & Reporting Tools
Post by: Tybot on May 19, 2020, 01:23:24 AM
Anyone know if it's possible to sort multi-value tags alphabetically somehow? I have a custom tag called <TrackInfo>, some with only one value and some with multiple values. The multiple ones are not ordered and very inconsistent.

Looking to turn this: [take 1]; [extended]; [5.1 mix]
Into this: [5.1 mix]; [extended]; [take 1]
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 23, 2020, 06:03:23 AM
How to get rid of this annoying error? I searched the forum, but I understand nothing of what I found about it.

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

Sorry, I have no clue.

I had to turn off that plugin because of this error.

Hopefully, I can find the answer because this is a really helpful and great plugin.
plugin wont work correctly if you see this message. go to mb menu> edit> prefs> tags (1)> custom tags> define new tags> configure fields. make sure that all tag names are unique.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 23, 2020, 06:06:52 AM
https://i.imgur.com/mbMCrct.jpg

Is there a way to print exactly the way the Library Report shows album artist, album, artwork when I run "preview"? See image attached.

If I try to do any or the exports HTML, CSV, M3U, TXT I don't get the same results. Under CSV, M3U, TXT i lose the album thumbnail. If I save under any of the HTML I get the Album thumbnails but no album artist or album, just the JPG info under the thumbnail.

The way the "Library Reports" generates the list before any export is what I am hoping to be able to print. It's alphabetized and simple, just album, artist and thumbnail. 



Thank you
suggest that you are looking in some subfolder of the folder where you saved html. find html file in upper folder.
Title: Re: Additional Tagging & Reporting Tools
Post by: un-imaginative on May 31, 2020, 03:19:16 AM
Hi boroda,

I am having several issues with ASR tool; both Change Case and Advanced Search & Replace. (Version 5.2 from Official Add-In page)
I'm unsure if there is something wrong with the tool, or possibly folder permissions on my PC but I have been unable to solve the problems.

There are two clear issues I'm having, and both seem to be related to the settings.xml located in user files:

Issue 1 - Change case ignoring some excepted words, but not others:
It seems that only words located in the default list under <exceptionWords> in mb_TagTools.Settings.xml work here.
If I delete/add a word such as 'and', 'for' or 'but' it will work, but other words are ignored (see example).

(https://i.imgur.com/jYwX9La.jpg)
The word 'out' not being detected.

(https://i.imgur.com/9deNw33.jpg)
Removing the word 'and' causing it to change case as expected.

Issue 2 -  'Set as default for Advanced Search & Replace preset' buttons located in Change Case do not work:
Despite setting '(' as a character in 'Except for words after symbols' list or '-' as a word splitter and pressing the button ASR will ignore those settings.
I managed to set '-' as a word splitter by manually editing <wordSplittersASR> (default setting is 'ASR'), but was unable to get ASR to detect brackets, etc.

Any advice you can give on how I can solve this would be great.

Edit: It seems like I misunderstood and Word Breaks don't force a capital, is it possible to add this feature (for example first letter after a bracket is always capitalised)?

I'm still having issues with the change case tool not syncing settings to ASR correctly.
Title: Re: Additional Tagging & Reporting Tools
Post by: SpirosG on June 08, 2020, 06:19:20 PM
Hi Boroda,

Any chance to add a function to convert ID3 tags from v2.3 to v2.4?
Title: Re: Additional Tagging & Reporting Tools
Post by: JMuller on June 20, 2020, 10:10:30 AM
Is there a way to import a list of tags to be replaced? I have hundreds of tags in the following format:
tagBefore1;tagAfter1
tagBefore2;tagAfter2
...

Advanced Search & Replace handles only up to 5 tags, and they can only be input manually.

Edit: Found another solution, see here (https://getmusicbee.com/forum/index.php?topic=31959.msg176399#msg176399).
Title: Re: Additional Tagging & Reporting Tools
Post by: hamlet35 on July 18, 2020, 03:44:46 PM
I've searched and searched on the form and I think my keyword is too short and vague to find what I'm looking for - so I apologize in advance if this has been answered fifty million times already but ....

I am looking to update and split my artists field using search and replace in Additional Tagging & Reporting Tools - I have the commas working and the "/" and the "&" but the word "and" or "And" is causing issues with a Name like "Nancy Anderson" - it's changing and splitting it into "Nancy" and "erson".  I was thinking I could just do it by case, but some of the tags have "And" not "and" for the word.


Thanks for any help - I'm sure I am missing something that is already there, but I can't figure it out.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on July 19, 2020, 12:06:44 AM
I've searched and searched on the form and I think my keyword is too short and vague to find what I'm looking for - so I apologize in advance if this has been answered fifty million times already but ....

I am looking to update and split my artists field using search and replace in Additional Tagging & Reporting Tools - I have the commas working and the "/" and the "&" but the word "and" or "And" is causing issues with a Name like "Nancy Anderson" - it's changing and splitting it into "Nancy" and "erson".  I was thinking I could just do it by case, but some of the tags have "And" not "and" for the word.


Thanks for any help - I'm sure I am missing something that is already there, but I can't figure it out.

Not exactly sure how splitting tags with the plug-in works, but if using regular expressions, add "\s" after "and" or if not simply use "and "
Title: Re: Additional Tagging & Reporting Tools
Post by: Corliss Rain on July 19, 2020, 07:18:15 AM
I've searched and searched on the form and I think my keyword is too short and vague to find what I'm looking for - so I apologize in advance if this has been answered fifty million times already but ....

I am looking to update and split my artists field using search and replace in Additional Tagging & Reporting Tools - I have the commas working and the "/" and the "&" but the word "and" or "And" is causing issues with a Name like "Nancy Anderson" - it's changing and splitting it into "Nancy" and "erson".  I was thinking I could just do it by case, but some of the tags have "And" not "and" for the word.


Thanks for any help - I'm sure I am missing something that is already there, but I can't figure it out.

The simplest solution would be to do a serch and replace for " and " in the artist field and replace it with " & ". Then "and" won't be an issue.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on July 21, 2020, 07:12:10 PM
EDIT: Disregard.

For the last few days, I've been trying to use the plugin's $Len() function with the built-in $If() function and have been running into an issue.

Let's say $Len(<Composer>) is 8.
Code
$If($Len(<Composer>)=8,T,F)
$If($Len(<Composer>)>0,T,F)
$If($Len(<Composer>)>7,T,F)
...all should return "T," which they do.


Code
$If($Len(<Composer>)>9,T,F)
...correctly returns "F."


Code
$If($Len(<Composer>)>10,T,F)
...incorrectly returns "T." From then on, all numbers up to 79 return "T" when then they should be false. If I insert a leading zero ahead of $Len()...


Code
$If(0$Len(<Composer>)>79,T,F)
...I get the correct result "F."

Is $Len() is returning the number as a string?
Title: Weird issues with auto-rating tracks - (Using Additional tagging tools)
Post by: ParaGnosis on August 14, 2020, 11:21:41 AM
Information:

Musicbee Version: 3.3.7491 Store

Plugins Used: Additional Tagging Tools - Version: 5.0.7049



Hi folks,

I'm having issues with the Additional Tagging Tools plugin and auto-rating my tracks in Musicbee.


It seems to be working mostly fine, except for the fact that occasionally some of my tracks are being rated at very high values; 50 being the highest.

I'm very confused as to how a track can be rated at 50 when (to the best of my knowledge) the rating is out of 5.



Here is a screenshot of the settings I'm using to auto-rate my tracks.

(https://i.imgur.com/OUaj3FN.png)


Side Issue: I'm not sure what settings would be best to use so if anyone has any better suggestions on that then let me know.





Attached is a Google Sheets spreadsheet with my entire library in it with the information as follows;

1. Album Artist (Displayed)
2. Album
3. (Track) Title
4. (Date) Last Played
5. DateValue - converts date into format where I can calculate the number of days since a track is played)
6. Days Since Played
7. Rating
8. Custom8 - Number of plays per day (calculated by Auto-rate)
9. Average value(Play Count/URL)
10. Average value(Skip Count/URL)
11. Average value(Rating/URL)
12. Todays Date (Will automatically update as each day passes)

The Spreadsheet is https://docs.google.com/spreadsheets/d/15OYaYM4ARKX_XOPDNNY2M_6niFdoJspqwL9htidA3Ro/edit?usp=sharing (https://docs.google.com/spreadsheets/d/15OYaYM4ARKX_XOPDNNY2M_6niFdoJspqwL9htidA3Ro/edit?usp=sharing)



If anyone has any ides or help with this issue then that would be amazing!

Like I said, the auto-rating mostly seems to be working fine, it's just some random, very high values that have got me really, really, confused.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 14, 2020, 12:55:21 PM
I moved your post from Questions to the Additional Tagging & Reporting Tools thread so the author would have a better chance of seeing it. That being said, he hasn't been on the forum for the past three months. Hopefully someone will be able to offer some suggestions.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on August 24, 2020, 08:06:44 PM
Hi,
re this:
https://getmusicbee.com/forum/index.php?topic=3833.msg140371#msg140371

Does arithemtic operations work with Search & Replace ?

I'm attempting (on Tag1 = 160)
Step 1
Search for:
^(.*)
Replace with:
$Div($1,2)

Results in:
"$Div($1,2)"
not
80
which I was attempting for...

Where's my brainfart here... does S&R not work with the arithmetic operations...? or is my syntax messed...?
Churs.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: KLGavin on September 04, 2020, 10:38:06 AM
Hi, just got the error message below when trying to get ASR plugin installed & working properly. Probably something I've done wrong somewhere in installing. I installed MusicBee (Windows 10) from the full installer pack, downloaded the ASR plugin and copied the files to the Plugins folder.


MusicBee v3.3.7491.38139D  (Win10.0), 4 Sep 2020 10:34:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zHqthFCuvsWP5aw_SIg==.#=zmnQgvZ0=(IntPtr #=zBcSYWJaalro8)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on September 04, 2020, 11:59:04 AM
downloaded the ASR plugin and copied the files to the Plugins folder.
Make sure there is sub-directory "ASR Presets" exists in the Plugins directory. And that mb_TagTools.dll exists in the Plugins directory.

Does "additional tagging tools" show up under Preferences > Plugins? If so what happens when you click on "Configure"?

You might to wait for the plugin's author to check in with suggestions. But note that he hasn't been on the forum since May and is (was) usually very responsive.
Title: Re: Additional Tagging & Reporting Tools
Post by: KLGavin on September 04, 2020, 04:46:19 PM
downloaded the ASR plugin and copied the files to the Plugins folder.
Make sure there is sub-directory "ASR Presets" exists in the Plugins directory. And that mb_TagTools.dll exists in the Plugins directory.

Does "additional tagging tools" show up under Preferences > Plugins? If so what happens when you click on "Configure"?

You might to wait for the plugin's author to check in with suggestions. But note that he hasn't been on the forum since May and is (was) usually very responsive.

Thanks - yes sub-directory and .dll in the right place. I get that error when I click on the 'configure' button under Preferences>Plugins. It's intermittent - I seem to be able to get it to work for a while by uninstalling/deleting/re-starting pc and reloading, but I haven't worked out exactly how. I'll keep playing around.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on September 04, 2020, 04:51:27 PM
I seem to be able to get it to work for a while by uninstalling/deleting/re-starting pc and reloading, but I haven't worked out exactly how. I'll keep playing around.
Needless to say, but I'll say it anyway, you shouldn't have to do that to get it to work. Boroda always gives the ZIP a file name of "latest version." What version are you running (Preferences > Plugins > additional tagging tools > configure and it's in the lower left corner. I'm using 5.2.7357 on MB v3.4.x, but it was working fine for me going back to MB v2.5.x.

Sorry I can't be more help.
Title: Re: Additional Tagging & Reporting Tools
Post by: dankjankem on December 21, 2020, 02:09:29 AM
This might be a dumb question, but how can I use meta taqs within Advanced Search & Replace?
For example, I downloaded an album with each song named "Untitled" and I wanted to use AS&R to convert these into [untitled #1], [untitled #2], [untitled #3] and so on...
(https://i.imgur.com/HnqtogN.png)
I tried using the method pictured above, but the track names simply changed to "[untitled #<Track#>]" so I was hoping you guys could maybe guide me in the right direction with using meta tags in AS&R. Thanks!
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 21, 2020, 02:57:25 AM
Which preset are you using in your screenshot?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 21, 2020, 03:15:50 AM
You can't do it directly in AS&R, but here's a three step work-around
   - Use the preset 'Add text <Custon text 1> to the beginning of <Tag 1>
   - Set Tag 1 to Track#
   - Set Custom text 1 to untitled #
This will change the <Track#> to "untiltled #x"
(http://i.imgur.com/TYiJXxMl.jpg) (https://i.imgur.com/TYiJXxM.jpg)

Then use the present 'TOY: Copy tag command'
   - Set Tag 1 to Track#
   - Set Tag 2 to Title

Lastly, to restore <Track#> back to what it was, use MB's Tools > Tagging Tools > Renumber Tracks

Test this on a few tracks before doing a lot of tracks. And make backups of the test tracks before starting.
Title: Re: Additional Tagging & Reporting Tools
Post by: dankjankem on December 21, 2020, 05:47:38 AM
Thank you so much!

Edit: Oh I just now saw your question, i was using a custom preset that i was in the process of making
Title: Re: Additional Tagging & Reporting Tools
Post by: dankjankem on December 21, 2020, 06:22:58 AM
Ok I just found an even better method, what I did was make a copy of the "TOY: Copy tag command" and then revised it as such:
(https://i.imgur.com/NYWLOAA.png)

This will then yield the following:
(https://i.imgur.com/6QkPzpb.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 21, 2020, 12:54:05 PM
Nice. Somewhat more elegant than my suggestion. Glad you figured it out.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 30, 2020, 08:21:37 PM
Could anyone enlighten me on what 'TOY' stands for?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 30, 2020, 09:09:45 PM
Could anyone enlighten me on what 'TOY' stands for?
It couldn't possibly be one of these, could it?   :-}
TOY   Toys R Us Inc. (stock symbol)
TOY   Time of Year
TOY   Thinking Of You
TOY   Theater of Youth (Buffalo, NY)
TOY   Trademark of Youth (band)
TOY    Toyama, Japan - Toyama (Airport Code)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 30, 2020, 10:00:14 PM
TOY Toys R Us Inc. (stock symbol)
TOY Time of Year
TOY Thinking Of You
TOY Theater of Youth (Buffalo, NY)
TOY Trademark of Youth (band)
TOY Toyama, Japan - Toyama (Airport Code)

I'll give you a C for effort.

Anybody has knowledge to share that he thinks deserves an E A?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 30, 2020, 10:23:03 PM
I'll give you a C for effort.
Anybody has knowledge to share that he thinks deserves an E?
I reject the C and will take an F instead. I cheated. I lied. I stole from the Internet.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 30, 2020, 10:33:46 PM
I reject the C and will take an F instead. I cheated. I lied. I stole from the Internet.

And I got the order of the A–F thingy wrong. (we don't use that system in the biotope I am existing in)

So… a correction: I am in need of an A, not an F:
What does TOY mean regarding the Additional Tagging & Reporting Tools?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on January 06, 2021, 10:45:19 AM
I've just found this plugin and I was hoping someone could help.

I'm looking at creating a tag in my MP3s for "Favourite Artist".

Is it possible using this plugin to search for several artists and then create a "Y" in another tag called "FavArtist"?

This way, a smart playlist can be created using this information. Also, if it is possible, can it auto update whenever new music gets added that matches the criteria?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2021, 12:01:42 PM
Are you sure you want/need a custom tag for this?
It will be easier to accomplish by using a virtual tag.
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on January 06, 2021, 12:13:04 PM
Cool no problem I'll have a look into virtual tags cheers

I guess the advantage of doing it with the actual tags though is that is is saved to the music file which might be an advantage.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2021, 01:09:43 PM
I guess the advantage of doing it with the actual tags though is that is is saved to the music file which might be an advantage.
Both have their own advantage/disadvantage.

If you decide on using custom tags for it I am sure some users experienced with the Additional Tagging Tool can help you out.
It has a lot of presets build-in b.t.w., you could try one that fits the bill the most and adjust it to your requirements.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2021, 01:10:55 PM
What does TOY mean regarding the Additional Tagging & Reporting Tools?

Surely somebody must know?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on January 06, 2021, 01:37:43 PM
I guess the advantage of doing it with the actual tags though is that is is saved to the music file which might be an advantage.
Both have their own advantage/disadvantage.

If you decide on using custom tags for it I am sure some users experienced with the Additional Tagging Tool can help you out.
It has a lot of presets build-in b.t.w., you could try one that fits the bill the most and adjust it to your requirements.

I did have a look but couldn't really figure it out in the find and replace and none of the presets seemed to quite fit.

It looks really powerful and all I would need would be something like:
If artist contains artist 1 or artist 2 or artist 3 etc etc, write Y to a custom tag called FavArtist.

But I couldn't really get it to work properly.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2021, 04:21:30 PM
But I couldn't really get it to work properly.
Just curious, how many artists are we talking about here?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on January 07, 2021, 08:43:36 AM
But I couldn't really get it to work properly.
Just curious, how many artists are we talking about here?

Not that many - I'll probably just revert to using my smart playlist  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: so_la_la on January 27, 2021, 04:18:58 PM
With me *MB v3.4 Win 10), the plug in's menu is unreadable with a dark skin because its text color won't change to white so it's white on white. Just sayin' - I know that maintaining involves a lot of work and I don't expect anything...
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 15, 2021, 08:01:55 PM
Hey! Complete noobie here. How do I go about downloading and installing the plugin? I don't see a link for the most recent version or anything and there's quite a lot of posts to sift through!
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on February 15, 2021, 08:13:15 PM
Hey! Complete noobie here. How do I go about downloading and installing the plugin? I don't see a link for the most recent version or anything and there's quite a lot of posts to sift through!
On the official add on page afaik:
https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/

c.
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 15, 2021, 10:29:05 PM
Hey! Complete noobie here. How do I go about downloading and installing the plugin? I don't see a link for the most recent version or anything and there's quite a lot of posts to sift through!
On the official add on page afaik:
https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/

c.
Thanks!
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 15, 2021, 10:48:24 PM
I think I have a bug with $Random? It keeps adding a prefix and suffix segment when I ask for a number.

If I do anything 2 or lower, it will print D0#5 (# being the random number)
If I do anything up to 30 it will print D1<number>5.
If I do anything up to 315 it will print D2<number>5.
etc.

So for example, if I do "$Random(100) and the value is 57, it will print "D2575"

What's going on here?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 15, 2021, 11:17:11 PM
Not to dampen your spirit, but the developer of this plugin hasn't been on the forum since last May.
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 15, 2021, 11:50:29 PM
Not to dampen your spirit, but the developer of this plugin hasn't been on the forum since last May.
Ah well that's tragic! It's not a suuper big deal at least since you can use some functions to trim the first two and last digit off, at least! I was just curious if there was a reason for the extra characters.

Edit:
Yeah not too hard using the "CutLeft" and "CutRight" functions that are provided by the plugins.

Using this works for all potential max values:
$CutRight($CutLeft($Random(####),2),1)
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 16, 2021, 02:42:40 PM
Followup question about "Random"

Anybody here actually try using it for anything? It has a major flaw in that it refreshes every single time it is called, which wouldn't be a big deal except that that even extends into if you have an external virtual tag for it. I was hoping to use it for some logic but there's no way to call it and have it retain it's same value throughout an instance which would be required for using it with logic.

For example, if I have a virtual tag <Random10> that's a random between 0 and 9, and I try to have it do something different for each number response with a long series of If, else statements (or even discrete if/then statements for each case), like below:
$If(<Random10>=0,???,)
$If(<Random10>=1,???,)
...
etc.

It will sometimes output multiple values. Conversely, if I did one really large if/else that counts down I have majority of cases having it completely going to the bottom of the loop, since the function is being updated every time it is called because it might get updated with a value that matches one of the cases that was already failed...

Does anybody know a way to utilize this function for logic like this effectively? Am I just missing something? I hope so!  :(
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 18, 2021, 01:46:38 AM
Hey I have a question for everyone with more experience with this tool. I'm trying to figure out if there's a way I can use the Automatic Library Reports feature to do the following:

Make a report that will work with the $ALR(<URL>,preset_id) function and, for any given track, check to see what tracks have been played, and sum up the duration for every track in the same album that has been played at least once (ideally using whatever criteria MusicBee does to group the tracks). My hope is that I can take this value, and use $SubDuration with the <Album Duration> to give me a track-by-track display of the time remaining before the album is finished for when I am shuffling by album.


virtual function id: timeplayed (is sum of TIME for all played tracks in a given track URL's album)

Track information field entry:
$SubDuration(<Album Duration>,$ALR(<URL>,timeplayed))

So if an album is 5 tracks and 14:30 total, and the play data looks like this:
Track 1: PLAYED         1:53
Track 2: PLAYED         4:20
Track 3: PLAYED         0:52
Track 4: PLAYING       4:25
Track 5: UNPLAYED   3:00

While playing Track 4
$ALR(<URL>,timeplayed) = 7:05

and therefore
$SubDuration(<Album Duration>,$ALR(<URL>,timeplayed)) = 7:25


Is such a thing possible?
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 18, 2021, 03:45:38 PM
Okay so I can get the actual ALR preview box to work with the following setup, now it's just a matter of figuring out how to grab the info with the $ALR function real-time!

Used a pair of Virtual tags:
AlbumDisc = <Album><Disc>  (I am using disc to denote albums in my library, so this gives a unique ID for each disc individually)
TimeIFPlayed = $If(<Play Count>>0,<Time>,)  (Displays track time if it has been played)

I then set it up in the ALR menu as so:
"AlbumDisc, Sum(TimeIFPlayed)"
I set it to save Sum(TimeIFPlayed) to <NULL> and assigned virtual tag function ID "test"

When I update and preview it does what I expect in the preview window, but I have not figured out how to grab this info in the "Track Information" panel.
I tried the following:
$ALR(<URL>,test)   -   which is NULL for all but a few random albums? Maybe 6 out of the hundreds of albums
and
$ALR(<AlbumDisc>,test)  - which throws an exception for about half of the results and nothing at all for the other half.

Exception text: "$ALR Failed: Exception has been thrown by the target of an invocation."


Am I missing something here? I feel like I'm soooo close!


Edit: I have confirmed for the 1% that displays correctly using <URL> for that it does update after each track is played, however I'm getting an exception with Sub/AddDuration when I try to use it. Going to try to see if I can work around it.

Edit Edit: Trying to see if I can define a Custom Tag for it to save to (that isn't saved to any files so I don't change the modified dates on them), so I can then use the Custom tag in my formulas and hopefully get around the issue with it throwing exceptions when I try to use the value. It seems to throw an exception when I use the ALR function with any of AT&RT's math functions, even if I go and only use a numerical bit (no :'s) with a standard add or subtract function. :\

However, I can't seem to get it to save to the tag. I set it to save "Sum(TimeIFPlayed)" to custom tag "PlayedTime", but it doesn't seem to be saving. idk if I am missing something.. Here's a screencap:

 (https://i.imgur.com/LC5Gavx.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: MayorQwert on February 18, 2021, 06:51:12 PM
Got the softlock fixed. For some reason, now if I tell any to update at startup it will freeze when the counter says 100% until I right click the taskbar process and press "close" then wait a few seconds and press "no". For some reason it never finishes updating otherwise and softlocks. The same is true if it tries to automatically update all the tags while the process has been open (by using the "update every x tracks" tick box).

For now I just unticked both presets I had and will just go from there. At least the preset that displays the number of sections an album has (counting every 'disc' value) still works..

Aaaaand great.... somehow I softlocked MusicBee.... :|

I unchecked the tick next to the preset at the top and also checked "Save only if tag" AlbumDisc IS AlbumDisc. (wasn't sure but thought that would maybe cause it to write every time I changed songs since it would always be equal).

Also added a second preset to display the number of unique disc values for a given album (the default disc count function wasn't displaying appropriately for all cases).
I did it with:
Album, Count(Disc#) linked with a virtual function id. Confirmed that one worked perfectly, at least.

The problem started when I restarted MusicBee. It freezes while generating previews with the text "Generating preview (reading): 100%" perpetually at the bottom.

I tried deleting the folder for the plugin, but to no avail... is there a way I can fix this without a total reinstall?
Title: Re: Additional Tagging & Reporting Tools
Post by: snively on March 12, 2021, 01:52:39 PM
Would this plugin have the capability of combining two different play counts? I've spent time between foobar and iTunes and it's not looking good on finding a way to combine the two diff play count tags.

(https://i.imgur.com/5fobTlQ.png)

Edit: So I found this option here:

(https://i.imgur.com/2gcLQnp.png)

but this doesn't actually combine (add one into the other, 1+2=3) it just takes both of the tags and incorporates them into 1 tag. Would it be possible to get an option to do this?

edit: if anyone ever comes across this, you can use a program titled Mp3Tag to combine two different play counts.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 18, 2021, 09:07:08 AM
What would be the easiest way to copy everything before (or after) a certain character to another tag? For example, in a file with track title "Café Del Mar [Humate Remix]", I'd like to copy Café Del Mar to <album>. I know that there is a preset "Move everything before <Custom text> from <Tag 1> to <Tag 2>", but if I want to copy instead of move. I'm sure I'm just missing something here, but how would you do it? (In one single step that is, I guess I could copy the entire tag, and then use "remove everything before and including...".)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on March 18, 2021, 12:42:55 PM
I don't think you can do it in one step. You'll have to use the preset "TOY: Copy tag command" to move <title> to <album> and then use one of the "remove" presets. There are a few that might work, but you'll have to test them to see which does exactly what you want. And DO NOT do a mass change until you're certain it's working as expected.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 18, 2021, 01:11:39 PM
I don't think you can do it in one step. You'll have to use the preset "TOY: Copy tag command" to move <title> to <album> and then use one of the "remove" presets. There are a few that might work, but you'll have to test them to see which does exactly what you want. And DO NOT do a mass change until you're certain it's working as expected.

Thanks @phred, will do so (including testing first...)! And to @boroda, may I put this to a wishlist?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on March 18, 2021, 01:15:02 PM
And to @boroda, may I put this to a wishlist?
Please let us know how it worked.

Boroda hasn't been on the forum since last May, so I don't know what will happen with your request.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 18, 2021, 08:55:06 PM
Please let us know how it worked.

Boroda hasn't been on the forum since last May, so I don't know what will happen with your request.

Oh, I hope he's ok!

As a follow-up, I ended up using the regular Additional Tagging Tools>Tagging tools>Copy Tag and copied <title> to <album>, and then ATRT's "Remove everything after and including <Custom Text> in tag <Tag 1>.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on March 18, 2021, 09:11:18 PM
Oh, I hope he's ok!
I have send him a PM a couple of weeks (probably months) ago, that should get forwarded to his email, but I got no response from that either.
Let's hope he's O.K.
Or, if he is just done with MusicBee it would be helpful if he could state that.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 18, 2021, 09:17:31 PM
I have send him a PM a couple of weeks (probably months) ago, that should get forwarded to his email, but I got no response from that either.
Let's hope he's O.K.
Or, if he is just done with MusicBee it would be helpful if he could state that.

Oh, impossible to not think about Covid...  :'(
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on March 18, 2021, 09:32:23 PM
Oh, impossible to not think about Covid...  :'(
No, he is Russian, he's probably tough.
Title: Re: Additional Tagging & Reporting Tools
Post by: cjoprey on April 08, 2021, 05:50:44 PM
Let's hope he's OK...

On another bug note - I'm using the latest portable build of Musicbee (3.4.7764) and every time I try to enable the latest version of mb_tagtools  I get an error telling me: "Unable to initialise plugin: mb_TagTools.dll Exception has been thrown by the target of an invocation." - anyone know how to get round this and get the tools working again? I miss the support it gives!
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 08, 2021, 05:56:37 PM
Are you certain that the plugin is in the Plugin's directory which is directly under the MB directory?

The only other thing I can think of would be to whitelist the entire MB directory in your AV/Security software application. DLLs can sometimes trigger a false positive.
Title: Re: Additional Tagging & Reporting Tools
Post by: cjoprey on April 08, 2021, 06:22:45 PM
Thanks for the response @phred.

Just to be sure, I redownloaded the latest ZIP file, and unpacked it to the Plugins folder under my portable Musicbee install. I know it's the correct one as I also added the Discordbee plugin to the same folder, and that works. I then went into my AnitVirus and excluded the entire Musicbee install folder to ensure that won't affect it.

I have the same symptoms sadly - I can see that mb_tagtools is in the Plugins tab on the Preferences dialog, but it is marked as disabled. When I try to enable it, it fails to start as explained before.

One more thing I just tried - I deleted the tagtools files from the Plugins folder, opened Musicbee to ensure it was gone in the Plugins dialog, and then used the "Add plugin" button to reinstall from the ZIP I downloaded today. It re-added the mb_tagtools entry on the dialog, and then immediately failed in the same way when trying to enable it.

I'm not sure I can think of anything else to try.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 08, 2021, 06:32:13 PM
I'm not sure I can think of anything else to try.
Nor can I. Hopefully someone else will have an idea. Unfortunately the developer of this plugin has not been on the forum since last May.
Title: Re: Additional Tagging & Reporting Tools
Post by: frankz on April 08, 2021, 06:34:26 PM
Have you ever had it installed before?  Check your MusicBee3Settings.ini file for references to the plugin in locations other than the one it's in now.
Title: Re: Additional Tagging & Reporting Tools
Post by: cjoprey on April 08, 2021, 08:18:59 PM
Thanks @frankz - tried that and it looked OK, but it did show me that there is a file called "mb_TagTools.Settings.xml" in the AppData folder. Deleted that file,moved the entry for tagtools from the musicbee3settings.ini file, and deleted the mb_tagtools.dll in Plugins. Then restarted musicbee and re-added the plugin from the zip file and all is working again - I can only assume a corrupt XML file. Thanks all for the help, and I hope my solution can help others in future. :)
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on April 09, 2021, 02:38:56 PM
I'm trying to use this plugin to generate some cool stats from my music library but I'm failing at the first step!

When I load up the Library Reports and try to run one of the default built in presets I get this "No Files in Current View".

Are there any guides on how to make reports using this tool? I'd like to have some basic reports such as: most played songs; most played artists etc etc

Title: Re: Additional Tagging & Reporting Tools
Post by: frankz on April 09, 2021, 02:57:02 PM
Are there any guides on how to make reports using this tool? I'd like to have some basic reports such as: most played songs; most played artists etc etc
Have you read the aptly-named Readme (https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/)?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on April 09, 2021, 03:41:43 PM
Are there any guides on how to make reports using this tool? I'd like to have some basic reports such as: most played songs; most played artists etc etc
Have you read the aptly-named Readme (https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/)?

I did yeah, but it turns out the report wasn't running as I needed to select "All Artists" in "Music" first so it could run a report.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on April 22, 2021, 06:40:05 AM
Is there a way to remove featured artists from title when files are named "Artist1 - Songname (feat. Artist2)"? I seem to recall that the "Extract feat. artists..." used to do this earlier but now I can't find a way to remove it completely.
Title: Re: Additional Tagging & Reporting Tools
Post by: dankjankem on April 29, 2021, 02:32:59 AM
Ok so I opened up my MusicBee today and out of nowhere the Additional Tagging and Reporting Tools plugin is just not working or even showing up in the menu. If I go to the tools menu, Additional Tagging and Reporting Tools does not appear underneath "Tagging Tools" like it normally does. How do I fix this? I've lost all of my custom presets because of this :-/
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 29, 2021, 02:58:08 AM
Have you looked in the plugins directory to confirm that mb_TagTools.dll exists? If it doesn't try reinstalling the plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on April 29, 2021, 01:19:29 PM
Ok so I opened up my MusicBee today and out of nowhere the Additional Tagging and Reporting Tools plugin is just not working or even showing up in the menu. If I go to the tools menu, Additional Tagging and Reporting Tools does not appear underneath "Tagging Tools" like it normally does. How do I fix this? I've lost all of my custom presets because of this :-/

This has been oddly happening to me too lately. The plugin menu will not be there, then be there. I haven't attempted to reinstall yet.
Title: Re: Additional Tagging & Reporting Tools
Post by: dankjankem on April 29, 2021, 08:58:18 PM
Have you looked in the plugins directory to confirm that mb_TagTools.dll exists? If it doesn't try reinstalling the plugin.

I checked and it was no longer in the directory, but after reinstalling, it has already happened again. Hmmmmm
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 29, 2021, 09:29:48 PM
I checked and it was no longer in the directory, but after reinstalling, it has already happened again. Hmmmmm
Whitelist the entire MB directory in your AV/Security software.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bizy on July 02, 2021, 10:48:17 PM
I had the same problem:  'mb_TagTools.dll Exception has been thrown by the target of an invocation' (not possible to enable the plugin, tools invisible)
And the solution of Cjoprey did solve it!

Quote
there is a file called "mb_TagTools.Settings.xml" in the AppData folder. Deleted that file, moved the entry for tagtools from the musicbee3settings.ini file, and deleted the mb_tagtools.dll in Plugins. Then restarted musicbee and re-added the plugin from the zip file and all is working again

So thanks a lot @cjoprey!! :-D

b.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 06:18:20 PM
Edit: It seems like I misunderstood and Word Breaks don't force a capital, is it possible to add this feature (for example first letter after a bracket is always capitalised)?
capitalize all words in tag (untick exceptions), then tick exception back, change casing to "Title Case" and click "Reapply" button to apply new changed rule to "New tag value" column (NOT to original tag values) without saving tags to files. if you are satisfied with preview click "Proceed" button.

For ASR presets copy "title case" preset and change "replace by" field in step 2 from:

\@tc[[$1;;\@1]]

to:

\@tc[[\@uc[[$1;;]];;\@1]]

save this new preset.

I don't want to change behavior of "change case" command because of legacy code and the ability to achieve desired results in 2 steps anyway.

for exception symbols in ASR: i'll check this later.

EDIT: there is no \@uc function at the moment, but i'll add it.


maybe i'll change behavior for exception symbols. i need to think more what is the way to make it more clear and not to loose current functionality.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 06:37:36 PM
also, case changing asr presets included in plugin package don't use asr defaults for exception words (i've changed these presets to use explicit exception word list instead of defaults). if you want to use asr defaults from 'change case' command, copy preset and change "replace by" from, for example:

\@tc[[$1;;\@1]]

to:

\@tc[[$1]]

it's for 'title case' preset, the same change for other presets.

i'll remove "set asr defaults" for exception words from 'change case' command, but all other asr defaults from 'change case' command must work as expected. 
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 09, 2021, 06:40:04 PM
Ah!

Since you're back, what does ASR stand for?
I asked this on the forum a while back, and nobody knew the answer…
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 06:53:19 PM
Hi,
re this:
https://getmusicbee.com/forum/index.php?topic=3833.msg140371#msg140371

Does arithemtic operations work with Search & Replace ?

I'm attempting (on Tag1 = 160)
Step 1
Search for:
^(.*)
Replace with:
$Div($1,2)

Results in:
"$Div($1,2)"
not
80
which I was attempting for...

Where's my brainfart here... does S&R not work with the arithmetic operations...? or is my syntax messed...?
Churs.
c.
this won't work directly, but you can define virtual tag with any formula and use this virtual tag in asr.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 06:55:31 PM
Ah!

Since you're back, what does ASR stand for?
I asked this on the forum a while back, and nobody knew the answer…
ASR is "Advanced Search & Replace" (plugin command). MSR is "Multiple Search & Replace" (multi-step search & replace, another plugin command).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 09, 2021, 07:05:16 PM
ASR is "Advanced Search & Replace" (plugin command). MSR is "Multiple Search & Replace" (multi-step search & replace, another plugin command).
I'm sorry, I was confused.
(a bit tired and having a drink ;-)

I meant to say: what does TOY mean?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 07:17:47 PM
EDIT: Disregard.

For the last few days, I've been trying to use the plugin's $Len() function with the built-in $If() function and have been running into an issue.

Let's say $Len(<Composer>) is 8.
Code
$If($Len(<Composer>)=8,T,F)
$If($Len(<Composer>)>0,T,F)
$If($Len(<Composer>)>7,T,F)
...all should return "T," which they do.


Code
$If($Len(<Composer>)>9,T,F)
...correctly returns "F."


Code
$If($Len(<Composer>)>10,T,F)
...incorrectly returns "T." From then on, all numbers up to 79 return "T" when then they should be false. If I insert a leading zero ahead of $Len()...


Code
$If(0$Len(<Composer>)>79,T,F)
...I get the correct result "F."

Is $Len() is returning the number as a string?
it's strange. $Len() returns just number without leading zeros and it works fine for me. but $If(0$Len(<Composer>)>10,T,F) alway results in F in my case.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 07:33:11 PM
I meant to say: what does TOY mean?
it's for historical reasons. initially ASR had no auto-applying capability and some asr presets like "copy tag", "swap tags" seemed to be toys, because corresponding dedicated plugin commands were much more powerful. all these presets were created just for demonstration of ASR capabilities. now only "swap tags" asr preset is just a useless toy, while other "toy" resets may be useful.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 09, 2021, 07:39:33 PM
it's for historical reasons.
Ah! So it literally means toy.
Me (and everybody else) were searching for the meaning behind it as it being some acronym.
Just so you know, some brain-cells have been sacrificed because of this ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 07:52:12 PM
I think I have a bug with $Random? It keeps adding a prefix and suffix segment when I ask for a number.

If I do anything 2 or lower, it will print D0#5 (# being the random number)
If I do anything up to 30 it will print D1<number>5.
If I do anything up to 315 it will print D2<number>5.
etc.

So for example, if I do "$Random(100) and the value is 57, it will print "D2575"

What's going on here?
thanks for bug report. it' fixed. i'll upload fixed version later.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on July 09, 2021, 07:53:19 PM
it's for historical reasons.
Ah! So it literally means toy.
Me (and everybody else) were searching for the meaning behind it as it being some abbreviation.
Just so you know, some brain-cells have been sacrificed because of this ;-)
Thanks for ending the mystery boroda. I'm one of the "everybody else" who lost brain cells trying to figure out what T O Y meant.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 08:03:22 PM
it's for historical reasons.
Ah! So it literally means toy.
Me (and everybody else) were searching for the meaning behind it as it being some abbreviation.
Just so you know, some brain-cells have been sacrificed because of this ;-)

by the way, you are not the only guy who asked why these presets are named "toy" :) . i  want to change prefix for these presets (which duplicate other plugin commands) to something else, while keeping them together in preset list (presets are sorted alphabetically, that's why i need prefix). could you suggest something other than "toy: "?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 09, 2021, 08:05:48 PM
could you suggest something other than "toy: "?
I think I'd better leave that to native English speakers…?

edit
Who am I kidding, I have an opinion on everything ;-)
Maybe something like 'basic'?

Or an alternative starting with the letter 'a', so they are top of the list?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 08:49:58 PM
Would this plugin have the capability of combining two different play counts? I've spent time between foobar and iTunes and it's not looking good on finding a way to combine the two diff play count tags.

(https://i.imgur.com/5fobTlQ.png)

Edit: So I found this option here:

(https://i.imgur.com/2gcLQnp.png)

but this doesn't actually combine (add one into the other, 1+2=3) it just takes both of the tags and incorporates them into 1 tag. Would it be possible to get an option to do this?

edit: if anyone ever comes across this, you can use a program titled Mp3Tag to combine two different play counts.
you can use arithmetic functions in virtual tags.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2021, 09:16:13 PM
Let's hope he's OK...

On another bug note - I'm using the latest portable build of Musicbee (3.4.7764) and every time I try to enable the latest version of mb_tagtools  I get an error telling me: "Unable to initialise plugin: mb_TagTools.dll Exception has been thrown by the target of an invocation." - anyone know how to get round this and get the tools working again? I miss the support it gives!
i wish i could pin this advice on the topic: try to close mb, delete file <mb appdata folder>\mb_TagTools.Settings.xml and start mb again.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on July 10, 2021, 03:00:59 PM
i wish i could pin this advice on the topic: try to close mb, delete file <mb appdata folder>\mb_TagTools.Settings.xml and start mb again.

Me too.
That simple trick immediately fixed my months-long issue of the "Create" and "Edit" popups in the ASR window opening silently and the only way of closing them being SHIFT + ALT + F4.  ???

Another thing, is there a tutorial available somewhere for the Library Reports feature? I think I can use it to automatically rate albums based on the number of tracks (by taking the album <Track Count> divided by the number of <Love>d tracks), but I haven't been able to quite figure out how to use them.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 11, 2021, 10:37:06 AM
the only tutorial is readme on add-on page. i'm too lazy to write complete tutorial, but i'm ready to help you here.

i think you need the opposite to what you wrote. grouping fields must be <album artist>,<album>,<loved> and calculated field must be 'average count(<loved>/<url>)'. save 'average count' to custom tag (or assign virtual tag function id) only if <loved>='L'
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 11, 2021, 10:44:14 AM
new version of plugin is available:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

* fixed $Random() function
* 'change case' command now has no button for setting asr default excepted words, because asr presets anyway use explicit list of excepted words.
* 'TOY: *' presets are renamed to 'Example: *' presets. also, i've changed their descriptions. import new presets after installing new plugin version. 'TOY: Swap tags' preset is removed from plugin package (because it's completely useless), but you need to manually delete it (it won't be automatically deleted on importing new presets).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 12, 2021, 08:25:01 PM
new plugin version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

now ASR presets can calculate any expression valid for virtual tag without creation of virtual tag. see preset "Example: Write result of virtual tag expression defined in <Custom text 1> to <Tag 2>".

you will need mb latest patch to use new plugin version:

https://getmusicbee.com/patches/MusicBee34_Patched.zip
Title: advanced search and replace - move featured artist(s) from title to Artist tag
Post by: spon on July 15, 2021, 12:33:40 AM
Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!
Title: Re: advanced search and replace - move featured artist(s) from title to Artist tag
Post by: phred on July 15, 2021, 02:35:44 AM
I have moved this to the Additional Tagging & Reporting Tools plugin thread so the developer of the plugin can see it.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 15, 2021, 04:16:29 PM
Could the 'new tag value' get some easier to read contrast?:

(https://i.imgur.com/4BIs6bY.png)

you will need mb latest patch to use new plugin version:
https://getmusicbee.com/patches/MusicBee34_Patched.zip
Perhaps it would be good to specify the minimum version needed?
(something like 3.4.7866 I think?)
Users reading this in a year's time that are already using a fairly recent version could get the impression they will still need to do an update again.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on July 15, 2021, 07:12:25 PM
Could the 'new tag value' get some easier to read contrast?:
+1
What I've done when using ATRT on only one track, which is rare, is select two tracks and place the highlight line on the -other- track. That enables me to preview the new value. Yeah, I know, but it works. I guess I've been too lazy to ask for a change to this.
Title: Re: Additional Tagging & Reporting Tools
Post by: spon on July 17, 2021, 06:15:25 PM
Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

Hope it's ok that I bumped this message. I've been playing around with modifying the scripts and just can't quite figure out what I'm doing.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on July 19, 2021, 12:31:09 PM
Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

Do you not have the ASR preset available that would assist in this?

the only tutorial is readme on add-on page. i'm too lazy to write complete tutorial, but i'm ready to help you here.

i think you need the opposite to what you wrote. grouping fields must be <album artist>,<album>,<loved> and calculated field must be 'average count(<loved>/<url>)'. save 'average count' to custom tag (or assign virtual tag function id) only if <loved>='L'

Thanks for the assist. Unfortunately, I'm having some trouble interpreting the numbers.
For example, I have an album with four loved tracks and nineteen total tracks.
If I include <Loved> in the GROUPING, I get two rows of the album, one showing .07 (1/15) and the other .25 (1/4). The interpretation of this is 1 album divided by 15 tracks (not <Loved>) and 1 album divided by 4 tracks (<Loved>).
If I don't include <Loved> in the GROUPING, I get one row, but the number .11. I'm not sure how this one is calculated.

EDIT: How can I process the Report so that the combined track count per album (for example, 19) divided by the <Loved> track count per album (for example, 4)?
Title: Re: Additional Tagging & Reporting Tools
Post by: spon on July 19, 2021, 05:42:02 PM
Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

Do you not have the ASR preset available that would assist in this?



Hi, thanks for the response. I have played around with the presets but haven't been able to modify them in a way to get the desired outcome. The closest I've gotten is using the "Extract featuring artists from track time and add them to the "Artist" tag. This will copy the featured artists and put them in the Artist tag, but I have a few things I'd like to change about the result and can't figure out how.

1. Remove the featured artist from the title rather than copy them
2. Have it work if there are ( ) around the featured artists or not. Right now it requires parenthesis to work
3. Move the featured artists to the Display Artist tag, including having feat. before the artists

I know I'm close, but each time I try different modifications to the code, it seems to get worse. lol.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on July 20, 2021, 01:58:13 PM
Hi, thanks for the response. I have played around with the presets but haven't been able to modify them in a way to get the desired outcome. The closest I've gotten is using the "Extract featuring artists from track time and add them to the "Artist" tag. This will copy the featured artists and put them in the Artist tag, but I have a few things I'd like to change about the result and can't figure out how.

1. Remove the featured artist from the title rather than copy them
2. Have it work if there are ( ) around the featured artists or not. Right now it requires parenthesis to work
3. Move the featured artists to the Display Artist tag, including having feat. before the artists

I know I'm close, but each time I try different modifications to the code, it seems to get worse. lol.

I've never used the ASR tool for this purpose, so you'll likely have to tweak the below.

Code
Step 1
Search: \sfeat\.\s([\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist

Step 2
Search: \,|\&|and in tag: Artist
Replace: ; in tag: Artist

Step 3
Search: (\sfeat\.\s[\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist (displayed)

Step 4
Search: \sfeat\.\s([\s\S]*?$) in tag: Title
Replace: (leave blank) in tag: Title
Title: Re: Additional Tagging & Reporting Tools
Post by: archetypewriter on July 20, 2021, 04:52:36 PM
Hi,
I'm having a really hard time getting this plugin to install. I've tried several times, always hitting the same issue. After putting the unzipped folder into the MusicBee plugins folder, I start the program. TagTools shows up in the preferences menu, but isn't enabled. When I hit enable I get this error message:
Unable to initialise plugin: mb_TagTools.dll
Exception has been thrown by the target of an invocation.

Twice, I uninstalled and deleted files from AppData before attempting another install. No luck

Any help would be greatly appreciated. Cheers
Title: Re: Additional Tagging & Reporting Tools
Post by: archetypewriter on July 20, 2021, 11:43:38 PM
Never mind. I tried one last time and it finally worked without issue. No idea what the problem would have been. Cheers!
Title: Re: Additional Tagging & Reporting Tools
Post by: spon on July 22, 2021, 05:15:37 AM

I've never used the ASR tool for this purpose, so you'll likely have to tweak the below.

Code
Step 1
Search: \sfeat\.\s([\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist

Step 2
Search: \,|\&|and in tag: Artist
Replace: ; in tag: Artist

Step 3
Search: (\sfeat\.\s[\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist (displayed)

Step 4
Search: \sfeat\.\s([\s\S]*?$) in tag: Title
Replace: (leave blank) in tag: Title

Thanks for posting this! It does correctly remove the "feat. Artist A" from the title. Unfortunately the resulting Artist fields now show the original artist and then the entire song title afterwards.

Is there any sort of guide on the coding language? I'm trying to back my way into understanding but it's been tough.
Title: Re: Additional Tagging & Reporting Tools
Post by: ketchupman36 on July 25, 2021, 05:28:20 AM
Hello, I'm trying out ASR for the first time but maybe I'm missing something completely.  I want to find tracks with a certain phrase in their title and then add a track number to that track.

(https://i.imgur.com/gJ9MzZK.png)

This doesn't seem to work.  Am I just way off here?  Is there any easier way to accomplish this?

Title: Additional Tagging plugin - Changing display artist field for last.fm scrobbles?
Post by: sgarciaesteban on August 21, 2021, 04:13:13 PM
I already made a post in this board but I did not specify the plugin with which I suppose this process could be automated, that's why I suppose the topic was moved to the questions board.

My idea is to split the artists with a "Seach & Replace" searching for commas in the artist field and replacing it with semicolons to have the artists separated since now I have them with a comma (for example "Gunna, Playboi Carti"). But the problem is I don't know how to automate the process of changing the display artist field to make it only the first artist, that is, only "Gunna". This way I have read in other posts that last.fm will read the display artist which will be "Gunna" and will not read "Gunna, Playboi Carti".

Is there a way to automate this process with the Additional Tagging & Reporting plugin?

I hope someone can help me, thanks!
Title: Re: Additional Tagging & Reporting Tools
Post by: sgarciaesteban on August 21, 2021, 10:46:52 PM
My idea is to split the artists with a "Seach & Replace" searching for commas in the artist field and replacing it with semicolons to have the artists separated since now I have them with a comma (for example "Gunna, Playboi Carti"). But the problem is I don't know how to automate the process of changing the display artist field to make it only the first artist, that is, only "Gunna". This way I have read in other posts that last.fm will read the display artist which will be "Gunna" and will not read "Gunna, Playboi Carti".

Is there a way to automate this process with the Additional Tagging & Reporting plugin?

I hope someone can help me, thanks!
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on August 22, 2021, 02:23:03 PM
Thanks for posting this! It does correctly remove the "feat. Artist A" from the title. Unfortunately the resulting Artist fields now show the original artist and then the entire song title afterwards.

Is there any sort of guide on the coding language? I'm trying to back my way into understanding but it's been tough.

I never responded to this - sorry!
If you haven't already figured it out, the AT&T plugin uses regular expressions to manipulate text.
Try this in Step 1 and Step 3.

Code
Step 1
Search: ^[\s\S]*?\sfeat\.\s([\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist

Step 3
Search: ^[\s\S]*?(\sfeat\.\s[\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist (displayed)

Hello, I'm trying out ASR for the first time but maybe I'm missing something completely.  I want to find tracks with a certain phrase in their title and then add a track number to that track.

...

This doesn't seem to work.  Am I just way off here?  Is there any easier way to accomplish this?

I think you need to move to "replace with:" part in Step 2 to Step 1.

My idea is to split the artists with a "Seach & Replace" searching for commas in the artist field and replacing it with semicolons to have the artists separated since now I have them with a comma (for example "Gunna, Playboi Carti"). But the problem is I don't know how to automate the process of changing the display artist field to make it only the first artist, that is, only "Gunna". This way I have read in other posts that last.fm will read the display artist which will be "Gunna" and will not read "Gunna, Playboi Carti".

Is there a way to automate this process with the Additional Tagging & Reporting plugin?

Try this.

Code
Step 1
Search: \, in tag: Artist
Replace: ; in tag: Artist

Step 2
Search: \,[\s\S]*$ in tag: Artist (displayed)
Replace:  (leave blank) in tag: Artist (displayed)
Title: Re: Additional Tagging & Reporting Tools
Post by: VadimBerkut on August 25, 2021, 01:52:29 PM
Autorating process takes too long (about 3 hours). Is that normal? My music collection is about 26k songs in FLAC, and it storages on external hard drive as well as my portable Musicbee. I chose Rating tag as basic in plugin preferences and unticked store ratings in music files function in Musicbee itself. What could be wrong?
Title: Re: Additional Tagging & Reporting Tools
Post by: sgarciaesteban on August 26, 2021, 12:17:24 AM

Try this.

Code
Step 1
Search: \, in tag: Artist
Replace: ; in tag: Artist

Step 2
Search: \,[\s\S]*$ in tag: Artist (displayed)
Replace:  (leave blank) in tag: Artist (displayed)

I have managed to do step 1 with the normal musicbee search & replace. But for step 2, I have no experience of Advanced Search & Replace and have tried this in various ways but got nothing. What I want is for the program to take the first ARTIST field (since there are now two fields, an ARTIST field for each artist) and copy it into the DISPLAY ARTIST field. Thank you
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on August 29, 2021, 04:59:38 AM

I have managed to do step 1 with the normal musicbee search & replace. But for step 2, I have no experience of Advanced Search & Replace and have tried this in various ways but got nothing. What I want is for the program to take the first ARTIST field (since there are now two fields, an ARTIST field for each artist) and copy it into the DISPLAY ARTIST field. Thank you

Can you provide an exact example of how your tags (use the Tag Inspector) and how you want them to look?
Didn't multiple artists already exist in the <Artist (displayed> tag?

Quote
...since now I have them with a comma (for example "Gunna, Playboi Carti")
Title: Re: Additional Tagging & Reporting Tools
Post by: jan_axhell on September 16, 2021, 02:31:29 PM
Hello, I'm getting Out of Memory Exception when I try to Backup tags for all tracks.
I have 32 Gb of RAM and about 22% is being used when this happens.
The process starts, then between 30-40 % it halts giving error.
Code
16/09/2021 19:22:34 - 10.0.19043.0 - 3.4.7805.33439D - System.OutOfMemoryException: Generata eccezione di tipo 'System.OutOfMemoryException'.
   in System.Collections.Generic.SortedSet`1.AddIfNotPresent(T item)
   in System.Collections.Generic.TreeSet`1.AddIfNotPresent(T item)
   in System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
   in MusicBeePlugin.BackupType.setValue(String valueParam, Int32 trackId, Int32 tagId)
   in MusicBeePlugin.BackupIndex.saveBackup(String backupName, String statusbarText, Boolean isAutocreatedParam)
   in MusicBeePlugin.BackupIndex.saveBackupAsync(Object parameters)
   in #=zlFwaJ1S_oYR_8J8laA==.#=zyNO4kjvnVZVY6HOBVD_9GiRtxZo6os9OGA==(Object #=zK7i1NeE=)

(https://images4.imagebam.com/a5/f7/5d/ME3MGQC_o.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: SonicRings on October 25, 2021, 11:45:45 AM
Can you help me in calculating the total duration based on track length and play count? (Track duration x play count)

I'm not sure how to do this. Tried this so far but this doesn't work: $AddDuration(<Play Count>,<Time>)

I want it to show 0:00 (or nothing) when the play count is 0, since, well, no time was spent listening to the song.

As well, I want it to show the sum of the time listened to all highlighted tracks, so if I highlight an album of 100 minutes where I've listened to every track 10 times, for example, it will show 1000 minutes time listened.

I made a post about it here https://getmusicbee.com/forum/index.php?topic=35695.msg195187#msg195187 but it might be better asking here.
Title: Re: Additional Tagging & Reporting Tools
Post by: SonicRings on October 26, 2021, 09:37:46 AM
Another question: is it possible to add a newline/line break to a tag? And if so, how?
Title: Copy Tag not working
Post by: khordy on October 27, 2021, 02:18:55 PM
Hello,

I've been exploring the Additional Taggint Tools but have not been able to copy between tags. For my test I'm trying to copy the content of "Custom13" tag to "Custom14". When using the "copy tag" functionality I set both tags as origin and destination of the copy. When I press the "Preview" button everything seems to work fine and "New tag value" is updated with the value in "Custom13" as shown in the following image.

(https://i.imgur.com/Q1CQJwv.jpg)

But when I push the "Proceed" button nothing happens. There is no error message or any other indication, but the copy is not performed and the "Custom14" tag is not update with the value of "Custom13".
I have tried to do the same with the "Advanced Search & Replace" function, which also has a perset for copying between tags, but the result is the same, no action is performed.

Does anybody know if I'm doing something wrong? The function seems very straightforward and easy to understand, but you never know...

Thanks in advance.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 27, 2021, 05:25:33 PM
I've been exploring the Additional Taggint Tools but have not been able to copy between tags.
Have you been using the plugin before on other functions that do work o.k.?
What file format are the files in question? Anything special about them?
Are these custom tags written to the files or to MB's database?

What MB version and type of install?

My only explanation for now for this rather straightforward function not working would be some corruption in the plugin installation.
Perhaps remove it, rescan your library, and try a clean install?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on October 27, 2021, 07:11:24 PM
Are these custom tags written to the files or to MB's database?
My guess is that this is the issue. From what I can tell, a lot of people creating custom tags don't understand the difference between saving to MB's database and re-purposing an unused tag.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 27, 2021, 07:36:10 PM
My guess is that this is the issue. From what I can tell, a lot of people creating custom tags don't understand the difference between saving to MB's database and re-purposing an unused tag.
Still, surely both should work fine here?
I only asked the question to possibly narrow down what the issue could be here.
Title: Re: Additional Tagging & Reporting Tools
Post by: frankz on October 27, 2021, 07:40:58 PM
I'm not in front of it right now, but isn't there another button like "save all" or "save and close" that you have to click?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on October 27, 2021, 07:44:36 PM
I'm not in front of it right now, but isn't there another button like "save all" or "save and close" that you have to click?
The tags are written in real-time. The "save all" and "save all and close" buttons save the AS&R settings that may have been changed during the session. For instance - it saves the column width of the preview window. Or the AS&R window location on the desktop. At least that's been my experience.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on October 27, 2021, 07:46:21 PM
Still, surely both should work fine here?
I only asked the question to possibly narrow down what the issue could be here.
I'm not sure. I never use the "save to mb's database" for custom tags. But it seemed like a good possibility as to a cause.
Title: Re: Additional Tagging & Reporting Tools
Post by: khordy on October 28, 2021, 01:34:27 PM
   Thanks everyone for the answers.

   The problem finally got solved after playing around the "Uninstall", "Enable", "Disable" options of the plugin. I'm not sure which was the specific action which solved the problem as I pushed all the options for the plugin repeatedly. Probably disabling and enabling the plugin did the work. Everything works fine now!

   Thanks again.

Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 02, 2021, 06:38:08 PM
Hi

I'd like to copy everything before (or after) a certain character to another tag, using only a single step. Would this be possible to do via Multiple S&R? This title could serve as an example:

Concerto no. 4 in E major, RV 263a∶ II. Largo

I'd like to copy everything before the ":" to the <set subtitle>. As of now, I use the Copy Tags, and then the ATRT command "remove after...", but I'd like to everything in a single step if possible.

All help much appreciated!
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on November 04, 2021, 02:16:39 AM
Hi

I'd like to copy everything before (or after) a certain character to another tag, using only a single step. Would this be possible to do via Multiple S&R? This title could serve as an example:

Concerto no. 4 in E major, RV 263a∶ II. Largo

I'd like to copy everything before the ":" to the <set subtitle>. As of now, I use the Copy Tags, and then the ATRT command "remove after...", but I'd like to everything in a single step if possible.

All help much appreciated!

I've never even clicked on the option until now.
But, it doesn't seem so.
You have to use the Advanced Search & Replace.
An expression you could use in the "Search for:" input box is...
Code
^(.+):[\s\S]*?$
...and "Replace with:"
Code
$1

Then, in Step 2, put...
Code
^[\s\S]*?:\s
...into the first input box and leave the second one blank.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 09, 2021, 08:40:10 PM
You have to use the Advanced Search & Replace.
An expression you could use in the "Search for:" input box is...
Code
^(.+):[\s\S]*?$
...and "Replace with:"
Code
$1

Then, in Step 2, put...
Code
^[\s\S]*?:\s
...into the first input box and leave the second one blank.

Thanks Boom Boom for helping out!
Sorry though, but I can't figure out how to get it to work. Here's how I entered everything:

(https://imgur.com/coq2RTV.png)

but then when I use the preset, it can't find any files. I haven't used the advanced search and replace before (quite obviously...), so I'd appreciate any nudge in the right direction regarding what I'm doing wrong.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on November 09, 2021, 11:30:38 PM
but then when I use the preset, it can't find any files. I haven't used the advanced search and replace before (quite obviously...), so I'd appreciate any nudge in the right direction regarding what I'm doing wrong.

You need to set the tags you want to manipulate using the dropdown forms on the right side of the pop-up window.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 10, 2021, 12:33:18 AM
but then when I use the preset, it can't find any files.
First select the files to be changed > then open AS&R  > select the preset > preview (to make sure it doing what you want) > apply > save.

DO NOT check the box next to the preset as that will AUTOMATICALLY apply the present to everything in your library.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 10, 2021, 10:53:25 AM
You need to set the tags you want to manipulate using the dropdown forms on the right side of the pop-up window.
First select the files to be changed > then open AS&R  > select the preset > preview (to make sure it doing what you want) > apply > save.
DO NOT check the box next to the preset as that will AUTOMATICALLY apply the present to everything in your library.
Sorry, I still can't get it to work. In the Preset Editor, I'm guessing that I should set <Tag 1> to writable? And should I change "corresponds to" from <Null> to something else? Further, I guess I don't need <Tag 2>, nor <Custom text 1>? I do have a file selected, but when I click Preview, it's empty.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 10, 2021, 01:16:56 PM
I do have a file selected, but when I click Preview, it's empty.
If you're not seeing anything in the preview, and you have file(s) selected, that means nothing in the selection meets the criteria of the preset's 'search' entry.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 10, 2021, 02:19:39 PM
If you're not seeing anything in the preview, and you have file(s) selected, that means nothing in the selection meets the criteria of the preset's 'search' entry.
Ok, so here's a file that I'm trying to use the preset on:
(https://imgur.com/OVXXHyD.png)

I've entered the following in the editor:
(https://imgur.com/PuRMoxj.png)

But when I use it like this:
(https://imgur.com/wFFuauS.png)

I get nothing.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 10, 2021, 02:32:21 PM
I get nothing.
Correct.

As BoomBoom said in Reply #2419:
You need to set the tags you want to manipulate using the dropdown forms on the right side of the pop-up window.
Right now they're showing as <Temp 1> when they should be the tag you're looking to change.
In Step 1, change the line "Search for" from <Temp 1> to <Tag 1>.
And in the line "Replace with" from  <Temp 1> to <Tag 2>.

I think you don't need what you have in Step 2 as you've got search criteria but you don't have a replace with criteria.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 10, 2021, 04:06:24 PM
Sorry, I still can't get it to work. In the Preset Editor, I'm guessing that I should set <Tag 1> to writable? And should I change "corresponds to" from <Null> to something else? Further, I guess I don't need <Tag 2>, nor <Custom text 1>? I do have a file selected, but when I click Preview, it's empty.

I believe The Incredible Boom Boom's solution should be applied like this:

(https://i.imgur.com/yly0MxF.png)
 
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 10, 2021, 05:35:59 PM
I think you don't need what you have in Step 2 as you've got search criteria but you don't have a replace with criteria.
The blank line in 2 makes it so that what matches the regex in line 1 gets blanked.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 10, 2021, 07:20:42 PM
The blank line in 2 makes it so that what matches the regex in line 1 gets blanked.
Thanks for the clarification.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 10, 2021, 07:21:15 PM
I believe The Incredible Boom Boom's solution should be applied like this:
(https://i.imgur.com/yly0MxF.png)
 
[/quote]
And whatabout the area above this, the "<Tag 1> is Not used/Writable/Readable corresponds to ..."? I'm trying using both nothing, or filling in writable and then e.g. <Title>. Thanks for helping out you too Hiccup, as you can see, I'm way in over my head :)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 10, 2021, 07:35:47 PM
And whatabout the area above this, the "<Tag 1> is Not used/Writable/Readable corresponds to ..."? I'm trying using both nothing, or filling in writable and then e.g. <Title>. Thanks for helping out you too Hiccup, as you can see, I'm way in over my head :)
I have it set to 'not used', which will grey out all other fields in that top panel.
Be aware that the brilliant mind that created this plugin is not a native-English speaker, so 'not used' should probably not be taken literally.
I am guessing it means something along the lines of 'leave as is'.
(somebody with a deeper and better understanding of this plugin: please correct me if I am wrong. I am also a non-native English speaker)
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 10, 2021, 07:53:34 PM
@The Incredible Boom Boom, @phred and @hiccup, thanks for helping out! It turns out the reason I couldn't get it to work wasn't all me being stupid. Instead, it turns out that the file I tried to use had a different colon sign (in ascii I guess?). When I copy-pasted the colon from your suggestion Boom Boom, it worked perfectly fine!
That adds another aspect - how would I go about to be able to fill in the breaking character in <custom text 1> instead?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 10, 2021, 08:21:53 PM
Instead, it turns out that the file I tried to use had a different colon sign (in ascii I guess?)
Far as I know the colon is identical between utf8 and ascii, so I am guessing something else was going on.
Anyway, great that you have it working now.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on November 10, 2021, 09:33:15 PM
Far as I know the colon is identical between utf8 and ascii, so I am guessing something else was going on.
Anyway, great that you have it working now.

Strange, right? This is the colon from Boom Boom followed by the one from the file. Obviously different, but I assume they're both are just alternate versions of the colon and not different characters

∶ :

In any way, perhaps it would be better to have a preset where one could enter the breaking character in <custom text>?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 10, 2021, 09:43:29 PM
Strange, right? This is the colon from Boom Boom followed by the one from the file. Obviously different, but I assume they're both are just alternate versions of the colon and not different characters
∶ :
Interesting indeed.
One of them seems to be the symbol/character for 'ratio'.
I never knew that.
It shouldn't be hard to edit the regex to catch both.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 10, 2021, 10:16:29 PM
Glad to hear you've got it all figured out. You put your Sherlock Holmes hat to good use.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on November 10, 2021, 11:05:34 PM
Strange, right? This is the colon from Boom Boom followed by the one from the file. Obviously different, but I assume they're both are just alternate versions of the colon and not different characters

∶ :

In any way, perhaps it would be better to have a preset where one could enter the breaking character in <custom text>?

It is hella annoying when you discover non-standard characters are used in tags. The most annoying one is some dash that MusicBrainz Picard always wants to insert in place of the normal one, because they are visually identical.

As for the Custom Text option, we'll have to wait for @boroda to clarify, as I have no idea how to use that option. 😅
Title: Re: Additional Tagging & Reporting Tools
Post by: DQ on November 13, 2021, 12:00:37 PM
Can the ASR tool search for the occurrence of one tag within another?
Example: Can I use it to look if the value in the 'Artist' field also exists in the 'Album artist' field?
I can't find an example doing this in the presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 13, 2021, 12:34:44 PM
I don't know if AT&RT can do this by itself.
But as a guess:
Virtual tags can do this, so perhaps it's possible to configure a virtual tag to do the matching part, and then let AT&RT write an actual (or custom) tag using that virtual tag as a source?
Title: Re: Additional Tagging & Reporting Tools
Post by: DQ on November 13, 2021, 01:12:26 PM
Hello Hiccup
I was actually trying to do it the other way around because I can't get my virtual tag to work as I want. So I was hoping the use the $ASR function as a workaround
Basically I want to remove the name of the album artist in the album field.
But when I do $RxReplace(<Album>,<Album Artist>,"DQ") it inserts 'DQ' between every two characters. So it matches an empty string. (and the name of the artist isn't removed)
It looks like this is the same problem I encountered before where it was not possible to use a function or tag as second or third parameter for other functions.
If you have any suggestion...
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 13, 2021, 01:19:15 PM
It looks like this is the same problem I encountered before where it was not possible to use a function or tag as second or third parameter for other functions.
If you have any suggestion...
You are talking about this I guess?:
https://getmusicbee.com/forum/index.php?topic=35639.0

I have no solution for that. We can only hope that Steven sees a purpose in this and grants the wish someday.
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on November 13, 2021, 01:40:48 PM
Basically I want to remove the name of the album artist in the album field...
But when I do $RxReplace(<Album>,<Album Artist>,"DQ")...
Do you mind providing an example of one of the album names you would like changed?
If I'm getting this right, you want the album name Encore [Eminem] to change to Encore [DQ]? Is that right?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 13, 2021, 02:22:46 PM
If I'm getting this right, you want the album name Encore [Eminem] to change to Encore [DQ]? Is that right?
In this thread it is described what DQ is aiming to achieve:
https://getmusicbee.com/forum/index.php?topic=35629.0
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on November 13, 2021, 03:45:27 PM
But when I do $RxReplace(<Album>,<Album Artist>,"DQ") it inserts 'DQ' between every two characters.
Back here, are you supposed to be using $RxReplace or $Replace?
I don't think $RxReplace is being used correctly there.
Those two are different functions (even though they achieve the same thing, they work differently).

Edit: Did more testing and apparently, $RxReplace should still work, even with the same input as that of $Replace.

$RxReplace(<Album>, abc, DQ) produces the same result as $Replace(<Album>, abc, DQ)
$RxReplace(<Album>,<Album Artist>, DQ) does not produce the same result as $Replace(<Album>,<Album Artist>, DQ)

I now understand what you mean by this:
It looks like this is the same problem I encountered before where it was not possible to use a function or tag as second or third parameter for other functions.
Title: Re: Additional Tagging & Reporting Tools
Post by: DQ on November 13, 2021, 04:01:50 PM
Hello Mayibongwe
Something like that (but without the DQ, that was only to make it more visible)
Basically I want to remove the artists name from the title regardless of where it appears.
Some samples: (sorry for the misalignement, I used colors to make it more readible)

Album - Album artist = Desired result
African Chill - African Chill
Joe Cocker - Greatest hits Joe Cocker Greatest hits
The best of ABBA ABBA The best of
Best Elvis Presley Music Ever Elvis Presley Best Music Ever
Bob Dylan's Greatest Hits Bob Dylan Greatest Hits
Ultimate Prince Prince Ultimate
Klara - Muziek voor de 4 elementen - Klara - Muziek voor de 4 elementen
Wagner - Meesterlijke melodieën Wagner Meesterlijke melodieën

(I use a hyphen as 'Album artist' to flag compilations as otherwise MusicBee replaces it with the 'Artist')

I found a solution by first replacing the artist name with a fixed text and then use that in the RxReplace.
I have to use RxReplace because I also need to remove trailing or preceding spaces, hyphens or 's
So I came up with
$RxReplace($Replace(<Album title>,$Split(<Album Artist>,",",1),DQ),"(( - )?DQ( - | |’s)?)","")
(The reason I split the <Album artist>  is because 'Wagner' is actually 'Wagner, Richard')
This is actually part of a larger expression to group my albums in the albums & tracks view
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on November 13, 2021, 04:39:25 PM
$RxReplace($Replace(<Album title>,$Split(<Album Artist>,",",1),DQ),"(( - )?DQ( - | |’s)?)","")
Does that work well? I'm getting a fail at "lbum title>,$Split(<Album Artist>,",",1),DQ),"(( - )?DQ( - | |’s)?)","")"

Edit: I see it now. I should be using <album> in place of <album title>.
Title: Re: Additional Tagging & Reporting Tools
Post by: DQ on November 14, 2021, 10:59:54 AM
Yes, 'Album title' is another virtual tag.
Thanks for helping out.
Title: Re: Additional Tagging & Reporting Tools
Post by: voodoopunk on December 06, 2021, 01:02:18 PM
Hi All,

Is it possible to change the role/instrument in Performer to lower case using the additional tagging and reporting tools, just the text that ends up in parentheses. I've had a look at the 'change case' function and that doesn't appear to do what I'm after. I have looked at the advanced search and replace but the regex is beyond me.

TIA,
Voodoo
Title: Backup Musicbee \ tag backups \ baseline is corrupted
Post by: djdalex on December 21, 2021, 08:47:00 PM
https://imgur.com/a/mZbApxp

Can this be solved easily? Got a 1TB + library

The XML document contains a fault (6348261,_8)

MusicBee v3.4.7805.33439D  (Win10.0), 21 dec 2021 21:39:

System.NullReferenceException: De objectverwijzing is niet op een exemplaar van een object ingesteld.
   bij MusicBeePlugin.BackupType.save(String fileName)
   bij MusicBeePlugin.BackupIndex.saveBackup(String backupName, String statusbarText, Boolean isAutocreatedParam)
   bij MusicBeePlugin.Plugin.regularAutobackup(Object state)
   bij System.Threading.TimerQueueTimer.CallCallbackInContext(Object state)
   bij System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   bij System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   bij System.Threading.TimerQueueTimer.CallCallback()
   bij System.Threading.TimerQueueTimer.Fire()
   bij System.Threading.TimerQueue.FireNextTimers()
   bij System.Threading.TimerQueue.AppDomainTimerCallback(Int32 id)
Title: Re: Backup Musicbee \ tag backups \ baseline is corrupted
Post by: The Incredible Boom Boom on December 22, 2021, 05:11:33 PM
What are you trying to accomplish?
You can't use the Tag Backup option in the AT&T plugin unless you create a baseline XML first.
Title: Re: Backup Musicbee \ tag backups \ baseline is corrupted
Post by: djdalex on December 22, 2021, 06:44:00 PM
It made a lot of backups the last months. A while ago it start giving this fault.
For now i disabled (auto) backup settings in the Additional Tagging Tools menu.
Problem still not solved. Same fault message!
Title: Re: Backup Musicbee \ tag backups \ baseline is corrupted
Post by: The Incredible Boom Boom on December 23, 2021, 01:21:44 PM
It made a lot of backups the last months. A while ago it start giving this fault.
For now i disabled (auto) backup settings in the Additional Tagging Tools menu.
Problem still not solved. Same fault message!

Why would you expect a different message?
It's quite clear that somehow your backup baseline file is either not in its supposed location, or corrupted somehow.
If it's a matter of the file having been moved, you need to move it back to its original location.
If it's corrupted, maybe you can delete the previous backup and try again? Else, there's not much you can do besides recreating the baseline file.

EDIT: This thread should be moved to the AT&T plugin thread, moderators.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on February 03, 2022, 12:08:06 PM
I'd love some help on how to swap parts of a tag  :)

I have about 150 Mazurkas by Chopin, with the <work> like this:

Mazurka in A minor, Op. 7, No. 2

However, by this, they will list according to key, and not opus which is what I'd like. Is there anyway, perhaps using regexp, to get the above example to

Mazurka Op. 7 No. 2 in A minor

Whatever happens to commas etc is fine, I can search and replace later. Is this possible? The different files will of course have different keys and opus numbers :/ I found the Swap command but I don't think it'll be able to do this, at least not from what I've tried so far.

Any help appreciated!
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on February 04, 2022, 12:56:06 AM
I'd love some help on how to swap parts of a tag  :)

I have about 150 Mazurkas by Chopin, with the <work> like this:

Mazurka in A minor, Op. 7, No. 2

However, by this, they will list according to key, and not opus which is what I'd like. Is there anyway, perhaps using regexp, to get the above example to

Mazurka Op. 7 No. 2 in A minor

Whatever happens to commas etc is fine, I can search and replace later. Is this possible? The different files will of course have different keys and opus numbers :/ I found the Swap command but I don't think it'll be able to do this, at least not from what I've tried so far.

Any help appreciated!

Regex for moving relatively fixed text around is quite simple to learn.
In fact, you could do what you're needing with just opening and closing parentheses, a period and the plus symbol.
Wrapping a phrase with parentheses means you're grabbing that phrase to place elsewhere. The period means "match any character." And the plus symbol stands for "continue matching whatever the previous character is."

Here is an expression (https://regex101.com/r/P4oUsL/1) that solves your request, but I would advise taking the time to look at it and attempt to understand how the text substitution is accomplished. This way, instead of waiting assistance in the future, you can throw something together yourself (and then ask for assistance if you get stuck.)
Title: Re: Additional Tagging & Reporting Tools
Post by: anywaysayhi on February 04, 2022, 04:10:56 AM
In Change Case I couldn't manage to realize the following examples:

T'Aggio → t'Aggio

(https://i.imgur.com/mYaMhyK.png)

No matter what I have tried, it didn't change at all. Same as L'Amour → l'Amour didn't work either.
I have put t in the exception list, and ' in the word splitter list. Any idea?
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on February 04, 2022, 07:43:21 AM
Regex for moving relatively fixed text around is quite simple to learn.
In fact, you could do what you're needing with just opening and closing parentheses, a period and the plus symbol.
Wrapping a phrase with parentheses means you're grabbing that phrase to place elsewhere. The period means "match any character." And the plus symbol stands for "continue matching whatever the previous character is."

Here is an expression (https://regex101.com/r/P4oUsL/1) that solves your request, but I would advise taking the time to look at it and attempt to understand how the text substitution is accomplished. This way, instead of waiting assistance in the future, you can throw something together yourself (and then ask for assistance if you get stuck.)


What a fantastic answer - kind, helpful and educational at the same time! I'll have a look and start trying out future ideas by myself first. Top of the line respone @The Incredible Boom Boom!
Title: Re: Additional Tagging & Reporting Tools
Post by: anywaysayhi on February 05, 2022, 12:57:53 PM
In Change Case I couldn't manage to realize the following examples:

T'Aggio → t'Aggio

(https://i.imgur.com/mYaMhyK.png)

No matter what I have tried, it didn't change at all. Same as L'Amour → l'Amour didn't work either.
I have put t in the exception list, and ' in the word splitter list. Any idea?

OK so I just manually change them since there are not a lot of them
But I am wondering to achieve this in advanced search and replace. However I couldn't figure out what to use in regular expressions for setting upper case or lower case in "replace" field. The only guide for case change in this forum is not clear with the regular expressions.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on February 05, 2022, 03:51:44 PM
What a fantastic answer - kind, helpful and educational at the same time! I'll have a look and start trying out future ideas by myself first. Top of the line respone @The Incredible Boom Boom!

No problem. Hope you get it sorted.


OK so I just manually change them since there are not a lot of them
But I am wondering to achieve this in advanced search and replace. However I couldn't figure out what to use in regular expressions for setting upper case or lower case in "replace" field. The only guide for case change in this forum is not clear with the regular expressions.

Unfortunately, it doesn't look like MB supports case conversion replacement with regular expressions, so you'd either have to use another tool, like MP3TAG, or search for all tracks matching the regex \s\w\'\w+ and then use the built-in Search and Replace tool and go through each letter.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 05, 2022, 09:30:08 PM
In Change Case I couldn't manage to realize the following examples:

T'Aggio → t'Aggio

No matter what I have tried, it didn't change at all. Same as L'Amour → l'Amour didn't work either.
I have put t in the exception list, and ' in the word splitter list. Any idea?

I'm neither Italian nor French, but are you sure that the word after the apostrophe from your examples indeed should be in upper case to begin with?
(I have some doubts about that)
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on February 10, 2022, 10:01:11 AM
Windows 10 just did some upgrade, and after reboot, my AT&RT can't be started. Re-downloaded thje latest version and put it in the folder but it does not help. If I go into preferences>plugins, it's there, but when I click Configure, I get the following error:

Code
MusicBee v3.4.8033.18564D  (Win10.0), 10 feb 2022 10:57:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zMnhegC3cZoGqJc9MnQ==.#=zHNzzNWE=(IntPtr #=zznrCYSH69sZI)

Any idea of what I could do?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 10, 2022, 02:32:45 PM
Make sure your presets are in the correct directory. They belong in \AppData\ASR Presets. They do not belong in the plugin directory
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on February 10, 2022, 02:35:35 PM
Make sure your presets are in the correct directory. They belong in \AppData\ASR Presets. They do not belong in the plugin directory
Thank you, will move them!
Title: Re: Additional Tagging & Reporting Tools
Post by: PlumBlossom on February 16, 2022, 07:59:08 PM
Hello~
I see that the developer hasn't been on it a while but I was hoping I could get some help. I've got the plugin install just for the ability to save the play count as a tag. I had it working perfectly last night following the guide written up by Redwing so that the ASR preset would update the tag as the song played and added to the play count. When I was done, I closed musicbee and shut down my computer like I normally do. Now when I startup musicbee the plugin isn't found where I have it set (in the tools menu) and it isn't there when I right click on a track. When I go to configure it I get this error:

MusicBee v3.4.8033.18564D  (Win10.0), 16 Feb 2022 14:53:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zMnhegC3cZoGqJc9MnQ==.#=zHNzzNWE=(IntPtr #=zznrCYSH69sZI)

I don't know what any of this means or how I get it because I haven't messed with anything. So I uninstalled and reinstalled the plugin through musicbee and it showed up again in the tools menu. But now saving the play count doesn't work and update the play count as it goes anymore  :'( The play count that's stored in musicbee's database will go up but the tag I created won't so I have two different play counts now
I don't understand what went wrong because I had it working before. And the error happens every time I close musicbee. What should I do?

EDIT
Okay, so it seems I got it back working again (though I'm not really sure how by just closing musicbee, deleting the plugin from the plugin folder and simply moving it back before restarting musicbee). But the error still occurs when I close musicbee and restart it, making me have to fumble around again to (hopefully) fix it. I can't just leave it running so how do I avoid this?
Title: Re: Additional Tagging & Reporting Tools
Post by: psychoadept on February 16, 2022, 08:55:22 PM
It's not the same message, but have you tried the solution here: https://getmusicbee.com/forum/index.php?topic=35245.0
Title: Re: Additional Tagging & Reporting Tools
Post by: PlumBlossom on February 25, 2022, 12:49:41 AM
Sorry for the late reply. But yeah I gave that a try and it still happens. My app has been crashing a lot lately too with an "out of memory" error so it's making it extra difficult to fix
Title: Re: Additional Tagging & Reporting Tools
Post by: Steven on February 25, 2022, 01:08:59 AM
try updating to v3.5 from psychoadept's signature which might help with the plugin initialisation error
Title: Re: Additional Tagging & Reporting Tools
Post by: PlumBlossom on February 25, 2022, 01:51:06 AM
I've updated to 3.5 and it does seem to have fixed the initialisation error when I tested it with a few restarts! But I've noticed that the plugin doesn't stay where I configure it (in the tools/additional tools' menu although it does appear when I left click. I'm not sure if that's more of a tic with the plugin itself than musicbee though. Thank you!
Title: Re: Additional Tagging & Reporting Tools
Post by: Steven on February 25, 2022, 02:24:13 AM
the initialisation error would have been because the plugin will be installed in 2 locations (user/appdata/musicbee/plugins and programfiles/musicbee/plugins, each installation with its own settings
while v3.5 ensures only 1 installation is loaded, any settings you previously had might have been from the duplicate installation
Title: Re: Additional Tagging & Reporting Tools
Post by: PlumBlossom on February 25, 2022, 02:37:09 AM
Ah I understand! Thank you very much! Everything seems to be working properly now I think. Would 3.5 also address the memory error as well? (I have the editbin patch but when I ran it the command prompt box appeared and quickly disappeared again)
Title: Re: Additional Tagging & Reporting Tools
Post by: anywaysayhi on February 26, 2022, 04:23:28 PM

OK so I just manually change them since there are not a lot of them
But I am wondering to achieve this in advanced search and replace. However I couldn't figure out what to use in regular expressions for setting upper case or lower case in "replace" field. The only guide for case change in this forum is not clear with the regular expressions.

Unfortunately, it doesn't look like MB supports case conversion replacement with regular expressions, so you'd either have to use another tool, like MP3TAG, or search for all tracks matching the regex \s\w\'\w+ and then use the built-in Search and Replace tool and go through each letter.

Thank you. I used MP3Tag action to solve this problem. Thank you so much.
Title: Re: Additional Tagging & Reporting Tools
Post by: anywaysayhi on February 26, 2022, 04:29:58 PM
In Change Case I couldn't manage to realize the following examples:

T'Aggio → t'Aggio

No matter what I have tried, it didn't change at all. Same as L'Amour → l'Amour didn't work either.
I have put t in the exception list, and ' in the word splitter list. Any idea?

I'm neither Italian nor French, but are you sure that the word after the apostrophe from your examples indeed should be in upper case to begin with?
(I have some doubts about that)

I think Yes. Basically the articles (il la) should be in lowercase while the nouns in uppercase, hence l'Amore. But i've also seen L'Amore and L'amore somewhere, so probably depends on personal choices without criterion.
Title: Re: Additional Tagging & Reporting Tools
Post by: PlumBlossom on February 27, 2022, 02:26:00 AM
I'm not sure what happened but I got this error again after starting up musicbee and trying to congfigure the plugin since it wasn't showing up in the tools menu or when I left click my files. It only fixes when I uninstall the plugin from within musicbee (not file explorer) and add it back within musicbee. But then there's the issue of having to set up the plugin all over again

MusicBee v3.5.8089.36178D  (Win10.0), 26 Feb 2022 21:15:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zaI7vUK8z9CS_YU7ohQ==.#=zba0oQ50=(IntPtr #=zL7gKgw_yhOzK)
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 07, 2022, 02:42:33 PM
Is there a way of getting ATRT to be able to edit Instruments: Performer and similar tags?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on March 07, 2022, 02:45:48 PM
Is there a way of getting ATRT to be able to edit Instruments: Performer and similar tags?
I think the only one who could implement that would be boroda, the plugin's developer. And unfortunately he hasn't been active on the forum for a number of months.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 07, 2022, 02:46:51 PM
Ok, thanks phred!
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on March 07, 2022, 05:26:33 PM
Is there a way of getting ATRT to be able to edit Instruments: Performer and similar tags?
'Instruments: Performer' is a virtual tag used by MusicBee for displaying purposes.
If you edit 'Artists: Performer', the results should be reflected in 'Instruments: Performer'.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 07, 2022, 07:09:21 PM
'Instruments: Performer' is a virtual tag used by MusicBee for displaying purposes.
If you edit 'Artists: Performer', the results should be reflected in 'Instruments: Performer'.

Ok, so blatantly showing my incompetence here, it seems to me that only some presets can write to e.g. Artist: Performer? Actually, doing a quick test, the only preset I found that could write to the virtual tags was the Example: Write result of virtual tag expression defined in <Custom text 1> to <Tag 2>. In the rest, these are simply not showing up in the dropdown menu. Probably doing something wrong, but what? :)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on March 07, 2022, 07:54:21 PM
…the only preset I found that could write to the virtual tags was the Example: Write result of virtual tag expression defined in <Custom text 1> to <Tag 2>. In the rest, these are simply not showing up in the dropdown menu. Probably doing something wrong, but what? :)
Presets are there to make some common operations available, but more importantly, they have the purpose to be an example and can be used as a template (copy them) to create a preset that does specifically what you want.
So you would either need to learn how to create such a preset yourself, or ask others to help you with it.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 07, 2022, 08:00:23 PM
Presets are there to make some common operations available, but more importantly, they have the purpose to be an example and can be used as a template (copy them) to create a preset that does specifically what you want.
So you would either need to learn how to create such a preset yourself, or ask others to help you with it.
Absolutely, I'm with you on this. However, if I reformulate my question, how come that some presets (on my setup, only Example: Write result of virtual tag expression defined in <Custom text 1> to <Tag 2>) list all virtual tags in the <tag 1> drop-down, while all others don't? For example, I'm trying to use your recent preset for adding values to tags, but Artist:Performer simply isn't there.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on March 07, 2022, 08:05:51 PM
I'm sorry, my computer says she's tired.
I'm sure other members can provide some suggestions. Else I'll take a look in a few days.
Title: Re: Additional Tagging & Reporting Tools
Post by: Johan_A_M on March 07, 2022, 08:07:28 PM
I'm sorry, my computer says she's tired.
I'm sure other members can provide some suggestions. Else I'll take a look in a few days.
Let her sleep  :-*
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on March 08, 2022, 05:10:06 PM
If you look at the tags of a file using the Tag Inspector you will see that the tags that contain the values you are looking for are TMCL for id3v2, and 'performer' for vorbis comments.
It also shows the correct formatting. (the use of delimiters and brackets)
So these are the tags that AT&RT would need to write to.

(https://i.imgur.com/c1SYc8O.png)

edit:

Taking a second, and a better look at this, I am guessing that if AT&RT could do this, you would just need to select 'Artists: Performer' and the plugin would take care of correct formatting for both id3v2 and vorbis.

I never tried to do this myself (I am using Picard to write these tags and have no need to make alterations afterwards), but giving it a better look I am now not so sure this can be done.
While AT&RT seems to know these performers tags and can read them, I don't see them being available to write to.

Hopefully somebody with a deeper knowledge of AT&RT can chip in.
The best would be boroda himself, but as phred mentioned earlier, he has been absent from the forum for a long time, and also hasn't responded to pm's.
Let's hope he is well.
Title: Re: Additional Tagging & Reporting Tools
Post by: anywaysayhi on March 09, 2022, 03:48:59 PM
(https://i.imgur.com/zsT08hU.png)

I wanted to use Library Report to show play counts of each artist (not only displayed artist but every artist in the <Artists>), just like the playcounts shown under artist picture in music explorer of musicbee. However, as shown in the screenshot above, it fails to seperate each artist in <Artists>. What am I supposed to change to achieve it?

I want to generate a report in the form of:
Artist Playcount
Alice Sara Ott 150
Franz Liszt 100
Maurice Ravel 10
Munchner Philharmoniker 10
Title: Re: Additional Tagging & Reporting Tools
Post by: frankz on March 09, 2022, 05:31:51 PM
I think you want "Artists" there or one of the variations. Experiment to see which one gives the results you want.

EDIT: I just tried it on mine an Artists: Artist seems to give the results you want.
Title: Re: Additional Tagging & Reporting Tools
Post by: anywaysayhi on March 09, 2022, 05:57:26 PM
I think you want "Artists" there or one of the variations. Experiment to see which one gives the results you want.

EDIT: I just tried it on mine an Artists: Artist seems to give the results you want.

Thank for your advice but seems like neither "Aritists" nor "Artists: Artist" achieves it. Here is the screeshot of "Artists: Artist"
(https://i.imgur.com/6GlCKOL.png)

Here is how I tag <Artists> one example:
(https://i.imgur.com/sgByKvT.png)

I am still trying to figure it out.
Title: Re: Additional Tagging & Reporting Tools
Post by: barlet on April 16, 2022, 04:57:19 PM
This error was created this morning. Up till yesterday, everything was fine
MusicBee v3.5.8135.36838P  (Win10.0), 15 Apr 2022 14:20:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zlzGadM3B9bXeaXFUig==.#=zENO5D_Q=(IntPtr #=zBcSYWJaalro8)

I found out the culprit behind this error:

If one enables Quick Tagger by A100X, it will interfere with Additional Tag Tools by boroda.Tthe additional tag tools would not load and would produce the error posted above.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on April 25, 2022, 01:28:53 PM
Just updated to 3.5beta and AT&RT vanished. Clicking "configure" gives

MusicBee v3.5.8146.38239D  (Win10.0), 25 Apr 2022 8:21:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zFATgFjBdBS9YrWXGWg==.#=zhhGt68w=(IntPtr #=zTJWEEq3dlH_v)

Tried disabling all other plugins (last.fm (already disabled, don't use), cd art display (already disabled, don't use), lyrics reloaded, media control, taskbar tidbits, theater mode) and restarting but still no AT&RT and same error message. Tried complete uninstall (clicked uninstall, closed MB, deleted AT&RT files from plugin folder) and reinstall. Works until I restart MB and then vanishes and gives same error.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 25, 2022, 01:54:22 PM
Are you certain that you have AT&RT installed in the proper directories?
The dll needs to be in \MusicBee\Plugins
The entire ASR Presets directory needs to be in \MusicBee\AppData.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on April 25, 2022, 03:48:48 PM
Are you certain that you have AT&RT installed in the proper directories?
The dll needs to be in \MusicBee\Plugins
The entire ASR Presets directory needs to be in \MusicBee\AppData.

Yes I believe so. Per plugin's homepage install directions
Quote
Installation and Usage

Extract content of archive to plugins sub-folder of MusicBee installation folder (e.g. to "C:\Program Files (x86)\MusicBee\Plugins"). See "Tools> Tagging Tools" menu. To configure plugin go to "Edit> Preferences> Plugins".

Then, under "Advanced Search and Replace" click "Import All". Looked in C:\Users\XXXXX\AppData\Roaming\MusicBee and ASR Presets is there.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on April 25, 2022, 03:53:46 PM
Just updated to 3.5beta and AT&RT vanished.
Are you using the latest version of the plugin?
(mine shows 5.2.7865, I think it is from around nov/dec last year)
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on April 25, 2022, 04:16:47 PM
Just updated to 3.5beta and AT&RT vanished.
Are you using the latest version of the plugin?
(mine shows 5.2.7865, I think it is from around nov/dec last year)

Downloaded from plugin homepage "mb_TagTools_2021-07-11.zip"
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on April 25, 2022, 04:36:36 PM
Downloaded from plugin homepage "mb_TagTools_2021-07-11.zip"
It's a bit confusing to me what is the latest version and when it was released.

Here: https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/
it says: "Updated on November 20, 2021, 5:55 am"
But if you download it from there, you indeed get one that is dated July 11th 2021.

If you download it from forum post #2386, you get one dated July 14th 2021, so slightly newer.

Anyway, I don't think your issue would be related to using one of those versions.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on April 26, 2022, 01:13:00 PM
Updated MB to 3.5.8150 and AT&RT to 5.2.7865 but still disappears after restart.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 26, 2022, 01:35:37 PM
Updated MB to 3.5.8150 and AT&RT to 5.2.7865 but still disappears after restart.
Unfortunately you may have to wait for boroda (plugin developer) to take a look at this. Even more unfortunately, boroda hasn't been on the forum for quite some time. 
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on April 26, 2022, 05:24:05 PM
Unfortunately you may have to wait for boroda (plugin developer) to take a look at this. Even more unfortunately, boroda hasn't been on the forum for quite some time.  

Looked at boroda's profile, says he's in Moscow, so I guess I'm SOL.
Title: Re: Additional Tagging & Reporting Tools
Post by: Dalinar on April 27, 2022, 09:09:56 AM
is there any documentation for this thing aside from the readme? I haven't read this thread as it is quite long.

also the readme hints that tags can be applied when new files are added to the inbox, does anyone know how to configure that?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 27, 2022, 12:54:51 PM
is there any documentation for this thing aside from the readme? I haven't read this thread as it is quite long.
What you see is what you get.

Quote
also the readme hints that tags can be applied when new files are added to the inbox, does anyone know how to configure that?
If you tick the box for a preset, it gets automatically applied.
Title: Re: Additional Tagging & Reporting Tools
Post by: Dalinar on April 28, 2022, 11:30:38 AM
Quote
also the readme hints that tags can be applied when new files are added to the inbox, does anyone know how to configure that?
If you tick the box for a preset, it gets automatically applied.
[/quote]

so there is no way to apply it just to inbox files? the docs says something about applying to the inbox and files that are modified also.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 28, 2022, 01:07:41 PM
so there is no way to apply it just to inbox files?
Not that I have found.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on April 30, 2022, 02:59:14 PM
Hm, I know that Boroda74 hasn't been around for a wee while (hope all is OK!).
But maybe else has encountered this:
For 3+ years I've had a (for me complicated) regex script Boroda helped me with.
Now, after upgrading to Musicbee 3.5 an issue that occassionally occured (i.e. in dozens to 100s of uses per month, it occurred once every 3-6 months but always had me stumped, and always was on a very few files - with no pattern I have noticed...), and this has now become a constant after updating.

So what the 'script' is meant to do:
- it's based on one of the default combine scripts
- it's meant to take the rating (star) value [with half-stars] as numerical [not the actual numerical rating value - which it always just worked, regardless of the format - since id3 & vorbis have different absolute rating values, I assumed this was some magic musicbee api bit inbetween that was converting this correctly...]
- then, take a numeric value from a second [custom] field (call 'Energy' that could have values from 0 -10)
- then combine the 2 with a ' - ' inbetween and write them to 2 other fields (so '10 - 5' would be the resulting tag value for a 5 star rated track, with an Energy value of 10...)

What it now does:
- the energy value gets always written correctly still
As for the weird bits:
- the star value now gets written as:
   - sometimes the numerical value (only on flac files, I have not seen this happen on id3 tags, so a vorbis rating of 60 for a 3 star track, 20 for a 1 star track, etc pp)
   - sometimes the rating value gets written as 1 (regardless of the actual rating / star value)
- on top, IF the rating value gets written as 1, the [custom text 1] ' - ' always gets written twice [minus a ' '...], resulting in '10 - - 1' [instead of '10 - 5']

So, in the above example track [with 10 & 5 respectively] I may end up with '10 - - 1' or,  ' 10 - 100'
I'm a tad lost there.

If anyone spots anything off here - and feels like helping - I would love to fix this up again....
I'll add a screenshot of both ASR Windows as well:
--------------------------------------------
(https://i.imgur.com/xQWWn39.png)

--------------------------------------------

Also - could it be that with MB 3.5 there's something that changed, and therefore ASR Scripts would need to be adjusted ?
Did anyone encounter issues with old ASR presets after switching to 3.5 ?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 30, 2022, 03:50:40 PM
Did anyone encounter issues with old ASR presets after switching to 3.5 ?
While I'm sorry that I can't help with the issue you're experiencing, I can say with certainty that all the original presets, and the few custom ones that I created, are working as expected with 3.5.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on April 30, 2022, 04:18:21 PM
While I'm sorry that I can't help with the issue you're experiencing, I can say with certainly that all the original presets, and the few custom ones that I created, are working as expected with 3.5.
Thanks for the feedback! I only tested a few, but couldn't produce any issues either... makes it all the more odd why it would suddenly break completely...
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on April 30, 2022, 10:32:10 PM
While I'm sorry that I can't help with the issue you're experiencing, I can say with certainly that all the original presets, and the few custom ones that I created, are working as expected with 3.5.
Could you do me a favour and test the default ASR combine script (i.e. "Combine tags '<Tag 1>', '<Tag 2>' placing between them <Custom text 1> and write result in '<Tag 3>'.") with a mixture of rated tracks, and set <Tag 1> as from 'Rating' [ideally on a mix of formats as well (but, multiples of the same - as I even see mixed behaviour on tracks from the very same album... and flac/vorbis seems to be the culprit here... )] and then do a preview in ASR window.

Do you then:
- see a consistent number for 'Rating' equal to the 'stars' shown for the rating ?
- or a consistent number equal to the numeric value of the rating tag field [0, 10, 20, etc for vorbis, 0, 32, 64, etc for id3] ?
- or a mixture ?

 For me mp3/id3 are consistent still & working as before, i.e. the queried rating value then is 1, 1.5, 2, 2.5 [= the 'star' rating...], etc not the numeric value i.e. 0, 32, 64, etc in the ASR preview...
But for .flac/vorbis files, I get a mixture of numeric values [0, 10, 20, etc for vorbis], as well as only '-1' (no matter the actual rating, either in 'stars' or numeric values) in the result from ASR - even with the default combine script... [and turns out Boroda helped with another one... my version is pretty much just a copy of the default 2 value combine, writing to 2 fields...]

Cheers.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on April 30, 2022, 11:07:10 PM
Could you do me a favour and test the default ASR combine script (i.e. "Combine tags '<Tag 1>', '<Tag 2>' placing between them <Custom text 1> and write result in '<Tag 3>'.") with a mixture of rated tracks, and set <Tag 1> as from 'Rating' [ideally on a mix of formats as well (but, multiples of the same - as I even see mixed behaviour on tracks from the very same album... and flac/vorbis seems to be the culprit here... )] and then do a preview in ASR window.
Sorry, but I do not rate my tracks. Nor do I have any flac tracks.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on May 01, 2022, 09:52:57 AM
Sorry, but I do not rate my tracks. Nor do I have any flac tracks.
Thanks & no worries!
If anyone else could have a try to see if this is repeatable behaviour, that would be awesome, just to see if this is a general issue or a local one...
Cheers.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on May 02, 2022, 12:48:55 AM
Thanks & no worries!
If anyone else could have a try to see if this is repeatable behaviour, that would be awesome, just to see if this is a general issue or a local one...
Cheers.
c.

@alec.tron
Tried that preset combining ratings with a few different number fields and had no problems.
Also couldn't see any differences between your regex fields and what I'm using straight from ATRT
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on May 02, 2022, 01:36:50 PM
Tried that preset combining ratings with a few different number fields and had no problems.
Also couldn't see any differences between your regex fields and what I'm using straight from ATRT
Thanks a lot for double checking!!
Just to confirm - this was with .flac files as well, correct ?
Cheers.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on May 03, 2022, 07:28:08 AM
Just to confirm - this was with .flac files as well, correct ?
flac, mp3 and ogg and various combinations of them.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on May 03, 2022, 07:50:24 PM
flac, mp3 and ogg and various combinations of them.
Thanks muchly for testing. (which Advanced Tag & Reporting Tool version are you using, out of curiousity ? Not 100% certain if I am on the latest version Boroda published... and that could be a last option to try - as that's so odd that I get a random mix of absolute as well as properly parsed (star count) values from rating fields.)

Churs.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on May 04, 2022, 08:29:48 AM
Not 100% certain if I am on the latest version Boroda published...
Not certain it's the latest one either but I'm using 5.2.7863
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on May 04, 2022, 12:53:04 PM
Not certain it's the latest one either but I'm using 5.2.7863
Same one in use here. I assume it is the latest boroda published.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on May 04, 2022, 04:40:33 PM
Not 100% certain if I am on the latest version Boroda published...
Not certain it's the latest one either but I'm using 5.2.7863
I believe the most recent version is 5.2.7865
https://getmusicbee.com/forum/index.php?topic=3833.msg199916#msg199916
Title: Trying to backup my tags and get a system out of memory exception
Post by: Phaedrus on May 15, 2022, 05:32:04 AM
I've been having trouble backing up my tags for a while, but I just had a bit of a scare and feel like I need to fix it. I get this message when I try to backup my tags; (My current signature has been updated to reflect my current setup.) I can't believe my library is too big. In my search I didn't see anything specific to my issue.

5/14/2022 11:56:54 PM - 10.0.22000.0 - 3.4.8033.18564D - System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
  at System.Text.StringBuilder..ctor(String value, Int32 startIndex, Int32 length, Int32 capacity)

I have been unable to run a full backup for quite some time, but this is my current status. I was trying to clean up my file structure, and ran into an issue where MuscBee wouldn't start at all. I may not have a fully standard setup, but damned if I know what's really different. I restored an older version of my ini file and I don't see any lost information. I fully admit that I may have caused most of these issues on my own trying to customize file locations, but damned if I can remember doing anything out of the ordinary.

I'm sure I've done something odd but for the life of me, I can't figure out what. Any pointer on where to look are most appreciated. Am I just hitting raw system limitations? I've been looking for an excuse to upgrade, but I am hoping to limp along for at least a few more months so I can buy at least second gen new OS. Thanks, y'all rock!
Title: Re: Trying to backup my tags and get a system out of memory exception
Post by: phred on May 15, 2022, 01:16:19 PM
How are you doing the backup?
Title: Re: Trying to backup my tags and get a system out of memory exception
Post by: Phaedrus on May 15, 2022, 02:14:23 PM
I would have sworn I put that in there. I'm using the "Additional Tagging Tools" Backup and restore. I'm trying to create a new baseline.

I was a bit panicked because I could not find my database files. Turns out my Database files are in the Windows "Music" special folder, which maps to C:\Users\<Me>\Music. I now have that backed up to my OneDrive using "MusicBee/File/Library/Backup Library."
Title: Re: Trying to backup my tags and get a system out of memory exception
Post by: phred on May 15, 2022, 02:38:50 PM
I'm using the "Additional Tagging Tools" Backup and restore. I'm trying to create a new baseline.
Thanks. I've never been happy with using AT&RT's backup function. Despite every else that boroda has done with that plugin, the back was always sketchy in its performance. I admit that I haven't tried it in years, so if I have some time later today, I'll test it.

Are you certain the plugin is installed properly?
Has it every worked for you?
Do you use the other functions of the plugin?

Boroda hasn't been on the forum in quite some time, but I'm going to merge this with the AT&RT thread to increase the chances that others who may use its backup function can jump in with suggestions.

Title: Re: Additional Tagging & Reporting Tools
Post by: Phaedrus on May 15, 2022, 11:15:07 PM
I use additional tagging tools so much that I forget that it's a plugin and not part of MusicBee. In fact, I was close to ditching MusicBee until I found it. The stuff that works is <Chef's Kiss>. To answer the questions;

I'm never certain about anything, so I removed and reinstalled the latest version.
I think my most recent successful backup was in the beginning of 2021, so it worked at one time.
I use the other features of Advanced tagging constantly. Especially "Advanced Find and Replace," "Reports," and "copy / Paste tags."

I was poking around and created a temporary library to test with. That one worked perfectly. I must be running into a limit based on my library size. It would explain why it worked just fine for a while; my library continues to grow.
Title: Re: Additional Tagging & Reporting Tools
Post by: AisSora on May 28, 2022, 01:12:48 AM
Greetings everyone,

So I'm quite new to MB, or rather new to tagging and actually taking care of my library  :P
I have artists in the artist field separated by a column ( ; ) and I noticed that a bunch of my album artist tags being empty; I know of the existence of the copy tag functionality, however, I would like it to be where I only copy the first artist as the album artist, I've looked for a bit for an answer on this, but I couldn't find one, probably due to my lack of knowledge on mb and this plugin.

So for the wizards in the forum, is this possible? and if so, please let me know how ^^

Edit:

I was able to do it through a custom preset:
https://ibb.co/2j1XwQW (https://ibb.co/2j1XwQW)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 05:40:49 PM
Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

redownload plugin, import new presets, find "Extract featuring artists from track title and add them to the (Guest) 'Artist' tag - 'Title <Custom text 1> <Artist1> <Custom text 2> <Artist2>' format" preset.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 06:11:45 PM
save 'average count' to custom tag (or assign virtual tag function id) only if <loved>='L'

Thanks for the assist. Unfortunately, I'm having some trouble interpreting the numbers.
For example, I have an album with four loved tracks and nineteen total tracks.
If I include <Loved> in the GROUPING, I get two rows of the album, one showing .07 (1/15) and the other .25 (1/4). The interpretation of this is 1 album divided by 15 tracks (not <Loved>) and 1 album divided by 4 tracks (<Loved>).
If I don't include <Loved> in the GROUPING, I get one row, but the number .11. I'm not sure how this one is calculated.

EDIT: How can I process the Report so that the combined track count per album (for example, 19) divided by the <Loved> track count per album (for example, 4)?
[/quote]

you missed this my note:
save 'average count' to custom tag (or assign virtual tag function id) only if <loved>='L'
and *include* loved in grouping.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 06:15:58 PM
Hello, I'm trying out ASR for the first time but maybe I'm missing something completely.  I want to find tracks with a certain phrase in their title and then add a track number to that track.

(https://i.imgur.com/gJ9MzZK.png)

This doesn't seem to work.  Am I just way off here?  Is there any easier way to accomplish this?


you better try mb native search & replace or plugins multiple search & replace. asr wont help you in this case.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 06:20:15 PM
I already made a post in this board but I did not specify the plugin with which I suppose this process could be automated, that's why I suppose the topic was moved to the questions board.

My idea is to split the artists with a "Seach & Replace" searching for commas in the artist field and replacing it with semicolons to have the artists separated since now I have them with a comma (for example "Gunna, Playboi Carti"). But the problem is I don't know how to automate the process of changing the display artist field to make it only the first artist, that is, only "Gunna". This way I have read in other posts that last.fm will read the display artist which will be "Gunna" and will not read "Gunna, Playboi Carti".

Is there a way to automate this process with the Additional Tagging & Reporting plugin?

I hope someone can help me, thanks!
step 1: search for , replace by ; for tag artist
step 2: search for ^(.*?),.* in artist tag replace by $1 for display artist tag
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 06:32:49 PM
Hello, I'm getting Out of Memory Exception when I try to Backup tags for all tracks.
I have 32 Gb of RAM and about 22% is being used when this happens.
The process starts, then between 30-40 % it halts giving error.
Code
16/09/2021 19:22:34 - 10.0.19043.0 - 3.4.7805.33439D - System.OutOfMemoryException: Generata eccezione di tipo 'System.OutOfMemoryException'.
   in System.Collections.Generic.SortedSet`1.AddIfNotPresent(T item)
   in System.Collections.Generic.TreeSet`1.AddIfNotPresent(T item)
   in System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
   in MusicBeePlugin.BackupType.setValue(String valueParam, Int32 trackId, Int32 tagId)
   in MusicBeePlugin.BackupIndex.saveBackup(String backupName, String statusbarText, Boolean isAutocreatedParam)
   in MusicBeePlugin.BackupIndex.saveBackupAsync(Object parameters)
   in #=zlFwaJ1S_oYR_8J8laA==.#=zyNO4kjvnVZVY6HOBVD_9GiRtxZo6os9OGA==(Object #=zK7i1NeE=)

(https://images4.imagebam.com/a5/f7/5d/ME3MGQC_o.jpg)
try not to back up artworks
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 06:53:03 PM
Can you help me in calculating the total duration based on track length and play count? (Track duration x play count)

I'm not sure how to do this. Tried this so far but this doesn't work: $AddDuration(<Play Count>,<Time>)

I want it to show 0:00 (or nothing) when the play count is 0, since, well, no time was spent listening to the song.

As well, I want it to show the sum of the time listened to all highlighted tracks, so if I highlight an album of 100 minutes where I've listened to every track 10 times, for example, it will show 1000 minutes time listened.

I made a post about it here https://getmusicbee.com/forum/index.php?topic=35695.msg195187#msg195187 but it might be better asking here.
redownload latest plugin version, use formula: $MulDuration(<Time>,<Play Count>)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 07:08:43 PM
Hi

I'd like to copy everything before (or after) a certain character to another tag, using only a single step. Would this be possible to do via Multiple S&R? This title could serve as an example:

Concerto no. 4 in E major, RV 263a∶ II. Largo

I'd like to copy everything before the ":" to the <set subtitle>. As of now, I use the Copy Tags, and then the ATRT command "remove after...", but I'd like to everything in a single step if possible.

All help much appreciated!
try multiple search & replace, you can achieve this in 2 steps.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 07:39:16 PM
In Change Case I couldn't manage to realize the following examples:

T'Aggio → t'Aggio

(https://i.imgur.com/mYaMhyK.png)

No matter what I have tried, it didn't change at all. Same as L'Amour → l'Amour didn't work either.
I have put t in the exception list, and ' in the word splitter list. Any idea?
untick "or only words" option
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 07:51:27 PM
But I am wondering to achieve this in advanced search and replace. However I couldn't figure out what to use in regular expressions for setting upper case or lower case in "replace" field. The only guide for case change in this forum is not clear with the regular expressions.
redownload latest plugin version, use "$Capitalize(string)" or "$UpperCase(string)" or "$LowerCase(string)" in virtual tag or ASR preset. 
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 08:09:18 PM
Is there a way of getting ATRT to be able to edit Instruments: Performer and similar tags?
use in search pattern .*(\0\u0002.*) to find performer(s) in artist tag and plugin's functions \@null[[]]\@char[[2]] in replace pattern to write performer(s) in artist tag.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 08:14:20 PM
Is there a way of getting ATRT to be able to edit Instruments: Performer and similar tags?
'Instruments: Performer' is a virtual tag used by MusicBee for displaying purposes.
If you edit 'Artists: Performer', the results should be reflected in 'Instruments: Performer'.
not at all. mb api uses string for artists where individual artists are separated by U+0000 char and performers names start with U+0002 char.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 08:25:49 PM
Presets are there to make some common operations available, but more importantly, they have the purpose to be an example and can be used as a template (copy them) to create a preset that does specifically what you want.
So you would either need to learn how to create such a preset yourself, or ask others to help you with it.
Absolutely, I'm with you on this. However, if I reformulate my question, how come that some presets (on my setup, only Example: Write result of virtual tag expression defined in <Custom text 1> to <Tag 2>) list all virtual tags in the <tag 1> drop-down, while all others don't? For example, I'm trying to use your recent preset for adding values to tags, but Artist:Performer simply isn't there.
Artist:Performer is some kind of virtual tag, so it's read-only. to *write* Artist:Performer to Artist tag add \@null[[]]\@char[[3]] to the beginning of performer name (if you use ASR).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 07, 2022, 08:47:36 PM
I use additional tagging tools so much that I forget that it's a plugin and not part of MusicBee. In fact, I was close to ditching MusicBee until I found it. The stuff that works is <Chef's Kiss>. To answer the questions;

I'm never certain about anything, so I removed and reinstalled the latest version.
I think my most recent successful backup was in the beginning of 2021, so it worked at one time.
I use the other features of Advanced tagging constantly. Especially "Advanced Find and Replace," "Reports," and "copy / Paste tags."

I was poking around and created a temporary library to test with. That one worked perfectly. I must be running into a limit based on my library size. It would explain why it worked just fine for a while; my library continues to grow.
try to disable backing up artworks, probably one or several tracks have corrupted artworks. corrupted artworks very frequently cause 'out of memory' errors (in .net in general, not only in at&rt plugin).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 10, 2022, 03:28:38 PM
use "$Capitalize(string)" or "$UpperCase(string)" or "$LowerCase(string)" in virtual tag or ASR preset.
1.
$Upper and $Lower are already available by default in MusicBee.
Are these two new ones doing something different?

2.
$Capitalise is doing 'sentence case', correct?
Not 'word case'.
Perhaps it would be good to have both options available.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 10, 2022, 09:27:38 PM
1.
$Upper and $Lower are already available by default in MusicBee.
Are these two new ones doing something different?
i'll remove $UpperCase(string) or $LowerCase(string) functions from plugin.

2.
$Capitalise is doing 'sentence case', correct?
Not 'word case'.
Perhaps it would be good to have both options available.
sentence case.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 10, 2022, 09:36:28 PM
2 new virtual tag functions are added: $SentenceCase(string) and TitleCase(string)

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Error when invoking Advanced Tagging Tools
Post by: barlet on June 12, 2022, 05:58:52 PM
The following error was thrown today when invoking Advanced Tagging Tools;

MusicBee v3.5.8167.33754P  (Win10.0), 12 Jun 2022 18:55:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zoKrwgApZgrpBSGsmYQ==.#=zJ9TUB2A=(IntPtr #=zPAzIZva3ahh8)
Title: Re: Error when invoking Advanced Tagging Tools
Post by: phred on June 12, 2022, 07:02:21 PM
The following error was thrown today when invoking Advanced Tagging Tools;
Searching the forum before posting is always a good idea.
As is posting bug reports in the plugin's thread.
https://getmusicbee.com/forum/index.php?topic=35245.0
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on June 13, 2022, 08:56:42 PM

So what the 'script' is meant to do:
- it's based on one of the default combine scripts
- it's meant to take the rating (star) value [with half-stars] as numerical [not the actual numerical rating value - which it always just worked, regardless of the format - since id3 & vorbis have different absolute rating values, I assumed this was some magic musicbee api bit inbetween that was converting this correctly...]
- then, take a numeric value from a second [custom] field (call 'Energy' that could have values from 0 -10)
- then combine the 2 with a ' - ' inbetween and write them to 2 other fields (so '10 - 5' would be the resulting tag value for a 5 star rated track, with an Energy value of 10...)

What it now does:
- the energy value gets always written correctly still
As for the weird bits:
- the star value now gets written as:
   - sometimes the numerical value (only on flac files, I have not seen this happen on id3 tags, so a vorbis rating of 60 for a 3 star track, 20 for a 1 star track, etc pp)
   - sometimes the rating value gets written as 1 (regardless of the actual rating / star value)
- on top, IF the rating value gets written as 1, the [custom text 1] ' - ' always gets written twice [minus a ' '...], resulting in '10 - - 1' [instead of '10 - 5']

So, in the above example track [with 10 & 5 respectively] I may end up with '10 - - 1' or,  ' 10 - 100'
I'm a tad lost there.


flac, mp3 and ogg and various combinations of them.
Thanks muchly for testing. (which Advanced Tag & Reporting Tool version are you using, out of curiousity ? Not 100% certain if I am on the latest version Boroda published... and that could be a last option to try - as that's so odd that I get a random mix of absolute as well as properly parsed (star count) values from rating fields.)

Eh - I found part of the problem - this only happens to flac files when the ASR preset is run in the inbox. As soon as I run the same scripts on flac files in a playlist or library, all is fine and the rating gets written as the star equivalent as usual.
Which gives me a work around - in case this helps anyone else
c.

ps. welcome back Boroda!
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on June 14, 2022, 08:20:08 PM
Which gives me a work around - in case this helps anyone else
Meh, called it too early. It's still happening on flac files that have been sent to library too. It's so utterly odd, altogether and that on the 10 files I randomly tested with with, sending to library seemed to bypass the issue, but now it's back when I try to run the script on files I haven't fully tagged yet.... :/
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 16, 2022, 09:04:26 AM
new plugin beta version is released (you will need latest mb 3.5 patch or stable 3.5 mb version or later when they are released):

https://www.mediafire.com/file/9tpb95arr33qvu1/mb_TagTools_beta.zip/file

some bug fixes and probably new bugs are introduced  :)  

MSR command is significantly reworked, now it can be used for very complex searching (without replacements). you can gradually refine your search by adding new rows to the search table and clicking the 'Find' button again. this command is incomplete, 'Select found' button doesn't work yet.

Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 19, 2022, 02:57:15 PM
i've found that i've missed mb native custom search, which is almost perfect (maybe only "not" checkboxes are needed before tag names). so i've removed "search only" capability from MSR.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 19, 2022, 03:03:49 PM
Could the 'new tag value' get some easier to read contrast?:
(https://i.imgur.com/4BIs6bY.png)
bump
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 19, 2022, 03:41:11 PM
try  this version (i've changed plugin colors, when i was modifying MSR (and these modifications are now obsolete), but haven't tested new colors with various skins):

https://www.mediafire.com/file/9tpb95arr33qvu1/mb_TagTools_beta.zip/file

if you are satisfied with coloring, then i'll remove msr "search only" option from this version and upload it as new stable version.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 19, 2022, 04:18:41 PM
try  this version
It doesn't look good:

(https://i.imgur.com/OF41xSF.png)

Does the download contain the correct files?:

(https://i.imgur.com/F6I3cdi.png)
Both the dates and the version number seems off.
settings says: 5.4.8202

B.t.w.,
I never use 'use skin colours' for your plugin, since I am mainly using dark skins, and things become quite ugly/unreadable using that setting.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 19, 2022, 04:29:26 PM
redownload beta version again. also what colors are you using for windows (suggest it's windows 10)?.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 19, 2022, 04:38:00 PM
No visual changes or improvements.
Version now says 5.4.8205

My Windows 10 colour settings:

(https://i.imgur.com/ZGgZ9uZ.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 19, 2022, 05:10:29 PM
try this version:

https://www.mediafire.com/file/9tpb95arr33qvu1/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 19, 2022, 05:38:22 PM
That looks a lot better:

(https://i.imgur.com/Dc9s42G.png)

Personally I don't care much for the alternating line colouring, but that will be a matter of taste.

edit:
Besides my personal dislike for alternating row colours (a useless and distracting feature in my opinion), I am also not sure why the first line has a different (darker) background colour than the other lines?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 20, 2022, 12:56:33 AM
Besides my personal dislike for alternating row colours (a useless and distracting feature in my opinion), I am also not sure why the first line has a different (darker) background colour than the other lines?
blue line in your screenshot is "selected" or "current" line. this line can't be edited in asr anyway, so it doesn't make much sense to highlight it, but i'm not sure if this highlighting can be easily disabled (this behavior is either default or the only one for .net "grid view" control). i'll leave it as is for now.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 20, 2022, 12:06:37 PM
new stable version (minor improvements and bug fixes):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 20, 2022, 01:29:33 PM
new stable version (minor improvements and bug fixes)
Thanks boroda.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on June 22, 2022, 03:33:00 PM
Hi, just tried the new version
new stable version (minor improvements and bug fixes):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


but it still vanishes after restart.

Previous post
Just updated to 3.5beta and AT&RT vanished. Clicking "configure" gives

MusicBee v3.5.8146.38239D  (Win10.0), 25 Apr 2022 8:21:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zFATgFjBdBS9YrWXGWg==.#=zhhGt68w=(IntPtr #=zTJWEEq3dlH_v)

Tried disabling all other plugins (last.fm (already disabled, don't use), cd art display (already disabled, don't use), lyrics reloaded, media control, taskbar tidbits, theater mode) and restarting but still no AT&RT and same error message. Tried complete uninstall (clicked uninstall, closed MB, deleted AT&RT files from plugin folder) and reinstall. Works until I restart MB and then vanishes and gives same error.

Current error message
MusicBee v3.5.8157.35511D  (Win10.0), 22 Jun 2022 10:16:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zCJ5ZapFPlFl7hsQxGA==.#=zFyIrpRo=(IntPtr #=z5gr9m3RiL7fx)

I tried deleting the settings.xml as well (https://getmusicbee.com/forum/index.php?topic=35245.0) but still AT&RT fails after restart.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 22, 2022, 09:00:11 PM
Current error message
MusicBee v3.5.8157.35511D  (Win10.0), 22 Jun 2022 10:16:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zCJ5ZapFPlFl7hsQxGA==.#=zFyIrpRo=(IntPtr #=z5gr9m3RiL7fx)
do you see message "System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation" on plugin initialization (on mb startup if plugin is enabled)?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 22, 2022, 09:20:45 PM
some visual glitches are fixed. also, highlighting of changed tags in most commands is back (because there is untickable option 'highlight changed tags' in plugin prefs):

https://www.mediafire.com/file/null/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 22, 2022, 10:11:21 PM
https://www.mediafire.com/file/null/mb_TagTools_latest.zip/file
@boroda: this doesn't look like a valid MediaFire link. And comes up with:
(http://i.imgur.com/50NiQi0l.jpg) (https://i.imgur.com/50NiQi0.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 22, 2022, 10:40:10 PM
sorry, here is correct link:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 22, 2022, 10:45:57 PM
sorry, here is correct link:
Thanks for correcting it.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 22, 2022, 10:59:14 PM
Using today's update (5.4.8208) with MB 3.5.8205 P, I'm finding that is a selected preset has no files that meet the criteria, that upon clicking the 'preview' button AS&R locks  up. All presets are grayed out and the only way to exit AS&R is to 'x' out. 'Save all and close' will also exit AS&R.

I've been testing with the two "Remove leading zeros in  Tag 2>" presets.

Let me know if you need more information.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 23, 2022, 01:46:23 AM
i can reproduce this. will look at this issue tommorow.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 23, 2022, 03:03:52 AM
i can reproduce this. will look at this issue tommorow.
Not an "emergency" so take your time. Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 23, 2022, 11:03:24 AM
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 23, 2022, 01:06:17 PM
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Thanks once again, boroda. Working just fine now.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on June 23, 2022, 03:26:48 PM
Current error message
MusicBee v3.5.8157.35511D  (Win10.0), 22 Jun 2022 10:16:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.SettingsPlugin.InitializeComponent()
   at MusicBeePlugin.SettingsPlugin..ctor(Plugin TagToolsPluginParam, PluginInfo aboutParam)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zCJ5ZapFPlFl7hsQxGA==.#=zFyIrpRo=(IntPtr #=z5gr9m3RiL7fx)
do you see message "System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation" on plugin initialization (on mb startup if plugin is enabled)?

The only way I know the plugin failed is because 1. AT&RT does not appear in the "Tools" menu and 2. when I check it in my plugins menu in preferences and click configure the above error message pops up. Otherwise, there is no indication that it has failed.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 23, 2022, 04:28:45 PM
are you using portable or installer mb?
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on June 24, 2022, 03:06:50 PM
are you using portable or installer mb?

Installer
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 24, 2022, 05:03:47 PM
can you upload (or pm) your mb_TagTools.Settings.xml? i'll try to reproduce the bug.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on June 25, 2022, 04:33:06 PM
can you upload (or pm) your mb_TagTools.Settings.xml? i'll try to reproduce the bug.

PM sent
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 25, 2022, 08:12:50 PM
@iamambuser

try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on June 25, 2022, 10:47:08 PM
@iamambuser

try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Thanks. Looks good so far. Restarted MB a few times and everything seems fine.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 25, 2022, 11:11:39 PM
there was a very serious bug in initialization of Advanced search & replace (on plugin startup, without even using ASR). it's strange that nobody has reported it before you.
Title: Re: Additional Tagging & Reporting Tools
Post by: Baba on July 02, 2022, 07:47:54 AM
Hello, I just started using this plugin and for some reason it's not working. I'm trying to use the "Multiple Search & Replace..." feature. I'm trying to replace ";" in the "Artist (displayed)" tag in all songs with ",". I enter them both in their respective places, select the songs and hit "Proceed". It shows that it's done along with the sound-effect (I've selected the asterisk sound) but when i check the song, it hasn't been changed. I hit F5, restarted the app too but still no change.

I haven't tried with other fields yet. In the screenshots linked, i've only shown it on a single file but this happens to every file. The format of the files in question is FLAC.

Screenshot of the pop-up:
(https://i.imgur.com/APaVTTX.png)
Screenshot of the final file in library:
(https://i.imgur.com/A0kJYZP.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 02, 2022, 05:44:28 PM
I'm trying to replace ";" in the "Artist (displayed)" tag in all songs with ",".
I am guessing there is something particular about 'Artist (displayed)'.
It's not even available as a tag using MusicBee's native: Tools > Tagging tools > Search and replace
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 02, 2022, 06:03:34 PM
@Baba, i'll check this. as a suggestion, mb parses "Displayed Artist" tag, and reformats it in some cases. but i'm not sure.

@hiccup, it's actually 'Displayed Artist' tag. I've changed its name due to localization issues at the time i made this functionality. now it's worth to change this tag name to mb native one, maybe i'll do this later.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 02, 2022, 06:11:03 PM
@hiccup, it's actually 'Displayed Artist' tag. I've changed its name due to localization issues at the time i made this functionality.
Ok. But Baba's screenshot says: 'Artist (displayed)'
And that's what is displayed when I tested this too.
(and neither 'Displayed artist' nor 'Artist (displayed) is available using MusicBee's native search and replace function)

Anyway, I'll shut up now. I am not sure what I am talking about, and I am confident you will figure things out.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 02, 2022, 06:41:35 PM
@hiccup, i don't know why 'displayed artist' is not available in mb native search & replace, but you can find this field in multiple artist splitter in tag properties. this tag is always used to to represent track artist(s), but only if it is defined (i.e. if it is redefined by user compared to automatically generated value).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 02, 2022, 06:54:08 PM
Yeah, I know you can see it in the tag editor, and I know it is used (and is very useful) for displaying 'artist' in different situations/panels.
I just don't have a good understanding of the internal mechanics behind it. I believe that MusicBee writes it automatically when any other tag gets written.
I only mentioned this here because the tag seems to be something of an odd duck, and I thought it could perhaps be related to the issue that Baba raised.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 02, 2022, 08:06:12 PM
@ Baba, mb has changed the way it writes multiple artists and displayed artist (using api) some time ago. now writing displayed artist will rewrite multiple artists (list of multiple artists is auto-generated by mb), and writing multiple artists will rewrite displayed artist (also, auto-generated by mb).  i can do nothing without Steven's help. i pm'ed him, let's wait for his answer.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 03, 2022, 09:27:24 AM
@Baba

it's strange, but i can't reproduce this issue today. either i've changed something related in my code yesterday while i was testing the issue or something has been changed in mb latest patch. just to be sure that all is working as expected, redownload the latest plugin version (1) - anyway, i've fixed one bug yesterday - and update mb to the latest patch (2):

(1) https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
(2) https://getmusicbee.com/patches/MusicBee35_Patched.zip
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 10, 2022, 01:54:20 AM
new version released:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

ASR presets now can be exported to/imported from any folder (to share your custom/adjusted standard presets with other people and/or to back up custom presets).
Title: Re: Additional Tagging & Reporting Tools
Post by: fbt78 on July 22, 2022, 11:07:41 AM
Hello,
I downloaded the latest version (22-07-12).
The Library Reports function can no longer export the file. The file is still empty.
Can you fix the bug?
Thanks, it's urgent.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 22, 2022, 12:23:41 PM
try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 22, 2022, 02:55:32 PM
actually, i've found even more bugs in library reports command. download link is the same.
Title: Re: Additional Tagging & Reporting Tools
Post by: zpoison on July 22, 2022, 03:25:02 PM
Hello, when I use the ADV Tagging Tool: Search & Replace, the window which opens has the fonts black on "dark skin" I tried gray skins and I still cannot see (it's both the same contrast every time) I always have to use a white or a really pale skin to be able to see the letters

Here with the One-dark skin:
https://imgur.com/a/r9cFpbG

 Here with the Midnight blue skin
https://imgur.com/a/swuQtkr

It seems to be working only with lighter themes
Is there a fix for this plz, thx
Title: Re: Additional Tagging & Reporting Tools
Post by: fbt78 on July 22, 2022, 03:30:55 PM
everything is working normally again.
Many thanks and congratulations for your developments
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 22, 2022, 04:10:12 PM
@zpoison
unfortunatelly .net coloring for buttons, text labels, etc. is very limited. the main problem is disabled controls. try to turn 'use skin colors' option on/off on plugin prefs (edit> prefs> plugins> additional tagging tools> configure).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 22, 2022, 04:28:55 PM
@zpoison, also, looking at your screenshots, i see you are not using the latest plugin version.
Title: Re: Additional Tagging & Reporting Tools
Post by: zpoison on July 22, 2022, 05:03:44 PM
Excellent, it's working, and looking perfect
Sorry I had forgot that there is a config setting, thank you for your patience
https://imgur.com/a/8K6j2LV (https://imgur.com/a/8K6j2LV)

I did the update. Plugin is well maintained!
I see your other plugins will be useful too. Awesome. See you later have a good weekend
Title: Re: Additional Tagging & Reporting Tools
Post by: endelos on July 23, 2022, 06:06:51 PM
Hi, I've installed the last version : 5.4.8239 along with MusicBee last version 3.4.8033 and I've noticed a new bug.

In my virtual tags, the $Add() function isn't working anymore. It returns nothing (I've even tried $Add(1,1) to check, the result is nothing).

I've tried a rollback with MusicBee, it didn't help. I've tied a rollback with the Additional Tagging & Reporting Tools v. 5.2.7391 and it this time, the problem disapears. I will stay with this version for now, but if you can correct the bug I'd be happy to use the last version again.

Anyway, thank you for your amazing work, this plugin is a must !
Title: Re: Additional Tagging & Reporting Tools
Post by: Steven on July 23, 2022, 10:38:39 PM
$Add is performed by musicbee not this plugin. I have unlocked the other post
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on July 23, 2022, 11:00:13 PM
$Add is performed by musicbee not this plugin. I have unlocked the other post
Sorry Steven. I thought the function was something that boroda added.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 24, 2022, 11:31:56 PM
new virtual tag function is added to plugin (no setup is required to use it, just install plugin and use the function like mb native functions): $DateCreated(<URL>)

type "<URL>" exactly like this, don't use another function argument value. function returns creation date of music file (not last modification date!)

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 25, 2022, 04:58:54 PM
I have updated my virtual tag functions cheat sheet (https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257), and added some explanations on additional AT&RT functions.
There are a few I was not able to write a brief explanation or give a short and practical real-world example formula for.
If you (or anyone else) have suggestions for brief explanations and examples I could add for them, let me know.
They are:

$Lg(number)
$Ln(number)
$Log(number,base)
$AddDuration(duration1,duration2)
$AddDurationToDateTime(datetime,duration)
$SubDateTime(datetime1,datetime2)
$SubDuration(duration1,duration2)
$SubDurationFromDateTime(datetime,duration)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 25, 2022, 06:37:19 PM
hmm... hiccup, i don't see any explanations on ATT functions in that post.

btw these functions can accept tags if tag types correspond to types in function signature:

$CutLeft(string,count)
$CutRight(string,count)
$SentenceCase(string)
$TitleCase(string)
$Add(number1,number2)
$Sub(number1,number2)
$Mul(number1,number2)
$Div(number1,number2)
$Abs(number)
$Lg(number)
$Ln(number)
$Log(number,base)
$Mod(number1,number2)
$Random(max_number)
$Round(number,number_of_digits_after_decimal_point)
$RoundDown(number,number_of_digits_after_decimal_point)
$RoundUp(number,number_of_digits_after_decimal_point)
$Sqrt(number)
$NumberOfDays(datetime1,datetime2)
$AddDuration(duration1,duration2)
$AddDurationToDateTime(datetime,duration)
$SubDuration(duration1,duration2)
$SubDurationFromDateTime(datetime,duration)
$MulDuration(duration, number)
$SubDateTime(datetime1,datetime2)
$Name(filename)

i mean (this note is just for consistency with other function descriptions in your sheet) that these are valid usage of functions:

$CutLeft(<field1>,<field2>)
$CutRight(<field1>,<field2>)
$SentenceCase(<field>)
$TitleCase(<field>)
$Add(<field1>,<field2>)
$Sub(<field1>,<field2>)
$Mul(<field1>,<field2>)
$Div(<field1>,<field2>)
$Abs(<field>)
$Lg(<field>)
$Ln(<field>)
$Log(<field1>,<field2>)
$Mod(<field1>,<field2>)
$Random(<field>)
$Round(<field1>,<field2>)
$RoundDown(<field1>,<field2>)
$RoundUp(<field1>,<field2>)
$Sqrt(<field>)
$NumberOfDays(<field1>,<field2>)
$AddDuration(<field1>,<field2>)
$AddDurationToDateTime(<field1>,<field2>)
$SubDuration(<field1>,<field2>)
$SubDurationFromDateTime(<field1>,<field2>)
$MulDuration(<field1>, <field2>)
$SubDateTime(<field1>,<field2>)
$Name(<URL>)


here are short description of functions you asked:

$Lg(number) returns number
$Ln(number) returns number
$Log(number,base) returns number

above are just mathematical functions: decimal logarithm of any number (or field containing number) - integer or floating point one, it's actually log(number,10); natural logarithm, it's log(number,e), where 'e' is Euler number (~2.71...); and general logarithm. these functions may be useful for volume analysis, i don't remember who requested them.

$AddDuration(duration1,duration2) returns duration
$AddDurationToDateTime(datetime,duration) returns datetime
$SubDateTime(datetime1,datetime2) returns duration (difference between two dates and/or times)
$SubDuration(duration1,duration2) returns duration
$SubDurationFromDateTime(datetime,duration) returns datetime

above functions are self-explanatory, considering that datatime may be either defined as literal (eg. 07/25/2022 or 07/25/2022 8:31 pm or 8:31:15 pm) or as any date tag in mb (eg. 'year', 'original year', 'date added', etc.). duration can be either defined as literal (eg. 00/00/0001 means 1 year, 5:00 means 5 mins, 00/01/0000 10:05:15 means 1 day 10 hours 5 mins 15 secs, etc.) or it can be obtained by subtracting two dates or two times (or two datetimes in general). also, <Time> tag (track duration) is a valid duration.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 25, 2022, 07:23:27 PM
hmm... hiccup, i don't see any explanations on ATT functions in that post.

Damn, you're right. (I shouldn't have been making all these changes with tired eyes)
The ones for which I had already created explanations and examples are there now.

Thanks for the extra input. I will try to figure it out and include it in the sheet when I am in a little bit brighter state of mind…
Title: Problem with Additional Tagging Tools and MB 3.5.8247
Post by: adac on August 01, 2022, 10:41:17 AM
Problem with Additional Tagging Tools and MB 3.5.8247

There seems to be a problem with the artists (multiple field). After restarting Musicbee, the newly entered fields are deleted again.
Apparently only guest artists are copied, not performers

Apparently the problem only occurs with "Copy Tags To Clipboard" (Additional Tagging Tools). There are no problems with manual copying (display as text).


Please excuse my bad english
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 01, 2022, 11:05:25 AM
working as usual for me. please provide step-by-step instructions to reproduce issue and screenshots.
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on August 01, 2022, 12:17:22 PM
Hi Boroda,

Ok I'll try... :-)

1. I take "Wrong Or Right" from 1977 from "The Babys" and copy the data already there using "Copy Tags To Clipboard" and paste it into the album from 2008.

(Screenshot 1 shows the existing data being copied)

(https://i.imgur.com/Vt3OLg0.jpg)
(https://i.imgur.com/bqJU1ci.jpg)

2. After pasting, only the artist (Künstler) and guest artist (Gast-Künstler) are present. Apparently the performers are deleted again. You can see on the left that the performers are still being read out even though they are no longer present in the "Multiple artists field".

(https://i.imgur.com/C7YAZKP.jpg)

3. After I close and restart Musicbee, the performers are no longer available.
Of course, I've also tried this on various other files, always with the same result.
I only noticed it after installing the 3.5.8247 update. I hope the information is enough for now.

(https://i.imgur.com/wbEdJzE.jpg)

Many Thanks
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 01, 2022, 01:59:33 PM
what happens if you copy/paste only 'Künstler' tag? keep in mind that you must hit F5 after pasting tags to see changes.
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on August 01, 2022, 02:13:10 PM
Unfortunately the same result. Tried it with a single file and also with multiple files.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 01, 2022, 04:14:58 PM
pm me one of problem source files. also, what is file type of destination file?
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on August 03, 2022, 02:33:59 PM
@boroda, sadly, I cannot update to v3.5, because it seems like my complex Virtual Tags do not work with it. 😣
It appears that every Virtual Tag that contains non-native functions gets stripped down to just the native ones.

Or maybe I'm performing the update steps incorrectly since the newest versions of the AT&T plugin now require MusicBee v3.5?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 03, 2022, 03:26:37 PM
this is the last plugin version i have for mb 3.4:

 https://www.mediafire.com/file/jv6zni7mceena0a/mb_TagTools_2022-06-08.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on August 03, 2022, 06:04:05 PM
It appears that every Virtual Tag that contains non-native functions gets stripped down to just the native ones.
Can you tell why they don't work anymore?
I would expect that those functions are now seamlessly processed by MusicBee?
(except for Xor, which is now gone)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 04, 2022, 10:50:29 AM
i have the same question. mb 3.5 has many new native functions, therefor they are removed from plugin. but they should work normally in mb 3.5
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 05, 2022, 06:20:18 PM
minor improvements and bugfixes:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

recommended to use with mb 3.5:

https://getmusicbee.com/patches/MusicBee35_Patched.zip
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on August 21, 2022, 10:27:19 AM
…i mean (this note is just for consistency with other function descriptions in your sheet) that these are valid usage of functions:…
That's a good observation.
For the native MusicBee functions I took how they are described in Template Editor > Function Selector as a starting point.
I have reviewed them all, including yours, and tried to have some consistency in the descriptions.

The table and the explanations are updated:
https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257

Let me know if you see something wrong…

PS
I didn't create explanations or examples on the logarithmic stuff.
It's unknown territory for me, and I couldn't find other posts containing formulas that use them.
And people that do want to use them probably already know what they are doing.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on August 21, 2022, 10:29:07 AM
P.S.
Considering the value and the popularity of AT&RT, shouldn't this thread be made sticky?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 21, 2022, 11:59:21 AM
The table and the explanations are updated:
https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257

Let me know if you see something wrong…
all seems to be fine, but i'd replaced a couple of description strings like "(eg. 'year', 'original year', 'date added', etc.)" to "(eg. <Year>, <Original Year>, <Date Added>, etc.)". i mean to use tag names as they are defined in template editor. just for clarity.

PS
I didn't create explanations or examples on the logarithmic stuff.
It's unknown territory for me, and I couldn't find other posts containing formulas that use them.
And people that do want to use them probably already know what they are doing.
forget them. these functions have been requested only once, i don't remember who has requested them, and for what purpose. maybe i'll remove them in future at all.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 21, 2022, 12:00:35 PM
P.S.
Considering the value and the popularity of AT&RT, shouldn't this thread be made sticky?
I don't mind, but I don't think it's up to me to decide.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 21, 2022, 12:20:27 PM
The table and the explanations are updated:
https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257

Let me know if you see something wrong…
also, i think it's worth to add examples with tags as parameters for string functions, something like:


$SentenceCase(string)

capitalises the first letter of the first word in a string, e.g. $SentenceCase(<Title>)
___

$TitleCase(string)

capitalises the first letter of every word in a string, e.g. $TitleCase(<Title>)

other plugin functions seem to have already examples with tags as parameters.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on August 21, 2022, 02:12:27 PM
all seems to be fine, but i'd replaced a couple of description strings like "(eg. 'year', 'original year', 'date added', etc.)" to "(eg. <Year>, <Original Year>, <Date Added>, etc.)". i mean to use tag names as they are defined in template editor. just for clarity.
I agree.

also, i think it's worth to add examples with tags as parameters for string functions, something like:
$SentenceCase(string)
capitalises the first letter of the first word in a string, e.g. $SentenceCase(<Title>)
I left out such examples for functions that seem very obvious.
But I guess it doesn't hurt to add it for those too.

edit
Done.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 21, 2022, 03:26:45 PM
@hiccup, i've found 1 mistake in your cheatsheet:


$SubDuration(duration1,duration2)

returns the sum of two durations.


please change descpiption from "sum" to "subtraction" or "difference".
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on August 21, 2022, 03:35:13 PM
please change descpiption from "sum" to "subtraction" or "difference".
done
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on August 21, 2022, 09:49:58 PM
It appears that every Virtual Tag that contains non-native functions gets stripped down to just the native ones.
Can you tell why they don't work anymore?
I would expect that those functions are now seamlessly processed by MusicBee?
(except for Xor, which is now gone)

I forgot about this comment when mine was moved to another board, but it was because the @Steven and @boroda had implemented the $CutLeft() and $CutRight() functions differently.

P.S.
Considering the value and the popularity of AT&RT, shouldn't this thread be made sticky?

I agree.

Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 22, 2022, 02:01:35 AM
Considering the value and the popularity of AT&RT, shouldn't this thread be made sticky?
Done
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 22, 2022, 09:22:30 AM
Problem with Additional Tagging Tools and MB 3.5.8247

There seems to be a problem with the artists (multiple field). After restarting Musicbee, the newly entered fields are deleted again.
Apparently only guest artists are copied, not performers

Apparently the problem only occurs with "Copy Tags To Clipboard" (Additional Tagging Tools). There are no problems with manual copying (display as text).
for the reference for future users. it was very strange bug, i can't explain it, i even don't know if it was related to plugin or to something else. @adac has solved this problem by deleting mb library (only .mbl file, not music tracks) and recreating library from scratch. probably mb library was corrupted.
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on August 23, 2022, 12:34:29 AM
Problem with Additional Tagging Tools and MB 3.5.8247

There seems to be a problem with the artists (multiple field). After restarting Musicbee, the newly entered fields are deleted again.
Apparently only guest artists are copied, not performers

Apparently the problem only occurs with "Copy Tags To Clipboard" (Additional Tagging Tools). There are no problems with manual copying (display as text).
for the reference for future users. it was very strange bug, i can't explain it, i even don't know if it was related to plugin or to something else. @adac has solved this problem by deleting mb library (only .mbl file, not music tracks) and recreating library from scratch. probably mb library was corrupted.


Unfortunately, the error reappeared after two days. However, rebuilding the library fixed other small bugs that I hadn't noticed as such before. If I find anything else I'll get back to you.
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 23, 2022, 05:41:55 PM
I love the additional tagging tools but I'm a little stuck. And maybe this could be an idea for a preset?

I'd like to search the lyrics tag for certain, explicit, words. If found, I'd like to add [Explicit] to the end of the title of the file.

How do I do this? I've manage to just replace the word in the lyrics with the word explicit :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 23, 2022, 07:52:24 PM
could you post here search and replace patterns for your solution? i've almost managed to do what you want, but for single-line tags, eg. album name, etc, but not for lyrics, which is multi-line.

do you need to determine that lyrics contain all searched words or any of the words?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 23, 2022, 08:39:00 PM
could you post here search and replace patterns for your solution? i've almost managed to do what you want, but for single-line tags, eg. album name, etc, but not for lyrics, which is multi-line.

do you need to determine that lyrics contain all searched words or any of the words?

It would be lyrics that contain any of the words.

So, I'm guessing something like
Search for: (badword1|badword2|badword3) in tag Lyrics

All the files found that contain the words, append "Explicit" onto the end of the tag "Title".
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 23, 2022, 09:22:37 PM
first update plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

then import these 2 custom presets (click 'import' button in ASR, not 'import new', not 'import all'):

https://www.mediafire.com/file/iyxeqf11z3ugenf/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_all_words_entered_in_%255BCustom_text_1%255D_and_separated_by_slash_%2528-%2529.ASR_Preset.xml/file

https://www.mediafire.com/file/e8u6e3o4c5fu816/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_any_of_the_words_entered_in_%255BCustom_text_1%255D_and_separated_by_slash_%2528-%2529.ASR_Preset.xml/file

you need the 2nd preset (search for any of the words), but maybe 1st one will be useful for somebody else (it searches for all words).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 23, 2022, 09:39:33 PM
i've changed slash separator (/) to vertical bar (|):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

https://www.mediafire.com/file/0z4dorrpvc0myhg/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_all_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

https://www.mediafire.com/file/xjg0u3hhblp554h/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_any_of_the_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 23, 2022, 09:51:10 PM
Wow thanks for this.

I've changed one thing when I've imported it, in "Step 1" I changed the tag from "URL" to "Lyrics" but when I do this and I do a preview it seems to want to change test in the lyrics tag and not the title?

What I thought would happen is:

Search lyrics tag for word(s)
Find files that match
Change Title from "Song Title" to "Song Title Explicit"

What seems to happen is that it matches all files and adds "\@eval[[$If($TagContainsAnyString($1,Lyrics,\@1), [Explicit],)]]" to the lyrics tag?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 23, 2022, 10:09:18 PM
Wow thanks for this.

I've changed one thing when I've imported it, in "Step 1" I changed the tag from "URL" to "Lyrics" but when I do this and I do a preview it seems to want to change test in the lyrics tag and not the title?

What I thought would happen is:

Search lyrics tag for word(s)
Find files that match
Change Title from "Song Title" to "Song Title Explicit"

What seems to happen is that it matches all files and adds "\@eval[[$If($TagContainsAnyString($1,Lyrics,\@1), [Explicit],)]]" to the lyrics tag?

Ok, so I've reverted it back to URL for the tag and it does work, but the reason it wasn't working is that the case is sensitive in the Custom Text field!

So, I used badword in the custom text field and it wasn't working, whereas Badword did.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 23, 2022, 10:17:49 PM
1st parameter of $TagContainsAnyString() must be track path (URL), it's captured in step 1, and passed to the function as $1. second parameter is tag name without angle brackets (i.e. "Lyrics" in your case).

i'll make search case-insensitive.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 23, 2022, 10:24:10 PM
redownload plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

presets are not changed.
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 23, 2022, 10:24:40 PM
Brilliant thanks.

Case insensitive would be great!

The only other thing I've noticed is that in the newer version I now get an error if I try and load "Library Reports". I know it's unrelated and it also happened in the version from earlier this month but if I roll back to the 2021 plugin it works.

MusicBee v3.4.8033.18564D

System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at MusicBeePlugin.LibraryReportsCommand.initializeForm()
   at MusicBeePlugin.LibraryReportsCommand..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.libraryReportsEventHandler(Object sender, EventArgs e)
   at #=ztdEURO9iLJryE.#=za3znDkU=(Object #=z09rm0$E=, EventArgs #=z5EKpxKY=)
   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 & Reporting Tools
Post by: bkev on August 23, 2022, 10:44:18 PM
redownload plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

presets are not changed.

redownload plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

presets are not changed.

Yes, the case insensitivity works on this thanks.

What I'm getting now though is that some title tags are changed correctly, and others have the script in it.

For example, some songs change from "Title" to "Title [Explicit]" whereas some others change from "Title" to "Title$Uf($TagConatinsAnyString(<path>...."

I'll have a look tomorrow, but it looks like it's where the album begins with a "T"?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 24, 2022, 08:18:33 AM
So it is doing something a little strange.

It seems that it does want to change the names of titles where the album begins with a T. It also looks like it does it where there is a comma (,) in the title and what happens is that

So for example:

Track = 1-1. Artist - Album beginning with T - Song name
Original Title = Song Name

New title tag then = Song name$If($TagContainsAnyString(<file path>)

But in the file path, the separator \ between Artist and Album has been replaced and the "T" at the beginning of the album is $he

So, if the path was \artist\Thealbum

The script adds this to the title and changes it to \artist$healbum

If that makes sense?

It also looks like it is trying to replace T in the Artist name too?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 24, 2022, 09:09:24 AM
The only other thing I've noticed is that in the newer version I now get an error if I try and load "Library Reports". I know it's unrelated and it also happened in the version from earlier this month but if I roll back to the 2021 plugin it works.

MusicBee v3.4.8033.18564D

System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at MusicBeePlugin.LibraryReportsCommand.initializeForm()
   at MusicBeePlugin.LibraryReportsCommand..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.libraryReportsEventHandler(Object sender, EventArgs e)
   at #=ztdEURO9iLJryE.#=za3znDkU=(Object #=z09rm0$E=, EventArgs #=z5EKpxKY=)
   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)
working fine here. first check that unzipped all files from plugin package, especially "Missing Artwork.png". also, what version of mb are you using (installer, portable, store) and how you have installed plugin (manually copying to <mb folder>\plugins\ or using "add plugin" button in edit> prefs> plugins)?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 24, 2022, 10:04:07 AM
The only other thing I've noticed is that in the newer version I now get an error if I try and load "Library Reports". I know it's unrelated and it also happened in the version from earlier this month but if I roll back to the 2021 plugin it works.

MusicBee v3.4.8033.18564D

System.ArgumentException: Parameter is not valid.
   at System.Drawing.Bitmap..ctor(String filename)
   at MusicBeePlugin.LibraryReportsCommand.initializeForm()
   at MusicBeePlugin.LibraryReportsCommand..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.libraryReportsEventHandler(Object sender, EventArgs e)
   at #=ztdEURO9iLJryE.#=za3znDkU=(Object #=z09rm0$E=, EventArgs #=z5EKpxKY=)
   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)
working fine here. first check that unzipped all files from plugin package, especially "Missing Artwork.png". also, what version of mb are you using (installer, portable, store) and how you have installed plugin (manually copying to <mb folder>\plugins\ or using "add plugin" button in edit> prefs> plugins)?


I've tried deleting the files from AppData\Roaming\MusicBee\Plugins

Closed Musicbee

Opened Musicbee

Added the new zip via the preferences and still get the same.

MusicBee version 3.4.8033 which is the installed version.

Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 24, 2022, 11:10:26 AM
So it is doing something a little strange.

It seems that it does want to change the names of titles where the album begins with a T. It also looks like it does it where there is a comma (,) in the title and what happens is that

So for example:

Track = 1-1. Artist - Album beginning with T - Song name
Original Title = Song Name

New title tag then = Song name$If($TagContainsAnyString(<file path>)

But in the file path, the separator \ between Artist and Album has been replaced and the "T" at the beginning of the album is $he

So, if the path was \artist\Thealbum

The script adds this to the title and changes it to \artist$healbum

If that makes sense?

It also looks like it is trying to replace T in the Artist name too?

Could it be that the script is getting confused?
I can see that
$TagContainsAnyString(<URL>,TagName,string1|string2|etc.): returns "T" if tag
  contains any of the strings separated by |, otherwise returns "F".
  TagName must be written without angle brackets.

I think it is getting mixed up when a "T" already exists in the URL?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 24, 2022, 01:14:24 PM
I've tried deleting the files from AppData\Roaming\MusicBee\Plugins
it was a bug, plugin was always looking for "Missing Artwork.png" in "<mb installation path>\Plugins" folder. this didn't work if users install plugin by ''add plugin"  button in prefs (because plugin is installed to "<AppData>\Plugins" folder in this case). i've embedded "MissingArtwork.png" into plugin .dll, so this must be fixed now.

Could it be that the script is getting confused?
I can see that
$TagContainsAnyString(<URL>,TagName,string1|string2|etc.): returns "T" if tag
  contains any of the strings separated by |, otherwise returns "F".
  TagName must be written without angle brackets.

I think it is getting mixed up when a "T" already exists in the URL?

no, it's another bug. seems to be just legacy and buggy part of code. its fixed. also i've changed $1 to "$1" for URL in presets to take into account commas in file paths (commas also delimit function parameters).

fixed plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

updated presets:

https://www.mediafire.com/file/0z4dorrpvc0myhg/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_all_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

https://www.mediafire.com/file/xjg0u3hhblp554h/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_any_of_the_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

delete old 2 presets before importing new ones to avoid preset duplicating.
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 24, 2022, 08:30:19 PM
I've tried deleting the files from AppData\Roaming\MusicBee\Plugins
it was a bug, plugin was always looking for "Missing Artwork.png" in "<mb installation path>\Plugins" folder. this didn't work if users install plugin by ''add plugin"  button in prefs (because plugin is installed to "<AppData>\Plugins" folder in this case). i've embedded "MissingArtwork.png" into plugin .dll, so this must be fixed now.

Could it be that the script is getting confused?
I can see that
$TagContainsAnyString(<URL>,TagName,string1|string2|etc.): returns "T" if tag
  contains any of the strings separated by |, otherwise returns "F".
  TagName must be written without angle brackets.

I think it is getting mixed up when a "T" already exists in the URL?

no, it's another bug. seems to be just legacy and buggy part of code. its fixed. also i've changed $1 to "$1" for URL in presets to take into account commas in file paths (commas also delimit function parameters).

fixed plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

updated presets:

https://www.mediafire.com/file/0z4dorrpvc0myhg/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_all_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

https://www.mediafire.com/file/xjg0u3hhblp554h/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_track_title_if_lyrics_contain_any_of_the_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

delete old 2 presets before importing new ones to avoid preset duplicating.


That. Is FANTASTIC!

I've given it a test and the library menu now loads and the presets work too!

One last thing I've found. Is there anyway that when the explicit preset is scanning the files, if the word "Explicit" already exists in the title, it skips it?

At the moment, everytime it is run, an additional "Explicit" is added to the title. I'd really like to set this preset to auto run everytime MusicBee is loaded so any new files can be tagged, but at the moment the files would just build up with "Explicit" on the end  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on August 24, 2022, 09:03:28 PM
also, i've added 2 new functions to plugin:

Code
$TagContainsAnyString("<URL>",tag_name,string1|string2|etc.): returns "T" if tag
  contains any of the strings separated by |, otherwise returns "F".
  tag_name must be written without angle brackets,
  e.g. $TagContainsAnyString("<URL>",Title,a|an|the)

$TagContainsAllStrings("<URL>",tag_name,string1|string2|etc.): returns "T" if tag
  contains all strings separated by |, otherwise returns "F".

Are these new functions supposed to work in Virtual Tags too? I cannot get them to do anything.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 25, 2022, 07:30:48 AM
yes, but i've mistaken, quotes around <URL> tag must not be used, they don't work at all, and all is working just fine without them.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 25, 2022, 07:38:14 AM
One last thing I've found. Is there anyway that when the explicit preset is scanning the files, if the word "Explicit" already exists in the title, it skips it?
presets already skips " [Explicit]" at the end of title (notice a space before "[Explicit]"). maybe this space is the problem? or do you want to skip [Explicit] in the middle of the title?
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 25, 2022, 08:55:19 AM
One last thing I've found. Is there anyway that when the explicit preset is scanning the files, if the word "Explicit" already exists in the title, it skips it?
presets already skips " [Explicit]" at the end of title (notice a space before "[Explicit]"). maybe this space is the problem? or do you want to skip [Explicit] in the middle of the title?

No it's [Explicit] at the end of the title as you say.

So, for example

On the first run if lyrics doesn't have a word it's skipped, so that works. If lyrics do contain the word, change "Title" to "Title [Explicit]"

So far so good.

If I run the script again, on the same songs;

If lyrics don't contain the word, it's skipped. Again that's great. If lyrics do contain the words, what happens for me is that "Title [Explicit]" is change to "Title [Explicit] [Explicit]". It doesn't seem to skip it for me, just adds it on again.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 25, 2022, 12:10:21 PM
yes, it's another serious bug in ASR, which even is not directly related to your ASR presets.

fixed plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

fixed presets (delete old 2 presets before importing new presets):

https://www.mediafire.com/file/vb7re29q060oaed/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_%255BTag_1%255D_if_lyrics_contain_all_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

https://www.mediafire.com/file/gmd3v3fzgv06zs0/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_%255BTag_1%255D_if_lyrics_contain_any_of_the_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 25, 2022, 01:25:32 PM
yes, it's another serious bug in ASR, which even is not directly related to your ASR presets.

fixed plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

fixed presets (delete old 2 presets before importing new presets):

https://www.mediafire.com/file/vb7re29q060oaed/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_%255BTag_1%255D_if_lyrics_contain_all_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file

https://www.mediafire.com/file/gmd3v3fzgv06zs0/Add_text_%2527%2527%255BExplicit%255D%2527%2527_to_%255BTag_1%255D_if_lyrics_contain_any_of_the_words_entered_in_%255BCustom_text_1%255D_and_separated_by_%2523.ASR_Preset.xml/file


Yes! That looks like it works, but I may have come across another bug (so sorry!)

If I set "Auto apply present only if track is contained in playlist" to a smart playlist and I also set "Autoapply ticked presets at startup" and tick this present, it seems that the plug in crashes? I think it is still there at start up, as some auto library stats I use still show, but it doesn't appear in the menu and it doesn't seem to change the tags.

I'm not sure if this is because it takes a bit of time for Musicbee to generate the auto playlist and it's maybe not ready before the preset tries to access the files?

But thanks so much so far :)

Edit:
If I set it to just "Autoapply ticked presets on startup" the "Additional tagging tools" option disappears from the menu and to get it back I have to edit the mb_TagTools.Settings file and change   <autoapplyTickedPresetsOnStartup>true</autoapplyTickedPresetsOnStartup> to false
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on August 25, 2022, 01:49:15 PM
yes, but i've mistaken, quotes around <URL> tag must not be used, they don't work at all, and all is working just fine without them.

Sorry, I had not updated properly. It works!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 25, 2022, 05:52:05 PM
but I may have come across another bug (so sorry!)

If I set "Auto apply present only if track is contained in playlist" to a smart playlist and I also set "Autoapply ticked presets at startup" and tick this present, it seems that the plug in crashes? I think it is still there at start up, as some auto library stats I use still show, but it doesn't appear in the menu and it doesn't seem to change the tags.
i cant reproduce plugin crashes using these settings. try to: close mb, delete mb_TagTools.Settings, start mb again, and adjust ASR settings from scratch.
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 25, 2022, 07:22:31 PM
but I may have come across another bug (so sorry!)

If I set "Auto apply present only if track is contained in playlist" to a smart playlist and I also set "Autoapply ticked presets at startup" and tick this present, it seems that the plug in crashes? I think it is still there at start up, as some auto library stats I use still show, but it doesn't appear in the menu and it doesn't seem to change the tags.
i cant reproduce plugin crashes using these settings. try to: close mb, delete mb_TagTools.Settings, start mb again, and adjust ASR settings from scratch.

Still happens for me I'm afraid.

I've closed mb, deleted the file. Opened mb. Deleted all the presets. Closed mb. Open mb. Import any word explicit preset. Add the word. Tick the preset and tick the box for "Autoapply ticked presets at startup". Click Apply and "Save all and close"

Close mb

Open mb and the option for "Advanced Tagging Tools" no longer appears in the mb menu.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 25, 2022, 09:44:44 PM
i thinks it's just a combination of 2 known issues (internal mb issue and plugin issue), each of which separately is not very important to fix it. roughly speaking, you click mb "tools" menu before plugin's submenu registration (and plugin's submenu won't be ever registered in this case). i've moved plugin's submenu registration to the beginning of plugin initialization (before auto-applying asr presets at startup).

try fixed plugin. it's worth to wait 1-2 sec. before clicking mb menu on mb startup in any case.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 25, 2022, 10:17:06 PM
i thinks it's just a combination of 2 known issues (internal mb issue and plugin issue), each of which separately is not very important to fix it. roughly speaking, you click mb "tools" menu before plugin's submenu registration (and plugin's submenu won't be ever registered in this case). i've moved plugin's submenu registration to the beginning of plugin initialization (before auto-applying asr presets at startup).

try fixed plugin. it's worth to wait 1-2 sec. before clicking mb menu on mb startup in any case.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Brill, it doesn't break now nice one!

One question, when does the plug in change the tags? Will it rescan the playlists or does something else need to be done for it to check the playlist and/or library so it can check any new files added?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 26, 2022, 02:39:51 AM
One question, when does the plug in change the tags? Will it rescan the playlists or does something else need to be done for it to check the playlist and/or library so it can check any new files added?
If you tick the box to the left of the desired preset, it will automatically apply the preset to all files that meet the criteria. Otherwise you must select the files > open ASR > select the preset > preview > apply.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 26, 2022, 10:23:14 AM
One question, when does the plug in change the tags? Will it rescan the playlists or does something else need to be done for it to check the playlist and/or library so it can check any new files added?
asr auto-applies ticked presets if "changed" file meet the criteria (as phred has written) directly on file change. "file change" is either any change of its tag(s), if this tag change is not made by asr itself (to avoid infinite loops), or moving file from inbox to library, or just adding new file to the library.

i would recommend you not to auto-apply asr presets on mb startup. it's slower that:

1st manually apply required presets to files that belong to required playlist (select playlist in the left navigator panel to show only tracks from that playlist in the main panel, and select all tracks from playlist (ctrl+A))

2nd auto-apply required presets on "tag changes" (this will also auto-apply presets on adding new tracks to the library), if "changed files" belong to that (auto)playlist


i've made auto-applying asr presets slightly faster, not sure if it's noticeable:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on August 26, 2022, 12:04:10 PM
One question, when does the plug in change the tags? Will it rescan the playlists or does something else need to be done for it to check the playlist and/or library so it can check any new files added?
asr auto-applies ticked presets if "changed" file meet the criteria (as phred has written) directly on file change. "file change" is either any change of its tag(s), if this tag change is not made by asr itself (to avoid infinite loops), or moving file from inbox to library, or just adding new file to the library.

i would recommend you not to auto-apply asr presets on mb startup. it's slower that:

1st manually apply required presets to files that belong to required playlist (select playlist in the left navigator panel to show only tracks from that playlist in the main panel, and select all tracks from playlist (ctrl+A))

2nd auto-apply required presets on "tag changes" (this will also auto-apply presets on adding new tracks to the library), if "changed files" belong to that (auto)playlist


i've made auto-applying asr presets slightly faster, not sure if it's noticeable:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


That's great thanks. Happy to run it through my library I've already got manually and the tick in the preset means it applies to any new files is perfect. Thanks for putting so much work in to getting this sorted.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 26, 2022, 12:34:12 PM
you are welcome :)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on August 27, 2022, 07:46:17 PM
I seem to have encountered an unusual problem with the \@replace function.  A simple single step reproducer is outlined below.

<Tag 1> is writable, corresponds to Title
<Custom text 1> is active, and set to: 1/A|2/B|3/C
Search for: (\d)
Replace with: \@replace[[$1;;\@1]]

Testing with a title of "Let A = 2" results in the expected "Let A = B" (single match to the regex).

However, if the regex finds two matches such as in the title "Let 1 = 3" (which should result in "Let A = C"), the result is instead a very mangled:

Let A;;A/A|B/B|C/C]] = \@replace[[C

...which seems to be a combination of the title with the 'A' and 'C' parts visibly changed as expected, but the rest is actually the data from the preset fields themselves.

Again, this only happens when 2 or more pattern matches are encountered in a title, single matching works reliably.

Using the latest version of the plugin (from 26-Aug-22), and the latest MB (3.5.8274 P)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 27, 2022, 09:02:28 PM
exactly for the case you've described, use search pattern ^(.*), not (\d), because you already have explicitly defined to replace only digits 1, 2 and 3 in <custom text 1>. or is it a simplified example?

btw, are you using "Multiple Search & Replace" to create this ASR preset? function "\@replace" had been created only as backend for MSR. it's better to use MSR (convenient frontend) for such tasks.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on August 27, 2022, 10:08:05 PM
...or is it a simplified example?
It's a vastly simplified example (what the grumpy StackOverflow people would call "Minimal, Complete, and Verifiable").  :)

My actual regex is this: ((?=\b[MCDXLVI]{1,6}\b)M{0,4}(?:CM|CD|D?C{0,3})(?:XC|XL|L?X{0,3})(?:IX|IV|V?I{0,3}))

(It matches Roman Numerals to the exclusion of other text - using that as the example would just complicate everything!)

btw, are you using "Multiple Search & Replace" to create this ASR preset? function "\@replace" had been created only as backend for MSR. it's better to use MSR (convenient frontend) for such tasks.
I was using ASR (that's the more convenient frontend, isn't it?) - MSR is almost impossible to use as the UI input-fields don't seem to allow simple cursor movement with the <Left>/<Right> keys, so editing is a lost cause.  (The ASR input fields work fine, so that's the best one for me.  I have no idea why the MSR input is so difficult - maybe I adjusted the keyboard settings in MB and it interferes with your UI?)

In any event, the result is the same for either (I just tried it), so it's something in the function itself, probably not user-error.  ;)

To be completely fair, what I'm really looking for is a function which is the opposite of @lc (I need roman numerals in all upper-case, after using @tc on the rest of the text).  There doesn't seem to be an all upper-case function (is there?), so I'm using @replace as an awkward workaround.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 28, 2022, 06:14:50 AM
\@replace function was never intended to use this way. you must always use ^(.*) as search pattern and $1 as 1st parameter of \@replace.

but you can use any regexes in the second parameter of \@replace (in "Custom text 1" in your case), e.g. something like \@replace[[$1;;*(\\d)/A]], which replaces all digits by "A" (asterisk means using regex for search, backslashes must be escaped). in msr just tick checkbox in "(*)" column to use regex.

I was using ASR (that's the more convenient frontend, isn't it?) - MSR is almost impossible to use as the UI input-fields don't seem to allow simple cursor movement with the <Left>/<Right> keys, so editing is a lost cause.  (The ASR input fields work fine, so that's the best one for me.  I have no idea why the MSR input is so difficult - maybe I adjusted the keyboard settings in MB and it interferes with your UI?)
it's strange, because <left>/<right> keys are working fine for me in msr.

To be completely fair, what I'm really looking for is a function which is the opposite of @lc (I need roman numerals in all upper-case, after using @tc on the rest of the text).  There doesn't seem to be an all upper-case function (is there?), so I'm using @replace as an awkward workaround.
\@uc was missing only because i was thinking it wouldn't be needed to anyone. not a big deal, it's just couple of new lines of code in plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

i've also added asr preset "Example: 'Change case' command - UPPER CASE" as an example.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on August 28, 2022, 07:57:40 AM
...you can use any regexes in the second parameter of \@replace (in "Custom text 1" in your case), e.g. something like \@replace[[$1;;*(\\d)/A]], which replaces all digits by "A"...
Nice to know, except your example (typed literally) doesn't seem to work (the title is returned as blank).  Not sure what I could be doing wrong, as I simply copy/pasted your regex directly into MSR.  :-\

\@uc was missing only because i was thinking it wouldn't be needed to anyone... i've also added asr preset "Example: 'Change case' command - UPPER CASE" as an example.
...umm.... doesn't seem to be working.  Downloaded the new version from your link, found the new ASR preset, but it doesn't seem to work: it's literally replaced by "\@uc[[movement iii;;]]".  @lc works as usual.

 :'(
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on August 28, 2022, 08:08:37 AM
it's strange, because <left>/<right> keys are working fine for me in msr.
I discovered that I had set "Playback: Skip Forward 5 seconds" in MB to the <Right> key and Back 5 seconds to the <Left> key, and that messes up your input fields (only in that MSR listview form).  Deleting those hotkeys allows the fields/keys to work properly.  Weird.  At least that's one mystery solved.  ::)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 28, 2022, 08:22:05 AM
Nice to know, except your example (typed literally) doesn't seem to work (the title is returned as blank).  Not sure what I could be doing wrong, as I simply copy/pasted your regex directly into MSR.  :-\
no, this example is for use in asr preset. msr do all escaping for you automatically, type usual regexes in msr, i.e. the same example for msr is:

search for (\d) and replace by A. no asterisk and escaping of backslashes is needed in msr.

...umm.... doesn't seem to be working.  Downloaded the new version from your link, found the new ASR preset, but it doesn't seem to work: it's literally replaced by "\@uc[[movement iii;;]]".  @lc works as usual.
hmm... it seems that you haven't updated plugin .dll, only asr presets.

(https://i.imgur.com/yJT8kpO.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 28, 2022, 08:27:57 AM
...umm.... doesn't seem to be working.  Downloaded the new version from your link, found the new ASR preset, but it doesn't seem to work: it's literally replaced by "\@uc[[movement iii;;]]".  @lc works as usual.
sorry, it's me who haven't updated plugin .dll in plugin .zip :) redownload plugin from the same link.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on August 28, 2022, 08:44:29 AM
msr do all escaping for you automatically
Ah, that explains that.  I actually searched through all 177 pages of this thread before I posted originally, and the "documentation" for \@replace amounts to a single example when you first added it, no other details.  Thanks.

hmm... it seems that you haven't updated plugin .dll...
Ok, the most recent one from 28-Aug now works properly, the previous one from a few hours ago did not work - maybe the mediafire link needed flushing.

Thank you very much.  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 28, 2022, 09:24:32 AM
I actually searched through all 177 pages of this thread before I posted originally, and the "documentation" for \@replace amounts to a single example when you first added it, no other details.  
it's because this is the service function for use by msr only, i've documented some more "generic" asr functions (which can be useful not only for preinstalled presets, but for custom presets also) on the 1st post on this topic.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 29, 2022, 09:35:02 PM
boroda...

Using plugin 5.4.8272 with MB 3.5.8276 P

I'm having some issues with two presets which have worked previously, but don't seem to be working as they did before. Both are "extract featuring artists and add the to the guest artist tag.
(http://i.imgur.com/e2QflDkl.jpg) (https://i.imgur.com/e2QflDk.jpg)
Both of them do add the featured artist(s) to Guest Artist as expected.
But both of them now remove the featured artist(s) from the title while previously they were left as part of the title.
The first of the two leaves a "(" as part of the title and removes everything that follows.

Please let me know if you need more info to correct the functionality of these two presets.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 30, 2022, 09:15:44 AM
Both of them do add the featured artist(s) to Guest Artist as expected.
But both of them now remove the featured artist(s) from the title while previously they were left as part of the title.
it's strange that this ever has been working for you this way. copy required preset and erase search/replace patterns in step 3. save the copy and use it instead of the original preset. your custom presets (including copies of original presets) won't be deleted/overwritten on plugin update.

The first of the two leaves a "(" as part of the title and removes everything that follows.
i cant reproduce this. could you post here exact title of track in question?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 30, 2022, 11:55:28 AM
Thanks boroda. I will admit that I haven't used this particular preset in quite some time. But I assure you that it did work as intended previously.

I removed the criteria from step 3 and it now works as expected.

As for the lingering parenthesis, it was the -second- present that did that, not the first. I followed the same steps to fix this one and now the one remaining parenthesis is at the end of the last guest artist.

Before copying and changing step 3 on the second preset:
(http://i.imgur.com/Yasi5VNl.jpg) (https://i.imgur.com/Yasi5VN.jpg)

After applying the second preset and before copying and changing step 3:
(http://i.imgur.com/pa3D2mml.jpg) (https://i.imgur.com/pa3D2mm.jpg)

After copying and changing step 3 and applying the second preset:
(http://i.imgur.com/Ta370O8l.jpg) (https://i.imgur.com/Ta370O8.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 30, 2022, 01:44:24 PM
post text quotations of title tag, not screenshots. or better, pm me the problem track.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 30, 2022, 03:37:40 PM
PM with link sent
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 30, 2022, 08:04:54 PM
phred, i still can't reproduce your issue, but anyway i've found some bugs in these 4 'extract guest artists' presets. delete 2 your custom copies of presets, redownload plugin, update it, import new presets (it's even better to import all presets, but this will reset any settings you've made for predefined presets). test 2 updated presets on 1 test track. if they work as expected, copy 2 predefined presets and remove step 3 from copies.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 30, 2022, 10:28:48 PM
- I exited MB and overwrote mb_TagTools.dll with the new version (5.4.8275.)

- I then launched MB, then ASR and deleted all the presets.

- Exited MB, copied all the presents from the ZIP to the ASR Presets directory, relaunched MB, and imported all presets.

- Using the same track I've been testing with I applied the first preset and it did not create any guest artists. I copied the preset and removed the criteria in step 3, tried again and it works as expected.

- Restored the tags as before and tried with the second preset. This removed the featured artists from the title leaving the title and an open parenthesis, created the guest artists, with the last one having a close parenthesis.

- Restored the tags as before, copied the reset removing step three and applied. This left the featured artists as part of the title, but still had a close parenthesis on the last of the guest artists.

Since the copied first preset works as I wish, I'm willing to consider this solved. However, if you want to continue troubleshooting, I'm more than happy to help.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 31, 2022, 06:46:00 AM
As for the lingering parenthesis, it was the -second- present that did that, not the first. I followed the same steps to fix this one and now the one remaining parenthesis is at the end of the last guest artist.
ahh, yes, sorry, haven't noticed this.

preset "Extract featuring artists from track title and add them to the (Guest) 'Artist' tag - 'Title <Custom text 1> <Artist1> <Custom text 2> <Artist2>' format" indeed treats parenthesis as parts of track title and last guest artist name.

Since the copied first preset works as I wish, I'm willing to consider this solved. However, if you want to continue troubleshooting, I'm more than happy to help.
it's intended behavior for 1st and 2nd presets. 1st preset stripes parenthesis, 2nd one must be applied when there are no parentheses in track title.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on August 31, 2022, 01:44:40 PM
it's intended behavior for 1st and 2nd presets. 1st preset stripes parenthesis, 2nd one must be applied when there are no parentheses in track title.
Ahhh!  Thanks for the clarification, boroda.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on September 17, 2022, 06:19:17 PM
@boroda...

If it's not too difficult, could you make the cursor appear in the search box whenever AS&R is launched?

I'm finding that I'm enabling auto-apply presents unintentionally because I'm expecting the cursor to be in the search box.

Thanks for considering.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 17, 2022, 08:17:09 PM
@phred:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on September 17, 2022, 08:44:07 PM
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
WOW! That's some damn fast service. This is really great.
Thanks very much, boroda.
Title: Re: Additional Tagging & Reporting Tools
Post by: so_la_la on September 17, 2022, 09:41:51 PM
Could it be that this plugin overrides the MB option to not update the timestamp when making changes to files?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 17, 2022, 10:15:41 PM
Could it be that this plugin overrides the MB option to not update the timestamp when making changes to files?
plugin is using mb api to update track tags. so it depends on mb behavior, but i'm pretty sure that mb api calls respect this setting.

try to disable this option and use for example 'copy tag' command on one track to copy any tag to tag stored in file (eg. some custom tags may not be stored in files). then check last modified time of that track.
Title: Re: Additional Tagging & Reporting Tools
Post by: so_la_la on September 23, 2022, 05:11:13 PM
Hi and thanks for getting back.
I have tried out your suggestion and what I get is this:
I have "don't update file modification time when saving tags" ticked.
I highlight a file, select Tools, Tagging and Reporting, Copy Tag.
I tell it to write the album title into the comment.
The command is executed and the timestamp both in MB and in Windows Explorer is updated.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 25, 2022, 03:42:52 PM
i can't reproduce this. what happens if you change some tag in tag editor (i.e. not using plugin)?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 25, 2022, 08:22:49 PM
new plugin version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Title: Re: Additional Tagging & Reporting Tools
Post by: so_la_la on September 28, 2022, 10:34:30 PM
i can't reproduce this. what happens if you change some tag in tag editor (i.e. not using plugin)?
Hi there this would also update the timestamp -- I am confused...
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 29, 2022, 07:15:36 AM
try to post it on the "bug reports" board. maybe Steven could help.
Title: Re: Additional Tagging & Reporting Tools
Post by: Anoushka on October 13, 2022, 12:30:21 AM
Hello,
I want to use the additional tagging for batch tagging much more.
I tried to copy & edit some of the presets with regular expressions- but without success  :(
I want to achieve: Copy a tag (f.e. ".Relax Music") to another field, but without the dot. So in the other field should be then "Relax Music".
I searched the web for the regular expressions and tested them on regular-expression-test-sites ([^.]). There my tests were succesful, but not in the plugin. I tried it in different variations- without success....
I think, it should be easy, but....
Please help....
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 13, 2022, 12:39:54 AM
I searched the web for the regular expressions and tested them on regular-expression-test-sites ([^.]). There my tests were succesful, but not in the plugin. I tried it
Can you be specific on what you tried exactly?
It's a bit vague to me.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 13, 2022, 05:09:29 PM
Hello,
I want to use the additional tagging for batch tagging much more.
I tried to copy & edit some of the presets with regular expressions- but without success  :(
I want to achieve: Copy a tag (f.e. ".Relax Music") to another field, but without the dot. So in the other field should be then "Relax Music".
I searched the web for the regular expressions and tested them on regular-expression-test-sites ([^.]). There my tests were succesful, but not in the plugin. I tried it in different variations- without success....
I think, it should be easy, but....
Please help....
it's strange that [^.] is working somewhere because it means "search either for beginning of string or any symbol" (unescaped dot means "any symbol" in regex). what is working for me is:

search for ^\.?(.*)

replace by $1
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on October 13, 2022, 05:36:38 PM
For new users of the Advanced Search & Replace function of this plugin, and even for us oldsters, here's (at least to me) a (formerly) hidden feature:

for the info for future users:

1. if any asr preset is ticked the color of warning text at the top of asr window is changed
2. to easily see all ticked presets (and only ticked presets) tick the checkbox in the yellow frame on screenshot:

(https://i.imgur.com/xiQQNgT.png)

(https://i.imgur.com/MJdMkfr.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: Anoushka on October 13, 2022, 08:09:07 PM
Hello boroda,

yeah,
Quote
search for ^\.?(.*)

replace by $1
works :-)
Thanks a lot!!
But: Could you please tell me, what the characters mean? I'd like to understand things, not only to copy them.
^ =Beginning of the line, right?
\. =escaped dot? But dot is not a special character, is it? So, why escaped?
Does the ? after the dot mean, "do not match dot"? Nowhere I found, that a ? after a character negates it...
(.*) =find any character in any number of times, right?

My test before: In f.e. https://learn.microsoft.com/en-us/dotnet/standard/base-types/regular-expression-language-quick-reference?redirectedfrom=MSDN (and other regular expression learning sites) it is explained like this: [^ character_group ] Negation: Matches any single character that is not in character_group. By default, characters in character_group are case-sensitive. [^aei] Finds "r", "g", "n" in "reign".

@hiccup: I am really sorry, I cannot tell you so much more about my testings. About 30 variations I had- I do not remember anymore. Something like ^[^.](.*) & [^.](.*) & (.*)[^.] & ^(.*)[^.] & ([^.].*) & ^([^.].*) and so on and so on...  and another site said, that ?! also negates, this I tried also in many variations.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 14, 2022, 02:39:38 PM
^=yes, beginning of line
.="any character", \.=literally "dot"
?=previous character or pattern must be encountered 0 or 1 time (i.e. dot literal must be used 1 time or not used at all in the pointed search pattern)
.*="any character matched any number of times", (.*)=capture .* as $1 ($1 because parenthesis are used 1st time (when read from left to right) in search pattern)

you can see the link to regex language here:

(https://i.imgur.com/YSsDq9p.png)

--------------

yes, sorry, ^ inside brackets has different meaning. it's negation. dot inside brackets has different meaning also, it's just dot. that is [^.] means "not dot". so 1st character will be skipped from capture $1 (inside following parenthesis) if 1st char is not dot
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 14, 2022, 10:13:22 PM
you can see the link to regex language here:
(https://i.imgur.com/YSsDq9p.png)
It never occurred to me to click on that sentence.
Probably because I didn't consider or understand it to have some useful function.

Perhaps it would be better if it was renamed to something like:
Microsoft Regular Expression Quick Guide
?


Title: Re: Additional Tagging & Reporting Tools
Post by: phred on October 14, 2022, 10:41:46 PM
Perhaps it would be better if it was renamed to something like:
Microsoft Regular Expression Quick Guide
+1
I never realized that was a click-able link.
Title: Re: Additional Tagging & Reporting Tools
Post by: Anoushka on October 16, 2022, 08:23:26 PM
Hello boroda,
thanks for your explanation :-) But... still I do not really understand, why yours is working and mine not. Maybe my IQ is not high enough ;-) But I think, I do not understand because my english is not good enough & because of technical terms.  :-[
Or I just don't understand the basic. [^.] means "not dot". (.*) means "any character in any number. So it should find everything except dot and copy the found (without dot because it didn't found dot) into the other field. But it doesn't...
^\.?(.*): With your explanation it should find anything with no or one dot and copy the found into the other field. But it copies the found without dot...

But I already have other questions...
I'd like to get rid of other programs for my music-editing and because of that hoping to find MB-solutions for the following wishes:
* Batch resizing of Covers: I read, it is not (easy) possible in MB. Maybe, it could be possible with this plugin??
* Copy the field-value from one folder to another: F.e. I have track "Song" in the "Records"-folder with correct genres. And the same track in the "All bands"-folder with incorrect genres. At the moment I copy them always manually but would love to do it in a more easier & faster way :-)
* Delete all unnecessary fields /their values and keep only my wanted fields with their values- in one step.
* For my MP3-Player my files have to be with tag types ID3v2.3 and without other types. With foobar2000 I can control that and if needed I can correct it in an easy way. Is that possible in MB too?

 ;D  8) Of course I noticed the regex-link in the plugin and used it already- it's the one I mentioned above ;-)

Thanx for your help :-)
Anoushka
Title: Re: Additional Tagging & Reporting Tools
Post by: codingduo on October 20, 2022, 10:40:33 AM
Hi borodo,

thank you for your wonderful plugin! It adds so many useful features to MB.

One issue I noticed in the more recent version:

Two buttons in the advanced search & replace window are cut off:

(https://i.imgur.com/9ydls1j.jpg) (https://i.imgur.com/9ydls1j.png)

I'm running MB 3.5.8296 portable on Windows 11 Version 21H2 (Build 22000.1098).


And by the way: is it possible to increase the amount of assignable hotkeys to like 50? This would be awesome.

Thank you!
Title: Re: Additional Tagging & Reporting Tools
Post by: Anoushka on October 26, 2022, 07:05:18 PM
Hello again,
das really nobody has any idea for these wishes??
Quote
* Batch resizing of Covers: I read, it is not (easy) possible in MB. Maybe, it could be possible with this plugin??
* Copy the field-value from one folder to another: F.e. I have track "Song" in the "Records"-folder with correct genres. And the same track in the "All bands"-folder with incorrect genres. At the moment I copy them always manually but would love to do it in a more easier & faster way :-)
* Delete all unnecessary fields /their values and keep only my wanted fields with their values- in one step.
* For my MP3-Player my files have to be with tag types ID3v2.3 and without other types. With foobar2000 I can control that and if needed I can correct it in an easy way. Is that possible in MB too?
I tried by myself to do it with this plugin. But I have fear to damage anything, because I am not firm enough with these things.
Title: Re: Additional Tagging & Reporting Tools
Post by: Ploki on October 29, 2022, 10:46:40 PM
Request for new feature or extend current one

In current function repunct it only translate some special characters to some of this
Code
<< " [ ((
Full definition is in AutoLibraryReports.cs rows starts with 827

It is possible to do something similar with letters? For example I want to translate artists like this:
Céline Dion -> Celine Dion (é -> e)
Christina Stürmer -> Christina Sturmer (ü -> u)
Horkýže Slíže -> Horkyze Slize (ý -> y, ž -> z, í -> i)

Maybe this could help with specifying characters
https://stackoverflow.com/questions/18123501/replacing-accented-characters-with-plain-ascii-ones
https://stackoverflow.com/questions/286921/efficiently-replace-all-accented-characters-in-a-string
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on November 03, 2022, 07:55:25 PM
But I already have other questions...
I'd like to get rid of other programs for my music-editing and because of that hoping to find MB-solutions for the following wishes:
* Batch resizing of Covers: I read, it is not (easy) possible in MB. Maybe, it could be possible with this plugin??
* Copy the field-value from one folder to another: F.e. I have track "Song" in the "Records"-folder with correct genres. And the same track in the "All bands"-folder with incorrect genres. At the moment I copy them always manually but would love to do it in a more easier & faster way :-)
* Delete all unnecessary fields /their values and keep only my wanted fields with their values- in one step.
* For my MP3-Player my files have to be with tag types ID3v2.3 and without other types. With foobar2000 I can control that and if needed I can correct it in an easy way. Is that possible in MB too?

None of these things are as simple to do in MusicBee as with a dedicated tagging program like mp3tag, for instance.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 04, 2022, 06:44:02 PM
A request:

Could AT&RT be extended to support the deletion of tags?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 04, 2022, 07:00:32 PM
Could AT&RT be extended to support the deletion of tags?
+1
Title: Re: Additional Tagging & Reporting Tools
Post by: Anoushka on November 07, 2022, 09:31:50 PM
But I already have other questions...
I'd like to get rid of other programs for my music-editing and because of that hoping to find MB-solutions for the following wishes:
* Batch resizing of Covers: I read, it is not (easy) possible in MB. Maybe, it could be possible with this plugin??
* Copy the field-value from one folder to another: F.e. I have track "Song" in the "Records"-folder with correct genres. And the same track in the "All bands"-folder with incorrect genres. At the moment I copy them always manually but would love to do it in a more easier & faster way :-)
* Delete all unnecessary fields /their values and keep only my wanted fields with their values- in one step.
* For my MP3-Player my files have to be with tag types ID3v2.3 and without other types. With foobar2000 I can control that and if needed I can correct it in an easy way. Is that possible in MB too?

None of these things are as simple to do in MusicBee as with a dedicated tagging program like mp3tag, for instance.
Oh, what a pity! But thanx for your answer!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 08:38:50 AM
Hello boroda,
thanks for your explanation :-) But... still I do not really understand, why yours is working and mine not. Maybe my IQ is not high enough ;-) But I think, I do not understand because my english is not good enough & because of technical terms.  :-[
Or I just don't understand the basic. [^.] means "not dot". (.*) means "any character in any number. So it should find everything except dot and copy the found (without dot because it didn't found dot) into the other field. But it doesn't...
^\.?(.*): With your explanation it should find anything with no or one dot and copy the found into the other field. But it copies the found without dot...

But I already have other questions...
I'd like to get rid of other programs for my music-editing and because of that hoping to find MB-solutions for the following wishes:
* Batch resizing of Covers: I read, it is not (easy) possible in MB. Maybe, it could be possible with this plugin??
* Copy the field-value from one folder to another: F.e. I have track "Song" in the "Records"-folder with correct genres. And the same track in the "All bands"-folder with incorrect genres. At the moment I copy them always manually but would love to do it in a more easier & faster way :-)
* Delete all unnecessary fields /their values and keep only my wanted fields with their values- in one step.
* For my MP3-Player my files have to be with tag types ID3v2.3 and without other types. With foobar2000 I can control that and if needed I can correct it in an easy way. Is that possible in MB too?

 ;D  8) Of course I noticed the regex-link in the plugin and used it already- it's the one I mentioned above ;-)

Thanx for your help :-)
Anoushka
just read search pattern from left to right and keep and mind that we will find something or won't, but only captured chars (which will fall in parenthesis) will be placed instead of $1 in replacement pattern.

^\.?(.*)

^ at the beginning of means that only search started from the beginning of tag must be taken. without ^ search may be repeated again thru the rest of tag after successful finishing search pattern (but not finishing the whole tag).

\.? if 1st char is dot then we go further and ignore it ("ignore" because we don't capture it).

(.*) we capture any number of any chars from previous point (i.e. skipping previous dot if it was before our capture).

the task is not only to find dot at the beginning of tag, but to capture the rest of tag in this case OR capture the whole tag otherwise.
------------

as for your other questions, i don't it's possible with the help of plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 08:56:50 AM
Hi borodo,

thank you for your wonderful plugin! It adds so many useful features to MB.

One issue I noticed in the more recent version:

Two buttons in the advanced search & replace window are cut off:

(https://i.imgur.com/9ydls1j.jpg) (https://i.imgur.com/9ydls1j.png)

I'm running MB 3.5.8296 portable on Windows 11 Version 21H2 (Build 22000.1098).


And by the way: is it possible to increase the amount of assignable hotkeys to like 50? This would be awesome.

Thank you!
support for german, polish and french localizations are discontinued long time ago (because all translators haven't visited this site for a log time). your localization files are from some old plugin version. delete 'de' subfolder from mb 'plugins' folder to switch to english localization.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 09:04:39 AM
A request:

Could AT&RT be extended to support the deletion of tags?
what do you mean by 'deletion'? writing empty values? or physically deleting tags from music files? if latter, then no, it couldn't, because plugin is working with tags by using mb api only, and api doesn't provide such functionality. why you just don't use mb native 'tools> tagging tools> remove tags' command?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 09:06:00 AM
Request for new feature or extend current one

In current function repunct it only translate some special characters to some of this
Code
<< " [ ((
Full definition is in AutoLibraryReports.cs rows starts with 827

It is possible to do something similar with letters? For example I want to translate artists like this:
Céline Dion -> Celine Dion (é -> e)
Christina Stürmer -> Christina Sturmer (ü -> u)
Horkýže Slíže -> Horkyze Slize (ý -> y, ž -> z, í -> i)

Maybe this could help with specifying characters
https://stackoverflow.com/questions/18123501/replacing-accented-characters-with-plain-ascii-ones
https://stackoverflow.com/questions/286921/efficiently-replace-all-accented-characters-in-a-string
it's interesting idea. thanks for your proposition, i'll look at this deeper.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 09:56:48 AM
i've tried this plugin (https://getmusicbee.com/forum/index.php?topic=37276.0), it's working fine with ASR (if just having such virtual tag function is not sufficient).  
open ASR, find preset "Example: Write result of virtual tag expression defined in <Custom text 1> to <Tag 2>". modify this preset or better, copy it to see in copy how to use virtual tag functions in ASR. here is screenshot of what i've tested:

(https://i.imgur.com/nqknCSs.png)

or

(https://i.imgur.com/U4917dD.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 08, 2022, 01:01:40 PM
what do you mean by 'deletion'? writing empty values? or physically deleting tags from music files?
Speaking for myself, I was thinking of deleting the entire tag value. Unless if writing an empty value would appear as a blank/clean tag to MB. Perhaps I'm wrong in my interpretation, but I envision writing an empty tag value as the tag still has something in it, but it's empty and won't appear. But since there -is- a value there (even empty) it would not show up on a search for missing tags.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 01:12:33 PM
phred, where you are looking for missing tags? and which exactly missing tags?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 08, 2022, 01:33:49 PM
phred, where you are looking for missing tags? and which exactly missing tags?
No, not quite. There have been some occasions where I just want the ability to search for data in a tag (or tags) that is incorrect and delete it. I can't believe I never knew this before (or maybe I knew it and forgot) that there is a native 'remove' tag(s) in the Tools menu. Which will take care of the "project" I'm currently doing.

As for searching for missing tags, that too is in the Tool menu. So I think I totally misunderstood the original request and can't (currently) see any need for it. I would assume that hiccup, who originally requested this, will have more to say about the use of his request.

I appreciate you reaching out to get a better understanding of what I wanted. And no longer need. Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 08, 2022, 02:45:12 PM
Request for new feature or extend current one

In current function repunct it only translate some special characters to some of this
Code
<< " [ ((
Full definition is in AutoLibraryReports.cs rows starts with 827

It is possible to do something similar with letters? For example I want to translate artists like this:
Céline Dion -> Celine Dion (é -> e)
Christina Stürmer -> Christina Sturmer (ü -> u)
Horkýže Slíže -> Horkyze Slize (ý -> y, ž -> z, í -> i)

Maybe this could help with specifying characters
https://stackoverflow.com/questions/18123501/replacing-accented-characters-with-plain-ascii-ones
https://stackoverflow.com/questions/286921/efficiently-replace-all-accented-characters-in-a-string

i've created new asr preset "Transliterate Unicode characters of <Tag 1> to ASCII characters". 'import new' asr presets after updating plugin. you need to install this plugin (https://getmusicbee.com/forum/index.php?topic=37276.0) to use new preset.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 08, 2022, 05:09:08 PM
what do you mean by 'deletion'?
Deleting an existing tag completely.

I was aiming to create a keyboard shortcut that performed a sequence of steps, one being the deletion of a tag.
But I realise that when you remove the contents of a tag, MusicBee will delete that tag at saving.

So I created a preset 'delete tag' that writes 'null' to a tag, so at saving it gets deleted.

Case closed ;-)

off-topic:
Two presets starting with "Generate 'Dispalyed…' have 'Displayed' misspelled.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 09, 2022, 06:33:39 AM
Two presets starting with "Generate 'Dispalyed…' have 'Displayed' misspelled.
thanks, it's fixed
Title: Re: Additional Tagging & Reporting Tools
Post by: codingduo on November 11, 2022, 02:46:40 PM
Thank you boroda for pointing out the issue with the translations! I didn't know that. Deltetd the folder as sugessted and it works now.

Would it possible to increase the amount of assignable hotkeys from 10 to maybe 50? That would be awesome!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2022, 03:40:49 AM
it's not so easy because every hotkey requires dozen of new lines of code in plugin, there is no universal solution (that's how support for hotkeys implemented in mb api). maybe 20 hotkeys is sufficient?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2022, 04:33:29 AM
i've increased the number of asr hotkeys to 20:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: codingduo on November 17, 2022, 07:36:41 PM
i've increased the number of asr hotkeys to 20:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


That's very nice boroda, thank you! That already helps a little. The reason I could need that much hotkeys is, that I have a little controller called StreamDeck. I want to assign my genres and subgenres to its keys, so I can tag my library more quickly. It can send keycommands, therefore my request. I also experimented with an old android tablet and a software called Touch Portal which also allows you to make some buttons on your tablet to trigger hotkeys for example.
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on December 01, 2022, 05:14:38 PM
Hello Boroda,

Is there a way to access the ten possible configurations for "COPY TAGS TO CLIPBOARD" via shortcut?
I currently only see the option of using a shortcut to access the last run and then switch it manually. I think it would be easier and faster to work with direct access. Is just an idea...

Best wishes
adac
Title: Re: Additional Tagging & Reporting Tools
Post by: gaiastar on December 01, 2022, 05:53:07 PM
Hi @boroda

can the plugin work and keep musicbee full portable?
just becase i have a portable version when i have at work
amazing plugin
thanks a lot
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 01, 2022, 06:23:02 PM
Is there a way to access the ten possible configurations for "COPY TAGS TO CLIPBOARD" via shortcut?
I currently only see the option of using a shortcut to access the last run and then switch it manually. I think it would be easier and faster to work with direct access. Is just an idea...
for now, no, there isn't. maybe i'll make this later.

can the plugin work and keep musicbee full portable?
just becase i have a portable version when i have at work
yes, of course. i'm using mb portable (and all my plugins with mb portable) from the beginning.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 01, 2022, 07:52:02 PM
Is there a way to access the ten possible configurations for "COPY TAGS TO CLIPBOARD" via shortcut?
I currently only see the option of using a shortcut to access the last run and then switch it manually. I think it would be easier and faster to work with direct access. Is just an idea...
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on December 02, 2022, 08:03:06 AM
Is there a way to access the ten possible configurations for "COPY TAGS TO CLIPBOARD" via shortcut?
I currently only see the option of using a shortcut to access the last run and then switch it manually. I think it would be easier and faster to work with direct access. Is just an idea...
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


Wow.  :o  With later I thought soon sometime. I've set up two keyboard shortcuts as a test. In some cases, the result from the first process is entered in the field for the second process. Something doesn't seem to be working properly there. can you watch this again

Thank you in advance for your quick and helpful work.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 02, 2022, 01:29:56 PM
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on December 02, 2022, 05:59:16 PM
https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

First of all, thanks boroda, I'll take a look at it again tomorrow. I saw one small mistake. The keyboard shortcuts say "Clipbiard" instead of "Clipboard".
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 02, 2022, 08:31:56 PM
I saw one small mistake. The keyboard shortcuts say "Clipbiard" instead of "Clipboard".
:) it's fixed. redownload plugin from the same link before testing it, because hotkeys will be reset after plugin update.
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on December 03, 2022, 07:23:24 AM
I saw one small mistake. The keyboard shortcuts say "Clipbiard" instead of "Clipboard".
:) it's fixed. redownload plugin from the same link before testing it, because hotkeys will be reset after plugin update.


Unfortunately still the first problem. I'll try to describe it again in more detail. I assigned the first shortcut with ALBUM and a second with TITLE. If I now copy the first one (ALBUM), it will be inserted correctly into another file. If I copy the next (TITLE) now, it will be pasted into the previous field (ALBUM) when I paste it. I also tried it with a third customer (LISTE) and this is also entered under ALBUM. It appears as if the selected field is not set.

By the way, I temporarily copied the data to a text file to check whether the data ended up correctly on the clipboard. Everything seems to have been adopted here.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 03, 2022, 08:05:55 AM
this bug should be fixed now:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on December 03, 2022, 03:15:51 PM
this bug should be fixed now:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

 :-[ Now there is no paste clipboard under keyboard shortcuts


(https://i.imgur.com/Tx15oeM.jpg)

However, it seems to work manually
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 03, 2022, 03:39:21 PM
it's there, but without "Tagging Tools:" prefix:

(https://i.imgur.com/y0mLRU3.png)

i've fixed it:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on December 03, 2022, 04:01:45 PM
it's there, but without "Tagging Tools:" prefix:

(https://i.imgur.com/y0mLRU3.png)

i've fixed it:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


yeah now it's perfect I thank you again for your commitment
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 04, 2022, 02:45:48 PM
I am probably overlooking something very simple, but I can't figure this out at the moment:

I would like to create a function that writes a tag with a pre-defined value.
For example:
tag name: 'New tag'
pre-defined value: 'Some value'

So I am not trying to edit/create something by using some existing tag or values.
I just want to create a new tag with a pre-defined value.
(and have a shortcut for it)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 10, 2022, 05:16:25 PM
I would like to create a function that writes a tag with a pre-defined value.
Is it safe to assume this can not be done?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 10, 2022, 08:26:19 PM
of course, it can be done. go to ASR, find preset "Example: Set tag", either modify it or better copy it and modify the copy: set <tag 1> to your 'New tag', set <custom text 1> to 'Some value', tick 'assign hotkey for this preset' checkbox (DO NOT TICK preset for AUTO APPLYING!), click 'save all & close', and restart mb. after mb restart go to prefs> hotkeys: "Tagging Tools: (magnifying glass): Example: Set tag". assign hotkey to it.

it's somewhat inconvenient and not obvious to assign hotkeys to ASR presets, but it's limitation of mb api  :-\

p.s. sorry for late answer, i don't know why, but several last days haven't been visiting plugin's board.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 11, 2022, 11:07:53 AM
of course, it can be done. go to ASR, find preset "Example: Set tag",
I went through the list of presets multiple times.
I don't understand how I could have missed it. Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 11, 2022, 11:47:39 AM
i've modified plugin, so now it's not required to restart mb to assign hotkeys to asr presets (it turned out that it can be safely done using the current mb api). just tick 'assign hotkey for this preset' checkbox for all required presets, save asr settings (by clicking either 'save all' or 'save all & close' button), then go to edit> prefs> hotkeys. assign hotkeys to asr presets.

it's still required to restart mb if you have UNTICKED 'assign hotkey for this preset' checkboxes for some asr presets, and wanted the changes to take effect.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 11, 2022, 02:28:16 PM
minor bugfixes and improvements, e.g. now asr presets with assigned hotkeys are also shown in both plugin menus (main menu and context menu):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on December 16, 2022, 03:44:19 PM
Hi,
Just updated MB to 3.5.8384 and converting mmm:ss to hh:mm:ss didn't work for some files "syntax error". Went and updated to the latest ATRT version still get "syntax error". Looked at the stock "time" field and it's now set to hh:mm:ss.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 16, 2022, 05:05:53 PM
interesting. could you upload somewhere one of problem tracks? don't upload it to file sharing site, such sites can block downloads if they detect copyrighted tracks. upload track to google drive, ms one drive, etc.
Title: Re: Additional Tagging & Reporting Tools
Post by: iamambuser on December 16, 2022, 05:42:34 PM
interesting. could you upload somewhere one of problem tracks? don't upload it to file sharing site, such sites can block downloads if they detect copyrighted tracks. upload track to google drive, ms one drive, etc.

Mostly I use that for podcasts. Some are longer than 1 hour and MB used to show them as mmm:ss instead of h:mm:ss which annoyed me. Maybe you could try http://feeds.feedburner.com/MarkusSchulzGlobalDJBroadcast since that has 2 hour episodes. When I updated that podcast ATRT showed a blank time field (custom 10 is what was assigned for me). When I tried to manually convert the time in ATRT, it showed a syntax error. It looks like anything over 60 minutes doesn't work.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 16, 2022, 06:51:16 PM
which mb version are you using? because mb 3.5rc2 displays long "time" track property as hh:mm:ss (this is a relatively recent fix made by Steven), so i can't check this issue using your podcast. of course, i get "syntax error!" in this case, as it's not the expected format for that asr preset. i get correct conversion of mmm:ss format by asr preset if i enter that value manually to custom tag.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 20, 2022, 07:22:55 PM
Steven was asked to implement this some time ago. i've done this in plugin: option to store "last skipped date/time". plugin saves it to any writable tag, but i'd recommend saving it to a custom tag.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

install/update plugin, go to mb menu> edit> prefs> plugins> tagging tools> configure. see the button "save last skipped date..." at the bottom of plugin settings window.

Plugin strictly follows MusicBee convention of what is "skipped track".

To define date type of custom tag, open MusicBee menu> Edit> Preferences> Tags (1)> Define New Tags> Configure Fields. Find "Custom1" tag (or some other custom tag), change type to "Date":

(https://i.imgur.com/C1gPwaK.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 27, 2022, 10:03:18 PM
Just throwing this out there:

I must admit that I still don't have a good understanding of what AT&RT is capable of, and more importantly: how to use it's features and what all buttons and options do exactly.
 
Is it just me?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 28, 2022, 04:21:25 AM
do you mean AT&RT or ASR?

all functions of plugin are located in tools> additional tagging tools menu (but one function is in settings window - saving last skipped date, and virtual tag functions are automatic).

short description for every command is located on add-on site page, except for description of saving last skipped date because description on add-on page has 15000 characters limit  :-\

some unimportant functionality descriptions are placed on the 1st page of this topic.

-----

i had tried to make informative tooltips, which appears on mouse-over on buttons/dropdowns/text fields/checkboxes/etc.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 28, 2022, 12:03:48 PM
@boroda-

I just updated AT&RT to yesterday's version (5.5.8.97.) After copying over the presets and the dll I opened MB (3.5.8388) > Preferences > Plugins > AT&RT > Configure. I changed nothing (just checking version number) and clicked 'OK' and MB threw this error. Repeated and clicked 'Cancel" and got the same error. I shut down MB over installed the dll and presets from v5.4.8380 and the error no longer appears.

MusicBee v3.5.8388.32476P  (Win10.0), 28 Dec 2022 6:55:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidOperationException: Instance validation error: '0' is not a valid value for MusicBeePlugin.Plugin.MetaDataType.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterSavedSettingsType.Write5_MetaDataType(MetaDataType v)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterSavedSettingsType.Write8_SavedSettingsType(String n, String ns, SavedSettingsType o, Boolean isNullable, Boolean needType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterSavedSettingsType.Write9_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()
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=z1mgrv$_$6GN1Y3k46g==.#=zbm0_O3k=(IntPtr #=z4UJlY40SuO_w)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 28, 2022, 03:02:06 PM
thanks, phred. it's fixed:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 28, 2022, 05:47:14 PM
thanks, phred. it's fixed:
Confirmed as fixed. Thanks boroda!
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 30, 2022, 07:16:19 PM
do you mean AT&RT or ASR?
It was a rather unspecific and general spur-of-the-moment remark.
Probably triggered by the fact that I realised that I don't have a good understanding of all the elements in the user interface.
But for a part it's also a more general observation.
For example, while 'Advanced Search & Replace' is well-known and familiar, there also is a 'Multiple Search & Replace' feature.
I never even clicked that one because I have no clue about what that does or why I would use it.

More specific about the AS&R panel:
Here's a screenshot containing some highlighted elements.
These are buttons that I have never clicked, because I have no idea what they do, and/or what the differences are between similar named buttons.

(https://i.imgur.com/b1cGdJa.png)

Again, my comment was rather vague and un-directed, probably a bit lazy, and maybe not very helpful.
And the fact that nobody else voiced any sort of agreement on my observation probably means it's just me.

But still hopefully somebody will one day write: Additional Tagging & Reporting Tools for Dummies.
It surely would help me.

P.S.
Even though you there is a comment in CAPITALS about it, I still feel that it should be more clear what the check boxes in front of the functions mean.
It is a function that can very easily raise havoc on a music library. (it has happened to me too)
There is no tool-tip when hovering over them, and no pop-warning when you have activated one.
Most users of AT&RT probably have learned what that does the hard way?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 30, 2022, 08:47:19 PM
1. "star" button will enter "star" char in search text box. this will show only presets, which have "star" char in their name (i.e. presets, which have assigned hotkeys).

i had to make (and will make) explanation tooltip for this button.

2. you can assign virtual tag function id to any preset, and use this preset in virtual tags, file naming templates, etc. as $ASR(<URL>,preset_id).

note: this option may be useful for simple asr presets, but it will return last changed tag for complex (multistep) presets, what may be not very obvious in this case.

3. asr preset ("skip input values" option is per preset option) won't change any tag (i write "any tag" because some presets have several steps, which can change different tags) if this tag exactly equals to one of the values (separated by ";;") enumerated in this field.

example: you try to apply "sentence case" preset to change "album artist" tag of several tracks, and one of tracks has "UB40" album artist. you enter "UB40" in "skip input tag" field, and all album artist tags, except for "UB40", will be sentence cased.

i had to make (and will make) explanation tooltip for this field.

4.A. "export" button will export selected (custom or customized predefined - with changed <tag 1>, <tag 2>, <custom text 1>, etc.) preset to the folder of your choice. this button has good toolip.
4.B. "export custom" button will export all custom (NOT selected, NOT customized predefined) presets to the folder of your choice. this button has good toolip.
4.C. "import" button will import any exported earlier (by you or by some other user) presets from the folder of your choice (you will be able to select individual presets from this folder). this button has good toolip.
4.D. "import new" button will import new and updated predefined (if any) presets after updating plugin. it won't change customized predefined presets. this button has good toolip.
4.E. "delete" button will delete any selected preset. this button has good toolip.
4.F. "delete all" button will delete all predefined presets, but won't delete any custom presets. this button has good toolip.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 30, 2022, 09:16:32 PM
i've added a couple of new tooltips to asr buttons/fields.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 31, 2022, 03:04:49 AM
@boroda-

Having the top line of the AS&R window ("Select preset below to edit ...") show a different color (blue in my case) when there are presets that are ticked is a great feature. It would be even better if the user could click on that blue line and have the window show -only- the ticked presets. The way it works now is that I have to scroll through all presets to find the ones that are ticked.

This screenshot from another thread "implies" that my request is already the way AS&R behaves:
(http://i.imgur.com/hAGVLVBl.jpg) (https://i.imgur.com/hAGVLVB.jpg)

Yet this is mine:
(http://i.imgur.com/9RYtjsMl.jpg) (https://i.imgur.com/9RYtjsM.jpg)

Also, the box with the 'X' at the far right of that line looks like it's one pixel short at the right side of the box as it's missing the right side vertical line.
(http://i.imgur.com/zLK8p6Hl.jpg) (https://i.imgur.com/zLK8p6H.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 31, 2022, 03:30:25 AM
the checkbox to the left of "star" button is checked on my screenshot, but not on your screenshot. that's why only ticked presets are shown on my screenshot, but not on yours.

so you don't need to scroll through all presets to find ticked ones.

but i believe that clicking on highlighted warning text to show only ticked presets in addition to that checkbox is a good idea. i'll make this.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 31, 2022, 03:49:34 AM
the checkbox to the left of "star" button is checked on my screenshot, but not on your screenshot. that's why only ticked presets are shown on my screenshot, but not on yours.
And you even have a tool tip on that check box. <sigh>

Quote
but i believe that clicking on highlighted warning text to show only ticked presets in addition to that checkbox is a good idea. i'll make this.
Not necessary for me now that I've seen the error of my ways. I do think it will help others who come along ignoring the check box like I did. Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 31, 2022, 08:22:10 AM
A question about installing/updating:

When installing AT&RT I use the Plugins > Add plugin… button.
For updating I close MB, then copy the downloaded mb_TagTools.dll over to MBs Plugins folder to overwrite the existing dll.

But I notice the download also contains a folder named 'ru' that contains mb_TagTools.resources.dll
But there is no 'ru' folder, nor mb_TagTools.resources.dll to be found in my MB install.

Should that file also be used in some way when updating to a new AT&RT version?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 31, 2022, 01:47:13 PM
Should that file also be used in some way when updating to a new AT&RT version?
I've always assumed the RU dll has something to do with the Russian language. Perhaps a translation of the .dll. Obviously boroda will let us know.

However, the method I use to update is to open the ZIP and drag the (first level) dll to MB's pluglin folder. I then drag the zipped ASR Presets to MB's AppData folder. In both cases allowing the originals to be overwritten. I have never had nor used the RU .dll.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 31, 2022, 11:00:38 PM
@phred, you are right. 'ru' folder always contains the only file 'mb_TagTools.resources.dll', it contains russian localized strings. everybody can safely delete this file to always use english localization, but this file won't be used anyway, if windows regional settings are not russian.

'asr presets' folder is supposed to be copied either to folder mb folder\plugins\ or to folder mb appdata folder\plugins\, depending on how you have installed plugin (manually in 1st case or by using 'add plugin' button in 2nd case). after updating plugin you need to open asr and either 'import all' or 'import new' asr presets. 'import new' button also preserves any customized predefined presets.

you can copy 'asr presets' folder from plugin zip directly to mb appdata\ folder, but you won't be able to (re)install only updated asr presets in this case, not overwriting customized predefined presets.

--------------------------

i've improved asr ui/ux. now you must double-click preset to tick/untick it. this prevents presets from accidental ticking. warning sound is played if you have ticked preset. tool tip over warning text at the top part of asr window is now more informative. now you can click warning text to show only ticked presets. and some more minor enhancements.

(https://i.imgur.com/23II6bK.png)

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

--------------------------

HAPPY NEW YEAR TO ALL FORUM MEMBERS!
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 01, 2023, 03:33:17 PM
HAPPY NEW YEAR TO ALL FORUM MEMBERS!
The same to you boroda.
And thanks for continuing development and support for your plugin.

While the (new) pop-up explanations are certainly nice and useful, I think ideally a user interface should by itself be as self-explaining as possible.
The new double-click feature of checkboxes certainly adds a layer of security in preventing user errors, which is good.
But it's not standard behaviour for checkboxes, so it's not something a user would expect.

Thinking out loud: perhaps instead of having this double-click restriction, have a new text field/pane right beneath the presets panel, that as soon as there are auto-applied presets active, displays something like: "Warning: you have one or more presets active that will automatically apply changes to your tags when files are edited or updated"
(I'm not sure about the "edited or updated" part in that sentence. Does that indeed describe when AT&RT will perform its magic?)

And when a user checks (adds) another preset, perhaps a brief pop-up saying something like "preset will now be applied automatically to files in your library"

P.S.
The new audio warning may be helpful for some too, but personally the first thing that I do after installing AT&RT is going to preferences and uncheck the one 'Sounds' option that is checked by default.
It's pretty much the first thing I do for any and all programs that I use, including Windows itself.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 01, 2023, 04:03:57 PM
And another observation…

The buttons on the left pertain to presets. Perhaps give them a separate header saying so? (something like 'preset management')
The buttons on the right would affect processing the preset on files, right?
But what about a button like 'Delete all' that is on the right?
Shouldn't that one be together with the ones on the left?

(https://i.imgur.com/iOeuVc3.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 01, 2023, 04:34:24 PM
And thanks for continuing development and support for your plugin.
Yes. Thank you boroda for the greatest MB plugin and for the continued improvements.
And wishing all forum members good health and good times in 2023 and beyond.

While I haven't had time to test the latest improvements to AT&RT, I do want to offer up a comment or two based on what hiccup has stated.

Since any audio I listen to via my PC is through headphones, I also immediately disable all Windows/Applications sounds upon installation. The audio warning may be helpful for some, but it won't do me any good. Nor will it help hiccup.

I have often been the victim of not realizing I have clicked a preset's checkbox and all of a sudden experiencing unexpected behavior. Double-clicking -may- prevent that, but I also think a visual warning would be better. I often double-click on things that don't need to be double-clicked. My suggestion would be to take the top line of the AS&R window ("Select preset...") and split it into two lines. The first being the current first sentence, which would also be there. Then on a (new) line underneath, something like "Some presets have been activated and will be automatically applied. Tick the box to see which ones are active." Obviously this warning should only appear if the user has presents enabled.

I think a combination of what I suggested above (which basically is a static warning) and a brief popup warning when a preset is ticked/double-clicked would make it very clear that a preset will be automatically applied.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 01, 2023, 04:54:57 PM
I think a combination of what I suggested above (which basically is a static warning) and a brief popup warning when a preset is ticked/double-clicked would make it very clear that a preset will be automatically applied.
Which I believe is what I just suggested.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 01, 2023, 05:01:54 PM
Which I believe is what I just suggested.
Yes, pretty much. But I felt verbal and didn't want to simply plus one it.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 01, 2023, 05:05:56 PM
Which I believe is what I just suggested.
Yes, pretty much. But I felt verbal and didn't want to simply plus one it.

Ok, then I will +1 your proposal, which was my proposal.
(probably the first time I am +1'ing myself ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 01, 2023, 06:48:36 PM
hiccup, phred, not exactly what you described, but something close to it:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

p.s. playing sound on asr preset ticking now can be disabled in plugin prefs.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 01, 2023, 07:30:34 PM
i've changed the casing of warning text and tool tip over it. download link is the same.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 01, 2023, 08:16:04 PM
I'm not sure. (from a 'commonly understood' user interface point of view)

The text at the top (Select preset below to…) is an explanatory text which is helpful.
But later on it changes its function to be some sort of status indicator.
To me that's a bit ambiguous. I feel it should either be a helpful text, or an indicator of current operations.

Here a mock-up of what I was thinking of:
(https://i.imgur.com/36Jecuk.png)
And when no preset is activated just have it grayed-out saying something like "no active prests".

And I still think checkbox behaviour should be single-click.
MusicBee itself also has some features that could have unwanted (not understood) consequences that can be activated by clicking a checkbox.
It then also warns with a pop-up balloon. It doesn't make it more difficult by requiring a double-click that nobody would expect for a checkbox.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 01, 2023, 08:50:59 PM
Here a mock-up of what I was thinking of:
(https://i.imgur.com/36Jecuk.png)
And when no preset is activated just have it grayed-out saying something like "no active prests".
i'll leave it as is for now. very big problem is insufficient space in ASR window. i was always trying to keep this window as much compact as possible.

And I still think checkbox behaviour should be single-click.
MusicBee itself also has some features that could have unwanted (not understood) consequences that can be activated by clicking a checkbox.
It then also warns with a pop-up balloon. It doesn't make it more difficult by requiring a double-click that nobody would expect for a checkbox.
that's where the main problem comes, and that's why i've changed ticking checkboxes to double-clicking. standard .net behavior of a list with check boxes is not only to change checked state on clicking inside a checkbox, but also to change this state on single-clicking anywhere on the line of the list. it was too easy to accidentally tick a checkbox.

i've changed button placements in ASR window:

(https://i.imgur.com/rfV95kJ.png)

download link is the same.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 01, 2023, 09:43:36 PM
well, ok. it turned out not be difficult to limit ticking presets to checkboxes only. now single-clicking is required instead of double-clicking, but mouse click must be inside checkbox to tick/untick preset.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 01, 2023, 09:50:28 PM
now single-clicking is required instead of double-clicking, but mouse click must be inside checkbox to tick/untick preset.
Thanks boroda (and hiccup for expressing my thoughts.)

Overall I think these changes will keep me (and others) from inadvertently enabling presents. The one thing I've noticed, and I think this goes back many versions, is that ticked presets do not remain persistent throughout -version- changes. And yes, I do exit AS&R by clicking "Save all & Close."

BTW: showing the number of presets ticked is a nice touch.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 01, 2023, 10:51:59 PM
The one thing I've noticed, and I think this goes back many versions, is that ticked presets do not remain persistent throughout -version- changes. And yes, I do exit AS&R by clicking "Save all & Close."
yes, auto-applying option is stored in preset file. try to always 'import new' presets instead of copying them directly to 'mb appdata\asr presets' folder. another approach is to always turn this option on to copied predefined preset instead of original one. this problem doesn't exist for user created presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 01, 2023, 11:23:44 PM
try to always 'import new' presets instead of copying them directly to 'mb appdata\asr presets' folder
Okay - I've got to get into the habit of doing this. Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 02, 2023, 11:42:18 PM
new plugin version.

ASR improvements:

* now all ASR settings (including any created/changed/imported/deleted presets) are saved only by clicking "save all" or "save all & close" buttons. previously some changes were saved even on closing ASR window by clicking "cross" button in window title bar.

* auto-applying and hotkey assignment options are moved from preset files to plugin settings file. these option will be preserved on any preset updates by any of the ways (@phred, it's what you asked).

MSR improvements:

* MSR presets for ASR now can be deleted/renamed/set for auto-applying (and created as it has been already earlier) directly in MSR window.



https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 03, 2023, 04:28:09 AM
@boroda-

I don't know how you continue to do it, but you've taken what started out as a very helpful and great plugin, and made it even greater!!!

Full disclosure: I haven't had time to install this new update yet, but will have time tomorrow.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 03, 2023, 07:13:21 AM
some bug fixes of last version, and code refactoring:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 03, 2023, 04:03:53 PM
I'm not able to do in-depth testing, but I am noticing issues with the latest update.

- when using keyboard shortcuts for AT&RT presets, sometimes the wrong preset gets applied

- importing presets doesn't work
  (maybe due to to a discrepancy between the use of ".asr-preset.xml" and "ASR Preset.xml"?)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 03, 2023, 05:58:09 PM
- importing presets doesn't work
If I'm doing this correctly, I can confirm that importing presets does nothing.

I copied over the .dll to the plugins directory > opened MB > opened AS&R > import all and nothing happens. And the previously ticked presets were not kept ticked.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 03, 2023, 06:06:30 PM
- when using keyboard shortcuts for AT&RT presets, sometimes the wrong preset gets applied
i'll look at it.

- importing presets doesn't work
  (maybe due to to a discrepancy between the use of ".asr-preset.xml" and "ASR Preset.xml"?)
now only presets having new format are imported if any of them exists in import folder ("plugins\asr presets"), old format presets will be imported if no new format presets exist in that folder. just delete all old format presets from "pluins\asr presets" folder. presets in "appdata\asr presets" folder will be auto-converted to new format on any preset saving inside ASR. "import new" now is having very strict meaning, i.e. no presets, which content is not updated since last import, will be imported. "import all" should work as usual.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 03, 2023, 06:11:16 PM
some bug fixes of last version, and code refactoring:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file


@phred, hiccup, have you redownloaded fixed version from that my post?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 03, 2023, 07:41:42 PM
@phred, hiccup, have you redownloaded fixed version from that my post?
Yes, I downloaded from the link in Reply # 2761.

I have no "ASR Presets" under the Plugins directory after trying the new version and running "import all" and "import new." My presets are in, and have been in, MusicBee\AppData\ASR Presets. The ZIP contains 111 presets. I have 8 custom presets. There are a total of 119 presets in AppData\ASR Presets.

I  will download again and report back.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 03, 2023, 08:47:20 PM
I have no "ASR Presets" under the Plugins directory after trying the new version and running "import all" and "import new." My presets are in, and have been in, MusicBee\AppData\ASR Presets. The ZIP contains 111 presets. I have 8 custom presets. There are a total of 119 presets in AppData\ASR Presets.
both "importing" buttons will import ASR presets only from "mb folder\plugins\asr presets" folder or from "mb appdata\plugins\asr presets" folder. you may not import presets at all (no new presets are included in latest plugin zip). old format presets should be working fine, and they will be automatically converted to new format if you open ASR, and click "save all" or "save all & close". but conversion of presets to new format is not necessary.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 03, 2023, 09:00:06 PM
@phred:  close mb, backup all your presets, delete all presets having new format (*.asr-preset.xml) from "mb appdata\asr presets" folder, open mb, open ASR, click "save all". all your presets including custom presets will be converted to new format.

in the future, you can update the plugin and asr presets in any way you find convenient.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 03, 2023, 09:04:55 PM
@phred:  close mb, backup all your presets, delete all presets having new format (*.asr-preset.xml)

in the future, you can update the plugin and asr presets in any way you find convenient.
Great minds think alike. I just did as you suggested and all the presets are converted and present. There is one custom preset that won't import or convert. Would you be willing to take a look at it? I can zip it and upload it to MediaFire. No rush whatsoever.

Everything else seems to be working as expected. Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 04, 2023, 03:42:30 AM
@phred, i've made various bug fixes.

hotkeys must be handled correctly now.

also, any mixture of old format and new format presets can be either placed directly to "mb appdata\asr presets" folder (it's working folder for ASR), or copied to one of possible installation folders: "mb install folder\plugins\asr presets" or "mb appdata\plugins\asr presets", and then imported in ASR.

in case, if there are some duplicated presets (e.g. one "old format" preset and one "new format" preset) the duplicates will be automatically removed.

phred, try to convert the problem preset by new plugin version, but if new version also fails, then pm this preset.



https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 04, 2023, 04:04:22 AM
phred, try to convert the problem preset by new plugin version, but if new version also fails, then pm this preset.
I'll give this newest version a shot tomorrow and let you know if the preset automatically converts. The problem so far has been when I imported -all- the presets (stock and custom) all but the problem one installed and ASR threw a "one preset did not import" (or something close to that.) No matter what directory I place the problem custom preset it hasn't imported automatically. When I click 'import' and navigate to the folder where it is, the file picker doesn't show it because the picker is looking for ".asr-preset.xml" while the problem file is ".ASR Preset.xml"

I'll get back to you tomorrow.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 04, 2023, 02:17:06 PM
Using 5.5.8404 I extracted the dll and placed it in the plugins directory. I then placed the problem custom preset in \AppData\ASR Presets. Note that this has an extension of .ASR Preset.xml. I opened MB, opened ASR and clicked on "import new" and got this error. Note that it's looking for the presets under the Plugins directory, while your most recent reply states they could go under AppData.
(http://i.imgur.com/2qWU3eLl.jpg) (https://i.imgur.com/2qWU3eL.jpg)

I noticed that while the time stamp on the problem preset had not changed, the extension did change to .asr-preset.xml, so I selected 'import' and got this error:
(http://i.imgur.com/Tp81EuJl.jpg) (https://i.imgur.com/Tp81EuJ.jpg)

I then moved MusicBee\AppData\ASR Presets to \MusicBee\Plugins\ASR Presets, I placed the problem preset, with its original extension (.ASR Preset.xml) in the "new" presets directory and launched MB, followed by opening ASR which showed no presets. I clicked 'import all' and 117 of the 118 presets were imported. The one that did not import is the problem one. And this time the file extension did not change to the new format.

With the presets in Plugins\ASR Presets each time I launch MB and open ASR the presets are missing and I have to 'import new.' [EDIT: This may be because I failed to 'Save All & Close'] For the time being, I moved them back to under the AppData directory and things are back to the way they were.

I will upload the problem preset to MediaFire and PM the link to you shortly.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 04, 2023, 11:39:17 PM
@phred, actually, there still was one bug related to preset import. it's fixed.

also, i've fixed one bug related to "copy tags to clipboard" command.

preset files naming is changed. now preset filenames are generated from preset friendly name rather than preset GUID. but some special characters (illegal for filename) in preset name can be removed or replaced by other characters on generating preset filename.

p.s. i've received your pm, and will look at problem preset soon.

-------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 04, 2023, 11:55:21 PM
@phred, your "problem" preset is an exact copy of the predefined preset:

Extract artists from track title and add them to the 'Artist' tag - 'Title <Custom text 1> <Artist1> <Custom text 2> <Artist2>' format

i see no differences. but if you still want to import/convert it, just click "import" button in ASR window (not "import new", not "import all"), browse to the folder with your exported or backed up preset, and enter "*.*" in filename field at the bottom of file open dialog (to show ALL files of ANY type in selected folder). this way you can import both new format and old format presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 05, 2023, 03:56:41 AM
@boroda-

.8405 has resolved everything. Changing the filenames to "user-friendly" filenames is a great change.

I am pretty sure I got the "problem" present from someone who posted it here in this thread, but I may be mistaken. The fact that it is an exact duplicate of a stock preset took the pressure off me fighting to get in installed. Thanks for the *.* tip with the file picker.

Once again, keep up the great work.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 05, 2023, 04:33:12 AM
I am pretty sure I got the "problem" present from someone who posted it here in this thread, but I may be mistaken.
it's very likely it was me  :) (i'm not sure, though). and later, i have added it to predefined pack, because it was more useful than original preset:

Extract artists from track title and add them to the (Guest) 'Artist' tag - 'Title <Custom text 1> <Artist1> <Custom text 2> <Artist2>' format
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 05, 2023, 02:50:07 PM
Hmm... just updated to .8405 and none of the hotkeys for presets (normal or custom) seem to work.  I deleted them all (and verified that they were removed from the hotkey-list), then re-added them (the usual way), and they reappeared in the list as expected, and I assigned keys to them again.

But nothing happens to selected items when the hotkeys keys are hit.  The presets work fine when used manually from the ASR screen itself, but not via hotkeys.  I've restarted MB multiple times (with and without the plugin to refresh it), but nothing seems to help.

They all worked fine before you went mad on this recent updating binge.  :)

And while I'm thinking of it, would it be possible for ASR to show a message on MB's status-bar when a hotkey is pressed (like "ASR: Applied Lower-Case Preset" or something daft like that)?  I have a few custom presets which modify things (custom tags) which have no visual cues when changed, and having a message would give the user an indication that something actually happened.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 05, 2023, 05:31:58 PM
hotkeys must be handled correctly now.
Not for me, a wrong preset still sometimes gets triggered, and some preset hotkeys don't work at all.

P.S.
Could you provide a download link to the last December version?
I don't have it anymore and would like to use it until these issues are resolved.

edit:
The results of this 'test set' I am using might be helpful in figuring things out:

(https://i.imgur.com/njFRcHa.png)

(https://i.imgur.com/u4B6jFS.png)

Ctrl+1 triggers rating to ★★ (instead of ★)
Ctrl+2 triggers rating to ★★★ (instead of ★★)
Ctrl+3 triggers rating to ★★★★ (instead of ★★★)
Ctrl+4 triggers rating to ★★★★★ (instead of ★★★★)

Both Ctrl+5 and Ctrl+0 do nothing
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 05, 2023, 07:45:32 PM
Could you provide a download link to the last December version?
In an attempt to save boroda a little time, here is a link to mb_TagTools_5.5.8400 which I believe is the last release of 2022..
https://www.mediafire.com/file/hsvrof59i5x1k5p/mb_TagTools_5.5.8400.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 05, 2023, 08:01:23 PM
Could you provide a download link to the last December version?
In an attempt to save boroda a little time, here is a link to mb_TagTools_5.5.8400 which I believe is the last release of 2022..
Thanks phred! My presets are working fine again with this version.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 05, 2023, 08:14:08 PM
Thanks phred! My presets are working fine again with this version.
Happy to help.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 05, 2023, 08:58:17 PM
And while I'm thinking of it, would it be possible for ASR to show a message on MB's status-bar when a hotkey is pressed (like "ASR: Applied Lower-Case Preset" or something daft like that)?  
this had been implemented from the beginning, but the status-bar message was cleared after applying ASR preset, and became unnoticeable if you apply preset to only a few tracks (it was cleared too quickly). i've removed status-bar message clearing.  

Hmm... just updated to .8405 and none of the hotkeys for presets (normal or custom) seem to work.  I deleted them all (and verified that they were removed from the hotkey-list), then re-added them (the usual way), and they reappeared in the list as expected, and I assigned keys to them again.

Not for me, a wrong preset still sometimes gets triggered, and some preset hotkeys don't work at all.

it's even strange that it somehow worked ever at all. there was a blunder. internal counter of all hotkeys was shifted by 1, and this internal counter very vaguely related (and relates, it's by design) to any display order of presets/hotkeys. i hope, it's fixed:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 05, 2023, 10:07:52 PM
I'm glad my example seems to have been useful to solve the issue indeed.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 05, 2023, 11:37:40 PM
Well, almost solved: the hotkeys invoke the correct preset, but only to the first selected item; if I select 11 songs to tag, the first is processed as expected, but the other 10 are ignored. :(
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 05, 2023, 11:59:57 PM
Well, almost solved: the hotkeys invoke the correct preset, but only to the first selected item; if I select 11 songs to tag, the first is processed as expected, but the other 10 are ignored. :(
Confirmed, same here.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 06, 2023, 02:29:24 AM
I'm glad my example seems to have been useful to solve the issue indeed.
yes, thank you for your observations.

Well, almost solved: the hotkeys invoke the correct preset, but only to the first selected item; if I select 11 songs to tag, the first is processed as expected, but the other 10 are ignored. :(
another very stupid bug is fixed:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

we are getting closer and closer to the stable version  ;D
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 06, 2023, 06:28:56 AM
i've marked this as a beta because of insufficient testing, but actually i've just made some code refactoring and now status bar messages about (auto)applied preset(s) are cleared after 5 secs:

https://www.mediafire.com/file/m6jo0wczobidwkp/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 07:48:32 AM
Thanks for this - hotkey problems appear to be fixed.  And thanks for the status-messages, not too obtrusive and much more informative than just "hoping something happened".  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 06, 2023, 07:55:42 AM
And thanks for the status-messages, not too obtrusive and much more informative than just "hoping something happened".  :)
do you mean "beta" (where messages disappear after 5 secs) or "latest" version?
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 08:30:29 AM
As I just downloaded it, I'd assumed they were one and the same thing (.8406).

Honestly, I think 5 seconds to be a bit short, considering if you apply a preset to (for example) a thousand files at once, the message doesn't show up until after the task is done (which can take up to 5 or 10 seconds), so immediate notification would be my preference (with longer display time) - but I doubt many users regularly do that sort of thing.  (It works, that's the main thing!)

If you can stand yet another comment about the UI... my 2-cents suggests that having 3 different "import" buttons is not great design (don't worry, I've developed tools myself and I know it's impossible to keep users happy about UI design, so it's not a criticism, just an observation).

However, now that you've settled on single-click to activate checkboxes, it'd be nice if double-click could be employed for "Rename / Edit", as that's a function I use most and searching for a button (impractically placed next to "Delete") to edit something repeatedly (as happens with RegEx's!) was always awkward.  It's also generally the default for list-view d-click's.  But again, it's not a criticism - maybe others don't spend as much time editing presets as I do.  ;)

But yeah, three different imports?  Behind hiccup's observations that ASR had a somewhat confusing interface, I'd say it can border on downright intimidating for newcomers despite your best efforts (the new tooltips are welcome, though, as is the move away from CLSID nomenclature!).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 08:55:31 AM
And throwing out another thought:

When you use the 'proper' way to install AT&RT (Preferences > Plugins > Add Plugin...), no presets are placed in any folder in MusicBee's installation path.
So the buttons 'import new' and 'import all' simply won't work.
If possible I think it would be good when installing AT&RT, the presets were placed in a location within the MusicBee installation folder so that these import functions will work without the need to learn and understand you should copy them first yourself to some location.

And I agree with Messiaen that three import buttons seem a bit much.
Perhaps just have one, that after clicking provides some options on what to import (and from where)?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 10:12:50 AM
2. you can assign virtual tag function id to any preset, and use this preset in virtual tags, file naming templates, etc. as $ASR(<URL>,preset_id).
note: this option may be useful for simple asr presets, but it will return last changed tag for complex (multistep) presets, what may be not very obvious in this case.
I have read this a couple of times, but I still don't think I understand this feature.

(https://i.imgur.com/hlnpzUh.png)

1.
Is it so that this makes it possible for a preset to use the output of an existing virtual tag, or the other way around, a virtual tag being able to use the output of a preset?

2.
What would you enter exactly in the entry field? The name of an existing virtual tag? Some unique text of your own choice?

3.
What does the (pointed at) button do?

4.
So $ASR is a function that can be used for virtual tags?
Should I then add it here?:
https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257

edit, I now see $ALR and $ASR are explained in the readme on the plugins page.
So maybe I should learn to read readme's ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 10:58:47 AM
$ASR and $ALR are both fantastic functions.  I'll give a couple examples of how I've used them.

Say I wanted to embed a 0-width space in a virtual function (yes, I know, "But why?" - have patience :))... I'd first create a preset which looks like

Search for: ^(.*)
Replace with: \@char[[200B]]

In the "Assign virtual function id", I would just enter "0Width", which can then be used in a virtual expression like:

$IsNull(<Playlist>,,{color: 128,255,255}$ASR(<URL>,0Width))<Title (vf)>

The effect is that the embedded 0-Width Space character actually "activates" the {color} code, allowing <Title (vf)> to be one colour or another, whereas without the 0-Width Space just using <Title (vf)> in a conditional virtual expression the {color} doesn't activate for any following text.  (If that makes sense.)

An even better example (which I imagine Boroda would find amusing) is in the use of $ALR.  Say I wanted to store the length of a classical "work" (as the sum of individual movements), I would first define an Auto-Library-Report as:

<Grouping>: Album Artist, Album, Work, Sum(Time) -> Save Field: Sum(Time)

and assign that ALR a virtual function ID of "SetWorkDur".

Then create the ASR preset that looks like this:

Search for: ^(.*)
Replace with: \@eval[[$IsNull(<Work>,"0:00",$ALR(<URL>,SetWorkDur))]]

where the result is assigned (conditionally!) to a custom tag <Work Duration (c)>.

This allows me to set a hotkey to the ASR (since ALR's don't have hotkeys), and I can apply it on an ad-hoc/one-off basis, instead of it being used as a normal ALR auto-executed command.

So... yeah.  A little complex, but infinitely useful once you get the hang of it.  I actually meant to request Boroda export the \@char[[]] function as a full virtual $Char() function (since none of the usual \xnnnn regex codes seem to work as they should), but I found the use of the virtual ID name easier to use than remembering the code for 0-width space to begin with.  Unfortunately I have to create a new preset for each unicode character I need (hence $Char makes sense), but the "Assign virtual ID" code makes it recognisable in a complex expression.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 11:08:51 AM
I will freely admit that I have absolutely no idea what that extra checkbox-type thing does.  :)

A result of the <Work Duration (c)> example can be seen used in the picture from this post: https://getmusicbee.com/forum/index.php?topic=37692.0 (https://getmusicbee.com/forum/index.php?topic=37692.0)  Note the display at the end of the <Work> headers.  (By the way, hiccup, I got the idea for these sorts of things from reading your expansive posts on how to promote classical music collections, so it wasn't all in vain.  Cheers for that.  ;) )
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 11:20:02 AM
$ASR and $ALR are both fantastic functions.  I'll give a couple example of how I've used them.
Thanks Messiaen! These are great explanations and examples.
This has been untreaded territory for me, this was very helpful.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 11:30:26 AM
I will freely admit that I have absolutely no idea what that extra checkbox-type thing does.  :)
It must be making the function some place of interest ;-)
⌘ https://unicode-table.com/en/2318/
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 12:00:13 PM
4.
So $ASR is a function that can be used for virtual tags?
Should I then add it here?:
https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257
Answering myself: Yes, you probably should.
As a brief explanation I am thinking of this:

- - -
$ALR(<URL>,function_id)

$ASR(<URL>,preset_id)

These functions make it possible to use and integrate ALR (Auto Library Reports) and ASR (Advanced Search & Replace) presets in virtual tags.
- - -

Would that be a correct description?
Any suggestions for better wordings or other improvements?

(since the functions are rather complex I won't explain them further in the cheatsheet, but create links to the plugin page (README) and to Messiaen's explanation and examples)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 12:25:15 PM
Would that be a correct description?
Seems pretty succinct to me... though either way it requires a bit of trial-and-error before one finds that elusive "A-Ha!" moment when using them.  ::)

(Slightly aside, for me discovering the \@eval[[]] function was a revelation in the real use of ASR/ALR Virtual ID's, but that wouldn't belong in your guide as it's plugin-specific.  "But Daddy, you can't put a universe inside a universe inside another universe - I'd be scared of falling in!")
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 12:53:31 PM
(Slightly aside, for me discovering the \@eval[[]] function was a revelation in the real use of ASR/ALR Virtual ID's, but that wouldn't belong in your guide as it's plugin-specific.
Yeah, that falls outside the scope and intention of the cheatsheet.
But as I said, I will add a link to your explanatory post here.
So if you feel like it, you could always edit that post and add more interesting stuff like these advanced functions to it?
Or write and publish an "AT&RT for Dummies" book ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 01:59:08 PM
So if you feel like it, you could always edit that post and add more interesting stuff like these advanced functions to it?
Yeah, I kind of have already, but it just gets messy trying to over-explain something so arcane in excessive detail.  Things like that are best left to immediate use-case questions, like "How do I just make it go forward?"  (When I discovered horses didn't come with automatic break-systems the romance of riding became somewhat tarnished, if you know what I mean; Snooker is one of those games that's much easier to play on telly than it is in real life.)  ;)

Or write and publish an "AT&RT for Dummies" book
My forays, trisques, and self-effacing callumnies combined with irrepressible sesquipedalianesque tendencies towards longwindedness would scupper that particular lyrical essay before I even finished the frontispiece.  ;)  <Cough>

Seriously though, considering AS&RT is (at its core) a Reg-Ex meister's wet-dream, it's no small task making it beginner friendly, never mind dumbing it down to being actually practical (like the fun Boroda's having making the UI ergonomically viable with well-meaning hecklers like us in the audience).  I help where I can, but I'm still learning myself.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 06, 2023, 02:07:50 PM
My forays, trisques, and self-effacing callumnies combined with irrepressible sesquipedalianesque tendencies towards longwindedness would scupper that particular lyrical essay before I even finished the frontispiece.  ;)  <Cough>
You are smoking a pipe, right?
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 02:25:44 PM
You are smoking a pipe, right?
If you've ever read The Decline and Fall of the Roman Empire by Edward Gibbon, it's a paraphrastic play on his 18th-century style of writing.  Who said you can't mix abstruse tech with a little cultural entertainment? No pipes necessary, though phred is going to scold us for going too far off-topic soon.   :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 06, 2023, 08:13:16 PM
Honestly, I think 5 seconds to be a bit short, considering if you apply a preset to (for example) a thousand files at once, the message doesn't show up until after the task is done (which can take up to 5 or 10 seconds), so immediate notification would be my preference (with longer display time)
the problem is that preset can be applied conditionally (only if tracks belongs to some auto or regular playlist), so it's impossible to show a status bar message before applying preset. but i've increased displayed time to 10 sec.

https://www.mediafire.com/file/m6jo0wczobidwkp/mb_TagTools_beta.zip/file

However, now that you've settled on single-click to activate checkboxes, it'd be nice if double-click could be employed for "Rename / Edit", as that's a function I use most and searching for a button (impractically placed next to "Delete") to edit something repeatedly (as happens with RegEx's!) was always awkward.  It's also generally the default for list-view d-click's.  
again, there is a problem. predefined presets can't be edited, and most users won't create custom presets. what do you think, maybe it's worth to edit custom preset and edit the copy of predefined preset (there may be warning dialog shown asking to edit the copy) on double-clicking?

When you use the 'proper' way to install AT&RT (Preferences > Plugins > Add Plugin...), no presets are placed in any folder in MusicBee's installation path.
So the buttons 'import new' and 'import all' simply won't work.
the proper way is to manually copy plugin zip content to "mb folder\plugins". just because "add plugin" button had been added to mb relatively recently, AND plugin can't be UPDATED via "add plugin" button (i've asked Steven to implement full support for installing/updating/removing plugins by the means of mb, without manually copying/deleting any files. maybe he will make this for mb 3.6).

but anyway, what you have written is not the case already a couple of days. now plugin searches in both "appdata\plugins\asr presets" and "mb folder\plugins\asr presets" folders for importing presets

moreover, portable mb 3.5rc3 installs plugins to "mb folder\plugins" rather than "mb folder\appdata\plugins" as it was earlier (of course installer mb3.5rc3 still installs plugins to writable "appdata\plugins" folder rather than to write-protected "c:\program files (x86)\musicbee\plugins\").

And I agree with Messiaen that three import buttons seem a bit much.
for now, i'll just rename import/export buttons because they have different meanings for importing/exporting user presets, and for importing predefined presets.

(https://i.imgur.com/hlnpzUh.png)

What would you enter exactly in the entry field? The name of an existing virtual tag? Some unique text of your own choice?

What does the (pointed at) button do?
these 2 buttons assigns virtual tag function id, and removes assignment. my fault, i had to make a tool tips for these buttons.

An even better example (which I imagine Boroda would find amusing) is in the use of $ALR.  Say I wanted to store the length of a classical "work" (as the sum of individual movements), I would first define an Auto-Library-Report as:

<Grouping>: Album Artist, Album, Work, Sum(Time) -> Save Field: Sum(Time)

and assign that ALR a virtual function ID of "SetWorkDur".
it's not very important, but tou can save Sum(Time) to <Null> tag to save one custom tag, and still assign virtual tag function id to Sum(Time).

also, you can assign individual id to every aggregated function (and saving aggregated functions to custom tags is not obligatory).


-----------------------------------


hiccup, Messiaen, i'm very impressed by your conversation  8)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 06, 2023, 09:13:54 PM
i've increased displayed time to 10 sec.
Thank you.

predefined presets can't be edited, and most users won't create custom presets. what do you think, maybe it's worth to edit custom preset and edit the copy of predefined preset
I just imagined it working the way it does now - if you click Rename / Edit on a preset it just opens up in the editor so the user can look at it... sure, it can't be edited, but I learned a lot just from looking at your reg-ex codes without actually needing to copy the whole thing over first.  So, a double-click would just be the same as pressing the Edit button, without anything special.  Like you say, most users don't create custom edits and it stands to reason that those self-same users would be terrified of actually editing one of yours blindly.  ;)  So just being able to look at it is sufficient, I should think, they can always copy it later.

these 2 buttons assigns virtual tag function id, and removes assignment
Huh, I always just assumed that the Save All/Close button did that automatically - if the text field has content, then it's applied, if the field is empty, it's removed.  If there's some mystical need for this two-step approach, then it definitely should be documented better! :)

you can save Sum(Time) to <Null> tag to save one custom tag, and still assign virtual tag function id to Sum(Time).
Yeah I know (I did that accidentally and was surprised it worked), but when writing that example above the more pressing concern was brevity/clarity.  Also, sometimes I have a heck of a time getting the ALR configurations to work as I expect them to (forgetting or accidentally changing even a small grouping element can wreak havoc), so the standard philosophy is "if it ain't broke..."  :)

hiccup, Messiaen, i'm very impressed by your conversation
I kind of figured you'd come home after a long day only to find that the kids had messed up the house (thread) again, and who wants to read all this bloody English text anyway?  :-\

(Any thoughts on the idea of exporting a proper $Char() function?  The world isn't really banging on your door demanding one so I suppose it's not of much use to anyone else, and my work-around is functional, so it's just a thought.)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 01:03:41 AM
i've added a few new tool tips to ASR, and renamed "import all"/"import new" buttons to "update all"/"update new". double-clicking on user preset now opens it for editing, double-clicking on predefined presets open preset copy for editing, but i will change it so original predefined presets will be opened in read-only mode.

i've made new virtual tag function $Char(hexadecimal unicode code). it was just a couple of new lines of code. it works the same way as ASR function
Code
\@char[[charcode]]
https://www.mediafire.com/file/m6jo0wczobidwkp/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 07:27:34 AM
these 2 buttons assigns virtual tag function id, and removes assignment
Huh, I always just assumed that the Save All/Close button did that automatically - if the text field has content, then it's applied, if the field is empty, it's removed.  If there's some mystical need for this two-step approach, then it definitely should be documented better! :)
actually, you are right. ⌘ button does nothing, id assignment is happening, when caret leaves id text field. the only function of ⌘ button is to provide an easy way to move input focus from id field.

----------------------------

new beta version:

numerous minor bug fixes, improvements, new tool tips, confirmation dialogs, and code refactoring. i only hope that i didn't break some functionality during code refactoring, but source code is now more readable.

now double-clicking user ASR presets opens preset editor, double-clicking stock ASR presets opens preset editor in read-only mode.

https://www.mediafire.com/file/m6jo0wczobidwkp/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 07:46:31 AM
actually, you are right. ⌘ button does nothing, id assignment is happening, when caret leaves id text field. the only function of ⌘ button is to provide an easy way to move input focus from id field.
But that also happens when you click somewhere else in the panel.
So wouldn't it be best to just remove the place of interest button?
That will also allow for a slightly wider input field.

edit:
This warning also pops up when the field is left blank.
That probably shouldn't happen?

(https://i.imgur.com/c697ypH.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 07, 2023, 08:23:19 AM
i've made new virtual tag function $Char(hexadecimal unicode code)
Does this require Steven to activate it or something, as it doesn't seem to work: Something simple like $Char(00A7) is just replaced by... nothing.  (Should be a '§', as a test.)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 10:30:30 AM
Not for me, a wrong preset still sometimes gets triggered, and some preset hotkeys don't work at all.
it's even strange that it somehow worked ever at all. there was a blunder. internal counter of all hotkeys was shifted by 1, and this internal counter very vaguely related (and relates, it's by design) to any display order of presets/hotkeys. i hope, it's fixed:
1.
I'm still (again?) getting wrong presets being triggered by hotkeys and some not working at all.
Using similar presets as from my earlier example.
5.5.8407

Never mind, my mistake, I see was using an older virtual tag that didn't align with how I have now setup the presets.
All's good.

2.
Nitpicking: perhaps change both texts to Auto-apply ?
(https://i.imgur.com/5tQf1Zy.png)

3.
I have never used this feature, but do I understand correctly that it allows to enter tags that will remain unchanged, no matter what the preset says?
(https://i.imgur.com/y1QxRH2.png)
If that is the case, perhaps a wording such as 'preserve tags' would be better than 'skip input tag values'.
And I am also curious when you would use this feature?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 04:12:47 PM
…and renamed "import all"/"import new" buttons to "update all"/"update new".
Not sure about that one to be honest.
As the tooltip says, it's more of loading presets than updating them I think?
Or will it sometimes indeed update existing presets with updated/improved versions?

(https://i.imgur.com/wkJLoBb.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 04:23:53 PM
actually, you are right. ⌘ button does nothing, id assignment is happening, when caret leaves id text field. the only function of ⌘ button is to provide an easy way to move input focus from id field.
So wouldn't it be best to just remove the place of interest button?
That will also allow for a slightly wider input field.
i've made this button to not confuse users that there is no "confirmation" button (though this button is actually not needed). i'll keep this button. as for width of id field, i've changed anchors of that field and 2 adjacent buttons, so id field is resized on ASR window resizing.

This warning also pops up when the field is left blank.
That probably shouldn't happen?

(https://i.imgur.com/c697ypH.png)
damn. the same for ALR. nobody noticed it, though this bug existed from the beginning. it's fixed.

Does this require Steven to activate it or something, as it doesn't seem to work: Something simple like $Char(00A7) is just replaced by... nothing.  (Should be a '§', as a test.)
i've copied this function from ASR, and kept "private" declaration instead of changing it to "public", so the function was invisible to mb. it's fixed.

Nitpicking: perhaps change both texts to Auto-apply ?
(https://i.imgur.com/5tQf1Zy.png)
ok, i'll change this.

I have never used this feature, but do I understand correctly that it allows to enter tags that will remain unchanged, no matter what the preset says?
(https://i.imgur.com/y1QxRH2.png)
If that is the case, perhaps a wording such as 'preserve tags' would be better than 'skip input tag values'.
And I am also curious when you would use this feature?
not tags, but any values of any tags, no matter what tags contain these values.

i don't remember why i've introduced this field, but here is an offhand example:

you want to apply some preset to album artist, but don't want to change "service" album artists, e.g. "Various Artists" or "Compilations".

--------------

mentioned fixes, and some other fixes and very minor UX improvements (on ASR preset importing):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 04:33:23 PM
actually, you are right. ⌘ button does nothing, id assignment is happening, when caret leaves id text field. the only function of ⌘ button is to provide an easy way to move input focus from id field.
So wouldn't it be best to just remove the place of interest button?
That will also allow for a slightly wider input field.
i've made this button to not confuse users that there is no "confirmation" button (though this button is actually not needed). i'll keep this button. as for width of id field, i've changed anchors of that field and 2 adjacent buttons, so id field is resized on ASR window resizing.
With all due respect, I disagree.
This is a button that does nothing. (and has a symbol that nobody will understand)

To make things more consistent all over, why not make it so that the virtual tag id is not automatically saved as soon as the field gets out of focus, and make it behave just like any other field (both in AT&RT and in MusicBee) so that a user will need to press 'save' to apply it?
Don't you agree it would make things more consistent and intuitive?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 04:59:14 PM
not tags, but any values of any tags, no matter what tags contain these values.
Ah, so values indeed.
Thanks for explaining.

edit:
Still, something like: 'preserve' tag values may be better than 'skip' input tag values?
I'm not sure.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 05:45:53 PM
…and renamed "import all"/"import new" buttons to "update all"/"update new".
Not sure about that one to be honest.
As the tooltip says, it's more of loading presets than updating them I think?
Or will it sometimes indeed update existing presets with updated/improved versions?

(https://i.imgur.com/wkJLoBb.png)
the problem is that the english is not my native language. it would be helpful if you could suggest better wording.

yes, 2 "update" buttons really update some presets in use by ASR from the folder "Plugins\ASR Presets" (either from "mb folder\plugins\asr presets" or "mb appdata\plugins\asr presets", depending on how you have installed the plugin (and its presets), and depending on what mb version you are using - portable or installer). it's supposed that "Plugins\ASR Presets" folder contains all most recent "stock" asr presets. but you may not want to load them all to "mb appdata\asr presets" folder. this folder is working folder for asr. it can contain user presets, default "stock" presets, customized "stock" presets (you can change <tag #> and <custom #> values for some "stock presets"). some "stock" presets may be deleted by user from asr working folder.

"update all" loads all available in ""Plugins\ASR Presets" folder "stock" presets to asr working folder, but this command will ask you if you want to update customized "stock" presets (if any), i.e. "slightly changes" stock presets (user can't edit "stock" presets for real).

"update new" loads to asr working folder only "stock" presets, changed by me since last time user loaded "stock" presets, but this command will also ask you if you want to update customized "stock" presets (if any). and it won't reload any deleted by user "stock" presets (i mean deleted by user from asr working folder).

-------------------------

Nitpicking: perhaps change both texts to Auto-apply ?
(https://i.imgur.com/5tQf1Zy.png)

i've unified all instances of "auto apply"/"auto-apply"/"autoapply" words in the whole plugin to "auto-apply".

I have never used this feature, but do I understand correctly that it allows to enter tags that will remain unchanged, no matter what the preset says?
(https://i.imgur.com/y1QxRH2.png)
If that is the case, perhaps a wording such as 'preserve tags' would be better than 'skip input tag values'.

i've changed field label and tool tips (over label and over field itself).

------------------------------------

you are welcome to propose further improvements to wordings.

------------------------------------

update plugin version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 05:59:04 PM
the problem is that the english is not my native language. it would be helpful if you could suggest better wording.
Yeah, while it's not mine either, I believe that the Russian language is far more complicated, and more distanced from English than mine.
I'll give things some further thought now I understand the functions a little bit better, but I also hope that some native English speakers (such as e.g. Messiaen and phred) have something to say/add to all this too.
(as long as they don't try to impersonate 18th century writers, I declare)

This may all seem a little bit of nitpicking, but I truly believe the choice of one single word will be able to confuse a user. Certainly new ones.
And improving on it might invite users to try out features they would otherwise ignore or be a little bit scared of.

Thanks for being open to all this. I have been learning some things here ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 06:04:14 PM
hiccup, i've edited my previous post when you were answering. you may want to reread it.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 06:06:15 PM
hiccup, i've edited my previous post when you were answering. you may want to reread it.
I surely will.
But I'm calling it a day for now. Cheers.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 06:07:11 PM
but I also hope that some native English speakers (such as e.g. Messiaen and phred) have something to say/add to all this too.
yeah, i really hope for them
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 07, 2023, 06:50:42 PM
...as long as they don't try to impersonate 18th century writers, I declare
So I guess you don't want my ghostly spirit channeling of Montaigne, Dostoevsky, Proust, or Rabelais?  I can do Harry Potter too, if pushed.   :)  Jeez, tough audience.

This may all seem a little bit of nitpicking, but I truly believe the choice of one single word will be able to confuse a user. Certainly new ones.
And improving on it might invite users to try out features they would otherwise ignore or be a little bit scared of.
It's not nitpicking at all as your motives are in the honest pursuit of helping users make sense of the things in front of them.  When I first discovered MB about a year ago I wouldn't ordinarily have looked too closely at virtual expressions as I couldn't see a practical application for them.  And then I ran into the wall of Steven's very strange decision (since changed, thank god) to calculate all times in minutes and seconds, no hours.  So, I dug into this virtual stuff, and now I can't live without it.  So, the more inviting something is, the better.

Every now and then I do get a particular sense of glee at how someone else expresses an idea in English... say, for example, in the Auto-Library UI there's a lovely option which says "Calculate aggregated functions and save them to tags..."  The problem is, while I think I fully understand what that means, I'm not entirely sure, and I love the wording so I don't want to change it - though if ever there were options people might "be a little bit scared of" they'd for sure be worded just like that one.  :)  It makes me smile every time I see it though I know 99% of users would be confused by the nature of combining words like "aggregate" and "function".

Honestly though, I have no idea how to simplify it. (At the moment.)  Let me commune with my Shakespearean brethren and I'll get back to you on that one.   ;)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 07, 2023, 06:52:24 PM
but I also hope that some native English speakers (such as e.g. Messiaen and phred) have something to say/add to all this too.
yeah, i really hope for them
I haven't been paying close attention to all the suggestions over the past two forum pages. I will reread the verbiage comments closely and try to come up with some suggestions for better tool tips and button text. I will get to this over the course of this weekend.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 07, 2023, 07:07:45 PM
I can do Harry Potter too, if pushed.   :)
I never heard of that writer, what works is he known for?

(yeah, tough crowd here ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 07, 2023, 07:16:57 PM
...nobody noticed it, though this bug existed from the beginning. it's fixed.
I had run into it a few times, but I just figured it was me doing something wrong (or out of order), and since it always went away after a few clicks I didn't think of reporting it.

There used to be (?) a bug where if I edited a preset multiple times which was assigned to a hotkey, every time I saved it the number of "left" slots would go down.  I could never reliably reproduce it, so I left that off the list too.  You may have accidentally fixed it with all your recent refactoring, as I haven't run into it for awhile.

i've copied this function from ASR, and kept "private" declaration instead of changing it to "public", so the function was invisible to mb. it's fixed.
Yep, all good now, thank you very much.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 07, 2023, 08:18:51 PM
Every now and then I do get a particular sense of glee at how someone else expresses an idea in English... say, for example, in the Auto-Library UI there's a lovely option which says "Calculate aggregated functions and save them to tags..."  The problem is, while I think I fully understand what that means, I'm not entirely sure, and I love the wording so I don't want to change it - though if ever there were options people might "be a little bit scared of" they'd for sure be worded just like that one.  :)  It makes me smile every time I see it though I know 99% of users would be confused by the nature of combining words like "aggregate" and "function".
firstly you are welcome (of course, not only you, but also phred & hiccup) to suggest better english wording for any plugin function/option. "Aggregated function" is just literal translation from russian to english of a professional term from database world. i actually don't know what is the correct english term for this concept.

secondly, what do you (and, also, phred and hiccup) think about renaming "update all"/"update new" buttons to "install all"/"install new"?

-----------------------

i'm now in the middle of changing the entire structure of the plugin package. Downloadable .zip (Additional-Tagging-Tools_latest.zip, Additional-Tagging-Tools_beta.zip or Additional-Tagging-Tools_YYYY-MM-DD.zip depending on situation) will contain inside "ASR Presets" folder, file README.TXT, and another real plugin .zip (always Additional-Tagging-Tools-Plugin.zip). users must manually extract downloadable .zip (1st level .zip) to some folder (e.g. desktop).  README.TXT must contain the following instructions (it's a beta version of instructions 8) ):

---

INSTALLATION

Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Add Plugin...", browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences. Open MusicBee menu: Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace. Click button "Update All", browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open subfolder "ASR Presets" to load all predefined presets. To configure plugin, open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Configure" under "additional tagging & reporting tools" header.


UPDATING PLUGIN

Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Disable" under "additional tagging & reporting tools" header. Restart MusicBee. Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Add Plugin...", browse to the folder where updated file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences.

Updating ASR presets:

Open MusicBee menu: Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace. Click button "Update All" to install all new predefined ASR presets and reinstall all old predefined ASR presets or click button "Update New" to install only predefined presets, changed by developer since last time you installed predefined presets by either of two methods. "Update New" action won't reinstall any deleted by you predefined presets. Predefined presets can't be edited for real, but you can "customize" them, i.e. adjust a few available for changing options. Both installation commands will ask you if you want to update customized predefined presets (if any) and lose your adjustments or to skip updated by developer, but customized by you presets.


UNINSTALLATION

Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Uninstall" under "additional tagging & reporting tools" header. MusicBee will delete all automatically created files (e.g. settings), but you will need to close MusicBee and manually delete file "mb_TagTools.dll" and  and subfolder "ru" from "Plugins" folder. "Plugins" folder is located in MusicBee application folder if you are using portable MusicBee and in folder "%AppData%\MusicBee" if you are using installer version of MusicBee.

Unfortunately, any plugin can't be uninstalled from Store version of MusicBee at the moment.

---

can somebody suggest any corrections to installation/updating/uninstallation process and/or to english text (maybe there are some grammar/syntax errors or stammering/tongue-tie)?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 08, 2023, 02:24:27 PM
In advance of my offering English language suggestions, I've reread the last three pages and have some comments.
1- The "import" button: what does "shared" presets refer to? Would that be the same as -custom- presets?

2- Hiccup raises some good comments regarding the "Update New" and "Update All" buttons and the related tool tip referring to "load". Boroda's comment is that it's due to his English language skills. Which in my opinion are pretty damn good. I will work on this and get a feel for what word works best.

3- "Auto-apply ticked presets on startup". If these aren't applied at startup, then when do they get applied? If ticked, does ASR scan the user's entire library looking for criteria matching the preset? Does that slow down MB's startup when there's a large library?

4- Reply # 3959 - Boroda's proposed readme.txt file is a good idea and I'll will put my eagle eyes on it.

I hope to post my comments/suggestions on these, along with anything else I find, by the end of my day here.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 08, 2023, 10:23:52 PM
phred, thanks for your response.

In advance of my offering English language suggestions, I've reread the last three pages and have some comments.
1- The "import" button: what does "shared" presets refer to? Would that be the same as -custom- presets?
"import" will import any asr preset(s) from an arbitrary folder (open file dialog supports multi-selection, so preset(s)). "shared" means "previously exported" by you (e.g. to back up) or by another user to share preset(s) with others. users are free to export any presets, but "shared" presets are suggested to be mostly custom presets, or they also can be customized predefined presets (users can't fully edit predefined presets, but most predefined presets have some adjustable options: all these <tag #>, <custom text #>).

i want to change all mentions of "custom presets" in the plugin to "user presets" to emphasize the difference between user presets and customized predefined presets.

2- Hiccup raises some good comments regarding the "Update New" and "Update All" buttons and the related tool tip referring to "load".
my current intention is to change the words "update" (in button names) and "load" (in tooltips of these buttons) to "install", e.g.: "install all" button with tooltip "install all predefined presets, and update installed predefined presets to the latest version".

3- "Auto-apply ticked presets on startup". If these aren't applied at startup, then when do they get applied? If ticked, does ASR scan the user's entire library looking for criteria matching the preset? Does that slow down MB's startup when there's a large library?
actually, this option is a rudiment from time, when ASR doesn't have auto-applying option on tag changes/adding new tracks to library/inbox. maybe i must remove this option at all, it's obsolete now.

using this option won't slow down mb startup if library is large, instead it will slow down mb responsiveness in general after startup (during some time depending on library size).

4- Reply # 3959 - Boroda's proposed readme.txt file is a good idea and I'll will put my eagle eyes on it.
the problem is that i very want to put readme in plugin zip, but placing another real plugin zip into downloadable zip is not very good idea. i don't know where and how to put/publish installation/updating/uninstallation instructions, so that they will attract attention, and won't be unnoticed by users.  

----------

very big problem is so called (by me  :) ) "aggregated functions" in ALR. i simply can't come up with a clear english name for them. they are not just "functions", because they return not a value calculated for a track, but an array of values calculated for some groups of tracks. typical "aggregated function" is mb native $Sum function, e.g. $Sum(<Time>,<Artist>) will show total duration of all tracks of track artist for every track in track list. i just don't know how to name these "functions".
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 09, 2023, 01:39:41 AM
i'm now in the middle of changing the entire structure of the plugin package. Downloadable .zip (Additional-Tagging-Tools_latest.zip, Additional-Tagging-Tools_beta.zip or Additional-Tagging-Tools_YYYY-MM-DD.zip depending on situation) will contain inside "ASR Presets" folder, file README.TXT, and another real plugin .zip (always Additional-Tagging-Tools-Plugin.zip). users must manually extract downloadable .zip (1st level .zip) to some folder (e.g. desktop).  README.TXT must contain the following instructions (it's a beta version of instructions 8) ):
I'm still trying to understand this. These questions come from my reading and re-reading your first draft of the readme. Once I get a clearer picture of how you're planning on packaging the zip, I'll be able to tackle the readme. My questions are as follows (you can simply answer by referencing to my question numbers.) Note that your answers (or my re-reading) my prompt more questions. :-)
1- Why will there be three versions? I can understand two: the stable .dll and the beta .dll.
2- Why the YYYY-MM-DD?
3- Will releasing a beta help you in producing the stable? You've never had a beta before. Or perhaps every release was a beta.
4- Is the name of the downloaded zip changing from mb_TagTools_latest to Additional Tagging Tools?
5- Each of the downloadable zips will consist of the Presets folder (as has been the case,) the RU folder, the readme, and another zip?? Why not just put the .dll without having it in a folder?
6- Will the downloadable zip always be named "Additional-Tagging-Tools-Plugin.zip"? Not "Additional Tagging Tools latest? Or ..beta? Or ...YYYY-MM-DD?

I've attacked the "Installation" section of the readme and depending on your answers to the above, I may be finished with it. My eyes are blurry and my head hurts, so I will continue this tomorrow.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 09, 2023, 08:11:30 PM
1. "latest" is the latest stable version, but may require beta version of mb, "yyyy-mm-dd" may be (or may not exit at all) just some stable plugin versions for some specific mb (probably only stable) versions. "beta" is just some beta version of plugin. only "latest" will definitely exist.

2. it's simply the date of plugin version. it's much simpler for me to mark plugin versions by release date (not always simpler, but in most cases).

3. yes, but it's rare cases, when plugin is significantly updated, but not sufficiently tested.

4. yes

5. i've decided to put in downloadable zip only 2 files: readme.txt and mb_TagTools.zip. the latter will be structured as now. presets and ru folders will be inside mb_TagTools.zip as it is now.

6. only the name of the downloadable zip may be somehow changed, if the situation requires this.

-

actually, all this doesn't relate to translation. i've found out that even advanced users don't realize how to correctly install/update plugin and asr presets. i've tried to ask active plugin users, what "distribution model" (and hence, installation/updating process) they suppose to be more clear and easy. it's not the question of translation.

----------

about translation of readme. here is the latest readme version, but it's still not final. it would be helpful if you can suggest some corrections of english text.

--

PLUGIN INSTALLATION

Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Add Plugin...", browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences. Open MusicBee menu: Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace. Click button "Install All", browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open subfolder "ASR Presets" to load all predefined presets. To configure plugin, open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Configure" under "additional tagging & reporting tools" header.


PLUGIN UPDATING

Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Disable" under "additional tagging & reporting tools" header. Restart MusicBee. Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Add Plugin...", browse to the folder where updated file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences.

Updating ASR presets:

Open MusicBee menu: Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace. Click button "Install All" to install all predefined presets, updating already installed predefined presets to the latest version, or click button "Install New" to (re)install predefined presets, created or updated by developer since last time you installed/updated them. If you have deleted some predefined presets, then they won't be reinstalled by "Install New" action. Predefined presets can't be edited for real, but you can "customize" them, i.e., adjust some available for changing options. Both installation actions  will ask you if you want to update customized predefined presets (if any) and lose your adjustments or to skip updated by developer, but customized by you presets.


PLUGIN UNINSTALLATION

Open MusicBee menu: Edit> Edit Preferences> Plugins. Click button "Uninstall" under "additional tagging & reporting tools" header. MusicBee will delete all automatically created files (e.g., settings), but you will need to close MusicBee and manually delete file "mb_TagTools.dll" and  and subfolder "ru" from "Plugins" folder. "Plugins" folder is located in MusicBee application folder if you are using portable MusicBee and in folder "%AppData%\MusicBee" if you are using installer version of MusicBee.

Unfortunately, any plugin can't be uninstalled from Store version of MusicBee at the moment.

----------------

new plugin version.

6 new functions to compare integer or fractional numbers are added:

$eq(num1,num2): determines if num1 is equal to num2, e.g. $eq(1.0,1) returns "T"

$ne(num1,num2): determines if num1 is not equal to num2

$gt(num1,num2): determines if num1 is greater than num2

$lt(num1,num2): determines if num1 is less than num2

$ge(num1,num2): determines if num1 is greater than or equal to num2

$le(num1,num2): determines if num1 is less than or equal to num2

--

"update all"/"update new" buttons are renamed to "install all"/"install new". tooltips for these buttons (and some other buttons) are also changed. process of updating (i.e. reinstalling) of predefined presets is improved, some customization options (e.g. "auto-apply preset only if track belongs to playlist") of predefined presets are correctly and silently transferred to updated presets, if other customization options were adjusted by user (but only adjusted after updating plugin to this version), then plugin will ask user if he wants to keep current customized presets or to update customized presets anyway, losing these customizations, etc.

anyway, user can always copy any predefined preset to preserve it in case of any predefined preset reinstallation.

-

buttons ⌘ are removed from ASR and ALR.  

-

layout of ASR window is slightly changed. wording of some labels/buttons is changed.

-

many syntax errors are corrected in ASR presets, but you must "install all" presets to update them, not "install new". or just copy 'asr presets' folder from plugin zip to 'mb appdata' folder, overwriting all files.

-----------------------------------------------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 09, 2023, 08:43:15 PM
PLUGIN INSTALLATION
As a more general and undirected  observation:

Both 'installing' and 'updating' plugins to me seems something a lot of software doesn't have a tight grip on, and is very often confusing for users. For both novice and experienced ones.
Some software desire the user to load some zip file and the program will take care of the rest, some will require to extract a zip file and copy specific files to specific locations. etc. etc.

MusicBee certainly is no exception. It has an 'add plugin' button in its interface. But for AT&RT it should not be used?

Also, the fact that both MusicBee and AT&RT don't use the commonly known concept of 'beta' for their releases isn't helping much in making any of that easier for the common user.

Both MB and AT&RT have had functionality added and removed to align things to make them work properly, but how would any user (besides maybe some that have been close on following up on all this) know what is required?

Please take this as a crude observation at the spur of the moment.
Just saying this is something that could and should be improved on, while acknowledging I have no specific or useful proposals for that at this moment.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 10, 2023, 02:02:14 AM
actually, all this doesn't relate to translation. i've found out that even advanced users don't realize how to correctly install/update plugin and asr presets.
Thanks for answering my questions. I does indeed relate to the translation I'm doing on the readme because I need to what you're trying to do in order to make the readme as complete and understandable as possible.

Quote
i've tried to ask active plugin users, what "distribution model" (and hence, installation/updating process) they suppose to be more clear and easy. it's not the question of translation.
The way I install and/or update the plugin and the presets is to close MB > open the zip > drag the .dll to the plugins folder > drag the presets to the presets folder > restart MB.

Now going back to work on the readme. I may have something for you later tonight.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 10, 2023, 02:32:25 AM
@boroda...

I'm still having trouble with this statement from the "Updatng the ASR Presets" section.

NOTE: "Install New" will not reinstall any predefined presets deleted by you. Predefined presets can't be edited but can be "customized." For example, adjusting some criteria of a predefined preset will result in a "customized" preset. Both installation commands will ask you if you want to update the customized preset(s) (if any) and lose your adjustments, or to skip those updated by developer, but customized by you.

Specifically the sentence that is underlined. To me it means that
the user can update the customized preset(s) -AND- lose the adjustments the user made
OR
skip the developer updated presets but update the ones the user customized

If the user makes adjustments to a preset, it can be updated but the adjustments are lost. Are the adjustments lost or saved/imported/updated? Perhaps "discarded" is a better choice of words if in fact the adjustments get saved/imported/updated first.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 10, 2023, 03:55:26 PM
"install new" gives 2 options:

1. the user can update the customized preset(s) to latest version from developer (if modification date of latest preset > modification date of installed preset) -AND- lose the adjustments the user made (this concerns only situation, when date of latest preset > date of installed preset). 2. or user can skip updating of such customized presets (but update not customized presets to latest version anyway, because it's safe).

modification date of predefined presets is not changed on preset customization. the fact of preset customization is tracked by other means.

if user really edit preset, then preset modification date is changed. but users can edit only user presets, not predefined. user presets can't be somehow affected by predefined presets updating.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 10, 2023, 03:58:44 PM
PLUGIN INSTALLATION
As a more general and undirected  observation:

Both 'installing' and 'updating' plugins to me seems something a lot of software doesn't have a tight grip on, and is very often confusing for users...
i agree about "installing"/"uninstalling", i must change them to "adding"/"removing". but i don't think that word "updating" may be confusing. i already avoid the word "upgrading".
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 10, 2023, 07:31:17 PM
Here's my third draft on a readme file for the ASR plugin. Comments, corrections, and clarifications welcome.

ADDING THE PLUGIN
1- Download the appropriate ZIP file and remember where you saved it.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin...
3- Browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close the Preferences window.
4- Open MusicBee. From the menubar > Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace > Click Update All > browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open subfolder "ASR Presets" to load all predefined presets.
5- To configure plugin, open MusicBee. From the menubar > Edit > Edit Preferences> Plugins > Additional Tagging & Reporting Tools" > Configure.

UPDATING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where updated file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences.

UPDATING THE ASR PRESETS
1- Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a- Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b- Click the "Install New" button to (re)install predefined presets which were created or updated by developer since last time you installed or updated them by either of two methods.

IMPORTANT NOTE: "Install New" will not reinstall any predefined presets deleted by you. Predefined presets can't be edited but can be "customized." For example, adjusting some criteria of a predefined preset will result in a "customized" preset. Both installation commands will ask you if you want to update the customized preset(s) (if any) and lose your adjustments, or to skip those updated by developer, but update only those customized by you. For example, User A customizes a predefined preset and shares it with User B. User B makes a change to it and shares it back to User A. User A selects "Install New" and User B's changes will replace User A's customized preset. Thereby discarding (or removing) User A's original changes.

REMOVING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins.
2- Additional Tagging & Reporting Tools > Uninstall. MusicBee will delete all automatically created files (e.g. settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolder "ru" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder folder "%AppData%\MusicBee".

Unfortunately no plugin can be uninstalled from Store version of MusicBee at the moment.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 10, 2023, 07:51:33 PM
UPDATING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where updated file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences.
Is this indeed the necessary procedure?
So you can't just overwrite the mb_TagTools.dll with a newer version? (with MB closed of course)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 10, 2023, 07:59:18 PM
Is this indeed the necessary procedure?
So you can't just overwrite the mb_TagTools.dll with a newer version? (with MB closed of course)
According to the readme texts boroda has posted over the previous two to three pages, yes. I cleaned up what he wrote somewhat.

BUT! I overwrite the DLL -and- the presets when a new version is released and never had an issue.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 11:14:15 AM
my corrections (mostly related to latest changes of asr handling and downloaded plugin zip structure. italic text as added by me, strike-through text is removed by me):

ADDING THE PLUGIN
1- Download the appropriate ZIP file, unpack it to some temporary folder, and remember where you saved it where this folder is located.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin...
3- Browse to the folder where you have unpacked downloaded zip, file "Additional-Tagging-Tools-Plugin.zip" is located and open this file "mb_TagTools.zip". Close the Preferences window.

Installing Advanced Search & Replace Presets
4- Open MusicBee. From the menubar > Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace > Click Update Install All > browse to the folder where file "Additional-Tagging-Tools-Plugin.zip" is located and open subfolder "ASR Presets" to load all predefined presets.
5- To configure plugin, open MusicBee. From the menubar > Edit > Edit Preferences> Plugins > Additional Tagging & Reporting Tools" > Configure.

UPDATING THE PLUGIN
0 - Download the appropriate ZIP file, unpack it to some temporary folder
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where updated file "Additional-Tagging-Tools-Plugin.zip" "mb_TagTools.zip" is located and open this file. Close preferences.

UPDATING THE ASR PRESETS
1- Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a- Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b- Click the "Install New" button to (re)install predefined presets which were created or updated by developer since last time you installed or updated them by either of two methods.

IMPORTANT NOTE: "Install New" will not reinstall any predefined presets deleted by you. Predefined presets can't be edited, but can be "customized" (most predefined presets allows changing some options). For example, Adjusting some criteria of a predefined preset will result in a "customized" preset. Both installation commands will ask you if you want to update the customized preset(s) (if any) and lose your adjustments, or to skip those updated by developer, but and update only those not customized by you. (The following sentence by pred doesn't relate to installing new or all predefined presets, it's about exporting/importing presets. for now all presets are always exported as new user presets. i'll try to improve preset exporting/importing and come back later with new implementation) For example, User A customizes a predefined preset and shares it with User B. User B makes a change to it and shares it back to User A. User A selects "Install New" and User B's changes will replace User A's customized preset. Thereby discarding (or removing) User A's original changes.

REMOVING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins.
2- Additional Tagging & Reporting Tools > Uninstall. MusicBee will delete all automatically created files (e.g. settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolders "ASR Presets" and "ru" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder "%AppData%\MusicBee".

Unfortunately, no plugin can be uninstalled from Store version of MusicBee at the moment.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 11:24:06 AM
UPDATING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where updated file "Additional-Tagging-Tools-Plugin.zip" is located and open this file. Close preferences.
Is this indeed the necessary procedure?
So you can't just overwrite the mb_TagTools.dll with a newer version? (with MB closed of course)
did you want to say "overwrite the mb_TagTools.dll and ASR Presets folder with a newer version"? it's possible, but won't give you any automatization of installing/updating predefined presets.

maybe direct copying of files is not very difficult even for dummies in case of portable mb, but not in case of installer mb.

readme is intended mostly for not very experienced users. removing plugin can't be simplified at the moment, but at least adding/updating can.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 11:44:45 AM
@phred, could you check (and correct if needed) the following warning massages? i mostly care about acceptable usage of tense, articles and punctuation, but not only:

Some predefined presets customized by you are changed by developer.
Do you want to update your customized predefined presets by new versions from developer?
All your customizations will be lost!
-
One or several imported presets already exist.
Do you want to import them as new presets, and keep your current presets?
Otherwise, existing presets will be overwritten!
-
# presets were successfully imported as new presets.
-
#  presets were successfully imported.
-
# presets failed to import due to file read errors or wrong format.
-            
# presets were successfully installed.
-
# presets were successfully updated.
-
# presets customized by you were updated.
-
# presets were not changed since last update, and skipped.
-
# presets were customized by you, and skipped.
-
# presets failed to install due to file read errors or wrong format.
-
No presets for installing found in expected directory!
-
Do you want to delete all predefined presets?
 -
No presets were deleted.
-
# presets were successfully deleted.
-
# presets failed to delete.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 11, 2023, 11:46:13 AM
did you want to say "overwrite the mb_TagTools.dll and ASR Presets folder with a newer version"? it's possible, but won't give you any automatization of installing/updating predefined presets.
I was thinking of when a user just wants to update the plugin itself, leaving all user- and predefined presets as they are.
I'm not sure I understand all workings and explanations at this moment, but I'll leave you and phred to work things out further without me interrupting ;-)
I'll make sure to test things out when the next version and explanations are published, and perhaps give some comments or suggestions then.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 11, 2023, 01:08:11 PM
...but I'll leave you and phred to work things out further without me interrupting ;-)
Please interrupt. Having another set of "experienced user" eyes on the project is helpful. And your testing is even more so as you use more presets than I do. At this point I'm focusing on helping write the readme.
Title: Re: Additional Tagging & Reporting Tools
Post by: FCerral on January 11, 2023, 01:53:39 PM
Hi

After installing the plugin for the first time (5.5 versión) the item "Additional Taggin & Reporting Tools" appears in the Tools Menu but doesn't include any commands.

(https://i.ibb.co/gFLHw2S/Sin-t-tulo.png)

Apologies if this issue has been addressed already, I can't seem to find it
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 11, 2023, 02:10:27 PM
Updated readme with boroda's latest changes:

ADDING THE PLUGIN
1- Download the appropriate ZIP file and remember where you saved it.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin...
3- Browse to the folder where you have unpacked the downloaded zip and open it and then open mb_TagTools.zip. Close the Preferences window.

INSTALLING ADVANCED SEARCH & REPLACE PRESETS
1- Open MusicBee. From the menubar > Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace > Click Install All to load all predefined presets.
2- To configure plugin, open MusicBee. From the menubar > Edit > Edit Preferences> Plugins > Additional Tagging & Reporting Tools" > Configure.

UPDATING THE PLUGIN
1- Download the appropriate ZIP file and unpack it to a temporary folder of your choice.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
3- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where the updated file mb_TagTools.zip is located and open this file. Close preferences.

UPDATING THE ASR PRESETS
1- Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a- Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b- Click the "Install New" button to (re)install predefined presets which were created or updated by developer since last time you installed or updated them by either of two methods.

IMPORTANT NOTE: "Install New" will not reinstall any predefined presets deleted by you. Predefined presets can't be edited but can be "customized." Most predefined presets allow changing some options. Adjusting some criteria of a predefined preset will result in a "customized" preset. Both installation commands will ask you if you want to update the customized preset(s) (if any) and lose your adjustments, or to skip those updated by developer amd update only those not customized by you.

REMOVING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins.
2- Additional Tagging & Reporting Tools > Uninstall. MusicBee will delete all automatically created files (e.g. settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolder "ru" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder folder "%AppData%\MusicBee".

Unfortunately no plugin can be uninstalled from Store version of MusicBee at the moment.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 02:14:03 PM
Hi

After installing the plugin for the first time (5.5 versión) the item "Additional Taggin & Reporting Tools" appears in the Tools Menu but doesn't include any commands.

(https://i.ibb.co/gFLHw2S/Sin-t-tulo.png)

Apologies if this issue has been addressed already, I can't seem to find it

it's known issue. it's not very important, but difficult to fix, so i'm leaving it unresolved for ages. you simply have clicked mb menu too quickly, before full plugin initialization. i'm always waiting a couple of seconds before trying to use plugin menu.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 02:17:25 PM
phred, i've updated that my post. below is the quote of changed post:

@phred, could you check (and correct if needed) the following warning massages? i mostly care about acceptable usage of tense, articles and punctuation, but not only:

Some predefined presets customized by you are changed by developer.
Do you want to update your customized predefined presets by new versions from developer?
All your customizations will be lost!
-
One or several imported presets already exist.
Do you want to import them as new presets, and keep your current presets?
Otherwise, existing presets will be overwritten!
-
# presets were successfully imported as new presets.
-
#  presets were successfully imported.
-
# presets failed to import due to file read errors or wrong format.
-           
# presets were successfully installed.
-
# presets were successfully updated.
-
# presets customized by you were updated.
-
# presets were not changed since last update, and skipped.
-
# presets were customized by you, and skipped.
-
# presets failed to install due to file read errors or wrong format.
-
No presets for installing found in expected directory!
-
Do you want to delete all predefined presets?
 -
No presets were deleted.
-
# presets were successfully deleted.
-
# presets failed to delete.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 11, 2023, 02:31:38 PM
From your most recent version. Strike-through means remove; italics means add.


Some predefined presets customized by you are have been changed by developer.
Do you want to update your customized predefined presets by new versions from developer?
All your customizations will be lost! ALL YOUR CUSTOMIZATIONS WILL BE LOST
-
One or several more imported presets already exist.
Do you want to import them as new presets, and keep your current presets?
Otherwise, existing presets will be overwritten! OTHERWISE, EXISTING PRESETS WILL BE OVERWRITTEN!
-
# presets were successfully imported as new presets.
-
#  presets were successfully imported.
-
# presets failed to import due to file read errors or wrong format.
-          
# presets were successfully installed.
-
# presets were successfully updated.
-
# presets customized by you were updated.
-
# presets were not changed since last update, and skipped.
-
# presets were customized by you, and skipped.
-
# presets failed to install due to file read errors or wrong format.
-
No presets for installing found in expected directory!
-
Do you want to delete all predefined presets?
 -
No presets were deleted.
-
# presets were successfully deleted.
-
# presets failed to delete.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 03:26:48 PM
phred, thank you. some minor corrections from my side:

ADDING THE PLUGIN
1- Download the appropriate ZIP file and unpack it to a temporary folder of your choice. and remember where you saved it.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin...
3- Browse to the folder where you have unpacked the downloaded zip and open it, and then open mb_TagTools.zip from this folder. Close the Preferences window.
4- To configure plugin, open MusicBee. From the menubar > Edit > Edit Preferences> Plugins > Additional Tagging & Reporting Tools" > Configure.

INSTALLING ADVANCED SEARCH & REPLACE PRESETS
1- Open MusicBee. From the menubar > Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace > Click Install All to load all predefined presets.
2- To configure plugin, open MusicBee. From the menubar > Edit > Edit Preferences> Plugins > Additional Tagging & Reporting Tools" > Configure.

UPDATING THE PLUGIN

NOTE: You can just copy file mb_TagTools.dll from archive mb_TagTools.zip to "Plugins" folder in MusicBee application folder if you are using the portable version of MusicBee, and want to update plugin only, keeping all ASR presets as is.

OTHERWISE:


1- Download the appropriate ZIP file and unpack it to a temporary folder of your choice.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
3- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where the updated file mb_TagTools.zip is located and open this file. Close preferences.

UPDATING THE ASR PRESETS
1- Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a- Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b- Click the "Install New" button to (re)install predefined presets which were created or updated by developer since last time you installed or updated them by either of two methods.

IMPORTANT NOTE: "Install New" will not reinstall any predefined presets deleted by you. Predefined presets can't be edited but can be "customized." Most predefined presets allow changing some options. Adjusting some criteria of a predefined preset will result in a "customized" preset. Both installation commands will ask you if you want to update the customized preset(s) (if any) and lose your adjustments, or to skip those updated by developer and update only those not customized by you.

REMOVING THE PLUGIN
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins.
2- Additional Tagging & Reporting Tools > Uninstall. MusicBee will delete all automatically created files (e.g. settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolders "ru"  and "ASR Presets" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder "%AppData%\MusicBee".

Unfortunately, no plugin can be uninstalled from Store version of MusicBee at the moment.

--------------------

i've changed exporting/importing behavior of the plugin. now export command will export any selected plugin preset as is, without any modifications (i.e. won't export any preset as new (copy) user preset). plugin asks the user to import an exported preset as a new (and slightly renamed - "*" is appended to the name) preset, or to overwrite an existing preset if the preset, which was at least initially the same (preset with the same guid), already exists.

---------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 03:37:11 PM
From your most recent version. Strike-through means remove; italics means add.

Some predefined presets customized by you are have been changed by developer.
Do you want to update your customized predefined presets by new versions from developer?
...

thanks, i'll update plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 03:41:54 PM
phred, one question. is it a correct english phrase?

    Do you want to update your customized predefined presets by new versions from developer?

or maybe something like this is better?

    Do you want to update your customized predefined presets by new versions by developer?

or some other wording?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 11, 2023, 05:44:50 PM
   Do you want to update your customized predefined presets by new versions by developer?
Phred said I could interrupt. (even when I am not closely following up on what you guys are discussing exactly)

There are two thing that confuse me personally in that sentence.

1.
Far as I understand there would be predefined presets (by boroda) and there would be customised presets. (by a user)
So, to me the term 'customised predefined preset' is a little bit confusing.

2.
'new version by developer'. Firstly I would assume the developer of the plugin (boroda) is referred to here.
Is that correct, or is it referring to the person that edited and/or shared a custom preset?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 11, 2023, 10:15:15 PM
Phred said I could interrupt. (even when I am not closely following up on what you guys are discussing exactly)
Thanks for interrupting. You raise a couple of valid questions, which I will answer and suggest that boroda make changes

Quote
1.
Far as I understand there would be predefined presets (by boroda) and there would be customised presets. (by a user)
So, to me the term 'customised predefined preset' is a little bit confusing.
I would propose using the term "user-customized preset(s)"

Quote
2.
'new version by developer'. Firstly I would assume the developer of the plugin (boroda) is referred to here.
Is that correct, or is it referring to the person that edited and/or shared a custom preset?
Yes, that's correct, but I'd propose this to make it more clear:
"new version by plugin developer"
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 11, 2023, 10:21:30 PM
There are two thing that confuse me personally in that sentence.

1.
Far as I understand there would be predefined presets (by boroda) and there would be customised presets. (by a user)
So, to me the term 'customised predefined preset' is a little bit confusing.
i've changed the terms i'm using recently to avoid this confusion. now there are "user presets" - they are not named anymore "custom presets" - (either created by user from scratch or copied from predefined presets), and there are "customized predefined presets" (along with "predefined presets", which are not changed by user at all). customized presets are small adjustments of predefined presets without converting them to user presets. only <tag #> and <custom text #> field can be "customized".

2.
'new version by developer'. Firstly I would assume the developer of the plugin (boroda) is referred to here.
Is that correct, or is it referring to the person that edited and/or shared a custom preset?
"developer" is me in this context (and in all contexts i'm using for this plugin).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 11, 2023, 10:24:21 PM
2.
'new version by developer'. Firstly I would assume the developer of the plugin (boroda) is referred to here.
Is that correct, or is it referring to the person that edited and/or shared a custom preset?
Yes, that's correct, but I'd propose this to make it more clear:
"new version by plugin developer"
Or: "new version(s) of predefined preset(s)"?

I'm still stuck at thinking that 'predefined preset' vs. 'custom preset' should be enough?
Explaining who created a preset doesn't seem that important? (for the purpose of the user interface, that is)
But maybe I am missing something in-between 'custom' and 'predefined' that should indeed be added and explained?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 11, 2023, 10:31:06 PM
"developer" is me in this context (and in all contexts i'm using for this plugin).
At the risk of repeating my post from a couple of minutes ago, I think that could be confusing.
Somebody that created a custom preset could (with some imagination) also be considered to be the developer of that preset.
I think the word 'developer' should be avoided here.
Presets are either predefined AT&RT presets, or they are custom presets.
Why make things more complicated for both the interface, and for new users?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 11, 2023, 10:36:25 PM
How about "custom-defined presets"? Or "user-defined presets"?

I think any reference to "the developer" should be changed to "the plugin developer."
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 11, 2023, 10:39:04 PM
@boroda...

I've incorporated your latest changes (deletes/adds/corrections) into this:

ADDING THE PLUGIN:
1- Download the appropriate ZIP file and unpack it to a temporary folder of your choice.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin...
3- Browse to the folder where you have unpacked the downloaded zip and open mb_TagTools.zip from this folder. Close the Preferences window.
4- To configure plugin, open MusicBee. From the menubar > Edit > Edit Preferences> Plugins > Additional Tagging & Reporting Tools" > Configure.

INSTALLING ADVANCED SEARCH & REPLACE PRESETS:
1- Open MusicBee. From the menubar > Tools> Additional Tagging & Reporting Tools> Advanced Search & Replace > Click Install All to load all predefined presets.

UPDATING THE PLUGIN:
NOTE: If you are using the portable version of MusicBee, you can update the plugin only by copying  the file mb_TagTools.dll from the archive mb_TagTools.zip to "Plugins" folder in the MusicBee application folder. This will keep all ASR presets as is.

OTHERWISE:
1- Download the appropriate ZIP file and unpack it to a temporary folder of your choice.
2- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Disable > Close and restart MusicBee.
3- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Add Plugin... > browse to the folder where the updated file mb_TagTools.zip is located and open this file. Close preferences.

UPDATING THE ASR PRESETS:
1- Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a- Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b- Click the "Install New" button to (re)install predefined presets which were created or updated by the plugin developer since last time you installed or updated them by either of two methods.

IMPORTANT NOTE: "Install New" will not reinstall any predefined presets deleted by you. Predefined presets can't be edited but can be "customized." Most predefined presets allow changing some options. Adjusting some criteria of a predefined preset will result in a "customized" preset. Both installation commands will ask you if you want to update the customized preset(s) (if any) and lose your adjustments, or to skip those updated by the plugin developer and update only those not customized by you.

REMOVING THE PLUGIN:
1- Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins.
2- Additional Tagging & Reporting Tools > Uninstall. MusicBee will delete all automatically created files (e.g. settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolders "ru" and "ASR Presets" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder "%AppData%\MusicBee".

Unfortunately, no plugin can be uninstalled from Store version of MusicBee at the moment.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 11, 2023, 10:51:31 PM
How about "custom-defined presets"? Or "user-defined presets"?
What would be the difference between a 'custom preset' (what most people will understand without much explanation) and a 'custom-defined preset'? (which I have never heard of before and have no idea of what that means)

Quote
I think any reference to "the developer" should be changed to "the plugin developer."
So we disagree about using the term 'developer' in a user interface.
So if I create a custom preset for AT&RT and share it, am I the 'preset developer'?
Or is there now just another custom preset out there?

edit
Or maybe I am mixing up what you have been discussing about the user interface of the plugin itself vs. explanatory texts?
Hm, this is why I thought it would be better to leave you and boroda at it and just await the next version of the plugin and the explanatory texts before opening my mouth.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 12, 2023, 03:32:57 PM
How about "custom-defined presets"? Or "user-defined presets"?
What would be the difference between a 'custom preset' (what most people will understand without much explanation) and a 'custom-defined preset'? (which I have never heard of before and have no idea of what that means)

you probably have missed my recent explanation.

i've changed the terms i'm using recently to avoid this confusion. now there are "user presets" - they are not named anymore "custom presets", there are now no "custom presets" at all - (user presets are either created by user from scratch or copied from predefined presets), and there are "customized predefined presets" (along with "predefined presets", which are not changed by user at all). customized presets are small adjustments of predefined presets without converting them to user presets. only <tag #> and <custom text #> field can be "customized".
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 12, 2023, 03:43:17 PM
@boroda...

I've incorporated your latest changes (deletes/adds/corrections) into this:
...
@phred, i think we will stop on this edition. it's completely acceptable from my point of view.

i still have one question. that's where my english is too poor to determine if this phase means in english what i want:

     NOTE: If you are using the portable version of MusicBee, you can update the plugin only by copying the file mb_TagTools.dll from the archive mb_TagTools.zip

here i meant "update only the plugin by copying the file", not "update the plugin by only copying the file"

does this english phrase from your latest version of readme mean what i intend to?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 12, 2023, 10:32:51 PM
Hi

After installing the plugin for the first time (5.5 versión) the item "Additional Taggin & Reporting Tools" appears in the Tools Menu but doesn't include any commands.

(https://i.ibb.co/gFLHw2S/Sin-t-tulo.png)

Apologies if this issue has been addressed already, I can't seem to find it

it's known issue. it's not very important, but difficult to fix, so i'm leaving it unresolved for ages. you simply have clicked mb menu too quickly, before full plugin initialization. i'm always waiting a couple of seconds before trying to use plugin menu.

1. i've tried to fix this issue. now, plugin menu creation is not 100% reliable, but much more reliable than earlier.

-------------

2. from now plugin menu placement can't be changed, menu always is located under mb "tools" menu.

3. any adjustments of menu in plugin settings take effect immediately. mb restart is not required anymore.

4. two text labels are placed in ASR window, which notify if selected preset is user preset, or if it is customized. 

5. some corrections of info messages in plugin (@phred, thank you).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

-------------

@phred, hiccup, i've uploaded plugin to github, changed plugin description on add-on page, and uploaded plugin .zip (see the link on add-on page) structured in new way (.zip contains files mb_TagTools.zip, README FIRST!.txt and README FIRST (RUS)!.txt).

if you have any critical comments, I will be happy to listen to them.

https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 12, 2023, 10:56:09 PM
@phred, i think we will stop on this edition. it's completely acceptable from my point of view.
Ok. Just note that I'm still available (as time permits) to help out further if needed.
It's been a pleasure doing business with you.   :-)

Quote
i still have one question. that's where my english is too poor to determine if this phase means in english what i want:
     NOTE: If you are using the portable version of MusicBee, you can update the plugin only by copying the file mb_TagTools.dll from the archive mb_TagTools.zip
here i meant "update only the plugin by copying the file", not "update the plugin by only copying the file"
does this english phrase from your latest version of readme mean what i intend to?
Hmmm ... I've worked on this for a bit of time today and finally asked my wife to take a look. She's an editor and copywriter and knows English better than Shakespeare.
We have come up with:
If you are using the portable version of MusicBee, you have the ability to update just the plugin (mb_TagTools.dll) without updating any presets. To update only the plugin, simply copy the file mb_TagTools.dll from the zipfile to the plugins folder of MusicBee. You'll have to give permission to overwrite the existing file.

How's that?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 13, 2023, 08:24:59 AM
great! i'll change readme.
Title: Re: Additional Tagging & Reporting Tools
Post by: adac on January 13, 2023, 09:52:02 AM
You guys are really crazy... I've been watching it all these days now. Thank you in advance for your great work. I think it will be another great help to everyone to use this great addon in this great program. Thanks alot. That just had to be said  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 15, 2023, 06:32:31 AM
some bug fixes in ASR and MSR:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 16, 2023, 04:46:28 PM
So over the last week or so I have been looking at the recent updates to both the plugin and the readme and have been taking some notes.
Here they are:

- about the interface

(https://i.imgur.com/F6qwGpQ.png)
This button will add a star to filter out presets that have a hotkey assigned to them.
But at every subsequent click it will just be adding other stars.
I think it would be better if it would toggle between one star vs. no star.
Then also the 'close' button next to it could be removed.


(https://i.imgur.com/vcf4FX5.png)
Shouldn't it be: (separated by ; )
It doesn't require two semi-colons, or does it?


A nitpick:
(https://i.imgur.com/WQdQPqc.png)
Personally I find the bold text not so nice to read. Perhaps make it regular. Maybe in a nice blue colour?
And perhaps make the header say: 'Preset description:'


These two buttons are next to each other:
(https://i.imgur.com/dndUR4A.png)
But one pertains specifically to presets, the other more to (changed) settings. A novice user would not understand that.

It would help if the 10 buttons on the left and the 4 on the right had some more obvious visual separation.
Maybe something like this:
(https://i.imgur.com/Pb0Dn5u.png)



(https://i.imgur.com/gMnfcDg.png)
This doesn't seem to work properly.
When selecting a predefined preset and use 'Rename/Edit' to edit the preset and then save it, the indicator will not say 'customised by user'.
(I'm not even sure it is supposed to be allowed to edit a predefined preset?)
When selecting a predefined preset and use 'Copy', make some change and save it, it will highlight 'User preset', not 'customised by user'.
So when should 'customised by user' get highlighted?

But, this also goes to the point that I have made earlier: Why not keep things simple, and use only two concepts of presets:
Just 'predefined preset' and 'custom preset'.

There are now: Predefined presets, Customised predefined presets, Customised by user presets, Shared presets, Own presets, and Custom presets.
(and maybe I missed some more)


(https://i.imgur.com/9jo8Kbz.png)
This one says 'shared presets'.
But in fact it is about 'custom presets'. If a preset has been shared with somebody or not is irrelevant here.
And there is no such thing as presets that can be shared with other people (or different installations) vs. presets that can't.
(well, some will work and some won't, depending on what custom or virtual tags it references, but that's a different matter?)

resulting pop-up balloons with texts like these certainly make no easy read:
(https://i.imgur.com/Mvk2w9G.png)


These two buttons both pertain to 'custom presets':
(https://i.imgur.com/4XCyTTs.png)

The 'export' button specifies it is about custom presets, the 'import' one doesn't.
And the export balloon mentions 'user presets', while the import balloon mentions 'shared presets'.

Why not name these buttons: 'Export custom…' and 'Import custom…'
And make both balloons use the words 'custom presets' instead of 'user' and 'shared'.

b.t.w.
If you do believe it is important to have a certain type of preset being described as 'customised predefined preset', perhaps change it to 'modified predefined preset'?
I think it's equally bad, but it would at least create some extra linguistic distance between it and 'custom preset'.


I think I understand part of the reason that this all came to be is the effort to stuff a lot of explanatory information and variables into the user interface. (both in buttons and balloons)
But I think the interface itself should be as clean and non-confusing as possible.
The same goes for pop-up balloons. They disappear after a couple of seconds and should be brief and comprehensible.

Any further explanations can well go into manuals.

Which brings me to another suggestion:
Have a 'help' button in the main panel. (or maybe a 'documentation' button)
Which leads to a webpage that contains detailed and updated information on the buttons and functions of AS&R.

- - -

-  about the forum topic & the plugin webpage:

Personally I like it if a plugin forum topic (the first post), or a plugin webpage contains a direct download link and perhaps a very brief explanation on how to install it.
Neither the AT&RT forum page, nor the plugin webpage has that, and the user will need to do more clicking to get to that.
Not a big problem, a user may be asked of to make some effort, but I think it wouldn't hurt making things a bit easier.
Not only for novice users, I would also like it if could download a new plugin version by simply clicking one link in the first forum post.
(or maybe Phred could add another link in his signature ;-)

- - -

-  uninstalling the plugin

Uninstalling the plugin using MB's configuration panel does not remove the folders 'RU' and 'ASR presets'
Shouldn't it?

- - -

-  about the readme.txt

1.
The readme text has a chapter on updating the plugin.
For updating a portable version of MB it explains that it allows for updating the plugin itself only.
But under 'OTHERWISE' it does not explain what gets updated exactly.
So is that updating procedure in fact identical to doing a clean install of the plugin?
Are predefined or custom presets affected in anyway?

2.
There is a chapter: UPDATING THE ASR PRESETS:

1 – Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a – Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b – Click the "Install New" button to (re)install predefined presets which were created or updated by the plugin developer since the last time you installed or updated them by either of two methods.



It doesn't say anything about how the user would acquire these updated predefined presets.
And I am assuming that the 'Install new' button does not have the functionality to download new presets by itself.
(which would not be a bad idea?)
So there probably should be some steps added to the tutorial about downloading and extracting files?

The same goes for the related buttons in the interface itself.
When a user clicks the 'Install new' button (and predefined presets are already present), it will just say that nothing was changed:

(https://i.imgur.com/zh35PqM.png)
not giving any explanation to the user about the mechanics behind it.
He would have to guess that a newer set of presets should have been downloaded first.
I'm not sure about how to improve on that exactly, but one option could be to have that button opening a filebrowser that defaults to the location where the plugin is looking for 'updated presets'. That would make things much more obvious to the user.


And pressing 'Install all' can result in this:
(https://i.imgur.com/jEesUvc.png)

So it's a successful error?  ;-)

Also, contrary to what it says, nothing was updated in this case.
It will also say this if you click the button and hadn't downloaded any new presets at all.

- - -

I'm sorry if all this comes across at criticism.
While it probably is in a way, I really like the improvements that have been made over the last couple of weeks/months.
So this is just another effort in trying to help making things even better…
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 16, 2023, 04:56:33 PM
It would help if the 10 buttons on the left and the 4 on the right had some more obvious visual separation.
Maybe something like this:
(https://i.imgur.com/Pb0Dn5u.png)
I appreciate the time it must've taken you to test, make notes, and create the reply. I, as "editor" of the readme, will do nothing until boroda has had time to digest your comments and makes changes.

As for the interface, I think the suggestion I quoted is an award-winner. It really makes it clear which buttons are for which part of the plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 16, 2023, 05:01:24 PM
I appreciate the time it must've taken you to test, make notes, and create the reply. I, as "editor" of the readme, will do nothing until boroda has had time to digest your comments and makes changes.
1.
Many of these issues/questions have been simmering in my brain for a couple of years already.
Now that the momentum is there, it seemed a good idea to present them in a decent manner, trying to help making AT&RT less of an enigma than it used to be ;-)

2.
Yeah, also: I have some ideas for minor improvements on the readme myself, so it's probably better to wait so not to do any double work.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 19, 2023, 12:17:13 AM
- about the interface

(https://i.imgur.com/F6qwGpQ.png)
This button will add a star to filter out presets that have a hotkey assigned to them.
But at every subsequent click it will just be adding other stars.
I think it would be better if it would toggle between one star vs. no star.
Then also the 'close' button next to it could be removed.
'star' is just a part of the preset name, 'star button' simply adds 'star' character to the search field. 'close' button clears the search field, which can contain arbitrary text, not only 'star' character. also, you can search for some text AND 'star' character, i.e. search for some preset name only among presets with assigned hotkeys. i don't want to change current implementation.

(https://i.imgur.com/vcf4FX5.png)
Shouldn't it be: (separated by ; )
It doesn't require two semi-colons, or does it?
no, tag values must be separated by TWO semicolons, because one semicolon can be used in real tag value, e.g. in 'genre' tag (but not only in 'genre').

A nitpick:
(https://i.imgur.com/WQdQPqc.png)
Personally I find the bold text not so nice to read. Perhaps make it regular. Maybe in a nice blue colour?
And perhaps make the header say: 'Preset description:'
i'm avoiding using fixed color values because windows color scheme can be changed. i've changed text color in this panel to 'menu highlight' color. please check new coloring, as my windows color scheme is rather specific.

These two buttons are next to each other:
(https://i.imgur.com/dndUR4A.png)
But one pertains specifically to presets, the other more to (changed) settings. A novice user would not understand that.

It would help if the 10 buttons on the left and the 4 on the right had some more obvious visual separation.
Maybe something like this:
(https://i.imgur.com/Pb0Dn5u.png)
i've changed this. now ASR window looks similar to your makeup, but not exactly as on your screenshot.


(https://i.imgur.com/gMnfcDg.png)
This doesn't seem to work properly.
When selecting a predefined preset and use 'Rename/Edit' to edit the preset and then save it, the indicator will not say 'customised by user'.
(I'm not even sure it is supposed to be allowed to edit a predefined preset?)
When selecting a predefined preset and use 'Copy', make some change and save it, it will highlight 'User preset', not 'customised by user'.
So when should 'customised by user' get highlighted?
it's a bug. i haven't noticed it because i'm using the plugin in special 'developer mode' (some functionality disabled by default is enabled in this mode). of course, 'edit' button must be disabled for predefined presets. i've fixed this.

But, this also goes to the point that I have made earlier: Why not keep things simple, and use only two concepts of presets:
Just 'predefined preset' and 'custom preset'.
because there is no more concept of 'custom preset'. only 'user preset' and 'predefined preset'. well, also, 'customized predefined preset', which is a special case of 'predefined preset''.

There are now: Predefined presets, Customised predefined presets, Customised by user presets, Shared presets, Own presets, and Custom presets.
(and maybe I missed some more)


(https://i.imgur.com/9jo8Kbz.png)
This one says 'shared presets'.
But in fact it is about 'custom presets'. If a preset has been shared with somebody or not is irrelevant here.
And there is no such thing as presets that can be shared with other people (or different installations) vs. presets that can't.
(well, some will work and some won't, depending on what custom or virtual tags it references, but that's a different matter?)

resulting pop-up balloons with texts like these certainly make no easy read:
(https://i.imgur.com/Mvk2w9G.png)


These two buttons both pertain to 'custom presets':
(https://i.imgur.com/4XCyTTs.png)

The 'export' button specifies it is about custom presets, the 'import' one doesn't.
And the export balloon mentions 'user presets', while the import balloon mentions 'shared presets'.

Why not name these buttons: 'Export custom…' and 'Import custom…'
And make both balloons use the words 'custom presets' instead of 'user' and 'shared'.
no, no, no. i've simply forgotten to change some button names and tool tips. no more 'custom presets', i've fixed this. as for mentions of 'share/sharing', it's some specific of exported/imported presets, these presets are not some 'new type' of presets, but simply exporting/importing is intended mostly for preset exchanging, for sharing.

btw, could you inspect latest button names and tool tips? i think they now looks unified.

If you do believe it is important to have a certain type of preset being described as 'customised predefined preset', perhaps change it to 'modified predefined preset'?
I think it's equally bad, but it would at least create some extra linguistic distance between it and 'custom preset'.
again, there is no more 'custom presets'. but maybe i'll change very long term 'customized predefined preset' to just 'customized preset' later, because only predefined presets can be customized anyway. user presets can be just edited by user, not customized. i'm keeping this long term for now to avoid confusing with former 'custom presets' (which are now 'user presets') by old users.

I think I understand part of the reason that this all came to be is the effort to stuff a lot of explanatory information and variables into the user interface. (both in buttons and balloons)
But I think the interface itself should be as clean and non-confusing as possible.
The same goes for pop-up balloons. They disappear after a couple of seconds and should be brief and comprehensible.

Any further explanations can well go into manuals.

Which brings me to another suggestion:
Have a 'help' button in the main panel. (or maybe a 'documentation' button)
Which leads to a webpage that contains detailed and updated information on the buttons and functions of AS&R.
who would write this help page? i'll be happy to add 'help' button to ASR window.

Personally I like it if a plugin forum topic (the first post), or a plugin webpage contains a direct download link and perhaps a very brief explanation on how to install it.
Neither the AT&RT forum page, nor the plugin webpage has that, and the user will need to do more clicking to get to that.
Not a big problem, a user may be asked of to make some effort, but I think it wouldn't hurt making things a bit easier.
Not only for novice users, I would also like it if could download a new plugin version by simply clicking one link in the first forum post.
(or maybe Phred could add another link in his signature ;-)
i'll add download link to 'mb_TagTools_latest.zip' to the first post of plugin topic (and will try to revise this post, but keeping it in relevant up-to-date state is too tedious. so i don't want to write full plugin description on this page).

-  uninstalling the plugin

Uninstalling the plugin using MB's configuration panel does not remove the folders 'RU' and 'ASR presets'
Shouldn't it?
it shoud! and not only 'ru' and 'asr presets' folders, but also plugin .dll. but this can't be done by plugin. i've requested Steven for full support of plugins uninstalling (and simplier way of reinstalling). waiting for his responce (but this support won't impleneted in mb for 3.5, maybe for 3.6 only). though deletion of 'asr presets' folder CAN be done by plugin if plugin IS NOT installed to 'c:\program files\musicbee\plugins' folder.

-  about the readme.txt

1.
The readme text has a chapter on updating the plugin.
For updating a portable version of MB it explains that it allows for updating the plugin itself only.
But under 'OTHERWISE' it does not explain what gets updated exactly.
So is that updating procedure in fact identical to doing a clean install of the plugin?
Are predefined or custom presets affected in anyway?
clean install of the plugin: yes it's plugin reinstallation to the latest version, so 'updating'.

Are predefined or custom presets affected in anyway?: no. any working asr presets are not changed in any way in this step. preset management must be done after plugin update.

2.
There is a chapter: UPDATING THE ASR PRESETS:

1 – Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace.
2a – Click the "Install All" button to install all predefined ASR presets. This installs all predefined presets and will update to the latest version any preset(s) that have already been installed.
OR
2b – Click the "Install New" button to (re)install predefined presets which were created or updated by the plugin developer since the last time you installed or updated them by either of two methods.



It doesn't say anything about how the user would acquire these updated predefined presets.
And I am assuming that the 'Install new' button does not have the functionality to download new presets by itself.
(which would not be a bad idea?)
So there probably should be some steps added to the tutorial about downloading and extracting files?

The same goes for the related buttons in the interface itself.
When a user clicks the 'Install new' button (and predefined presets are already present), it will just say that nothing was changed:

(https://i.imgur.com/zh35PqM.png)
not giving any explanation to the user about the mechanics behind it.
He would have to guess that a newer set of presets should have been downloaded first.
I'm not sure about how to improve on that exactly, but one option could be to have that button opening a filebrowser that defaults to the location where the plugin is looking for 'updated presets'. That would make things much more obvious to the user.
i don't know how to describe all this in a simple and clear manner. presets are downloaded during plugin download. they are included in plugin .zip. adding/updating plugin also adds to/updates presets in "local preset repository" (special asr presets folder, which is different from asr preset working folder). ideally there must be no "local preset repository" at all to simplify the entire concept of preset 'installing' (what could be renamed to preset 'downloading' in this case). but downloading files programmatically from publically available services such as Google Drive is not so easy, and is not worth required efforts.

i will be very glad if you or @phred suggest some readme modifications, concerning this aspect.

And pressing 'Install all' can result in this:
(https://i.imgur.com/jEesUvc.png)

So it's a successful error?  ;-)
yes, very stupid bug  :) . i was sure that passing null pointer instead of empty string to message box title will result in empty title. it turned out not to be so. it's fixed.

Also, contrary to what it says, nothing was updated in this case.
It will also say this if you click the button and hadn't downloaded any new presets at all.
this info message should mean 'updated in case of installing new presets or reinstalled in case of installing all presets'. i've slightly changed this info message.

I'm sorry if all this comes across at criticism.
While it probably is in a way, I really like the improvements that have been made over the last couple of weeks/months.
So this is just another effort in trying to help making things even better…

no, I myself asked to make critical comments.

i've given as much explanations as i could. now waiting for you and @phred to suggest new wordings for ui elements (or to accept my new wordings), and new corrections of readme.

---------------------------------------------------------------------------------------------

latest plugin version:

NOTE: i highly recommend to delete both 'asr presets' folders ('plugins\asr presets' and '<mb appdata>\asr presets') before updating plugin and reinstall all asr presets from scratch (i've changed preset naming to avoid preset files duplicating in future if only names of some presets are changes. predefined presets files from plugin zip are named according to guids again, but preset filenames will be changed to friendly names after any saving of asr settings).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 19, 2023, 12:42:39 AM
- about the interface

(https://i.imgur.com/F6qwGpQ.png)
This button will add a star to filter out presets that have a hotkey assigned to them.
But at every subsequent click it will just be adding other stars.
I think it would be better if it would toggle between one star vs. no star.
Then also the 'close' button next to it could be removed.
'star' is just a part of the preset name, 'star button' simply adds 'star' character to the search field. 'close' button clears the search field, which can contain arbitrary text, not only 'star' character. also, you can search for some text AND 'star' character, i.e. search for some preset name only among presets with assigned hotkeys. i don't want to change current implementation.
I should be in my REM sleep right now, so I'll only respond to this one point for now.
Trying to place myself in the position/thinking of a 'simple' user:
 
There is a button that simply says 'show presets with assigned hotkeys only'
I would be expecting it to do just that. I wouldn't care about 'stars'. And I would be confused that it adds 'stars' after pressing it again.
What is the purpose of having it adding more stars? I'm confused. I'm going to hit the pillow. Maybe I have a different view on it tomorrow.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 19, 2023, 03:00:29 AM
i've changed this. now ASR window looks similar to your makeup, but not exactly as on your screenshot.
This looks much better now.

Quote
who would write this help page? i'll be happy to add 'help' button to ASR window.
Not me!! But I would be happy to read it and offer grammatical suggestions and corrections.


(or maybe Phred could add another link in his signature ;-)
Sorry, but there are only a limited number of characters allowed in a signature and I already asked Steven to up the maximum quite some time ago. Personally I don't like to see a signature that's longer than the reply.

Quote
i've given as much explanations as i could. now waiting for you and @phred to suggest new wordings for ui elements (or to accept my new wordings), and new corrections of readme.
I will look this over more carefully tomorrow. In the meantime, could you (boroda) please PM me the latest version of the readme? Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 19, 2023, 09:10:32 AM
'star' is just a part of the preset name, 'star button' simply adds 'star' character to the search field.
Wait, so that's a search/filter bar...

My brain never registered that. (even though I now see there's a search icon)
I feel a little bit dumb now.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2023, 12:03:32 AM
i've added a tooltip over the search bar.

process of preset installing is changed: 'install new' will always silently update all (customized or not) predefined presets, preserving all customizations. 'install all' will ask the user (only if some presets are customized) if he wants to reinstall all presets resetting all customizations, or preserving all customizations.

info messages related to preset installing are more detailed now (e.g. real preset updating to newer versions and preset reinstalling from stock versions (e.g. in case of damaged working presets) is now distinguished).

numerous minor ui bug fixes, related not only to ASR.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

edit:

plugin now tries to delete 'plugins\asr presets' folder on uninstallation. this folder can't be deleted by plugin only if plugin is installed to "program files\musicbee\plugins" folder, i.e. installed manually, not using 'add plugin' button in mb prefs.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 20, 2023, 04:34:14 PM
- about the interface

(https://i.imgur.com/F6qwGpQ.png)
This button will add a star to filter out presets that have a hotkey assigned to them.
But at every subsequent click it will just be adding other stars.
I think it would be better if it would toggle between one star vs. no star.
Then also the 'close' button next to it could be removed.
'star' is just a part of the preset name, 'star button' simply adds 'star' character to the search field. 'close' button clears the search field, which can contain arbitrary text, not only 'star' character. also, you can search for some text AND 'star' character, i.e. search for some preset name only among presets with assigned hotkeys. i don't want to change current implementation.

1.
Why not make that part of the panel completely obvious?
Since a user will probably not be entering more than two or three search words in the search field, there is no need for it to be that wide.
Then something like this could be done:

(https://i.imgur.com/SoAfNpz.png)


2.
The non-bold text for preset description reads nicer.
Only the light-blue on grey contrast is a bit low (my eyes? my monitor?)
Perhaps the text could be made a little bit darker?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 20, 2023, 04:51:53 PM
Which brings me to another suggestion:
Have a 'help' button in the main panel. (or maybe a 'documentation' button)
Which leads to a webpage that contains detailed and updated information on the buttons and functions of AS&R.
who would write this help page? i'll be happy to add 'help' button to ASR window.
I was not thinking of a brand new webpage.
There is already a lot of info on the plugin page, and also in the forum start post.
So the button could link to one of those?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 24, 2023, 02:26:55 AM
I was not thinking of a brand new webpage.
There is already a lot of info on the plugin page, and also in the forum start post.
So the button could link to one of those?
where? this page must be written from scratch to consolidate all info scattered across the forum and plugin page. it doesn't matter where this page must be located. it must be a new page anyway (even if it would be just another page on this topic).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 24, 2023, 02:29:20 AM
i've added a new button to ASR window to filter out only presets with assigned function ids:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 24, 2023, 03:01:36 AM
Why not make that part of the panel completely obvious?
Since a user will probably not be entering more than two or three search words in the search field, there is no need for it to be that wide.
Then something like this could be done:

(https://i.imgur.com/SoAfNpz.png)
because 'star' and (new) 'gear' characters are part of preset names. i've added these 2 buttons only because 'star' and 'gear' characters can't be typed on keyboard. auto-applied presets don't change their names, so there is no button to filter them, there is a checkbox for this. also, search algorithms for 'starred'/'geared' presets and for 'ticked' presets are completely different.

but i'll change tool tips for 'star' and 'gear' buttons to make their functions more clear.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 24, 2023, 03:18:15 AM
(https://i.imgur.com/SoAfNpz.png)
In the block of text at top, it states "Tick presets to automatically apply them..."
In the search/filter presets line, it shows "[] Active presets."
I think for the sake of consistency "Active presets" should be changed to "Auto presets". Or better still, but I don't think there's enough room, "Auto-apply presets".
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 24, 2023, 06:09:43 PM
because 'star' and (new) 'gear' characters are part of preset names. i've added these 2 buttons only because 'star' and 'gear' characters can't be typed on keyboard. auto-applied presets don't change their names, so there is no button to filter them, there is a checkbox for this. also, search algorithms for 'starred'/'geared' presets and for 'ticked' presets are completely different.
I understand that, but I also think a user would not be interested in the behind-the-screen workings of such buttons.
Show all? yes/no, Filter custom presets? yes/no, Filter hotkey-assigned presets? yes/no
Those seen obvious choices, so the interface (in my opinion) would best reflect that.
(but if it makes things programmatically a bit too complicated I understand that too)


I'm getting this error with the latest version:

Code
MusicBee v3.5.8402.19544P  (Win10.0), 24 Jan 2023 18:58:

System.ArgumentException: Value of '-22' is not valid for 'red'. 'red' should be greater than or equal to 0 and less than or equal to 255.
   at System.Drawing.Color.CheckByte(Int32 value, String name)
   at System.Drawing.Color.FromArgb(Int32 alpha, Int32 red, Int32 green, Int32 blue)
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.initializeForm()
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand..ctor(Plugin tagToolsPluginParam)
   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 & Reporting Tools
Post by: boroda on January 24, 2023, 06:46:51 PM
@hiccup, i've not made check for correct color values, hoping that all must work as is.

i've changed preset description color to more dimmed (though this color is derived from system 'menu highlight' color anyway). it now looks much better using my current windows color scheme, but i must check new coloring using other color schemes. also, i've not yet added the check if new color is always correct (e.g. doesn't have negative color components). it seems that new color will be always correct, but i need to check this.

i've added a new 'playlist' button to search for presets, which are constrained to playlist.

all tool tips for 'star', 'gear' and 'playlist' buttons are changed.

behavior of these buttons is also changed. now they toggle search mode (adding/removing corresponding characters to/from search field).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

------------------

i'm still reluctant to convert search buttons to checkboxes. maybe, i'll do this, not sure.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 24, 2023, 06:56:14 PM
i'm still reluctant to convert search buttons to checkboxes. maybe, i'll do this, not sure.
It's obviously your decision.
I'm only throwing out some opinions and ideas.
And I believe nobody else has been sharing his opinions on this aspect of the interface, so maybe it's just me ;-)

The download still produces the error.
(v.5.6.8424)

Perhaps Mediafire is slow in updating, or there is some caching issue going on?
I will be trying it out again at a later time.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 25, 2023, 05:23:20 AM
i've replaced search buttons by checkboxes. also, i've changed coloring algorithm for preset description: maybe it's not very great for my own color scheme, but it least it works acceptably for all color schemes i've tried (~10 schemes).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 25, 2023, 05:57:49 PM
...it now looks much better using my current windows color scheme, but i must check new coloring using other color schemes. also, i've not yet added the check if new color is always correct (e.g. doesn't have negative color components). it seems that new color will be always correct, but i need to check this.
Things look fine to me.
Personally I wouldn't worry about making small adjustments for themes (skins).
I never use 'match MusicBee skin colours', since for most of the skins I use the AS&R panel then becomes ugly and pretty much unusable.
Complete skin support might be nice, but I think I recall that was not possible, or very complicated to do.
Not a problem, the default 'Windows theme' is working fine for me.

Quote
all tool tips for 'star', 'gear' and 'playlist' buttons are changed.
The option to filter on hotkey-assigned presets seems to be gone?
Is that intentional?
(also, the filter button for 'custom presets' has the pop-up balloon for 'hotkey-assigned')
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 25, 2023, 11:29:41 PM
The option to filter on hotkey-assigned presets seems to be gone?
Is that intentional?
(also, the filter button for 'custom presets' has the pop-up balloon for 'hotkey-assigned')
should be there. but i've already deleted the previous plugin version and can't check this. redownload plugin from the same link (i've made minor bug fixes).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 26, 2023, 08:20:22 AM
The option to filter on hotkey-assigned presets seems to be gone?
Is that intentional?
(also, the filter button for 'custom presets' has the pop-up balloon for 'hotkey-assigned')
should be there. but i've already deleted the previous plugin version and can't check this. redownload plugin from the same link (i've made minor bug fixes).

Now there is no 'filter on custom presets' option anymore.
Was that removed intentionally?
5.6.8426
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 26, 2023, 01:33:20 PM
custom presets? there was never such a filter. but i'll add it, it seems to be useful.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 26, 2023, 01:44:36 PM
custom presets? there was never such a filter. but i'll add it, it seems to be useful.
Ah yes, here's why I thought that:
Pretty much all my custom presets have keyboard-shortcuts, so if I wanted to see only my custom presets, I ticked the * filter button.
So in my mind it was a custom preset filter.
Adding an actual custom preset filter seems like a good idea to me.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 26, 2023, 02:28:39 PM
i've added user preset and predefined preset filters (of course, you can untick both filters to view both user and predefined presets):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 26, 2023, 03:24:08 PM
i've added user preset and predefined preset filters
Doing a brief test, my user presets do not get filtered and are regarded (same) as predefined presets.

Could you explain the mechanics behind it a bit?
Does this maybe require a specific way how user presets should be imported?
(they were already present in this case, I updated the plugin by simply copying the new dll)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 26, 2023, 10:47:58 PM
suggest that these presets weren't loaded as user presets after changing preset format (".ASR Presest.xml" -> ".asr-preset.xml"). i was fiddling with old format loading during some time, now loading of old format presets must work fine, but your presets are already converted to new format.

to check that this is not a bug with presets list filtering, select one of your user presets and see if the label "user preset" below preset list is marked by a tick.

if you want to convert your old custom presets to "user presets" (to preserve them on any preset reinstalling/updating), just copy them one by one (every copy of any preset is always a user preset), and delete old custom presets.

-----------------------------

download new version - a bit more filters, and minor bug fixes:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 27, 2023, 02:50:42 AM
@boroda...

I'm just catching up from the past few days. It appears that you've changed the filename of the presets. Is that intentional, and if so, why? They were so much easier to know which was with with actual -names- rather than whatever these are now...
(http://i.imgur.com/QCqcFLCl.jpg) (https://i.imgur.com/QCqcFLC.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 27, 2023, 03:56:09 AM
predefined presets included in plugin zip are now named so that ASR always imports latest presets (no matter which presets are already stored in "local preset repository"/"preset distribution" folder - or how should i name this folder?) independently of their displayed names. but this concerns only presets stored in plugin .zip and in "plugins\asr presets\" folder (folder where ASR imports working presets from). any presets will be (re)installed to/updated in ASR working folder ("<mb appdata>\asr presets\"), or resaved in ASR working folder on saving ASR settings, using preset displayed names.

if you are manually copying presets from plugin .zip to ASR working folder ("<mb appdata>\asr presets\"), not using "install all"/"install new" buttons, then just open ASR and click "save all & close" to resave all presets in working folder using displayed names.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 27, 2023, 11:18:26 AM
Jesus lads, I disappear into real-life-issues for a few weeks and all hell breaks loose here.  ;)

Boroda, not exactly a criticism, but I'm at a loss to see how you turned Hiccup's magnificent filtering mock-up into something that looks like Pac-Man...

(https://i.imgur.com/4Qgn2aY.png)

I don't know what .NET calls them, but whatever happened to (WinAPI) ComboBox/Dropdownlist controls?  Granted, selecting combinations of filters is more difficult, but for quick and dirty filtering (without having to read 7 different tooltips), it's a lot more compact and readable than... Pac-Man.  The object here (or at least as I interpret Hiccup's suggestions) is to make it accessible to beginners.  Pac-Man is not for beginners.  :(

That aside, I have a suggestion/request about something else.  Since the ALR window has a little "Preset Not Saved" indicator that pops up when you edit something, could the ASR window have something similar?  Not for every little change (that would be too much to track), but principally when actual custom-presets are edited: Reg-ex lines, writable-tags, etc. Many times I have accidentally hit the close button (forgetting to save first) only to discover my mistake later.  Maybe a little modal popup that says "Modified Presets are Not Saved, are you sure you want to continue?"

Yes, I know, you can just tell me to always use "Save All & Close", but that button's not exactly in a logical position - maybe at least some kind of indication that saving's necessary?  As an extreme choice, maybe just auto-save everything and replace the save buttons with a simple Cancel button instead.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 27, 2023, 01:06:07 PM
if you are manually copying presets from plugin .zip to ASR working folder ("<mb appdata>\asr presets\"), not using "install all"/"install new" buttons, then just open ASR and click "save all & close" to resave all presets in working folder using displayed names.
Perfect! Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 27, 2023, 08:03:15 PM
Jesus lads, I disappear into real-life-issues for a few weeks and all hell breaks loose here.  ;)

Boroda, not exactly a criticism, but I'm at a loss to see how you turned Hiccup's magnificent filtering mock-up into something that looks like Pac-Man...

(https://i.imgur.com/4Qgn2aY.png)
it seems that plugin uses wrong fonts on your pc. it's not what i see:

(https://i.imgur.com/pMUB2yv.png)

i've tried to fix this issue, could you check new plugin version using your windows/musicbee setup?

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 27, 2023, 09:23:06 PM
Nope, 5.6.8427 looks precisely the same.  I switched off the "Use skin colours" option (just in case) and the result is identical.  This machine is using Win7, so it's entirely possible that whatever symbolic font you're attempting to access is not installed.

(Although now the already small Listview text font is completely ignoring a 1.25 DPI setting, so it's gotten even smaller.  Oh joy.  But at least now I can see the character-descenders, so that's something.)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 29, 2023, 03:45:29 AM
i've enlarged the font of the preset list, and changed font symbols to icons above the preset list. also, i've added confirmation on ASR window closing if there are unsaved changes. but i've failed to fix preset customization symbols in preset list itself for pre-windows 10 systems (in red rectangle):  

(https://i.imgur.com/XXfq0gr.png)

---------------------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 06:31:40 AM
i've enlarged the font of the preset list, and changed font symbols to icons above the preset list.
Filter icons work fine now (as long as skin colours aren't being used, where they disappear for dark skins).  

i've added confirmation on ASR window closing if there are unsaved changes  
The warning modal displays even when Save All & Close is pressed, which is a bit redundant (especially as the icon only displays on the Close button).  I'm thinking some people might find the popup slightly annoying as it shows for even really minor (non-Preset-Editor) changes, but I understand the thinking behind it.

I still think a dropdown selection button for filtering (and/or even preset importing) would simplify the UI by removing a lot of clutter-controls (words are always clearer than icons), but at least it's not Pac-Man anymore, and (under normal circumstances) the icons do at least directly relate to what's shown in the preset list, so they make sense.  But 8 different buttons to filter 1 little listview?  Hmm.

That being said, much improved overall!  Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 29, 2023, 07:14:21 AM
Filter icons work fine now (as long as skin colours aren't being used, where they disappear for dark skins). 
will try to fix it.

The warning modal displays even when Save All & Close is pressed, which is a bit redundant (especially as the icon only displays on the Close button).  I'm thinking some people might find the popup slightly annoying as it shows for even really minor (non-Preset-Editor) changes, but I understand the thinking behind it.

I've just overlooked this. it will be fixed.

I still think a dropdown selection button for filtering (and/or even preset importing) would simplify the UI by removing a lot of clutter-controls (words are always clearer than icons)...
 
i'm not sure how you imagine this dropdown button. could you make a mockup?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 29, 2023, 09:17:25 AM
When pressing 'Save all & close', it doesn't seem to do any saving? (nor closing):

(https://i.imgur.com/CUS9a32.png)


I find the font sizes in the panels quite unbalanced.
In the presets panel they are so large that longer names can't be read. (unless widening the whole panel)
The preset description panel has a much smaller font that makes it harder to read.
Perhaps have them both at an identical in-between font size?

(https://i.imgur.com/5mmbE7B.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 10:53:22 AM
i'm not sure how you imagine this dropdown button. could you make a mockup?
The dropdown is just the standard pedestrian control:

(https://i.imgur.com/bJAsJZS.png)

The useful part is how the WC_COMBOBOXW/CBS_DROPDOWNLIST control actually works.  

Code
case Combo_FILTERPARSING :
   switch (HIWORD(wParam)) {
      case CBN_SELENDOK : // Selection is about to change... get current (old) selection (if needed)
      case CBN_SELCHANGE : // Selection has actually changed, so apply new filter

I don't claim to know how the .NET framework works, but I believe it's still the standard WinAPI Msg/Event-driven system underneath which does the rendering at the end of the day.  You can take advantage of the SELCHANGE msg in real-time to apply the filter without any silly extra "apply" buttons.

Obviously, this only allows the user to apply one filter at a time, but if one wanted to entertain madness, they could add a whole ridiculous system of "if the user holds <Ctrl> while clicking the filters could be layered", etc, but that's severe overkill.

It's just an idea.

Oh, and as per Hiccup's idea with the font sizes, whatever you do please don't make anything smaller - some of us are probably older than others.   ;)  Either that, or at least make it more DPI aware.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 29, 2023, 01:52:46 PM
When pressing 'Save all & close', it doesn't seem to do any saving? (nor closing):

(https://i.imgur.com/CUS9a32.png)

you can click "yes" and changes will be saved. but it's of course an overlooked bug, and it's already fixed. redownload plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

I find the font sizes in the panels quite unbalanced.
In the presets panel they are so large that longer names can't be read. (unless widening the whole panel)
The preset description panel has a much smaller font that makes it harder to read.
Perhaps have them both at an identical in-between font size?

(https://i.imgur.com/5mmbE7B.png)

this question is completely up to users. Messiaen "complained" that font used in preset list is a bit small. i'm open to suggestions, and am ready to make any font sizes for preset list and preset description.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 29, 2023, 02:15:26 PM
i'm not sure how you imagine this dropdown button. could you make a mockup?
The dropdown is just the standard pedestrian control:

(https://i.imgur.com/bJAsJZS.png)

The useful part is how the WC_COMBOBOXW/CBS_DROPDOWNLIST control actually works.  
no, the problem is not implementation (well, in most cases, and not in this case). the problem is design of UI/UX.

i can make dropdown, which allows setting multiple filters. but dropdown doesn't allow to quickly show, which filters are currently set.

again, i'm open to discussion about any UI/UX elements, but they should be acceptable for most users.

---

my development of your idea: dropdown, clicking adds/removes filter (or another variant: clicking switches current filter, ctrl+clicking adds/removes filter), 1st item resets all filters (it can be named either "reset all" or "no filters"), dropdown list shows all checked filters, and row of compact highlighted/dimmed icons without checkboxes quickly show, which filters are active.

your (and hiccup, phred) opinion?

---

btw, i've changed coloring of filter icons in last plugin version, for plugin to obey current color scheme lightness - either lightness of mb skin colors (if plugin uses skin colors) or lightness of windows colors (e.g. light/dark mode).
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 03:01:25 PM
my development of your idea: dropdown, clicking adds/removes filter (or another variant: clicking switches current filter, ctrl+clicking adds/removes filter), 1st item resets all filters (it can be named either "reset all" or "no filters"), dropdown list shows all checked filters, and row of compact highlighted/dimmed icons without checkboxes quickly show, which filters are active.
That's more or less what I said - though I was just giving an example of "quick and dirty" filtering without worrying about applying multiple filters at once - personally I've never really needed more than one at a time, but I'm simple that way.  :)  I'm mainly just suggesting a more condensed alternative to 8 consecutive checkboxes - that was a fine idea back when it was just a couple of filters, but now...

And (just for verification), yes Icons now show properly in dark theme, and the Save All/Close works as expected; thank you.

For parity, I might suggest the same popup warning be applied to the ALR window if closing without hitting the "Update preset" button first.  Also, the "Preset not saved" text is a little hard to see (dark blue on dark-theme background) doesn't work well.  Maybe red-text, as warning?  And/or the icon you use on the ASR close button is nice and clear too, so maybe that.

The two windows (ASR/ALR) obviously shouldn't look the same, but they should at least behave similarly for UI consistency, and have similarly named buttons... Like, how is "Update Preset" different from just Save?  ASR doesn't use the same terminology, so it stands out as "odd" (to me).
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 29, 2023, 03:02:35 PM
5.6.8429 is throwing this:
Code
MusicBee v3.5.8421.33583P  (Win10.0), 29 Jan 2023 9:59:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.presetList_ItemCheck(Object sender, ItemCheckEventArgs e)
   at System.Windows.Forms.CheckedListBox.OnItemCheck(ItemCheckEventArgs ice)
   at System.Windows.Forms.CheckedListBox.SetItemCheckState(Int32 index, CheckState value)
   at System.Windows.Forms.CheckedListBox.SetItemChecked(Int32 index, Boolean value)
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.initializeForm()
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand..ctor(Plugin tagToolsPluginParam)
   at MusicBeePlugin.Plugin.asrEventHandler(Object sender, EventArgs e)
   at #=z09qWh4vN1pxXik4I5_AJNtNOHzqd.#=z0kxop_4=.#=z0i39nrE=(ApplicationCommand #=zcmfSZOE=, Object #=z03MCJ4c=, IList`1 #=zV00LM84=)
   at #=zWIZyVUuxNLL39$ggm5ULXcz19Z0b.#=zQR5oFdUR0lPU.#=zSXhXp0jQU1ix(MouseEventArgs #=zDE4WdZg=)
   at #=zWIZyVUuxNLL39$ggm5ULXcz19Z0b.OnMouseClick(MouseEventArgs #=zDE4WdZg=)
   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.Form.WndProc(Message& m)
   at #=zVKmx8Jq1oMbPbhNevsGwYtg=.WndProc(Message& #=zieEqYDo=)
   at #=zWIZyVUuxNLL39$ggm5ULXcz19Z0b.WndProc(Message& #=zieEqYDo=)
   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)

Rolled back to 5.6.8427 and no issues.

As for the dropdown menu, while it does indeed save space, I think being able to see exactly what is filtered is better. Also being able to simple tick a filter rather than mouse to open the dropdown and then mouse to the desired option.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 03:26:46 PM
...while it does indeed save space, I think being able to see exactly what is filtered is better. Also being able to simple tick a filter rather than mouse to open the dropdown and then mouse to the desired option.
My idea wasn't just to save space, part of the thought is to "not freak out the newbies" with too many options, like dozens of checkboxes which all do subtly different things.  But fine, nobody likes the dropdown idea, I can lose gracefully.  :)

(I've been opening/closing the windows on the nwest version without error, so that's strange...)
Title: Re: Additional Tagging & Reporting Tools
Post by: miste on January 29, 2023, 04:05:16 PM
Hey guys, I got the same error when I updated to the new version 5.6.8429

Code
MusicBee v3.5.8402.19544D  (Win10.0), 29 jan 2023 13:04:

System.NullReferenceException: Object reference not set to an instance of an object.
   em MusicBeePlugin.AdvancedSearchAndReplaceCommand.presetList_ItemCheck(Object sender, ItemCheckEventArgs e)
   em System.Windows.Forms.CheckedListBox.OnItemCheck(ItemCheckEventArgs ice)
   em System.Windows.Forms.CheckedListBox.SetItemCheckState(Int32 index, CheckState value)
   em System.Windows.Forms.CheckedListBox.SetItemChecked(Int32 index, Boolean value)
   em MusicBeePlugin.AdvancedSearchAndReplaceCommand.initializeForm()
   em MusicBeePlugin.AdvancedSearchAndReplaceCommand..ctor(Plugin tagToolsPluginParam)
   em MusicBeePlugin.Plugin.asrEventHandler(Object sender, EventArgs e)
   em System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   em System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   em System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   em System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   em System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   em System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   em System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   em System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   em System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   em System.Windows.Forms.Control.WndProc(Message& m)
   em System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   em System.Windows.Forms.ToolStrip.WndProc(Message& m)
   em System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   em System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   em System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 29, 2023, 04:07:03 PM
5.6.8429 is throwing this:
A reboot of the PC and the (re)installation of 5.6.8429 seems to have resolved the issue.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 29, 2023, 04:31:56 PM
this question is completely up to users. Messiaen "complained" that font used in preset list is a bit small. i'm open to suggestions, and am ready to make any font sizes for preset list and preset description.
As I said, I find the preset names too large, and the description a little bit to small.
If both would get the same size, e.g. the size of one font size larger than the rest of the text in the panel thing will probably look fine?

About the dropdown menu, I'm not crazy about the idea. Except for the fact of having text instead of icons, which would be an improvement in my opinion.
The icons by themselves are certainly nice, but I think icons would best be avoided for software that is not going to be used on a daily bases.
People just won't remember their functions.

So I am still a proponent of using text as much as possible. It is much more obvious and inviting to all sorts of users.
So, here is a rigorous idea that involves a lot of reshuffling of the panel:

(https://i.imgur.com/63QylxG.png)

But this will probably require a lot of work, so I could imagine boroda not getting very enthusiastic about the idea.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 29, 2023, 04:40:40 PM
While I agree with hiccup on text vs icons, the current layout (with icons) does provide a popup tool tip when hovering over each. Which for my purposes works well.

The mockup hiccup provides is a winner! But as he states, there are a lot of elements that need to be moved around and boroda many not have the time, or may not be interested in making sure a massive GUI update.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 29, 2023, 04:49:45 PM
... the current layout (with icons) does provide a popup tool tip when hovering over each. Which for my purposes works well.
I really dislike the need to hover over an icon to find out what it does.
You have to wait a few moments for the popup to show, and read it before it's gone again.
And the popup won't even always show at the first try.
And then you will probably have to repeat that effort before you have found the right checkbox to click.

I think it's a hindrance and should be avoided whenever possible.
If I want to play some (reverse) Whac-A-Mole I'll go the the fair or a game hall ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 29, 2023, 04:53:23 PM
I really dislike the need to hover over an icon to find out what it does.
I don't disagree on the Whack-A-Mole interplay of the tool tips. I was just pointing out that they exist in case you weren't hovering long enough.

The mockup really seems to address all the issues.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 05:45:48 PM
The mockup really seems to address all the issues.
If we were discussing Hiccup's first Mock-up (from last week), then I'd agree wholeheartedly.  But I have to offer a dissenting vote for this last one - I don't see the need to move anything around so drastically, especially after all the effort that already went into the "Import/Save/Edit" layout.

As for filters... maybe there should be more voices from those (not us) who actually use them?  This is a forest-for-the-trees thing to me, yes more options are always a good thing, but the search-bar (which incidentally looks much nicer in its current shortened form) by itself solves many evils.

For what it's worth my use case is simple: I tend to delete the presets I know I'll never use, so I only have about 40 in total, 11 of which can be called full (from scratch) user-presets. Since the font issue has plagued me for some time, I started prefixing all my custom user presets with the '_' underscore character so they automatically went to the top of the list by default and I don't ever need to search for them.

Obviously, other people's needs will be different, but considering Hiccup (please take this with humour) by his own admission didn't even know the search-bar existed until a month ago - how much filtering can one man need?   :o

As for fonts - yes, regularising them would be nice - if it were up to me they would all be roughly the same, with just button text being slightly enlarged for clarity, and without doubt the "description" text needs to be larger and preferably not that blue colour... for those who use the "skin" option, it's virtually unreadable on a dark background.

And as ridiculous as it may sound, I will again plead on my knees that the Preset-List text go no smaller, or, indeed, be changed in any way.  It's only in the few days that it's become acceptable (for me).

My two-cents, as they say.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 29, 2023, 06:05:05 PM
If we were discussing Hiccup's first Mock-up (from last week), then I'd agree wholeheartedly.  But I have to offer a dissenting vote for this last one - I don't see the need to move anything around so drastically, especially after all the effort that already went into the "Import/Save/Edit" layout.
Adding the seven text lines with checkboxes takes up more vertical space. Space that isn't really available when leaving the rest of the panel the same.
So I thought reshuffling the larger buttons—what makes this possible—would be a good solution.

And as an added benefit, the groups of buttons are now very nicely separated between the ones that handle presets (at the top), and the ones that preview and save the results (at the bottom).
I myself only see benefits here.
Except for the work this will probably take.

Quote from: Messiaen
but considering Hiccup (please take this with humour) by his own admission didn't even know the search-bar existed until a month ago
That's simply the truth.
And it is one of the reasons I started raising suggestions to improve on the whole interface.
I'm pretty sure I'm not the only one that isn't using all features of the plugin (or even use the plugin at all) because things look confusing and complicated at first (and second) sight.

Quote from: Messiaen
As for filters... maybe there should be more voices from those (not us) who actually use them?  This is a forest-for-the-trees thing to me, yes more options are always a good thing, but the search-bar (which incidentally looks much nicer in its current shortened form) by itself solves many evils.
If we would take my previous mock up (that you and me both like), and tweak it a little bit so to add some of the new current filters, I am guessing 4 filters would be the maximum that can be displayed, considering the available space.

That could look something like this:
(https://i.imgur.com/tLR4ZXA.png)

But that means that 3 of the 7 existing filters would need to go. I myself don't see 3 that could easily be removed.

edit:
Maybe I do.
I'm not sure I understand why there are both customised presets and user presets.
(but that's probably well-explained somewhere in this thread)
So for me, 'customised presets' as a filter could go, and the remaining filter could show them both?
Also, I don't think I will be using 'constrained by playlist' and ''assigned virtual tag function ids' filters.
And also, such presets will probably already get shown when filtering on 'user presets'?

So together that would indeed make three filters that could be removed. (in my personal opinion)
 
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 06:45:23 PM
Don't get me wrong - I appreciate the why of your (new) design, I just don't like it.  I also accept that others may appreciate and love having a serious multitude of filtering options, so they aren't going to go away.  I just think (for the tenth time) that 8 bleeding checkboxes are overwhelming overkill for one option - imagine what MusicBee itself would look like if Steven one day lost his head and decided all filtering will be done similarly!  For a couple of filters, yes, it's great and better than the "old" system, but advanced options are usually best somewhat hidden away (yet accessible when needed), not presented all the time and taking up so much real-estate.

I'll also admit that part of my goals are selfish, where DPI comes into play, one of the side-effects is that windows (frames and all) automatically expand, and since ASR/ALR windows are already rather large and seriously cluttered with controls, there's no hope at all that that flexibility could ever be properly applied in the future without breaking the layout... so 8 checkboxes (my new mantra, apparently  ;) ) is just wacky.  Wacky, I say!  :)

So yeah - I'll go sit quietly in the corner now and hope nobody shrinks anything.  I'm just happy I won't accidentally lose any complex reg-ex edits now that safeguards are in place.  I'm a man of simple needs.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 06:55:34 PM
So together that would indeed make three filters that could be removed. (in my personal opinion)
Options are like nuclear weapons (or a really serious chocolate cake): once invented, they can't be un-invented.  Boroda doesn't strike me as a man who likes to remove things.  And I don't think they should be removed - I think (like a really serious chocolate cake) they should be harnessed, and embraced.  Just slightly hidden away until desired.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 29, 2023, 07:04:32 PM
And I don't think they should be removed
Ok, then I misunderstood you.
Probably because you found my first mockup to be magnificent, and that one had only two filters.

Quote from: Messiaen
imagine what MusicBee itself would look like if Steven one day lost his head and decided all filtering will be done similarly!
No imagination needed:

(https://i.imgur.com/MMNhfTY.png)
;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 29, 2023, 07:48:46 PM
...and that one had only two filters.
That's because at the time there were only two filters!  And then Boroda lost his head and decided filters were like mice - if you see one, you know there's 10 more in the walls just waiting to pounce, and now here we are!  :)

Hagiography and metaphors aside, your first (now mythical) mockup was a triumph of simplicity and design, whilst avoiding the pitfalls of icons and tooltips.  That's one of the things that led me to the dropdown idea (of condensing stuff, not removing stuff - what Buckminster Fuller called Ephemeralisation, the "art of doing more with less").  But I didn't know everybody was so attached to the (admittedly nice) flexibility of combined filters.  Unfortunately I don't have a better solution.  :(
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on January 29, 2023, 08:03:47 PM
Unfortunately I don't have a better solution.  :(
Just in case you missed it, I edited my previous post (reply #2913) and included a mockup that uses 4 presets, and explaining why (I think) that would be enough.
I still see no real issues with my previous 'rigorous' mockup, but perhaps the 4-preset one could be a compromise.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on January 30, 2023, 06:20:17 AM
i've enlarged the font of the preset list
I prefer the original font size.
My OCD kicks in when the bottom of the 'g' in  <Tag 1> gets cut off.

All other changes look OK to me.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2023, 08:03:39 PM
here is what i've currently done. there are both (btw, clickable and ctrl-clickable) icons to quickly show which filters are active, along with dropdown (also, items are ctrl-clickable) with text instead of icons. font sized are changed for both preset list (now preset list font is a bit smaller than earlier) and preset description (now font is a bit larger).

i think i'll stop on ASR UI/UX updating, if nobody strongly objects to the current implementation.

also, i've fixed a number of minor, but very numerous bugs.

still to do: lite redesign of ALR window (to make it look/behave more similar to ASR).

(https://i.imgur.com/yMjh4lR.png)

-------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2023, 08:28:43 PM
I prefer the original font size.
My OCD kicks in when the bottom of the 'g' in  <Tag 1> gets cut off.
yeah, that was bothering me too. hopefully i've found a fix to this (at 1st glance unresolvable using standard .net controls) issue. it's in the last plugin update.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 30, 2023, 08:46:39 PM
The <Ctrl>-clicking combining filters doesn't seem to work.  One filter will work fine, but if I <Ctrl+Click> on another the appropriate icon lights up, but the listview is blank (and no text in combobox).  Clicking on any single filter again restores it as expected.

And just as an odd experiment, <Ctrl+Click> on all filters consecutively again results in a blank listview, but oddly clicking on the "User" filter will randomly enable/disable some other icons, as if it considers such filters are incompatible with each other.  Like I said, this part was just playing around.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2023, 08:48:09 PM
I'm not sure I understand why there are both customised presets and user presets.
(but that's probably well-explained somewhere in this thread)

user preset (no matter how it has been created - from scratch or by copying predefined preset) doesn't relate anymore to any other (e.g. predefined) preset. user has full control over user preset, can completely change (edit) it, and user preset will never be affected by any deletion/(re)installation/updating of predefined presets.

customized preset is always a tiny modification (only allowed by me modification) of predefined preset (and only predefined preset) made by user. it's not a new copy of preset, and it's still predefined preset. user can reset all customizations of predefined preset by clicking "install all" button, and clicking "yes" in the following confirmation dialog.

so, user presets and customized presets are completely different.

Also, I don't think I will be using 'constrained by playlist' and ''assigned virtual tag function ids' filters.
And also, such presets will probably already get shown when filtering on 'user presets'?

no, only changing allowed <tag #> tags and <custom text #> values are considered to be customization.

such preset settings as "constrained by playlist", "assigned virtual tag function ids", etc. are not customizations and are always preserved on any predefined presets update.

p.s. probably i must include in "customization" concept all changed settings except for hotkey and function id assignments.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2023, 09:44:30 PM
The <Ctrl>-clicking combining filters doesn't seem to work.  One filter will work fine, but if I <Ctrl+Click> on another the appropriate icon lights up, but the listview is blank (and no text in combobox).  Clicking on any single filter again restores it as expected.
works fine here. filters are combined using AND operation, not OR. blank combobox field means "mixed filters". i don't know how to display some text if no exact item (actually, if no item) is selected in combobox. 

And just as an odd experiment, <Ctrl+Click> on all filters consecutively again results in a blank listview, but oddly clicking on the "User" filter will randomly enable/disable some other icons, as if it considers such filters are incompatible with each other.  Like I said, this part was just playing around.
"predefined"/"customized" and "user" filters ARE mutually exclusive (because they are combined using AND operation, preset can't be predefined AND user simultaneously).

i'll change tool tips to explain that all checked filter are applied simultaneously (using AND operation).

i only don't know how to phrase this in English in a simple and clear way.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 30, 2023, 10:05:22 PM
filters are combined using AND operation, not OR.
Ah, ok, that explains it - my mistake, I didn't expect that.  I imagine you'll get a lot of confused users by this method, no matter how simplistically you try explaining the difference between an applied logical conjunction vs disjunction.  Sometimes rigorous logic is not a good thing when dealing with... people.  ;)

It's also the opposite of how the previous multi-checkbox filtering worked.  Most people would "expect" a cummulative system (i.e., all filters selected == no filters selected, regardless of logical "conflicts").
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 31, 2023, 02:15:00 PM
Ah, ok, that explains it - my mistake, I didn't expect that.  I imagine you'll get a lot of confused users by this method, no matter how simplistically you try explaining the difference between an applied logical conjunction and disjunction.  Sometimes rigorous logic is not a good thing when dealing with... people.  ;)
yes, it may be hard to explain the difference between conjunction vs disjunction a person with no mathematical background.

It's also the opposite of how the previous multi-checkbox filtering worked.  
no, filters always worked this way.

Most people would "expect" a cummulative system (i.e., all filters selected == no filters selected, regardless of logical "conflicts").
maybe, but cumulative system makes almost no sense for preset filtering (imho).

-------------

i've changed ALR UI/UX to make it more consistent and logical in respect to preset creating, saving new preset, saving (updating) existing preset, and deleting preset. also, it behaves more similar to ASR now.

also, i've changed coloring algorithms for ASR/ALR again.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 31, 2023, 05:35:05 PM
no, filters always worked this way.
Sometimes I wonder about my brain... I just checked the version from last week, and (obviously) you're right.  Pay me no mind; I wasn't testing with my regular collection of presets before, so I didn't have enough of the varying types to see the distinction.  I need a holiday.

i've changed ALR UI/UX to make it more consistent and logical in respect to preset creating, saving new preset, saving (updating) existing preset, and deleting preset. also, it behaves more similar to ASR now.
Much improved.  The only small thing I can see (in ALR) is that checking/unchecking a preset's "Apply on Startup" status doesn't seem to count as a "changed setting" as far as closing the window is concerned.  Not a big deal - almost all of mine only ever need to be run once, so I bind them to hotkeys using the ASR bridge anyway.  However, since now checking an ASR preset's Auto-Apply status seems to result in extra Bells-&-Whistles (I'm assuming to draw extra attention to it?), that's a behavioural mismatch.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 31, 2023, 05:56:04 PM
Oh, and for simplicity, you might shorten the ALR "Calculate ticked presets at startup..." to just say "Apply ticked presets to custom tags on startup" (and roughly the same for the "every 100 changes" option), leaving out the whole "calculate" and "aggregated functions" phrasing.

While the word "aggregated" is technically more accurate to describe what a preset is, it's a rather uncommon word in English, except in mathematical-set theory, and/or geology classes, so it would only serve to confuse people.  Once someone has created a working preset, the rest is reasonably self-explanatory (I would think?).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 31, 2023, 08:28:17 PM
ok, i'll change ALR labels.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 31, 2023, 10:40:16 PM
The only small thing I can see (in ALR) is that checking/unchecking a preset's "Apply on Startup" status doesn't seem to count as a "changed setting" as far as closing the window is concerned.

it's intentional. preset list is blocked (and presets can't be ticked/unticked) if ALR detects any modification until you click "save preset" or "undo changes".

btw. i've renamed the button "discard changes" to "undo changes". the meaning is the same, but i guess that new wording is better.

Oh, and for simplicity, you might shorten the ALR "Calculate ticked presets at startup..." to just say "Apply ticked presets to custom tags on startup" (and roughly the same for the "every 100 changes" option), leaving out the whole "calculate" and "aggregated functions" phrasing.

you are right, my phrasing was too sophisticated and confusing for most users. i've renamed these labels.

---

i've changed ASR filters tool tips to make it more clear that all filters are applied simultaneously, if several filters are checked.

now preset combo box displays the text "(Mixed filters)" instead of empty field, if several filters are checked.

---

i guess that all necessary UI/UX updates are done now. still waiting @phred for suggestions on updated readme. then i'll change readme files in plugin .zip, 1st post on this topic, and add-on page.

---

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 01, 2023, 02:12:32 AM
i guess that all necessary UI/UX updates are done now. still waiting @phred for suggestions on updated readme. then i'll change readme files in plugin .zip, 1st post on this topic, and add-on page.
@boroda- do you have the last revision I did? If so, can you PM it to me? Or post it here, if you wish. If you don't have it, can you get me the last one -you- did?

I'll have some time towards the end of the week to look it over, ask you questions, and get it done.

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on February 01, 2023, 06:59:41 AM
preset list is blocked (and presets can't be ticked/unticked) if ALR detects any modification until you click "save preset" or "undo changes".
Unless you tick/untick ALR presets before you do any edits to them.  Just open the window, tick one or more (it takes two clicks), then close the window.  The "changes" are saved automatically, but there's no indication that a change happened.  This is not especially important, but I point it out as an inconsistency.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 01, 2023, 02:54:47 PM
preset list is blocked (and presets can't be ticked/unticked) if ALR detects any modification until you click "save preset" or "undo changes".
Unless you tick/untick ALR presets before you do any edits to them.  Just open the window, tick one or more (it takes two clicks), then close the window.  The "changes" are saved automatically, but there's no indication that a change happened.  This is not especially important, but I point it out as an inconsistency.
you are right. at the moment, there is only one variable to store "some modifications are made" state, which blocks the preset list. i simply could add another variable "preset checked states are changed".
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 01, 2023, 03:38:28 PM
i guess that all necessary UI/UX updates are done now. still waiting @phred for suggestions on updated readme. then i'll change readme files in plugin .zip, 1st post on this topic, and add-on page.
@boroda- do you have the last revision I did? If so, can you PM it to me? Or post it here, if you wish. If you don't have it, can you get me the last one -you- did?

I'll have some time towards the end of the week to look it over, ask you questions, and get it done.

Thanks.
i think, no. the latest readme version i have is very old. here what i have now:

https://www.mediafire.com/file/xw1y91qr66id89r/README_FIRST%2521.txt/file

but ASR behavior have been changed since the time this readme version have been written. here is the current ASR behavior, which is different from described in readme:

----

process of preset installing is changed: "install new" will always silently update all (customized or not, but only if there are new versions of installed presets, or new presets have been added to plugin zip since presets have been installed/updated last time) predefined presets, always preserving all customizations. 'install all' will ask the user (ask, only if some presets are customized) if he wants to reinstall all unchanged and update all modified by plugin developer presets resetting all customizations, or preserving all customizations. 'install all' will always install presets not existing among working presets (i.e. new or previously deleted by user presets), and always reinstall/update all not customized presets.

reinstallation of unchanged presets (only when performing 'install all' command) may be useful if some working predefined presets (not presets located in "plugins\asr presets" folder - "local preset repository" - i'm, actually, not sure how these presets must be named) are somehow damaged (or if user wants to reset all customizations).

----

this warning must be inserted to readme:

Be careful to not ACCIDENTALLY tick some "Advanced Search & Replace" preset(s) for AUTOMATIC APPLYING!  there will be a reddish (color near to red) warning message at the top of ASR window, if you have any ASR presets ticked for auto-applying.

----

i think that the following explanation (but very shortened and simplified) must be mentioned in readme:

user preset (no matter how it has been created - from scratch or by copying predefined preset) doesn't relate anymore to any other (e.g. predefined) preset. user has full control over user preset, can completely change (edit) it, and user preset will never be affected by any deletion/(re)installation/updating of predefined presets.

customized preset is always a tiny modification (only allowed by me modification) of predefined preset (and only predefined preset) made by user. it's not a new copy of preset, and it's still predefined preset. user can reset all customizations of all predefined presets by clicking "install all" button, and clicking "yes" in the following confirmation dialog.

----

all the text i've written above is just a draft. it's not suitable for final readme.

so, could you (and maybe @hiccup and @Messiaen) make the whole readme as much simple and clear for not advanced users as it possible?

and, of course, the big problem personally for me is that the english readme text must "sound" naturally for natives (without using awkward and uncommon words/phrases).
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 01, 2023, 03:55:27 PM
Thanks boroda.

I've got what I need to get started. I should have something for your review Friday or Saturday, if not before.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 08, 2023, 10:41:35 PM
i've merged ALR and LR commands into one LR command. united LR command code is almost written from scratch. new LR code must be much more efficient and fast. new LR window looks/behaves more similar to ASR window.

$ALR(<URL>,function_id) virtual tag function is renamed to $LR(<URL>,function_id).

@hiccup, please update your cheatsheet.

BE CAREFUL! YOU WILL LOSE ALL ALR/LR PRESETS ON PLUGIN UPDATE AND MUST RECREATE THEM.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 08, 2023, 11:26:51 PM
i've added a download link to the latest plugin .zip at the top of the 1st post of this topic, and at the top of the add-on page.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 09, 2023, 05:41:04 AM
forgot to mention: new LR command allows assigning hotkeys to LR presets. hotkey can apply a preset to the entire library or to selected tracks only.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on February 09, 2023, 12:20:42 PM
BE CAREFUL! YOU WILL LOSE ALL ALR/LR PRESETS ON PLUGIN UPDATE AND MUST RECREATE THEM.
Thanks for that. <Heavy, smothering, doom-laden sarcasm>

I don't seem to be able to assign $LR ID's to custom presets.  The text field accepts input, I click the "Assign" button next to it, and Save the preset - except when I reopen the ALR window and click on the preset to edit it, the ID text-field is empty, so it doesn't stick.  And obviously trying to execute the $LR function results in the curiously helpful "Incorrect $LR() ID!" being assigned to the custom tag instead.

And I'm sure we discussed this before, but why do those Assign/Unassign buttons even exist?  Logic suggests that if there's text in the field when the preset is saved, it should be considered assigned, and likewise, if the field is blank, then the ID is considered unassigned when saved.  (Also, if you insist on keeping those buttons, their current tooltips still include that deprecated "Aggregated Function" text.)

<Superficial comments>
Why are the default preset names in all capital letters?  Weird.  Also, since the listview only really allows 6 presets to be displayed (before needing to scroll down), it's awkward that the default ones take up 4 of those slots - I can't even override the sort order (like I can with ASR presets) by prefixing a "_" to my custom preset names.
</Superficial comments>
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 09, 2023, 08:43:15 PM
BE CAREFUL! YOU WILL LOSE ALL ALR/LR PRESETS ON PLUGIN UPDATE AND MUST RECREATE THEM.
Thanks for that. <Heavy, smothering, doom-laden sarcasm>

hmm, i didn't think that somebody has more than a couple of custom presets, so haven't implemented preset migration mechanism. sorry.

I don't seem to be able to assign $LR ID's to custom presets.  The text field accepts input, I click the "Assign" button next to it, and Save the preset - except when I reopen the ALR window and click on the preset to edit it, the ID text-field is empty, so it doesn't stick.  And obviously trying to execute the $LR function results in the curiously helpful "Incorrect $LR() ID!" being assigned to the custom tag instead.

there was a blunder related to saved function id loading to LR GUI. i've fixed it. but ids are saved as they should, and $LR function is working fine on my machine. though i'd uploaded the plugin several times during last night, maybe i've already fixed this bug. in any case, download the latest version.

And I'm sure we discussed this before, but why do those Assign/Unassign buttons even exist?  Logic suggests that if there's text in the field when the preset is saved, it should be considered assigned, and likewise, if the field is blank, then the ID is considered unassigned when saved.  (Also, if you insist on keeping those buttons, their current tooltips still include that deprecated "Aggregated Function" text.)

"clear id" button was always in place. i had a good reason for adding "assign id" button during ALR/LR merging, but at the moment i agree that it's residual. i'll remove it.

Why are the default preset names in all capital letters?  Weird.  Also, since the listview only really allows 6 presets to be displayed (before needing to scroll down), it's awkward that the default ones take up 4 of those slots - I can't even override the sort order (like I can with ASR presets) by prefixing a "_" to my custom preset names.

i'll enlarge vertical size of preset list.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on February 09, 2023, 09:51:51 PM
i didn't think that somebody has more than a couple of custom presets, so haven't implemented preset migration mechanism.
Actually I was just joking - while I have more than "a couple" of presets, rebuilding them again gave me a chance to fix a couple of grouping inaccuracies, so all good.

i'd uploaded the plugin several times during last night, maybe i've already fixed this bug.
Yep, that was it - seems to work now (odd, both versions were 5.7.8440).  Isn't it some kind of programmer's sin to upload changes without modifying the build number?   :)

i'll enlarge vertical size of preset list.
Maybe not enlarge it so much, just allow custom presets to sit "above" the default ones?  I would think a user would be more interested in revisiting the ones they make themselves rather than the default/example presets (except at first, of course).

Speaking of lists, knowing how much people seem to be upset by little things, I might point out that the descenders are cut-off on the font used in the tag-selection list.

(https://i.imgur.com/yfNCkFG.jpg)

Lastly, as a suggestion, when creating a new preset, the "Save field to tag..." always defaults to <Date Created> for some reason.  Wouldn't it be better if it defaulted to <Null> on the odd chance that someone creates a preset but forgets to assign this part properly then executes it?  At least <Null> won't change anything accidentally.

I curiously seem to miss the old "Update/Save Preset" button, since making a preset is often a multi-stage thing, it was nice to be able to "save it" without actually having to "Save & Close" at the same time.  I know that it doesn't really matter (it would all be saved at the end anyway), but I was so used to clicking that button that it's weird it's gone.  Then again, I'm funny that way, so don't think too hard on it.  ;)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 10, 2023, 11:07:24 AM
...(odd, both versions were 5.7.8440).  Isn't it some kind of programmer's sin to upload changes without modifying the build number?   :)
last 4 digits are the auto-generated build number. it's the number of days between build date and 01/01/2000. i've added to plugin version revision number (several digits after build number), it's also auto-generated and somehow relates to build time (i don't know what they exactly mean). also, the plugin version is now displayed at the bottom of plugin menu.

i'll enlarge vertical size of preset list.

ASR, MSR and LR windows are now split to resizable top and bottom parts. unfortunately, i've failed to make splitter bar visible, but cursor will be changed over splitter.

Speaking of lists, knowing how much people seem to be upset by little things, I might point out that the descenders are cut-off on the font used in the tag-selection list.

(https://i.imgur.com/yfNCkFG.jpg)
i've increased vertical spacing for this list.

Lastly, as a suggestion, when creating a new preset, the "Save field to tag..." always defaults to <Date Created> for some reason.  Wouldn't it be better if it defaulted to <Null> on the odd chance that someone creates a preset but forgets to assign this part properly then executes it?  At least <Null> won't change anything accidentally.
it's just the 1st item in the destination tag list selected, this tag list is sorted alphabetically. earlier 1st item was <null>, later i've added <date created> pseudo-tag, which became the 1st. not a problem, i've set default item explicitly to <null>.

I curiously seem to miss the old "Update/Save Preset" button, since making a preset is often a multi-stage thing, it was nice to be able to "save it" without actually having to "Save & Close" at the same time.  I know that it doesn't really matter (it would all be saved at the end anyway), but I was so used to clicking that button that it's weird it's gone.  Then again, I'm funny that way, so don't think too hard on it.  ;)

previously, clicking "save preset" button only "saved" preset to ram, you anyway had to click "save all & close" to really save preset (all modified presets). now just click "copy preset" and continue editing the copy.

--------------------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 11, 2023, 07:21:12 AM
$ALR(<URL>,function_id) virtual tag function is renamed to $LR(<URL>,function_id).
At this very moment I don't recall what these functions do, but there was &ALR and $ASR.
Just from a 'reading' standpoint they look nice together ;-)
And users may have gotten used to them.
Are you sure it is a good idea to rename $ALR to $LR, and keep $ASR as it is?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 11, 2023, 08:52:28 AM
yes  8) because $ASR stands for Advanced Search & Replace and $ALR for Auto Library Reports, which doesn't exist anymore (i've merged ALR and LR commands into united LR one).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 11, 2023, 09:01:28 AM
(i've merged ALR and LR commands into united LR one).
I changed it.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 11, 2023, 10:21:48 AM
thanks.

you forgot to change 2nd post (which contains function explanations/examples) on cheatseet topic.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 11, 2023, 10:59:30 AM
you forgot to change 2nd post (which contains function explanations/examples) on cheatseet topic.
fixed
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 11, 2023, 04:11:21 PM
i'll enlarge vertical size of preset list.
Maybe not enlarge it so much, just allow custom presets to sit "above" the default ones?  I would think a user would be more interested in revisiting the ones they make themselves rather than the default/example presets (except at first, of course).

copy your existing user presets, they will be placed at top of preset list, and delete original presets (at the end of list).

copies of new user presets will be inserted right below the original presets, copies of predefined presets will be placed at the top of the preset list.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on February 11, 2023, 05:57:44 PM
copy your existing user presets, they will be placed at top of preset list, and delete original presets (at the end of list).

That was surprisingly painless - thanks for that, and thank you for all your recent work on this, your baby is growing up nicely.  ;)

Messing with the build number seems to have altered the spacing a bit at the bottom of the settings menu - it's a little out of whack.

(https://i.imgur.com/v81eHD5.jpg)

Quote
...it's the number of days between build date and 01/01/2000

Off-topic: And sure enough, there have been 8442 days since.  Is this something Visual Studio does?  I love weird metrics... my personal favourite is how Windows API derives timestamps - filetimes in Windows are actually stored as the number of 100-nano-second intervals since January 1st in the year 1601. Yes, the 17th-century, as in 400 years ago - older than Bach!  For the curious, 100-nano-seconds is basically 1/10,000th of a millisecond - so the accumulated (dare I say 'aggregated'?  ;) ) number of them in the last 4 centuries amounts to - well, a heck of a lot; we can be glad that number's not used as a build metric.  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 11, 2023, 06:31:01 PM
That was surprisingly painless - thanks for that, and thank you for all your recent work on this, your baby is growing up nicely.  ;)

i'd forgotten to change "new preset" action, it should have moved new preset to the top of the list instead of bottom. redownload plugin.

Messing with the build number seems to have altered the spacing a bit at the bottom of the settings menu - it's a little out of whack.

(https://i.imgur.com/v81eHD5.jpg)

damn, haven't checked english settings window. i'll fix it, but now plugin version is also shown in at the bottom of plugin menu.

Off-topic: And sure enough, there have been 8442 days since.  Is this something Visual Studio does?  

yes, of course, i wouldn't calculate this manually  ;D actually i can set build number manually to any 32-bit int, but it's too tedious to manually increment this number on every build.

I love weird metrics... my personal favourite is how Windows API derives timestamps - filetimes in Windows are actually stored as the number of 100-nano-second intervals since January 1st in the year 1601. Yes, the 17th-century, as in 400 years ago - older than Bach!  For the curious, 100-nano-seconds is basically 1/10,000th of a millisecond - so the accumulated (dare I say 'aggregated'?  ;) ) number of them in the last 4 centuries amounts to - well, a heck of a lot; we can be glad that number's not used as a build metric.  :)

 yeah, it's a bit odd system ;) but it's not so bad to quickly (and approximately) compare 2 different builds. <build number difference>/7 = # of weeks, <build number difference>/30 = # of months, etc  8)

personally, i would prefer is if the build number was just the 6-digit YYMMDD date, if expressed as decimal number.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on February 11, 2023, 07:01:24 PM
i've fixed these 2 visual glitches of setting window:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 13, 2023, 02:48:03 PM
@boroda-

Suggestion for the ASR warning regarding presets that are ticked for auto-applying...
- Instead of a "reddish" color for the warning, make it red. Or more red. Or redder. I barely notice the change from black to the warning color.

- Change the wording of the warning to "PRESETS ARE TICKED AND WILL BE AUTOMATICALLY (or AUTO-) APPLIED:" (If enough space use "AUTOMATICALLY APPLIED:" otherwise use "AUTO-APPLIED:"

- if at all possible, only change the sentence with the warning to red and not the instructions preceding the warning.

I will be sending you a PM with my updates to the readme shortly.
Title: Re: Additional Tagging & Reporting Tools
Post by: nsd3 on February 13, 2023, 05:37:09 PM
It's not working at all for me.  The instructions work fine until I get to this part:
Open MusicBee. From the menubar > Tools > Additional Tagging & Reporting Tools > Advanced Search & Replace > Click "Install All"
I get an unexpected error with the following info (note I've placed the error messages right at the bottom of this reply).  If I use the import button instead of the Install button, I can include the presets, but they don't work.  I can't even save and close.  Any help appreciated.



MusicBee v3.4.8033.18564D  (Win10.0), 13 Feb 2023 17:28:

System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)
   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
   at System.IO.Directory.CreateDirectory(String path)
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.install(Boolean installAll)
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.buttonInstallAll_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 & Reporting Tools
Post by: hiccup on February 13, 2023, 05:44:57 PM
It's not working at all for me.
You are using an older version of MusicBee.
Check the first topic in the first board topic to update to 3.5

I'm not saying it will definitely solve your problem, but both MusicBee and the AT&RT plugin have been under a lot of development since.
So make sure you are using both the latest MB version, and the latest AT&RT version. Either one being an older version can cause issues.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 13, 2023, 06:21:37 PM
There was a new AT&RT version released within the  past few days, so start at the end of the plugin's thread and work backwards. It will be on the last or next to last page.

As for MB version, the recent development of the plugin (starting a couple of months ago) requires the use of 3.5.x, as hiccup said.
Title: Re: Additional Tagging & Reporting Tools
Post by: nsd3 on February 14, 2023, 12:12:54 PM
I thought V3.5 was still in beta, hence I've not updated.  If 3.5 is a prerequisite, I'll just wait for the official release.  My thanks to you all that bothered to reply, it's appreciated.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on February 22, 2023, 05:54:43 PM
It's been awhile since I used them, but the two predefined presets "Replace repeating spaces" and "Replace underlines with spaces" both seem to be missing the required actual space-character (for replacement) in their definitions - resulting in either all spaces being removed, or all underlines being simply stripped (not replaced).  I tested with a fresh install of the most recent version's ASR Presets folder.

I know these presets used to work properly, so something might have broken when you revamped the preset-installing procedure recently?  The oldest xml's I have from backup are only from mid January (they're bad too), so the definitions might have been corrupted for awhile.

Strange.

Edit:  Actually, this is odd - if I "fix" the preset by copying it and editing back in the necessary space character, the preset works, and if saved will continue to work unless MB itself is restarted, at which point the preset fails because the "fixed" space character is gone from the definition again!
Title: Re: Additional Tagging & Reporting Tools
Post by: badchild on March 06, 2023, 01:07:16 PM
Hey Man!
Been using Musicbee for years and love it. My library is big enough 53 000 tracks, full albums only all in Flac. I keep track of it on a spreadsheet and have noticed there are discrepancies in the library reports where the results don't match up with reality. Upon further inspection, I've found that the report skips Album titles that are the same....example "Live" or "Greatest Hits".

It's not really important unless you're afflicted with asperger's.....:)

As FZ said....."Music (bee) is the best !
Title: Re: Additional Tagging & Reporting Tools
Post by: Babydoll32 on April 07, 2023, 06:37:01 PM
Hi,
since yesterday I got a little problem with additional tagging tools. I have a template which copied some tags like artist, genre i.e. and also rating tag.
It worked very well till yesterday. All ratings copied fine, but rating tag. I can do what I want, but it makes always a 3-star rating. Has anyone a solution?

Best regards
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 02, 2023, 08:25:52 PM
It's been awhile since I used them, but the two predefined presets "Replace repeating spaces" and "Replace underlines with spaces" both seem to be missing the required actual space-character (for replacement) in their definitions - resulting in either all spaces being removed, or all underlines being simply stripped (not replaced).  I tested with a fresh install of the most recent version's ASR Presets folder.

I know these presets used to work properly, so something might have broken when you revamped the preset-installing procedure recently?  The oldest xml's I have from backup are only from mid January (they're bad too), so the definitions might have been corrupted for awhile.

Strange.

Edit:  Actually, this is odd - if I "fix" the preset by copying it and editing back in the necessary space character, the preset works, and if saved will continue to work unless MB itself is restarted, at which point the preset fails because the "fixed" space character is gone from the definition again!
sorry, don't know how this could happen. i've fixed, will upload fixed version later today.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 02, 2023, 08:29:15 PM
Hey Man!
Been using Musicbee for years and love it. My library is big enough 53 000 tracks, full albums only all in Flac. I keep track of it on a spreadsheet and have noticed there are discrepancies in the library reports where the results don't match up with reality. Upon further inspection, I've found that the report skips Album titles that are the same....example "Live" or "Greatest Hits".

It's not really important unless you're afflicted with asperger's.....:)

As FZ said....."Music (bee) is the best !
never use just album tag in LR, mb itself treats "album" as a combination of album/album artist tags. do the same in LR. define 2 groupings: album/album artist (displayed!) instead of just album.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 02, 2023, 08:31:58 PM
Hi,
since yesterday I got a little problem with additional tagging tools. I have a template which copied some tags like artist, genre i.e. and also rating tag.
It worked very well till yesterday. All ratings copied fine, but rating tag. I can do what I want, but it makes always a 3-star rating. Has anyone a solution?

Best regards
send me 1 of problem tracks (if ratings are stored in tracks), and you "copy" preset (select preset and click "export..." button).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 02, 2023, 10:26:54 PM
It's been awhile since I used them, but the two predefined presets "Replace repeating spaces" and "Replace underlines with spaces" both seem to be missing the required actual space-character (for replacement) in their definitions - resulting in either all spaces being removed, or all underlines being simply stripped (not replaced).  I tested with a fresh install of the most recent version's ASR Presets folder.

I know these presets used to work properly, so something might have broken when you revamped the preset-installing procedure recently?  The oldest xml's I have from backup are only from mid January (they're bad too), so the definitions might have been corrupted for awhile.

Strange.

Edit:  Actually, this is odd - if I "fix" the preset by copying it and editing back in the necessary space character, the preset works, and if saved will continue to work unless MB itself is restarted, at which point the preset fails because the "fixed" space character is gone from the definition again!
i've fixed it:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on May 02, 2023, 11:03:44 PM
i've fixed it
Umm... no, not so much - the problem remains (I tested on a fully replaced set of presets, just in case, and the plugin version seems to remain unchanged [5.7]).  There is something which is still removing the ' ' character from the actual "Replace with" field, like you're cleaning excess whitespace during installation or something.

The only way I've found to "fix it" properly is to not use a typed <space> character at all and just use "\@char[[0020]]" in the field instead.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 03, 2023, 01:32:02 AM
you are right. the problem is "whitespace cleanup" for xml files. i see the same when i reimport presets back. this xml behavior is adjustable, but i better stick with your solution.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 03, 2023, 01:48:57 AM
i've fixed some LR bugs. also, LR export folder is remembered now. download link is the same.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on May 03, 2023, 07:20:37 AM
Thanks, all good now.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 03, 2023, 01:01:33 PM
fixed behavior of "#" grouping for LR. may be useful only for generating reports for playlists, but not for entire library:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Ploki on May 04, 2023, 08:44:20 AM
Request for new feature or extend current one

In current function repunct it only translate some special characters to some of this
Code
<< " [ ((
Full definition is in AutoLibraryReports.cs rows starts with 827

It is possible to do something similar with letters? For example I want to translate artists like this:
Céline Dion -> Celine Dion (é -> e)
Christina Stürmer -> Christina Sturmer (ü -> u)
Horkýže Slíže -> Horkyze Slize (ý -> y, ž -> z, í -> i)

Maybe this could help with specifying characters
https://stackoverflow.com/questions/18123501/replacing-accented-characters-with-plain-ascii-ones
https://stackoverflow.com/questions/286921/efficiently-replace-all-accented-characters-in-a-string

i've created new asr preset "Transliterate Unicode characters of <Tag 1> to ASCII characters". 'import new' asr presets after updating plugin. you need to install this plugin (https://getmusicbee.com/forum/index.php?topic=37276.0) to use new preset.
Works great, but with one error - if there is comma in tag, for example:
Money, Money, Money   ->   $TransliterateToAscii(Money, Money, Money)
No Woman, No Cry   ->   $TransliterateToAscii(No Woman, No Cry)
Don't Worry, Be Happy   ->   $TransliterateToAscii(Don't Worry, Be Happy)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 04, 2023, 10:51:43 AM
now LR remembers last exported report file name per preset:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 04, 2023, 12:00:27 PM
Works great, but with one error - if there is comma in tag, for example:
Money, Money, Money   ->   $TransliterateToAscii(Money, Money, Money)
No Woman, No Cry   ->   $TransliterateToAscii(No Woman, No Cry)
Don't Worry, Be Happy   ->   $TransliterateToAscii(Don't Worry, Be Happy)

thank you that you noticed this important issue. actually, it was much more general and concerned much more presets than just this one. it's fixed:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

p.s. no need to update presets, just update plugin.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 07, 2023, 10:43:57 AM
Minor LR bug fixes:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 10, 2023, 09:42:56 PM
Minor LR bug fixes, e.g. now max/min aggregated functions now can be used for string tags (earlier they correctly worked for numeric/date tags only):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on May 12, 2023, 01:01:08 AM
Hmm... unfortunately I seem to have lost my older versions of the plugin (for testing), so I only have the newest one, but it seems one of the most recent updates broke the "\@eval[[ ... ]]" function.  Any preset which uses something like:

Code
\@eval[[$If(<Genre>=Classical,1,0)]]

...in the replace-with field results in "Invalid naming template -- $If(<Genre>=Classical,1,0)" written to the target tag... the expression itself is not evaluated, whereas it used to work as expected.

Edit: Curiously, the preset "Example: Write result of virtual expression" does seem to work (the default $Len function), however anything using $IsNull or $If seems to fail as above. (Whether used in relation to that preset or in an original one.)

Edit 2: Fails for any function/expression which contains/requires a comma (so anything with more than 1 parameter) - functions which don't (like $Len or $Upper) are ok.  Probably related to the recent $Transliterate fix.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 14, 2023, 10:38:16 PM
Probably related to the recent $Transliterate fix.

yes, you are right. i've fixed this, but now you must use TWO commas to separate virtual tag function parameters, e.g. \@eval[[$IsNull("$1",,NULL,,$1)]].

reimport new (or all) presets.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on May 15, 2023, 01:14:04 AM
i've fixed another \@eval[[]] bug related to tag values containing quotes. Now, if you want to pass a string to a virtual tag function as is, you must put it in DOUBLE quotes, e.g.

\@eval[[$IsNull(""$1"",,NULL,,$1)]]

instead of

\@eval[[$IsNull("$1",,NULL,,$1)]].



reimport ASR presets.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on May 15, 2023, 07:44:38 AM
Thanks.  The syntax may be getting stranger, but at least it's consistently stranger!  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on June 02, 2023, 01:22:21 PM
Oh no, this latest update seems to have broken a custom preset for me.

The original, which was working before had this:

Search for
^(.*?)(\s*\[Explicit\])?$
replace with
$1

Step 2
Search for
^(.*)
replace with
\@eval[[$If($TagContainsAnyString(<URL>,Lyrics,"\@1"), [Explicit],)]]


I've tried a combination of things but I still can't get it to work.

For, if I change it to this:
\@eval[[$If($TagContainsAnyString(<URL>,,Lyrics,,""\@1""), [Explicit],)]]

It just adds $If($TagContainsAnyString(<URL>,Lyrics,"bad|words"), [Explicit],) to the existing title.

I'm confused!

EDIT

I think I've done it.

I've just replaced all " with "" and doubled up all the commas and it now seems to work. I'll keep testing.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 02, 2023, 03:27:00 PM
could you be more specific? you wrote:

I think I've done it.

I've just replaced all " with "" and doubled up all the commas and it now seems to work. I'll keep testing.

but you have already replaced " by "" in this example (which didn't work for you):

For, if I change it to this:
\@eval[[$If($TagContainsAnyString(<URL>,,Lyrics,,""\@1""), [Explicit],)]]

It just adds $If($TagContainsAnyString(<URL>,Lyrics,"bad|words"), [Explicit],) to the existing title.

I'm confused!
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 02, 2023, 03:58:50 PM
I think the end of his eval had two comma's which were overlooked for doubling... ""\@1""), [Explicit],)]]

Which is understandable as if you copy his full eval into the preset editor text control, those last few characters would be hidden unless you intentionally scroll through to the end.  You probably never envisioned anyone using excessively long replacement strings when you originally made the box.  I contemplated once about requesting you to make the preset editor WS_THICKFRAME compatible, but considering there's a few dozen controls in there to link, it hardly seemed a practical amount of effort for something so rarely needed.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 03, 2023, 01:55:47 AM
Plugin update:

1. numerous typos are fixed in ASR presets. reimport them.
2. several UI/UX bug fixes/adjustments.
3. i've made most input fields auto-scalable in the main ASR window and in ASR preset editor window (which is now resizable and can be maximized like most other plugin windows).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 03, 2023, 06:23:49 AM
I knew you were going to take that too seriously - it really was just a comment and not a real request.  :)

I think this is just a DPI issue, but the new vertical scale is slightly off (the bottom OK/Cancel buttons are cut and the lower "replace" field for all 5 steps are also slightly sheared):

(https://i.imgur.com/YwaCdmx.png)

But other than that, the horizontal scaling works as expected.
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on June 03, 2023, 10:12:05 AM
Apologies for not being clear.

In my first attempt I doubled up the " and the , but only within the if statement. I ended up doubling up anywhere there was a " and a , and that seemed to fix it.

could you be more specific? you wrote:

I think I've done it.

I've just replaced all " with "" and doubled up all the commas and it now seems to work. I'll keep testing.

but you have already replaced " by "" in this example (which didn't work for you):

For, if I change it to this:
\@eval[[$If($TagContainsAnyString(<URL>,,Lyrics,,""\@1""), [Explicit],)]]

It just adds $If($TagContainsAnyString(<URL>,Lyrics,"bad|words"), [Explicit],) to the existing title.

I'm confused!
Title: Re: Additional Tagging & Reporting Tools
Post by: bkev on June 03, 2023, 10:12:50 AM
I think the end of his eval had two comma's which were overlooked for doubling... ""\@1""), [Explicit],)]]

Which is understandable as if you copy his full eval into the preset editor text control, those last few characters would be hidden unless you intentionally scroll through to the end.  You probably never envisioned anyone using excessively long replacement strings when you originally made the box.  I contemplated once about requesting you to make the preset editor WS_THICKFRAME compatible, but considering there's a few dozen controls in there to link, it hardly seemed a practical amount of effort for something so rarely needed.

Yeah that was it. I missed off some of the end commas and once I doubled those up it worked again.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 03, 2023, 04:20:29 PM
Plugin update:
Thanks for the update. It is strictly a coincidence that the plug version is 5.7.8554 and the latest MB version is 3.5.8554?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 03, 2023, 04:33:09 PM
@boroda...

I just updated MB and AT&RT and am finding that when launching AS&R the 'action' buttons are all grayed-out.
The new DLL was placed in the plugins directory and overwrote the previous DLL. The presents were placed in MusicBee\AppData\ASR Presets. Obviously this makes it impossible to import the new presets per the update's instructions.
(http://i.imgur.com/uC3Lurul.jpg) (https://i.imgur.com/uC3Luru.jpg)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 03, 2023, 06:13:18 PM
phred, it's a visual glitch with your color scheme. actually, export/edit buttons are grayed-out on your screenshot, which is correct.

are you using "use skin colors" plugin option?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 03, 2023, 06:16:26 PM
I knew you were going to take that too seriously - it really was just a comment and not a real request.  :)

I think this is just a DPI issue, but the new vertical scale is slightly off (the bottom OK/Cancel buttons are cut and the lower "replace" field for all 5 steps are also slightly sheared):

(https://i.imgur.com/YwaCdmx.png)

But other than that, the horizontal scaling works as expected.

what dpi scaling are you using? all is fine for me at 100% and 125%.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 03, 2023, 07:13:28 PM
Messiaen, i can't reproduce this visual glitch (neither at 100% scaling nor at 125%), but i've tried to fix it. could you check if it's fixed now?

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 03, 2023, 07:40:28 PM
what dpi scaling are you using? all is fine for me at 100% and 125%.
I use 125% - all I can say is that previous versions rendered fine.  I can live with the slight cutoffs on the "replace" text boxes, but the main OK/Cancel buttons are rather important.  I have done all the usual tricks: restart MB, reinstall plugin, disable theme colours, restart system, etc., etc., but it remains the same.  The inconsistencies even remain when switching down to 100% DPI.  I should mention that this is a Win7 system, but again, all other versions rendered more-or-less fine.

Quote from: boroda
...but i've tried to fix it. could you check if it's fixed now?
Well, now the OK/Cancel buttons are only 50% cut-off, whereas before they were almost 80% missing, so they are "useable" at least.  Curiously the "replace" lines remain exactly the same.  I do understand the "if you can't reproduce it you can't fix it" dictum, so I can live with it and just suffer in my stubborn, and ever-shrinking, Win7 world. ;)

(https://i.imgur.com/tdterD6.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 03, 2023, 07:45:34 PM
phred, it's a visual glitch with your color scheme. actually, export/edit buttons are grayed-out on your screenshot, which is correct.
Okay - I see that the "white" buttons can be clicked.

Quote
are you using "use skin colors" plugin option?
No, but I am now. I assume this was due to your change making the window and fields scalable, yes?

Additionally, I've always had my presets in MusidBee\AppData\ASR Presets. Now when I try to import them, an error is thrown "Could not find a part of the path \MusicBee\Plugins\ASR Presets. I moved the to the "new" path and got them imported. But why all of a sudden did the path change?

And lastly, prior to your major rewrite of the plugin, the file names of the presets looked similar to "!{30a13189-7eb4-4f3b-9b42-c1af79a22555}.asr-preset.xml". After the rewrite, and importing the presets, the "original" file names were renamed to something more helpful like "Multiple search & replace.asr-preset.xml". After my current import all, both sets of presets are in the directory? So instead of have 111 presets, I have 222. Again, is this something I did incorrectly? How do I "convert" the original file name to the more understandable file name?

For clarification, I always update this plugin but opening the zip file and dragging the various components to the required directory. This has always worked prior to this update. Could this be the reason for all these issues I'm seeing?

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 03, 2023, 07:56:59 PM
@phred,

For what it's worth, I always update by taking the ASR Presets folder (with the UUID-style names) directly from the ZIP file and placing it into the Plugins folder alongside the DLL itself.  Using the plugin's "install new" button will automatically transfer the updated presets (and conveniently change their names at the same time) into the appdata folder.  This method has never failed yet.  Essentially, there's no reason to ever touch the appdata ASR folder, let it manage itself.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 03, 2023, 08:12:15 PM
Thanks Messiaen. I've just done as you suggested with the most recent plugin update and it behaves as you said. The question becomes, with two presets directories (\plugins\ASR Presets and \AppData\Presets) is there any reason to keep the directory that's under plugins? Especially seeing that it would be recreated when unzipping the next update.

Thanks again.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 03, 2023, 08:21:10 PM
The question becomes, with two presets directories (\plugins\ASR Presets and \AppData\Presets) is there any reason to keep the directory that's under plugins?
Well, if you (like me) go mad sometimes and delete a bunch of unused presets (removing clutter makes finding the ones I use regularly much easier), the Plugins\ASR Presets folder still retains the original versions so they can be restored quickly without having to reinstall the plugin again.  If, on the other hand, you never delete superfluous presets, then I guess you don't need to keep the originals.

It's distantly related to the Chicken-And-The-Egg School of Philosophy.  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 03, 2023, 08:49:27 PM
It's distantly related to the Chicken-And-The-Egg School of Philosophy.  :)
Isn't everything?  :-)

I don't know if boroda is willing to add another filter option and icon, but adding an option to save "favorites" might be a nice addition. This would make it easier to find often used presets. Yes, the search field helps, but bookmarking a favorite would be really nice.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 04, 2023, 01:45:43 PM
No, but I am now. I assume this was due to your change making the window and fields scalable, yes?

Additionally, I've always had my presets in MusidBee\AppData\ASR Presets. Now when I try to import them, an error is thrown "Could not find a part of the path \MusicBee\Plugins\ASR Presets. I moved the to the "new" path and got them imported. But why all of a sudden did the path change?

And lastly, prior to your major rewrite of the plugin, the file names of the presets looked similar to "!{30a13189-7eb4-4f3b-9b42-c1af79a22555}.asr-preset.xml". After the rewrite, and importing the presets, the "original" file names were renamed to something more helpful like "Multiple search & replace.asr-preset.xml". After my current import all, both sets of presets are in the directory? So instead of have 111 presets, I have 222. Again, is this something I did incorrectly? How do I "convert" the original file name to the more understandable file name?

all this is strange because i've been changing UI/UX only during last month. i'll try to check this, but don't promise any solution.

The question becomes, with two presets directories (\plugins\ASR Presets and \AppData\Presets) is there any reason to keep the directory that's under plugins? Especially seeing that it would be recreated when unzipping the next update.

initially, "plugins\asr presets" was required because instructions for manual presets installation to "<mb app data>\asr presets" folder (in case of installer mb version) would be too sophisticated for many users, and rather simple instructions to install presets (alongside with plugin itself) to "program files\musicbee\plugins(\asr presets)" folder led to presets stored in windows-protected folder.

now (and already for a while), mb has "add plugin" button for automatic plugin installation to "<mb app data>\plugins" (always writable, not only for portable mb) folder.

now, i could remove the need for "plugins\asr presets" folder, but i'm not sure if it would be better than current implementation.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 04, 2023, 01:48:20 PM
I use 125% - all I can say is that previous versions rendered fine.  I can live with the slight cutoffs on the "replace" text boxes, but the main OK/Cancel buttons are rather important.  I have done all the usual tricks: restart MB, reinstall plugin, disable theme colours, restart system, etc., etc., but it remains the same.  The inconsistencies even remain when switching down to 100% DPI.  I should mention that this is a Win7 system, but again, all other versions rendered more-or-less fine.

the problem is that i can't test the plugin using win7, i have only win10. i'll try to do something again to fix it, but i'm not sure, what i must try.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 04, 2023, 02:47:23 PM
now (and already for a while), mb has "add plugin" button for automatic plugin installation to "<mb app data>\plugins" (always writable, not only for portable mb) folder.

now, i could remove the need for "plugins\asr presets" folder, but i'm not sure if it would be better than current implementation.
As for my alleged issues, you can leave things as they are. I am now using the method Messiaen stated.

Perhaps I'm old school, but I've never used the "add plugin" button for installing new plugins. I just drag and drop to the appropriate directories.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 04, 2023, 08:10:35 PM
Well, now the OK/Cancel buttons are only 50% cut-off, whereas before they were almost 80% missing, so they are "useable" at least.  Curiously the "replace" lines remain exactly the same.  I do understand the "if you can't reproduce it you can't fix it" dictum, so I can live with it and just suffer in my stubborn, and ever-shrinking, Win7 world. ;)

(https://i.imgur.com/tdterD6.png)

try new version (notice that now you can also slightly enlarge preset editor window vertically, if new version doesn't work acceptably):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

also, are there similar visual glitches in the main ASR window on your pc?
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 05, 2023, 06:59:14 AM
notice that now you can also slightly enlarge preset editor window vertically, if new version doesn't work acceptably)
Well, you fixed the "replace with" fields  :) , they are now spaced properly, but there's no change at all in the Ok/Cancel button cutoffs.  And no, the window doesn't enlarge vertically - the cursor changes (to "adjustable") when mousing over the top/bottom border, but it can't be dragged larger/smaller.  (Horizontal works as expected.)

Curiously (as an experiment), if I click the "maximise" button the preset window maximises horizontally, and tries to stretch vertically but doesn't quite make it all the way, again with no change to the buttons.

Quote from: boroda
also, are there similar visual glitches in the main ASR window on your pc?
They are not as pronounced - only a couple of overlaps in the "middle" panel, where the <Custom Text 3> and <Custom Text 4> fields are (but they are perfectly useable).  The rest of the main window is fine.  These particular glitches aren't recent, they have been there as long as I remember - I just never mentioned them as they are minor and never interfered with anything.

(https://i.imgur.com/d7jDclU.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 09, 2023, 04:03:42 AM
And no, the window doesn't enlarge vertically - the cursor changes (to "adjustable") when mousing over the top/bottom border, but it can't be dragged larger/smaller.

try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 07:41:34 AM
That did it - the manual vertical adjustment works (and saves).  Thank you for the extra attention to this small detail.  An odd amount of trouble for 10 pixels (which, come to think of it, is suspiciously close to a DPI offset of the title-bar height windows adds to modals by subtracting from client-space).  Maybe Visual Studio is "helpfully" screwing around with newer versions of manifests for their UX additions again.

In any event, I appreciate it.    8)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 09, 2023, 06:05:11 PM
ok. i'm glad that this is solved.

one minor enhancement: i've changed vertical maximized size of preset editor to last manually set restored vertical size (i mean that now this maximized window must not cut off ok/cancel buttons too).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 07:19:21 PM
now this maximized window must not cut off ok/cancel buttons too
The Devil is in the details - works as expected.

Speaking of details, in the description of the "Write result of virtual tag expression..." example preset, you put in the (English) description: "...If you want to pass a string to a function as is, you must put it in DOUBLE quotes."

Due to the vagaries of English, the _"_ symbol is actually called "double quotes", while the _'_ apostrophe symbol is "single quote".  So, when you say "put it in double quotes" you're actually just saying surround it in a single set of quotation marks, which is obviously the wrong syntax.

So, instead of "DOUBLE QUOTES" you should probably say something like "put it in two sets of double-quotes", or "double-double quotes", or even "quadruple quotes", though the last two are neither colloquially correct or properly descriptive.

I think originally you had an actual \@eval example in the description which showed the proper syntax, not just in the <Custom Text 1> slot, which can be overwritten by the user if they modify that text.  Including the example in the description was the simplest thing.

So, yeah, that's the long way of describing a silly detail.  Just a devilish suggestion.  God knows why English became the de facto internet standard - almost anything else would have probably been better.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 07:30:23 PM
So, instead of "DOUBLE QUOTES" you should probably say something like "put it in two sets of double-quotes", or "double-double quotes", or even "quadruple quotes", though the last two are neither colloquially correct or properly descriptive.
A not-native English speaker here.

These suggestions sound very weird to me.
It might make some sense if AT&RT was saying 'in two quotes', but it says 'in double quotes'.
Perhaps change 'in' to 'between', but still in my mind it will be clear to anyone and will not cause any confusion.
The term 'double quotes' is plural, so I would think it is obvious there need to be two double quotes.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 07:54:16 PM
The term 'double quotes' is plural, so I would think it is obvious there need to be two double quotes.
It's NOT actually plural in this sense.  A quoted phrase is "enquotated" between two single-"double quote" characters, so "put it in quotes" and "put it in double-quotes" actually mean exactly the same thing.  (Trust me, they really are the same.)  Theoretically, you would technically say "enclosed with double-enquotation", but that's even weirderererer!

Putting something in two sets of double-quotes is never grammatically correct in English (or probably any other language), so it doesn't really have a description.  (A "quotation within a quotation" would use single-quotes [Apostrophe's] inside the outside double-quotes.)

By the way, the suggestions sound weird to me too (and I am a native speaker), that's why I included the long-winded explanation.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 08:32:48 PM
A quoted phrase is "enquotated" between two single-"double quote" characters, so "put it in quotes" and "put it in double-quotes" actually mean exactly the same thing.
So to you 'between quotes' and 'between double quotes' is the same thing?

edit
To prevent time being wasted on some purely academical issue, could you give a link to a real-world example where somebody misunderstood the term 'double quotes', used two single quotes and couldn't figure it out?

(if such an example actually exists, the person involved will and shouldn't be using neither MusicBee nor AT&RT)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 08:41:16 PM
Yes, because the "double" in "double quotes" is descriptive, not literal.  To be literal, you'd still have to say double-double-quotes, which would then mean 8 apostrophes (single quotes), or 4 double-quotes.  Yuck!
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 08:46:13 PM
Yes, because the "double" in "double quotes" is descriptive, not literal.  To be literal, you'd still have to say double-double-quotes, which would then mean 8 apostrophes (single quotes), or 4 double-quotes.  Yuck!
I specifically wrote 'between double'.

You can't really put anything between a singular thing can you? (Between a rock and hard place, etc.)
I can not imagine saying 'between double' indicating you should put something between single quotes.
It's like saying the exact same thing twice. Both 'between' and 'double' indicate 2 items.
I'm sure there is an English word for such a grammatical error.
Something is 'between quotes' or 'between double quotes'. Seems clear enough (and correct) to me.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 09:02:00 PM
To prevent time being wasted on some purely academical issue, could you give a link to a real-world example where somebody misunderstood the term 'double quotes', used two single quotes and couldn't figure it out?
Well, technically, by even bringing this issue up in the first place, I myself am the perfect example.  I don't interpret words literally, I interpret them figuratively.  A non-native speaker in any language would "probably" interpret literally, so from that point of view you're "accidentally correct", if that makes any sense.

I'm not trying to be difficult - it just seems to come naturally to me.  And yes, this issue is silly, but we've already had one user in this thread (above) who was tripped-up by the new syntax, so for anyone reading the description, it's important. (I guess.)

Quote
I can not imagine that to be a correct phrasing of putting something between single quotes.
No, I am not related to that other user (whatever his name was) who caused you such a tizzy last week.   :)

Putting something between single quotes would mean printing it as 'hello'.
Putting something between double quotes would mean printing it as "hello".

So yeah, clarity is not the friend of English!
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 09:13:03 PM
so from that point of view you're "accidentally correct",
In my language I would be correct both accidentally and on purpose.

We call something such as 'between double' a grammatical style error. We call it a tautology.
(I used G-translate for that word)
Perhaps the English language should adapt that concept? ;-)
(or maybe it is some hood vs. trunk thingy?)

(apologies to Boroda for somewhat derailing here, but I am guessing he will excuse us and finds the matter mildly interesting)
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 09:49:20 PM
There's an old joke that is often used to show why the element of Aristotelian-logic called a Syllogism (a major and a minor premise followed by a conclusion) is flawed:

A man reads in a newspaper that the odds of someone bringing a bomb onto an airplane are 100,000 to 1, but the odds on 2 people bringing bombs onto the same plane are 100 million to 1.  He thinks to himself, reasoning (incorrectly) that if two bombs has the higher odds, "If I bring my own bomb onto the plane the odds are much better that I will be safer!"

Tautology is a rigorous logic where something is "always true" which is best suited to the language of mathematics, not natural human language, which is poetically messy, even when trying to be simple.  Reminds me of the old adage about the so-called Golden Rule: "Do unto others as you would have them do unto you" - which sounds like a great idea until you realise that masochists use the same language as everyone else, but not with the same meaning.

I'm not trying to be flippant (and I too apologise for going way off-topic).  I just brought it up as a suggestion to making the plugin instructions clearer!  Guess I failed this time.   :)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 09:57:47 PM
There's an old joke that is often used to show why the element of Aristotelian-logic called a Syllogism
Thanks for that write-up. Funny and interesting, and food for the grey cells for sure.
(it really seems like a brilliant suggestion to bring a bomb aboard an airplane. It's now on my what-to-pack list. Thanks!)

But what I meant by throwing 'tautology' into the ring was simply to make a comparison between "between double" and somebody saying "a big enormity".
Let's await some certified English professor to lift a glove?
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 09, 2023, 10:12:23 PM
Too late to mention that I was an English major in University?  Probably why I changed to Philosophy afterwards before just dropping out and looking for Godot.  Hmm.  Are you a fan of Free-Jazz?  When I was younger I used to dismiss it as noisy nonsense, but as I get older I begin to find pleasure in the challenge of it.  Mayhap I have become the masochist, and it's all John Coltrane's fault!  :D
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 09, 2023, 10:27:03 PM
Let's keep this thread on topic please. If you wish to continue discussion double-quotes, please take it to "Beyond Music Bee"  and I'll split this off and merge it there.

The management thanks you.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 10:28:42 PM
Are you a fan of Free-Jazz?  When I was younger I used to dismiss it as noisy nonsense, but as I get older I begin to find pleasure in the challenge of it.
Thanks for asking.
Yes, I have opinions on free-jazz, and on Coltrane, and on getting older and realising younger me would have fierce arguments and disagreements with older me.
But going into that would (should) get us reprimanded.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on June 09, 2023, 10:34:30 PM
If you wish to continue discussion double-quotes, please take it to "Beyond Music Bee"
Yeah but, no but, the double-quote thingy directly refers to how AT&RT describes that matter.
So it might be good if somebody with a degree in English could say if it is wrong and should be changed, or if it is o.k. and can remain as it is?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 09, 2023, 11:30:06 PM
Due to the vagaries of English, the _"_ symbol is actually called "double quotes", while the _'_ apostrophe symbol is "single quote".  So, when you say "put it in double quotes" you're actually just saying surround it in a single set of quotation marks, which is obviously the wrong syntax.

So, instead of "DOUBLE QUOTES" you should probably say something like "put it in two sets of double-quotes", or "double-double quotes", or even "quadruple quotes", though the last two are neither colloquially correct or properly descriptive.

thanks for correcting me. you might want to reimport ASR presets (though this is the only change i've made for presets).

i've fixed a UI bug for "paste tags from clipboard" command:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

God knows why English became the de facto internet standard - almost anything else would have probably been better.

NO! it would be MUCH worse if CHINESE (or even russian) was internet standard language!  ;D
Title: Can't sort by album size
Post by: Electrolite on June 11, 2023, 11:42:42 PM
I'm trying to sort my albums by size but I can't get it working properly.

I used ALR to create the following preset:
(https://i.imgur.com/Hl38IJJ.png)

Then I set it to a custom tag called Album Bytes. When I sort by this tag the order is incorrect.
I think there is an issue with either the ALR preset or the Custom tag.

MusicBee is indeed sorting by the Album Byte field but the issue is that these values do NOT reflect the actual album size.
(https://i.imgur.com/YYgeyxf.png)

I already set my custom tag to Number in Configure Fields but that didn't help.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 12, 2023, 01:49:40 AM
1st of all, you CAN'T sort the output FILE using LR. table can be sorted only in preview (by clicking on column header), and this sorting is intended only for easy filtering results by some condition (e.g. write only those strings to file which has some field equal to/greater than/etc. some value). to sort the OUTPUT FILE (this sorting will be also default sorting of preview table), you need to sort MB VIEW you are using, when you generate the report.

2nd. what do you mean by "custom tag"? how do you set it? or do you mean "virtual tag" actually?

3d. from your 1st screenshot, LR, obviously, treats the <size> field as floating point numbers, and this is correct (because LR treats ANY number as floating point number). the problem is that the actual numbers are too big (all these E+19, E+20 ,... mean *10^19, *10^20 - multiply by 10 to the power of 19, etc.).

i suspect this is happening due to your windows regional settings. open mb menu> edit> prefs> plugins> tag tools> configure, check the measurement units.

if this doesn't solve the problem, create a static playlist containing 1 track, generate a report for it, and post screenshots of mb playlist view (containing <size> field) and of report.

EDIT:

you are using old plugin version. i've recently rewritten LR almost from scratch (and consolidated ALR/LR into one LR command). update plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Electrolite on June 12, 2023, 03:45:32 AM
1st of all, you CAN'T sort the output FILE using LR. table can be sorted only in preview (by clicking on column header), and this sorting is intended only for easy filtering results by some condition (e.g. write only those strings to file which has some field equal to/greater than/etc. some value). to sort the OUTPUT FILE (this sorting will be also default sorting of preview table), you need to sort MB VIEW you are using, when you generate the report.

I didn't try to sort directly from the LR table. I set the results into a MusicBee custom tag using the 'Save Field (...) to tag (...) option like this:
(https://i.imgur.com/vRZYP9s.png)

2nd. what do you mean by "custom tag"? how do you set it? or do you mean "virtual tag" actually?

I used the 'Save field to tag' option from LR to save the table results into one of these custom tags, I didn't use the Virtual tags. I tried to follow a very old tutorial on Album size sorting and they said there was a bug with virtual tags.
(https://i.imgur.com/q7C2FLf.png)

3d. from your 1st screenshot, LR, obviously, treats the <size> field as floating point numbers, and this is correct (because LR treats ANY number as floating point number). the problem is that the actual numbers are too big (all these E+19, E+20 ,... mean *10^19, *10^20 - multiply by 10 to the power of 19, etc.).

i suspect this is happening due to your windows regional settings. open mb menu> edit> prefs> plugins> tag tools> configure, check the measurement units.

if this doesn't solve the problem, create a static playlist containing 1 track, generate a report for it, and post screenshots of mb playlist view (containing <size> field) and of report.

EDIT:

you are using old plugin version. i've recently rewritten LR almost from scratch (and consolidated ALR/LR into one LR command). update plugin:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

I tried to update the plugin but now when I preview the table, I get this error:
MusicBee v3.5.8447.35843Store (Win10.0), 11 Jun 2023 23:31:

System.ArgumentException: An entry with the same key already exists.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.TreeSet`1.AddIfNotPresent(T item)
   at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
   at MusicBeePlugin.LibraryReportsCommand.executePreset(String[] queriedFiles, Boolean interactive, Boolean saveResultsToTags, String functionId)
   at MusicBeePlugin.LibraryReportsCommand.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()

Maybe I installed it incorrectly, I extracted the zip and used the add plugin to add the .dll file. I'm using the MusicBee from MS Store.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 12, 2023, 07:57:51 AM
it seems you are familiar with plugin updating/reinstallation process for mb store version, but i'll remind you: disable plugin, then restart mb, and click 'add plugin' button in mb prefs pointing mb to new plugin .zip

try to temporarily install this debug version:

https://www.mediafire.com/file/e7ux0rauaptj74g/mb_TagTools_debug.zip/file

post more detailed error message.
Title: Re: Additional Tagging & Reporting Tools
Post by: Electrolite on June 12, 2023, 08:35:46 AM
I installed your debugger version, looks like the error now shows the line of code where the issue happens.

MusicBee v3.5.8447.35843Store (Win10.0), 12 Jun 2023 4:32:

System.ArgumentException: An entry with the same key already exists.
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.TreeSet`1.AddIfNotPresent(T item)
   at System.Collections.Generic.SortedDictionary`2.Add(TKey key, TValue value)
   at MusicBeePlugin.LibraryReportsCommand.executePreset(String[] queriedFiles, Boolean interactive, Boolean saveResultsToTags, String functionId) in C:\Users\Alexander\Source\Repos\TagTools\Additional-Tagging-Tools\LibraryReports.cs:line 1168
   at MusicBeePlugin.LibraryReportsCommand.previewTrackList() in C:\Users\Alexander\Source\Repos\TagTools\Additional-Tagging-Tools\LibraryReports.cs:line 2214
   at MusicBeePlugin.PluginWindowTemplate.serializedOperation() in C:\Users\Alexander\Source\Repos\TagTools\Additional-Tagging-Tools\PluginWindowTemplate.cs:line 299
   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 & Reporting Tools
Post by: boroda on June 12, 2023, 01:58:17 PM
it seems that you have duplicated tracks in your library. try this version:

https://www.mediafire.com/file/e7ux0rauaptj74g/mb_TagTools_debug.zip/file

it's still a temporary debug version, i'll recompile it if no exceptions arise now.

keep in mind that Sum(Size) will be expressed in bytes. to see e.g. megabytes, use virtual tag "$Round($Div(<Custom1>, 1048756),1) MB"

but 1st, post a screenshot of preview table displaying album size using bytes. i want to make sure that numbers are not senselessly big (these E+19, E+20, etc.).
Title: Re: Additional Tagging & Reporting Tools
Post by: Electrolite on June 12, 2023, 10:58:57 PM
but 1st, post a screenshot of preview table displaying album size using bytes. i want to make sure that numbers are not senselessly big (these E+19, E+20, etc.).
This version is working, values on the table aren't unreasonably huge:
(https://i.imgur.com/omNoW6u.png)

keep in mind that Sum(Size) will be expressed in bytes. to see e.g. megabytes, use virtual tag "$Round($Div(<Custom1>, 1048756),1) MB"
I think MusicBee isn't using the 1024 x 1024 bytes definition so I just had to change your conversion to "$Round($Div(<Custom1>, 1000000),1) MB". Now the Virtual tag is calculating the Album Size correctly.
(https://i.imgur.com/Wl1kBZN.png)

Can I use a Virtual Tag Function to access the byte values directly from my Virtual Tag instead of saving these values into Custom1 tag?
(https://i.imgur.com/DyoRvD2.png)

And last question do I have to auto-apply the preset on every MusicBee startup or is there a way for the calculation to be called dynamically only if the album changes/new song is imported.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 13, 2023, 07:29:18 PM
keep in mind that Sum(Size) will be expressed in bytes. to see e.g. megabytes, use virtual tag "$Round($Div(<Custom1>, 1048756),1) MB"
I think MusicBee isn't using the 1024 x 1024 bytes definition so I just had to change your conversion to "$Round($Div(<Custom1>, 1000000),1) MB". Now the Virtual tag is calculating the Album Size correctly.

No, it's not resolution in pixels (1024px*1024px) in virtual tag formula, it's file size in bytes/KB/MB/etc (K usually means 1024 for file sizes, M - 1024*1024, etc. for file size, not for resolution, which doesn't have any direct relation to file size). but anyway, LR has been incorrectly working with units of measurements. i've fixed this, see download link at end of post.

Can I use a Virtual Tag Function to access the byte values directly from my Virtual Tag instead of saving these values into Custom1 tag?

yes, you can. then you can use the formula (or just part of a formula): $LR(<URL>,function_id)

And last question do I have to auto-apply the preset on every MusicBee startup or is there a way for the calculation to be called dynamically only if the album changes/new song is imported.

LR (and ASR too) virtual tag functions are calculated dynamically (you might want to "save" results to <Null> tag in this case). auto-calculating LR presets on startup (and after given # of tag changes) may be required only if you want to persistently store aggregated function results (not virtual tag functions!) in (custom) tags.

----------------------------

1. i've added some simple formatting to LR aggregated functions (and as a consequence for the virtual tag functions): now results can be multiplied/divided by a number, rounded to a number of digits after decimal point, and some custom text can be inserted between tag number value and tag text postfix after number.

NOTE: rounding is being calculated for final results (not for every file)!

(https://i.imgur.com/hpLSJEu.png)

2. Treating of units of measurements by LR is fixed. now <Size> field equal to "700 KB" for individual file (before summarizing) is treated as "700 * 1024 B", previously it has been treated as "700 * 1000 B". the same for <Bitrate> field and other similar fields.  

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Electrolite on June 14, 2023, 07:36:04 AM
First of all, thanks for the effort these are great changes.

No, it's not resolution in pixels (1024px*1024px) in virtual tag formula, it's file size in bytes/KB/MB/etc (K usually means 1024 for file sizes, M - 1024*1024, etc. for file size, not for resolution, which doesn't have any direct relation to file size). but anyway, LR has been incorrectly working with units of measurements. I've fixed this, see download link at end of post.
Sorry, there was a miscommunication here. We have 1 MB = 2^20 = 1024 x 1024 = 1,048,576 bytes but there is another definition for MB that is: 1 MB = 10^3 =1000 x 1000 = 1,000,000 bytes.
I meant to ask which definition of MB LR or MusicBee were using and if that was the reason for the wrong unit conversions.

2. Treating of units of measurements by LR is fixed. now <Size> field equal to "700 KB" for individual file (before summarizing) is treated as "700 * 1024 B", previously it has been treated as "700 * 1000 B". the same for <Bitrate> field and other similar fields.  
Oh, so the issue was what I asked about, LR was using the 1MB = 10^3 bytes definition not the classic 1MB = 2^20 bytes.

I'm calculating the MB size directly on LR and just created a virtual tag that fetches results from the virtual function:
(https://i.imgur.com/mabTFPC.png)

The virtual tag works fine to display the album sizes in the panels:
(https://i.imgur.com/feqEKxg.png)

Unfortunately, I can't use the virtual tag for any kind of sorting, when I sort my albums by the virtual tag it just crashes MusicBee. I suppose this happens due to the asynchronous nature of the LR function? This is a very old bug because I saw old posts talking about it.

Anyway if this can't be fixed I'll use the virtual tags for displaying album sizes dynamically and the static custom tag for sorting, this solution will work just fine :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 14, 2023, 09:13:58 AM
frankly speaking, i never tried to sort albums by any virtual in general, and by virtual tag containing $LR() function particularly.

i've implemented LR own caching several months ago, but i've commented this code out because mb also caches custom virtual tag function results, and this mb caching was working fine in my tests.

i'll try this to see what is happening and fix possible issues, but i don't promise.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 14, 2023, 09:48:34 AM
mb 3.5.8554 Portable is not crashing, when i try to sort albums by $LR(files size)  virtual tag, but it's working very slowly and unreliably. sometimes mb sorts by album size, sometimes doesn't, depending on the number of albums in the current view.

i don't see how this can be solved because sorting by $LR function may require calculation of this function for thousands of albums (if the entire library is included in the current view).
Title: Re: Additional Tagging & Reporting Tools
Post by: Electrolite on June 15, 2023, 01:21:50 AM
I'm using the same version but from MS Store. Now my MB isn't crashing but the sorting isn't working just like you.

But don't worry about this, I imagine solving this async problem will be a pain, using custom tags for sorting will work just fine :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 15, 2023, 01:54:50 AM
I don't know if boroda is willing to add another filter option and icon, but adding an option to save "favorites" might be a nice addition. This would make it easier to find often used presets. Yes, the search field helps, but bookmarking a favorite would be really nice.

not exactly what has been requested, but i've added the concept of "favorite presets". they can't be filtered, but they be always sorted 1st in preset list:

(https://i.imgur.com/lmvYdUw.png)

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 15, 2023, 02:29:53 AM
i've added the concept of "favorite presets". they can't be filtered, but they be always sorted 1st in preset list:
Thanks boroda. About to test it in a few minutes.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on June 15, 2023, 03:14:30 AM
Looking good, boroda. Your implementation to my request works just as nicely as my original request. Very much appreciated.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 15, 2023, 03:27:18 PM
I, too, appreciate and thank you for this new pseudo-filter.

Curiously, when trying to make more room in the bottom preview-panel (now that things at the top are easier to find), I've noticed that when I adjust the "invisible" splitter (just above the "preset management" panel), the custom size is not saved properly.

If you repeatedly close the ASR window, then open it again, the preview panel gets progressively smaller by a few lines (and the top preset-panel gets correspondingly larger by a few lines each time) until eventually the original size of the panels is restored.  A strange bug.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 16, 2023, 03:44:23 AM
Curiously, when trying to make more room in the bottom preview-panel (now that things at the top are easier to find), I've noticed that when I adjust the "invisible" splitter (just above the "preset management" panel), the custom size is not saved properly.

If you repeatedly close the ASR window, then open it again, the preview panel gets progressively smaller by a few lines (and the top preset-panel gets correspondingly larger by a few lines each time) until eventually the original size of the panels is restored.  A strange bug.

yes, i've noticed this too (on win10 @ 125%). i think it somehow relates to dpi scaling, and i haven't found a solution: simply setting splitter distance and immediately followed reading it gives different values.

all i can imagine in this case is to save splitter distance on manual splitter resizing rather than on window closing. saved splitter distance anyway will be slightly changed after resizing, but only once. it shouldn't be moved on every ASR window opening/closing.

i'll try to make this today. not sure if i succeed.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 16, 2023, 06:17:13 AM
@Messiaen (and maybe others), try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 16, 2023, 07:57:29 AM
Well, it's much improved, but now (and this is insignificant in the scheme of things), the splitter actually migrates very slowly up instead of down, probably 1 pixel for every 2/3 ASR open/close iterations.  In other words, you really have to look for the difference, and maybe within six months a pedestrian user might lose the height of half a line.

I only notice it because I prefix my custom presets with "_" underscores to raise them to the top, and that character acts as a horizontal line marker in this case.

I doubt too many users would ever even notice it - in fact, it only seems to happen if you adjust the splitter at all initially (at its lowest placement it appears static), and considering it's invisible in the first place, how many people really do that?

Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 17, 2023, 05:26:24 AM
anyway, i've tried to improve splitter behavior.  but i'll stop on this version if it's working acceptably:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on June 17, 2023, 07:03:01 AM
i'll stop on this version if it's working acceptably
Appears to be completely fixed.  Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on June 26, 2023, 04:00:52 PM
minor fix:

sorting of ASR preset list is updated after renaming preset:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Heathen Hammer on July 03, 2023, 02:19:43 AM
Hi everyone, I skimmed through this thread to see if anyone is having the same problem that I am. As this thread is very long, it is possible that I may have missed something. Pardon me if I'm repeating a previous problem.

I installed the plugin as per the instructions in the accompanying .txt file. I copied the folder AR Presets and the file mb_TagTools.dll to the Plugins folder under MusicBee.

However, whenever I click on Tools > Additional Tagging & Reporting Tools, nothing happens. The menu simply closes.

I am using MusicBee version 3.3.7261.

Any help is appreciated. I'm not computer savvy at all!  :(
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on July 03, 2023, 03:07:09 AM
I am using MusicBee version 3.3.7261.
The version of MB that you're using is three years old. Update to the latest 3.5 version from the first forum topic and then try using the plugin again.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 03, 2023, 02:07:16 PM
i can upload an old plugin version, which probably would work on mb 3.3, but i suspect that it anyway requires at least 3.4, and it's better to update mb to the latest version.
Title: Re: Additional Tagging & Reporting Tools
Post by: Heathen Hammer on July 03, 2023, 06:06:58 PM
Thank you all for your help! Plugin works nicely.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 09, 2023, 02:11:26 PM
Something not-so-important that has been triggering some of my overly sensitive brain cells for a while:

In MusicBee's confirmation panels, 'Yes' usually means 'save', 'No' usually means 'don't save':

(https://i.imgur.com/oofvdgR.png)

But AT&RT has confirmation panels that behave differently. (opposite)
E.g. here, contrary to MusicBee's behaviour, 'Yes' means 'don't save'

(https://i.imgur.com/u0VndUC.png)

And 'No' would probably better be labeled as 'cancel'?

I think it would be good if this was aligned with MusicBee's behaviour?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 09, 2023, 08:19:32 PM
Something not-so-important that has been triggering some of my overly sensitive brain cells for a while:

In MusicBee's confirmation panels, 'Yes' usually means 'save', 'No' usually means 'don't save':

(https://i.imgur.com/oofvdgR.png)

But AT&RT has confirmation panels that behave differently. (opposite)
E.g. here, contrary to MusicBee's behaviour, 'Yes' means 'don't save'

(https://i.imgur.com/u0VndUC.png)

And 'No' would probably better be labeled as 'cancel'?

I think it would be good if this was aligned with MusicBee's behaviour?

not sure if it's important (or even better), but i've changed this:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on July 09, 2023, 08:49:26 PM
not sure if it's important (or even better), but i've changed this:
I think he meant something more along the lines of "One or more presets ... / Save before closing?"

That wording (and action) would be more consistent with MB itself, so it'd be a change in procedure as well as the modal wording.  In other words, answering "Yes" is a positive action (Saving), instead of forcing the user to go back and choose the other button just to accomplish the same thing.

Or maybe an overall-checkbox like "Always save changes when closing" to optionally do away with the whole question in the first place, so everything becomes a "last used" paradigm by default.  Sometimes I get confused by the current modal and I have to think back about what I changed, only to realise it wasn't something important (like a preset definition itself), but just a minor thing like I trimmed an <Album Artist> instead of a <Title>.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 10, 2023, 04:40:13 AM
Ahh, ok. i've changed message text to "do you want to save changes?" and have made 3 buttons: yes, no, cancel.  clicked button is remembered and will be the default button next time, so you can press "enter" key on the keyboard to use the last choice.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on July 10, 2023, 06:53:10 AM
Curiously, pressing the Cancel button is also remembered (not a complaint! - just an observation).  I wonder what MS's suggested UI behaviour tips would say about that.  :)

Thanks, a small but useful improvement.  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 10, 2023, 10:58:52 AM
Curiously, pressing the Cancel button is also remembered (not a complaint! - just an observation).

it's intentional, but I did it without thinking too much  :D
do you think it's worth to disable this?
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on July 10, 2023, 11:24:39 AM
do you think it's worth to disable this?
God no, don't worry about it.  Besides, it's important to cater for the more indecisive users who get confused about what colour socks to wear on a Thursday.  Everyone needs a little love, especially those who fall into their own decision-loops.  ;D
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 10, 2023, 05:53:35 PM
Ahh, ok. i've changed message text to "do you want to save changes?" and have made 3 buttons: yes, no, cancel.
Thnx, I think this is much better.
(no more need to read the panel message twice before clicking a button  ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 14, 2023, 11:07:10 PM
The Plugin is very useful I see it now (Much appreciation 🫂) - rewriting the song titles to Spotify guidelines is a hassle without ASR**
My Problem.
1. I have set a hotkey to open the plug windows (Alt+D)
2. I have my custom Present
3. I checked the tick the assigning hotkey for the preset (hoping it is ALT+D)

Expectation: The preset would run to the selected tracks, silently without opening the ASR window

what should I do to reach the expectation?
(https://i.imgur.com/28p9XP8.png)

**I just realize most of the songs scrobble to LastFM are from Spotify (you can tell that cause Spotify does not use "( )" on remixes & other releases, Apple & Deezer does. Spotify uses " - "    also is because
** I use the "music bee sync to Service" plugin  to sync Musicbee & spotify  Playlist a lot (SpoBee - I call that)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 15, 2023, 07:17:55 AM
3. I checked the tick the assigning hotkey for the preset (hoping it is ALT+D)
No, after having ticked the hotkey checkbox for a preset, you then need to assign a specific hotkey to it in MusicBee itself.

(the hover-over tip tool explains that)
(https://i.imgur.com/TuUN81B.png)
Depending on the version of MusicBee/AT&RT you may need to restart MusicBee before you will find the preset in the hotkeys list.

Note that if you have ticked the checkbox in front of the preset, the preset will be applied automatically continuously. So be careful with that!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 15, 2023, 05:48:26 PM
an illustration to what hiccup has written:

(https://i.imgur.com/6zLF2Qz.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 15, 2023, 08:01:19 PM
 :)  :)  :)  :)  :)

🙏🙏🙏Thanks, both of you. It is working perfectly 🥂
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 15, 2023, 09:29:04 PM
Please bear with me
I have another issue - I wanna create another (2nd) preset [proving very challenging since the first present was a very slight modification of the one that come out of the box] I cant learn regex at moment I even asked Bing AI - IT DID NOT WORK(IT MISSED SOME STEPS AND OTHERS) HENCE WHY AM HERE.
(https://i.imgur.com/9WecIgE.png)


Expectation:
1. If the <tag> contains the word "remix" in it then find the first opened bracket "(" and replace it with " - " and then the closing bracket ")" which is usually accompanied by the word remix is removed
(https://i.imgur.com/AEYpVwT.png)


and this is what I want it to be
(https://i.imgur.com/acIb1Wb.png)


2. if possible in another presets I wanna be able to have control on that word "remix" sometimes it might not be it
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 15, 2023, 11:23:52 PM
bing suggestion for your prompt (on 1st screenshot) must work. tiny correction: maybe you should enter "$2- Remix" (without space after $2) in the replace field (instead of proposed by bing "$2 - Remix").

for 2: could you be more specific? give me some examples, which don't work for you now.
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 16, 2023, 01:07:44 AM
Thanks, Boroda

I tried it, and it was still fruitless
(https://i.imgur.com/4OZGxhs.png)
I have listed the steps (1-3) that i approached. i tried to work on a title for a trial and it did NOT work.
(it displayed nothing on the console for the trial)
 
on step 3: there is a single space between "-" and "R" ---> $2- Remix
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 16, 2023, 05:00:20 AM
in steps 2 & 3 look on the right side: you've selected "search in tag: <temp 1>" and "replace with to tag <temp 1>".

you need to select <tag 1> instead of <temp 1> on both steps. also, you can select tag <title> instead of <temp 1>, but then you won't be able to quickly change this tag without opening preset editor (<tag #> pseudo-tag can be reassigned to any actual tag directly in asr main window).

they are not "steps" in terms of asr, just "search settings" and "replace settings". every "asr step" has the own search/replace settings, and "asr steps" are executed in sequence, one after another.
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 16, 2023, 09:59:36 AM
Thanks again for the guidance

This one almost worked, except not to the intention I wanted
(https://i.imgur.com/nd55VWS.png)

Expectation: the "-" should replace the "("
so in the end the result would have been [  Boundaries - DRAMA Remix ]  NOT [ Boundaries DRAMA - Remix]

PS. Only if the title contains Remix this code should work, not if the title contains ( or ). Because there are other songs that contain ( or ) but not the word "remix" and they should not be touched with this Preset
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 16, 2023, 10:23:54 AM
ok, change replace field to

Code
- $2Remix

you can copy this exact string (including all required spaces) by clicking "copy" pictogram on the right.

p.s. you might want to change search field to

Code
\s*\((.*)Remix\)$

and replace field to

Code
 - $1Remix

if you also want to take into account tags like [  Boundaries (Remix) ] , not only [  Boundaries (DRAMA Remix) ].
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 16, 2023, 10:34:11 AM
ok, change replace field to

Code
- $2Remix

you can copy this exact string (including all required spaces) by clicking "copy" pictogram on the right.

Perfect. This one is perfect complete. Thanks 🙏

I am trying to find a way to design an UI for this plugin . to improve the UI (less coding more buttons). I will give a feedback once i have sketched something
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 16, 2023, 10:39:06 AM
i've changed my previous post when you were replying, reread it.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 16, 2023, 10:40:59 AM
I am trying to find a way to design an UI for this plugin . to improve the UI (less coding more buttons). I will give a feedback once i have sketched something

thanks for this. any good ideas on UI/UX improvement are welcome.
Title: Re: Additional Tagging & Reporting Tools
Post by: Tinidazone on July 16, 2023, 10:57:31 AM
i've changed my previous post when you were replying, reread it.

I had to create another Preseset to understand it - i didn't see what it was supposed to do
But
If it was to help with the Album name -  thanks 🙏I prefer to leave it as it came
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 16, 2023, 11:55:22 AM
that preset can be applied to any tag which values can be [  Boundaries (Remix) ] OR [  Boundaries (DRAMA Remix) ], e.g. to album name, and will ignore tag values (won't change tags), which don't have either of these patterns.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on July 19, 2023, 08:17:25 PM
Just discovered an odd bug from the stock Transliterate to ASCII preset.  If the preset is applied to the following title (note the unicode quotation marks and the unicode hyphen character):

Grave, ma non troppo tratto (“Muß es sein ”) – Allegro (“Es muß sein !”)

the returned title becomes:

Grave, ma non troppo tratto ("Muss es sein " – Allegro (“Es muß sein !”))

The first text ("Muss es sein " is converted (up to and including the closing quotation mark) as expected, but the following close-parenthesis is somehow transferred to the end of the text, and none of the other characters are transliterated.

It appears the $TransliterateToAscii() function via the plugin is not at fault - it returns the expected result, so it appears AT&RT's parsing might be the culprit.  I don't usually use this preset, so I don't know what other text (if any) might trigger it, I just noticed this as a fluke, and saw it was reproducible.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 19, 2023, 09:31:37 PM
Just discovered an odd bug from the stock Transliterate to ASCII preset.  If the preset is applied to the following title (note the unicode quotation marks and the unicode hyphen character):

Grave, ma non troppo tratto (“Muß es sein ”) – Allegro (“Es muß sein !”)

the returned title becomes:

Grave, ma non troppo tratto ("Muss es sein " – Allegro (“Es muß sein !”))

thanks a lot for this notification. have forgotten to change this preset, when had introduced new \@eval[[]] behavior:

i've fixed another \@eval[[]] bug related to tag values containing quotes. Now, if you want to pass a string to a virtual tag function as is, you must put it in DOUBLE quotes, e.g.

\@eval[[$IsNull(""$1"",,NULL,,$1)]]

instead of

\@eval[[$IsNull("$1",,NULL,,$1)]].

the updated preset (nothing else is changed):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on July 19, 2023, 11:14:45 PM
Thanks.  Now I'm kicking myself for not checking the preset myself - I thought to check the function, just not the preset itself.  So much for the thin veneer of cleverness in my disguise.  :)

If I may, a suggestion to mull over... I know it may be too much trouble to implement, given AT&RT "targeted nature" towards presets working on specific tags, but in MB 's <Ctrl-R> search/replace, the first tag in the list to choose from is "Any Field", and I've found that to be extremely useful recently.  Obviously, ASR presets can be made to reference many tags in one preset, but it still requires one to anticipate which fields are most likely.

For certain kinds of presets such as the clean-up type (like replacing multiple spaces with single space or whitespace trimming, etc), this sort of any-field thing is ideal.  However, I haven't thought it through enough to know if it's got broader appeal than just that (admittedly useful) example.

What do you think?

(And I must thank Hiccup for his most recent suggestion about changing the "Some presets have changed" behavior - just in the last week alone I must have breezily clicked though that modal enough times to make even the pope doubt his faith.  Why wasn't it suggested years ago?  A Godsend.)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 20, 2023, 02:20:08 AM
in MB 's <Ctrl-R> search/replace, the first tag in the list to choose from is "Any Field", and I've found that to be extremely useful recently.  Obviously, ASR presets can be made to reference many tags in one preset, but it still requires one to anticipate which fields are most likely.
...
What do you think?

well, it's possible, but it's not so easy, because it will require not only to iterate through all writable tags, but also to force the destination tag to be always the same as the source tag, and only if the source (pseudo)tag is set to <any tag>. UI behavior must be changed for this too.

i'm not sure if this functionality is really needed in the context of ASR (considering that it's already supported by mb native search & replace). maybe it's worth to wait for responses of other users?

Why wasn't it suggested years ago?

maybe, because this dialog (even in its initial form) has been implemented recently?  :)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on July 20, 2023, 05:07:59 PM
… And I must thank Hiccup for his most recent suggestion about changing the "Some presets have changed" behavior - just in the last week alone I must have breezily clicked though that modal enough times to make even the pope doubt his faith.  Why wasn't it suggested years ago?  A Godsend.)
Good to hear I'm not the only one that appreciates these small (slightly OCD) improvements implemented by boroda.

@boroda:
When using 'Import ASR preset', presets that have the (previous) .xml extension are not shown, nor can be imported in this way.
Is it intentional that you can now only import presets that have the newer asr-preset.xml extension?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 21, 2023, 05:43:46 PM
@hiccup
yes, i've recently completely removed the support for old format presets. because old presets have been actually very differently implemented, and they have been converted to new format by special function.

@Messiaen
i've added support for <ALL TAGS> pseudo-tag, but it's now experimental. you will need to copy exiting presets(s) and switch types one/more of <tag #> pseudo-tags from "writable" to "writable+<all tags>" in preset editor. you won't be able to select <ALL TAGS> pseudo-tag directly in preset editor, i.e. you won't be able to create preset/copy of preset, which will be defaulted to <ALL TAGS> (for safety reasons). but you will be able to select <ALL TAGS> in <tag #> field in ASR main window.

https://www.mediafire.com/file/r51stg5alaxwmup/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on July 21, 2023, 08:31:07 PM
...but it's now experimental...
That's the understatement of the century.  It's beginning to dawn on me just how dangerous this option actually is - if combined with auto-organizing it's capable of completely decimating whole albums and sending them in pieces to the four corners of the kingdom.  As such, while it's still experimental, I'd make it harder for people to actually use it, like maybe half-disabling the "apply" button for now and just allowing previews.  It does seem that setting a hotkey to one does not actually apply the results, though the status-bar says it was applied - this may be unintentional, but it's good for safety.  Same caveat would apply to auto-applying - not sure if it works or not, but might be wise to disable that too, just in case.

The "Always preserve these tag values" list is invaluable, to be sure.  If you decide to keep this <All Tags> option permanently, there might need to be a similar list where it's "only apply to" instead, as sometimes the "all" in "all tags" is a bit too many.  :)

Also, unrelated observation, in the description for "Always preserve" it says to separate the values with ";;" but using two semi-colons actually breaks the list (as in only the first item is preserved, the rest are applied).  It only works as described when using a single semi-colon to separate the list.  You might change that label.

And as Boroda didn't make this clear above, I'll say it: As a warning to anyone else experimenting with this, I can't underscore enough just how unintentionally destructive a command it can be by it's very nature.  Do not mess around with it on part of your living library - for now, only apply it to albums/songs you have no need for.

I shall experiment more, obviously.  I had a few crashes at first, so it's not entirely stable (but I guess you know that).  I didn't want to report the error logs until I can actually reproduce the steps necessary to reliably crash it again.

Thanks for your efforts.  (The idea seemed harmless enough originally... I'm rethinking that a bit now.)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 22, 2023, 06:19:18 AM
That's the understatement of the century.  It took a little while for me to interpret your description above (not a criticism of your English at all), once I figured out all the qualifications, it makes sense - however, (and read this as a joke, please) "I won't be asking you to give a general lecture on lamda-expressions in the near future".  :)

actually, i would be very thankful if you rephrased my warning in very clear way in natural english, because this is very important.

like maybe half-disabling the "apply" button completely for now and just allowing previews.  It does seem that setting a hotkey to one does not actually apply the results, though the status-bar says it was applied - this may be unintentional, but it's good for safety.  Same caveat would apply to auto-applying - not sure if it works or not, but might be wise to disable that too, just in case.

that's what i was thinking about yesterday. i'm going to completely disable auto-applying of such presets, explicitly disable hotkeys for them, and disable applying of them without explicitly generating preview at first.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 22, 2023, 06:44:58 PM
The "Always preserve these tag values" list is invaluable, to be sure.  If you decide to keep this <All Tags> option permanently, there might need to be a similar list where it's "only apply to" instead, as sometimes the "all" in "all tags" is a bit too many.  :)

this can be done by unchecking undesirable lines of preview. maybe this unchecking can be automated, but i'm not sure how this "automation" can be implemented in UI.

Also, unrelated observation, in the description for "Always preserve" it says to separate the values with ";;" but using two semi-colons actually breaks the list (as in only the first item is preserved, the rest are applied).  It only works as described when using a single semi-colon to separate the list.

i can't reproduce this, but i've found another much more important bug related to "always preserve" field. it's fixed, but could you recheck your issues using updated version?

i'm going to completely disable auto-applying of such presets, explicitly disable hotkeys for them, and disable applying of them without explicitly generating preview at first.

it's done.

also, numerous bug introduced by new <all tags> functionality are fixed:

https://www.mediafire.com/file/ycdl10fo8cgfwns/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: calderino on July 24, 2023, 01:05:47 AM
Hello,
I want to know if this is possible to do with the plugin:

I have my Japanese artist defined as "Translated Name [Original Name]", for example "Hashimoto Yukari [橋本 由香利]".
I want to find typos in the artist names by comparing the Japanese part of the tag and then comparing the English part.

Example:
Let's say I have a file with artist="Hashimoto Yukari [橋本 由香利]" and another one with artist="Hashimoto Yukaro [橋本 由香利]"
I want to check which artists have the same Japanese artist (in this case both match with 橋本 由香利).
Then, I want to compare the English part and have a result if they do not match (Hashimoto Yukari != Hashimoto Yukaro)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 25, 2023, 05:30:56 AM
hello, calderino. yes, it's possible. i'm not sure if you mean "artist" or "album artist" tag, i will suggest using "artist" tag. also, you can use any virtual tags instead of <virtual3> and <virtual4> in my example.

1. define <virtual3> as:
Code
$If($RxReplace(<Artist>,".*\[(.*)\]$","$1")=<Artist>,,$RxReplace(<Artist>,"(.*)\[.*\]$","$1"))

<virtual3> will show translated part of artist name if Japanese part is present (otherwise <virtual3> will be empty).

2. define <virtual4> as:
Code
$If($RxReplace(<Artist>,".*\[(.*)\]$","$1")=<Artist>,,$RxReplace(<Artist>,".*\[(.*)\]$","$1"))

<virtual4> will show Japanese part of artist name if it's present (otherwise <virtual4> will be empty).

3. create Library Reports preset: define 2 groupings: virtual4, virtual3.

this preset will show every unique combination of Japanese artist name and translated artist name, sorted by Japanese name, so you will be able to easily see if there are several translated names for every Japanese name. 1st line of report wil be empty, ignore it, it corresponds to all artists which don't have brackets in their names.
Title: Re: Additional Tagging & Reporting Tools
Post by: calderino on July 25, 2023, 06:12:39 AM
hello, calderino. yes, it's possible. i'm not sure if you mean "artist" or "album artist" tag, i will suggest using "artist" tag. also, you can use any virtual tags instead of <virtual3> and <virtual4> in my example.

1. define <virtual3> as:
Code
$If($RxReplace(<Artist>,".*\[(.*)\]$","$1")=<Artist>,,$RxReplace(<Artist>,"(.*)\[.*\]$","$1"))

<virtual3> will show translated part of artist name if Japanese part is present (otherwise <virtual3> will be empty).

2. define <virtual4> as:
Code
$If($RxReplace(<Artist>,".*\[(.*)\]$","$1")=<Artist>,,$RxReplace(<Artist>,".*\[(.*)\]$","$1"))

<virtual4> will show Japanese part of artist name if it's present (otherwise <virtual4> will be empty).

3. create Library Reports preset: define 2 groupings: virtual4, virtual3.

this preset will show every unique combination of Japanese artist name and translated artist name, sorted by Japanese name, so you will be able to easily see if there are several translated names for every Japanese name. 1st line of report wil be empty, ignore it, it corresponds to all artists which don't have brackets in their names.

Thanks for this. I was not aware of what Library reports did!
One last question, if there are multiple artists in the tag, virtual4 only uses the last japanese name.
How can I adapt the virtual tag to take into account several artists?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 25, 2023, 12:32:03 PM
firstly, there was a bug in library reports command related to "count" function. it's fixed, download latest plugin version to use my improved suggestion (read it below). latest plugin version is beta, but don't worry, beta status concerns only new advanced search & replace functionality.

https://www.mediafire.com/file/ycdl10fo8cgfwns/mb_TagTools_beta.zip/file

new suggestion:

create another LR preset (DON'T delete preset from my previous suggestion) containing 1 grouping "virtual4" and 1 function "Count(Virtual3)" (this function counts the number of unique virtual3 values per every virtual4 value). define condition "export only if Count(Virtual3) is greater than 1". export preset report to m3u playlist, and import this playlist to mb (file> playlists> import playlists).

select this playlist to see only tracks, which have more than 1 translated artist for every Japanese artist. then generate preview using preset from my previous post. now you will see only Japanese and translated artist names, but only for artists, which have both Japanese AND translated parts, AND only if there are MORE THAN ONE translated parts for Japanese part of artist name.

see screenshot as an example:

(https://i.imgur.com/v5ho0Jp.png)

-------------------------------

One last question, if there are multiple artists in the tag, virtual4 only uses the last japanese name.
How can I adapt the virtual tag to take into account several artists?

i'm not sure if there is a workaround for this, i must think about this more, but firstly i need to know how Japanese artist names are formatted in <artist> tag, i.e. are they separated by comma, or by comma followed by space, or by semicolon, etc.?
Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on July 25, 2023, 03:33:51 PM
Hi Boroda,
Thanks for this awesome plugin! I apologise if this has been asked before but I haven’t been able to find any information. There used to be a preset titled along the lines of “Copy tag 1 to tag 2 if tag 1 isn’t empty”. I haven’t been able to find it anywhere for a while now but it used to be in the list of presets supplied with the plugin. Do you still have this preset anywhere?
Cheers Aaron.
Title: Re: Additional Tagging & Reporting Tools
Post by: calderino on July 26, 2023, 12:47:43 AM
Quote
i'm not sure if there is a workaround for this, i must think about this more, but firstly i need to know how Japanese artist names are formatted in <artist> tag, i.e. are they separated by comma, or by comma followed by space, or by semicolon, etc.?

They are multiple artist entries, but in the Display Artist they are separated by a semicolon:
ex. : displayArtist="My Artist [JAPANESE]; My Other Artist [OTHER JAPANESE]"
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 28, 2023, 11:58:29 PM
There used to be a preset titled along the lines of “Copy tag 1 to tag 2 if tag 1 isn’t empty”. I haven’t been able to find it anywhere for a while now but it used to be in the list of presets supplied with the plugin. Do you still have this preset anywhere?

sorry, i'm not aware of such preset. dedicated "copy tag" command (not ASR preset) has the option "copy only if destination tag is empty", but it's not what you are looking for.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 29, 2023, 12:19:11 AM
They are multiple artist entries, but in the Display Artist they are separated by a semicolon:
ex. : displayArtist="My Artist [JAPANESE]; My Other Artist [OTHER JAPANESE]"

no, there is no solution for multiple entries per tag right now. but you gave me an idea how i can improve LR (also, to take into account your case). though, not sure when i make this improvement.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on July 29, 2023, 01:30:46 AM
new beta seems to be stable, but it would be great if somebody else has tested it. all changes relate to 5 things:

1. "copy tags to clipboard" window is now used not only for copying tags to clipboard, but also to simply select tags from some other commands (ASR, tag history, compare tracks). this window will look slightly different depending on context.

2. ASR support for <ALL TAGS> pseudo-tag is completed. preset support for this pseudo-tag must be enabled in preset editor 1st, i.e. this support can be added either to new user presets, or to user copies of predefined presets. either all tags, or only specified tags, or all tags except for the list of preserved tags will be processed, when using <ALL TAGS>.

3. now, LR presets can use another LR preset as the source of track list. of course, this makes sense only if the source preset uses conditional filtering (option "export/save tags only if..."). report itself generated by source preset is not used in this case, only filtered track list is used - all tracks (maybe even not displayed in source preset report), which satisfy source preset condition.

* LR presets can be chained to take advantage of multiple conditions.  

4. LR preset report preview can be interactively filtered, according to specified condition, by clicking "Filter" button.

5. plugin settings are extended. simplified quick settings can be opened from some commands.

(https://i.imgur.com/nChstQe.png)

(https://i.imgur.com/fkJ0Nnp.png)

(https://i.imgur.com/64ln5VQ.png)

--------------------------------------------------------

if somebody has ideas, for which ASR presets it might be useful to allow using <ALL TAGS> (along with generic tags, and considering possible restrictions to what to treat as "all tags"), post your suggestions!

download link:
https://www.mediafire.com/file/ycdl10fo8cgfwns/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: calderino on July 29, 2023, 03:27:12 AM
They are multiple artist entries, but in the Display Artist they are separated by a semicolon:
ex. : displayArtist="My Artist [JAPANESE]; My Other Artist [OTHER JAPANESE]"

no, there is no solution for multiple entries per tag right now. but you gave me an idea how i can improve LR (also, to take into account your case). though, not sure when i make this improvement.

Thanks, no worries, it's not like it's urgent  ;)
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on July 29, 2023, 04:45:24 PM
I want to know if this is possible to do with the plugin:

I have my Japanese artist defined as "Translated Name [Original Name]", for example "Hashimoto Yukari [橋本 由香利]".
I want to find typos in the artist names by comparing the Japanese part of the tag and then comparing the English part.
In the short time that I've been here, I have witnessed little to no requests that this plugin has failed to deliver a solution to.
I have yet to truly explore it in depth, but I've already seen enough to know it's an absolute gem.
Nevertheless, I went looking around for a solution within MusicBee's native features - simply because Steven is that amazing too :-)

Define the following virtual tags:

Japanese Artist   ---------   ​$RxReplace($RxMatch(<Artists>,"[^;]*\[.*\]"),"^\s","")
Translation           ---------   $RxReplace(<Japanese Artist>,"(.*?)\s\[.*?\](;\s)?","$1$2")
Original                 ---------   $RxReplace(<Japanese Artist>,".*?\[(.*?)\](;\s)?","$1$2")

Enable the Column Browser in View > Arrange Panels... like so:

(https://i.imgur.com/u6Mggh9.png)

Then whenever you click on a Japanese name in the Original column, MusicBee will filter all the corresponding different Translations.
And as far as my testing goes, the regular expressions in those virtual tags do take into account multiple artist entries.
Title: Re: Additional Tagging & Reporting Tools
Post by: northernlights on August 09, 2023, 05:07:10 PM
I'm using the plugins library report for adding some kind of calculated "album score" to a custom tag of each track belonging to the same album.

Given that, I would like to rank all albums depending on their "album score" and save this rank to a virtual/custom tag. The only way (I can think of so far) to achieve this in MusicBee seems to be $LR(<URL>,function_id) virtual function which is pretty cool already.  

Therefore I propose adding a ranking feature to "Function for new fields" that is able to rank an attribute based on all selected tracks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 10, 2023, 04:44:17 AM
I apologize, but I have no idea what an "album score" is or exactly how the "rank" function should work. should it be sum(album score) or average(album score)? and how it must be different from already available functions?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 12, 2023, 04:59:06 AM
New beta, which seems to be stable, but I don't want to upload it as a stable release yet:

https://www.mediafire.com/file/ycdl10fo8cgfwns/mb_TagTools_beta.zip/file

---------------------

new features:

1. The LR UI is rewritten.

2. LR now supports multiple item splitters for grouping tags. For example, you can define splitter ; for "artist" or "'genre" tags to split multiple artists or genres.

(https://i.imgur.com/rkBPFqn.png)

3. if several tags are split (i.e. several tags for one track may have several values) then all possible combinations of split values for every tag will be included in LR report.

(https://i.imgur.com/fJfXoeC.png)

4. LR now supports virtual tag expressions (any expressions valid for virtual tags). you can refer to any tag in an LR expression using the MB generic <tag name>  construction or refer to the current grouping/function tag (which can already be split tag value, if splitter is defined for this tag) as \@.

LR expressions are mostly intended to be used for regexes, though they are not limited to them. expressions can save you virtual tags if you need some expressions to be used in LR only, but the main purpose of LR expressions is to use them together with multiple item splitters for grouping tags.

if 2 virtual tags are split into multiple values (e.g., separated by ; ) for a given track, then all combinations of these values will be included in the LR report. contrary to this, several expressions of one split grouping tag for a given track produce a single combination for every split tag value.

(https://i.imgur.com/5Yrzki0.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: endelos on August 12, 2023, 02:07:42 PM
Hello, the new version seems really nice, but I couldn't use it with my old ASR presets.

They are xml files (exported with version 5.2.7391). When I try to import them in the very last version, a message prompts that the format is not correct. Do you know why ? Maybe I can edit the xml files and change a few things so it recognizes them ?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 12, 2023, 04:38:32 PM
it happens because asr preset format was changed some time ago. ASR had been converting the old format to the new one since then, but i've completely removed the conversion code a month ago.

all you can do now is manually recreate your ASR presets (actually, you can see all important information from old presets if you open them in any text editor, as they are xml files, i.e., text files).

------------

P.S. LR is now using a new preset format as well. it's converting old presets to new format at the moment, but i'll remove the conversion code too in a few months.
Title: Re: Additional Tagging & Reporting Tools
Post by: endelos on August 12, 2023, 06:21:34 PM
I see ! I've got something like 15 presets... well, you would not happen to have a version of the tool with this conversion code in your archives ? That would save me time ! Otherwise, I'm good to manually recreate them.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 12, 2023, 08:36:59 PM
i'm not sure which version i've kept supports both old and new asr preset formats, but you could try these versions:

https://www.mediafire.com/file/jv6zni7mceena0a/mb_TagTools_2022-06-08.zip/file

https://www.mediafire.com/file/2zcdwmoaphffbtc/mb_TagTools_2023-01-06.zip/file

------------------

check if presets are converted to a new format by exporting one of them. The exported new format preset must have the file extension ".asr-preset.xml", not ".ASR Preset.xml".
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 12, 2023, 08:48:40 PM
updated beta version. now LR preview table text is left- or right-aligned according to column data type (date/time/numbers are right-aligned; other data types, which are all considered by LR as strings, are left-aligned). alignment is not applicable to artworks, they always occupy entire cells.

https://www.mediafire.com/file/ycdl10fo8cgfwns/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: endelos on August 14, 2023, 10:43:36 AM
i'm not sure which version i've kept supports both old and new asr preset formats, but you could try these versions:

https://www.mediafire.com/file/jv6zni7mceena0a/mb_TagTools_2022-06-08.zip/file

https://www.mediafire.com/file/2zcdwmoaphffbtc/mb_TagTools_2023-01-06.zip/file

------------------

check if presets are converted to a new format by exporting one of them. The exported new format preset must have the file extension ".asr-preset.xml", not ".ASR Preset.xml".

Oh thanks !
The first one is still generating the old  ".ASR Preset.xml", but I can't manage to make the second one work. It appears in the plugins window, but I can't access to any of the tools...
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 15, 2023, 04:06:44 AM
forgot to warn you: don't install several versions of the plugin simultaneously. but if the first version (2022-06-08?) is still generating the old format, then it doesn't matter.

i'll try to find some old source code, but i'm not sure if i have the one that supports both old and new formats.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 15, 2023, 04:17:07 AM
this version should auto-convert old ASR presets to new ones:

https://www.mediafire.com/file/cwwtzg1bmy532j6/mb_TagTools_2023-06-26.zip/file

no need to export converted presets. if only to check that they are converted to a new format or for backup purposes.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 16, 2023, 09:43:36 AM
new beta, i hope this is the last beta for the 7.0 version:

1. various bug fixes
2. new option in settings window which allows choosing to either minimize or hide plugin windows on clicking "minimize" title bar button

https://www.mediafire.com/file/ycdl10fo8cgfwns/mb_TagTools_beta.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on August 17, 2023, 08:39:02 AM
7.0 version released:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: sn0nam3 on September 10, 2023, 10:31:57 PM
I am having issues with crashing when trying to do a Multiple Search & Replace. No matter if I pick all or a few files it crashes MusicBee doing a Preview.
So I have to Configure the plugin each time I launch MusicBee and some of the files appear to be duplicated in AppData but I have installed to Program files and gave modify permissions to all users but the issue has persisted. I have just installed the latest version to try that as well. Any help would be appreciated.
Also I have to hit Configure and OK on the plugin each time I launch MusicBee. It does not have any menu options until I do that if that might be related.

MusicBee v3.4.8033.18564D  (Win10.0), 10 Sep 2023 17:29:

System.ArgumentNullException: Value cannot be null.
Parameter name: TimerCallback
   at System.Threading.Timer.TimerSetup(TimerCallback callback, Object state, UInt32 dueTime, UInt32 period, StackCrawlMark& stackMark)
   at System.Threading.Timer..ctor(TimerCallback callback, Object state, Int32 dueTime, Int32 period)
   at MusicBeePlugin.Plugin.SetStatusbarText(String newMessage, Boolean autoClear)
   at MusicBeePlugin.Plugin.SetResultingSbText(String finalStatus, Boolean autoClear, Boolean sbSetFilesAsItems)
   at MusicBeePlugin.MultipleSearchAndReplaceCommand.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 & Reporting Tools
Post by: phred on September 10, 2023, 10:45:54 PM
The latest versions of this plugin require MB v3.5+. The error log shows that you're using v3.4.

Update to the latest 3.5 from the link in my signature below and report back.
Title: Re: Additional Tagging & Reporting Tools
Post by: sn0nam3 on September 12, 2023, 03:48:18 AM
Thank you. I didn't even realize I wasn't updating MB with Chocolatey so I haven't even checked or tried to update it. doh. Everything is working fine now. I gave you a heart in the add-on store. I use several features regularly. Thanks for all the hard work.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on September 12, 2023, 11:59:15 AM
this version should auto-convert old ASR presets to new ones:

https://www.mediafire.com/file/cwwtzg1bmy532j6/mb_TagTools_2023-06-26.zip/file

no need to export converted presets. if only to check that they are converted to a new format or for backup purposes.
Hi.
The ASR format switch caught me off guard as well when updating just now. Thanks a lot for the version that also converts!

But - How do you check for converted presets ? I see 
\Plugins\ASR Presets
which holds 221 xmls (with alphanumerical cryptic names). But, there's nothing I can identify as converted presets as such...?

And, when updatign to the new v7 - I can then delete the olden xmls (when it has been sucesfully converted to elsewhere ? and then v7 should just need those new ones...)

Cheers.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on September 13, 2023, 10:33:31 AM
Oh, another gotcha I encountered as an FYI - I had all 10 available hotkey slots filled with ASR user presets to fire off via hotkey. After the update (first to v7, then to the conversion-capable last version Boroda posted) these were gone from the hotkey editor.
But, looks like there's functional changes to hotkey assignment in ADDITIONAL TAGGING & REPORTING TOOLS anbd we have 20 ASR hotkey slots to fill now, which is great as I used all 10 before. Just a heads up that if you update, you will need to re-assign your ASR hotkeys most likely as well.
Churs.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 13, 2023, 07:51:56 PM
But - How do you check for converted presets ? I see  
\Plugins\ASR Presets
which holds 221 xmls (with alphanumerical cryptic names). But, there's nothing I can identify as converted presets as such...?

you can simply check the double-extension of any preset (because they all will have the same extension): new format presets must have the extension ".asr-preset.xml" (old format presets have the extension ".ASR Preset.xml").

...we have 20 ASR hotkey slots to fill now, which is great as I used all 10 before. Just a heads up that if you update, you will need to re-assign your ASR hotkeys most likely as well.

Strictly speaking, it's not true (in the case of sequential plugin version updates). usually, presets must be correctly auto-updated, and all assigned hotkeys must be kept.

yes, i agree that removing support for old preset formats (either ASR or LR) can be very uncomfortable, but i was trying to keep the old structures required for old format presets and the auto-conversion code as long as i could.
Title: Re: Additional Tagging & Reporting Tools
Post by: alec.tron on September 13, 2023, 09:10:23 PM
you can simply check the double-extension of any preset (because they all will have the same extension): new format presets must have the extension ".asr-preset.xml" (old format presets have the extension ".ASR Preset.xml").
Thanks for the insight! And the awesome component of yours of course!

...we have 20 ASR hotkey slots to fill now, which is great as I used all 10 before. Just a heads up that if you update, you will need to re-assign your ASR hotkeys most likely as well.

Strictly speaking, it's not true (in the case of sequential plugin version updates). usually, presets must be correctly auto-updated, and all assigned hotkeys must be kept.

yes, i agree that removing support for old preset formats (either ASR or LR) can be very uncomfortable, but i was trying to keep the old structures required for old format presets and the auto-conversion code as long as i could.
I assume I lost the hotkey presets as I updated to v7, which then had no presets at all (without the conversion-abillity), triggering an edge case with user asr tied to hotkeys (but who knows - the only observation I'd have was that the MB hotkey editor complained, when re-assigning the presets, that a given hotkey I had previouslty assigned, MB warned me that this is already set to "*" [iirc] hinting at a "ghost" hotkey of the previous ASR hotkey... [as the hotkey editor wasn't listing them anymore when there were no presets with v7 - they did re-appear once I re-assigned them as hotkey-able in ASR in the conversion capable version of the tools]).

But no worries - was easy to set up again - and, this is your component after all, and if you deem it beneficial to update something it will surely be ;)

Churs.
c.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 14, 2023, 05:18:12 AM
i've fixed a bug when any user interaction was required on plugin startup to see the values of virtual tags that use plugin functions. now, all virtual tags are available immediately after plugin initialization:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: austral on September 15, 2023, 01:40:46 PM
Hello,

Would it be possible to add an enhancement to $Char() function to repeat n times the specified character?
Something like $Char(2028;32)  <-- in this example it would put 32 "zero witdh characters" aka "invisible characters", etc..
This function would be really useful for people building custom sort order groupings in virtual tag formulas.

example
(https://i.postimg.cc/wjFYHkCv/Screenshot-15-Sep-23-14-52-03.png)

Cheers
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 15, 2023, 07:47:45 PM
no problem:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

use $CharSequence(hexadicemal_char_code,decimal_number_of_times)

also, i've extended ASR \@char[[]] function to accept (optional, decimal too) second parameter.
Title: Re: Additional Tagging & Reporting Tools
Post by: austral on September 15, 2023, 08:31:09 PM
thank you very much boroda!  :)
i just tested it with 32 nested $if and works perfectly.

example using the new function (https://getmusicbee.com/forum/index.php?topic=39920.msg216000#msg216000)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 16, 2023, 07:12:17 AM
glad to help

i saw your huge formula and guessed the most common application of this function. so, maybe it's worth to rename it to something more short until it's too late? e.g. $CharSeq() or $CharN()?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on September 16, 2023, 07:40:50 AM
maybe it's worth to rename it to something more short until it's too late? e.g. $CharSeq() or $CharN()?
$CharN() seems good. Or maybe $CharRep()
(for repeat, repetition)
Title: Re: Additional Tagging & Reporting Tools
Post by: austral on September 16, 2023, 07:58:46 AM
glad to help
i saw your huge formula and guessed the most common application of this function. so, maybe it's worth to rename it to something more short until it's too late? e.g. $CharSeq() or $CharN()?

That would be nice, the shortest the better!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on September 16, 2023, 08:38:51 AM
i've renamed it to $CharN(code,times)

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

hiccup, could you update your topic on the "tips & tricks" board and give a short description of the main purpose of this function (that it's strictly a service function)?
Title: Re: Additional Tagging & Reporting Tools
Post by: austral on September 16, 2023, 09:00:34 AM
i've renamed it to $CharN(code,times)

Thanks again boroda! i also updated my post with the example code.

This is how the formulas compare each other in Notepad++. With $CharN it will be much easier to explain the process to users interested in custom sort order groupings. Also the benefits to see the exact position of each grouping or be able to modify the formula directly inside MusicBee.

(https://i.postimg.cc/C5yg9fYh/Screenshot-16-Sep-23-09-52-53.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on September 17, 2023, 06:22:18 PM
hiccup, could you update your topic on the "tips & tricks" board and give a short description of the main purpose of this function (that it's strictly a service function)?
Thanks for adding this function.
I will update that Tips&Tricks topic, but modifying it requires some courage (its BB-code is quite a minefield), and I would also want to create a brief but clear example of its use, which I haven't figured out yet.
I'm going to do it, but not today ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on September 23, 2023, 09:10:45 PM
Hi,

I’m certain I recall a ASR preset that only copied tags from <Tag 1> to <Tag 2> if <Tag 1> wasn’t empty. Is there any possibility of this being added to the preset bundle?

Cheers!!
Title: Re: Additional Tagging & Reporting Tools
Post by: TheRealDavid on October 03, 2023, 10:07:07 PM
Would it be possible to amend one or both existing $TagContains functions to accept a partial/exact parameter? This would allow users to find exact-string matches instead of only partial-string matches.

As a simplified example of what I mean, the current behavior is for $TagContainsAnyString(<URL>,Genre,Pop|Rock) to return T for the exact matches of Pop and Rock in the Genre tag. It also returns T for partial matches like Synthpop, Hard Rock, etc.

What I am asking for would look more like $TagContainsAnyString(<URL>,Genre,Pop|Rock,1). By entering a "1" for the parameter identifies that I only want to return T if the Genre tag is exactly Pop or exactly Rock. Everything else, including partial matches would return F. Alternately, using a "0" (default value) for the parameter would result in the existing behavior.

Reverse-compatibility would probably require the assumption of the default value whenever the parameter is totally excluded. Effectively, $TagContainsAnyString(<URL>,Genre,Pop|Rock) and $TagContainsAnyString(<URL>,Genre,Pop|Rock,0) would both work in exactly the same way that the existing function currently works.

Lastly, I recognize that there are multiple workarounds that would probably achieve the same result. The problem is that those workarounds all become pretty cumbersome if you want exact matches for more than just a few strings. The requested update would scale up much more easily.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on October 07, 2023, 01:18:43 AM
As per post here:
Steven or  boroda,
Code
MusicBee v3.5.8669.34304P  (Win10.0), 6 Oct 2023 18:06:

System.Runtime.InteropServices.COMException (0x800401D0): OpenClipboard Failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN))
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Windows.Clipboard.Flush()
   at System.Windows.Clipboard.CriticalSetDataObject(Object data, Boolean copy)
   at System.Windows.Clipboard.SetDataInternal(String format, Object data)
   at System.Windows.Clipboard.SetText(String text, TextDataFormat format)
   at System.Windows.Clipboard.SetText(String text)
   at MusicBeePlugin.CopyTagsToClipboardCommand.CopyTagsToClipboard(Int32 tagSet)
   at MusicBeePlugin.CopyTagsToClipboardCommand.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)

Not sure if this exception is from MusicBee api or from ATRT plugin.

My understanding is that
Code
Clipboard.SetText(data);
should be replaced by
Code
Clipboard.SetDataObject(data);
to stop this issue.

Hope I'm correct and  that helps.

This occurs when using 'Copy Tags to Clipboard'
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on October 10, 2023, 07:02:10 AM
Used a couple of old mb_TagTools.dll's that I had.
5.5.8403 is the last one I have that 'Copy Tags to Clipboard' doesn't throw an error.
5.8.8577 and newer all throw an error.
Title: Re: Additional Tagging & Reporting Tools
Post by: The Incredible Boom Boom on October 14, 2023, 03:33:40 PM
@boroda, do you happen to keep a changelog from each version of AT&T?
I am going to be jumping from v5.7.8442.39379 to the latest (once the Copy Tags to Clipboard issue is sorted out) and I'm a bit overwhelmed by the number of additions that have been made since then.
Even if it's in Russian, I'll use Google Translate to interpret it and reference any questions I have here.
Title: Re: Additional Tagging & Reporting Tools
Post by: Buchas on October 19, 2023, 06:11:21 PM
Hey,
I have just downloaded mb_TagTools_latest.zip from https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
and I have read the description that "See the "README FIRST!" file inside this folder for instructions on adding/updating/removing the plugin."
However I do not see such a file in an archive. :(
How do I install the plugin?

I have tried to add it using MusicBee's "Add plugin" button in preferences, now I see a new configuration window. However menu entry "Tools -> Additional Tagging & Reporting Tools" does not work - nothing happens when I click it.
What am I missing?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 19, 2023, 09:09:51 PM
@Boroda

It seems like some arithmetic functions that previously were only available when using your plugin are now by default available in MusicBee.
(if there have been announcements about that I must have missed them)

E.g. $gt now works out-of-the-box.
Could you perhaps take a look at the functions overview here:
https://getmusicbee.com/forum/index.php?topic=35868.msg196257#msg196257
and let me know for which functions I can remove the blue asterisk?


Never mind, I now see that while $gt is producing output without AT&RT installed (output that happened to be correct when I was testing this), it is not actually functioning.
Title: Re: Additional Tagging & Reporting Tools
Post by: Buchas on October 20, 2023, 09:57:54 AM
It appears I had to upgrade MusicBee to the last version (3.5) (I had 3.4) to get menu "Tools -> Additional Tagging & Reporting Tools" working.
Now however I cannot figure out how to use the "Library Reports". I open it, select "LIBRARY TOTALS", click "Preview" and nothing happens.
A progress bar would be nice if the tool is doing something.
Title: Re: Additional Tagging & Reporting Tools
Post by: rak on October 21, 2023, 07:08:17 PM
In "Additional Reporting and Tagging Tools / Library Reports," no matter which HTML "Format" I choose for export, it always exports to csv.  What might I be doing wrong, or is this an issue others have experienced?  Thanks.

2023-12-17 update:  No responses here.  This problem still exists.  Anyone else have this problem?  Solution?  Many thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on October 28, 2023, 05:21:09 AM
Hi Boroda,

I was wondering if The ASR preset “sort performers by their roles”, could be used for sorting the involved people list tag? So the people can be sorted by their respective roles. Unless it’s a fairly simple alteration to the existing preset that I’m not seeing?

Regards
Dizza
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 01:48:52 AM
I’m certain I recall a ASR preset that only copied tags from <Tag 1> to <Tag 2> if <Tag 1> wasn’t empty. Is there any possibility of this being added to the preset bundle?
i don't recall such preset and can't imagine how it could be implemented.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 01:54:05 AM
Would it be possible to amend one or both existing $TagContains functions to accept a partial/exact parameter? This would allow users to find exact-string matches instead of only partial-string matches.

As a simplified example of what I mean, the current behavior is for $TagContainsAnyString(<URL>,Genre,Pop|Rock) to return T for the exact matches of Pop and Rock in the Genre tag. It also returns T for partial matches like Synthpop, Hard Rock, etc.

but how "exact strings" must be separated? what can be delimiter? only spaces? semicolons? Something else?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 02:00:04 AM
As per post here:
Steven or  boroda,
Code
MusicBee v3.5.8669.34304P  (Win10.0), 6 Oct 2023 18:06:

System.Runtime.InteropServices.COMException (0x800401D0): OpenClipboard Failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN))
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Windows.Clipboard.Flush()
   at System.Windows.Clipboard.CriticalSetDataObject(Object data, Boolean copy)
   at System.Windows.Clipboard.SetDataInternal(String format, Object data)
   at System.Windows.Clipboard.SetText(String text, TextDataFormat format)
   at System.Windows.Clipboard.SetText(String text)
   at MusicBeePlugin.CopyTagsToClipboardCommand.CopyTagsToClipboard(Int32 tagSet)
   at MusicBeePlugin.CopyTagsToClipboardCommand.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)

Not sure if this exception is from MusicBee api or from ATRT plugin.

My understanding is that
Code
Clipboard.SetText(data);
should be replaced by
Code
Clipboard.SetDataObject(data);
to stop this issue.

Hope I'm correct and  that helps.

This occurs when using 'Copy Tags to Clipboard'

Used a couple of old mb_TagTools.dll's that I had.
5.5.8403 is the last one I have that 'Copy Tags to Clipboard' doesn't throw an error.
5.8.8577 and newer all throw an error.

earlier plugin versions used win32 ClipboardSetText() function, but this led to tiny memory leaks. Later, i've changed it to .net function, which is working fine on my pc. but if this causes problems, I could revert to old implementation.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 02:01:47 AM
@boroda, do you happen to keep a changelog from each version of AT&T?
I am going to be jumping from v5.7.8442.39379 to the latest (once the Copy Tags to Clipboard issue is sorted out) and I'm a bit overwhelmed by the number of additions that have been made since then.
Even if it's in Russian, I'll use Google Translate to interpret it and reference any questions I have here.

no, only remarks about every release on this topic, but it's not so easy to track them here.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 02:04:54 AM
Hey,
I have just downloaded mb_TagTools_latest.zip from https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
and I have read the description that "See the "README FIRST!" file inside this folder for instructions on adding/updating/removing the plugin."
However I do not see such a file in an archive. :(
How do I install the plugin?

I have tried to add it using MusicBee's "Add plugin" button in preferences, now I see a new configuration window. However menu entry "Tools -> Additional Tagging & Reporting Tools" does not work - nothing happens when I click it.
What am I missing?

download full plugin archive from add-ons section of main site: Additional-Tagging-Tools-Plugin.zip.

simplified mb_TagTools_latest.zip is for experienced users.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 02:07:55 AM
It appears I had to upgrade MusicBee to the last version (3.5) (I had 3.4) to get menu "Tools -> Additional Tagging & Reporting Tools" working.
Now however I cannot figure out how to use the "Library Reports". I open it, select "LIBRARY TOTALS", click "Preview" and nothing happens.
A progress bar would be nice if the tool is doing something.

most likely you need mb latest patch from here: https://getmusicbee.com/patches/
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 02:11:17 AM
In "Additional Reporting and Tagging Tools / Library Reports," no matter which HTML "Format" I choose for export, it always exports to csv.  What might I be doing wrong, or is this an issue others have experienced?  Thanks.

in the last plugin versions, you must choose the exported format before clicking the 'export' button (above this button).
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 03:24:14 AM
As per post here:
Steven or  boroda,
Code
MusicBee v3.5.8669.34304P  (Win10.0), 6 Oct 2023 18:06:

System.Runtime.InteropServices.COMException (0x800401D0): OpenClipboard Failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN))
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Windows.Clipboard.Flush()
   at System.Windows.Clipboard.CriticalSetDataObject(Object data, Boolean copy)
   at System.Windows.Clipboard.SetDataInternal(String format, Object data)
   at System.Windows.Clipboard.SetText(String text, TextDataFormat format)
   at System.Windows.Clipboard.SetText(String text)
   at MusicBeePlugin.CopyTagsToClipboardCommand.CopyTagsToClipboard(Int32 tagSet)
   at MusicBeePlugin.CopyTagsToClipboardCommand.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)

Not sure if this exception is from MusicBee api or from ATRT plugin.

My understanding is that
Code
Clipboard.SetText(data);
should be replaced by
Code
Clipboard.SetDataObject(data);
to stop this issue.

Hope I'm correct and  that helps.

This occurs when using 'Copy Tags to Clipboard'

Used a couple of old mb_TagTools.dll's that I had.
5.5.8403 is the last one I have that 'Copy Tags to Clipboard' doesn't throw an error.
5.8.8577 and newer all throw an error.

earlier plugin versions used win32 ClipboardSetText() function, but this led to tiny memory leaks. Later, i've changed it to .net function, which is working fine on my pc. but if this causes problems, I could revert to old implementation.

try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 05:43:49 AM
redownload the latest version. there was a bug in .net function implementation, so that version may or may not work for you depending on the .net version.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 29, 2023, 07:45:26 AM
Is there a chance the 'use MusicBee skin colours' implementation could be improved a bit so that it works well for dark skins?

(https://i.imgur.com/PEULVQNm.jpg) (https://i.imgur.com/PEULVQN.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 29, 2023, 09:01:38 AM
I’m certain I recall a ASR preset that only copied tags from <Tag 1> to <Tag 2> if <Tag 1> wasn’t empty. Is there any possibility of this being added to the preset bundle?
i don't recall such preset and can't imagine how it could be implemented.
Wouldn't it be a solution to create a virtual tag that outputs <Tag 1> and <Tag 2> combined:

virtual tag
Copy tag 1 to tag 2

formula
$IsNull(<Tag 1>,$IsNull(<Tag 2>,,<Tag 2>),$IsNull(<Tag 2>,<Tag 1>,<Tag 1>"; "<Tag 2>))

and then have Advanced Search & Replace write that virtual tag to <Tag 2>?

(https://i.imgur.com/Vh2wFnm.png)

edit:
In case you don't want to add the value of Tag 1 to Tag 2, but replace Tag 2 with Tag 1 (if not empty), use this virtual tag:

formula
$IsNull(<Tag 1>,$IsNull(<Tag 2>,,<Tag 2>),<Tag 1>)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 09:12:53 AM
Is there a chance the 'use MusicBee skin colours' implementation could be improved a bit so that it works well for dark skins?

(https://i.imgur.com/PEULVQNm.jpg) (https://i.imgur.com/PEULVQN.png)

it's already the best i've succeeded in doing. much better than it was initially. maybe i can make disabled text less dark. do you think it helps?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on October 29, 2023, 09:23:32 AM
I’m certain I recall a ASR preset that only copied tags from <Tag 1> to <Tag 2> if <Tag 1> wasn’t empty. Is there any possibility of this being added to the preset bundle?
i don't recall such preset and can't imagine how it could be implemented.
Wouldn't it be a solution to create a virtual tag that outputs <Tag 1> and <Tag 2> combined:

virtual tag
Copy tag 1 to tag 2

formula
$If(<Tag 1>="",,$If(<Tag 2>="",,<Tag 1>"; "<Tag 2))

and then have Advanced Search & Replace write that virtual tag to <Tag 2>?

(https://i.imgur.com/Vh2wFnm.png)

you are right! i forgot that ASR supports VT expressions. but this already doesn't matter. i've added 1 new option to the dedicated 'copy tag' command to preserve non-empty destination tags, and 2 new options to ASR (1 three-state checkbox for every ASR step). copy 'copy tag' preset and adjust required "(?)" option (read tooltip over checkbox).

(https://i.imgur.com/fS95rWr.png)

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 29, 2023, 09:27:23 AM
it's already the best i've succeeded in doing. much better than it was initially. maybe i can make disabled text less dark. do you think it helps?
Absolutely. My concern is mostly about (un)readability.
The fact that some elements/bars are much whiter then they ideally would be is far less important.

And perhaps take a look at the two icons 'Clear search text' and "Open quick settings'?
They are also very difficult to discern.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 29, 2023, 09:51:17 AM
copy 'copy tag' preset and adjust required "(?)" option (read tooltip over checkbox).
(https://i.imgur.com/KiwB1gD.png)

Shouldn't the checkbox tooltip be a position lower, at 'Replace with:' instead of at 'Search for:'?
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 29, 2023, 10:05:23 AM
you are right! i forgot that ASR supports VT expressions. but this already doesn't matter. i've added 1 new option to the dedicated 'copy tag' command to preserve non-empty destination tags, and 2 new options to ASR…
Dizza17 must be pleased, going from zero options to two options within 30 minutes ;-)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on October 29, 2023, 02:29:08 PM
A request @boroda:

In the past AT&RT had a $log function, but I believe you removed it because you thought it was not used by anyone, and couldn't remember why it was implemented in the first place.

But...
I am currently trying to create a virtual tag that needs the ability to convert the decimal track peak value to dB's, and I found that that needs a logarithmic function.
(I believe it is specified as 'base 10' in this case)

See here to get some idea about what I am trying to do:
https://getmusicbee.com/forum/index.php?topic=40141.msg217380#msg217380

PS
I think I can now also recall why $log was implemented in the first place. I believe it had to do with a similar challenge regarding converting apples soundcheck to ReplayGain values?

Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on October 30, 2023, 12:08:37 AM
Absolutely wrapped guys!! Appreciate you both taking time to look at this for me. I am sincerely grateful for all the work you put into this forum.
Title: Re: Additional Tagging & Reporting Tools
Post by: Buchas on October 31, 2023, 02:52:13 PM
It appears I had to upgrade MusicBee to the last version (3.5) (I had 3.4) to get menu "Tools -> Additional Tagging & Reporting Tools" working.
Now however I cannot figure out how to use the "Library Reports". I open it, select "LIBRARY TOTALS", click "Preview" and nothing happens.
A progress bar would be nice if the tool is doing something.

most likely you need mb latest patch from here: https://getmusicbee.com/patches/

I have installed Additional-Tagging-Tools-Plugin.zip and patch " MusicBee35_Patched.zip 2023-10-30 08:38 3.0M ", but the problem remains: "Preview" or "Proceed" doesn't do anything in Library reports. I mean I click "Preview", some fields gets disabled, button changes to "Stop", but report does not appear at the bottom table.
(https://i.ibb.co/8X9PnKp/librep.png)

EDIT - Ahh it worked while I was typing a forum message!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 01, 2023, 04:56:48 AM
A request @boroda:

In the past AT&RT had a $log function, but I believe you removed it because you thought it was not used by anyone, and couldn't remember why it was implemented in the first place.

But...
I am currently trying to create a virtual tag that needs the ability to convert the decimal track peak value to dB's, and I found that that needs a logarithmic function.
(I believe it is specified as 'base 10' in this case)

it's done for the next update (i'm now fixing both skinned and not-skinned coloring and some other UI issues):

use Lg(number)

it's a decimal logarithm (natural logarithms are used mostly in mathematics and theoretical physics).
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 01, 2023, 07:30:58 AM
As per post here:

This occurs when using 'Copy Tags to Clipboard'

Used a couple of old mb_TagTools.dll's that I had.
5.5.8403 is the last one I have that 'Copy Tags to Clipboard' doesn't throw an error.
5.8.8577 and newer all throw an error.

earlier plugin versions used win32 ClipboardSetText() function, but this led to tiny memory leaks. Later, i've changed it to .net function, which is working fine on my pc. but if this causes problems, I could revert to old implementation.

try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Using Version: 7.1.8702.19923 and all is fine.
Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: TheRealDavid on November 01, 2023, 10:28:59 PM
Would it be possible to amend one or both existing $TagContains functions to accept a partial/exact parameter? This would allow users to find exact-string matches instead of only partial-string matches.

As a simplified example of what I mean, the current behavior is for $TagContainsAnyString(<URL>,Genre,Pop|Rock) to return T for the exact matches of Pop and Rock in the Genre tag. It also returns T for partial matches like Synthpop, Hard Rock, etc.

but how "exact strings" must be separated? what can be delimiter? only spaces? semicolons? Something else?

I don't know how difficult making these changes would be, so I have 2 ideas for how to resolve this. Both ideas would provide the "exact matches" I'm looking for, but one of these might be easier to code or more stable than the other.

Idea 1: Update the existing function. 
Maybe exact matches could use quotes within the existing format. Adjusting my prior example: $TagContainsAnyString(<URL>,Genre,"Pop"|Rock) would return T for an exact match of Pop (quotes = exact match) and partial matches for Rock (no quotes = partial match, current behavior). 

Idea 2: Create a new function.
Maybe the function could be cloned to create something like $TagMatchesAnyString. The new Matches variation could then be coded to ONLY return exact matches, while the existing Contains variation would continue to return partial matches.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 02, 2023, 01:58:03 AM
it's all obvious.

i mean, what must be treated as a "complete" or "separate" string inside a tag? depending on a tag, what of this is a "separate" or "complete" string "Pop" (all these are abstract examples)?

Pop;Synthpop
Pop,Synthpop
Pop:Synthpop
Pop+Synthpop
Pop-Synthpop
Pop/Synthpop
Pop(Synthpop)

or do you mean that only spaces must be treated as a string separator?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 02, 2023, 12:30:51 PM
new version available. i've done all i could to improve skinning support. i consider this version to be beta because i have tested it with a few skins only (functionality has not changed at all except for the new function $Lg(number)):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 02, 2023, 07:40:20 PM
new version available. i've done all i could to improve skinning support. i consider this version to be beta because i have tested it with a few skins only
Thanks for all your troubles with this.
It's a shame that this is something that is so difficult to do.
Couldn't Steven help out with some tips, or maybe improvements?

It's a little bit better, but still not great.
(https://i.imgur.com/UlqbWev.png)

1. is now black and almost unreadable (was light and readable before)

2. is probably using some low contrast 'disabled' element? Also very difficult to read.
    But that has also always been an issue with most dark skins in MusicBee.
    When creating bitmap skins there is an element available that can boost the contrast so that things look good.
    But something like that is probably not available for these kind of plugin skinning?

3. and the active buttons: still good


Quote
(functionality has not changed at all except for the new function $Lg(number)):
Great, thank you!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 03, 2023, 04:23:56 AM
thanks for the comments. The plugin now generates all colors itself (of course, they are derived from skin colors anyway).

1. i'll compare old and new code to see what has changed. maybe it's just a mistake.

2. it's disabled text. Earlier, this color was dim and dark, now it's light dim and light (it's for dark skins). how do you think disabled text must look? some mockup?

3. this hasn't been changed at all. because "and the active buttons: still good" (but this is not a button, it's label).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 03, 2023, 08:17:45 AM
2. it's disabled text. Earlier, this color was dim and dark, now it's light dim and light (it's for dark skins). how do you think disabled text must look? some mockup?
See the difference between the two 'disabled' lines in the skin, and the 'disabled' elements in the plugin:

(https://i.imgur.com/H4IwJGb.png)

(https://i.imgur.com/ZfSDT4R.png)

But as I said, it could be because the skin is using the 'contrastboost' element to improve on the contrast of these elements.

Just as a general comment on the concept of 'disabled':
I think there are (should be) two versions of it.
1. for elements/functions that are currently disabled, but you may want to enable. So you will need to be able to read that text.
2. for elements that are currently not functioning, but also provide no useful information. Such as 'back' and 'forward' arrows in navigation panels.
    These arrows (such functions) may be completely invisible when they can not be pressed.

But this is more of a general observation.
While I think there are a few locations in MusicBee where this distinction could have been useful, I think you can ignore the consideration for your plugin, since probably every disabled text or button will provide some useful information.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 03, 2023, 10:16:49 AM
for 1: it's just enabled text (both in the plugin and in MB, and in any app i'm aware of). of course, checked and unchecked check boxes/radio buttons look different anyway, but this doesn't concern text labels for them.

for 2: dim texts in the screenshot in your previous post are the labels for inaccessible controls, which can't be used at the moment. i've just checked how label for disabled controls look in mb: yes, it's somewhat lighter (for dark skins) than in plugin. i've tried to fix it:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

(https://i.imgur.com/qYU6X9H.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 03, 2023, 10:46:17 AM
That's looking a lot better.
The 'disabled' text is still somewhat darker in the plugin than in MusicBee, but it's not that much.

Another factor that I think makes the text more difficult to read in the plugin is the fact that the letters are rendered closer together:

(https://i.imgur.com/7OqnMYm.png)

So besides the lower brightness, that additionally make the text less sharp and more difficult to read.
But I can imagine it would be some nightmare to make adjustments to that in your carefully designed panels.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 03, 2023, 11:31:10 AM
mb API doesn't provide colors for disabled controls (also, don't confuse disabled (without quotes) controls with, e.g. unchecked check boxes. "disabled" is standard term), so i can only try to generate these colors from colors of enabled controls and background color  :'(

as for the font, the plugin uses the .net default font. i don't know what font is used by mb. i can change font used by plugin, but it must be some font included in most (better in all) Windows versions. Alternatively, I can use the same bold font. or slightly larger font.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 03, 2023, 11:45:59 AM
as for the font, the plugin uses the .net default font. i don't know what font is used by mb. i can change font used by plugin, but it must be some font included in most (better in all) Windows versions. Alternatively, I can use the same bold font. or slightly larger font.
I am pretty certain MusicBee and the plugin are both using Segoe UI
The difference is that MusicBee uses some wider spacing (tracking) between the letters than the plugin.
Testing in Photoshop, MusicBee uses -40 for the tracking value, the plugin -80.

(https://i.imgur.com/rOjkr7i.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 04, 2023, 08:10:08 PM
numerous bugs have been fixed, which STA PVS-Studio has found. UI is improved. all plugin windows are now using the Segoe UI 10 pt font (the default font for Windows 10 and 11) instead of Microsoft Sans Serif 8 pt (used earlier). i think MB is using Segoe UI 10 pt too.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on November 04, 2023, 08:36:33 PM
all plugin windows are now using the Segoe UI 10 pt font (the default font for Windows 10 and 11) instead of Microsoft Sans Serif 8 pt (used earlier). i think MB is using Segoe UI 10 pt too.
MusicBee's default font is Segoe UI 9pt, not 10pt.

(https://i.imgur.com/PQTAkJW.png)

If that turns out narrower in your plugin, it will be the result of narrower tracking between the individual characters.
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on November 05, 2023, 10:17:53 AM
all plugin windows are now using the Segoe UI 10 pt font (the default font for Windows 10 and 11)
I'm sure you've thought about it before...
but I was wondering if it wouldn't be best to just derive the MB font that the user has specified in hiccup's screenshot above? (Setting_GetDefaultFont)
Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on November 07, 2023, 10:35:30 PM
numerous bugs have been fixed, which STA PVS-Studio has found. UI is improved. all plugin windows are now using the Segoe UI 10 pt font (the default font for Windows 10 and 11) instead of Microsoft Sans Serif 8 pt (used earlier). i think MB is using Segoe UI 10 pt too.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Hi Baroda,
I'm using the latest version of the plugin and have noticed a small bug with the preview & proceed buttons. on the initial click they are labelled as normal. but when it finishes either loading the preview or completing changing tags, both buttons continue to display stop even after the task has been completed.

 (https://imgur.com/QqUv2bQ)
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on November 08, 2023, 06:42:13 AM
Hi Baroda,
I seem to have something weird going on with the new LR screen.
When I run the 'Preview' on a preset it shows dates in the column:
(https://i.imgur.com/wMS8M9S.png)

but if I run the preset from ASR I get the correct results:
(https://i.imgur.com/QbnuuM6.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2023, 11:10:05 AM
I'm sure you've thought about it before...
but I was wondering if it wouldn't be best to just derive the MB font that the user has specified in hiccup's screenshot above? (Setting_GetDefaultFont)

winforms app windows are scaled very badly when the app window font and especially the screen dpi are changed. i'll better stick with a fixed font.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2023, 11:22:26 AM
Hi Baroda,
I'm using the latest version of the plugin and have noticed a small bug with the preview & proceed buttons. on the initial click they are labelled as normal. but when it finishes either loading the preview or completing changing tags, both buttons continue to display stop even after the task has been completed.

(https://imgur.com/QqUv2bQ)

i can't reproduce this bug using my latest code, but there is another related bug now: using the current plugin version (not yet publicly available), this button is always labeled "proceed" and never "stop". i'll take a look at this issue.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 12, 2023, 11:27:53 AM
Hi Baroda,
I seem to have something weird going on with the new LR screen.
When I run the 'Preview' on a preset it shows dates in the column:
...

but if I run the preset from ASR I get the correct results:
...

LR tries to guess custom tag type using all tag values LR deals because it was created before Steven introduced user-defined types for custom tags. obviously, this guessing is not ideal.

i'll better just use the MB API to get user-defined types of custom tags.
Title: Re: Additional Tagging & Reporting Tools
Post by: Eggaian on November 29, 2023, 04:18:05 PM
Uh, I get error messages when I want to use this plugin. Such as:

(https://i.postimg.cc/kGXfJhdp/cum-the-fuk-on.png)

Then I try to "modify tag names so that they all are unique". But It all gets even more broken.

These are the offender tags:

Code
Adding URL / Url
Adding Kind / 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 Time / Duration
Adding Track Gain / ReplayGainTrack
Adding Album Gain / ReplayGainAlbum

The result when trying to modify tags to get this plugin to initialise is this:

Code
Adding Url / Url
Adding  / Kind
Adding Format / Format
Adding  / Size
Cant add  / Size
Adding  / Channels
Cant add  / Channels
Adding  / SampleRate
Cant add  / SampleRate
Adding  / Bitrate
Cant add  / Bitrate
Adding  / DateModified
Cant add  / DateModified
Adding  / DateAdded
Cant add  / DateAdded
Adding Duration / Duration
Adding ReplayGainTrack / ReplayGainTrack
Adding ReplayGainAlbum / ReplayGainAlbum

The error tells me there are duplicate tags. Then I delete them on "tags (2) > configure fields". But I get this:

(https://i.postimg.cc/VsX8dKbH/grrrrrrrr.png)

I tried to match the tags from your plugin with what musicbee says. Doesn't work either.

Code
Adding Kind / Kind
Adding Format / Format
Adding Size / Size
Adding Channels / Channels
Adding Bitrate / Bitrate

Are all the same yea. However, I do not understand

Code
Adding Date Modified / DateModified
Adding Date Added / DateAdded
Adding Time / Duration
Adding Track Gain / ReplayGainTrack
Adding Album Gain / ReplayGainAlbum

Code
Adding URL / Url
and this is simply an Upper case issue. Why is this so anal?

Even if I modify names to be "unique", I still get the same duplicate errors.

And I do not see any
Code
Adding Format / Format
tag present anywhere.

Would it not be much pertinent to match your plugin tags with whatever musicbee dictates? So many headaches. I found posts about this issue like from like 5 years ago or so. You suffer but why?

Just want to initialise the plugin and use it. Partially restore my sanity, please.
Title: Re: Additional Tagging & Reporting Tools
Post by: Eggaian on November 29, 2023, 04:23:40 PM
Also, the settings window within the plugins section, where you can hit "configure", is too large. I find no way to shrink it, therefore, I am unable to see the end of it and save any settings.

(https://i.postimg.cc/x86zSMMv/yyyyyyyy.png)

If I open some quick settings from the "advanced search and replace section", I check "use musicbee skin colours", I get something that is barely readable

(https://i.postimg.cc/cHgxJ3p7/darkcore.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on November 29, 2023, 07:25:04 PM
Also, the settings window within the plugins section, where you can hit "configure", is too large. I find no way to shrink it, therefore, I am unable to see the end of it and save any settings.
What is your monitor's scaling percentage? If not 100% try it at 100%
Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on November 29, 2023, 09:15:24 PM
Hi @ Eggaian,
The error is due to you having duplicate tags writing to the same field. Check your custom tags in Tag 1 settings. Make sure none of them are writing to the same field as other fields be it another custom tag or one that’s native to Musicbee. Also best not to tick use musicbee skin colours, as you’ve discovered it makes it impossible to read any text.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on November 30, 2023, 08:32:36 AM
These are the offender tags:

Code
Adding URL / Url
Adding Kind / 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 Time / Duration
Adding Track Gain / ReplayGainTrack
Adding Album Gain / ReplayGainAlbum

it's the tags which have been successfully registered. find lines which start with "Can't add..." somewhere in the log to see which tags (tag names will be repeated) are duplicated. plugin treats all tag names independently of case.

go to mb menu> edit> prefs> tags (2)> configure fields. check that all tag names are unique in the "override label" column.

don't use skin coloring. for now, this option works with light skins only. i'm working on better support of this option now.
Title: Re: Additional Tagging & Reporting Tools
Post by: Batmang on December 03, 2023, 10:52:36 PM
Hello
I'm having 3 problems with the plugin, both with the Library Reports tool. 2 & 3 may well be user error!

Firstly, with the "Save [field] to [tag]" settings. When I set a tag to save to, it is not saved as part of the auto report, returning to <NULL>. This applies even if I just close the Library Report tool, and if I restart MusicBee.

Secondly, I used to use several <Grouping> fields to calculate an average value, and write that to a tag for every track in that group.
Sadly, with the current system, that no longer works - a specific tag has to be chosen to calculate an average, rather than using the groupings.

Finally, even when using groupings, when writing tags, it appears to calculate using the individual tag rather than the results from the grouping - which are displayed properly on the preview settings.

Any help would be appreciated.
Windows 11
MusicBee Ver: 3.5.8698
AddTagTools: 2023-11-04 16:24:07

(https://imgur.com/a/RprLsjx)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 04, 2023, 02:32:56 AM
foremost, i apologize for my recent mistake: i've uploaded a new plugin version some days ago (and deleted the previous version both from the server and from my PC), which i thought was stable, but it turned out to be very buggy. so, i've had to re-upload the most recent version i could find, which was more or less stable. excuse me. all i can do now is advise you to try one of the very old, stable versions.

for example, you can try this version from 06/26/2023:

https://www.mediafire.com/file/cwwtzg1bmy532j6/mb_TagTools_2023-06-26.zip/file

it's stable, but very old.

also, you can try this recent version from 11/04/2023 (but only if you use win 10/11 (edited: i saw that you are on win 11) and screen dpi at 100%):

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

i'll upload a new, fixed, stable, and greatly improved version in a few days. maybe in a couple of weeks.

but maybe you are using the stable version (it depends on when you downloaded it).

-------------

about your issues:

1. seems to be a bug. i'll check this out. also, maybe it's a bug, which has been fixed already.

2. saving grouping fields to tags is disabled intentionally, just because all grouping fields are already some MB tags. why do you want to save grouping fields as tags?

3. there have been many plugin versions that exposed different LR behaviors (btw, no ALR has been available for a long time; it's been merged with LR. which plugin version are you using?). but i'm doubtful that the version you are using saves some "individual calculated tags." all i can suggest is that recent plugin versions take into account the tags of displayed tracks only (they may be filtered somehow, and you may see not all tracks of your library in the current view) for displaying/exporting LR reports, but all tracks, which have the same grouping tags as the currently displayed tracks for saving functions. this is quite different (and reasonable) behavior.

if you want to experience the same LR behavior for displayed reports and saved functions, don't filter displayed track list (e.g. don't generate reports for playlists, only for entire library).

---------------------

EDIT:

you might want to try the following latest version if you are mostly interested in LR. this version must be stable, but it's incomplete.
don't use the following commands with this version: MSR, both re-encode tag commands and tag history.
swap tags, save last skipped date dialog, and both settings windows may look ugly, but they must work.

https://www.mediafire.com/file/2tn27f7xxzf1sv4/mb_TagTools.dll/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 05, 2023, 05:35:42 PM
new version (i will consider it a beta for a while):

* code refactoring and some UX bug fixes.

* logarithm function is renamed to $Log()

* improved support for skin coloring. some colors are not provided by the MB API; they are auto-generated from the provided colors. skin accent (highlight) color can't be correctly generated, even approximately, but Steven will add support for it to future MB 3.6 versions. the current plugin version will be able to use the enhanced MB API when it is available.

+ now, most commands can't be executed without generating a preview by default. this behavior can be turned off in plugin prefs.

+ added support for 125% dpi screens (using Segoe UI 9pt font instead of .NET default font; this was not trivial), but mostly probably plugin windows will look ugly at 150% and higher scaling.

! still to do: make full support for hi-dpi screens and any font set as the default MB font (not only Segoe UI, not only 9pt). I am not sure when this will be ready. maybe add support for more native (not auto-generated by plugin) skin colors if Steven adds support for them.

! i forgot to make LR use user-defined (custom and virtual) tag types. now, LR is still guessing tag types from the tag values it deals with. but i'll fix this in the near future.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

NOTE: if you are using win 8 or earlier versions, download the full plugin package and follow the included instructions on installing the Segoe UI font family (free for all windows users).

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Dizza17 on December 06, 2023, 06:01:29 AM
Great job Boroda, your efforts and dedication to consistently improving this plugin is to be commended. Thanks again for a wonderful plugin.
Cheers Dizza
Title: Re: Additional Tagging & Reporting Tools
Post by: JMuller on December 06, 2023, 12:44:29 PM
I've ran into a crash, reproducible both with the 05.12.2023 version and the one from the 11.04.2023. It happens why I try to create a Library Report for my entire library (59k tracks, 4k albums).

(https://i.imgur.com/nj1M7KO.png)

Full log is as follows:

Code
MusicBee v3.5.8698.34385D  (Win10.0), 6 Dec 2023 13:39:

System.InvalidOperationException: Sum of the columns' FillWeight values cannot exceed 65535.
   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 System.Windows.Forms.Control.Invoke(Delegate method)
   at MusicBeePlugin.LibraryReportsCommand.applyOnlyGroupingsPresetResults(String[] queriedFiles, Boolean interactive, Int32 sequenceNumberGrouping, Nullable`1 filterResults)
   at MusicBeePlugin.LibraryReportsCommand.executePreset(String[] queriedFiles, Boolean interactive, Boolean saveResultsToTags, String functionId, Nullable`1 filterResults)
   at MusicBeePlugin.LibraryReportsCommand.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 & Reporting Tools
Post by: boroda on December 06, 2023, 07:37:02 PM
Code refactoring, bug fixes, UI/UX improvements:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package:

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file

-----------------------------

I've ran into a crash, reproducible both with the 05.12.2023 version and the one from the 11.04.2023. It happens why I try to create a Library Report for my entire library (59k tracks, 4k albums).

(https://i.imgur.com/nj1M7KO.png)

i'm not able to reproduce this, but i think i've fixed this issue.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 06, 2023, 07:51:00 PM
Hi Baroda,
I seem to have something weird going on with the new LR screen.
When I run the 'Preview' on a preset it shows dates in the column:
(https://i.imgur.com/wMS8M9S.png)

Bee-liever, could you check this issue using the latest plugin version (see the links in my post above)? The new plugin version first tries to get tag types via the MB API. If the API returns a "string" type, then the plugin will still guess the tag type by itself (or leave it as "string" if any conversion to other types fails).
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 06, 2023, 10:24:21 PM
Bee-liever, could you check this issue using the latest plugin version (see the links in my post above)? The new plugin version first tries to get tag types via the MB API. If the API returns a "string" type, then the plugin will still guess the tag type by itself (or leave it as "string" if any conversion to other types fails).

With tag type set to number I'm not getting date values anymore  :)
But I did have to rebuild LR presets.

New skin colour UI looks good.

Thanks for your work on this boroda.
Title: Re: Additional Tagging & Reporting Tools
Post by: JMuller on December 07, 2023, 03:44:10 PM
Code refactoring, bug fixes, UI/UX improvements:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package:

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file

-----------------------------

I've ran into a crash, reproducible both with the 05.12.2023 version and the one from the 11.04.2023. It happens why I try to create a Library Report for my entire library (59k tracks, 4k albums).

i'm not able to reproduce this, but i think i've fixed this issue.

Can confirm the update fixed the issue. Thanks!
Title: Re: Additional Tagging & Reporting Tools
Post by: tdstr on December 08, 2023, 09:31:57 PM
Hi boroda,

Recently I just messed up a ton of track titles in my library. Long story short, I can fix them by restoring their ID3 tags via iTunes, but it's going to corrupt the genre field in the process. Unfortunately I didn't have any good MusicBee tag backups prior to this incident, but I backed up my library right after messing it up, so is it possible to restore *just* the genre field and nothing else? I've been able to do it on an individual track basis in the Tag History window, but I want to extrapolate this for the full library.

Here's what I'm looking for, as seen in the Tag History window:
(https://i.imgur.com/qadNYBe.png)

It's possible to do it track-by-track but there's gotta be a way to do it in bulk. There are ways to import the full tags from the backup I have (I'm able to consistently switch between iTunes tags and MusicBee tags) but I just can't figure out how to only import the genre field.

Thanks for the help!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 10, 2023, 03:33:27 AM
no, it's not currently possible, but maybe i'll implement this later (though I'm not sure when).
Title: Re: Additional Tagging & Reporting Tools
Post by: gaiastar on December 16, 2023, 07:19:23 PM
@boroda
Quote
Be careful to not ACCIDENTALLY tick some "Advanced Search & Replace" or "Library Reports" presets for AUTOMATIC EXECUTION!
Hi Boroda

do you think could add a feature (a sort of safety ) to disable automatic execution ?  :-[
to enable/disable automatic execution
beautiful plugin

Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 17, 2023, 02:31:27 PM
do you think could add a feature (a sort of safety ) to disable automatic execution ?  :-[
to enable/disable automatic execution

i'll do this, but why a sad smile? have you suffered from this feature?
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 17, 2023, 03:51:27 PM
i'll do this, but why a sad smile? have you suffered from this feature?
I think most of us have "suffered" from the auto-apply feature at least once. Speaking only for myself, I learned from my mistake and when selecting a preset I always click in the middle or right side. Never on the left.

Perhaps a simple pop-up warning that the user has just enabled the auto-apply of a feature. Might be easier than a enable/disable routine which would then require an additional click or two.
Title: Re: Additional Tagging & Reporting Tools
Post by: gaiastar on December 17, 2023, 04:52:25 PM

i'll do this, but why a sad smile? have you suffered from this feature?
Hi Boroda
well I would like if you will add it "i'll do this" :)  :-*
about the sad face -> I did some disasters with  automatic execution

Quote from: phred
I think most of us have "suffered" from the auto-apply feature at least once. Speaking only for myself, I learned from my mistake and when selecting a preset I always click in the middle or right side. Never on the left.

thanks Boroda
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 17, 2023, 11:39:36 PM
@gaiastar, ASR/LR preset auto-execution is now disabled by default (you will see a warning message about this at the top of ASR/LR windows). you can enable auto-execution in plugin settings.

@phred, a warning message has been shown at the top of ASR/LR windows if any preset is ticked for auto-execution for a long time. also, a sound notification is played every time you tick preset for auto-execution.

It's possible to do it track-by-track but there's gotta be a way to do it in bulk. There are ways to import the full tags from the backup I have (I'm able to consistently switch between iTunes tags and MusicBee tags) but I just can't figure out how to only import the genre field.

now, the 1st item in the track list at the top of the tag history window is "selected tracks." it's the default item, but you can select just one track (or cycle through selected tracks to restore all or some of their tags track by track) from the list if you wish.

sometimes you'll see a tag value "(Mixed values)" if several tracks are selected; don't worry, the corresponding tag value will be restored for every track.

----------------

* improved support for skin colors (especially auto-generated), UI/UX improvements and fixes, source code refactoring, etc., etc., etc.

+ full support for high-DPI screens. actually tested using 100% and 125% only, but should work using any scale. would be great if somebody tested new version at 150% and higher scales because my monitor becomes almost unusable at so high scales.

+ support for MusicBee font (only when "use skin colors" option is enabled in plugin settings, otherwise "Segoe UI 9 pt" font is used).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package (use it if you are not familiar with plugin installation/update process or if you use pre-win 10 os; full package includes required fonts):

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file

---------------

NOTE: i will consider this version a beta for some time due to huge code refactoring
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on December 18, 2023, 12:53:11 AM
@phred, a warning message has been shown at the top of ASR/LR windows if any preset is ticked for auto-execution for a long time. also, a sound notification is played every time you tick preset for auto-execution.
Thanks boroda. I guess I've been a good boy and haven't enabled any auto-apply presets in quite some time as I never noticed the warning. Which I did see just now when testing it. As for a sound notification, I only have headphones on this PC and I use them when listening/watching media.
Title: Re: Additional Tagging & Reporting Tools
Post by: gaiastar on December 18, 2023, 06:29:29 AM
@gaiastar, ASR/LR preset auto-execution is now disabled by default (you will see a warning message about this at the top of ASR/LR windows). you can enable auto-execution in plugin settings.
Hi Boroda
Quote
+ support for MusicBee font (only when "use skin colors" option is enabled in plugin settings, otherwise "Segoe UI 9 pt" font is used).
can I ask you a question ?
if skin colors is enabled , the plugin does not need Segoe UI 9 pt ,doesn't it?
Quote
you can enable auto-execution in plugin settings.
great news , is  it easy to uninstall it ? I mean does it leave files (configs in musicbee configuration files) or registry?
just to perform a clean uninstall of the plugin and re-install it
thanks Boroda , I really appreciate a lot your effort
Title: Re: Additional Tagging & Reporting Tools
Post by: sveakul on December 18, 2023, 07:11:32 AM
can I ask you a question ?
if skin colors is enabled , the plugin does not need Segoe UI 9 pt ,doesn't it?

Quote
+ support for MusicBee font (only when "use skin colors" option is enabled in plugin settings, otherwise "Segoe UI 9 pt" font is used).

Quote
great news , is  it easy to uninstall it ? I mean does it leave files (configs in musicbee configuration files) or registry?

From the readme:

REMOVING THE PLUGIN

1 – Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Uninstall.
2 – MusicBee will delete all automatically created files (e.g., settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolders "ru" and "ASR Presets" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder "%AppData%\MusicBee".
Title: Re: Additional Tagging & Reporting Tools
Post by: gaiastar on December 18, 2023, 07:25:31 AM
From the readme:
REMOVING THE PLUGIN
1 – Open MusicBee. From the menubar > Edit > Edit Preferences > Plugins > Additional Tagging & Reporting Tools > Uninstall.
2 – MusicBee will delete all automatically created files (e.g., settings). You will need to close MusicBee and manually delete file "mb_TagTools.dll" and the subfolders "ru" and "ASR Presets" from "Plugins" folder. The "Plugins" folder is located in MusicBee application folder if you are using the portable version of MusicBee. If using the installer version of MusicBee, it's in the folder "%AppData%\MusicBee".
Hi
but does this procedure work with other plugins?
just because it could be very useful to perform it if a plugin could crash
I don't to be offtopic but I had some issues with LYRICSRELOADED (LATEST) plugins to uninstall it at 100% , it was used to  crash sometime musicbee
thanks
Title: Re: Additional Tagging & Reporting Tools
Post by: sveakul on December 18, 2023, 07:46:30 AM
The procedure I quoted is specfically from and for Boroda's plugin, which was the whole context originally.

I gave you the 100% uninstall procedure for the LyricsReloaded plugin in its own forum thread.  Problems with that one are almost ALWAYS associated with the person having multiple instances of the plugin dll installed from past or botched installs of MusicBee from "Installer" versions that were not properly removed before.  The best way to check for that is with a simple Windows File Explorer search (include "hidden files") for mb_LyricsReloaded.dll.
Title: Re: Additional Tagging & Reporting Tools
Post by: gaiastar on December 18, 2023, 09:48:10 AM
The procedure I quoted is specfically from and for Boroda's plugin, which was the whole context originally.

I gave you the 100% uninstall procedure for the LyricsReloaded plugin in its own forum thread.  Problems with that one are almost ALWAYS associated with the person having multiple instances of the plugin dll installed from past or botched installs of MusicBee from "Installer" versions that were not properly removed before.  The best way to check for that is with a simple Windows File Explorer search (include "hidden files") for mb_LyricsReloaded.dll.
Hi Sveakul
thank you , appreciate it
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 18, 2023, 08:52:15 PM
but does this procedure work with other plugins?
just because it could be very useful to perform it if a plugin could crash
I don't to be offtopic but I had some issues with LYRICSRELOADED (LATEST) plugins to uninstall it at 100% , it was used to  crash sometime musicbee
thanks

what happens when you click the "uninstall" button next to the plugin name in MB preferences depends absolutely on the plugin in question. i suggest that most plugins do nothing when calling their Uninstall() function. ALL MY plugins always delete all auto-created files.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 19, 2023, 04:48:06 AM
NOTE: i will consider this version a beta for some time due to huge code refactoring
Just a few things I've found.
1/.
In Library reports, you need to add a second column definition to have the first one calculate correctly
(http://i.imgur.com/42WwzkJ.jpg) (https://imgur.com/42WwzkJ)

(http://i.imgur.com/byKi9dh.jpg) (https://imgur.com/byKi9dh)
This was also happening in the previous version but unfortunately I didn't get to report it before you posted the new beta version. Sorry.

2/.
Save button highlight area is larger than underlying Save button and covers Help button.
(http://i.imgur.com/YIt635E.jpg) (https://imgur.com/YIt635E)

3/.
New 'use skin colouring' settings don't work as well as previous version on default, disabled and highlight buttons.
With some skins the only thing you can see is the warning symbol that shows for unsaved settings.
Title: Re: Additional Tagging & Reporting Tools
Post by: deviluke on December 19, 2023, 04:51:00 PM
I love this plugin! I'm using v7, latest downloadable from the plugin page.
Wishlist:
- Add the <Custom Text>'s to the list of tags you can search/save values into. This allows easy modifying of the input for slight variations.
It also allows easily doing things like replacing placeholders in the <Custom Text>, for example for the "Generate "Displayed Artist" separated by <Custom text> from multi-artist field":
"feat. (<?>)" where <?> can be set to be replaced with a value, resulting in "feat. (Artist1 & Artist2)"

- Add a conditional input in the Preset Editor. Basically, imagine in between every step there was a toggable input field, that allowed to write conditional statements like '<Temp 1> == "some value"', and if it results in a false expression, the steps terminate or skips (should be an option). If in between every step is too much, then maybe just one at end.

- Same as above but just for the processing and simpler. It just evaluates a regex expression in a chosen tag, if the expr doesn't match, the track gets skipped. I think this one is more important. It would allow pre-filtering the tracks that gets processed.
Many times I would have to do a few passes with slight variations and/or with similar presets to get all the tracks. An option like this would help a lot!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 19, 2023, 11:44:26 PM
1/.
In Library reports, you need to add a second column definition to have the first one calculate correctly

actually, there were much more LR bugs. i've fixed them, but please recheck updated LR.

2/.
Save button highlight area is larger than underlying Save button and covers Help button.

thanks, very stupid bug. it's fixed.

3/.
New 'use skin colouring' settings don't work as well as previous version on default, disabled and highlight buttons.
With some skins the only thing you can see is the warning symbol that shows for unsaved settings.

i wasn't able to reproduce this issue, but anyway there were bugs related to buttons rendering. also, try another skin if you see the same problem with updated plugin version; maybe it's autogenerated skin color's problem.

----------------

* numerous LR bug fixes
* some minor general UI/UX fixes and improvements

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package:

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 20, 2023, 12:22:50 AM
forgot to mention: new plugin version is targeted to .net 4.8 instead of 4.8.1 because it seems that 4.8 is the last .net version available for win 7.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 20, 2023, 01:52:34 PM
After clean-installing the plugin, you can't do anything.
All buttons are greyed out.
You can't create a new preset, you can't import a preset, etc.

(https://i.imgur.com/BaHJgxm.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 20, 2023, 06:38:22 PM
@hiccup, thanks a lot! don't know how i've missed this glaring mistake.

https://www.mediafire.com/file/wcggbq7pcgium2v/mb_TagTools.zip/file

full package:

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 20, 2023, 11:34:11 PM
i've fixed some stupid bugs of skin coloring. download links are the same.
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 21, 2023, 12:04:27 AM
This is the latest skin colouring with the default MusicBee3 skin (ATRT 8.0.8755.4510)
(http://i.imgur.com/w1AQSqi.jpg) (https://imgur.com/w1AQSqi)
Might still need some tweaking  ;D
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 21, 2023, 12:52:46 AM
@Bee-liever, this is not what i see using MusicBee3 skin:

(https://i.imgur.com/tdFEpAW.png)

but 8.0.8755.4510 is not the last version. i've re-uploaded the plugin in case of mistake:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file

also, i see you are using win 11. am i right?

-----------

edit: which MB version are you using?
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 21, 2023, 01:19:19 AM
also, i see you are using win 11. am i right?
-----------
edit: which MB version are you using?

Yes, Windows 11 and MB 3.5.8750 P

----------

and now using 8.0.8755.7682
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 21, 2023, 01:19:52 AM
ok, try this version:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on December 21, 2023, 01:35:17 AM
Had to wait for MediaFire server to update
Still shows 8.0.8755.7682 and still looks the same.
MB did take a bit longer to load the first time after updating to this version.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 21, 2023, 08:37:07 PM
@Bee-liever, new version must work correctly with MB 3.5 (it has been previously tested with 3.6 only).

Also:

* Final code refactoring and cleanup. It's still debug version. The next version will be built with compiler optimizations enabled, and debug info removed.
* Now, plugin windows are shown after some delay required to calculate window's layout and to reflow it (due to support for custom font and Hi-DPI screens). So, windows must be shown completely properly rendered. The delay is 750 ms for the most windows (e.g. copy tag/swap tags), but can exceed 2 sec. for very complex windows (e.g. ASR/LR). Would like to get feedback to this feature.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b8spddpp2oymr3x/Additional-Tagging-Tools-Plugin.new.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 23, 2023, 02:57:34 PM
"An unexpected error occurred" when selecting a preset, then use [Copy] and then pressing [OK]:
(plugin v.8.0.8756.26553)


Code
MusicBee v3.6.8736.15690P  (Win10.0), 23 Dec 2023 15:51:

System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.refreshPresetList(Guid selectedPresetGuid)
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.editPreset(Preset tempPreset, Boolean itsNewPreset, Boolean readOnly)
   at MusicBeePlugin.AdvancedSearchAndReplaceCommand.buttonCopy_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 & Reporting Tools
Post by: hiccup on December 23, 2023, 03:30:49 PM
Error: preset is gone after restart.

- download latest version of AT&RT

- use "Add Plugin…" to select and install "mb_TagTools.dll"

- use [Import] (preset management) to select all (111) presets from the downloaded "ASR Presets" folder

(https://i.imgur.com/E2cShwg.png)

You will see a preset named "Multiple search & replace":

(https://i.imgur.com/iJjr2YY.png)

Restart MusicBee, and that preset is gone from the list:

(https://i.imgur.com/YV1O5RA.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 23, 2023, 09:37:28 PM
i'll check the first bug today (null reference exception). as for the "MSR preset": it must exist to save presets from MSR, but it's a service preset (just a template for user MSR presets) and should be always hidden, so it's a bug that it's visible right after importing presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 24, 2023, 06:51:54 AM
as for the "MSR preset": it must exist to save presets from MSR, but it's a service preset (just a template for user MSR presets) and should be always hidden, so it's a bug that it's visible right after importing presets.
I don't understand.
I can see a purpose for that specific preset. How could a user make use of it if it is invisible?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 25, 2023, 04:27:33 PM
not user. MSR uses it as a template. of course i could hard code its body to paste it to every user MSR preset, but it turned out to be easier for me to make "service hidden" ASR preset to use it as a template for saved MSR presets.

never mind. users should never see this preset, and it's fixed now. i just didn't expect that somebody would "import" predefined presets, rather "install" them. again, this visual bug is fixed.

"null reference exception" from your previous bug report has been fixed also.

also:

* some UI/UX fixes and improvements.
* some "tag history" command bug fixes.
* it's the final release for the version 8.0 (it's not compiled in debug mode anymore).

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 25, 2023, 04:42:55 PM
not user. MSR uses it as a template. of course i could hard code its body to paste it to every user MSR preset, but it turned out to be easier for me to make "service hidden" ASR preset to use it as a template for saved MSR presets.
never mind. users should never see this preset, and it's fixed now. i just didn't expect that somebody would "import" predefined presets, rather "install" them. again, this visual bug is fixed.
At the moment I don't seem able to fully digest what you have explained here.
(It's me, I'm sure ;-)

But here's the gist of what made me wonder about this 'disappearing preset':
That preset seemed to make it possible to find and replace various strings in a tag.

E.g. if you would have a tag containing 'cats' and 'elephants', you could have them changed to 'dogs' and 'penguins'.
( doing: cats/dogs|elephants/penguins if I am not mistaken)

Is this still available as some preset that can be copied/modified?

And what do you mean by MSR?
Are you referring to that particular preset (Multiple search & replace), or some more general AT&RT feature?

Again, sorry for perhaps being a bit slow/thick tonight.
(for one thing, it looks like I need to understand the differences between what you are calling 'presets' and 'templates')
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 25, 2023, 05:50:36 PM
At the moment I don't seem able to fully digest what you have explained here.

no, it's very simple. of course, MSR is "multiple search & replace". every MSR query can be saved as ASR preset. such ASR presets (saved by user from MSR) will be visible/manageable both in ASR and MSR. all such presets use the same common part (the same "basis"). this common part is implemented as "service hidden" ASR preset. this service preset could be used directly by users, but it's not so easy to edit it manually. much better to allow MSR handling this. that's why this service preset is hidden.

every time you save MSR query as (ASR) preset, you actually create a new modification of this service preset.

----------------

edit:

initially, MSR has been created as this (not service or hidden at that time) ASR preset (it has been requested by @redwing). but later i've decided that most users won't be able to understand how to use it, and created a dedicated MSR command as simply some user-friendly frontend for this preset (and hidden this ASR preset).
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 25, 2023, 06:08:35 PM
no, it's very simple
Hi.
I am simple. (and not ashamed of it ;-)
I'm also a foreigner.

From a specific tag I would like to have the string 'cats' replaced by 'dogs', and the string 'elephants' replaced by 'penguins'.

I think there was a preset named "Multiple search & replace"  that could do that.
That preset (or template?) is now gone.

How can I find how to create or modify a preset that will change cats to dogs and elephants to penguins?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 25, 2023, 07:33:35 PM
I am simple. (and not ashamed of it ;-)

 :D

From a specific tag I would like to have the string 'cats' replaced by 'dogs', and the string 'elephants' replaced by 'penguins'.

just open MSR command. enter "cats" in the "search for" column of 1st line and "dogs" in the "replace by" column. then enter "elephants" and "penguins" respectively in the 2nd line. you can add as many subsequent search/replace lines as needed. also, you can use case-sensitive search or regex search/replacements if you wish (tick corresponding check boxes on the left columns of template table for required lines). you can save your search/replace pattern as ASR preset. this ASR preset can be auto-executed if needed.

i'm too lazy to write detailed documentation for every plugin command, but i tried to use tool tips as mush as possible. follow them.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 25, 2023, 07:50:02 PM
just open MSR command.
Ah!
Never underestimate how blind and ignorant a user can be for things that are there plain to see in the open.

So AT&RT has a specific "Multiple search & replace" feature.
(https://i.imgur.com/0dDXUS6.png)

Which is a different thing from the "Multiple search & replace" preset/template that I encountered and was talking about.

I'll shut-up for a while now, and see if I can digest and understand what you have been trying to explain.

Thanks!
 
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 26, 2023, 01:38:08 PM
So AT&RT has a specific "Multiple search & replace" feature.
Which is a different thing from the "Multiple search & replace" preset/template that I encountered and was talking about.

not exactly. MSR command is just a convenient frontend for that service hidden ASR preset, which (ASR preset) is also named "MSR". ASR & MSR are very tightly tied.

but you (and any user) don't need to know how MSR command is implemented, just use it, all its features are available on the MSR window.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 26, 2023, 02:08:00 PM
So AT&RT has a specific "Multiple search & replace" feature.
Which is a different thing from the "Multiple search & replace" preset/template that I encountered and was talking about.
not exactly. MSR command is just a convenient frontend for that service hidden ASR preset, which (ASR preset) is also named "MSR". ASR & MSR are very tightly tied.
With 'different' I meant that I had only looked at the "multiple search & replace" preset in AS&R, and I was completely oblivious of the "multiple search & replace" frontend that you were talking about.
(some RTFM (https://getmusicbee.com/addons/plugins/49/additional-tagging-amp-reporting-tools/) would have done me good…)

So I now understand that if you want to create a preset that can replace multiple strings in a tag, it's best to start by opening the "Multiple Search & Replace" function from the drop-down menu and create and then save it as a preset.
After that it will be available in the AS&R panel, where you can also modify it if so desired.

I'm still not sure why AS&R shouldn't have an 'example' preset for it that a user can use as a template to modify.

- - -

A practical question about such a preset that I can't get to work:

Suppose you have 'semi-roman' characters in the title tag, such as: VIII
And you want to change that string to Ⅷ
(the single character for the roman number 8 )

I tried doing this:
VIII/Ⅷ  (and *VIII/Ⅷ)
but it doesn't work.

What am I doing wrong?

- - -

edit:
I'm getting this error message when trying to create and save such a preset.
What does it mean, and what should I do?

(https://i.imgur.com/wBTsIyK.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 26, 2023, 05:31:39 PM
Quote
I'm still not sure why AS&R shouldn't have an 'example' preset for it that a user can use as a template to modify.

because even @redwing (!), who has requested this ASR preset (which has been available only as (visible) ASR preset at that time), wasn't able to completely understand how to use it. so i've created MSR frontend for it. do you think that direct access to this preset can be useful to somebody? this anyway won't give any additional features which are not supported by MSR command.

---------------

this error message means that service ASR preset (which is "MSR") hasn't been installed. 1st "Install All" ASR presets (to install "MSR" preset either), then you can safely delete any visible predefined (and of course user's) ASR presets ("MSR" preset won't be visible, so you can't delete it accidentally, only if you manually delete its XML file from "<AppData>\ASR Presets" working folder - NOT from "Plugins\ASR Presets" folder, which is just the source for installed presets and can be safely deleted at any time).

-----------------

new plugin version.

Some UI bug fixes and minor general bug fixes:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file

--------------

my GitHub account is blocked for unknown reasons (i hope only temporary), so the latest plugin source code is available here for now:

https://www.mediafire.com/file/gpg14ohuaocbzhv/TagTools_Latest_Source.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 26, 2023, 05:56:28 PM
because even @redwing (!), who has requested this ASR preset (which has been available only as (visible) ASR preset at that time), wasn't able to completely understand how to use it. so i've created MSR frontend for it. do you think that direct access to this preset can be useful to somebody? this anyway won't give any additional features which are not supported by MSR command.
I can only speak for myself.
I was happy to find the 'multiple search & replace' preset in ASR.
And thanks to the explanation it included (cats/dogs|this/that etc.) it seemed pretty easy to edit it and put it to use.
So I was confused when it didn't stick, and the preset disappeared after a restart.

So now I have learned that there is a separate MSR frontend that was designed for this specifically, and that it is not intended to have this available from the ASR panel.
But it will become available in ASR after you have used MSR.

I now understand how this came to be, but having the need of this additional MSR to create something that can be used in ASR doesn't seem the most optimal solution.
In my opinion it would be better if ASR was capable of doing this by itself, without the need to resort to some separate MSR feature.
 
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 26, 2023, 06:44:06 PM
I now understand how this came to be, but having the need of this additional MSR to create something that can be used in ASR doesn't seem the most optimal solution.
In my opinion it would be better if ASR was capable of doing this by itself, without the need to resort to some separate MSR feature.

let me rephrase what you said: you are actually just proposing easy access to "MSR window" (some access to MSR features) from ASR window. this can be done, but the problem is that (despite the fact that ASR and MSR share a common base internally) from user's point of view, these 2 commands have nothing common until the user save his MSR search/replace template for future use. saving MSR templates is neither required by plugin nor frequently demanded by users. also, saved MSR templates anyway can be managed from MSR command, their management doesn't require opening ASR window.

Close internal interconnection of ASR and MSR is the question of implementation, users must not care about this.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on December 26, 2023, 07:08:50 PM
let me rephrase what you said: you are actually just proposing easy access to "MSR window" (some access to MSR features) from ASR window. this can be done, but the problem is that (despite the fact that ASR and MSR share a common base internally) from user's point of view, these 2 commands have nothing common until the user save his MSR search/replace template for future use. saving MSR templates is neither required by plugin nor frequently demanded by users. also, saved MSR templates anyway can be managed from MSR command, their management doesn't require opening ASR window.
Back to my comfortable and simple state of mind ;-)

There is "Advanced Search & Replace".

I appreciate the word 'advanced', and I would think it is the most powerful version of what it does.

But then there is also "Multiple Search & Replace".
So now 'Advanced Search & Replace" doesn't seem to be the most advanced and complete version, but there also is some "Multiple Search & Replace" variety that does something different.

So 'advanced' can not do 'multiple?

From the perspective of a user that does not know the history and understand the background of how that came to be, that will seem confusing.

I don't have a specific suggestion at the moment, but I believe it would be better if there would be one ring to rule them all.

Just my opinion. Your arguments and perhaps the opinion of other users may be more valid.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 26, 2023, 09:02:28 PM
"advanced..." or some other name, but the purpose of ASR is to provide permanently saved presets (which allow only tiny adjustments), not arbitrary search/replacement, which is possible in ASR in principle, but its UI is NOT intended for this. the main purpose of MSR is to provide arbitrary search/replacement. saving MSR templates is just an additional bonus.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 28, 2023, 02:58:38 PM
Minor change. Plugin uses MusicBee font & skin colors by default now:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file

-------------

Plugin source code repository has been moved from GitHub to sourceforge.net:

https://sourceforge.net/p/tag-tools/code/ci/master/tree/
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on December 28, 2023, 06:20:51 PM
Quote from: boroda
Plugin uses MusicBee font & skin colors by default now
Long absence ("Real-Life-Stuff"), but some time to play now.

I'm not so sure that coupling the plugin to MB's custom font size is working quite right when DPI is 125%.  Using Win10, if the "default" Segoe UI 9pt is used, all is well, however, increasing that font even by 1 point causes problems.  Segoe UI 10pt (at 125% it actually becomes 10.2), the ASR window expands to below the taskbar, so the "preview" section is mostly cut off.  Worse, the preset editing window extends similarly, so that the "Step 5" controls are completely inaccessible.

Maybe only tie it to any custom font up to 9pt but decouple it for anything over that (if DPI > 100)?  At least the font/skin option can still be turned off for now, so it defaults back to 9pt, albeit with the sickly white default skin colours.

Also, was the "Ok" button intentionally removed from the plugin configuration (Options -> Plugins...)?  Hitting <Enter> seems to apply settings, so it's no great loss, but a dialog with no "Ok" button is just weird...

And, in that same window, in the "result filtering" options section, in the English translation the word "Include" is missing the 'l' letter, on all three lines.

Thanks for your continuing efforts.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 29, 2023, 06:46:59 PM
Maybe only tie it to any custom font up to 9pt but decouple it for anything over that (if DPI > 100)?  At least the font/skin option can still be turned off for now, so it defaults back to 9pt, albeit with the sickly white default skin colours.

ok, i'll separate the options "use MB font" & "use skin colors".

Also, was the "Ok" button intentionally removed from the plugin configuration (Options -> Plugins...)?  Hitting <Enter> seems to apply settings, so it's no great loss, but a dialog with no "Ok" button is just weird...

it's because i wasn't able to think of any good layout of settings window for 125%. but settings window must become vertically scrollable (entire window) if it doesn't fit vertical screen size. isn't it scrollable for you?

And, in that same window, in the "result filtering" options section, in the English translation the word "Include" is missing the 'l' letter, on all three lines.

thanks, i'll check this.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on December 29, 2023, 07:19:35 PM
Quote from: boroda
ok, i'll separate the options "use MB font" & "use skin colors".
Thanks.

Quote from: boroda
...isn't it scrollable for you?
It is scrollable, it's just that in one of the more recent updates, the "Ok" button was contained within the scrolling area, and while a bit unorthodox, it worked.  With the last version however, the scrolling only shows up to the "Unit of Billions..." option - if there's supposed to be options/buttons below that one, they aren't displayed, that's why I asked if you removed it.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 29, 2023, 10:25:00 PM
ok, i'll separate the options "use MB font" & "use skin colors".

it's done: "use skin colors" is enabled by default, "use MB font" is disabled by default.

it's because i wasn't able to think of any good layout of settings window for 125%. but settings window must become vertically scrollable (entire window) if it doesn't fit vertical screen size. isn't it scrollable for you?

i've added tabs to the plugin settings window. now, this window must fit most screens.

And, in that same window, in the "result filtering" options section, in the English translation the word "Include" is missing the 'l' letter, on all three lines.

i don't see this issue in the last uploaded plugin version. anyway settings layout has been changed, so could you check this for new version?

------------------

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on December 30, 2023, 07:14:07 AM
i don't see this issue in the last uploaded plugin version...

You can't see "Incude" instead of "Include"?  It's there whether skinning is on or not...

(https://i.imgur.com/tsei6Oj.jpg)

The rest of the changes are all great at first glance.  Many thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 30, 2023, 09:27:34 AM
Damn! English letters! I thought you meant I, not l  ;D
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on December 30, 2023, 10:49:28 AM
Typo and minor UI fixes:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: sebmuc on January 02, 2024, 01:28:00 PM
Can someone help me with the Library Report? I want to run the Library Report Export on every Start and it seems that something happens but i can't find the export file

Title: Re: Additional Tagging & Reporting Tools
Post by: pakk on January 05, 2024, 03:42:01 PM
Hi,
I need to manually update the "Last played" property for some files
According to this post (https://getmusicbee.com/forum/index.php?topic=23089.msg134959#msg134959), I should be able to do it with the ASR "Set tag" feature of this plugin.
Is this really possible ?

I've installed all presets, but when I click on "Set tag" checkbox, I have the following error:
Code
MusicBee v3.5.8150.17011D  (Win10.0), 5 janv. 2024 16:30:

System.NullReferenceException: La référence d'objet n'est pas définie à une instance d'un objet.
   à MusicBeePlugin.AdvancedSearchAndReplaceCommand.presetList_ItemCheck(Object sender, ItemCheckEventArgs e)
   à System.Windows.Forms.CheckedListBox.OnItemCheck(ItemCheckEventArgs ice)
   à System.Windows.Forms.CheckedListBox.SetItemCheckState(Int32 index, CheckState value)
   à System.Windows.Forms.CheckedListBox.SetItemChecked(Int32 index, Boolean value)
   à MusicBeePlugin.AdvancedSearchAndReplaceCommand.presetList_MouseClick(Object sender, MouseEventArgs e)
   à System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
   à System.Windows.Forms.ListBox.WndProc(Message& m)
   à System.Windows.Forms.CheckedListBox.WndProc(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
https://www.dropbox.com/scl/fi/6r4tpz75njyxkgsi1xa88/musicbee_ATRT_ASR_error.jpg?rlkey=67rljlkff9wxchbxnbzte8gtl&dl=0
Version: 5.7.8442.39379

How can I fix this ?
Thanks in advance and have a nice day
Title: Re: Additional Tagging & Reporting Tools
Post by: Mafios on January 10, 2024, 09:58:47 PM
Hello. I'm having some trouble with certain keys (backspace, spacebar, arrows, maybe more) not working, while also triggering MB actions in the background.
Title: Re: Additional Tagging & Reporting Tools
Post by: Kur0 on January 16, 2024, 02:47:29 PM
I seem to get this error for many things such as the "Copy Tags..."  button.
Using plugin version 8.0.8764.24665

Code
MusicBee v3.4.7805.33439P  (Win10.0), 16 Jan 2024 22:40:

System.ArgumentException: Value 'BackgroundColor' cannot be set to an empty value.
   at System.Windows.Forms.DataGridView.set_BackgroundColor(Color value)
   at MusicBeePlugin.PluginWindowTemplate.skinControl(Control control)
   at MusicBeePlugin.PluginWindowTemplate.skinMoveScaleAllControls()
   at MusicBeePlugin.PluginWindowTemplate.initAndShow()
   at MusicBeePlugin.PluginWindowTemplate.Show()
   at MusicBeePlugin.PluginWindowTemplate.Display(PluginWindowTemplate newForm, Boolean modalForm)
   at MusicBeePlugin.Plugin.copyTagEventHandler(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 & Reporting Tools
Post by: phred on January 16, 2024, 06:44:23 PM
MusicBee v3.4.7805.33439P  (Win10.0), 16 Jan 2024 22:40:
The more recent versions of this plugin require MB version 3.5+. Update to the latest version by applying the patch in my signature below and try again. If you still are having issues, report it here.
Title: Re: Additional Tagging & Reporting Tools
Post by: Kur0 on January 17, 2024, 04:43:16 AM
Yeah, that fixed it lol. I didn't think too much of the MusicBee version since the plugin page said to use at least v3. My bad.

Now that it's functional, I wanted to ask if it's possible to have a "Search and Replace" preset that takes the file path of a song and renames the file extension to something else? I converted a couple of songs from FLAC to MP3 outside of MusicBee and now it treats the converted files as new songs with a different "Date added" tag. "Locate Missing Files" doesn't work because the file extension is different. I can't just overwrite "Date added" with "Date modified" because it's not the same thing. Some songs have "Date modified" preserved and points to dates that take place before I even obtained the file.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 17, 2024, 12:37:25 PM
Yeah, that fixed it lol. I didn't think too much of the MusicBee version since the plugin page said to use at least v3. My bad.
@boroda... I haven't checked it myself, but perhaps the plugin page should be updated to indicate the minimum version of MB required.

EDIT: corrected a typo
Title: Re: Additional Tagging & Reporting Tools
Post by: simpjkee on January 17, 2024, 11:51:51 PM
Quote
MusicBee v3.4.8033.18564D  (Win10.0), 17 Jan 2024 16:49:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at MusicBeePlugin.PluginWindowTemplate.Display(PluginWindowTemplate newForm, Boolean modalForm)
   at MusicBeePlugin.Plugin.Configure(IntPtr panelHandle)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at #=zMnhegC3cZoGqJc9MnQ==.#=zHNzzNWE=(IntPtr #=zznrCYSH69sZI)


I followed the steps in the Readme First document to install it. Then I went to Tools and additional tagging tools, but that is it. I click on it and nothing happens. Went back in to Edit Preferences and click "configure" and got the above error. It doesn't seem as though it installed anything really.
Title: Re: Additional Tagging & Reporting Tools
Post by: frankz on January 18, 2024, 03:01:17 AM
Look three posts up (https://getmusicbee.com/forum/index.php?topic=3833.msg219932#msg219932) from yours.

It's always a good idea to read at least a few recent posts in a thread before posting to it.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 04:04:33 PM
phred, frankz, thank you for helping users while i was absent.

i now try to look at unanswered issues.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 04:07:24 PM
Can someone help me with the Library Report? I want to run the Library Report Export on every Start and it seems that something happens but i can't find the export file

no, no, no. LR reports can be exported to files only manually. 'auto-execute preset at startup' option is intended to save LR functions to (e.g. custom) tags!
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 04:09:28 PM
Hi,
I need to manually update the "Last played" property for some files
According to this post (https://getmusicbee.com/forum/index.php?topic=23089.msg134959#msg134959), I should be able to do it with the ASR "Set tag" feature of this plugin.
Is this really possible ?

I've installed all presets, but when I click on "Set tag" checkbox, I have the following error:
Code
MusicBee v3.5.8150.17011D  (Win10.0), 5 janv. 2024 16:30:

System.NullReferenceException: La référence d'objet n'est pas définie à une instance d'un objet.
   à MusicBeePlugin.AdvancedSearchAndReplaceCommand.presetList_ItemCheck(Object sender, ItemCheckEventArgs e)
   à System.Windows.Forms.CheckedListBox.OnItemCheck(ItemCheckEventArgs ice)
   à System.Windows.Forms.CheckedListBox.SetItemCheckState(Int32 index, CheckState value)
   à System.Windows.Forms.CheckedListBox.SetItemChecked(Int32 index, Boolean value)
   à MusicBeePlugin.AdvancedSearchAndReplaceCommand.presetList_MouseClick(Object sender, MouseEventArgs e)
   à System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
   à System.Windows.Forms.ListBox.WndProc(Message& m)
   à System.Windows.Forms.CheckedListBox.WndProc(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
https://www.dropbox.com/scl/fi/6r4tpz75njyxkgsi1xa88/musicbee_ATRT_ASR_error.jpg?rlkey=67rljlkff9wxchbxnbzte8gtl&dl=0
Version: 5.7.8442.39379

How can I fix this ?
Thanks in advance and have a nice day

this is VERY old plugin version. latest version is 8.0.xxxx
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 04:11:00 PM
Hello. I'm having some trouble with certain keys (backspace, spacebar, arrows, maybe more) not working, while also triggering MB actions in the background.

could you be more specific? i don't understand what you mean.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 04:13:57 PM
Now that it's functional, I wanted to ask if it's possible to have a "Search and Replace" preset that takes the file path of a song and renames the file extension to something else?

Unfortunately, no. it's not the restriction of the plugin, it's the restriction of MB API: track's path/filename/extension is read-only.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 04:16:40 PM
@boroda... I haven't checked it myself, but perhaps the plugin page should be updated to indicate the minimum version of MB required.

Thanks for advice. it's done.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 20, 2024, 05:36:55 PM
Hello. I'm having some trouble with certain keys (backspace, spacebar, arrows, maybe more) not working, while also triggering MB actions in the background.

could you be more specific? i don't understand what you mean.
I have seen this too - it's directly related to the hotkeys the user sets within Preferences -> Hotkeys.  For some reason the plugin window is not "insulated" from them, and MB takes the keystroke despite not having direct focus.

For example, were you to set the spacebar as the hotkey for Playback -> Play/Pause (as many media players do), if the ASR window is open and you are trying to type into a field (say <Custom Text 1> for example), every time you hit <Space> MB grabs the message and starts/pauses the music - but no <Space> character can be entered into the field, since the keystroke is gone.

The only way around it is to disable the keys you want from being hotkeys, so common ones such as <Left>, <Right>, <Back>, etc. can't be used, unless you want to have a lot of trouble in ASR windows.

I reported this once, but you got sidetracked onto other things so it was never looked into, or you couldn't reproduce it for some reason.  Try the above example (of spacebar) and you'll see what I mean.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 20, 2024, 06:59:25 PM
i won't check this because i already know what's the problem.

i've recently removed the code Steven has provided earlier to avoid this issue because it was very difficult to edit dialogs keeping this code. i thought it's not required anymore (doesn't matter why i thought so).

obviosly, i've mistaken. my fault. today is too late in Moscow, but i'll return this old code back tomorrow.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 21, 2024, 06:52:48 AM
* Fixed support for MusicBee hotkeys. I haven't tested this version, only returned previously removed code back, but all must be working as earlier.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on January 21, 2024, 07:17:08 AM
...but all must be working as earlier.
Appears to be fixed on initial testing.  Thanks.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 22, 2024, 06:48:36 PM
i've made minor improvement of "copy tags to clipboard"/"paste tags from clipboard" commands:

1. new pseudo-tag added: <Full path w/o ext.> (besides already existing <URL> pseudo-tag). it's full music file path including filename, but without extension.
2. If the clipboard contains either <Full path w/o ext.> or <URL> pseudo-tag, the plugin will prompt you to match tracks according to it or use the track displayed order as earlier.
3. There was (and is) the restriction that requires that the number of tracks from which the tags have been copied must be equal to the number of tracks to which the tags are pasted. this restriction can be violated in case of matching tracks by paths.

possible usage:

1. backup tags for selected tracks (plugin backup/restore feature always backup entire library though tags can be restored for selected tracks only).
2. copy tags form old format tracks to e.g. higher quality tracks.

note: it's debug version. i'll recompile it in release mode in couple of days if no bugs are reported.

https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 23, 2024, 03:58:23 PM
Latest release build:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 27, 2024, 10:07:03 AM
Critical bug fixes related to plugin window minimizing/hiding:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 28, 2024, 08:40:22 PM
New setting "Use custom font" (along with already existing setting "Use MusicBee font"), minor bug fixes, minor UI improvements:

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Mafios on January 29, 2024, 11:48:58 AM
Thanks for the fixes you made, it's now working well. I'm curious about the right-click menu if it's meant to have the lesser but maybe more common options than what it shows in the Tools menu?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 29, 2024, 01:03:21 PM
@Mafios, i agree with you.

@All, which context menu items should i leave in context menu on reducing their count?

-----------------------

1. Critical bug fix: some plugin windows (e.g., ASR) weren't shown at all if the "Use MusicBee font" option was on.

2. Minor UI improvements.

EDIT:

3. ASR preset names/descriptions typos are fixed. you might want to re-install predefined presets.

https://www.mediafire.com/file/h2t08o9562efboi/mb_TagTools_latest.zip/file

Full plugin package:

https://www.mediafire.com/file/b6jrq6nlkkcrxbv/Additional-Tagging-Tools-Plugin.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Mafios on January 30, 2024, 01:07:26 AM
@Mafios, i agree with you.

@All, which context menu items should i leave in context menu on reducing their count?
I meant if the right-click menu is meant to already have less options than the Tools menu at the moment. Because I'm not seeing certain options there like I used to in previous versions.

In fact, after just updating to the most recent one, both Swap Tags and ASR options are gone from the right-click menu.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 30, 2024, 02:01:43 AM
which context menu items should i leave in context menu on reducing their count?
I don't find the right-click context menu over crowded. However, the ones that I use the most and would not want to see removed, are
Copy Tag...
Swap Tag...
Change Case...
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2024, 10:46:54 AM
@phred, I've already removed the 'swap tags' item. Okay, I'll restore it.
Title: Re: Additional Tagging & Reporting Tools
Post by: Mbnation84 on January 30, 2024, 11:31:09 AM
hi,

thank you for your reply earlier.

1) how do i choose what columns i want? (as they dont seem to let me edit in anyway)
2) is there a way to just have album covers on the page for example side by side

sorry i am a noob at this
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2024, 01:10:21 PM
I meant if the right-click menu is meant to already have less options than the Tools menu at the moment. Because I'm not seeing certain options there like I used to in previous versions.

ahh. misunderstood you. yes, the context menu contains only commands that are meant to be mainly applied to selected tracks, e.g., all tag backups (except for tag history) are removed from it, or LR is removed. LR can be applied to selected tracks, but that's not the main purpose of this command.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on January 30, 2024, 01:14:49 PM
1) how do i choose what columns i want? (as they dont seem to let me edit in anyway)

if i understood correctly what your issue is, you can't edit predefined LR presets, but you can copy them and edit the copies as you want.

2) is there a way to just have album covers on the page for example side by side

not sure what you mean, mockup could help. try to edit copies of 'cd booklets' or 'albums and tracks' presets.
Title: Re: Additional Tagging & Reporting Tools
Post by: Mbnation84 on January 30, 2024, 01:33:22 PM
1) how do i choose what columns i want? (as they dont seem to let me edit in anyway)

if i understood correctly what your issue is, you can't edit predefined LR presets, but you can copy them and edit the copies as you want.

2) is there a way to just have album covers on the page for example side by side

not sure what you mean, mockup could help. try to edit copies of 'cd booklets' or 'albums and tracks' presets.


it wont let me edit anything in the presets, also i have a mockup image but i cant attach it here. if you imagine in itunes (dependinh on the view selected) you havethe album covers side by side with name underneath, so you its very visual rather that listed tracks and album.

what i am trying to achieve is to be able to print the cover art and names (Not tracks or anything else) where you have 3/4 album covers on the same line when printing, however it would only work with a pdf i believe.  does that explain it a little better?

also when i played around with exporting it would not show the image, just shows a musical note, and thats on the cd booklet and album and tracks, the preview dont match the export file either
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on January 30, 2024, 01:51:18 PM
@phred, I've already removed the 'swap tags' item. Okay, I'll restore it.
Sorry for not replying earlier, boroda. I didn't mean to cause you extra work, but thank you for restoring the Swap Tags function to the context menu.
Title: Re: Additional Tagging & Reporting Tools
Post by: Mafios on January 31, 2024, 04:22:18 AM
ahh. misunderstood you. yes, the context menu contains only commands that are meant to be mainly applied to selected tracks, e.g., all tag backups (except for tag history) are removed from it, or LR is removed. LR can be applied to selected tracks, but that's not the main purpose of this command.
I see. I didn't know such changes were being made as I was updating and thought it was some kind of issue.

Besides the ones suggested earlier, I like to have the ASR option again.
Title: Re: Additional Tagging & Reporting Tools
Post by: Fivda on February 02, 2024, 12:25:26 PM
So for some reason it seems like the Copy Tag (clipboard > basically any field) featureu seems to ignore my line breaks, and i'm not sure why. I've tried to copy tracklists manually and it still won't work, so this definitly doesn't have to do with myescrewing up on my end with notepad++ and my macros to copy tracklists from VGMdb or something. It's something to do with the copy clipboard to tag option and i have no idea what it is, it just stopped working one day and the next. I tried reinstalling the plugin but it still doesn't parse them properly.

(https://fivda.s-ul.eu/6R2c5eA6)
(https://fivda.s-ul.eu/3M1Y9FQe)

It keeps propagating all different lines as just a single one, as you can see here.
(https://fivda.s-ul.eu/aQmNczHN)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 02, 2024, 12:41:57 PM
So for some reason it seems like the Copy Tag (clipboard > basically any field) featureu seems to ignore my line breaks, and i'm not sure why. I've tried to copy tracklists manually and it still won't work, so this definitly doesn't have to do with myescrewing up on my end with notepad++ and my macros to copy tracklists from VGMdb or something.
Can you post a screenshot of what you have pasted in notepad++ using 'Show All Characters', like this?:

(https://i.imgur.com/nuBfSp7.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: Fivda on February 02, 2024, 12:44:51 PM
So for some reason it seems like the Copy Tag (clipboard > basically any field) featureu seems to ignore my line breaks, and i'm not sure why. I've tried to copy tracklists manually and it still won't work, so this definitly doesn't have to do with myescrewing up on my end with notepad++ and my macros to copy tracklists from VGMdb or something.
Can you post a screenshot of what you have pasted in notepad++ using 'Show All Characters', like this?:

(https://i.imgur.com/nuBfSp7.png)
(https://fivda.s-ul.eu/zkp4eIYM)
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 02, 2024, 12:51:05 PM
(https://fivda.s-ul.eu/zkp4eIYM)
So you have CR (carriage return) missing.
That's why AT&RT will consider the input as a single line.

You should probably be looking at how you have setup your macro's to copy text to the clipboard.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on February 02, 2024, 01:02:28 PM
...also i have a mockup image but i cant attach it here.
You have to upload the screenshot file to a file hosting service such as imgur.com and then paste the provided link here. See my signature below for additional instructions regarding posting screenshots.
Title: Re: Additional Tagging & Reporting Tools
Post by: Fivda on February 02, 2024, 01:42:48 PM
(https://fivda.s-ul.eu/zkp4eIYM)
So you have CR (carriage return) missing.
That's why AT&RT will consider the input as a single line.

You should probably be looking at how you have setup your macro's to copy text to the clipboard.

This isn't an issue on my macro. The text here isn't even due to a macro, nor has it changed ever since. Text from my screen was manually input. Even a regular manual linebreak doesn't desplay a carriaage return character, and i've never had to manually add it to my macro or any kind of text.
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 02, 2024, 01:48:26 PM
Text from my screen was manually input. Even a regular manual linebreak doesn't desplay a carriaage return character, and i've never had to manually add it to my macro or any kind of text.
Then something must have changed with your notepad++ settings.
E.g. check this:

(https://i.imgur.com/hF2XV7Qm.jpg) (https://i.imgur.com/hF2XV7Q.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: Fivda on February 02, 2024, 01:54:39 PM
Text from my screen was manually input. Even a regular manual linebreak doesn't desplay a carriaage return character, and i've never had to manually add it to my macro or any kind of text.
Then something must have changed with your notepad++ settings.
E.g. check this:

(https://i.imgur.com/hF2XV7Qm.jpg) (https://i.imgur.com/hF2XV7Q.png)

(https://fivda.s-ul.eu/L2LWxu9Y)
Exact same...
Title: Re: Additional Tagging & Reporting Tools
Post by: hiccup on February 02, 2024, 01:59:37 PM
Exact same...
That's very strange.
With the setting like that notepad++ should be adding [CR][LF] at the end of a line when you press [Enter]
So in your case that is not happening?

Are you testing this with new documents created in notepad++ , or with existing documents that you open with notepad++ that perhaps are already in some UNIX formatting?
Title: Re: Additional Tagging & Reporting Tools
Post by: Fivda on February 02, 2024, 02:46:49 PM
Exact same...
That's very strange.
With the setting like that notepad++ should be adding [CR][LF] at the end of a line when you press [Enter]
So in your case that is not happening?

Are you testing this with new documents created in notepad++ , or with existing documents that you open with notepad++ that perhaps are already in some UNIX formatting?

Holy crap i think that was it. i was just in a generic unsaved "new1" file all this time so i didn't think about closing the file itself and reloading it from scratch, so i guess i must have pressed a hotkey that deactivated it in the file itself or something...? well at least now it works and that's what matters. thanks a lot
Title: Re: Additional Tagging & Reporting Tools
Post by: theonecynic on February 03, 2024, 05:26:32 AM
Hi,

I've been having some problems with Auto Rate Tracks and Calculate Average Album Rating. I can run Auto Rate Tracks once, but on any subsequent run I get the following error message:

Code
MusicBee v3.5.8698.34385D  (Win10.0), 3 Feb 2024 5:09:

System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
   at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
   at MusicBeePlugin.Plugin.ThemedBitmapAddRef(Form form, Bitmap bitmap)
   at MusicBeePlugin.AutoRateCommand.initializeForm()
   at MusicBeePlugin.PluginWindowTemplate.PluginWindowTemplate_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.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)

After I get this error, when I close MusicBee I get another error:

Code
MusicBee v3.5.8698.34385D  (Win10.0), 3 Feb 2024 5:12:

System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
   at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
   at MusicBeePlugin.Plugin.FormsThemedBitmapsRelease(Form form)
   at MusicBeePlugin.PluginWindowTemplate.PluginWindowTemplate_FormClosed(Object sender, FormClosedEventArgs e)
   at System.Windows.Forms.Form.OnFormClosed(FormClosedEventArgs e)
   at System.Windows.Forms.Form.WmClose(Message& m)
   at System.Windows.Forms.Form.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)

and then immediately one more:

Code
MusicBee v3.5.8698.34385D  (Win10.0), 3 Feb 2024 5:14:

System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
   at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
   at MusicBeePlugin.Plugin.FormsThemedBitmapsRelease(Form form)
   at MusicBeePlugin.PluginWindowTemplate.PluginWindowTemplate_FormClosed(Object sender, FormClosedEventArgs e)
   at System.Windows.Forms.Form.OnFormClosed(FormClosedEventArgs e)
   at System.Windows.Forms.Form.WmClose(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at #=zU1NHuKSwN_K6TEY_Nc8bgw4=.WndProc(Message& #=zUkWzezk=)
   at #=zxdPeeS9uFa8oJzGFQK7gQYcaPZA_.WndProc(Message& #=zUkWzezk=)
   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)

If I try Calculate Average Album Rating at this point, I get this error:
Code
MusicBee v3.5.8698.34385D  (Win10.0), 3 Feb 2024 5:17:

System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
   at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
   at MusicBeePlugin.Plugin.ThemedBitmapAddRef(Form form, Bitmap bitmap)
   at MusicBeePlugin.CalculateAverageAlbumRatingCommand.initializeForm()
   at MusicBeePlugin.PluginWindowTemplate.PluginWindowTemplate_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.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)

... and again, errors when I close MusicBee.  At this point I have to end MusicBee in Task Manager.

 If I go into AppData/Romaing/MusicBee and delete mb_TagTools.settings.xml, then I can again run auto rate tracks once, but only once.

If I try using Calculate Average Album Rating, having deleted mb_TagTools.settings.xml; I see the notification in the bar where it would normally show rating progress "Error - Failed to compare two elements in the array."

I'm using plugin version 8.0.8790.17280, and I'm running Windows 10.

Is there any chance someone could please help me with these problems?

Thank you!
Title: Re: Additional Tagging & Reporting Tools
Post by: theonecynic on February 09, 2024, 02:37:42 AM
I've noticed that I don't get the dialogue box errors unless I turn on "auto calculate thresholds on startup" or "auto rate on startup". I still get the album rating one though.
Title: Re: Additional Tagging & Reporting Tools
Post by: ConspiracyPizza on February 12, 2024, 05:00:56 AM
I'm trying to make a custom tag for total plays of an album, the preview looks good and works properly, but when I run it, it just tags every track with it's own individual play count. What am I doing wrong here? Thank you!

(https://i.imgur.com/TTfOWZ2.png)(https://i.imgur.com/avJ6mma.png)
Title: Re: Additional Tagging & Reporting Tools
Post by: ChriUwe on February 25, 2024, 05:20:52 PM
Virtual Tag1 = $TitleCase(<title>)

How can I adjust the title formatting here?
$TitleCase("hit-mix") leads to Hit-mix.
But Hit-Mix would be correct.
Can this be changed?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 02, 2024, 02:55:31 PM
@phred, hiccup, thanks for your support.

@all others:

new plugin version contains many UI/UX bug fixes, so please try new version (8.1) first, then repost bug reports if some bugs are not yet fixed.

1. numerous UI/UX bug fixes. most bugs were very rare, but important.
2. better auto-generated skin colors (but it's obvious that auto-generated colors can't match the colors of any possible skin).
3. scroll bars are now skinned.
4. plugin now includes help files (.chm format, english and russian files). make sure to copy .chm files to 'plugins' folder in case of plugin manual quick update (or don't use 'help' item of plugin's menu).

* 'swap tags' command is restored in context menu.
* plugin's menus are now always dynamically updated. MB restart is never required anymore for menu update.
* it's known visual glitch that second function parameter (LR window) is always shown (must be shown for 'average' and 'average count' functions only). i'll fix this glitch today or tomorrow.

Virtual Tag1 = $TitleCase(<title>)

How can I adjust the title formatting here?
$TitleCase("hit-mix") leads to Hit-mix.
But Hit-Mix would be correct.
Can this be changed?

it's not possible at the moment, but this should be an easy fix. i'll try to upload a new plugin version tomorrow.

ahh. misunderstood you. yes, the context menu contains only commands that are meant to be mainly applied to selected tracks, e.g., all tag backups (except for tag history) are removed from it, or LR is removed. LR can be applied to selected tracks, but that's not the main purpose of this command.
I see. I didn't know such changes were being made as I was updating and thought it was some kind of issue.

Besides the ones suggested earlier, I like to have the ASR option again.

i've removed both ASR and LR commands from context menu, but you can tick 'assign hotkey' to ASR/LR presets, then those presets will appear in both main and context menus (in submenu), even if you don't actually assign hotkeys to them in MB prefs.

i'd like to get feedback on this change.

-------------------------

https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 02, 2024, 03:25:53 PM
I'm trying to make a custom tag for total plays of an album, the preview looks good and works properly, but when I run it, it just tags every track with it's own individual play count. What am I doing wrong here? Thank you!

(https://i.imgur.com/TTfOWZ2.png)(https://i.imgur.com/avJ6mma.png)

you must define at least 1 grouping field (define some unused/empty custom tag, for example). i vaguely recall that i've fixed this issue, and now LR should work without defining any gouping fields, but i'm not sure about this. please recheck using the updated plugin version, and let me know if it's not fixed and is important for you.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on March 02, 2024, 06:41:20 PM
3. scroll bars are now skinned.
Well, most of the scroll-bars are skinned - the main ASR one seems to have 2 scrollbars now...
(https://i.imgur.com/yT2MRLY.png)

And I might add that this last package doesn't seem to contain the usual folder of ASR Presets (for those who may be downloading it for the first time...)
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on March 02, 2024, 10:27:44 PM
https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Is this current version a "debug" or a "beta"?
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on March 02, 2024, 11:55:53 PM
Is anyone else having problems with getting $LR(<URL>,'virtual tag function ID') to work in a virtual tag?

The Library Report preview shows it works fine but when I try to use the results in a virtual tag the resulting output is either
Code
???
or '0'
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 05:26:35 AM
https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Is this current version a "debug" or a "beta"?

i've tested this version (well, maybe not very carefully), so i'd consider it "debug". it includes debug info (.pdb file) for better error reporting. i'll remove debug info from the final version.

Is anyone else having problems with getting $LR(<URL>,'virtual tag function ID') to work in a virtual tag?

The Library Report preview shows it works fine but when I try to use the results in a virtual tag the resulting output is either
Code
???
or '0'

it seems that i know what the problem is. i'll check my suggestion and upload the fixed version today.

3. scroll bars are now skinned.
Well, most of the scroll-bars are skinned - the main ASR one seems to have 2 scrollbars now...
(https://i.imgur.com/yT2MRLY.png)

And I might add that this last package doesn't seem to contain the usual folder of ASR Presets (for those who may be downloading it for the first time...)

strange, but i don't see this glitch. maybe i've fixed it already. please recheck it using the new version, which i'll upload later.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 08:16:49 AM
Virtual Tag1 = $TitleCase(<title>)

How can I adjust the title formatting here?
$TitleCase("hit-mix") leads to Hit-mix.
But Hit-Mix would be correct.
Can this be changed?

it turned out that this has been implemented from the beginning. open 'change case' command, add '-' to the field 'symbols to treat as word splitters', then click 'ASR' button to the right of this field.

3. scroll bars are now skinned.
Well, most of the scroll-bars are skinned - the main ASR one seems to have 2 scrollbars now...
(https://i.imgur.com/yT2MRLY.png)

please recheck this issue using new version.

BTW, what did you mean by 'most' (except for those doubled scroll bars in ASR)?

Is anyone else having problems with getting $LR(<URL>,'virtual tag function ID') to work in a virtual tag?

The Library Report preview shows it works fine but when I try to use the results in a virtual tag the resulting output is either

 or '0'

i wasn't able to reproduce this bug, but i have found another critical bug (it related to the $LR function only, not to the LR command). i've fixed it. try new version.

------------------------

https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on March 03, 2024, 08:44:18 AM
please recheck this issue using new version.

BTW, what did you mean by 'most' (except for those doubled scroll bars in ASR)?
Nope, scrollbar issue remains - strange that all the other scrollbars are fine, it's (as far as I have seen) just the main ASR one that's bugged.  Tried switching in and out of "use skin colours", even other skins, but no change.  (I just used the word 'most' because I hadn't tested for all of them at that time - I haven't seen any others in ALR either.)
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on March 03, 2024, 10:58:20 AM
Is anyone else having problems with getting $LR(<URL>,'virtual tag function ID') to work in a virtual tag?

The Library Report preview shows it works fine but when I try to use the results in a virtual tag the resulting output is either

 or '0'

i wasn't able to reproduce this bug, but i have found another critical bug (it related to the $LR function only, not to the LR command). i've fixed it. try new version.
No luck. Still not importing results from LR to VirtualTag

Library Report shows correct results
(http://i.imgur.com/sK8DwBG.jpg) (https://imgur.com/sK8DwBG)
I normally wouldn't include the Album grouping, That's just show the Album names for the screenshot  ;)

Virtual Tag configuration is correct
(http://i.imgur.com/FzJpz9s.jpg) (https://imgur.com/FzJpz9s)

But result is not correct
(http://i.imgur.com/YuiLAgR.jpg) (https://imgur.com/YuiLAgR)

If I set the virtual tag formula as just
Code
$LR(<URL>,KindCount)
it shows that it if just returning a value of '1'
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 11:35:56 AM
@Bee-liever, just as a guess: what happens if you define virtual tag as:

Code
$LR("<URL>",KindCount)

?
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 11:39:04 AM
@Messiaen, what Windows version do you use? also, please check the scroll bars in LR (you'll need to create several dummy/empty presets to see scroll bars).

only ASR and LR use the CheckedListBox control (for preset lists). all other commands use other controls (TextBox, ListBox, etc.)
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 11:40:06 AM
cosmetic UI/UX fixes, minor code cleanup:

https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on March 03, 2024, 11:47:04 AM
@Messiaen, what Windows version do you use? also, please check the scroll bars in LR (you'll need to create several dummy/empty presets to see scroll bars).
Oops, yeah, LR seems to suffer this problem too - I just didn't have enough presets to see it.

Standard boring Win10.  (And, just for the record, the issue persists in the version you just uploaded above whilst I was typing.)
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on March 03, 2024, 11:49:47 AM
@Bee-liever, just as a guess: what happens if you define virtual tag as:

Code
$LR("<URL>",KindCount)

?

Returns nothing (or a null character)
MB does save the syntax though
Title: Re: Additional Tagging & Reporting Tools
Post by: Bee-liever on March 03, 2024, 11:58:59 AM
Don't think it would interfere with your plugin but just in case, MBs own
Code
$Count(<Kind>,<Album>)
doesn't work either.
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 03:34:51 PM
@Bee-liever, i'll have a closer look at your issue today.

Standard boring Win10.  (And, just for the record, the issue persists in the version you just uploaded above whilst I was typing.)

hrr... the same version as mine. well, another try:

https://www.mediafire.com/file/odmp6wgn9hg7hfi/mb_TagTools_debug.zip/file
Title: Re: Additional Tagging & Reporting Tools
Post by: boroda on March 03, 2024, 04:07:25 PM
EDITED

forgot to mention changes in the last version.

$TitleCase and $SentenceCase now have extended syntax:

$TitleCase(input,exceptionWords,wordSplittersASRString,exceptionCharsASRString)
$SentenceCase (input,exceptionWords)

if exceptionWords, wordSplittersASRString or exceptionCharsASRString are completely empty, then ASR defaults are used. if they are whitespaces, then the function won't use any exception words, exception characters, or word splitters at all (excepted words are lowercased by these functions (besides the first and last word of the input string for the $TitleCase function),  words following exception characters are lowercased, and words after 'word splitters' will be capitalized). all characters and words must be separated by spaces. any number of the last parameters can be omitted. they will use ASR defaults in this case.

examples:

Code
$TitleCase("test", ,/ - &) is the same as:

$TitleCase("test", ,/ - &,) i.e., don't use excepted words, use characters / - & as word splitters, and use ASR defaults for characters after which the words must be lowercased.

Code
$TitleCase("test") is the same as:

$TitleCase("test",,,) i.e., use ASR defaults for excepted words, word splitters (spaces are always treated as word splitters), and characters after which the words must be lowercased.
Title: Re: Additional Tagging & Reporting Tools
Post by: Messiaen on March 03, 2024, 05:17:56 PM
well, another try:
And there we go - now all the scrollbars are working/appearing as advertised.  :)

Thank you.
Title: Re: Additional Tagging & Reporting Tools
Post by: ChriUwe on March 03, 2024, 05:51:27 PM
Unfortunately I get an error message:

(https://i.postimg.cc/svf3mHjn/Musicbee-2024-03-03-184933.png) (https://postimg.cc/svf3mHjn)
Title: Re: Additional Tagging & Reporting Tools
Post by: ChriUwe on March 04, 2024, 05:50:54 AM
If I integrate the latest version of the plugin, I also get this error message:

(https://i.postimg.cc/FdBDMccX/Music-Bee-2024-03-04-064638.png) (https://postimg.cc/FdBDMccX)

MusicBee v3.6.8816.34740D  (Win10.0), 4 Mrz 2024 6:45:

System.ArgumentNullException: Der Wert darf nicht NULL sein.
Parametername: brush
   bei System.Drawing.Graphics.FillRectangle(Brush brush, Int32 x, Int32 y, Int32 width, Int32 height)
   bei System.Drawing.Graphics.FillRectangle(Brush brush, Rectangle rect)
   bei MusicBeePlugin.CustomVScrollBar.OnPaint1(PaintEventArgs e, Image upArrowImage, Image downArrowImage, Image thumbTopImage, Image thumbMiddleImage, Image thumbBottomImage, Boolean stretchThumbImage)
   bei MusicBeePlugin.CustomVScrollBar.OnPaint(PaintEventArgs e)
   bei System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   bei System.Windows.Forms.Control.WmPaint(Message& m)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   bei System.Windows.Forms.ContainerControl.WndProc(Message& m)
   bei System.Windows.Forms.UserControl.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

(https://i.postimg.cc/Sj96SwbM/Music-Bee-2024-03-04-064836.png) (https://postimg.cc/Sj96SwbM)
Title: Re: Additional Tagging & Reporting Tools
Post by: ChriUwe on March 17, 2024, 11:02:09 AM
Is there no more support here?
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on March 17, 2024, 11:36:39 AM
Is there no more support here?
What do you mean? :/
Title: Re: Additional Tagging & Reporting Tools
Post by: ChriUwe on March 17, 2024, 12:30:46 PM
If I integrate the latest version of the plugin, I also get this error message:

(https://i.postimg.cc/FdBDMccX/Music-Bee-2024-03-04-064638.png) (https://postimg.cc/FdBDMccX)

MusicBee v3.6.8816.34740D  (Win10.0), 4 Mrz 2024 6:45:

System.ArgumentNullException: Der Wert darf nicht NULL sein.
Parametername: brush
   bei System.Drawing.Graphics.FillRectangle(Brush brush, Int32 x, Int32 y, Int32 width, Int32 height)
   bei System.Drawing.Graphics.FillRectangle(Brush brush, Rectangle rect)
   bei MusicBeePlugin.CustomVScrollBar.OnPaint1(PaintEventArgs e, Image upArrowImage, Image downArrowImage, Image thumbTopImage, Image thumbMiddleImage, Image thumbBottomImage, Boolean stretchThumbImage)
   bei MusicBeePlugin.CustomVScrollBar.OnPaint(PaintEventArgs e)
   bei System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   bei System.Windows.Forms.Control.WmPaint(Message& m)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   bei System.Windows.Forms.ContainerControl.WndProc(Message& m)
   bei System.Windows.Forms.UserControl.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

(https://i.postimg.cc/Sj96SwbM/Music-Bee-2024-03-04-064836.png) (https://postimg.cc/Sj96SwbM)

I described my problem here on March 03.
Title: Re: Additional Tagging & Reporting Tools
Post by: ChriUwe on March 17, 2024, 12:31:35 PM
Unfortunately I get an error message:

(https://i.postimg.cc/svf3mHjn/Musicbee-2024-03-03-184933.png) (https://postimg.cc/svf3mHjn)

I described my problem here on March 03.
Title: Re: Additional Tagging & Reporting Tools
Post by: Mayibongwe on March 17, 2024, 12:34:47 PM
Oh yeah right, one of our mods better give boroda a hiding in that case then.
It's really unacceptable that he hasn't been glued to his computer attending to these reports from two weeks ago.
Title: Re: Additional Tagging & Reporting Tools
Post by: phred on March 17, 2024, 12:38:03 PM
I described my problem here on March 03.
This is a user-to-user forum. Answers to questions are handled by fellow users. This plugin is maintained by one person who volunteers his time to keep the plugin updated and to provide support. He is not an employee of MB. He does not get paid. He has a life. He responds to plugin issues when he has the time.

Be patient.