# Custom Tags in Comment field

**URL:** <https://community.mp3tag.de/t/custom-tags-in-comment-field/51947>\
**Category:** Support\
**Created:** [February 12, 2021, 1:13pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947 "2021-02-12T13:13:17Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![chargeproduction](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/e480ec/32.png) [@chargeproduction](https://community.mp3tag.de/u/chargeproduction)\
**Post date:** [February 12, 2021, 1:13pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/1 "2021-02-12T13:13:17Z")

</div>

Hey folks,

Im DJ CHARGE and im Using Serato for my Music Stuff and Library Management. I dont like the fact in Serato that u cannot add multiple Custom Tags like in Rekordbox.

I used the comment field for my custom tags so this can look like this

Artist: Beyonce  
Trackname: Single Ladies  
BPM: 105  
Genre: Dancehall  
**Comment:** BIG ROOM - LADIES - PRIMETIME - SAFER

So this ist how I Tag my Songs. But for better search i need to put a [] for every Tag in the comment

Example: [BIG ROOM] [LADIES] [PRIMETIME] [SAFER]

Some Tracks have diffrent and other tags like here in the picture.

Is it possible to add [] before every word ?

Sorry guys my english is so bad i hope you understand what i need.

Best regards from Germany

 ![capture-20210212-141217](https://community.mp3tag.de/uploads/default/original/2X/0/0f20e577abff60cf8299259d409bdc250314a5df.png)

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [February 12, 2021, 2:05pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/2 "2021-02-12T14:05:35Z")

</div>

You can try Convert Tag -\> Tag or press ALT + 5  
with  
Field: `COMMENT`  
Format String: `$regexp(%COMMENT%,(.+?)( - |$),'['$1']' )`

tested here: [regex101: build, debug and test regex](https://regex101.com/r/Bxh6aj/1)  
(the syntax for square brackets differs for Mp3tag, they have to be enclosed in `'['`)

**But to be honest:**  
I don't see how this new syntax could be "_for better search_"

---

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [February 12, 2021, 3:00pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/3 "2021-02-12T15:00:42Z")

</div>

> [@chargeproduction](#):
>
> Is it possible to add before every word ?

Is it really that you want the brackets around every word? Or do you want them around every term?  
If the first is true, then

> [@chargeproduction](#):
>
> BIG ROOM

should not be

> [@chargeproduction](#):
>
> [BIG ROOM]

but [BIG] [ROOM]  
I quite agree with @LyricsLover:

> [@LyricsLover](#):
>
> I don't see how this new syntax could be "_for better search_"

I consider it as very redundant: if you enclose the terms (which I assume should be the result) in brackets - why do you still need the hypen? This only adds 2 more characters to the whole string (space and hyphen).  
I think you could get rid of these without any loss of information.

Which brings me to another approach - perhaps with 2 actions:  
First: a simple replace where you replace all "space hyphen space" with "] [".  
Than one of the type "Format value" for COMMENT with  
Format string: '['%comment%']'

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [February 12, 2021, 3:04pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/4 "2021-02-12T15:04:56Z")

</div>

> [@ohrenkino](#):
>
> if you enclose the terms (which I assume should be the result) in brackets - why do you still need the hypen?

There are no more hyphens in the above result (and as I understand the OP request). I'm wrong?

---

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [February 12, 2021, 3:09pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/5 "2021-02-12T15:09:48Z")

</div>

Yes, you are right. Sorry to all.

---

<div class="post-metadata">

**Author:** ![Jimmy\_Neutron](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/9de053/32.png) [@Jimmy\_Neutron](https://community.mp3tag.de/u/Jimmy_Neutron)\
**Post date:** [February 12, 2021, 4:05pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/6 "2021-02-12T16:05:09Z")

</div>

I noticed a "BIG ROOM" and "BIGROOM". Did not find the same kind of inconsistency with any of the other two-word comments, but we are presented a small sample of what is probably a large library. It would be a good idea to search for two-word comments both ways and resolve the inconsistencies that are found before trying to bracket the comments.

I suspect that the bracket desire is to prevent finding a search term in an artist or title by mistake.

---

<div class="post-metadata">

**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\
**Post date:** [February 9, 2026, 12:29pm UTC](https://community.mp3tag.de/t/custom-tags-in-comment-field/51947/7 "2026-02-09T12:29:04Z")

</div>


