# Issue with Text file-\>Tag

**URL:** <https://community.mp3tag.de/t/issue-with-text-file-tag/44799>\
**Category:** Support\
**Created:** [March 10, 2019, 12:41am UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799 "2019-03-10T00:41:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Harderthanyou](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/h/ccd318/32.png) [@Harderthanyou](https://community.mp3tag.de/u/Harderthanyou)\
**Post date:** [March 10, 2019, 12:41am UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799/1 "2019-03-10T00:41:03Z")

</div>

This seems simple but it is not working anymore. I have done this in the past with no issues but recently is has stopped working properly. I have a text file which is just a list of song titles. That's it, just titles. Each title is on a single line. There are no special characters in the titles. There are no spaces before or after the titles. When I try to use the Text file -\> Tag feature, I get an error saying "Cannot parse line 1", "Cannot parse line 2", "Cannot parse line 3" etc. In the field for Format string: I have %title% . That is all that I want there. It seems to work just fine when I try it for any other field such as %album% or %artist% or %genre%. Just doesn't for %title%. Any idea what is going on here? Thanks.

---

<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:** [March 10, 2019, 9:30am UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799/2 "2019-03-10T09:30:53Z")

</div>

The way you describe it, it should work.  
The only things I could imagine: when you tried it with %title% the file was still in a rich format mode as saved by word processors. After that, when you checked and retried it with %album% and other fields, you had saved the file as plain text.  
Or you have to supply a sample of the data so that others can try it.

---

<div class="post-metadata">

**Author:** ![Harderthanyou](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/h/ccd318/32.png) [@Harderthanyou](https://community.mp3tag.de/u/Harderthanyou)\
**Post date:** [March 12, 2019, 12:48am UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799/3 "2019-03-12T00:48:36Z")

</div>

Yes it should work. I tried again and here are the screen shots. I am using four mp3s that I took randomly from my collection. I created a text file with the test titles. One per line. Nothing special about them. It is just a .txt file and it is in the folder containing the mp3s.

 ![text%20file](https://community.mp3tag.de/uploads/default/original/2X/5/5df39d653f49269fc9355612596dacb07caed905.jpeg) Here is what I started with. ![blank%20title](https://community.mp3tag.de/uploads/default/original/2X/3/3e67c83e1bded262a176c6302b1c5c3b0bedafbe.jpeg) I used the Text file - Tag feature ![convert1](https://community.mp3tag.de/uploads/default/original/2X/4/4e616bf59d71f473c3b0c7fd33bdaa2c61bf7d93.jpeg) and then I get this parsing error. ![convert2](https://community.mp3tag.de/uploads/default/original/2X/f/f915dacbe670a4112ef3e6867b5206ae2816b717.jpeg) Then I tried the same thing but used the Album Artist field instead ![albumartist](https://community.mp3tag.de/uploads/default/original/2X/0/0a218b86933b15ea599e11b6ede251093738f75c.jpeg) ![albumartistconvert1](https://community.mp3tag.de/uploads/default/original/2X/b/bf6398a4bad209e0af5f7c81edb9267cac06fd68.jpeg) ![albumartistconvert2](https://community.mp3tag.de/uploads/default/original/2X/9/9a21a9326895f7b4ca9c4d56526e6b8e503ff134.jpeg) And it works just fine. Worked in the Album and Year field as well. ![albumyear](https://community.mp3tag.de/uploads/default/original/2X/6/6b9548530eceb04cb64ad327e8e2665641689636.jpeg) It just won't work in the Title field. So...any suggestions?

---

<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:** [March 12, 2019, 6:11am UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799/4 "2019-03-12T06:11:44Z")

</div>

> [@Harderthanyou](#):
>
> So...any suggestions?

Not a lot.  
Could you check the files for integrity?

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

Because ... I tried to import plain text data into %title% and it works ... so I can't really reproduce it.  
Or you could post the data file ... so that I can have a try with the original data.

---

<div class="post-metadata">

**Author:** ![shadonoz](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/ecd19e/32.png) [@shadonoz](https://community.mp3tag.de/u/shadonoz)\
**Post date:** [January 21, 2021, 10:38pm UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799/5 "2021-01-21T22:38:44Z")

</div>

ALWAYS check for trailing spaces in the format string! They're not always "visible".

---

<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:** [September 4, 2024, 5:03am UTC](https://community.mp3tag.de/t/issue-with-text-file-tag/44799/6 "2024-09-04T05:03:31Z")

</div>

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