# Making multiple changes in one move

**URL:** https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280
**Category:** Support
**Created:** [July 13, 2024, 10:36pm UTC](https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280 "2024-07-13T22:36:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![cmach1](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/46a35a/32.png) [@cmach1](https://community.mp3tag.de/u/cmach1)
#### Post date: [July 13, 2024, 10:36pm UTC](https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280/1 "2024-07-13T22:36:57Z")

</div>

Here's my example. I have a folder titled  
**De Wolfe DW\_LP 2975 - Town Beat (1966)**

I want to put that text in the album field using tag-tag, but I would like to not include the **(1966)** portion and I would also like to replace the underscore with a forward slash. So that it ends up looking like this in the album field:  
**De Wolfe DW/LP 2975 - Town Beat**

I have used $cutright(%\_directory%, 7) to eliminate the year, but that still leaves the underscore-forward slash issue. So as of now, I can't make all the necessary changes I want in one move. Is it possible to do this?

---

<div class="post-metadata">

### Author: ![rboss](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/r/5f9b8f/32.png) [@rboss](https://community.mp3tag.de/u/rboss)
#### Post date: [July 14, 2024, 12:46am UTC](https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280/2 "2024-07-14T00:46:10Z")

</div>

You'll need to chain the functions together. This is called nesting.  
Mp3Tag has the `$replace(string,from,to)` function, where `string` is what will be evaluated, `from` is what is to be replaced, and ` to` is what `from` is to be replaced with.

Building from your example,  
`$replace($cutright(%_directory%,7),_,/)`

This reads: "Replace all instances of "\_" with "/" in `string`, where `string` is `$cutright(%_directory%, 7)`".

Hope this helps.

---

<div class="post-metadata">

### Author: ![cmach1](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/46a35a/32.png) [@cmach1](https://community.mp3tag.de/u/cmach1)
#### Post date: [July 14, 2024, 1:00am UTC](https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280/3 "2024-07-14T01:00:12Z")

</div>

> [@rboss](#):
>
> $replace($cutright(%_directory%,7),_,/)

That worked beautifully. Thank you.

---

<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: [July 14, 2024, 6:39am UTC](https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280/4 "2024-07-14T06:39:15Z")

</div>

> [@cmach1](#):
>
> Here's my example. I have a folder titled  
> **De Wolfe DW\_LP 2975 - Town Beat (1966)**
> 
> I want to put that text in the album field using tag-tag

I find this apporach most astounding:  
Why the restriction to do it

> [@cmach1](#):
>
> in one move

and why the restriction to do it with

> [@cmach1](#):
>
> tag-tag

?  
Of course, there are many ways to scin a cat but if you have found a way to get the data from the

> [@cmach1](#):
>
> folder

into the album field, then the syntax should already be clear for Convert\>Filename-Tag:  
`%album% (%dummy%)\%dummy%)`  
The almost equivalent as an action for the converter is "Guess value".  
So the souce in "Guess value" would be:  
Source string: `$replace(%_directory%,_,/)`  
Target format string: `%album% (%dummy%)`  
This has the discrete charme not to fail because the year is shorter or longer.

---

<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: [August 13, 2024, 6:40am UTC](https://community.mp3tag.de/t/making-multiple-changes-in-one-move/65280/5 "2024-08-13T06:40:10Z")

</div>

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