# Tracknumbers with following space after import

**URL:** https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500
**Category:** Mac
**Created:** [December 23, 2022, 6:31pm UTC](https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500 "2022-12-23T18:31:06Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![VSG\_79](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/a698b9/32.png) [@VSG\_79](https://community.mp3tag.de/u/VSG_79)
#### Post date: [December 23, 2022, 6:31pm UTC](https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500/1 "2022-12-23T18:31:06Z")

</div>

Hi there!

I recently stumbled upon the same error and I found out Mp3tag (at least the macOS-version) not only adds 0 before single-digit numbers but also a space after the track numbers. That is what caused my import to fail the correct song-order.

Usually I create the mp4-files that have a format like this:

```auto
04 - artist - track

```

Then I use Mp3tag's feature to import tags from file names. This is when the tag for track is actually created like "04\_" with the \_ being a space added after the track-number.

If you could fix this issue, this would be great – and thanks for the best tagging-software out there!  
Best regards and everyone have some great holidays!  
VSG

---

<div class="post-metadata">

### Author: ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)
#### Post date: [December 23, 2022, 6:35pm UTC](https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500/2 "2022-12-23T18:35:04Z")

</div>

How are you getting the tags from the filename? That is where you are probably getting the space from. Can you show an example of your converter to get these?

---

<div class="post-metadata">

### Author: ![VSG\_79](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/v/a698b9/32.png) [@VSG\_79](https://community.mp3tag.de/u/VSG_79)
#### Post date: [December 24, 2022, 10:52am UTC](https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500/3 "2022-12-24T10:52:47Z")

</div>

My string looks like this:

```auto
%track% - %ARTIST% - %title%

```

But I found my own error in this: I was missing the space between track and ARTIST because these fields are display with a wide blue background in macOS and I thought there was a space after the track and before the -.

When you forget the space before -, Mp3tag will **add** a space after the track number for mysterious reasons.  
If you add the space correctly before and after the - then Mp3tag will correctly place the text within the ID-tags. In conclusion, my own fault. Sorry for the inconvenience!

Best regards  
VSG

 ![Bildschirm_foto 2022-12-24 um 11.49.56](https://community.mp3tag.de/uploads/default/original/2X/5/5c25b1c90cf3b369526f3a57f48f4637e4d75966.jpeg)

---

<div class="post-metadata">

### Author: ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)
#### Post date: [December 24, 2022, 12:15pm UTC](https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500/4 "2022-12-24T12:15:49Z")

</div>

This is what I suspected.

> [@VSG\_79](#):
>
> When you forget the space before -, Mp3tag will **add** a space after the track number for mysterious reasons.

No mystery, mp3tag will use the literal conversion of what you ask. Without specifying the space dash space “ - “ as a separator, that character was kept as-is and put into the track field.

Great that you were able to find this and fix moving forward.

---

<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: [March 3, 2023, 2:06pm UTC](https://community.mp3tag.de/t/tracknumbers-with-following-space-after-import/59500/5 "2023-03-03T14:06:35Z")

</div>

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