# Extended view changes the order of multivalue components

**URL:** https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [December 15, 2020, 7:43am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213 "2020-12-15T07:43:52Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![vkostas](https://community.mp3tag.de/user_avatar/community.mp3tag.de/vkostas/32/227_2.png) [@vkostas](https://community.mp3tag.de/u/vkostas)
#### Post date: [December 15, 2020, 7:43am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/1 "2020-12-15T07:43:52Z")

</div>

I noticed something rather buggy when editing multivalve tag. Components are changed arbitrarily.  
Tag: Artist  
Value Before: Value1\\Value2  
Value After: Value2\\Value1

Value1 and Value2, appear in different row in extended view.  
I modify Value2 but it moves up unexpectedly.  
Am I missing some mp3tag feature? I hope this one has a On/Off switch (defaulted to NO of course).

---

<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 15, 2020, 8:03am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/2 "2020-12-15T08:03:17Z")

</div>

> [@vkostas](#):
>
> I hope this one has a On/Off switc

No it has not.  
I don't think that you can set the order anywhere.  
BTW: I just edited a track with a multi-value field via the extended tags dialogue and the order stayed, even after closing the dialogue ...

---

<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 15, 2020, 8:08am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/3 "2020-12-15T08:08:54Z")

</div>

Yes, the order is supposed to stay in the sequence of the individual fields on the extended tag dialog. Please post detailed steps to reproduce the issue in case you observe something different.

---

<div class="post-metadata">

### Author: ![vkostas](https://community.mp3tag.de/user_avatar/community.mp3tag.de/vkostas/32/227_2.png) [@vkostas](https://community.mp3tag.de/u/vkostas)
#### Post date: [December 15, 2020, 8:11am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/4 "2020-12-15T08:11:42Z")

</div>

Edit tag Artist in Extended view.  
Step 1. Artist = **`Value1\\Value2`**  
 ![Mp3Tag-1](https://community.mp3tag.de/uploads/default/original/2X/e/e40ce2a703140afb6c77fc694b213ed0dd85d059.jpeg)

Step 2. Change **`Value1`** to **`Value1$`** and press OK.  
 ![Mp3Tag-2](https://community.mp3tag.de/uploads/default/original/2X/6/6b36288bb8384a5ac8cdeac4bbb42905a525724f.jpeg)

Result is Artist = **`Value2\\Value1$`**  
 ![Mp3Tag-2](https://community.mp3tag.de/uploads/default/original/2X/1/19f74deb93ebfc67602087811bcf8547e51260bb.jpeg)

Order has changed.  
I believe this behavior it is linked to special characters.

---

<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 15, 2020, 8:19am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/5 "2020-12-15T08:19:09Z")

</div>

These are not detailed steps to reproduce the issue.

Are you editing those fields in the extended tag dialog or is the tag panel or the file list involved also. Are there any contents present before? Are you removing the contents before step 2.

Please make a little bit more effort in describing this if you want me to research this further.

---

<div class="post-metadata">

### Author: ![vkostas](https://community.mp3tag.de/user_avatar/community.mp3tag.de/vkostas/32/227_2.png) [@vkostas](https://community.mp3tag.de/u/vkostas)
#### Post date: [December 15, 2020, 8:26am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/6 "2020-12-15T08:26:01Z")

</div>

Amended my previous comment with detailed steps.  
Hopefully you can reproduce it the same way as me.

---

<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 15, 2020, 8:29am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/7 "2020-12-15T08:29:39Z")

</div>

> [@vkostas](#):
>
> I believe this behavior it is linked to special characters.

I also tried it with a multi-value field with 3 values.  
As soon as I add a non-alphabetic character to an existing string/value, then that value goes to the end of the list.  
e.g. string -\> string. or stri-ng or string#  
This is also true if the value contains a non-alphabetic character and the modification consists of alphabetic characters.  
e.g. string. -\> shtring.

All these tests have been made in the extended tags dialogue.

---

<div class="post-metadata">

### Author: ![vilsen](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/e95f7d/32.png) [@vilsen](https://community.mp3tag.de/u/vilsen)
#### Post date: [December 15, 2020, 11:57am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/8 "2020-12-15T11:57:22Z")

</div>

In my testing this issue is not limited to special characters.

I tested with a clean, tag-less flac file.

In Extended Tags I added this to the empty file:

ARTIST=Adam  
ARTIST=Bob  
ARTIST=Charles

Then I closed Extended Tags

Then I opened Extended Tags again and edited "Bob" to "Bobby" which put the field last:

ARTIST=Adam  
ARTIST=Charles  
ARTIST=Bobby

I also repeated the above with an mp3 file with the same result.

---

<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 16, 2020, 8:33am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/9 "2020-12-16T08:33:04Z")

</div>

I can reproduce the order change when editing individual fields. I got sidetracked by

> [@vkostas](#):
>
> `Value1\\Value2`

which always preserves the given order. I'll look into it and see what I can do.

---

<div class="post-metadata">

### Author: ![vkostas](https://community.mp3tag.de/user_avatar/community.mp3tag.de/vkostas/32/227_2.png) [@vkostas](https://community.mp3tag.de/u/vkostas)
#### Post date: [December 16, 2020, 8:36am UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/10 "2020-12-16T08:36:49Z")

</div>

Take your Time Florian.  
It is not something blocking in the short time anyway. I only noticed by chance when doing some tests for my scripts.

---

<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 17, 2020, 4:02pm UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/11 "2020-12-17T16:02:31Z")

</div>

This is now fixed with [Mp3tag v3.04b](https://community.mp3tag.de/t/455). Thanks for reporting and the detailed explanations from everyone!

---

<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 16, 2021, 4:02pm UTC](https://community.mp3tag.de/t/extended-view-changes-the-order-of-multivalue-components/51213/12 "2021-01-16T16:02:33Z")

</div>

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