Additional Tagging & Reporting Tools

[boroda]

Version 9.2 Update 12 (9.2.9191)

* Help files update

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

Full plugin package:

https://www.mediafire.com/file/dm3rhfze89n3qwi/Additional-Tagging-Tools-Plugin.zip/file

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

Full change log since v9.1:

* Documentation update
* ASR UI bug fixes
* "Copy tags to clipboard" bug fix, when using skin colors
* ASR preset auto-execution/LR preset chaining fixed
* ASR UI/UX bug fixes using skin colors
* ASR presets "Add up to # leading zeros to first group of digits of <Tag 1>" have been fixed
* ASR/MSR bug fixes
* General critical bug fix
* Huge code refactoring. Many UI/UX bug fixes related to ASR/MSR and Change Case
+ "Change Case" presets
+ New command "Custom sorting for Column browser"
* Some UI and skin colors adjustments
+ New ASR preset attribute: "Hidden preset". You can enable displaying hidden presets using corresponding ASR filtering button, but unlike all other filtering buttons, clicking the button "Show hidden presets" will show BOTH hidden and generic presets
+ Now ASR presets can be "chained". You can assign to any ASR preset the next preset that will be executed right after the execution of the given preset. You can search the next preset to be selected in the "next preset" combo box by typing part or some parts of searched preset name. The searching works much better if skin coloring is on.
You can show all presets included in the chain containing the currently selected preset by clicking "filter" button next to button to clear next preset search field. Preset chain won't be auto-executed in interactive mode (with preview), but you can easily go to the next preset in the chain by clicking button "☛" for manual execution of the next preset. Alternatively, you can assign hotkey to preset by ticking check box "Assignt hotkey". ASR presets with "assigned" hotkeys will appear in plugin main and context menu, even if you haven't *actually* assigned hotkeys to them, but only ticked corresponding check box. Preset chains will be completely executed if you manually invoked (or ticked for auto-execution on tag changes) the first preset by hotkey or plugin menu item (i.e. not using ASR interactive mode).
You can use preset chains when five available preset replacements steps are insufficient or simply to chain independent existing presets

[boroda]

I can't figure out how to produce the values of one or more existing tags.

Suppose that I want to produce: Artist - Title
Looking at what I was able to find on the matter, I came up with:

Code

\@eval[[<Artist> - <Title>]]

But that doesn't work.
Am I doing something wrong with the syntax, or do I misunderstand how @eval works?

(I tried some variations using double quotes, and even double double-quotes that I saw in existing presets, but I still couldn't get it to work)

working fine for me. what are you searching for? it's important because replacement step is skipped if there are 0 matches in search pattern. search any tag for "^(.*)". it will always match the entire tag.

[boroda]

Version 9.2 Update 12 (9.2.9191)

* More help files updates

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

Full plugin package:

https://www.mediafire.com/file/dm3rhfze89n3qwi/Additional-Tagging-Tools-Plugin.zip/file

[boroda]

Updated custom ASR presets pack (not distributed with plugin, less important than predefined presets):

https://www.mediafire.com/file/ikb8wlburvvwjc9/ASR-Custom-Presets.zip/file

[miste]

I think in the new version, the preset "Remove all artist from Display Artist" is removing the artist field completely.

[boroda]

@miste, i haven't changed anything related for the very long time. resulting screenshot with empty tags is not helpful. please post the same screenshot before executing preset that erases tags. there are some requirement how "displayed artist" can be formatted. (i.e. not any format is accepted)

[miste]

@miste, i haven't changed anything related for the very long time. resulting screenshot with empty tags is not helpful. please post the same screenshot before executing preset that erases tags. there are some requirement how "displayed artist" can be formatted. (i.e. not any format is accepted)

Thanks for the reply, sure, I'll share some other screenshots
First I tried Artist 1 / Artist 2 and then Artist 1; Artist 2

In both cases, after applying the preset, the Artist tag and Display Artist are deleted

Artist 1 / Artist 2



Preview



Result



 Artist 1; Artist 2



I always used the standard  Artist 1 / Artist 2 or Artist 1; Artist 2 and had been working fine so far

[boroda]

@miste, it's strange that this preset was working earlier.

https://www.mediafire.com/file/uwkei4zqw9x9jno/Remove+all+artists+from+the+''Displayed+Artist''+tag+except+the+first+one.asr-preset.zip/file

unzip, open ASR, click "import" button. DON'T import as NEW preset! (you will be asked)

[miste]

@miste, it's strange that this preset was working earlier.

https://www.mediafire.com/file/uwkei4zqw9x9jno/Remove+all+artists+from+the+''Displayed+Artist''+tag+except+the+first+one.asr-preset.zip/file

unzip, open ASR, click "import" button. DON'T import as NEW preset! (you will be asked)

This worked now!

[boroda]

Version 9.2 Update 14 (9.2.9193)

* "Custom Sorting for Column Browser" hotkey description corrected

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

Full plugin package:

https://www.mediafire.com/file/dm3rhfze89n3qwi/Additional-Tagging-Tools-Plugin.zip/file

[TRegina]

Hello,

Is it possible to use a word range for the Change Case - Except for Words field?
For example, instead of typing out CD1 CD2 CD3...etc. in the field is there a range I can use?
CD* does not work for me.

Thanks.

[Mayibongwe]

Is it possible to use a word range for the Change Case - Except for Words field?
For example, instead of typing out CD1 CD2 CD3...etc. in the field is there a range I can use?
CD* does not work for me.

Hi there, welcome to the forum.
boroda or someone else will assist you when they get the time. I'm not that familiar with this command yet (it was introduced fairly recently).

In the meantime, I was having a look at MusicBee's native tools > search and replace function to see if it was case-sensitive for a job like this, and it looks like the regex is:
You can add negative lookups to the expression for the "except these words" portion (but that'd be complicated compared to this plugin's command).

[hiccup]

My apologies in advance, since I have an itch at the back of my head that this was asked and answered a while ago already.
But I can't find it in my brain, nor in the forum.

$TagContainsAnyString has this syntax:

Code

$TagContainsAnyString(<URL>,Lyrics,water|river)

I think it would be more intuitive it was:

Code

$TagContainsAnyString(<Lyrics>,water|river)

(I'm guessing you already considered that, but it would maybe limit some other possibilities of this <URL> function?)

[TRegina]

Is it possible to use a word range for the Change Case - Except for Words field?
For example, instead of typing out CD1 CD2 CD3...etc. in the field is there a range I can use?
CD* does not work for me.

Hi there, welcome to the forum.
boroda or someone else will assist you when they get the time. I'm not that familiar with this command yet (it was introduced fairly recently).

In the meantime, I was having a look at MusicBee's native tools > search and replace function to see if it was case-sensitive for a job like this, and it looks like the regex is:
You can add negative lookups to the expression for the "except these words" portion (but that'd be complicated compared to this plugin's command).

I tried various RegEx codes, but they did not work.
It seems to be in some kind of XML code that I was able to view in Notepad.
Thanks for your help, anyway.

[hiccup]

CD* does not work for me.

It won't, because when speaking regex, that would match things like C CD CDD CDDD etc.

I tried various RegEx codes, but they did not work.

Have you tried something like this?:



change 'Title' to the tag that contains cd* in your situation, and add this as a step after your other 'casing' steps


PS
A mandatory read for anyone attempting to use and master regex functions within MusicBee:
karbock's Review of Regular Expressions