# Struggling with Regular Expressions

**URL:** https://community.mp3tag.de/t/struggling-with-regular-expressions/16223
**Category:** General Discussion
**Created:** [October 9, 2014, 9:28am UTC](https://community.mp3tag.de/t/struggling-with-regular-expressions/16223 "2014-10-09T09:28:38Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![way2salty](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/w/8797f3/32.png) [@way2salty](https://community.mp3tag.de/u/way2salty)
#### Post date: [October 9, 2014, 9:28am UTC](https://community.mp3tag.de/t/struggling-with-regular-expressions/16223/1 "2014-10-09T09:28:38Z")

</div>

I have been using mp3Tag for years, but I have only just begun using regular expressions, and I am really having problems with them.

I tag my titles in sentence form, which gets complicated when dealing with remixes. Up until now, my solution has always been to add a "Replace" line for each new remixer I come across, meaning my regular action group includes well over 100 lines. I finally discovered REs and this forum a few days ago, and was thrilled when I found a thread with the exact RE I was looking for:

Action type: Replace with regular expression  
Field: TITLE  
Regular expression: ^(.\*?)((|$)  
Replace matches with: $caps3($1)$2

It is perfect, except for one small problem: It doesn't work. At least not for me, it doesn't. The first word after the opening parenthesis remains lowercase, and I don't understand how any of this works well enough to fix it.

Also, is there a way to restrict this change to that it only adds caps to remix information? I haven't gotten far enough with this to see for sure, but I suspect that as is, this RE, should it come across it, would give you something like:

Sweet dreams (are Made Of This) (eric Prydz Mix), or  
Get low (dirty Version)

Can I get it to limit the case change to only strings containing words like mix, remix, edit, dub, etc.? I have not updated since version 2.46 out of fear of losing the action group information I've spent compiling (I'm sure there's a way to move an existing action group to a newer build, but I don't know how, and I'd be too afraid of losing everything even if I did know). This seems to be a much, much better way to go, but at the moment, it is adding as many problems as it is solving.

---

<div class="post-metadata">

### Author: ![JJ\_Johnson](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jj_johnson/32/67_2.png) [@JJ\_Johnson](https://community.mp3tag.de/u/JJ_Johnson)
#### Post date: [October 10, 2014, 11:22pm UTC](https://community.mp3tag.de/t/struggling-with-regular-expressions/16223/2 "2014-10-10T23:22:28Z")

</div>

> [@His Holiness Pops Salty I](#):
>
> Can I get it to limit the case change to only strings containing words like mix, remix, edit, dub, etc.?

Possibly. I assume you also mean within parenthesis, correct? Can we make any other assumptions about those words? For instance, would the word also be the last word within the parenthesis?

> [@](#):
>
> I have not updated since version 2.46 out of fear of losing the action group information I've spent compiling (I'm sure there's a way to move an existing action group to a newer build, but I don't know how, and I'd be too afraid of losing everything even if I did know).

You don't have to worry about that. All of your program settings and action groups are preserved when you update Mp3tag.
