# Inserted CRLF when exporting field with more than one value

**URL:** <https://community.mp3tag.de/t/inserted-crlf-when-exporting-field-with-more-than-one-value/53864>\
**Category:** Support\
**Created:** [July 25, 2021, 10:31am UTC](https://community.mp3tag.de/t/inserted-crlf-when-exporting-field-with-more-than-one-value/53864 "2021-07-25T10:31:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahmonge](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/b9e5f3/32.png) [@ahmonge](https://community.mp3tag.de/u/ahmonge)\
**Post date:** [July 25, 2021, 10:31am UTC](https://community.mp3tag.de/t/inserted-crlf-when-exporting-field-with-more-than-one-value/53864/1 "2021-07-25T10:31:39Z")

</div>

Before version 3.08 I was able to export files with this export definition

$filename(Mp3tagPista.csv)Titulo;Artista;Disco;NumeroDisco;NumeroPista;Año;Duracion;Formato;TasaBits;Frecuencia;CompañiaDiscografica;TamañoMuestra;Autor;Genero  
$loop(%\_filename\_ext%)%title%;%artist%;%album%;%discnumber%;%track%;%year%;%\_length\_seconds%;%\_extension%;%\_bitrate%;%\_samplerate%;%publisher%;%\_bitspersample%;$meta(composer);%genre%  
$loopend()

Even if artist field had more than one value separetad by \ \ , the exported CSV file had just the first value followed by the ; field separator.

Now, with v 3.08 if this field has more than one value, the exported CSV file has a CRLF inserted just before the ; field separator. Is this the expected behaviour?

My environment is Win 10 up to date, Mp3tag download from mp3tag web page.

---

<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:** [July 25, 2021, 1:09pm UTC](https://community.mp3tag.de/t/inserted-crlf-when-exporting-field-with-more-than-one-value/53864/2 "2021-07-25T13:09:44Z")

</div>

the only fields that seems to have multi-values is COMPOSER:

> [@ahmonge](#):
>
> ....itspersample%;$meta(composer);%gen...

I tried it with 3.08 installation and it worked like before: multiple values were shown, separated by a comma.  
So: could you show us the screendump of the extended tags dialogue of a file where the export goes wrong? Or supply a link to such a file?

---

<div class="post-metadata">

**Author:** ![ahmonge](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/a/b9e5f3/32.png) [@ahmonge](https://community.mp3tag.de/u/ahmonge)\
**Post date:** [July 25, 2021, 3:50pm UTC](https://community.mp3tag.de/t/inserted-crlf-when-exporting-field-with-more-than-one-value/53864/3 "2021-07-25T15:50:49Z")

</div>

Thanks for your answer! I've just found what was going on (blame me fot it) I donwloaded a record from Qobuz store and, by default, the tracks file format is Wma, instead of Flac, which is the one I use for CD or haigher quality. I didn't notice it, so I believed I was working with Flac files. So I donwloaded the record again, but this time in Flac format. Now the Mp3tag export feature works as usual, being the same in 3.08 and in 3.07.

I apologize for the inconvenience caused.

---

<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:** [August 24, 2021, 3:51pm UTC](https://community.mp3tag.de/t/inserted-crlf-when-exporting-field-with-more-than-one-value/53864/4 "2021-08-24T15:51:14Z")

</div>

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