# Title has all the details

**URL:** https://community.mp3tag.de/t/title-has-all-the-details/70456
**Category:** Support
**Created:** [January 6, 2026, 11:51pm UTC](https://community.mp3tag.de/t/title-has-all-the-details/70456 "2026-01-06T23:51:54Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![ianwat](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/i/7993a0/32.png) [@ianwat](https://community.mp3tag.de/u/ianwat)
#### Post date: [January 6, 2026, 11:51pm UTC](https://community.mp3tag.de/t/title-has-all-the-details/70456/1 "2026-01-06T23:51:54Z")

</div>

Got an interesting one.

Was helping a friend with mp3tag and all was well.

Until I get a call that starts with oops.

They’ve managed to somehow put most of the meta date into the title field…twice.

So it looks like this.

Ottawan - D.I.S.C.O. ( Dj Vivid 2025 remix ) 123 bpm - Ottawan - D.I.S.C.O. ( Dj Vivid Santana 2025 remix ) 123 bpm

Now I’ve been playing around with tag - tag

and I thought

%artist% - %title% -%mixartist% %bpm% - %dummy%

Should work, but it doesn’t it just puts the big title in the other fields.

Any help would be much appreciated and happy new year !

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [January 7, 2026, 5:57am UTC](https://community.mp3tag.de/t/title-has-all-the-details/70456/2 "2026-01-07T05:57:29Z")

</div>

If the duplicated part of all titles ends with `bpm`, your friend can use an action **Replace with Regular Expression** for field `TITLE` with

Regular Expression: `^(.*? bpm).*`  
Replace matches with: `$1`

* * *

What took me a while to realise is that the two parts in your example are no exact duplicates. The first instance has `Dj Vivid 2025 remix` and the second instance has `Dj Vivid Santana 2025 remix`.

If both parts would be exact duplicates, you could use a back-reference like  
`^(.+?)(?:\s*-\s*\1)$`  
and replace this with `$1`

> **[Replace with Regular Expression – Mp3tag Documentation](https://docs.mp3tag.de/actions/replace-regexp/)**
>
> Documentation on the Replace with Regular Expression action type that can be performed as Quick Action or as reusable workflow from Action Groups. Mp3tag is the universal Tag Editor.

Happy new year to you too!

---

<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: [January 7, 2026, 7:55am UTC](https://community.mp3tag.de/t/title-has-all-the-details/70456/3 "2026-01-07T07:55:24Z")

</div>

> [@ianwat](#):
>
> Ottawan - D.I.S.C.O. ( Dj Vivid 2025 remix ) 123 bpm - Ottawan - D.I.S.C.O. ( Dj Vivid Santana 2025 remix ) 123 bpm
> 
> `%artist% - %title% -%mixartist% %bpm% - %dummy%`  
> but it doesn’t it just puts the big title in the other fields.

That's because your [guessing pattern](https://docs.mp3tag.de/actions/guess/) does not exactly match the real values:  
There is no space and minus character in front of `%mixartist%`, but parentheses around it.  
And the field `BPM` should only contain a number, not **123 bpm**

If you were to use a guessing pattern like this:  
`%artist% - %title% ( %mixartist% ) %bpm% bpm - %dummy%`  
it could work.

As @Florian already wrote above, this only works, if the `TITLE`s of your friends tracks always contain the " **nnn bpm -**" part before the second "duplicated" part starts.

---

<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 6, 2026, 7:56am UTC](https://community.mp3tag.de/t/title-has-all-the-details/70456/4 "2026-02-06T07:56:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
