# Yt-dlp downloads Description doesn't have Line Break

**URL:** https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384
**Category:** Support
**Created:** [September 1, 2022, 8:18am UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384 "2022-09-01T08:18:06Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 1, 2022, 8:18am UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/1 "2022-09-01T08:18:06Z")

</div>

MP3Tag needs carriage return + line feed (CRLF) to display correctly.  
yt-dlp uses ffmpeg to embed metadata and it show it correctly

 ![image](https://community.mp3tag.de/uploads/default/original/2X/c/cb649013d611f494a057070da268a8139f64512d.png)  
 ![image](https://community.mp3tag.de/uploads/default/original/2X/3/3e8cfd0c7fbc9dea413d58e113a1819505b86adc.png)  
 ![image](https://community.mp3tag.de/uploads/default/original/2X/5/5c03f481eac46ee7567e913294cdc156f74d7cf9.png)

---

<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: [September 1, 2022, 4:52pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/2 "2022-09-01T16:52:51Z")

</div>

I just copied and pasted the first 2 lines of your post into an MP3tag field:

 ![grafik](https://community.mp3tag.de/uploads/default/original/2X/e/eb3090b9324e9272d7c8794e72eb270c1d4fd4d1.png)

And that shows the line breaks ...  
So I am not sure what has happened to your text.

---

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 1, 2022, 5:18pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/3 "2022-09-01T17:18:57Z")

</div>

Line breaks but not when using unix-style LF.

---

<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: [September 1, 2022, 5:21pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/4 "2022-09-01T17:21:56Z")

</div>

Does that consist only of LineFeed or CarriageReturn?

Then you could try an action of the type "Replace with regular expression"  
Search: `\r`  
or  
Search `\n`  
(that depends which one has been used for the line break)  
and  
Replace with: `\r\n`

---

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 3, 2022, 7:37am UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/5 "2022-09-03T07:37:23Z")

</div>

It is a bug. Mp3Tag should accept both unix and windows style line breaks. someone marked it support please mark it Bug Report.

---

<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: [September 3, 2022, 2:06pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/6 "2022-09-03T14:06:34Z")

</div>

Can you solve your problem with the replace function?

---

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 3, 2022, 2:51pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/7 "2022-09-03T14:51:47Z")

</div>

No. Maybe the charter you told to replace are wrong

---

<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: [September 3, 2022, 3:16pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/8 "2022-09-03T15:16:29Z")

</div>

Could you supply such a file? So that others can have a look?

I just removed all `\r` from a field, so that only the `\n`are left and this is what it look like in the hex editor and what MP3tag shows:

 ![grafik](https://community.mp3tag.de/uploads/default/original/2X/7/7b0ffadbf5550f351093eb33f7723e477bc054d9.png)

---

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 3, 2022, 4:45pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/9 "2022-09-03T16:45:17Z")

</div>

[Blank Space.zip](https://community.mp3tag.de/uploads/short-url/m2Ao5ax0X6Ethu1cGO9exqICLxs.zip) (989.2 KB)

---

<div class="post-metadata">

### Author: ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)
#### Post date: [September 3, 2022, 4:50pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/10 "2022-09-03T16:50:23Z")

</div>

This opus song contains the SYNOPSIS like this (LF only).  
Not with CR+LF as you wrote in the 1st post.

 ![image](https://community.mp3tag.de/uploads/default/original/2X/2/215756e3030275fcf073aa5865011b375b89742a.png)

---

<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: [September 3, 2022, 5:25pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/11 "2022-09-03T17:25:18Z")

</div>

I just applied this:  
 ![grafik](https://community.mp3tag.de/uploads/default/original/2X/1/1a5152c2a5681127566cf45a4f2ca7750b26a074.png)

Which leads to a field with proper line breaks.  
So I cannot reproduce

> [@LWiv7](#):
>
> No. Maybe the charter you told to replace are wrong

I checked with the ID3 standard which says:  
"Fields that include more then one line uses [CR][LF] delimiters between lines. "  
I do not think that your assumption

> [@LWiv7](#):
>
> It is a bug. Mp3Tag should accept both unix and windows style line breaks

is correct in this respect.

---

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 4, 2022, 4:01pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/12 "2022-09-04T16:01:22Z")

</div>

1. Replacing works.

2. 

> I checked with the ID3 standard which says:  
> "Fields that include more then one line uses [CR][LF] delimiters between lines. "

Opus uses Vorbis Comments

[https://exiftool.org/faq.html#:~:text=[Unfortunately%20the%20Windows%20cmd%20shell%20provides%20no%20method%20to%20get%20a%20newline%20(CR/LF%20in%20Windows)%20into%20the%20command%20line.%20A%20linefeed%20(LF)%20may%20be%20inserted%20with%20CTRL-T%2C%20but%20I%20have%20found%20no%20way%20to%20insert%20a%20carriage%20return%20(CR).]](https://exiftool.org/faq.html#:~:text=%5BUnfortunately%20the%20Windows%20cmd%20shell%20provides%20no%20method%20to%20get%20a%20newline%20(CR/LF%20in%20Windows)%20into%20the%20command%20line.%20A%20linefeed%20(LF)%20may%20be%20inserted%20with%20CTRL%2DT%2C%20but%20I%20have%20found%20no%20way%20to%20insert%20a%20carriage%20return%20(CR).%5D)

Mp3Tag should automatically fix it as per container?

---

<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: [September 4, 2022, 4:10pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/13 "2022-09-04T16:10:56Z")

</div>

> [@LWiv7](#):
>
> Mp3Tag should automatically fix it as per container?

If this is so, it is still no bug but a Feature Request.  
As far as the discussion has come so far:  
Yes, the OPUS fields have only 0A as end-of-line character and that is not treated as such by MP3tag.  
Yet, there is an easy workaround with an action to replace the single control character with the 2 correct ones.

I have to admit that I found a different behaviour with ID3 tags which show line breaks even with only 0A at the end.  
And also, I found that pasted text with just 0A as end-of-line character is transformed into 0D0A after saving as long as it is an ID3 tag. Like that the tag data becomes standard compliant for ID3 tags.

It would help to see a similar specification for OPUS tags.

---

<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: [September 5, 2022, 9:18pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/14 "2022-09-05T21:18:46Z")

</div>

The problem is that the Windows edit control requires CRLF to correctly display linebreaks. I've mostly refrained from auto-translating linebreaks so far, because I always prioritized _what_ is actually stored in the tag fields over convenience of display.

---

<div class="post-metadata">

### Author: ![LWiv7](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/ce7236/32.png) [@LWiv7](https://community.mp3tag.de/u/LWiv7)
#### Post date: [September 6, 2022, 9:05am UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/15 "2022-09-06T09:05:44Z")

</div>

Make MP3Tag use both CRLF & LF.

---

<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: [September 6, 2022, 9:20am UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/16 "2022-09-06T09:20:34Z")

</div>

I think this would most likely address your specific needs, but not necessarily the expectations of all other users — some of which simply expect Mp3tag to not alter the data displayed in the edit field.

I've thought about auto-translating the LF (and single CR, which also exists) and translate it back when saving, but this also prevents users from _changing_ the linebreaks to their desired format.

I think for now you need to resort to the approach suggested in this topic to replace the linebreaks to your desired format. And if you want to have them correctly displayed in Mp3tag this would mean CRLF.

---

<div class="post-metadata">

### Author: ![mp3outie](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/85e7bf/32.png) [@mp3outie](https://community.mp3tag.de/u/mp3outie)
#### Post date: [October 21, 2023, 11:14pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/17 "2023-10-21T23:14:52Z")

</div>

When downloading with yt-dlp, use this flag to default to CRLF:  
`--replace-in-metadata "description" "\n" "\r\n"`

---

<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: [November 20, 2023, 11:15pm UTC](https://community.mp3tag.de/t/yt-dlp-downloads-description-doesnt-have-line-break/58384/18 "2023-11-20T23:15:08Z")

</div>

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