# \[X\] Action Schreibweise "\_ALL": Normal not always working

**URL:** <https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705>\
**Category:** No Bugs\
**Created:** [February 29, 2016, 8:49am UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705 "2016-02-29T08:49:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![blubserl](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/e8c25b/32.png) [@blubserl](https://community.mp3tag.de/u/blubserl)\
**Post date:** [February 29, 2016, 8:49am UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705/1 "2016-02-29T08:49:30Z")

</div>

hi!

since this never happened to me before, this could be a possible bug.  
i have ever since specified an action Schreibweise "\_ALL": Normal, that used to work just fine.  
however i stumbled upon a mp3 file where this action has no effect on the first character of each tag. i double checked that there is no whitespace character in front...

if i manually edit the first character of e.g. the artist tag and save, the action can then be used normally. maybe an ecoding issue, not sure...

i could provide a link to a sample mp3 file per e-mail for debugging.

greetings,

blubserl

---

<div class="post-metadata">

**Author:** ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)\
**Post date:** [February 29, 2016, 10:45am UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705/2 "2016-02-29T10:45:02Z")

</div>

> [@blubserl](#):
>
> ... this could be a possible bug. i have ever since specified an action Schreibweise "\_ALL": Normal, that used to work just fine. however i stumbled upon a mp3 file where this action has no effect on the first character of each tag. ... a sample mp3 file ...

Proposal for giving the forum users insight into the probably bad mp3 tag.

1. Open the notepad editor and write the word "TEST".
2. Save this text as a file with the name "TEST.mp3.txt".
3. Rename the file "TEST.mp3.txt" to "TEST.mp3".
4. Open Mp3tag and load both files, the "TEST.mp3" and the probably bad mp3 file.
5. Select the bad mp3 file and copy its entire tag from the bad file by [Ctrl+C] into the Mp3tag clipboard.
6. Select the test file and paste the Mp3tag clipboard by [Ctrl+V] into the test file "TEST.mp3".
7. Open the Mp3tag dialog "Extended Tags..." and check the tag content within the test file, it should now have the same content as the probably bad mp3 file.
8. Attach the test file to your next forum message, maybe as a zip archive.

DD.20160229.1244.CET

---

<div class="post-metadata">

**Author:** ![blubserl](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/e8c25b/32.png) [@blubserl](https://community.mp3tag.de/u/blubserl)\
**Post date:** [February 29, 2016, 3:11pm UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705/3 "2016-02-29T15:11:12Z")

</div>

thanks for this idea!  
here it is...the action doesn't work with this generated test file too...

[Test.mp3](https://community.mp3tag.de/uploads/default/original/2X/a/aa7783c67f3ebf85d6533b03df68efd75ba6d613.mp3) (2.16 KB)

---

<div class="post-metadata">

**Author:** ![blubserl](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/e8c25b/32.png) [@blubserl](https://community.mp3tag.de/u/blubserl)\
**Post date:** [February 29, 2016, 3:17pm UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705/4 "2016-02-29T15:17:41Z")

</div>

just noticed total commanders mp3tagview plugin also has problems with this file (see attachment), so most probably this is some strange encoding or wrongly tagged file...

![](https://community.mp3tag.de/uploads/default/original/2X/a/ab1c1a4ea84ad9c4db0248030b97c66b78d8ea70.PNG)

---

<div class="post-metadata">

**Author:** ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)\
**Post date:** [February 29, 2016, 4:18pm UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705/5 "2016-02-29T16:18:30Z")

</div>

Test.blubserl.defekt.mp3  
Test-Formatstring:  
$ord(%TITLE%) - $ord(%ALBUM%) ### %TITLE% - %ALBUM%  
==\>

65279 - 65279 ### ??burn - ??ready To Die

------------------^--------^-------------

Each tagfield contains a doubled leading Unicode character sequence "FF FE FF FE", ...  
which is somewhat suspicious.  
In Mp3tag dialog "Tag-Tag" preview it is shown as one symbol "square", ...  
but in fact it is a byte sequence, with a special meaning.  
In general "FF FE" this is the leading character sequence to define the byte order within the following string of Unicode byte sequence.

0100 49 44 33 03 00 00 00 00 10 17 54 41 4C 42 00 00 ID3.......TALB..

0110 00 1D 00 00 01 FF FE _FF FE_ 72 00 65 00 61 00 64 .........r.e.a.d  
0120 00 79 00 20 00 54 00 6F 00 20 00 44 00 69 00 65 .y. .T.o. .D.i.e  
0130 00 54 49 54 32 00 00 00 0D 00 00 01 FF FE _FF FE_ .TIT2...........  
0140 62 00 75 00 72 00 6E 00 00 00 00 00 00 00 00 00 b.u.r.n.........

Assumable something has happened with the text data, which has created the given situation with the doubled byte order mark.  
This situation can be repaired by ...

**Convert "Tag - Tag" ... or ... Action "Format value" Field ......: TITLE Formatstring: $regexp(%TITLE%,'^\x{FEFF}',)**

DD.20160229.1927.CET

---

<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 28, 2018, 2:37pm UTC](https://community.mp3tag.de/t/x-action-schreibweise-all-normal-not-always-working/17705/6 "2018-12-28T14:37:48Z")

</div>

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