# Comment's field Multiline
**URL:** https://community.mp3tag.de/t/comments-field-multiline/16708
**Category:** General Discussion
**Created:** [March 18, 2015, 2:26pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708 "2015-03-18T14:26:26Z")
**Posts on this page:** 15
**Page:** 1
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 18, 2015, 2:26pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/1 "2015-03-18T14:26:26Z")
Hello
I would like to propose an option of making a multiline for the tag field COMMENT
I use comments rarely. But most of the time that I do, I will put long sentences or make many separate lines [a list of something]. For me it's a pity that COMMENT field cannot be made into a multiline. [There is no workaround to this in the form of making a second field displaying the COMMENT tag, because you won't be able to create it]
And also I just can't understand, why can't I choose how a default values in Tag Panel should be displayed when at the time I can choose the appearance of additional fields. Or why can't I turn off default fields [don't really need that] or rearrange them [I would much like to mix them with my additional fields]. Or why can't I make a non default field like DISCNUMER to look as short as default YEAR / TRACK / GENRE. Or why can't I choose how many lines should a Multiline have
[The concern for a beginner users, who could mess things up to the point of making the Mp3tag "unusable", could be dealt with a simple "reset tags-menu-list to default" button]
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 18, 2015, 6:03pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/2 "2015-03-18T18:03:10Z")
> [@zerow](#):
>
> ... multiline for the tag field COMMENT ...
Maybe this picture can help ...
See also ....
[multiline comment field in the tag panel](https://community.mp3tag.de/t/14363/4)
[/t/12630/1](https://community.mp3tag.de/t/12630/1)
[/t/10489/1](https://community.mp3tag.de/t/10489/1)
[https://www.google.de/search?q=site%3Aforum...ltiline+comment](https://www.google.de/search?q=site%3Aforums.mp3tag.de+multiline+comment)
DD.20150318.2010.CET
---
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 18, 2015, 8:26pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/3 "2015-03-18T20:26:06Z")
> [@DetlevD](#):
>
> Maybe this picture can help ...
>
> 
Of course it helps; but:
If you use Winamp and have a FLAC file, then you have access to those fields with the possibility of editing them in Winamp
But MP3 files do not grand you access via Winamp to the edition of "less" popular tag fields [not mentioning the made up ones]. You can display them [by incorporating them to the code of shown tag fields], but to touch them you have to load them to Mp3tag [because creators of Winamp didn't thought that it would be good to make the user decide what fields to display, even in the ID3v2 panel]. And I can only guess that other players and file formats have similar issues
And also if you were to use a new COMMENT-ENCORE tag, the you are wasting space [by not using original COMMENT tag, which can't be turned off]; and aside that you are creating a made up field [that could be possibly not read by the car-audio equipment or some home stereo system]
> [@DetlevD](#):
>
> See also ....
> [multiline comment field in the tag panel](https://community.mp3tag.de/t/14363/4)
> [/t/12630/1](https://community.mp3tag.de/t/12630/1)
> [/t/10489/1](https://community.mp3tag.de/t/10489/1)
> [https://www.google.de/search?q=site%3Aforum...ltiline+comment](https://www.google.de/search?q=site%3Aforums.mp3tag.de+multiline+comment)
So what you are basically saying is: that is a problem that comes up again and again for different users
Seriously: what that hack does should be incorporated at last as an option [if not as default]. And all of my suggestions are still relevant and when implemented would make the Mp3tag a much better editor
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 19, 2015, 6:29am UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/4 "2015-03-19T06:29:12Z")
> [@zerow](#):
>
> Of course it helps; but: ... if you were to use a new COMMENT-ENCORE tag, the you are wasting space [by not using original COMMENT tag, which can't be turned off]; and aside that you are creating a made up field [that could be possibly not read by the car-audio equipment or some home stereo system] ... So what you are basically saying is: that is a problem that comes up again and again for different users ...
Did you try the proposal from there ... ?
[multiline comment field in the tag panel](https://community.mp3tag.de/t/14363/4)
> [@](#):
>
> To avoid the appearing of the new defined tag-field in the list of tag-fields, ...
> you may set a Mapping for Tag=ID3v2 with Source=MY\_COMMENT and Target=COMMENT.
DD.20150319.0829.CET
---
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 19, 2015, 7:26am UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/5 "2015-03-19T07:26:57Z")
> [@DetlevD](#):
>
> Did you try the proposal from there ... ?
> [multiline comment field in the tag panel](https://community.mp3tag.de/t/14363/4)
> [@](#):
>
> To avoid the appearing of the new defined tag-field in the list of tag-fields, ...
> you may set a Mapping for Tag=ID3v2 with Source=MY\_COMMENT and Target=COMMENT.
I did not
But I did now, and either you have proposed me now something not dealing with the problem or I don't know what it can be used for
I created that mapping. So now I can write in the made up field MY\_COMMENT some text. And after saving it, this happens:
- text will show up in the COMMENT field
- text will disappear from MY\_COMMENT field
- I can't edit text in COMMENT field
Am I missing something here or is that it?
If it is all there is to it, then I don't see any sense in this workaround. The only advantage is that I can see 5 lines of text in MY\_COMMENT, while writing them [instead of one in COMMENT]. But the same can be achieved without mapping; the only difference being that I won't access that written text in Winamp [because it will show me only COMMENT]
Also: can I define how many lines does a multiline have via this hack? Or does the digit value in \>\>multiline=\<\< can only be
> > 0\<\< [NO]
> > or
> > 1\<\< [YES]
> > ?
> > I tried to put higher number than 5, but it didn't make a difference
---
### Author:  [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 19, 2015, 9:04am UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/6 "2015-03-19T09:04:43Z")
> [@zerow](#):
>
> ... I created that mapping. So now I can write in the made up field MY\_COMMENT some text. And after saving it, this happens:
>
> - text will show up in the COMMENT field
> - text will disappear from MY\_COMMENT field
> - I can't edit text in COMMENT field
> Am I missing something here or is that it?
There is no problem to edit the COMMENT tag-field in all dialogs within Mp3tag.
> [@zerow](#):
>
> ... The only advantage is that I can see 5 lines of text in MY\_COMMENT, while writing them [instead of one in COMMENT]. But the same can be achieved without mapping; the only difference being that I won't access that written text in Winamp [because it will show me only COMMENT] ...
Because the new edit field MY\_COMMENT is a scrollable multi-line edit field, someone can view much more than 5 lines.
I do not believe, that someone, in a practical way, is able to put a multi line text into the standard "comment" edit field while in the dialog "Tag Panel".
> [@zerow](#):
>
> ... But the same can be achieved without mapping ..
Yes, it is possible, ...
- by using the edit dialog for the tag-field COMMENT within the dialog "Extended Tags", ...
- or when applying the "usrfields.ini" hack ...
[Multi-line comment box](https://community.mp3tag.de/t/11416/5)
... which adds an additional multi-line edit field to the Tag-Panel.
> [@zerow](#):
>
> ... Also: can I define how many lines does a multiline have via this hack? Or does the digit value in \>\>multiline=\<\< can only be \>\>0\<\< [NO] or \>\>1\<\< [YES]? I tried to put higher number than 5, but it didn't make a difference
'multiline=1' or 'multiline=0' is a ... 'yes/no'... 'on/off' ... switch.
DD.20150319.1104.CET
---
### Author:  [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 19, 2015, 7:50pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/7 "2015-03-19T19:50:22Z")
> [@zerow](#):
>
> [...]
> The only advantage is that I can see 5 lines of text in MY\_COMMENT, while writing them [instead of one in COMMENT]. But the same can be achieved without mapping; the only difference being that I won't access that written text in Winamp [because it will show me only COMMENT]
> [...]
> [@DetlevD](#):
>
> [...]
> Because the new edit field MY\_COMMENT is a scrollable multi-line edit field, someone can view much more than 5 lines.
Yes
But you have to... scroll it
If I could define the height [I know it now, it's not possible] of a multiline and use up the free space that I have in my panel tag, then over the years to come I would have much less to scrolling to do. 5 lines will work in most cases, but I wish I could extend the field.
And yes, I know that there is not such a thing as free space in tag panel, because it also can be scrolled down. But all that scrolling that prevents the user from just looking at the data and saving time and energy from not clicking [that's why I limit tag fields to the amount that are visible without scrolling]
> [@DetlevD](#):
>
> I do not believe, that someone, in a practical way, is able to put a multi line text into the standard "comment" edit field while in the dialog "Tag Panel".
> [...]
Yes, you are right
> [@DetlevD](#):
>
> [...]
> using the edit dialog for the tag-field COMMENT within the dialog "Extended Tags"
> [...]
Thank you for pointing that out; I didn't get the sense of it [while combined with the hach] when I red about it in those old linked posts
All of this info I can now digest and come up with some optimal way of COMMENTing my files
---
### Author:  [@esumsea](https://community.mp3tag.de/u/esumsea)
#### Post date: [April 22, 2024, 9:21pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/8 "2024-04-22T21:21:35Z")
Is there a way to map these values and keep a copy in the original field, so I would have the comment in both My Comment and in Comment?
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 23, 2024, 5:50am UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/9 "2024-04-23T05:50:05Z")
Mapping does not copy.
Apply an action of the type "Format value" to copy the contents of one tag field to another.
---
### Author:  [@esumsea](https://community.mp3tag.de/u/esumsea)
#### Post date: [April 23, 2024, 6:31pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/10 "2024-04-23T18:31:19Z")
Yeah, I king of figured that out, but it would be great if mapping could be set up as a copy and not just a transfer, as it is automatic, where the action is not. Using an action, as you suggested, is the way I am currently accomplishing.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 23, 2024, 8:07pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/11 "2024-04-23T20:07:18Z")
It would be nice if you could also describe what you do at the moment.
To me it looked like you needed more information about mapping.
---
### Author:  [@esumsea](https://community.mp3tag.de/u/esumsea)
#### Post date: [April 28, 2024, 6:50pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/12 "2024-04-28T18:50:14Z")
I am sorry. I do not understand. What did I omit?
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 28, 2024, 7:00pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/13 "2024-04-28T19:00:05Z")
The fact that you already used actions to copy the contents of one field to another.
---
### Author:  [@esumsea](https://community.mp3tag.de/u/esumsea)
#### Post date: [April 28, 2024, 8:49pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/14 "2024-04-28T20:49:03Z")
Oh, I understand now. Sorry for my oversight.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [July 15, 2024, 1:40pm UTC](https://community.mp3tag.de/t/comments-field-multiline/16708/15 "2024-07-15T13:40:08Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.