# What exactly is (id) when matching?

**URL:** <https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042>\
**Category:** Help\
**Created:** [February 28, 2022, 7:38pm UTC](https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042 "2022-02-28T19:38:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![47West63rd](https://avatars.discourse-cdn.com/v4/letter/4/a183cd/32.png) [@47West63rd](https://discourse.beets.io/u/47West63rd)\
**Post date:** [February 28, 2022, 7:38pm UTC](https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042/1 "2022-02-28T19:38:20Z")

</div>

This seems like a pretty good match to me. How can I tell the UI to allow this? I tried this in my match section with no luck. Any idea what the (id) actually is?

```auto
match:
    max_rec: 
        track_id: none
        track_title: none

```

![RoonNow](https://canada1.discourse-cdn.com/flex029/uploads/beets/original/1X/831a3d8bdc9aad2f26182343925a335764215703.jpeg)

---

<div class="post-metadata">

**Author:** ![RollingStar](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/rollingstar/32/728_2.png) [@RollingStar](https://discourse.beets.io/u/RollingStar)\
**Post date:** [February 28, 2022, 7:53pm UTC](https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042/2 "2022-02-28T19:53:35Z")

</div>

I thought track ID is the track number. Maybe if you make the penalty very small (0.01) instead of none (or None), it will work? Or make it 0?

---

<div class="post-metadata">

**Author:** ![47West63rd](https://avatars.discourse-cdn.com/v4/letter/4/a183cd/32.png) [@47West63rd](https://discourse.beets.io/u/47West63rd)\
**Post date:** [February 28, 2022, 8:03pm UTC](https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042/3 "2022-02-28T20:03:09Z")

</div>

When I set it to zero I get the following error:

configuration error: match.max\_rec.track\_id: must be one of [‘strong’, ‘medium’, ‘low’, ‘none’], not 0

---

<div class="post-metadata">

**Author:** ![47West63rd](https://avatars.discourse-cdn.com/v4/letter/4/a183cd/32.png) [@47West63rd](https://discourse.beets.io/u/47West63rd)\
**Post date:** [February 28, 2022, 8:10pm UTC](https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042/4 "2022-02-28T20:10:54Z")

</div>

So I set everything dealing with tracks to none (also tried low) and same results. I must not be understanding the relationship between (tracks) and (id) in the original screen shot above. Isn’t “tracks” in yellow the only thing not matching and the “ids” in each track are what the problem is? Note that the 6th track Ol’ Man River does not have that problem.

```auto
max_rec: 
        track_title: none
        track_artist: none
        track_index: none
        track_length: none
        track_id: none
        tracks: none

```

---

<div class="post-metadata">

**Author:** ![47West63rd](https://avatars.discourse-cdn.com/v4/letter/4/a183cd/32.png) [@47West63rd](https://discourse.beets.io/u/47West63rd)\
**Post date:** [March 1, 2022, 6:25pm UTC](https://discourse.beets.io/t/what-exactly-is-id-when-matching/2042/5 "2022-03-01T18:25:03Z")

</div>

If you are stuck on this like me. Check out the next couple of links. max\_rec uses names distance\_weights use numbers

> [@Can beets fix tracks which are wrongly named?](https://discourse.beets.io/t/can-beets-fix-tracks-which-are-wrongly-named/671):
>
> I have a few albums where the track titles are randomly swapped around. Let’s say an album has track 1 (2:56 minutes long) and track 2 (5:12 minutes long), but my tags are messed up, and I have the track 2 tagged with the title “track 1”, and vice versa. Will the autotagger fix this when importing, based on track lengths? Or will it assume, since the titles are actually correct titles from the album, that track 1 is indeed track 1, and track 2 is indeed track 2? EDIT: it seems that beets fetc…

**and**

> <https://github.com/beetbox/beets/blob/6ee824fb0f3419a502b580b171cf9530a1a65b34/beets/config_default.yaml#L132>

I was able to make track index and track id both 0.1 and the above match went from 84 to 99%. I seem to remember reading somewhere (but can’t find it) that ID and Index are named opposite of what you would think for backwards compatibility. Maybe somebody with more background can chime in and what I actually accomplished. Thanks to @RollingStar for putting me on the right path.

```auto
        track_index: 0.1
        track_length: 2.0
        track_id: 0.1

```