# Producing DISPLAY COMPOSER using multiple COMPOSER field

**URL:** https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248
**Category:** Support
**Created:** [December 18, 2020, 10:36am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248 "2020-12-18T10:36:53Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![Alfie\_Solomon84](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/7ba0ec/32.png) [@Alfie\_Solomon84](https://community.mp3tag.de/u/Alfie_Solomon84)
#### Post date: [December 18, 2020, 10:36am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/1 "2020-12-18T10:36:53Z")

</div>

To better understand the problem, refer picture

 ![Screenshot 2020-12-18 183128](https://community.mp3tag.de/uploads/default/original/2X/1/1dc759c4b97fc6bbf6bc06d6c410361ce824a9ea.png)  
Upon download, the COMPOSER is already split I would love to retain that.

I want to produce DISPLAY COMPOSER, a tag useful in Musicbee. My problem is that in order for me to do that, I need to **merge** COMPOSER with / separator, \*\* format value\*\* to DISPLAY COMPOSER, **split by expression** of "/" while doing all that, I would like to retain **multiple composer**.

_Any idea on how i should design my Action command?_\*

---

<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: [December 18, 2020, 10:39am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/2 "2020-12-18T10:39:04Z")

</div>

You add a further action to your action group that splits the field again: "Split field by separator"

> **[Split Field by Separator – Mp3tag Documentation](https://docs.mp3tag.de/actions/split-field/)**
>
> Documentation on the Split Field action type that can be performed as Quick Action or as reusable workflow from Action Groups. Mp3tag is the universal Tag Editor.

---

<div class="post-metadata">

### Author: ![Alfie\_Solomon84](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/7ba0ec/32.png) [@Alfie\_Solomon84](https://community.mp3tag.de/u/Alfie_Solomon84)
#### Post date: [December 18, 2020, 10:41am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/3 "2020-12-18T10:41:02Z")

</div>

I see. Meaning to say that the **Actions are done in the order described in the panel and don't happen simultaneously?**

---

<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: [December 18, 2020, 10:44am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/4 "2020-12-18T10:44:36Z")

</div>

I don't know what you mean by panel.  
If you create a new action group with Actions\>Actions ... \> New  
You enter a name for the action group and then add add an action, e.g. the action to merge the field.  
I would then, if this is the routine way of procedure, add the action of the type "Format value" to fill the display composer.  
And finally, add the action to split the field COMPOSER again.  
Now the action group should contain 3 actions:  
Merge  
Format  
Split  
These three steps will be executed in this order every time you call the action group.

---

<div class="post-metadata">

### Author: ![Alfie\_Solomon84](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/7ba0ec/32.png) [@Alfie\_Solomon84](https://community.mp3tag.de/u/Alfie_Solomon84)
#### Post date: [December 18, 2020, 10:48am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/5 "2020-12-18T10:48:03Z")

</div>

"These three steps will be executed in this order every time you call the action group."  
This answers it.

My flow now is merge-\>format-\>replaceregular-\>split.

**Just for future reference, the action group are sequential right?** like I can split, merge and split again, right?

---

<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: [December 18, 2020, 10:50am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/6 "2020-12-18T10:50:27Z")

</div>

Just a hint:  
If you replace a text constant (probably `/`) with another text constant (probably `;`) then you don't need an action of the type "Replace with regular expression" - this is just a plain "Replace" as you do not really define a pattern.

---

<div class="post-metadata">

### Author: ![Alfie\_Solomon84](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/7ba0ec/32.png) [@Alfie\_Solomon84](https://community.mp3tag.de/u/Alfie_Solomon84)
#### Post date: [December 18, 2020, 10:56am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/7 "2020-12-18T10:56:24Z")

</div>

Sorry my brain is foggy, would you mind explaining this further? I understand that sometimes **Replace is sufficient in the place of Replace with regular expression** , but what do you mean by that in my context?

And I'm starting to guess that **Replace with regular expression can do a different job than Replace but I'm not sure in what instance**

Edit: Gotcha. In another post. Lemme correct that real quick

---

<div class="post-metadata">

### Author: ![dano](https://community.mp3tag.de/user_avatar/community.mp3tag.de/dano/32/6_2.png) [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [December 18, 2020, 11:28am UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/8 "2020-12-18T11:28:53Z")

</div>

I think you just need one action:

```
Format value
Field: DISPLAY COMPOSER
Format string: $meta_sep(composer,/)
```

---

<div class="post-metadata">

### Author: ![Alfie\_Solomon84](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/7ba0ec/32.png) [@Alfie\_Solomon84](https://community.mp3tag.de/u/Alfie_Solomon84)
#### Post date: [December 18, 2020, 1:17pm UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/9 "2020-12-18T13:17:46Z")

</div>

that is the thing, I'm not adept at using format string yet I have to rely on set actions.

nevertheless, thank you for the infromation!

---

<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: [December 18, 2020, 1:19pm UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/10 "2020-12-18T13:19:22Z")

</div>

I think, together with the original "replace" it would be:  
`Format string: $meta_sep(composer,; )`

---

<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: [January 17, 2021, 1:19pm UTC](https://community.mp3tag.de/t/producing-display-composer-using-multiple-composer-field/51248/11 "2021-01-17T13:19:24Z")

</div>

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