Help & Support

I have noticed that virtually all of my albums that contain more than 1 disc get separated into separate albums. This does not seem to matter whether it is 2, 3, 4 or more discs.

I don't seem to have this issue with other programs like jplay and audirvana.

When I look at the tags in an editor like mp3 tagger, they all have the same album artist tag.

I also notice that many of my refresh library scans go only to 99% and then same to crash.

What might I do to address these issues?

Hi,

Regarding the library scanning issues, I’m aware that there are some problems with the current version, including scans getting stuck at 99% or causing the application to crash.

These issues are generally caused by empty album folders or folders containing problematic or corrupted files that the scanning process cannot handle correctly.

These problems have already been identified and fixed in the upcoming update. As I’ve mentioned before, the next version includes several improvements and fixes to the scanning process, so there’s no need to keep reporting the same issues.

I don’t have an exact release date yet, but I expect the update to be available soon.

As for multi-disc albums, MusicCovered already supports albums containing multiple discs, whether they have 2, 3, 4, or more. The application is designed to recognize and group them correctly.

If your discs are appearing as separate albums, I suspect there may be inconsistencies in the metadata. Having the same Album Artist tag is important, but other tags, such as Album, Disc Number, and Disc Total, should also be checked for consistency.

I recommend checking these tags carefully, as even small differences can affect how albums are grouped.

Thank you for your patience. I’m working hard to improve MusicCovered, and the next update should resolve the scanning issues you’ve been experiencing.

Appreciate the work you are doing.

Does musicbrainz ID also impact how box sets are grouped.

Also, when a box set contains cover art for each of the individual discs, is the cover art for each specific disc displayed?

Thank you, I really appreciate your support!

Regarding cover artwork, MusicCovered simply displays the artwork embedded in each audio file, nothing more and nothing less.

This means that the way you organize and manage your metadata and embedded artwork will be reflected in the MusicCovered interface. If individual discs have different embedded covers, MusicCovered will use the artwork associated with those files.

As for MusicBrainz, I’ve implemented support for all the metadata tags used by MusicBrainz Picard, including MusicBrainz IDs. These improvements will be available in the next update.

However, due to licensing and authorization requirements, it’s currently not possible to retrieve metadata directly from MusicBrainz within MusicCovered.

You can still use MusicBrainz Picard or other external tagging applications to organize your music collection, and MusicCovered will read and display the metadata stored in your files.

My goal is to give users as much flexibility as possible while keeping their music libraries fully compatible with standard metadata tagging tools.

Will there be a way to control which of the musicbrainz metadata are displayed on the screen?

I checked tags for a number of two disc sets. They all look OK in terms of album artist, disc number, album name and disc total. However, they all display as separate albums. What can I do to fix?

MusicCovered should correctly recognize and group multi-disc albums, provided that the metadata is consistent across all discs.

Since you’ve already checked the Album, Album Artist, Disc Number, and Disc Total tags, I suspect there might be something else in the metadata causing the albums to be separated.

For example, even small differences in album titles, hidden spaces, or conflicting metadata fields could potentially affect how the tracks are grouped.

Could you please send me screenshots of the complete metadata for one track from Disc 1 and another from Disc 2, preferably using a tag editor such as Mp3tag?

Also, are the two discs stored in separate folders, or are all the tracks in the same folder?

I’m going to double-check MusicCovered’s album grouping logic as well, just to make sure there isn’t an issue on the application’s side.

We’ll figure out what’s causing this!

Giorgio

Here is the mp3 tag info for Keith Jarrett's After the Fall, one track from Disc 1 and one from Disc 2

Could you please send me those two audio files so I can analyze them and investigate what might be causing the issue? info@musiccovered.com

How do I send you these files? The button below only allows images. Where do I send these files?

You can send me the files using WeTransfer. It’s very simple:

1. Create a new folder on your computer and put the two original audio files inside it (one from Disc 1 and one from Disc 2).
2. Compress the folder into a ZIP file.
3. Go to https://wetransfer.com
4. Upload the ZIP file.
5. Enter the MusicCovered email address I previously provided as the recipient.
6. Click Transfer to send the files.

That’s all! I’ll receive an email with a download link.

Please make sure you don’t modify the audio files or their metadata before sending them, so I can analyze the original tags and identify what’s causing the issue.

I sent you the files via wetransfer.

Hi,

I’ve received your files and tested them in MusicCovered.

I simply dragged and dropped the two audio tracks into the MusicCovered library, and the application correctly recognized them as belonging to two separate discs of the same album, without any issues.

As you can see in the attached screenshots, MusicCovered correctly identifies Disc 1 and Disc 2, so the metadata in the files appears to be perfectly fine.

This suggests that the issue might be related to something else in your library or the way the album was originally imported.

When I check each of the folders for information, I get the following warning message (see below):

It says that 4 files are in folders that do not match their current tags. Musiccovered does not reorganize folders automatically after tags are edited by another app.

How do I deal with this, since all my multidisc albums exist as individual discs. I have never had this issue with any other music application.

Please advise.

Hi,

The reason i mentioned this is that for the same files I gave you, in my library, these files appear in separate folders, not as part of 1 album with Disc 1 and Disc 2. Each of these folders appears to have all the correct information and are labeled Disc 1 and Disc 2. All my double albums appear as individual discs, not as one album with two discs included. Trying to understand how to fix this.

Here are the 2 separate listings for the jarrett album we have spoken about. Note they appear as two separate albums rather than one.

Hi,

Now I completely understand the issue!

I recreated your exact setup using two separate folders and was finally able to identify where the problem was coming from.

I’ve already fixed the bug, and the fix will be included in the next version of MusicCovered.

Thank you for your patience and for helping me track this down. Your feedback was very helpful in identifying and resolving the issue!

So at this point I will not do anything further and wait for the fix. Is that your recommendation?

Thanks,

Bruce

Hi Bruce,

Yes, exactly. If you prefer to keep the two discs in separate folders, my recommendation is to wait for the next version of MusicCovered, which will include the bug fix I’ve already implemented.

However, if you place both discs inside a single album folder, within the artist’s folder, the problem doesn’t occur, and MusicCovered will correctly recognize and organize both discs.

This is actually the folder structure used by iTunes and Apple Music, which originally inspired MusicCovered’s library organization.

So you have two options: keep your current folder structure and wait for the update, or temporarily organize both discs into a single album folder.

Either way, the issue has been identified and fixed, so you won’t have to worry about it in the next release.

Thanks again for your patience and for helping me identify this bug!