# How to import bunch of tracks that are not grouped by albums

**URL:** <https://discourse.beets.io/t/how-to-import-bunch-of-tracks-that-are-not-grouped-by-albums/1900>\
**Category:** Help\
**Created:** [October 13, 2021, 6:33pm UTC](https://discourse.beets.io/t/how-to-import-bunch-of-tracks-that-are-not-grouped-by-albums/1900 "2021-10-13T18:33:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![planetearth](https://avatars.discourse-cdn.com/v4/letter/p/82dd89/32.png) [@planetearth](https://discourse.beets.io/u/planetearth)\
**Post date:** [October 13, 2021, 6:33pm UTC](https://discourse.beets.io/t/how-to-import-bunch-of-tracks-that-are-not-grouped-by-albums/1900/1 "2021-10-13T18:33:51Z")

</div>

I have a few tracks that are not currently properly sorted. I have tried both `beet import -s` and `beet import -s --flat`. Even though beets was able to match the track, the album name was not updated (few other fields were updated) in both cases. Is this the expected behavior? Ideally, I would like to use beets to identify which albums these tracks belong to and update the tags so that I can manually sort them.

I tried the same after manually deleting the album tags and placing all the files in the same folder, but still the same (I cannot get the album tag written by beet).

It is possible that singleton is not the solution to my problem. If anyone has better ideas to match individual tracks and tag them, I would love to know.

Any advice?

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.beets.io/adrian/32/4_2.png) [@adrian](https://discourse.beets.io/u/adrian)\
**Post date:** [October 13, 2021, 9:29pm UTC](https://discourse.beets.io/t/how-to-import-bunch-of-tracks-that-are-not-grouped-by-albums/1900/2 "2021-10-13T21:29:19Z")

</div>

Hello! Singleton imports don’t fetch album-level metadata. This thread has some details:

> <https://github.com/beetbox/beets/issues/229>
>
> It appears beets will not add album information for a singleton, even though it
> …could.
> 
> For example you can run
> 
> \`\`\`
> beet import -s test.mp3
> \`\`\`
> 
> and no album info will be added, however if you instead run
> 
> \`\`\`
> beet import .
> \`\`\`
> 
> then album info will be added, where \`.\` contains \`test.mp3\`. Again, "Picard" treats both folders and individual files as "first class citizens".

---

<div class="post-metadata">

**Author:** ![planetearth](https://avatars.discourse-cdn.com/v4/letter/p/82dd89/32.png) [@planetearth](https://discourse.beets.io/u/planetearth)\
**Post date:** [October 13, 2021, 10:01pm UTC](https://discourse.beets.io/t/how-to-import-bunch-of-tracks-that-are-not-grouped-by-albums/1900/3 "2021-10-13T22:01:20Z")

</div>

> [@adrian](#):
>
> [Fetch album-level metadata in singleton imports · Issue #229 · beetbox/beets · GitHub](https://github.com/beetbox/beets/issues/229)

That thread basically discusses the problem but there is no solution. I am sure you have good reasons to not import album-level data for singletons. I would assume that whenever a match is found and users confirm the same, we should be importing everything that is available (something that Picard is able to do right now). May be something to consider in the future…