# Copy individual fields adds field on paste instead of replacing

**URL:** https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740
**Category:** Support
**Created:** [December 1, 2018, 5:55pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740 "2018-12-01T17:55:59Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [December 1, 2018, 5:55pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/1 "2018-12-01T17:55:59Z")

</div>

As I read it here [Mp3tag v2.91 released](https://community.mp3tag.de/t/mp3tag-v2-91-released/43723) there was this new feature

And so I installed the new version and when straight to it. And there is a bug apparently:

**The field is copied - but instead of replacing the existing one, another is created with the same name**  
  
  
I tried different fields, both legit and made up by me. I tried coping between two MP3 files and tried combination like e.g. FLAC \> WV, TTA \> MP3. The result was always the same: a creation of a doppelganger. And what is more, I can multiple that field to infinite numbers / versions, so that for example I can have two GENRE fields with `Rock` and 10 GENRE fields with `Pop` and 1 with `Hip-Hop`, all within one and the same file

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [December 2, 2018, 7:36am UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/2 "2018-12-02T07:36:05Z")

</div>

Confirmed.

I think it is a bug.  
But I like this behaviour as an alternate option if you intentionally want to create multiple tag-fields or just to be sure to not overwrite things by accident. To delete the unwanted content later is easy.

My suggestion therefore: A 4th selection beside Cut, Copy, Paste: "Replace".

---

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [December 2, 2018, 3:43pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/3 "2018-12-02T15:43:53Z")

</div>

> [@poster](#):
>
> [...]  
> I think it is a bug.  
> But I like this behaviour as an alternate option  
> [...]  
> My suggestion therefore: A 4th selection beside Cut, Copy, Paste: "Replace".

It could / should be a choice in Settings: if CTRL + V is to add another field of the same name or to replace [overwrite] it; with the default set [IMHO] to overwrite

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [December 2, 2018, 4:16pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/4 "2018-12-02T16:16:26Z")

</div>

> [@Zerow](#):
>
> It could / should be a choice in Settings: if CTRL + V is to add another field of the same name or to replace [overwrite] it; with the default set [IMHO] to overwrite

I don't think so.  
Hidden in settings it would be much too laborious to use these 2 options.  
Before I change the settings in Mp3Tag in order to create a multi-tag-field this way I would edit the tags manually.

---

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [December 2, 2018, 5:24pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/5 "2018-12-02T17:24:27Z")

</div>

You have a point [poster](https://community.mp3tag.de/u/poster), as I think I understand how you understood me

But what I really had in my was this: [assuming this bug will be left as an option] I would like to be able to turn then that option off- so that in my Mp3tag I would not have at all an additional `Replace` entry in that small menu that now consists of `Cut`, `Copy` and `Paste`. Or to make it informative, rather have the `Replace` not removed completely but have it greyed out [so that looking at that menu I would remember that this was my choice and there is a place somewhere in Settings where I can turn than back on]

---

<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: [December 7, 2018, 2:40pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/6 "2018-12-07T14:40:53Z")

</div>

I've moved this to #support as it's intended behavior. As a workaround for now, just remove any field you don't want to have duplicated.

---

<div class="post-metadata">

### Author: ![xRussianBeautyx](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/x/58f4c7/32.png) [@xRussianBeautyx](https://community.mp3tag.de/u/xRussianBeautyx)
#### Post date: [January 7, 2019, 6:13pm UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/7 "2019-01-07T18:13:57Z")

</div>

> [@poster](#):
>
> My suggestion therefore: A 4th selection beside Cut, Copy, Paste: "Replace".

I was about to suggest the same 👍

---

<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 7, 2021, 10:51am UTC](https://community.mp3tag.de/t/copy-individual-fields-adds-field-on-paste-instead-of-replacing/43740/8 "2021-01-07T10:51:12Z")

</div>

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